I had a mt3g and was always able to get to recovery manually. I recently bought a vibrant, rooted using adb, installed clockwork mod recovery, and did a nandroid. I am unable to get recovery manually. Ive tried every combo of vol^ volv that I could find on these posts. Im ready to start having fun, but am worried for this reason. Any help would be appreciated. Heres my question.
If I start flashing, and my phone gets stuck (vibrant screen, galaxy screen, bootloop, etc.), is there any way I can get recovery without having to do it manually? Would I be able to reboot recovery with adb without mounting? Is there's any other way?
Also, if there is a way, how do I get into clockwork mod recovery so I can restore with nadroid? Would I have to have clockworkmod update zip on my sd and reinstall packages thru stock recovery first? Thank you for any help. Im lost!
make sure you have your clockwork recovery on the root of the internal memory and have it named update.zip
open terminal or command prompt and type adb shell. you will get $ type su to get # type reboot recovery then when in samsung recovery select reinstall packages and you will be in clockwork.
Ok, so I can do this on the computer even though the phone can't be mounted? It will recognize the devise and reboot anyway? Sorry, I'm new to adb.
My recovery image seems to be messed up since I can't boot into it. My phone will boot but everytime it does ADW crashes over and over not allowing me to do anything. What can I do to go about getting the recovery fixed again and reflashing to try to smooth everything out?
*Edit*.I think I may have thought of a work around. I emailed my self the launcherpro.apk and installed it through gmail. Now I can access my phone. Now I just need to flash a working recovery..
I do appreciate your help though Riley.
You can try downloading ADW Launcher, putting it on your SD card and boot from recovery, then flash the launcher. It is a far shot, but if launcher is the only problem, maybe reflashing it will do the trick.
** EDIT ** My apologies. I misunderstood. I thought you were referring to a corrupted recovery image that you had made of your ROM!
You say you can't boot into recovery/ what's your phone do or say when trying to boo4 in recovery? You may have to push new recovery image via fastboot.
CGriffiths86 said:
My recovery image seems to be messed up since I can't boot into it. My phone will boot but everytime it does ADW crashes over and over not allowing me to do anything. What can I do to go about getting the recovery fixed again and reflashing to try to smooth everything out?
Click to expand...
Click to collapse
If you have USB debugging turned on you can flash Amon_RA via an adb shell using the flash_image tool - exactly the way the original Eris rooting process worked. With your phone looping, it will run very slowly, but will still succeed.
If you have the S-OFF bootloader installed, you can flash the recovery with fastboot.
I'll have an XDA admin move this thread to the Q&A forum.
Ok guys..I got launcher pro installed so I can actually access my phone now. I attempted to Flash a recovery with Rom Manager and it says it succeeds but it will never boot into it. I do have the bootloader with the "off". Is there a market app or something that can easily flash the recovery? I only ask because I am not at my PC with the android sdk stuff.
CGriffiths86 said:
Ok guys..I got launcher pro installed so I can actually access my phone now. I attempted to Flash a recovery with Rom Manager and it says it succeeds but it will never boot into it. I do have the bootloader with the "off". Is there a market app or something that can easily flash the recovery? I only ask because I am not at my PC with the android sdk stuff.
Click to expand...
Click to collapse
If you can't get to a PC to use adb, you could use a root shell in a terminal emulator to flash recovery using flash_image. That's kind of painful/tedious though - almost enough so to make it worth your while to just wait until you get back to your PC.
It is technically feasible to put together a flashable ROM to re-flash the recovery, but I'm not aware of anyone having done so for the Eris.
Oh ok..well I have RA Eris 1.6.2 recovery on my sd card. So I can just flash it via the termninal emulator, right?
** I tried to install via terminal and it says "header is the same, not flashing recovery". Do you think I could install the stock Eris recovery and reflash Amon's?
UPDATE!!: I got a recovery to flash..YAY..thanks guys
CGriffiths86 said:
Oh ok..well I have RA Eris 1.6.2 recovery on my sd card. So I can just flash it via the termninal emulator, right?
** I tried to install via terminal and it says "header is the same, not flashing recovery". Do you think I could install the stock Eris recovery and reflash Amon's?
Click to expand...
Click to collapse
are you using "flash_image"? If so, where is it from? To my knowledge (the statically linked version from Amon_RA - /sbin/flash_image) is a pretty simplistic program - it performs no checks, and will let you flash total garbage to any named partition on your phone. (Which is why you should verify the md5 of the recovery image before you flash it, BTW; you can use the AFV app for that)
Ok here is the situation
I had BoS installed. I nv flashed, installed Flashback. Everything was working fine. I had the standard recovery. So I wanted to install CWM recovery. Downloaded the 1.2 update.zip and put it in the root of the internal SD with the recovery folder.
I started up, seemed like the update applied. Then the tablet booted up normally perfectly fine. BUT now whenever I try to go into recovery, I get the birds, then "Recovery key detected" "Booting recovery kernel image". Then nothing. It just waits there. Still boots up normally fine.
Is there any way to fix the recovery mode without nv flashing again and loosing all the app installs I've done?
TIA
You can nvflash just the recovery partition or use ADB to flash it.
Instructions for doing that are on the BoS first post.
Edit: According to the changelog for flashback it has Roebeet's recovery pack built in.
Open a terminal emulator on the tablet.
Type "su" without the quote and tap enter.
Grant the terminal app superuser rights
Use one of the following commands...
fixrecovery.sh (for stock recovery)
cwmrecovery.sh (for ClockworkMod)
You might need to navigate to /system/bin if the commands are not recognized in the default directory.
Awesome. Worked like a charm.
Hi all. Before i start i want to say, i read a lot of threaths and comments before i started to booting recovery and i followed Tutorial that you can find somewhere here on XDA for MotoE.
I unlocked Bootloader correctly and everything was right. Then i downloaded latest version of TWRP and CWM if something will be wrong.
So i booted into bootloader, connected to PC (windows 8.1) and using adb i installed TWRP (by command window). After instalation was complete, i used comand: "fastboot reboot" to get my mobile start normally. Everything worked fine so i started last step. Turned off mobile, booted into bootloader(or maybe fastboot? idk...) and by volumebuttons i choosed "Recovery" . Then a black screen for a minute. After that mobile stuck on screen that i attached down below. So i tried this but with CWM (same process way). But nothing new... Someone said me i had to try "Minimal ADB and Fastboot" but again, nothing happend.
Can you help me guys?
The recovery isn't installed! Reinstall the recovery and follow correct steps!
I tried it one more time. I´m attaching image that is from command window showing that .img was booted ... Strange is, immediately after booting was completed, mobile restarted... and after i turned off mobile again, still i can´t reach recovery. Isn´t that problem in .img file? maybe it´s broken, isn´t it?
Tried once again
Ok last try didnt worked. So i complettly followed this guide http://forum.xda-developers.com/moto-e/general/guide-one-moto-e-beginners-guide-t2807891 STEP-BY STEP!
Command window screen attached, Fastboot screen attached.
After reboot, turn off i tried to open recovery and again that image that i posted in first coment. (android figure with words: no command)
By that guide i downloaded recovery from here: https://goo.im/devs/OpenRecovery/condor/
and i downloaded just "openrecovery-twrp-2.7.1.0-condor.img" as i have to do it (written in guide)
Well, your recovery is flashing fine from cmd but its not detected by your phone.
Try re-downloading the recovery and check md5 before flashing.
I'll look into it and see if the issue can be pinpointed.
Btw, you might need the flash the stock ROM back if nothing works.
Tapatalk with RAZR HD
neo.ank said:
Well, your recovery is flashing fine from cmd but its not detected by your phone.
Try re-downloading the recovery and check md5 before flashing.
I'll look into it and see if the issue can be pinpointed.
Btw, you might need the flash the stock ROM back if nothing works.
Tapatalk with RAZR HD
Click to expand...
Click to collapse
Ok i will re-download recovery, is that file that i downloaded ok? i mean should i dowload same file as before?
+ sorry for that but i completly dont know what the "md5" is. can you send me link from where i can learn what it is? you can explain that too but i dont want take your free time.
Mondop said:
Ok i will re-download recovery, is that file that i downloaded ok? i mean should i dowload same file as before?
+ sorry for that but i completly dont know what the "md5" is. can you send me link from where i can learn what it is? you can explain that too but i dont want take your free time.
Click to expand...
Click to collapse
Okay try this.
Flash CWM
If flashing fails or you get any error, then try booting into recovery.
Code:
fastboot boot recovery.img
If you boot into recovery, flash the SuperSU package.
Reboot and then flash the recovery.
See if it works.
neo.ank said:
Okay try this.
Flash CWM
If flashing fails or you get any error, then try booting into recovery.
Code:
fastboot boot recovery.img
If you boot into recovery, flash the SuperSU package.
Reboot and then flash the recovery.
See if it works.
Click to expand...
Click to collapse
no
flashed CWM from here http://forum.xda-developers.com/showthread.php?t=2793625
concretly from here http://www.mediafire.com/download/6odyyqgodw15f1b/recovery.img
then i flashed it, then i rebooted phone then i shuted it off (to boot into fastboot) in fastboot i selected recovery and again, that screen with android figure (no command) so i pressed power button for long. mobile rebooted. again i went into fastboot to write command you said me to boot into recovery. but i stucked at starting screen (that blue big M in "water" cycle)
this all means, files i downloaded was OK but my phone isnt :/
any idea :/
Mondop said:
no
flashed CWM from here http://forum.xda-developers.com/showthread.php?t=2793625
concretly from here http://www.mediafire.com/download/6odyyqgodw15f1b/recovery.img
then i flashed it, then i rebooted phone then i shuted it off (to boot into fastboot) in fastboot i selected recovery and again, that screen with android figure (no command) so i pressed power button for long. mobile rebooted. again i went into fastboot to write command you said me to boot into recovery. but i stucked at starting screen (that blue big M in "water" cycle)
this all means, files i downloaded was OK but my phone isnt :/
any idea :/
Click to expand...
Click to collapse
Do not flash CWM, just boot into it by the command I posted above.
Then try and flash SuperSU, (if you get a root prompt from CWM, select NO.)
Reboot device.
Then again boot into fastboot and now flash recovery (twrp).
neo.ank said:
Do not flash CWM, just boot into it by the command I posted above.
Then try and flash SuperSU, (if you get a root prompt from CWM, select NO.)
Reboot device.
Then again boot into fastboot and now flash recovery (twrp).
Click to expand...
Click to collapse
so now what if i flashed that CWM before?
Now i tried go to fastboot and used just command that you said(to boot into recovery) and as i said, i stucked on motorola starting logo
+ you said i have to flash cwm
Mondop said:
so now what if i flashed that CWM before?
Now i tried go to fastboot and used just command that you said(to boot into recovery) and as i said, i stucked on motorola starting logo
+ you said i have to flash cwm
Click to expand...
Click to collapse
I said if flash is not successful, then boot into it. So you can't boot into recovery either.
Here's last resort, extract the stock recovery from stock ROM and flash it. Then we'll try flashing TWRP again.
If you don't have stock ROM, download it. as you might need it to recover.
neo.ank said:
I said if flash is not successful, then boot into it. So you can't boot into recovery either.
Here's last resort, extract the stock recovery from stock ROM and flash it. Then we'll try flashing TWRP again.
If you don't have stock ROM, download it. as you might need it to recover.
Click to expand...
Click to collapse
Okay, can you give me link with tutorial? i found just this one which restores whole system (and its 4.4.3 and i have now 4.4.4, i mean this will be maybe problem, wouldn´t it?)
i mean this one (tutorial how to restore moto E)
http://forum.xda-developers.com/showthread.php?t=2759495
did you try updating / reinstalling USB-driver on your computer?
magicw said:
did you try updating / reinstalling USB-driver on your computer?
Click to expand...
Click to collapse
no i didnt, think you it will help? i mean if i can connect my mobile into pc without any problem in normal mode and in fastboot too... i will unninstal drivers, intall them again and them i will try unninstal motorola device manager and then again intall him.
(i had newest drivers i can update them)
LOL?
OK im in recovery i already flashed superSU...
What did i do?
As you said, i reinstalled all drivers...
then i downloaded same TWRP again (but with mirror source)
I downloaded attached md5 file ( still dont know what should i do with it )
moved recovery and .md5 files into minimal adb and fastboot (both files i renamed to "recovery")
turned off devices
started fastboot
connected to PC
started command window and entered command "fastboot flash recovery recovery.img"
then i didnt wrote sommand "fastboot reboot" as i done before
i just unpluged usb and navigate to recovery button and launched it
and VUALA im in recovery
hurraaa
just installed superSU and then rebooted.
everything works (superSU too)
i have one more question...
i downloaded twrp manager from google play
first start: asked for root permission a allowed it
then message appeard:
"The only compatible version of busybox we support is Stericson. All other cause havoc on all operations in this app. Please click yes to install Stericson busybox"
what the heck is busybox?
+Should i download it or not?
Do not use TWRP Manager, ROM Manager, CWM Manager or any other of these Tools. They often do not really work good together with "exotic" fones. Why the heck do you need TWRP manager? You have TWRP installed
Anyway - Busybox you also can download and install from Playstore. Busybox is a collection of executable terminal commands helpful for any kind of script. There are a couple of rooted apps who will ask for busybox support - so don't hesitate to install busybox - but do it directly with busybox app from playstore.
After you have installed the binaries you can de-install the busybox-app. Because all necessary binaries then are copied into /system/bin/ folder and the app itself only will become active once a new version would be available (but this is not the case very often).
ok then
magicw said:
Do not use TWRP Manager, ROM Manager, CWM Manager or any other of these Tools. They often do not really work good together with "exotic" fones. Why the heck do you need TWRP manager? You have TWRP installed
Anyway - Busybox you also can download and install from Playstore. Busybox is a collection of executable terminal commands helpful for any kind of script. There are a couple of rooted apps who will ask for busybox support - so don't hesitate to install busybox - but do it directly with busybox app from playstore.
After you have installed the binaries you can de-install the busybox-app. Because all necessary binaries then are copied into /system/bin/ folder and the app itself only will become active once a new version would be available (but this is not the case very often).
Click to expand...
Click to collapse
i have no reason to want twrp manager, i just wanted to look at this app, and i found that busybox there so i wanted to ask here
thx for answer, now i undertand
Hi,
I'm hoping that someone might be able to help me with my issue. I got my G5 H850 (european) today and got TWRP installed, installed SU and was in the process of installing a custom rom (this one https://forum.xda-developers.com/lg-g5/development/stock-h850-20a-eu-rom-flashable-zips-t3506514)
Was using the TWRP install method and using the LG-H85020A-Flashable.COMPLETE.zip
I suspect my issue occured when I performed a wipe and also completed the 'Format Data' option, where I had to type 'yes' to proceed.
I had installed the ROM and SU but now when rebooting system from within TWRP it just shows this orange warning https://support.google.com/nexus/an...4544340095349-2688197337&p=verified_boot&rd=1 and then boots back into TWRP.
I've tried the Terminal Emulator commands to get out of this and also tried the same thing from withing ADB on my computer.
I can still access TWRP and Bootloader, I can also still use ADB and Fastboot commands from my laptop, my phone is still detected. Because of this i'm sure it is still fixable but i'm at a bit of a loss for what to do as everything i'm trying seems to not be working.
Any help at all will be appreciated. My end goal is to have Stock Nougat installed with Root and TWRP
the orange warning comes from unlocking your device and is ok - because there is no other way for root;
try this: TWRP - Go to Wipe->Format Data. Don’t Swipe to Factory Reset
I had the same (loop), disabled the encryption for /data but didn't wipe it
If you have exsdcard, remove then boot without sdcard. Eventually format internall sdcard.