Database Users

Running CM-4.0.4. Unable to drop into recovery console

Hi,
I have weird situation with my T-mob MyTouch3G. Did a lot of searching – couldn’t find anything similar. About 3 weeks ago I used Recovery Flasher to load CyanogenMod (4.0.1), later upgraded to 4.0.4. When booting into recovery I see that I am running "Build: CyanogenMod v1.4 + JF". Phone works fine (kudos to Cyanogen), but when i decided to partition my SD card i got into the following situation:
1. When I try to use "parted" from terminal emulator, I am getting "not found" (I do su before), when it is clear that CM recovery 1.4 contains Gparted.
2. When in recovery mode I select "Console(Alt-x)", I get "press enter" in horizontal layout and then white dots start moving on the screen from left to right, eventually (in about 2 min) occupying the whole screen.
3. When I tried to reflash CM recovery through fastboot I get "not allowed" - although this might be due to the fact that i am still running original "perfect" SPL. When trying to re-flash recovery though adb, no error message is shown and the process is done immediately.
So, my question is what is wrong here? How do I get fully functional CM recovery?
Any help is appreciated!

Sounds to me that you hit it on the head... go back through the root process and rid your self of that buggered SPL.

I will try to revert to the original state and then repeat the process, but is there any other ideas? B/s restrictive SPL does prevent re-flashing, but i dont see why CM-recovery rom which is already installed and able to flash roms is itself not fully installed/function.
Thanks!

[Q] VISIONARY & Clockworkmod Couple Questions

I'm pretty sure I have these items in the correct order to "Permaroot" my MT4G and begin using Clockworkmod to load ROMs (and or/also want to be able to back up my default ROM)
My current attempts:
Downloaded and installed: VISIONary, from android.modaco.com, sorry I can't post actual links (VISIONary+, most recent version) was no longer avalible in the market so I had to install it from the URL)
Downloaded and installed "Clockwordmod" from the Market.
Put the phone into USB-Debugging mod, and disabled fast boot.
VISIONary+ question: I setup TEMPROOT, and "Root on Boot", assuming I would than be able to boot into "Recovery mode" via "Clockworkmod"
The phone reboots, and I'm assuming that would boot into "Root" **Root on boot** (Yes I know the temp. should fail after a reboot, but I thought, I'll stay away from "Permaroot" for now). However, I don't get to any sort of recovery mode, instead I get a screen with a triangle and exclamation in red, and that's it, it just hangs there, I'm thinking that this is just USB-Debugging, and I'm not achieving recovery mode, so this must be the result of not booting into a root mode.
Going back to VISIONary+, I attempt to "Permaroot", the phone's homescreen goes blank and nothing happens. The phone eventually turns itself off but doesn't reboot, subsequently, I must restart it manually, again, I'm not sure if I've achieved anything?
Advice, suggestions? Would be very appreciated.
Questions that might explain what's wrong?
Even in USB-Debugging mode, should I be connected to a PC via USB-Cable during all of this?
Any thoughts on why the PERMAROOT fails, or the "Root on boot" fails to get me to "Recovery mode"?
Last thing, I get a complaint from "Clockworkmod" when loading, that my SD Card must be mounted (which I'm assuming it isn't due to USB-Debugging mode and/or being connected to the PC) So should I get a good charge and disconnect from the PC while attempting all this? Fixed, disconnected USB-Cable, and mounted SD card in settings, this stopped this error
Also, I'm interested in backing up my default ROM ASAP as a safety-net in-case I screw something up. Is this possible via recovery mode in "Clockworkmod"? Links to advice on doing this?
Thanks everyone! Great board!

you should follow this as it worked for me flawlessly
http://forum.xda-developers.com/showthread.php?p=9534017#post9534017

thanks! that post seems to answer a lot of the specifics I might have been missing! Guess I missed it in search! I'll report my results!

I followed it exactly but I still get the Red Exclamation Point. I have rooted my phone s-off and I have superuser and rom manager. I did the Flash Clockwork Recovery but when I reboot into recovery I get Red Exclamation Point then when I click vol up and power the next says " E:Can't open /cashe/recovery/command " What should I do??

[*]The phone reboots, and I'm assuming that would boot into "Root" **Root on boot** (Yes I know the temp. should fail after a reboot, but I thought, I'll stay away from "Permaroot" for now). However, I don't get to any sort of recovery mode, instead I get a screen with a triangle and exclamation in red, and that's it, it just hangs there, I'm thinking that this is just USB-Debugging, and I'm not achieving recovery mode, so this must be the result of not booting into a root mode.
Click to expand...
Click to collapse
You can NOT flash clockwork without S-OFF and the red triangle is recovery. It is stock recovery if you press volup+power you will see the menu

S is off I rooted my phone using the terminal Emulator and that worked fine

When I press upvol and power I see
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cashe partition
E:Can't open /cashe/recovery/command
This is what my screen shows when I try to go into recovery and again my phone is rooted s-off and I use superuser

Try flashing the recovery again... for some reason people have reported it not sticking... just go back and flash it like 2 or 3 times then reboot

I found out the problem it was so easy but I never would of thought of checking but my wife said maybe my Rom Manager is a bad copy (because I get all my apps from a not so honest site) so I deleted my RM and downloaded the freebie on the market and it worked on the first try.....Now I have Glacier Rom running and I feel like a new man

