Database Develop

Bricked phone, urgent help requested!

So earlier I was flashing TrickDroid, and Aroma froze and crashed the phone while it was installing... CWM showed a screen that said root may have been lost, and offered to fix root. I touched it, and this got the phone stuck in a continual boot loop. I've managed to get into the bootloader, but this is after clearing the cache with the terminal command "fastboot clear cache", and I have to type "fastboot reboot bootloader" when the phone boots up (at the HTC logo) in order to even get into the boot loader... otherwise, the phone will try to enter recovery (to no avail). I really hope I did not brick the phone... any help would be great. Can I fastboot a stock image?

NowhereOutThere said:
So earlier I was flashing TrickDroid, and Aroma froze and crashed the phone while it was installing... CWM showed a screen that said root may have been lost, and offered to fix root. I touched it, and this got the phone stuck in a continual boot loop. I've managed to get into the bootloader, but this is after clearing the cache with the terminal command "fastboot clear cache", and I have to type "fastboot reboot bootloader" when the phone boots up (at the HTC logo) in order to even get into the boot loader... otherwise, the phone will try to enter recovery (to no avail). I really hope I did not brick the phone... any help would be great. Can I fastboot a stock image?
Click to expand...
Click to collapse
Reboot into fastboot and try to fastboot erase cache then fastboot flash recovery again. If you can get into recovery, just try to reflash your ROM or do a NAND restore. Otherwise, use the All-in-One toolkit to help you adb sideload a ROM(this will bypass Aroma's epic failure rate, too, btw).

unremarked said:
Reboot into fastboot and try to fastboot erase cache then fastboot flash recovery again. If you can get into recovery, just try to reflash your ROM or do a NAND restore. Otherwise, use the All-in-One toolkit to help you adb sideload a ROM(this will bypass Aroma's epic failure rate, too, btw).
Click to expand...
Click to collapse
Great, worked like a charm. I flashed a different version of CWM this time, that might have been the problem? Oh well. Thanks!

[Q] Trouble while flashing KitKat - Recovery gone

Hi folks,
I have a problem. I tried to flash SinlessRom GE Kitkat 5.1. It flashed allright, but then I got in a boot loop. It boots, but when the set up starts, and I see the screen where to choose the language, then device boots again (and it becomes a bootloop).
I interrupted the boot loop using Vol-down and power, but my recovery wasn't working. When I chose recovery, it didn't entered recovery but booted again.
Then I tried to flash a new recovery, but now I doesn't enter a new bootloop, but get's stuck at the white HTC Screen with in pink "entering recovery..."
I tried to erase cache in fastboot modus, but it didn't help.
Do you guys can help me? Any suggestions?

wybren said:
Hi folks,
I have a problem. I tried to flash SinlessRom GE Kitkat 5.1. It flashed allright, but then I got in a boot loop. It boots, but when the set up starts, and I see the screen where to choose the language, then device boots again (and it becomes a bootloop).
I interrupted the boot loop using Vol-down and power, but my recovery wasn't working. When I chose recovery, it didn't entered recovery but booted again.
Then I tried to flash a new recovery, but now I doesn't enter a new bootloop, but get's stuck at the white HTC Screen with in pink "entering recovery..."
I tried to erase cache in fastboot modus, but it didn't help.
Do you guys can help me? Any suggestions?
Click to expand...
Click to collapse
try erasing the userdata using fastboot. I has a similar problem earlier this week and I remember using that command. Sometime when I enter recovery it just goes to normal boot (randomly), not sure if thats your problem but try entering recovery multiple times. If not...
fastboot erase userdata
fastboot erase cache
fastboot flash recovery recovery.img

wybren said:
Hi folks,
I have a problem. I tried to flash SinlessRom GE Kitkat 5.1. It flashed allright, but then I got in a boot loop. It boots, but when the set up starts, and I see the screen where to choose the language, then device boots again (and it becomes a bootloop).
I interrupted the boot loop using Vol-down and power, but my recovery wasn't working. When I chose recovery, it didn't entered recovery but booted again.
Then I tried to flash a new recovery, but now I doesn't enter a new bootloop, but get's stuck at the white HTC Screen with in pink "entering recovery..."
I tried to erase cache in fastboot modus, but it didn't help.
Do you guys can help me? Any suggestions?
Click to expand...
Click to collapse
khhhhris said:
try erasing the userdata using fastboot. I has a similar problem earlier this week and I remember using that command. Sometime when I enter recovery it just goes to normal boot (randomly), not sure if thats your problem but try entering recovery multiple times. If not...
fastboot erase userdata
fastboot erase cache
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
1- are you s-on or s-off, 4.4 is not compatible (at least for now) with S-On devices!
2- you need to "fastboot erase cache" after flashing recovery; personally i do it before and after, but the important part is after
3- why are you recommending "fastboot erase userdata", just wondering.

nkk71 said:
1- are you s-on or s-off, 4.4 is not compatible (at least for now) with S-On devices!
2- you need to "fastboot erase cache" after flashing recovery; personally i do it before and after, but the important part is after
3- why are you recommending "fastboot erase userdata", just wondering.
Click to expand...
Click to collapse
+1, s-off is required. I only recommend erasing userdata because I had a very similar issue, erasing userdata and a fresh recovery seemed to do the trick after no luck with simply flashing a new recovery and wiping cache Just going off past experience.

khhhhris said:
+1, s-off is required. I only recommend erasing userdata because I had a very similar issue, erasing userdata and a fresh recovery seemed to do the trick after no luck with simply flashing a new recovery and wiping cache Just going off past experience.
Click to expand...
Click to collapse
good to know, was "fastboot erase userdate" successfully? what kind of output did you get?

nkk71 said:
good to know, was "fastboot erase userdate" successfully? what kind of output did you get?
Click to expand...
Click to collapse
Thanks all for the response.
This did the trick:
erase cache
flash twrp recovery (first I tried cwm)
erase cache
Then I managed to enter twrp recovery and flash a new rom.
Don't know why, but I'm happy again
Thanks for the help.

Cool.. hit the users's thanks button!

[Q] No Recoveries Working

I recently got an HTC One M7(ul) and have been trying to install a custom recovery to install KitKat or Lollipop. So far the only recovery that has worked has been Philz recovery and even then only up to version 6.25.0(All versions after that were 'unified' but don't work). All recoveries appear to install correctly in Fastboot but when booting recovery it hangs on the 'Entering Recovery' screen, flashes a black screen once and returns to 'Entering 'Recovery'. Is this a known problem or am I doing something really weird?

robtherobot101 said:
I recently got an HTC One M7(ul) and have been trying to install a custom recovery to install KitKat or Lollipop. So far the only recovery that has worked has been Philz recovery and even then only up to version 6.25.0(All versions after that were 'unified' but don't work). All recoveries appear to install correctly in Fastboot but when booting recovery it hangs on the 'Entering Recovery' screen, flashes a black screen once and returns to 'Entering 'Recovery'. Is this a known problem or am I doing something really weird?
Click to expand...
Click to collapse
Are you flashing recovery with the correct procedure?
Code:
fastboot flash recovery name-of-recovery.img
fastboot erase cache
fastboot reboot-bootloader
Then select recovery from the bootloader menu it should load fine

Danny201281 said:
Are you flashing recovery with the correct procedure?
Code:
fastboot flash recovery name-of-recovery.img
fastboot erase cache
fastboot reboot-bootloader
Then select recovery from the bootloader menu it should load fine
Click to expand...
Click to collapse
Yeah, I've tried many different versions and methods

robtherobot101 said:
Yeah, I've tried many different versions and methods
Click to expand...
Click to collapse
mmmmm! Try this on http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img :fingers-crossed:

wtf how did you know that would work?

Can I flash KitKat/Lollipop with this recovery?

robtherobot101 said:
Can I flash KitKat/Lollipop with this recovery?
Click to expand...
Click to collapse
Its not the first time I came across this problem here on xda. 2.6.3.3 has always been the most Stable and reliable version. And for some reason works even with this problem.
2.6.3.3 should work fine with kitkat roms but I'm not sure about lollipop. Unfortunately this Is the only recovery that works in this situation and I'm not sure what causes this issue.
The weird thing is in most cases the recovery actually loads normally but the screen stays stuck on the "Entering recovery" screen. While it's stuck like that you can type "adb devices" it should give the normal output showing the device is in fact in recovery. But for now it means your kinda stuck with 2.6.3.3.

[Q] Mismatched partition size (recovery) when flashing stock 5.0.1 recovery

I am trying to back out everything I've done to the phone and start fresh with 5.1. I had rooted, decrypted, and installed TWRP. To undo this, I did a factory reset, downloaded the shamu-lrx22c factory image from google, and used adb/fastboot to put it all back the way I found it. These are the commands I used :
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
It appeared to all work. Now when I try to get back into recovery, the phone sits at the android with the red triangle and !. The bootloader logs state "Mismatched partition size (recovery)."
Did I do a bad thing somewhere along the way? Thanks in advance.

Try flashing the recovery again. I think if I was you I would also fastboot -w to format the userdata and cache since you already did a factory reset or use google's images by using "fastboot flash userdata userdata.img", "fastboot erase cache" and then "fastboot flash cache cache.img".
Also, check the md5 of the image you downloaded to make sure it was not corrupt.

Evo_Shift said:
Try flashing the recovery again. I think if I was you I would also fastboot -w to format the userdata and cache since you already did a factory reset or use google's images by using "fastboot flash userdata userdata.img", "fastboot erase cache" and then "fastboot flash cache cache.img".
Also, check the md5 of the image you downloaded to make sure it was not corrupt.
Click to expand...
Click to collapse
I used fastboot -w to format the userdata/cache. And I also tried the three fastboot commands you listed. They all seem to work, but the reflashing of the recovery still throws the same error.
MD5 checksum of the whole zip is the same. I re-extracted the recovery.img file just to be sure and it still throws the same error.

Kramit said:
when I try to get back into recovery, the phone sits at the android with the red triangle and !.
Click to expand...
Click to collapse
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen

rootSU said:
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen
Click to expand...
Click to collapse
Sadly, that doesn't do anything. Pressed repeatedly, held down for a while, nothing. up until the point where it reboots from the power button being held long enough.

rootSU said:
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen
Click to expand...
Click to collapse
yes, thats norml

cmh714 said:
yes, thats norml
Click to expand...
Click to collapse
Hmm. And if it doesn't work?

Kramit said:
I am trying to back out everything I've done to the phone and start fresh with 5.1. I had rooted, decrypted, and installed TWRP. To undo this, I did a factory reset, downloaded the shamu-lrx22c factory image from google, and used adb/fastboot to put it all back the way I found it. These are the commands I used :
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
It appeared to all work. Now when I try to get back into recovery, the phone sits at the android with the red triangle and !. The bootloader logs state "Mismatched partition size (recovery)."
Did I do a bad thing somewhere along the way? Thanks in advance.
Click to expand...
Click to collapse
I have the same problem here but maybe i have found a solution for it:
what i did was i left the 5.1 bootloader.img and took all the other stuff from a 5.0 factory image such as: radio.img, system.img..... fastbooted everything and i was with a 5.0 LP stock out of the box, then i have rooted it, installed twrp with f2fs support and voila i'm now good to go
hope this will help you out

Kramit said:
Sadly, that doesn't do anything. Pressed repeatedly, held down for a while, nothing. up until the point where it reboots from the power button being held long enough.
Click to expand...
Click to collapse
When you see the android with the red triangle and !, you need to hold the power button, and while you are holding it down, press volume up. Pushing them both together, or one after the other, or holding them down together or whatever else won't work.
Sent from my Nexus 6 using Tapatalk

While upgrading from 6.01-7.0 crashed at 83% Now Stuck at Google logo image w/Unlock

Any help appreciated here, I have been searching the forums all morning, but haven't found the same issue as mine (lots of stuck at google ?'s but none from failed upgrade) last night I decided to take the plunge and update my N6 from build 6.0.1 (MOB31H, Oct 2016) to 7.0.0 (NBD90Z, Oct 2016)
I typically use the WugFresh NRT to upgrade via factory image. Last night I decided to give the OTA images a try.
Everything was going smoothly until I bumped my keyboard tray and my phone became disconnected while still flashing. It was almost done too.....it was at the point of flashing the system image and was interrupted at 83% and it failed install.
I then attempted to recover from this by flashing entire factory image for 7.0 but it doesn't seem to want to mount my device. I then tried to go back and flash 6.01 to device using the softbrick/bootloop function from the NRT toolkit. It seemed to partially work as the size of the word google on the screen changed during boot went smaller (so I assume the boot.img was able to flash?) but I am still stuck at the google logo with the unlock at the bottom. Bright side is device is bootloader unlocked.
If I try the recover from bootloop function on the NRT it seems to have trouble sending files to phone (goes through all the process just doesn't take it looks like it sending files but before each at beginning it doesn't seem to connect to device.
I can access bootloader, and recovery. In recovery I tried to wipe/cache (wipes but doesn't help), tried factory reset (wipes but still stuck at Google), tried to mount system through selecting via recovery and it fails.
Not sure which image I should try to flash now to recover 6.01 or 7.0 or if I can even recover from this? Any suggestions are appreciated.
When I first got my phone I did create a backup using the NRT but that was on I think 5.0 or 5.01 and I no longer have twrp installed, should I try putting twrp on it and restoring that back up? It was a long time ago and I am not sure if it will cause radio or boot img issues...since I have upgraded so far past without making another backup with a newer version.
I have read that some others with similar issues that were told to use the N beta to get a clean flash.....only issue is there is no longer a N beta for Nexus 6......it now only shows 7.01 for 6p, 5x, and pixel.
Should I try flashing twrp and a ROM? And after see if I can get to load that way then go back and flash stock image?
Any help or suggestions are appreciated.

On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit

Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
just a silly question really , can this work on on a locked bootloader /not rooted device ?

touns_j said:
just a silly question really , can this work on on a locked bootloader /not rooted device ?
Click to expand...
Click to collapse
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.

wavechapter said:
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.
Click to expand...
Click to collapse
alright , i thought twrp could be replaced with stock recovery

Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
Thank You Dirty_Jerz! I really appreciate the help.
I am now back up and running on 7.0!