Hi all,
I have a Google Nexus One which I had rooted a couple of months back (just root and no boot loader unlock). Everything was fine and I had factory restored it successfully once in the due course.
The problem was when I did a factory reset again yesterday so that I can sell it, there was a boot loop. I tired everything like restart, stock restore again from recovery, battery removal but all went vain. Fortunately I tried connecting via USB and thus I escaped from boot loop but still I was stuck there. None of the 4 system keys didn't work.
I just sat researching on Google and at last got the reason for the strange behaviour on the otherwise 2 year old not a single glitch ever phone. The issue was the with the stock Launcher apk. Just then I remembered that I had uninstalled the stock Launcher given the root access and so confident on the Holo launcher.
Again some researches and I came to know I can install (or "push") the launcher using the 'adb' command. I booted into recovery console, connected my phone to Windows 7 PC and installed the driver to get the phone detected. But when I typed 'adb remount' it gives 'error: device not found'. This is where I'm stuck now and since Googling didn't provide anything worth I'm back to my favourite tech forum.
Hope you got it clear here and someone can help me.
Regards,
ursJAR
Sent from my Galaxy Nexus using xda app-developers app
PS: And why is typing on the xda android app so terribly slow??!
Stock recovery doesn't allow ADB access.
Since you did factory reset - ADB isn't running on the phone either.
So you can't recover from this situation without unlocking the bootloader. Unlock it, install custom recovery, adb push the launcher through it.
Forgot to mention - I'm not suggesting PASSIMG, since your phone is likely updated to the latest, and all the PASSIMG are from older builds. You could try, though - if you don't want to unlock the bootloader, Korean PASSIMG might be what you need. See N1 Wiki, section "Unroot/restore", PASSIMG method.
If the boot loader is unlocked, I believe there is no way to revert to the fresh situation.. right?
Sent from my Galaxy Nexus using xda app-developers app
Related
I have been trying since yesterday to get my Nexus back in to working function. I had CM 6.0 with ClockWork recovery. Through recovery I wiped data/cache/etc then attempted to flash a stock frf91.zip from the sd card. As it was in the process of doing so recovery gave me an error and said it would reboot into Rom Manager. Now my phone hangs on Nexus X logo before the boot animation. I can power the device into fastboot to choose bootloader-reboot-reboot bootload-power off.
I believe that recovery process had the error/issue right after it deleted the system image.
YET I do not have the function of my Power/Multi-Use Button on the top of the phone. So I tried to use adb (which I have used with my phone previously without any issues) to attempt to install the stock rom image.
With adb running I sent the command to display the devices connected. It shows the list but with nothing connected (NOT an error or no devices connected), just blank. I then tried fastboot and sent the command to list connected devices, fastboot showed my devices serial as a connected device.
I was able to flash a system.img file using fastboot yet nothing happened, an all other restore attempts, like userdata.img or boot.img, etc. will not work and come back with a error of no remote permission.
Sorry for the entire book, but I am sort of lost.
My reason for this whole mess is because I wanted to restore my phone to a stock rom and recovery to send it in to have the power button fixed while retaining my warranty (my bootloaded IS locked).
When I get home from college today I am going try loading a stock factory passimg.zip of ERD79 on my sd and let fastboot try to pick up on it. I really have no other option haha.
Anyone have a suggestion? Honestly I am willing to just send it in AS-IS or brick it an tell them I had no idea what happened that I couldn't use the power button and it died after an update.
I see that no one has any idea really haha.
Couldn't tell from reading your write up - can you boot into recovery?
Sent from my Nexus One using XDA App
no I cannot. I do not have use of my power button. I am going to read through the new thread concerning accessing recovery without use of the power button.
To use adb, you need to be in recovery, or fully booted with debugging enabled.
To use fastboot, you need to unlock your boot loader.
Try reverting to stock via passimg method (one of the newer ones, if you have the Froyo radio).
Sent from my Nexus One using XDA App
I recently realized that was the issue with adb. So fastboot is out of the question then. Doesn't the passimg method require use of the power button though?
Unroot/Restore (use passimg method):
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my Nexus One using XDA App
hboot scrolls quickly when I try this and I catch that it says that is not a valid passimg.img
any ideas?
Should be passimg.zip (not img).
Makes sure it's not a zip inside a zip.
FRG83 seems problematic, so try FRG33 instead.
Sent from my Nexus One using XDA App
Just discovered this gem:
http://forum.xda-developers.com/showthread.php?t=825909
Sent from my Nexus One using XDA App
I got the passimg method working correctly. I mean passimg.zip in the previous post. I tried frf91 and it went through then said checking and went straight back to hboot without asking for permission. I'm going to try frg33 and if that doesn't work I will try the app you found.
frg33 seems to be working
hboot with FRG33 worked and the phone booted up with rom. thank you very much for all of your awesome help danger-rat.
No worries...
Sent from my Nexus One using XDA App
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 beckon ye geniuses of the XDA Forums with a yet to be slain beast of burdon.
I had Cyanogenmod mod beta 7 working on my N1 and noticed the gmail app was missing from the market and the phone after a flash. I then installed the official gapps which booted up once just fine. After that it bootlooped and I haven’t been able to reflash since.
I have clockwork installed but I can’t exit the bootloader to enter the recovery without my power button. It’s toast.
I can load up fastboot but my bootloader is still locked due to the power button being needed to root on the phone.
I’m limping by on a friends unlocked att blackjack ii until I get this working.
I have also sent it in to HTC to have the power button replaced but I have blown the liquid damage indicator early on in my N1’s life, thus I’m out $30 and have a microfiber cloth from HTC as a thank you.
I’m not sure what to do with my beautiful brick now.
The yodeler
Nevermind. Sorry I've never sent anything into HTC to be fixed. Have you tried letting the phone boot the point it loops and then issuing the command adb reboot recovery? That way you could flash from recovery?
ricosuaveishere said:
I beckon ye geniuses of the XDA Forums with a yet to be slain beast of burdon.
I had Cyanogenmod mod beta 7 working on my N1 and noticed the gmail app was missing from the market and the phone after a flash. I then installed the official gapps which booted up once just fine. After that it bootlooped and I haven’t been able to reflash since.
I have clockwork installed but I can’t exit the bootloader to enter the recovery without my power button. It’s toast.
I can load up fastboot but my bootloader is still locked due to the power button being needed to root on the phone.
I’m limping by on a friends unlocked att blackjack ii until I get this working.
I have also sent it in to HTC to have the power button replaced but I have blown the liquid damage indicator early on in my N1’s life, thus I’m out $30 and have a microfiber cloth from HTC as a thank you.
I’m not sure what to do with my beautiful brick now.
The yodeler
Click to expand...
Click to collapse
I know that certain fastboot (Bootloader) commands require root so I'm not sure that using a one time boot of a recovery image would work. Therefore your best choice would be to flash via the PASSIMG.zip method (There are good guides and information in this forum and wiki). This will restore your phone to stock where you can then reboot to recovery or use superboot etc to root.
Madj42 is also correct, adb commands can work if you repeatedly spam the commands at startup (Up arrow + then enter repeatedly while in the cmd window).
Passimg will work.
Adb requires the daemon to be running, which it won't be if you only have the bootloader running...
If your bootloader is unlocked, you can use fastboot...
Beware of dragons! xD
Sent from my Nexus One using XDA Premium App
Long story short: Phone won't boot past "Unlocked Bootloader" warning; Recoveries won't stick; Unknown Error & Freezing when trying to Flash System.img
I own an ATT Locked Moto X, but went ahead and unlocked it by purchasing the oem code. No issues there.
I decided to go ahead and try rooting it too, and was able to flash TWRP as my recovery. Still, everything seemed to be looking good, until I tried hard rebooting (to see if root would last). Upon rebooting, I could not get past the warning sign, notifying me that the bootloader was unlocked. I waited, and waited, and restarted again, but all progress stopped there. I would be the first to admit that whatever happened was probably my fault; perhaps I flashed some files in the wrong order, or entered a wrong command into fastboot. I don't know, and frankly don't care. My only question is how to get out of this mess and back to rooting, or at the very least, back to stock ROM now that I'm unlocked.
Booting into recovery only leads to the red triangle over an open android mascot, with the "Android Recovery" title. So clearly TWRP didn't stick; I tried reflashing, but nothing lasts past reboot. Then I tried flashing Philz Touch instead, which, upon exit, notified me that root was not enabled. So I rooted, rebooted, and was finally able to see Philz Tough again, even though I still can't boot normally. That time, both Philz Touch as well as root seemed to have stuck.
With that minor victory I downloaded the latest firmware for my model and tried to flash the components over, thinking I had somehow corrupted the existing OS files, but here's where it gets particularly frustrating. I am able to flash every file except for system.img, even though I am using moto-fastboot, which I understand is a common mistake. I get no specific error code, simply "Unknown Error," upon which the phone is frozen in fastboot. The phone remains unresponsive until I hard reboot [back into fastboot], and see that, once again, Recovery is back to stock. So now I'm baffled. I can't seem to find a way to flash the system file, factory resetting doesn't work, and my recoveries are constantly reverted back to stock. Does anyone have any advice, or suggestions for what I could try next?
You try RSD lite?
Sent from my XT1058 using xda app-developers app
southern87 said:
You try RSD lite?
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
I was already downloading it just as I saw your post, as my last-ditch effort. It also failed, but it gave me "Unknown USB Error," which is all I needed, it seems. I tried a different USB slot on another side of the computer, and lo-and-behold, the flash finished.
I'm not sure what saddens me more, the fact that I pushed off making this post for hours, only to have the solution less than an hour after I do, or the fact that I never thought to try a different USB port... In any case, sorry for the uselessness of this post. I think I'll save rooting for another day though...
I have had my Droid turbo since launch and as such followed the path the getting root on it for some time. I used Mofo to get root back on android 4.4.4, used it again to upgrade to 5.1 while keeping root, used sunshine to unlock the bootloader when that came out, and finally installed TWRP recovery on it. I had not done much to it since, but had Intended to install cyanogenmod for a while.
Well I thought I would finally get to it this weekend. I made a nandroid back-up with TWRP, copied it to my computer, backed up some files I didn't want to lose, and went ahead and installed the latest version of cyanogenmod 13 for quark (Moto MAXX and Droid Turbo) and the necessary gapps. It all went very well. I booted into cyanogenmod just fine, and signed in to google.
I was in the process of setting things up, like preferences/wallpapers/wigets etc, while google downloaded my apps. Not long after I started doing this, nova launcher would repeatedly crash, as well as cyanogenmod's built in launcher. I got fed up with it and rebooted. But the phone shut down and started acting odd. It would show what looked like the bootloader, but the open android guy was not there, and I had no options at the top. Sometimes it would just say AP Fastboot Flash Mode (Secure) with no other text.
I got it to go to the bootloader after holding down the power and volume down button, and got it to boot to TWRP. But TWRP said there is no OS installed, and it refused to install anything, wipe anything, and TWRP itself crashed after a bit when I left it there to try and use ADB to push my nandroid back up to it.
Now TWRP will not load from the bootloader, and I cannot flash anything. I wanted to just re-flash the stock firmware. So I downloaded fresh copies of it from the root thread here on XDA, but no matter what, i get the error "(bootloader) Failed to erase partition" It does this for anything. I tried flashing TWRP and the fresh system image. I tried following the steps on the root thread that flash things that you need to prepare the phone for the system image, but all attempts to flash fail with the same message.
I also tried using mofo to flash a clean system image. But it just stops and quits at 7%. I have had this problem before, and got around it by using mofo 0.0.2. But I no longer have that version.
I am at a loss here. I need my phone back ASAP. Any help would be much appreciated.
Have you tried doing everything from Terminal on your computer instead? That's what saved my butt once when I was in a similar situation.
Sent from my DROID Turbo using Tapatalk
arizonaomnia said:
Have you tried doing everything from Terminal on your computer instead? That's what saved my butt once when I was in a similar situation.
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
That's all I've been doing