slhpss said:
Try flashing the recovery again... for some reason people have reported it not sticking... just go back and flash it like 2 or 3 times then reboot
Click to expand...
Click to collapse
+1 on that, When I first flashed it, I was still getting the red triangle, after a quick google search I re flashed it an extra 2 times and it worked flawlessly

TWRP in continue loop

Hi, I have a big problem.
I installed CM7 with TWRP and I rebooted my KF. CM7 was ok.
My second step was to install gapp, so in CM7 I rebooted the KF in recovery mode, but now I have a vicious circle.
In TWRP I press reboot in system mode or in "power off" mode, but in each cases the KF continue to entry in TWRP without I press the power button.
It's impossible to launch android system.
If I use the KF utility, this recognize KF, but if I launch some option, it's stopped to wait for device.
Please help me.
Thank you
(sorry for my english )

a small video.....
on youtube: /watch?v=hUnGTR2DQDY

you need to update divers. I installed the divers with kindle utility and they didn't work. Try searching the threads
Edit.. don't worry I've been here so many times with different things. It seems to be very hard to brick a kindle. Its stuck in boot loop and this has been covered so many times. Hope this helps. If you can't find the right thread let me know and I'll have a look for you.
Sent from my Galaxy Nexus using xda premium

airjump said:
Hi, I have a big problem.
I installed CM7 with TWRP and I rebooted my KF. CM7 was ok.
My second step was to install gapp, so in CM7 I rebooted the KF in recovery mode, but now I have a vicious circle.
In TWRP I press reboot in system mode or in "power off" mode, but in each cases the KF continue to entry in TWRP without I press the power button.
It's impossible to launch android system.
If I use the KF utility, this recognize KF, but if I launch some option, it's stopped to wait for device.
Please help me.
Thank you
(sorry for my english )
Click to expand...
Click to collapse
If you are running windows this is the easiest way to go about fixing any booting problems that you may be having
http://forum.xda-developers.com/showthread.php?t=1428428
If you are not using windows look in my guide and the fix is also in there to do it manually from a command prompt:
My guide http://forum.xda-developers.com/showthread.php?t=1417234
Remember to hit that thanks button if this helped you

Looping Boot (Advanced Hack Kit)

Hi all,
Ok, so after attempting to root my device with the "Advanced Hack Kit / Source: http://forum.xda-developers.com/showthread.php?t=1259821), I managed to do something wrong in the process.
While rooting, I managed to drop my phone so I restarted itself. It went directly to the HTC logo. Now when powering up the phone it gets stuck at the logo and won't go any further.
What I have tried:
- Recovery (VOL.DOWN+POWER): Nothing really happens here, except that it directs me to an red exclamation mark with a triangle around it.
- Android System Recovery(3e): Tried all the choices available, none of them worked. However, in the menu I see an error message saying: E:Can't open /cache/recovery/command. When trying "Apply sdcard;updatezip" it just get's the same error message + "E:signature verification failed. Installation aborted.
Other info:
- Phone: HTC Desire HD
- Rooting Tool: Advanced Hack Kit
- Radio: S-OFF (26.03.02.23M)
-
I'm really no expert, but it seems like I'm left without a ROM or ClockWork Recovery.
If anyone got some good tips on what I can do,please help me
Thanks in advance!

You have S-Off, it's good, that means, that AAHK have done the main part of job. You can continue it yourself. Put that in the root of sdcard, and reboot into bootloader (Volume Down + PWR). It will ask to update or not, agree with VOL Up. Then wait, it will install ClockWorkMod Recovery. When you have done, install any ROM you like.

Dj_Amal said:
You have S-Off, it's good, that means, that AAHK have done the main part of job. You can continue it yourself. Put that in the root of sdcard, and reboot into bootloader (Volume Down + PWR). It will ask to update or not, agree with VOL Up. Then wait, it will install ClockWorkMod Recovery. When you have done, install any ROM you like.
Click to expand...
Click to collapse
That worked just fine. Thank you so much for the quick response and for the help

[Q] Nexus 7 stuck at google screen

Ok, my Nexus 7 is stuck - not getting passed from Google boot screen.
Here is a bit of history..
I unlocked and installed Cyanogen 10.1 awhile back, and TWRP recovery. It's actually dual rom - I can't remember the name of the other ROM.
I haven't used it for a few months and today I charged the battery and used it. It was all good until I checked for update and found that there is Cyanogen 10.2.1. So I clicked download and install.
It downloaded, then rebooted. And when the system is up, I got the pop up saying Google Service is stopped unexpectedly. Some app icons I got on my home screen are still there, but there is no menu bar. There is no home button, no app drawer. So I rebooted, and the same google service error.
So I thought, maybe it's not compatible with 10.2. I rebooted into recovery mode and install 10.1 (the old rom zip file was still on the device) using TWRP. Only took a few seconds and then it says successful/done. To make sure, I also did wipe dalvik cache, then reboot.
Now the system only goes as far as Cyanogen loading screen. That's it. So I hold the power button for a few seconds, then when the device restart, pressed the volumn down button. Then I chose 'reboot recovery'.
It doesn't. It just hangs at Google screen. I tried a few times, the same. So trying to reboot into recovery hangs at google screen, and trying to reboot normally hangs at Cyanogen screen.
As a last attempt, I let the screen hangs on Cyanogen log, connected the device to my Mac, then tried "fastboot devices". Nothing.. empty.
But when I tried "adb devices", I get an entry something like this
Code:
List of devices attached
015d2bcxxxxxx unauthorized
Code:
./adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
What should I do to get my tablet working again? I dont mind losing all data - I just want it working again. Someone please advice me..