Bricked my phone while trying to Flash

[PoRco1x]

Yeah I had something similar when I flashed something that wasn't compatible with the ROM. Once I reflashed recovery I was good. Glad you got it working.

Now that you got back into recovery, I would just restore your last backup and maybe redownload the ROM you're trying to flash it pick a new ROM.

Sent from my HOX+ loaded with Elegancia ROM v5.2.0

I don't know how to copy the file into my sd though...The device is being detected by my pc but I can't access the file system in it. It just showing as a drive with no GB in it whatsoever . when I use "adb devices" in cmd it shows my device along with the serial id though.

Is there a way to do it through CMD or something? Cause when I plug in the device, my pc says something like "Unrecognizes device driver installation failed" or something like that.

Tried installing htc drivers myself, that didnt work.

 

[VDub2174]

Before you flashed the ROM your having issues with, you did a nandroid backup right?

 

[PoRco1x]

Yeah I had something similar when I flashed something that wasn't compatible with the ROM. Once I reflashed recovery I was good. Glad you got it working.

Before you flashed the ROM your having issues with, you did a nandroid backup right?

No I didn't Followed the advice of one of the forumers on my other thread and didn't mention I had to. He said it was a really simple process and I have nothing to worry about. I should have known better and asked more questions.

Which is why I'm thinking ten times before taking any steps atm

 

[PoRco1x]

Yeah I had something similar when I flashed something that wasn't compatible with the ROM. Once I reflashed recovery I was good. Glad you got it working.

Just watched this video Tutorial - How To Use ADB - Includes Sideloading - Nexus 4 - YouTube

Should I try pushing in a new Rom using the adb push ?

 

[VDub2174]

No I didn't Followed the advice of one of the forumers on my other thread and didn't mention I had to. He said it was a really simple process and I have nothing to worry about. I should have known better and asked more questions.

Which is why I'm thinking ten times before taking any steps atm

Always always always make a backup.....lol I obsessively make one any time I flash anything to my phone.

Sent from my HOX+ loaded with Elegancia ROM v5.2.0

 

[scorpiodsu]

Just watched this video Tutorial - How To Use ADB - Includes Sideloading - Nexus 4 - YouTube

Should I try pushing in a new Rom using the adb push ?

Yes push via ADB. This method is typically used when users cannot access the file system anymore or they've mistakenly removed the OS entirely. I will note that when I flashed AR it got stuck on 30% for like 5 mins and then continued to install. It's a problem with the aroma installer and not the ROM. Always make a backup before you flash anything in the future so you can easily go back . Good luck.

 

[mstrblueskys]

Should I try pushing in a new Rom using the adb push ?

Yes - or run the RUU while in the bootloader. In fact, if you got stuck with the install of a new ROM, it may be best to reboot to bootloader and run the RUU, then reroot your device.

 

[PoRco1x]

Yeah I had something similar when I flashed something that wasn't compatible with the ROM. Once I reflashed recovery I was good. Glad you got it working.

Yes push via ADB. This method is typically used when users cannot access the file system anymore or they've mistakenly removed the OS entirely. I will note that when I flashed AR it got stuck on 30% for like 5 mins and then continued to install. It's a problem with the aroma installer and not the ROM. Always make a backup before you flash anything in the future so you can easily go back . Good luck.

Yes, I've read around and it seems that a lot of people get stuck at 30%! Just tried reinstalling..stuck again at 30% ... I'll wait a few minutes I guess

- - - Updated - - -

Yeah I had something similar when I flashed something that wasn't compatible with the ROM. Once I reflashed recovery I was good. Glad you got it working.

Yes - or run the RUU while in the bootloader. In fact, if you got stuck with the install of a new ROM, it may be best to reboot to bootloader and run the RUU, then reroot your device.

Problem i I can't get into the bootloader , is there a way to run RUU without bootloader? I can, however, get into recovery.

 

[scorpiodsu]

Yes - or run the RUU while in the bootloader. In fact, if you got stuck with the install of a new ROM, it may be best to reboot to bootloader and run the RUU, then reroot your device.

I agree here and the bootloader has to be relocked to run RUU and seems he can't get into bootloader mode. This is my preferred method as well when I want to start from scratch.

 

[scorpiodsu]

Yes, I've read around and it seems that a lot of people get stuck at 30%! Just tried reinstalling..stuck again at 30% ... I'll wait a few minutes I guess

- - - Updated - - -





Problem i I can't get into the bootloader , is there a way to run RUU without bootloader? I can, however, get into recovery.

Can you use the tool to boot you into bootloader or lock it? I see there are options to do so as well as sideload a ROM. See if it can get you there so you can relock and run RUU. See if any of those options work for you.

 

[PoRco1x]

Yeah I had something similar when I flashed something that wasn't compatible with the ROM. Once I reflashed recovery I was good. Glad you got it working.

Can you use the tool to boot you into bootloader or lock it? I see there are options to do so. See if it can get you there so you can relock and run RUU. If not, adb push a stock ROM that doesn't need aroma.

Haven't tried locking the bootloader, but tried booting to bootloader using the tool and didn't work. It just restarted the phone

 

