[Q] Cannot access recovery - G Tablet Q&A, Help & Troubleshooting

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.

Related

Booting into CWM form TNTLite 4.4

I tried booting into CWMod by pushing V+ and power button but it goes and reboots in to TNTLite 4.4. how do I get into CWM so I can completely erase my current ROM and flash an other ROM?
[email protected] said:
I tried booting into CWMod by pushing V+ and power button but it goes and reboots in to TNTLite 4.4. how do I get into CWM so I can completely erase my current ROM and flash an other ROM?
Click to expand...
Click to collapse
It looks like you have the wrong version of CWmod.. Did you get the sd card one or the internal one.
look here for the right one.
http://forum.xda-developers.com/showthread.php?t=844088
http://forum.xda-developers.com/showthread.php?t=865245
Place the file internally on the Root and then do it again. It will flash and then reboot and hold the keys again and u should be good.
In the TNT Lite 4.x thread roebeet explains how to do it using the built in recovery pack
http://forum.xda-developers.com/showthread.php?t=842004
New for TNT Lite 4.3.0+ : GTAB 3588 Recovery Pack
This is a set of scripts to change between standard recovery and clockworkmod recovery, without having to reboot. All you need is adb or a Terminal Emulator package.
I don't use clockworkmod for flashing ROM's anymore, due to its inability to flash the bootloader (something that may be required, in the future). But I still use it for nandroid backups and data wipes, so this is how I can easily switch between the two.
a) To flash recovery to 3588 stock recovery, using your GTablet
- Download the app "Android Terminal Emulator", by Jack Palevich.
- Run the app, toggle the soft keyboard and change the font settings, if desired (default is very small)
- Type "su" (Superuser should allow su access.
- Type "fixrecovery.sh". This should run the flash_image tool and complete in 5-10 seconds
Reboot into recovery to test. 3588 stock has no options, so assuming you have no update.zip in the root of your /sdcard, it should just error out with an "!" error (that's what we want to see).
b) To flash recovery to legacy clockworkmod .8 bekit version recovery, using your GTablet
- Follow steps 1 to 3, above
- Type "cwmrecovery.sh". This should run the flash_image tool and complete in 5-10 seconds.
Reboot into recovery to test. You should see the clockworkmod .8 bekit screen, which means the flash was successful.
c) To flash either recovery with adb
Just use an "adb shell" and then run the shell script needed.
Click to expand...
Click to collapse

[Q] Can't Update CWM in HTC-G2 [Solved]

Hi everyone
I am having this weird issue with my T-Mobile G2... I am still on clockworkmod recovery 2.5.1.3 I don't know why and it is preventing me from doing everything! In the beginning I didn't notice I was on this version because in Rom Manager it appears to be in 3.0.? but when I reboot in CWM recovery I still have the green letters and the older version... The thing is that I am using right now CM7 and I am having problems with file formats, mounting system, etc. I have tried to S-Off my phone with a tut here with no luck.
About the root method, I don't even remember which one I used to root my phone because I was new when I did it and I just followed tuts around the web. Only thing I remember is that I used the first perma root method available by the time and it wasn't S-Off or carrier unlock.
The point is, I need to update to clockworkmod 3.0 or 5.0 in order to solve all the issues with my phone! I can't even do a nand at the moment because of this. What do you recommend?
Appreciate any help.
Solution in a post below.
If your having trouble getting ROM Manager to flash your recovery, this is how to do it manually through ADB.
1. Download this file here.
2. Rename the file to recovery.img
3. open a command prompt/terminal window and navigate to the location that you saved the file to. c:\path\to\recovery.img
4. type adb reboot bootloader
5. once booted into fast boot, back in the cmd prompt/terminal type fastboot flash recovery recovery.img
when its done reboot and then back in cmd prompt/terminal type fastboot reboot.
after reboot type adb reboot recovery and you should boot into clockwork. Make a nandroid and go find a custom rom.
I followed step by step but still showing version 2.5.1.3 and still having green letters.
Ok got it solved. Here is what I did:
The problem was that I had the wrong hboot installed which left my cellphone with S-ON and furthermore blocked me from doing anything. What you have to do if you have the same issue is to follow first this tutorial http://forum.xda-developers.com/showthread.php?t=1178912 to downgrade to stock rom, and then you have to re root the system following this tutorial http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
That's it! Good luck

[Q] Problem with Root

