Hello,
I have a Google Nexus One that doesn't start up, i tried booting into bootloader and it works fine. I hadn't rooted my phone, so i did, everything was working fine, then i couldn't boot into recovery, i would get an exclamation point with the green android.
I am trying to flash clockworkrecovery, or Recovery_RA, however everytime I try to use the fastboot command it gives me the following error: ERROR: Unable to create a plug-in (e00002c7) and I have to shut down the terminal.
I searched for the error but couldn't find anything, is there anyway to install a recovery image, my phone doesn't boot up so i can't access anything, it just blocks on the splash screen with the Unlock icon, and in the bootloader, it says Unlocked.
I don't know if it helps but i have the HBOOT-0.35.0017
When I Rooted and flashed superboot, the command was working fine.
Any help is appreciated.
Thanks.
I just restarted the whole process from different sources and flashed Oxygen!
Working great!
If a mod can please close the thread
Related
Hi Guys,
I have a rooted HTC Hero so am familiar with rooting Android etc.
I said I'd help a colleague out with a problem on her newly purchased Nexus One but I'm struggling. When you turn it on, it doesn't actually boot up - the static X (not the animated one) just sits there indefinitely. We've left it for ages and it doesn't do anything at all.
The only progress I have managed to make so far is to unlock the bootloader through "fastboot oem unlock". I've since tried copying some stock N1 ROMs onto the SD Card and tried getting them to install through the Bootloader/Hboot screen as passimg.zips. They're recognised and the blue progress bar runs but it always fails.
I also don't seem to be able to get adb access to the device. "adb devices" returns no results and "adb shell" obviously says "device not found".
I've also tried writing amon_ra's recovery to the device via fastboot and while it sends it fine, it fails to write (remote: image update error).
I'm assuming the last two points are because usb debugging isn't enabled (can't boot it to do so) and it isn't rooted.
Is there some way I can get a ROM flashed onto this that will boot to allow me to root it and then install the custom recovery and a ROM of my choice?
If it makes any difference, the model should be a UK Vodafone one. One of the passimg.zips I've tried has been PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_release_signed.zip, which I read is the one to downgrade Vodafone N1's to but it failed.
Any help at all will be gratefully received.
Thanks in advance.
Just a quick update about the passimg.zip failures...the error message is "main version is older"
Have also just tried a "fastboot boot recovery.img" (where recovery.img is a renamed amon_ra)...it downloaded fine and kicked off a reboot but it didn't actually boot into the recovery image at all...it remains at the static X screen (with unlocked padlock).
Have now tried a stock FRF91 as passimg.zip and this time it didn't error at the end. Instead it just returned to the menu after checking the passimg and didn't prompt me to apply etc...
Look here and download the PASSIMG.zip from the second post. put in root of sd .This will pass the "Older rom version" But it will downgrade you to EPE76.
If everything works out good. You would have EPE76 and a working N1. but you will need to download FRF85B. http://www.mediafire.com/?j5zejudgngm. rename that to update.zip. put into root of sd. boot into stock recovery. once you see triangle and android hold power and hit volume up. You will then see the recovery menu. Select apply update.zip. if its an success you will have FRF85B. Then just go to settings>system updates and search for FRF91 update.
Thanks for the reply. EPE76 is one of the ones I recently tried but even though it passes the check, it doesn't seem to apply. I don't get an option to apply and rebooting results in the static X again.
Earlier I managed to successfully apply amon_ra's recovery through fastboot. Apparently. The text in my command prompt said it was successful but attempting to boot into recovery from the bootloader menu presents me with the same static X.
I really don't understand what's going on with this thing.
I've now downloaded EPE76 in its original img component format from modaco and flashed boot, system, and userdata onto the three partitions separately using fastboot. System took three attempts but succeeded eventually.
Despite now having what should be EPE76 forced onto it, it still refuses to boot, giving me only the static X again.
I'm running out of ideas here. Does anyone have any suggestions at all?
Anybody? (bump)
I'm assuming she bought it used (because if it's new you would have took it back). From what I know, it sounds like a radio flash gone bad
I hope I'm wrong though.
About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Montor said:
About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Click to expand...
Click to collapse
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
csoulr666 said:
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
Click to expand...
Click to collapse
How can i unlock the bootloader again?
The only way i know is via the console and "fastboot oem unlock" - i cant get my phone to connect though.
The available devices the console gives me are an emulator and three times my phone, which is/are offline.
Edit:
Stupid me. "Fastboot oem devices" and it shows my phone in fastboot mode.
Next problem: "fastboot oem unlock" does not work, and flashing the recovery with "fastboot flash myrecovery.img" doesn't work either :/
Edit 2: Managed to unlock the bootloader again (mistook the android folder with de adb folder, no unlocktoken there of course)
Directly after unlocking the bootloader again, the device went into recovery mode, showed the recovery starting logo, and went black.
After turning it back on, it got stuck in the starting screen again - will have to wait for it to run out of battery.
Edit 3: Flashed the recovery, but i can't seem to find a stock rom (only one i did find is this here - and the files are down...)
Solved it!
Just did a factory reset in bootloader menu.
(I hope i didn't forget anything, since I don't know s*** about android development)
Phone is unloacked and S-OFF
So my phone was ONLY able to boot into recovery/bootloader.
I tried wiping my phone, but TWRP gave "Failed" message
I decided to simply continue and try flashing the ROM anyways
Phone rebooted and was stuck on the HTC logo
After a LONG time of waiting I decided to pull the battery out
Phone will not turn on, but my computer can detect it.
Also, I was unable to turn on USB-Debugging because, well no OS, and TWRP did not give an option to do so.
Edit: Update
Phone is now turning on and I am able to boot into bootloader
I am able to boot into TWRP (v2.8) now. Image of error below:
http://i.imgur.com/EGBpufh.jpg (embedding image only shows the large full size)
Unable to mount "System" partition
What are my options? I am using WinToolKit and it's not working. When I boot into fastmode (manually) my computer gives a message saying it cannot be recognized and that there may be a problem with the device.
Edit: solved my problem, thank you all for your help
So this morning i tried this. Kingroot didn't complete the root, some error happened, i didn't mind since i was just testing to see if i could root my phone for the first time [i've never done it before and it seemed simple enough].
I quit the app, a bunch of errors showed up, one after the other [i didn't register what exactly the windows said, i'm pretty sure it was a google application that stopped working]. The phone turned itself off.
i booted it up again, and it showed me the AP Fastboot Flash Mode screen. i know this from previously doing a factory reset, so i tried doing it again. After it wiped all of my data and custom, i tried rebooting it.
it showed me the motorola icon, but a few seconds later, i was back at the fastboot screen. i'm pretty desperate right now since this is my only phone. i tried selecting the "normal powerup" command, it didn't work. this is my screen right now:
"hab check failed for boot
failed to validate boot image
fastboot reason: fall-through from normal boot mode
USB conected
hab check failed for boot
failed to validate boot image
boot up failed"
none of the other commands, aside from Recovery, work. it takes me to the no command screen and all of the known options once i use the power+volume up command: reboot system now, reboot to bootloader, apply update from ABD, etc.
sorry if this thread reads weird, i'm sort of freaking out right now and english isn't my main language. thanks in advance to anyone who might help!
Check here
If you have questions PM me I will try to help. I got the same problem on Monday and solved it yesterday.
Hi all,
Any help I can get would be greatly appreciated. I have a Sprint HTC One M7 that was previously rooted. Currently it is relocked with S-On, but at some point an OTA update was downloaded and now my phone keeps restarting itself and boots to this "android is upgrading..." screen. It keeps doing this loop over and over. It restarts itself, and then goes to this "android is upgrading..." I've spent hours in the forum this afternoon and I've tried numerous things and nothing seems to be working. Everything I've tried keeps giving me errors. At this point I would simply like to go back to the stock ROM and have a working phone. Can anyone help?
FYI...
I've tried using the .exe method from an RUU, but that isn't working because when it reboots to bootloader at the very beginning of the process my phone boots to android and I get the "android is upgrading..." message.
I've tried extracting the rom.zip and sideloading it, but I can't sideload because installing the TWRP.img recovery fails every time.
I've tried a factory reset and that fails. Again, I get the "android is upgrading..." loop.
Basically, everything I've done to run RUU fails because my phone reboots to android instead of rebooting to the bootloader, and everything I've tried to work around that problem fails.
I'm currently running 6.23.651.7 and I'm trying to flash 6.23.651.10.
Again, any help would be massively appreciated. I'm desperate...
johnnycr said:
I've tried extracting the rom.zip and sideloading it, but I can't sideload because installing the TWRP.img recovery fails every time.
Click to expand...
Click to collapse
You can't flash a rom.zip extracted frin a ruu.exe using TWRP, it must be flashed using fastboot with the phone booted in RUU mode.
Basically, everything I've done to run RUU fails because my phone reboots to android instead of rebooting to the bootloader
Click to expand...
Click to collapse
Holding power and volume down doesn't work? This should get you in bootloader mode. If your phone can't boot to a stable bootloader there is nothing you can do. Once in bootloader there are many options to unbrick your phone.
alray said:
You can't flash a rom.zip extracted frin a ruu.exe using TWRP, it must be flashed using fastboot with the phone booted in RUU mode.
Holding power and volume down doesn't work? This should get you in bootloader mode. If your phone can't boot to a stable bootloader there is nothing you can do. Once in bootloader there are many options to unbrick your phone.
Click to expand...
Click to collapse
I first tried flashing the rom.zip using fastboot, but when the phone is supposed to display the HTC logo screen my phone just reboots and goes back to the "android is upgrading..." page.
I can get into bootloader when I hold power and volume down, but I haven't been able to successfully do anything from there. I tried flashing TWRP so that I could attempt to sideload a ROM, but I got an error when flashing TWRP.img.
johnnycr said:
I first tried flashing the rom.zip using fastboot, but when the phone is supposed to display the HTC logo screen my phone just reboots and goes back to the "android is upgrading..." page.
I can get into bootloader when I hold power and volume down, but I haven't been able to successfully do anything from there. I tried flashing TWRP so that I could attempt to sideload a ROM, but I got an error when flashing TWRP.img.
Click to expand...
Click to collapse
What is the error when flashing twrp?
fastboot oem rebootRUU doesnt work?
Is your bootloader still relocked? If it is, you can't flash custom recovery. The only thing you can do is run RUU in that state
alray said:
What is the error when flashing twrp?
fastboot oem rebootRUU doesnt work?
Click to expand...
Click to collapse
Well, I was just going to try and do this again, but now my PC can't even find it when I run "fastboot devices." I have the SDK and ADB driver installed, so I don't know why it can't find it all of a sudden.
I can't install the RUU by running the .exe, because when I do and it gets to the "waiting for bootloader..." screen my phone reboots and loads android and goes to the "android is upgrading" screen. So I need to flash the RUU via fastboot, but now my PC isn't recognizing my device in CMD...
Okay... so I finally got adb and fastboot working again. When I run "fastboot oem rebootRUU" the phone reboots to Android and goes to the "android is upgrading..." screen.
Update: So... I was able to successfully use adb and fastboot to unlock my HTC One again. I then tried to flash a custom recovery via fastboot, but I kept getting "FAILED (remote: signature verify fail)". I tried flashing TWRP, CWM, and stock HTC recovery and got the same failed message for each one. I'm just trying to find a way to break this stupid boot loop... HELP!
Update: So, my phone even restarts itself when I boot into safe mode... not good. Can anyone help me out?