[scorpiodsu]

Haven't tried locking the bootloader, but tried booting to bootloader using the tool and didn't work. It just restarted the phone

Yeah you have to lock the bootloader to run RUU. But like I said, try using the options in the AIO tool to see if it can get you you into bootloader and/or relock it for you then. If you can get there then running the RUU is the easy part.

Also, some of the RUU have been made into ZIPs which you can run like any other ROM. Try that if you cannot get into the bootloader nor lock it. This thread has a good collection of stock ROMs and RUU files. If you cannot get RUU to run, just sideload a stock ROM using the AIO tool or adb.

[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads - xda-developers

 

[PoRco1x]

Yeah I had something similar when I flashed something that wasn't compatible with the ROM. Once I reflashed recovery I was good. Glad you got it working.

Can you use the tool to boot you into bootloader or lock it? I see there are options to do so as well as sideload a ROM. See if it can get you there so you can relock and run RUU. See if any of those options work for you.

Just tried pushing and cmd is giving error message "failed to copy : Read-only file system"

 

[scorpiodsu]

Just tried pushing and cmd is giving error message "failed to copy : Read-only file system"

Try this command to remount in adb:

mount -o remount,rw /dev/block/mtdblock3 /system

Or, try typing this in terminal/cmd:

adb remount

 

[PoRco1x]

Yeah I had something similar when I flashed something that wasn't compatible with the ROM. Once I reflashed recovery I was good. Glad you got it working.

I was following advice on this thread and now I'm stuck on a different screen. God help me...

[Q] Help! Bricked my phone during Flash! - Page 7 - xda-developers

I was trying to sideload a Rom and got stuck on the Sideload started screen. Phone won't reboot. Tried holding down power button under bright light etc etc. Nothign works. It's..stuck.

 

[PoRco1x]

Yeah I had something similar when I flashed something that wasn't compatible with the ROM. Once I reflashed recovery I was good. Glad you got it working.

Gonna have to try waiting for phone to reset

 

[BobR1908]

Gonna have to try waiting for phone to reset

I totally understand why some Flash and play around with ROM's but reading this thread has made me realize exactly why I don't LOL. Sounds like this has been a total nightmare and I hope everything turns out alright for you mate.

My fingers are crossed for you.

 

[Ryandroid86]

I dont recommend AIO tool kits. They can just make it more confusing because you dont know what its doing.
I would use Fastboot (unless the debugging was off)

Also you can run an RUU even if the bootloader is unlocked. You will just need to flash the stock Boot.img first via fastboot. (fastboot flash boot boot.img) or push the boot.zip through ADB and install via recovery.
HTC can be tricky and one of the worst to root. but keep at it.

Read some forums on XDA. They will help you. But Id ditch the tool kit.
Once I learned all the CMD lingo... its way easier.

 

[PoRco1x]

I dont recommend AIO tool kits. They can just make it more confusing because you dont know what its doing.
I would use Fastboot (unless the debugging was off)

Also you can run an RUU even if the bootloader is unlocked. You will just need to flash the stock Boot.img first via fastboot. (fastboot flash boot boot.img) or push the boot.zip through ADB and install via recovery.
HTC can be tricky and one of the worst to root. but keep at it.

Read some forums on XDA. They will help you. But Id ditch the tool kit.
Once I learned all the CMD lingo... its way easier.

Lol this entire experience made me learn some cmd lingo in regards to ADBs

I realized the toolkit was just doing for you what you would type in the cmd

- - - Updated - - -

UPDATE : I ended up just returning the phone and getting my 500$ back from the guy who sold it to me. The phone was supposed to be sold to me with stock on it and not a mod, so I convinced him to give me back my money. Phew

Didn't want to deal with the hassle and figured that the sooner I try and return it the better. I'm gonna buy a locked unrooted phone next... AND MAYBE root it etc... However, I'm really reluctant after the hassle all of this has caused.

Btw ,A guy who is with BELL is selling his phone. Will it be easy to unlock it and have it working on Fido? Or should I stay away from that?

(AFAIK this shouldn't be a problem but I'm really questioning every step I take from hence forth )

 

[TarekElsakka]

I am glad this is all sorted, you did the right thing. Yeah, sim unlocking is possible but mine is unbranded and unlocked so I haven't really looked into it. To be honest with you, rooting and installing custom ROMs is extremely easy, it's just the Chinese software the pretty much messed up everything on your older device. I'd say wait and get an unbranded and unlocked one to avoid the hassle of learning how to unlock it, using ADB commands and doing things that may or may not brick your device if something goes wrong, why take the risk on a $500+ investment?

After you get an unlocked device, we can then talk about rooting and custom ROMs and whether you really need them. Yesterday I had a terrible experience with my device as it wasn't connecting to any network the whole day after I updated its firmware. I tried all the modems/radios available, several custom ROMs and nothing was working; I then decided it was time to download an install a RUU and that fixed everything, and to be honest I am going to stick to the stock 4.1.2 ROM that came with the device and prepare it to receive OTA when it comes.