My DZ has been doing some weird things lately and I'm at a bit of a loss as to what could be causing them.
It's rooted, S-OFF, running MIUI with ClockworkMod 5.0.2.0 installed but the recovery image won't do anything at all any more.
I click on an option and it just goes to the top-hat, circular arrow 'thinking' screen and stays there. It's the same with everything I select; it won't reboot, power off, wipe..nothing.
The problems started with the previous version of ClockworkMod, but are still present with the update.
It worked fine before, I was able to flash ROM's and do all the other usual tinkering, but then it literally just stopped with no instigation.
I've tried wiping the recovery and manually installing a new one via FastBoot but it won't work in FastBoot any more either. I just get the FAILED (remote: not allowed) message for everything I try and do.
I'm baffled.
Any ideas?
TIA
Tone-Fu said:
My DZ has been doing some weird things lately and I'm at a bit of a loss as to what could be causing them.
It's rooted, S-OFF, running MIUI with ClockworkMod 5.0.2.0 installed but the recovery image won't do anything at all any more.
I click on an option and it just goes to the top-hat, circular arrow 'thinking' screen and stays there. It's the same with everything I select; it won't reboot, power off, wipe..nothing.
The problems started with the previous version of ClockworkMod, but are still present with the update.
It worked fine before, I was able to flash ROM's and do all the other usual tinkering, but then it literally just stopped with no instigation.
I've tried wiping the recovery and manually installing a new one via FastBoot but it won't work in FastBoot any more either. I just get the FAILED (remote: not allowed) message for everything I try and do.
I'm baffled.
Any ideas?
TIA
Click to expand...
Click to collapse
The new clockwork 5 has alot of issues. You should try to reflash clockwork mod 3 or 4
Sent from my HTC Vision using XDA Premium App
Thanks for the reply, mate.
The problem is that I can't reflash to any other recovery.
The issues started when I was using the previous version, which was 4.X or something, so I updated to the latest iteration hoping it would fix the problem, but it didn't.
Don't use the power button to select stuff in clockwork, that's like a sleep mode.
Use either trackpad or camera button.
-Nipqer
Nipqer said:
Don't use the power button to select stuff in clockwork, that's like a sleep mode.
Use either trackpad or camera button.
-Nipqer
Click to expand...
Click to collapse
This. I think he's using the power button or volume buttons to move and select, which is incorrect.
You have to use the trackpad to scroll and select items.
So why are you trying to flash the new recovery through fastboot? Just pull your battery and boot into MIUI normally, then go to ROM manager and flash CWM 3.0.2.4, it will work. If it doesn't flash properly, go into the settings and select "wipe recovery before flash".
Tone-Fu said:
Thanks for the reply, mate.
The problem is that I can't reflash to any other recovery.
The issues started when I was using the previous version, which was 4.X or something, so I updated to the latest iteration hoping it would fix the problem, but it didn't.
Click to expand...
Click to collapse
I have met the similar problems too.
and I solved it via reflashing the recovery using the ROM manager.
So you can reflash your clockworkmod recovery 5.0.2.0 by ROM Manager, I guess that will work.
Cheers for the replies Nipqer & martonikaj.
The trackpad thing might be the issue but I can't tell because my wife's gone out with the phone! I'm used to using the recovery on my GS2 and DS2, which doesn't have the trackpad etc. so I may well have been using the volume rocker and power key on muscle memory.
Though it is interesting that that method obviously worked in previous iterations of the recovery.
Oh and in answer to your question I was trying to use FastBoot because I perceived the problem to be due to the flash via ROM manager.
@Sunkins - Yeah, I think ROM manager was working just fine. The problem seems to be down to the man in the loop! Cheers for the advice, mate.
I would recommend recovery 3.0.2.4 as it is rock solid, and seems to be the most reliable.
Related
Hi:
Really need some assistance here.
I am currently trying to install CM 7.0 RC1. From my ROM manager I selected the CM MOD and it went to reboot and install. Now it is just stuck on a screen with a little green Android Logo and Exclamation.
What can I do here? I am afraid to pull the battery but it doesn't seem to be moving past this point.
Do you have a custom recovery like Amon_RA or ClockWorkMod installed?
cyrus_mc said:
Hi:
Really need some assistance here.
I am currently trying to install CM 7.0 RC1. From my ROM manager I selected the CM MOD and it went to reboot and install. Now it is just stuck on a screen with a little green Android Logo and Exclamation.
What can I do here? I am afraid to pull the battery but it doesn't seem to be moving past this point.
Click to expand...
Click to collapse
You'll be fine pulling the battery since you're only flashing a ROM... it's a NO NO when flashing Radio though. That being said... the CORRECT way to restart when you're in a bootloop or stuck on that particular screen is to use the three finger salute and reboot by holding down the power button, volume down button, and pressing the trackball. From there, I'd immediately hold down the volume down button, which will force the phone into the bootloader and you can enter Recovery from there. Do a FULL wipe of data and cache, as well as dalvik-cache from the Advanced menu, then flash the ROM.
uansari1 said:
You'll be fine pulling the battery since you're only flashing a ROM... it's a NO NO when flashing Radio though. That being said... the CORRECT way to restart when you're in a bootloop or stuck on that particular screen is to use the three finger salute and reboot by holding down the power button, volume down button, and pressing the trackball. From there, I'd immediately hold down the volume down button, which will force the phone into the bootloader and you can enter Recovery from there. Do a FULL wipe of data and cache, as well as dalvik-cache from the Advanced menu, then flash the ROM.
Click to expand...
Click to collapse
Yup this is what to do. Quick bit of info; You can get to the boot loader by simply holding the volume button down and pressing the power button, just a little easier to do
That's what I had to do. Mine also got stuck.
Sent from my Nexus One using XDA App
Hollow.Droid said:
Yup this is what to do. Quick bit of info; You can get to the boot loader by simply holding the volume button down and pressing the power button, just a little easier to do
Click to expand...
Click to collapse
Agreed. I was just referring to what to do if you're stuck on the X or in a boot loop. ;-)
Sent from my Nexus One using Tapatalk
You're stuck with stock recovery. Reboot back to ROM, install recovery, only then reboot to install ROM.
Hey guys I'm having a similar problem, however my phone gets stuck on the initial nexus screen. I've been working on the phone problem for the better half of the day and this is what i've done, what works, and what doesn't.
WHAT I'VE DONE:
Full wipe, including Devik
Played around with installing different radios.
Download CM7-RC1 from CWM and the computer
WHAT WORKS:
MIUI Roms
Stock Gingerbread Rom
MY Back-up, which has CM7 Nightlie #45
WHAT DOESN'T:
All Cyanogen Mods
I even tried the CM6.0
So I'm a little stump on how to get my phone to run the latest Cyanogen or matter of fact, any CM Roms. Maybe my phone wants something different in her life
Any help will be great guys...thx
How much time did you wait?
Did you try erasing /system?
Well I just waited for 5 hours leaving it on the initial Nexus screen, in hopes it might do something, but it was to no success.
/system? not quite sure where that is... I am assuming it's in the roots... I can only do what I can from the recovery.
Try to install LeoGingerbread, for example. Does it work?
If yes - right after it installs, try to flash CM7.
cyrus_mc said:
Hi:
Really need some assistance here.
I am currently trying to install CM 7.0 RC1. From my ROM manager I selected the CM MOD and it went to reboot and install. Now it is just stuck on a screen with a little green Android Logo and Exclamation.
What can I do here? I am afraid to pull the battery but it doesn't seem to be moving past this point.
Click to expand...
Click to collapse
Whenever you see "little green Android Logo and Exclamation", you can press volume up and power button together to get into the bootloader menu and reboot your N1. It seems like your custom recovery did not work. Try to flash Clockworkmod recovery 2.5.1.4 (not 3.0.0.5) or RA recovery again. It may help.
Jack_R1 said:
Try to install LeoGingerbread, for example. Does it work?
If yes - right after it installs, try to flash CM7.
Click to expand...
Click to collapse
Wow that actually worked, thanks... can you explain why this is needs to be done to get it to work?
LeoGingerbread executes "format /system", that actually works and cleans the remains of the old OSes. Some other ROMs do, too.
armyshawkeye said:
Wow that actually worked, thanks... can you explain why this is needs to be done to get it to work?
Click to expand...
Click to collapse
Because you still have the stock recovery installed, that is how you access the menu for it.
Here's a flashable script that does the same thing. It was put together by temasek - I'm just sharing...
http://db.tt/wdeoIMI
Sent from my Nexus One using XDA App
danger-rat said:
Here's a flashable script that does the same thing. It was put together by temasek - I'm just sharing...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
How I flash this? As a update.zip?
Yes. I believe it executes "FORMAT SYSTEM:" command, maybe more than once.
Yes, it formats system, boot, data, and cache, each twice...
It's quicker than flashing a full ROM to achieve the same results...
Sent from my Nexus One using XDA App
danger-rat said:
Yes, it formats system, boot, data, and cache, each twice...
It's quicker than flashing a full ROM to achieve the same results...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
CW Recovery has options to format system, and other partitions, under Mounts and Storage.
Sent from my Nexus One using Tapatalk
I wanted to update to CM7, once it rebooted into recovery mode it gives me an error. I got the official Sprint update and the same thing happens. Once it verifies the file, something happened and it says there was an error and does not update. I did a factory reset on the phone, got the official sprint update and the same thing happened. The error is always "signature verification failed" on both roms.
What can I do?
Thanks.
When flashing a rom, are you selecting 'install from SD" then find where you saved the zip, etc?
It sounds like you're trying it thru the update.zip option (don't do that). Also, when you reboot into recovery, you should be seeing orange type clockwork 3.0.0.6 (not blue or green).
Ask if you have any other questions.
Sent from my SPH-D700 using Tapatalk
Are you using cwm 3?
Thanks for the replies guys.
I am using clockword mod 3, with their option on updates.
I don't know how to do the "update from sd", haven't seen that. I'm not sure if I am seeing the orange you mention...I just go to restart in recovery mod from CM3.
capt_peo said:
Thanks for the replies guys.
I am using clockword mod 3, with their option on updates.
I don't know how to do the "update from sd", haven't seen that. I'm not sure if I am seeing the orange you mention...I just go to restart in recovery mod from CM3.
Click to expand...
Click to collapse
If you don't see orange text you're not on CWM3, you are either on CWM 2.5 or stock recovery and neither of those would be used for what you want to do.
Ya, check out the development section on getting the latest clockwork, if you don't have it already. And just in case, first, try powering off your phone, then hold camera button, volume down and power (after device is completely shut off). If you don't see orange text, you should update to the latest clockwork.
Sent from my SPH-D700 using Tapatalk
I turned off the phone, turned it on with the vol down/camera button and it automatically booted on CM recovery 3.0.0.5. Doing a rom backup. Then I see the orange text with several options but I can't pick any of them...I'm hitting the "home" button but nothing.
The phonr wont respond...I can toggle between the options but thats it.
I turned off the phone, turned it on with the vol down/camera button and it automatically booted on CM recovery 3.0.0.5. Doing a rom backup. Then I see the orange text with several options but I don't know where the hell CWM downloaded the file!!! I cant find it, or the official 2.2 one...
And now the phone is stuck in the SAMSUNG screen...
Bricked...tried factory reset and nothing. Tried restore through CWM and nothing...
If you are able to get into CWM or download mode then your phone is not bricked. It sounds like you will have to use ODIN to restore your phone back to stock.
capt_peo said:
Bricked...tried factory reset and nothing. Tried restore through CWM and nothing...
Click to expand...
Click to collapse
ClockworkMod 3 automatically converts your phone's filesystem from RFS to EXT4. You need a ROM that supports EXT4 or else it won't boot.
You wanted CM7 so go ahead and flash that if it's on the sd card. If you don't have it on the card it's easy to fix. Just turn off your phone and plug your memory card into a computer and copy a ROM that supports CWM3.
Once you flash a ROM your phone should boot normally.
Bro, when u boot into clockwork (orange) are u opening the slider and using the arrows and enter key. ? You shouldn't be using the home key.
Don't be so quick to "I'm bricked" .. cuz that's rarely the case. And annoying when ppl are trying to help.
Sent from my SPH-D700 using Tapatalk
K, thx for being patient. I did Odin and its again working.
Now the phone updated to 2.2.1
For future reference, can this Odin method be used o update to a non official rom (like CM7)?
Thanks for all the help.
I wouldn't rely odin for that, and as far as I know, no. For frame of reference, I've probably flashed epic roms over 100 times, and have only odin'd 5-- Used mostly to return to stock/update a modem. So, odining probably wasn't necessary for you. Do what arashed says a few posts up.
I'm using SRF 1.1.0/Twilight Zone and its amazing. Battery lasts a lot longer too.
Thanks again.
capt_peo said:
I'm using SRF 1.1.0/Twilight Zone and its amazing. Battery lasts a lot longer too.
Thanks again.
Click to expand...
Click to collapse
Thanks for your support!
Search function is down but I did go through a few pages of threads looking for what was going on and no luck but I apologize if this has been solved somewhere else.
First off I would rate my rooting know-how as beginner to intermediate. I've jailbroken/unlocked multiple iPhones awhile back and have rooted/flashed roms on a cliq, mts, my3g, and this mt4g before.
I recently returned my current mt4g back to stock rom and unrooted. I do not think I turned s back on but I should have double checked before.
I currently have root and flashed clockwork and am trying to flash CM7 (I had ran it before on this phone as well). I have an issue right now where I cannot get into clockwork recovery as it will just sit at the mytouch logo forever and if I try and volume up and power into recovery all I get is 3 vibrations and a flashing amber light.
I can boot into the stock (but rooted) rom.
Any ideas? I feel like my recovery is broken or something but this goes beyond what I know. Any help would be great and any information you need I'll be happy to provide.
myTouch 4G, rooted, s (probably) off, stock rom, clockwork says i'm on 3.0.2.4
After reading that, I'm not fully convinced you actually have root and S-OFF. If you're sure you do, download ROM Manager from the Market and use that to install a fresh copy of CWM recovery. Also make sure the "fast boot" option is turned off somewhere under Settings. At that point, there should be nothing preventing you from getting into recovery if you have perm root.
I've got ROM Manager and it has SU permissions and I have the latest recovery flashed but I am still stuck on mytouch logo or the 3 vibrations/amber light when I try to get to recovery. If I reboot there is still no problem getting SU in terminal emulator or ROM manager or anything.
Fast boot is off as well. Thanks for the help so far.
Any ideas?
I don't often boot into recovery manually since most custom ROMs have an enhanced reboot menu with a recovery option, but if memory serves, I believe the key press combination is actually Power + Volume Down, not up like you mentioned in your OP. Give that a try.
Man I am really crazy. Here I am a tmo rep and also a novice modder and I'm hitting power + volume up.
Worked like a charm.. Now just to figure out why clockwork is sitting at the mytouch screen when trying to install CM7.
Thanks for the fresh set of eyes!
breakaway87 said:
Worked like a charm.. Now just to figure out why clockwork is sitting at the mytouch screen when trying to install CM7.
Click to expand...
Click to collapse
After flashing CM7, the phone hangs at the myTouch screen when attempting the first boot?
From ROM Manager if I try to flash CM7 from there it goes to the mytouch screen and hangs before anything else happens.
breakaway87 said:
From ROM Manager if I try to flash CM7 from there it goes to the mytouch screen and hangs before anything else happens.
Click to expand...
Click to collapse
What if you select the "boot into recovery" option in ROM Manager? Does the phone reboot into CWM recovery? (you should see the main CWM menu in orange text)
Boot into recovery takes me to MT4G logo and hangs.
breakaway87 said:
Boot into recovery takes me to MT4G logo and hangs.
Click to expand...
Click to collapse
So you don't have a good installation of CWM. Open ROM Manager again and re-flash a fresh recovery. I think there's an option to wipe your existing recovery beforehand, so if you see that, select it. You need to get a working recovery image before you can do much else.
Deleted current recovery and I confirm my model again and it takes a total of 5 seconds. Trying to reboot into recovery again after and I still hang at MT4G.
I hate it when you know something you need to do but you've been working on it so long you can't come up with new ideas.
Thanks again for the help.
Sorry multipost since it didn't register on my computer the first time for some reason
Yeah sorry man, I've never heard of a situation where CWM stubbornly refuses to install. If you have the engineering bootloader, you could manually flash it that way, but that's my only other idea.
Alright well thanks for all the help man, I'll dig around and pick up tomorrow.
I ended up looking for the recovery myself on the SD card and deleted it and then it flashed no problem. Thanks again for the help
breakaway87 said:
I ended up looking for the recovery myself on the SD card and deleted it and then it flashed no problem. Thanks again for the help
Click to expand...
Click to collapse
Sure, glad you figured it out.
I used Cyanogen's downgrade and rooting process. Seems to work great. However,,,,
I've been searching the MT4G boards on booting into clockwork recovery. I'm still struggling with this. I've tried hboot (hold volume down + power), and that doesn't take me anywhere. I do get a couple of haptic bumps. I also tried volume up + return key + power key. It seems to occasionally get me to hboot, but I think I keep factory resetting, because I loose my google log-in and my root. Note, it does say S=Off on this screen, when I can get to it. The last time, I think I flashed the PD15IMG.zip file when I got into hboot, but honestly I'm not exactly sure. It reloaded several functions and took about 10 minutes, so I think it did.
I can re-root. Once I figure this out, I will go through the perma-root process, but I'm just getting started on my wife's old MyTouch 4G. I've rooted my G1, my Galaxy S2, my G2x, now I'm trying to root and try some customer ROMs for my wife's old and no longer used MT4G.
Can anyone help me out here? Maybe point me to some obvious threads or websites? Bottom line, I want to get into Recovery once I root my phone. I can't seem to get there, except through ROM Manager, which is not very dependable, particularly if I screw something up, or get into an infinite bootloop, like I did flashing AOKP ICS.
TU Homer said:
I used Cyanogen's downgrade and rooting process. Seems to work great. However,,,,
I've been searching the MT4G boards on booting into clockwork recovery. I'm still struggling with this. I've tried hboot (hold volume down + power), and that doesn't take me anywhere. I do get a couple of haptic bumps. I also tried volume up + return key + power key. It seems to occasionally get me to hboot, but I think I keep factory resetting, because I loose my google log-in and my root. Note, it does say S=Off on this screen, when I can get to it. The last time, I think I flashed the PD15IMG.zip file when I got into hboot, but honestly I'm not exactly sure. It reloaded several functions and took about 10 minutes, so I think it did.
I can re-root. Once I figure this out, I will go through the perma-root process, but I'm just getting started on my wife's old MyTouch 4G. I've rooted my G1, my Galaxy S2, my G2x, now I'm trying to root and try some customer ROMs for my wife's old and no longer used MT4G.
Can anyone help me out here? Maybe point me to some obvious threads or websites? Bottom line, I want to get into Recovery once I root my phone. I can't seem to get there, except through ROM Manager, which is not very dependable, particularly if I screw something up, or get into an infinite bootloop, like I did flashing AOKP ICS.
Click to expand...
Click to collapse
Settings>Power>Turn off fast boot.
Power off your phone.
Hold VOLUME DOWN BUTTON + POWER BUTTON.
Now select Recovery.
crazykas said:
Settings>Power>Turn off fast boot.
Power off your phone.
Hold VOLUME DOWN BUTTON + POWER BUTTON.
Now select Recovery.
Click to expand...
Click to collapse
How long? Until after the first bump?
I re-rooted. Can't seem to get there except through ROM Manager...
If you hold vol down and while booting, the phone should boot directly to bootloader. If it doesn't, there may be something wrong with one of the buttons. You have to have the button held down early, though.
You can also use terminal emulator:
su
reboot recovery
Or in adb:
adb reboot recovery
estallings15 said:
If you hold vol down and while booting, the phone should boot directly to bootloader. If it doesn't, there may be something wrong with one of the buttons. You have to have the button held down early, though.
You can also use terminal emulator:
su
reboot recovery
Or in adb:
adb reboot recovery
Click to expand...
Click to collapse
Much thanks for your help.
I cannot boot directly into recovery. It simply doesn't work. Occasionally, I can reset my phone and boot directly into hboot, though I'm not sure what the process actually is. I've only done it twice, and I was just dicking around and didn't track my button sequence. I'm trying to track this methodically, but I really think the process works intermittently, which masks the appropriate process.
I gain SU status in terminal, but I cannot reboot into recovery. I can get in via ADB, so that works.
Two processes into recovery: ROM Manager and ADB.
My issue is I've tried to flash an ICS ROM, in this case Ice Cold Sandwich AOKP 8.5 Final Edition. It gets caught in bootloop. Twice. Can't seem to load up properly.
Could my phone simply be dorked? Maybe I need to push a new recovery file?
Start with something easy like Cyanogenmod 7.2. Make sure you wipe cache, data, and system partitions.
Ok. I got everything working. I think your perception that my down button is non-functioning is the first culprit. Also, I'm not sure why I just boot-looped. I did this for both CM7.1 and for ICS. One other issue is I could not reboot into recovery from stock. I could, however, adb into recovery.
I first loaded CM7.1 plus GAPPs. This just bootlooped. I then got back into recovery via ADB and just flashed CM7.1. This worked. From here, I could use terminal to reboot into recovery. I could also use the CM reboot option right into recovery. At this stage, I flashed GAPPs and that was fine. I then upgraded to ICS and it is working great. My down button still doesn't work, so the only method of getting into recovery in an emergency is via ADB. I can, however, use the reboot option into Recovery from my working phone.
Strange. I might dig deeper to see if I can correct the lingering issues, but it seems to work well, and I finally figured out how to get around with this old phone that's been collecting dust for over a year. Not a bad daily driver. ICS seems very stable, compared with my G2X.
Again, thanks for your help.
Well, progress is always good. Congrats.
I'm not sure if you already did this or not but take the PD15IMG.zip out of the root directory on your SD card. After you remove/move it and get to hboot you should be able to go to recovery. From there you could recover a backup (which hopefully you made before trying to flash a new rom).
Sent from my Dark Unicorn Resurrected v4.1 using xda app-developers app
Good advice. I'll do that.
Sent from my HTC Glacier using xda app-developers app
I unlocked my Nexus 10 bootloader, then installed the latest CWM, and finally the latest SuperSU, and it's all fine. But it seems that the only way to get into recovery is to first go into the bootloader (hold power, vol up and vol down) then select recovery from there. And when I leave recovery to boot back into the OS (stock - i've not flashed any other roms yet) I get a warning about how stock is going to revert my recovery and lose root, and do I want to try and fix it, and how this cannot be reversed. I select fix it, but next time I try and get into recovery it's not there. Is this normal, or a known problem? Have I done something wrong? I don't want to fiddle around too much and brick my device; it works perfectly and the only reason I did all this was so I could install an app to prevent me from having to connect my N10 to my pc to used ADB over USB - I much prefer doing it all over Wifi!
poldie said:
I unlocked my Nexus 10 bootloader, then installed the latest CWM, and finally the latest SuperSU, and it's all fine. But it seems that the only way to get into recovery is to first go into the bootloader (hold power, vol up and vol down) then select recovery from there. And when I leave recovery to boot back into the OS (stock - i've not flashed any other roms yet) I get a warning about how stock is going to revert my recovery and lose root, and do I want to try and fix it, and how this cannot be reversed. I select fix it, but next time I try and get into recovery it's not there. Is this normal, or a known problem? Have I done something wrong? I don't want to fiddle around too much and brick my device; it works perfectly and the only reason I did all this was so I could install an app to prevent me from having to connect my N10 to my pc to used ADB over USB - I much prefer doing it all over Wifi!
Click to expand...
Click to collapse
Try Quick Boot in the Playstore.
sfobrien said:
Try Quick Boot in the Playstore.
Click to expand...
Click to collapse
I might try that but really I'm more concerned about my recovery going missing when I exit it.
Strange, never seen that and can't reproduce it. I suggest switch to TWRP and maybe custom ROM and see if that corrects the issue.
Is recovery returned to stock or just flat out missing? I haven't had a permanent recovery, stock or non-stock, on mine for some time now though it will still work loading temp recoveries.
mhausig said:
Is recovery returned to stock or just flat out missing? I haven't had a permanent recovery, stock or non-stock, on mine for some time now though it will still work loading temp recoveries.
Click to expand...
Click to collapse
I don't think anything actually happened - it just warned me that it might, and that I could either do nothing, or copy some files into system.
In the end I used TWRP which doesn't have the same problem.
This allowed me to return to my original problem, where I discovered that my game doesn't have a bug; instead, every single Nexus 10 has a problem with multitouch which Google doesn't even acknowledge, let alone fix.