Related
First of all, I have checked around quite a bit on this forum as well as others to try and avoid having to ask a question that's already been answered. Here's my problem/ what happened. I was rooted (one-click with locked bootloader) and had tried out several roms for a couple of months now. A few days ago I reverted back to an old stock 2.2 backup. My phone received two ota updates and I'm pretty sure I lost root. I had just went on using the phone for about two days when I ran into a problem today. After shutting the phone off I have now become "stuck" at the initial "X" screen (not animated). I pulled the battery and tried again several times. I then tried to reboot into recovery from the bootloader/ 3 skateboards screen with no luck. Any time I hit recovery it simply takes me back to my stuck "X" screen. I have an entire backup of my SD card from earlier as well as at least 4 nandroid backups (one of which was the stock 2.2 before the latest ota). I am thinking I need to somehow put clockwork recovery back on my phone so I can restore to one of my backups. I do not know how to do this. Sorry for the lengthy post but I want to provide as much information as possible. Any help at all would be greatly appreciated.
Just like you restore to stock 2.2. You should have used recovery.img. use adb fastboot to put the stock or anom recovery. I am not am expert but I have had the same problem few times. Always use adb commands
Sent from my Nexus One using Tapatalk
Does my n1 have to be in usb debugging mode because it's acting like it's not connected or something. I get the message "error: device not found." I'm on the fastboot screen on my n1 and using terminal on a mac. I usually didn't leave debugging mode on
No it doesn't but you have to have the drivers installed as well as the SDK with dependencies.
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
fastbook oem unlock
install Amon RA recovery
flash new rom.
Caseyp789 said:
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
Click to expand...
Click to collapse
The exclamation mark is just the stock Android recovery - it was re-installed when you loaded the stock FRG33 ROM.
Performing OTA updates requires you to have the stock recovery installed. Simply reverting to a stock 2.2 nandroid isn't sufficient, so trying to install those OTAs (which should have failed without stock recovery) may have broken something there.
GldRush98 said:
fastbook oem unlock
install Amon RA recovery
flash new rom.
Click to expand...
Click to collapse
This is by far the easiest (and safest) way. Google/HTC provided us an easy and safe method for gaining full access to our phones.... Why so many people refuse to use it is beyond me. If you root it the proper way (with fastboot oem unlock), it will make recovery from any further issues a lot more simple.
From what I can tell, I am having the same symptoms as the topic creator. I believe the problems started during a failed flash of cyanogenmod 6, but I am not sure by what means the flashing took place.
I can't boot the phone normally, it hangs on the X splash screen and the same occurs when trying to enter recovery mode.
I have tried the passimg approach to fix this, it either doesn't recognize my zip or starts loading it and freezes on a loading bar.
Fastboot flashing recovery completes, but doesn't fix the issue.
I can fastboot flash every image partition except system or radio, both hang.
As danger rat and dude random both know, I have posted this problem on the nexus one forums but I thought I'd post here to have some more minds look at it.
I'm trying to unroot my NookColor, and I'm having quite a bit of trouble. I know I have to reflash the ROM to its original state, (by doing the eight failed boot attempts thing.) but it seems that in the process of doing that, ClockWorkMod gets in my way, and doesn't allow to Nook to do its thing (resetting on its own). I'm not sure of what I should do to resolve this issue.
I've tried with the SD card in, and out, and after scouring Google for hours, I relented and decided to post here.
Any help would be great.
Tom
Can you still boot to home screen? If so, you can try this:
http://forum.xda-developers.com/showpost.php?p=10543243&postcount=124
memorydead said:
I'm trying to unroot my NookColor, and I'm having quite a bit of trouble. I know I have to reflash the ROM to its original state, (by doing the eight failed boot attempts thing.) but it seems that in the process of doing that, ClockWorkMod gets in my way, and doesn't allow to Nook to do its thing (resetting on its own). I'm not sure of what I should do to resolve this issue.
I've tried with the SD card in, and out, and after scouring Google for hours, I relented and decided to post here.
Any help would be great.
Tom
Click to expand...
Click to collapse
By flashing the ClockWorkMod recovery it overwrites the stock recovery that would allow you to do the failed boot restore. You will get more answers and support if you read and post your question within the ClockWorkMod Recovery post, found HERE. There are a couple people in that post that are working on fixing this same problem as you. I have not read in detail, but I believe they are attempting to boot from the SD card with froyo, found HERE, to be able to attempt to flash back to stock.
I can confirm that booting from froyo allows you to mount internal boot partition (mmcblk0p1) and replace uRecRam to revert back to original recovery. Then proceed to system reset and then to factory reset. See clockwork recovery thread for further information.
Sam
Sent from my HTC Desire using XDA App
OK guys, Im not new to the android deal, or flashing, but im stuck here. I have a Sprint Hero, and I need to go back to stock. Problem is, the USB port is broken, and will only charge. So i cant enter ADB, and the phone wont boot past the HTC screen. Its rooted, and i still have root, and clockwork recovery. I cant seem to get any rom to flash though, it just hangs at the HTC screen, and I cant get the HBoot (version 1.47) to read anything. I tried renaming the extracted RUU from the sprint update to HERCIMG and it wont read it. So, anyone have any ideas???
Without usb or an s-off bootloader I think its impossible to go back to stock. Why do you need to?
can u get one of those USB SD card readers? (this way u can put ur SD card into ur computer USB port and transfer files onto it)
search around there is a HERCIMG from the ruu for HBOOT somewhere on here.
i looked real quick and found this, it may help.
moxlon69 said:
This isn't really the place for this, but these questions have already been covered, many many times..
Rooting instructions. I know this works on the latest official sprint, because I've done it successfully.
As far as not being able to RUU, some people have an issue running the RUU if they haven't ran HTC Sync. Try that and see if it works, and if not, follow this method.
HERCIMG-2.31.651.7.ZIP download it. it's the Sprint 2.31.651.7 executable but in signed zip format, for people who aren't running windows. Not sure who actually converted the executable to a signed zip, but props to you for helping those that can't run the regular RUU.
Rename the file to HERCIMG.zip and place it on the root of your SD card.
Power the phone off.
Press and hold your Volume Down button, and while still holding it press the power button to power your phone back up into HBoot mode.
HBoot should then automatically verify the zip file, and ask you if you would like
to flash it. Press your trackball to confirm the update (downgrade in this case),
or press your send button to cancel.
Once on 651.7 you would root as normal, but you should not have to RUU back to 651.7 just to root.
Click to expand...
Click to collapse
rodcpierce said:
OK guys, Im not new to the android deal, or flashing, but im stuck here. I have a Sprint Hero, and I need to go back to stock. Problem is, the USB port is broken, and will only charge. So i cant enter ADB, and the phone wont boot past the HTC screen. Its rooted, and i still have root, and clockwork recovery. I cant seem to get any rom to flash though, it just hangs at the HTC screen, and I cant get the HBoot (version 1.47) to read anything. I tried renaming the extracted RUU from the sprint update to HERCIMG and it wont read it. So, anyone have any ideas???
Click to expand...
Click to collapse
Just a thought, can you download the RUU onto the phone via dropbox or something similar?
Ok. I have an s off bootloader. I can't boot to any rom as it gets stuck at the htc screen. I have tried the above mentioned hercimg file (even though you cant open it, because it says the file is invalid, and I have downloaded it a number of times, so its not a download error) and hboot wont find it even after renaming. I can move files to the sd card via my computer. I have the adapter. I need to get back to something close to stock, so that i can activate the phone. I dont want to get the thread off topic though, just need help getting back there.
Check your computer's USB drivers. If you can charge it you should be able to use USB. Or use someone else's computer. Then running the ruu from HTC website will work just fine. This sounds more like the computers end then the phone. Ymmv.
®patience is a virtue©
If you are s off just flash a recovery from h boot. What bootloader version do you have?
Edit: also theres a link to an s off RUU in the links thread I started. Also, you never said why you wanted to unroot?
il, I dont even necessarilly need to unroot. But if people would please read the first post. It would help answer some of the questions.... I CAN FLASH ANY ROM, BUT NOTHING WILL BOOT PAST THE HTC SCREEN. It also says what bootloader version i have, its version 1.47. I have clockwork customer recovery version 2.5 I believe it is. HBOOT wont find any file, period. Including a recovery. And its not a computer issue, its with the USB. Trust me.
I used this when I RUU'd recently and it worked great. jasonmaloney put this up a while ago and this gem was in the middle of the thread. It broke root and I rerooted using Regaw's method this time.
H-boot should have no problem recognizing this.
Drunk, it wont read that either. It doesnt even recognize that there is a HERCIMG on the SD card. This phone is bunk. not even a week ago, it was booting AOSP rom fine, no issues. Then I went to turn it on the other day, and wont boot past the HTC screen. Not sure what the deal is with this POS. About ready to bounce it off the concrete here.
rodcpierce said:
il, I dont even necessarilly need to unroot. But if people would please read the first post. It would help answer some of the questions.... I CAN FLASH ANY ROM, BUT NOTHING WILL BOOT PAST THE HTC SCREEN. It also says what bootloader version i have, its version 1.47. I have clockwork customer recovery version 2.5 I believe it is. HBOOT wont find any file, period. Including a recovery. And its not a computer issue, its with the USB. Trust me.
Click to expand...
Click to collapse
Whoa, calm the F down. My phone isn't the broken one, it's yours. Anyway, I did read the OP, but it was real early, and I missed the 1.47. AFAIK hboot cannot fail IF you build the zip correctly. Pull out the SDcard and put this recovery zip on it, then flash from hboot. Do the device erase thing in fastboot before that. I just flashed it and it went fine. It's CWM 2.5.0.1. You will to rename it to "HERCIMG.zip". Also, were you using any other mods like FR or something? http://dl.dropbox.com/u/5669105/HERCIMG2501.zip
il, I have clockwork recovery 2.5. Ill try this though here in a minute and see what happens. This phone is just ticking me off something fierce.
Il, it wont find that either. I put the zip on the root of the SD, and renamed it to HERCIMG and HBOOT still doesnt recognize that there is a HERCIMG file on the SD
rodcpierce said:
Il, it wont find that either. I put the zip on the root of the SD, and renamed it to HERCIMG and HBOOT still doesnt recognize that there is a HERCIMG file on the SD
Click to expand...
Click to collapse
just to clarify, you named it HERCIMG.zip all caps and with .zip at the end? If so, maybe your card is bad or your reader in the phone is bad? Do you have another card you can try it on?
yes sir. HERCIMG.zip And its on the card, as when i boot into recovery, I can see the file there.
Man, if you can get into recovery you can fix it. Do a full wipe and flash a stable ROM, reboot, and then walk away from the phone for about 15 minutes.
Try the instructions at http://romrepo.info/wiki/index.php?title=Install_from_another_ROM
See, thats what I think too, but it wont do anything but boot to the HTC screen. I have tried quiet a few roms, and get the same thing. I just left for roughly 2 hours, came back and still stuck at the HTC boot screen. Im lost brother.
OK, just a quick update. Got it fixed with the help of laei1472. The recovery was botched, that was what was not letting me flash anything. Finally got it to boot one of AOSP's earlier roms (which was the last rom it had booted, before going haywire). Then we were trying to flash RA 1.7 through terminal, but it wouldnt find flash_image. Ended up finding a file to flash it as that version of AOSP was missing the flash_image file in /system/bin. Once we got that, then I was able to flash RA 1.7, and now can flash any rom I want too. What a pain in the butt experience. But happy the phone is back up and going. Thanks again laie1472.
good to hear. glad you got it fixed
I'm definitely kind of a noob to all of this stuff but I think I've really messed up at this point and could use some help as I've exhausted pretty much everything I can think of. I have a Sprint HTC One. I decided to root my phone yesterday, after rooting it and installing a kernal I wasn't liking the way things were going (Just some things on the phone weren't working right so I decided to wipe it and re-do it all hoping to get better results. Spending quite a while messing around with it, running on no sleep and multitasking I effectively formatted the phone removing OS and everything, so at that point was sitting at the boot menu obviously. So I downloaded the RUU pack from here hoping to just run that and going back to factory, doing that came to realize I had 1.31.651.2 which doesn't appear to have a working RUU at the moment. I really don't have much experience with any of this or much of an idea what I'm doing aside from following the Tutorials you guys have posted. So I thought maybe I would try to flash the 1.31.651.2 ROM posted here by "Indirect" using the fastboot in CMD. Doing that (With an unlocked bootlocker and custom recovery) am getting a problem with writing the Zip with this message- FAILED (Remote: Not Allowed), which after searching I can't find much about how to resolve that. So my next thought was to try to use the all in one toolkit to sideboot the same ROM and was just getting an error when doing that.
So at this point I'm really at a loss and would really like some help from you guys who seem to know a whole lot more than I do
I don't care whether it's rooted, bone stock or anything else I just want the phone to work again and can't figure out what to do and I'm sure I'm just doing something stupid but hoping you guys can shed some light on it for me!
Maxy1292 said:
I'm definitely kind of a noob to all of this stuff but I think I've really messed up at this point and could use some help as I've exhausted pretty much everything I can think of. I have a Sprint HTC One. I decided to root my phone yesterday, after rooting it and installing a kernal I wasn't liking the way things were going (Just some things on the phone weren't working right so I decided to wipe it and re-do it all hoping to get better results. Spending quite a while messing around with it, running on no sleep and multitasking I effectively formatted the phone removing OS and everything, so at that point was sitting at the boot menu obviously. So I downloaded the RUU pack from here hoping to just run that and going back to factory, doing that came to realize I had 1.31.651.2 which doesn't appear to have a working RUU at the moment. I really don't have much experience with any of this or much of an idea what I'm doing aside from following the Tutorials you guys have posted. So I thought maybe I would try to flash the 1.31.651.2 ROM posted here by "Indirect" using the fastboot in CMD. Doing that (With an unlocked bootlocker and custom recovery) am getting a problem with writing the Zip with this message- FAILED (Remote: Not Allowed), which after searching I can't find much about how to resolve that. So my next thought was to try to use the all in one toolkit to sideboot the same ROM and was just getting an error when doing that.
So at this point I'm really at a loss and would really like some help from you guys who seem to know a whole lot more than I do
I don't care whether it's rooted, bone stock or anything else I just want the phone to work again and can't figure out what to do and I'm sure I'm just doing something stupid but hoping you guys can shed some light on it for me!
Click to expand...
Click to collapse
go into recovery and sideload install a rom
flex360 said:
go into recovery and sideload install a rom
Click to expand...
Click to collapse
When I go into TWRP and try to ADB sideload I go through trying to do that and it fails immediately
E: Unable to moundt "/data"
/cache
/data
internal storage
/data/media during gui startup
/cache
E:TW Func: :copy_log -- Can't open destination lo
E: Unable to mount '/cache'
/data/media/twrp/,twrps when
/data
/data
I'm not sure if I'm doing something wrong with it or if this means something I don't know much about
Maxy1292 said:
I'm definitely kind of a noob to all of this stuff but I think I've really messed up at this point and could use some help as I've exhausted pretty much everything I can think of. I have a Sprint HTC One. I decided to root my phone yesterday, after rooting it and installing a kernal I wasn't liking the way things were going (Just some things on the phone weren't working right so I decided to wipe it and re-do it all hoping to get better results. Spending quite a while messing around with it, running on no sleep and multitasking I effectively formatted the phone removing OS and everything, so at that point was sitting at the boot menu obviously. So I downloaded the RUU pack from here hoping to just run that and going back to factory, doing that came to realize I had 1.31.651.2 which doesn't appear to have a working RUU at the moment. I really don't have much experience with any of this or much of an idea what I'm doing aside from following the Tutorials you guys have posted. So I thought maybe I would try to flash the 1.31.651.2 ROM posted here by "Indirect" using the fastboot in CMD. Doing that (With an unlocked bootlocker and custom recovery) am getting a problem with writing the Zip with this message- FAILED (Remote: Not Allowed), which after searching I can't find much about how to resolve that. So my next thought was to try to use the all in one toolkit to sideboot the same ROM and was just getting an error when doing that.
So at this point I'm really at a loss and would really like some help from you guys who seem to know a whole lot more than I do
I don't care whether it's rooted, bone stock or anything else I just want the phone to work again and can't figure out what to do and I'm sure I'm just doing something stupid but hoping you guys can shed some light on it for me!
Click to expand...
Click to collapse
If your unlocked and you have a custom recovery its not a big deal bro. Its alright you can calm down . So first go download any rom like a stock rom ok? once you have one like OMJ's or even indirects take the zip and rename it to lets say stock. Then if you have adb (should be in fastboot folder) add that zip to that folder. Next boot into your recovery either through bootloader or through fastboot command. If your stuck on splash screen just hold power and volume down button until led's start flashing and the phone turns off let go for a sec and hold the power and volume down buttons again until you get into bootloader. Once your in recovery plug your phone into your computer and in twrp or even cwm recovery you should have the option adb sideload. Tap it and start that. Once thats running open cmd (command prompt) and type adb sideload stock.zip seeing as you renamed the stock rom to exactly how I spelled it, no differently. Then it should show you that it is loading in the command prompt once it is done loading it should start flashing and then your good to go. Wow i typed a lot lol.
Edit: wow totally didnt see the two posts above. OK see if what i sent you works. may wanna try reflashing your recovery in fastboot usb mode with fastboot flash recovery twrp.img
HTC_M7 said:
If your unlocked and you have a custom recovery its not a big deal bro. Its alright you can calm down . So first go download any rom like a stock rom ok? once you have one like OMJ's or even indirects take the zip and rename it to lets say stock. Then if you have adb (should be in fastboot folder) add that zip to that folder. Next boot into your recovery either through bootloader or through fastboot command. If your stuck on splash screen just hold power and volume down button until led's start flashing and the phone turns off let go for a sec and hold the power and volume down buttons again until you get into bootloader. Once your in recovery plug your phone into your computer and in twrp or even cwm recovery you should have the option adb sideload. Tap it and start that. Once thats running open cmd (command prompt) and type adb sideload stock.zip seeing as you renamed the stock rom to exactly how I spelled it, no differently. Then it should show you that it is loading in the command prompt once it is done loading it should start flashing and then your good to go. Wow i typed a lot lol.
Edit: wow totally didnt see the two posts above. OK see if what i sent you works. may wanna try reflashing your recovery in fastboot usb mode with fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Thanks for the help, When I typed the command in to the CMD, I got
"Adb server is out of data. killing...
*Daemon started successfully*
error: closed
I've reflashed the recovery like you suggested and still am unable to get much to change, does it have anything to do with anytime I do anything it says it's unable to mount or is that normal?
Sorry if I'm asking stupid questions but this is only the second phone I've rooted and haven't ran into a problem like this before
Also has anyone heard anything about a 1.31.651.2 RUU?
May have found a work around, after formatting again and running through a bunch of reboots and attempts to mount the partitions and everything I think I finally got it mounted. Am flashing a ROM to the phone now so here's hoping!!! :fingers-crossed:
And I'm up and going phew. Thanks for all the help guys. If anyone runs into this problem definitely Format the device again, once you do that it should start to mount
Maxy1292 said:
And I'm up and going phew. Thanks for all the help guys. If anyone runs into this problem definitely Format the device again, once you do that it should start to mount
Click to expand...
Click to collapse
What do you mean format it? How? From where?
axtn95 said:
What do you mean format it? How? From where?
Click to expand...
Click to collapse
From TWRK, under the wipe menu, had to Format it again (Which is what originally caused the problem to begin with ironically). I had to Format it to get the data and whatnot to mount. Once I did that I was able to flash a ROM and was back up and going
Maxy1292 said:
From TWRK, under the wipe menu, had to Format it again (Which is what originally caused the problem to begin with ironically). I had to Format it to get the data and whatnot to mount. Once I did that I was able to flash a ROM and was back up and going
Click to expand...
Click to collapse
Thanks for the reply, so just making sure, you went into advanced wipe and checked cahce?
Edit: oops i saw format data lol
axtn95 said:
Thanks for the reply, so just making sure, you went into advanced wipe and checked cahce?
Click to expand...
Click to collapse
Not quite. When I loaded up TWRK and go into Wipe there's 3 buttons, the slide button for "Factory reset" there's the Advanced Reset button and the 3rd button says "Format". Format wipes literally everything except the custom recovery off the phone. Which is the mistake I made last night (Bonehead move but I was running on zero sleep lol)
I have messed my new Mot G 5inch 2nd generation phone up really bad
any help would be greatly appreciated.
I unlocked the bootloader then tried (unsuccessfully) to root. It just wouldn't take on any method I tried.
So I had the great idea to reinstall the firmware (in the hope that a clean install would help), following this guide here... http://techtrickz.com/how-to/how-to...irmware-on-2nd-gen-moto-g-2014/#comment-16531.
While I was going down the cmd list it failed on boot and recovery giving me the error 'hab check failed for boot’ (and the same for recovery.
I carried on down the list as I was stuck now and when I've rebooted the 'unlocked' page comes up but then all that happens is the screen flickers on/off with nothing else happening.
I got into recovery once (green man with triangle) and noticed that adb sideloading was there if that helps.
I'm in the uk.
any help would be massively appreciated.
i don't know anything about the phone in question as i have the first one. all i can say is have you tried going to @rootjunky;s site and ask him if maybe he can help you. i think he has already rooted and installed custom recovery. worth a shot. he is pretty good. any way good luck.
If you can boot into the bootloader, here is a guide that will help you out.
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Kindly correct the title. Exclamation mark doesn't clarify what you are trying to ask. Some users may just ignore your post if you Title your threads like this.
Cam you boot into bootloader? (power + volume down) if yes try flashing a recovery downloaded from here. If that works too, try downloading a rom, copying it to USB storage (by mounting via recovery) and flashing that