So, I have a HTC Desire with Android 2.2 on it. Some time ago I rooted it with the unrevoked program. Everything went fine, until the phone rebooted in recovery(after the root process). In ClockworkMod recovery, it gave me 5 errors like: Can't mount Cache. Then I realized that nothing in recovery works, not even the factory reset.
I wanted to flash a new recovery (AmonRa) with the terminal emulator ('cause the recovery flash function won't work), but it didn't recognize the command "flash". After some research I found out that I have to "put" the command file in xbin on my phone so that it could work. The "flash command" file has 3mb, but i have only 2mb system memory free.
Ok, so I ditched the recovery problem, and installed the "root" uninstaller so I can uninstall the default Flickr app on my phone. But, whenever i try to uninstall a system app, the phone reboots and the app doesn't uninstall. Same with the Titanium Backup "integrate update into ROM" function.
Sooo, first question: How do i fix my recovery so i can flash a new one? Can i flash one using Adb?
Second one: Does the rebooting of the phone when i try altering the rom has any to do with the recovery errors? If no, then:
Thrid one: How do i fix the rebooting?
1)You need to make sure that your fastboot and adb are configured correctly first of all, if adb/fastboot doesnt recognize "flash" then you probably are in the wrong directory in CMD prompt. Yes you can flash a recovery and even a rom with a properly set up adb
2) All I can recommend is try flashing a new recovery and start fresh. If the new rom continues to reboot then that is a whole-nother issue.
abaaaabbbb63 said:
So, I have a HTC Desire with Android 2.2 on it. Some time ago I rooted it with the unrevoked program. Everything went fine, until the phone rebooted in recovery(after the root process). In ClockworkMod recovery, it gave me 5 errors like: Can't mount Cache. Then I realized that nothing in recovery works, not even the factory reset.
I wanted to flash a new recovery (AmonRa) with the terminal emulator ('cause the recovery flash function won't work), but it didn't recognize the command "flash". After some research I found out that I have to "put" the command file in xbin on my phone so that it could work. The "flash command" file has 3mb, but i have only 2mb system memory free.
Ok, so I ditched the recovery problem, and installed the "root" uninstaller so I can uninstall the default Flickr app on my phone. But, whenever i try to uninstall a system app, the phone reboots and the app doesn't uninstall. Same with the Titanium Backup "integrate update into ROM" function.
Sooo, first question: How do i fix my recovery so i can flash a new one? Can i flash one using Adb?
Second one: Does the rebooting of the phone when i try altering the rom has any to do with the recovery errors? If no, then:
Thrid one: How do i fix the rebooting?
Click to expand...
Click to collapse
Sounds like your CWM needs to be updated. Simple way is to download Rom Manager from the Market. Open it and Flash the latest Recovery for your device. Yes as the person before me stated. If correctly setup you can Flash a Recovery, and even a Rom throught ADB. You can also remove unwanted apps, or push apps to the phone. HERE is a good guide about ADB. Also another good one is HERE.

[Q] Can't boot CWM Recovery consistently! Help please :)

I am unlocked and rooted. I checked with a root check app and it says i am...
Not sure if this has already been posted, but whenever i flash Romracer's cmw5 I can only boot into CWM Recovery under one condition. And that is:
Right after I type "fastboot reboot" and hold the volume down button right as it's rebooting. From here, when I select Android recovery, i can boot into CWM. Any other times, I.E. If i let the phone boot up to the point where I can make phone calls.and other stuff and power down afterwards and try to boot into CWM via Android recovery, the android with the exclamation pops up. At which point, I have to re-flash CWM every time.
Also, I finally found recovery-install.sh, however whenever i try to select it with astro file manager, it says "activity not found" or something like that and won't let me delete it. Does this have any effect on not being able to boot into CWM Recovery?
Thanks for the help, having to reflash CWM is annoying.
PS: I downloaded the file "Blue 5.0.2.7-atrix5 / ZIP version" from http://forum.xda-developers.com/showthread.php?t=1204500 and the file name saved as
"recovery-blue-atrix5.img". So when I type it into the command prompt, I would actually type the exact command of
"fastboot flash recovery recovery-blue-atrix5.img". I know the directions say that the command is "fastboot flash recovery recovery-atrix5.img" Is there any chance that my problem is resulting from this discrepancy in the file name?
Update: I found the CWM boot method inside CM7 itself and it works. Does this mean i'm scott free? Or should i continue to try and delete
"recovery-install.sh"?
If you have that file in /etc, it should be deleted. You don't need to use a file manager for that, a terminal or adb will do.

Can´t reach Recovery

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

Categories

Resources