Related
Hi,
I'm desperate! Problems startet when the phone (defy, green lense) could not be charged anymore. Always getting a question mark. Tried the original charger as well as third party charger.
Anyway, right now my recovery is screwed and I cannot boot the phone anymore!
How do I get out of this mess?
First I'd like to get recovery working, I guess. Have adb access but how do I flash a recovery via adb? Or better question where do I get the recovery image file? Cannot find any .img - always .zip files.
(I'd appreciate a solution that doesn't involve Windows)
You can't flash a recovery via adb, since boot loader on defy is locked. I suggest you read up on the beginner's guide and learn how to flash an sbf. Your phone will be then as it was out of the box
Sent from my Nexus 7 using XDA Premium HD app
Damnit!
Worst custom rom phone ever..
Thanks!
Well, actually once you're rooted then installing a recovery is actually installing just an apk 2ndinit search for it once you've flashed an sbf
And we've got really good developers fortunately
Sent from my MB526 using xda premium
Hello guys, first time posting here, I'm pretty sure it's a silly question, sorry if it is but I couldn't find the answer anywhere. I have an unlocked and rooted device, I installed the last 4.3 update this morning, and usually TWRP let me automatically fix the root just after install the update. But this time it just installed it and booted the tablet, and when I try to enter the recovery mode to fix the root in TWRP, I only see the droid with the exclamation mark.
So the problem is that I don't have root, and I cannot enter TWRP to fix it. TWRP went away with the latest update?. For entering the TWRP I pressed vol+ vol- and power and the pick recovery... is it correct?
Thank you in advance for the great community we have in android and sorry for my english
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
3DSammy said:
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
Click to expand...
Click to collapse
Same for me, Starting have some problems as I tried a "reboot to recovery" apk and got it stuck in the bootloader screen and it wasnt going anywhere.. still had TWRP but reflashing things wasnt working..
Used Wug's Nexus Root Toolkit to bring it back to life..
All good
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
prezeus said:
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
Click to expand...
Click to collapse
Nice that it is solved but please do nog use toolkits anymore. I respect the effort and time people take to make them but learning fastboot is just way better. Maybe harder but hard work pays off. Almost everyone will tell the same.
For people who want to use fastboot:
1. Flash custom recovery via fastboot.
2. Boot into recovery.
3. Flash latest supersu.
You can put solved in the title by edeting it.
Sent from my Galaxy Nexus using XDA Premium HD app
same
Good time . I have a similar problem : after a recent update missing root. I tried to flash a custom recovery by fastboot, but the process hangs at downloading recovery.img to nexus. I tried using other drivers and a different version of fastboot, but to no avail.
Ps: by same drivers and fastboot I got the root before.
I had to do a complete wipe from the computer and flashed clockwork mod recovery. Since it was likely an old version I had the double 0 partition problem which I fixed by manually moving the files. I tried to update the recovery to twrp, but it won't flash using goomanager. It downloads and says it's flashed but it's not there.
I also seem to have a weird problem where I have to push the power button to get it to boot past the Google screen. If I don't push power it gets stuck there forever.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk 4
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
SlowCobra96 said:
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
T-Keith said:
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This might be an odd question, but have you tried just updating CWM first, and THEN flashing TWRP? Sometimes the flash won't go smoothly with an older version of one recovery to a newer version of a different recovery- not sure why, but that's just been my experience. I would update CWM first then try flashing TWRP.
Also, if goo is not working for you, you could try Rom Manager to update CWM and then flash TWRP. It can flash either. (If you really want to flash via the device).
Otherwise, (me personally) I'd just use adb fastboot to flash a new recovery.
Hope that helps
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
No problem. Let us know how it works out for you.
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Ahh, that sucks! How are you *attempting to* access recovery... via reboot menu, via adb, or via 3-button press? It shouldn't matter, but you could try all three methods to see if any way will give you recovery access. Then, if/when you manage to get in, you could reflash again straight from recovery. I'm going to do some digging to see if I can find a better solution. I KNOW I've read about the same issue before, I know there's a solution... I just have to find it again.
Worse comes to worse, you might have to reflash stock recovery then reflash custom recovery. Might be a corrupt recovery img, but I will check and try some things out and let you know what I find.
Edited to add:
Yes. there was a bug in the older bootloader that bypassed/refused access to recovery... so since you restored stock, you probably need to update your bootloader to at least to version 4.18 (via fastboot). THEN you should be able to access recovery. I can't add links, but I can give you a text link once I find just the IMG file instead of the full firmware. Honestly, I never do backups so I don't have the file on hand. However, I may do one backup at least so I can extract my boot img and give it to you.
OK, so I found the info I was looking for.
From Elsewhere:
Steps:
Install latest nexus 7 bootloader.
This fixes the boot loader bug and now you can enter recovery from the bootloader screen.
Update the bootloader to at least 3.18. Make sure NOT TO DELETE THE BOOTLOADER!!!!!!!!!!!!!
I cannot emphasize this enough!!!!!!!!!!! I bricked my first one this way.
Use
fastboot flash bootloader C:\>>>>>>\bootloader-grouper-3.18.IMG***
Click to expand...
Click to collapse
Do NOT erase bootloader before you flash the new one. And after you have flashed the new one type;
fastboot reboot bootloader
Click to expand...
Click to collapse
and check the bootloader version to make sure you succeeded.
Click to expand...
Click to collapse
***Or whatever you name the boot img file!***
https://dl.dropboxusercontent.com/u/19608328/boot.img.zip --> This is from MY Nexus 7. It's Bootloader version 4.23, and works with JB 4.2.2- it does NOT have the recovery access bug.
https://dl.dropboxusercontent.com/u/19608328/recovery.img.zip --> This is a copy of MY CWM, which I just updated to 6.0.3.6 yesterday.
I'd flash the bootloader, then flash your recovery of choice. Not being able to access recovery is a bootloader issue, not a recovery issue. The fact that you restored/reverted an older full firmware put you on an older bootloader that would not allow users to access recovery.
Try the new(er) bootloader, it should work. My device is a 16gb grouper Nexus 7 running 4.2.2. Before that, it ran 4.1.2 without any issues, so it should work to resolve the problem you're having.
I've spent hours scouring these forums for this answer and I can't figure this out and need help. I had a flash go bad and caused me to hang at the LG logo. I followed the instructions on how to revert to stock and after several attempts and methods, I managed to get to a Verizon boot loop after flashing the 12b kdz. Then using the tot method, I got the 11a to work. So, now I am back to stock and re-rooted with ioroot20.
Now no matter what I do, I cannot boot to CWM recovery. Please help. All I can get is the Android laying on his side with an exclamation point inside a red triangle.
unkle_77 said:
I've spent hours scouring these forums for this answer and I can't figure this out and need help. I had a flash go bad and caused me to hang at the LG logo. I followed the instructions on how to revert to stock and after several attempts and methods, I managed to get to a Verizon boot loop after flashing the 12b kdz. Then using the tot method, I got the 11a to work. So, now I am back to stock and re-rooted with ioroot20.
Now no matter what I do, I cannot boot to CWM recovery. Please help. All I can get is the Android laying on his side with an exclamation point inside a red triangle.
Click to expand...
Click to collapse
Since you flashed back to stock, the restore process restored stock recovery (dead android with red exclamation). You need to reinstall a custom recovery.
Sent from chdhsheh fhhdud
I've done that several times. The way I am doing it is through clockwork and just letting it download. Is there another way I should be doing it?
Use freegee from the play store to install twrp or cwm...
Sent from my VS980 4G using xda app-developers app
unkle_77 said:
I've done that several times. The way I am doing it is through clockwork and just letting it download. Is there another way I should be doing it?
Click to expand...
Click to collapse
You can use the adb file in ioroot to flash your recovery. Adb will verify if your recovery has been flashed properly.
Use one of these files
http://forum.xda-developers.com/showthread.php?p=48879826
And follow this guide
http://forum.xda-developers.com/showthread.php?p=45713343
Option one is the best/safest
Sent from chdhsheh fhhdud
scram99 said:
Use freegee from the play store to install twrp or cwm...
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
That worked! THANK YOU THANK YOU THANK YOU. What a simple solution.
What does that do different than installing through CWM?
Hello, i accidentally flash twrp on to my phone (should just boot it). Now i dont have stock recovery anymore. i have tried flash my phone using stock recovery i got from here, here and here. but still no luck. anyone can help?
my phone firmware is latest marsmallow. Unlocked Bootloader and Rooted using miaulightouch method.
Thanks,
FRezING
FRezING said:
Hello, i accidentally flash twrp on to my phone (should just boot it). Now i dont have stock recovery anymore. i have tried flash my phone using stock recovery i got from here, here and here. but still no luck. anyone can help?
my phone firmware is latest marsmallow. Unlocked Bootloader and Rooted using miaulightouch method.
Thanks,
FRezING
Click to expand...
Click to collapse
The links you give mostly for L.. I don't know if that will work on M though
Try to extract boot.img from your Asus zip and flash it, root might lost (?)
#sfmbe
Sent from my ASUS_Z00RD using XDA Labs
testeraphy said:
The links you give mostly for L.. I don't know if that will work on M though
Try to extract boot.img from your Asus zip and flash it, root might lost (?)
#sfmbe
Sent from my ASUS_Z00RD using XDA Labs
Click to expand...
Click to collapse
Thanks for reply, ya all of them for Lollipop because i have tried to flash boot.img from stock Marshmallow but still no recovery so i tried using Lollipop still no luck. Yesterday i tried back2stock method the rom flashed sucessfully but still no stock recovery.
Thanks,
FRezING
FRezING said:
Thanks for reply, ya all of them for Lollipop because i have tried to flash boot.img from stock Marshmallow but still no recovery so i tried using Lollipop still no luck. Yesterday i tried back2stock method the rom flashed sucessfully but still no stock recovery.
Thanks,
FRezING
Click to expand...
Click to collapse
So, I'm curious about it, and flash twrp myself just awhile ago...
And got bootloop, really... wait, seriously?
I'm like
How did the other day I'm able to survive this? It boot normally,
After 1st successful boot, flashing root, (I don't remember but just say I'm booting twrp this time), xposed, aware that root lost after reboot, I did my backup here,
Then deciding to start from scratch, installing official Asus, boot normally, flash twrp, rooting,rebooting few times and somehow root intact, install xposed, root lost...
Restart again, install Asus official (I'm not restoring my backup, really, the only thing I know how to install stock is by stock recovery itself) , boot twrp, install root by system, reboot, root intact, xposed, root intact, surfing net, registering xda yesterday, just now replying to your thread, then you can read from above again...
Just few minutes ago, restore recovery from backup (still bootloop though), installing Asus again, and make this reply...
Sorry can't help you, even I'm confused right now
Sent from my ASUS_Z00RD using XDA Labs
testeraphy said:
So, I'm curious about it, and flash twrp myself just awhile ago...
And got bootloop, really... wait, seriously?
I'm like
How did the other day I'm able to survive this? It boot normally,
After 1st successful boot, flashing root, (I don't remember but just say I'm booting twrp this time), xposed, aware that root lost after reboot, I did my backup here,
Then deciding to start from scratch, installing official Asus, boot normally, flash twrp, rooting,rebooting few times and somehow root intact, install xposed, root lost...
Restart again, install Asus official (I'm not restoring my backup, really, the only thing I know how to install stock is by stock recovery itself) , boot twrp, install root by system, reboot, root intact, xposed, root intact, surfing net, registering xda yesterday, just now replying to your thread, then you can read from above again...
Just few minutes ago, restore recovery from backup (still bootloop though), installing Asus again, and make this reply...
Sorry can't help you, even I'm confused right now
Sent from my ASUS_Z00RD using XDA Labs
Click to expand...
Click to collapse
It's ok thanks for your help tho, my phone still usable im just curious why the stock recovery still missing after flashing it via fastboot. u can use back2stock method if bootloop that method really handy no need to wipe anything i use it before when bootloop and my data still there.
FRezING said:
It's ok thanks for your help tho, my phone still usable im just curious why the stock recovery still missing after flashing it via fastboot. u can use back2stock method if bootloop that method really handy no need to wipe anything i use it before when bootloop and my data still there.
Click to expand...
Click to collapse
My phone already recovered by the time I'm replied above, and somehow.. systemless work.. duh
back to topic
Sent from my ASUS_Z00RD using XDA Labs
testeraphy said:
My phone already recovered by the time I'm replied above, and somehow.. systemless work.. duh
back to topic
Sent from my ASUS_Z00RD using XDA Labs
Click to expand...
Click to collapse
How did u fix dat issue? no recovery here and on booting logo it shows invalid boot.img
Plz help
arunperul said:
How did u fix dat issue? no recovery here and on booting logo it shows invalid boot.img
Plz help
Click to expand...
Click to collapse
Sorry, which part?
If about how I got my recovery back then, I don't really understand, let's assume I have my backup that time. now I have my backup, for real.
From what I understand, invalid boot mean either you got broken boot images or locked bootloader, so which one is familiar to you?
Anyway, you can try to flash back stock boot (grab from asus zip) and stock recovery (if you have them, or find on this forum?).
I don't know if locked bootloader can flash boot/recovery, never tried it myself. So, good luck!
Sent from my ASUS_Z00RD using XDA Labs