Related
Hello all,
I think I may have bricked my nexus one. It is completely my fault for attempting things that I knew little about, so flame away But after the flaming, if anyone is willing to help I would be sooooo thankfull...
I successfully rooted my phone following the instructions on this page: (all links edited with a double asterisk as I don't believe I can post links)
h**p://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
Then successfully installed cyanogenmod (which is awesome!) following this page:
h**p://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
All was well, I even got the modaco desire rom up and running, and was happily switching back and forth using the recovery screen. I had nand backups for specific setups, etc.
Then I decided it would be good to know how to go back to stock, and found this page:
h**p://**w.androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
I followed the instructions to the letter (I think) except for erasing userdata (it said "failed: remote not allowed"). I thought that things would be ok, since I'd recently wiped, so I followed the page till the end.
The phone rebooted, and I got the original nexus boot animation - but it's in an endless loop! What's worse, it that now when I try to go to the bootloader or recovery mode, I get the exclamation triangle with the little android.
Is there any way through a command prompt (or other method) that I can fix this? I tried to re-flash the RA recovery image through the command prompt, but the response was, "waiting for device."
ANYTHING that anyone can suggest to help, I would be so thankful! I've been loving the nexus, and hate to think that I crippled it
Thanks in advance,
Randy
I doubt its bricked.
Noticed you didnt mention that fast boot doesnt work? (power button+trackball) try it.
Once you get to fastboot you can flash any ROM back. (fastboot flash **** commands from a command shell)
Did you ever perform a Nand Backup from Recovery?
It's not bricked, the only way to brick is to interrupt power when flashing a Radio image
Connect phone to PC. Open command prompt.
adb reboot recovery
Wipe, reflash.
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
nexus5894 said:
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
Click to expand...
Click to collapse
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Paul22000 said:
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Click to expand...
Click to collapse
............................
It worked!!!!!
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Randy Malkoski said:
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Click to expand...
Click to collapse
Glad to hear it. You learn the most by trial and error.
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
revonomics said:
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
Click to expand...
Click to collapse
Tell me what i need to download again and how to go about it...i really need my phone working again ((((
So, I got my new replacement EVO after loosing my first one.
So, first thing I wanted to do was get it rooted.
This time I wanted to try the unrevoked method. I did the other method before and had some issues, but it worked out in the end.
So, I got all the files I needed. And started my process.
I ran the reflash_package.exe and at the end it said this was a triumph...
So, I went and tried to go to recovery mode so I can run the unrevoked_forever.zip. However, I just got a fail. Didn't work.
So, I said, whatever, same issue I had before, let me just do the old fashioned manual way. Got all my files and went and did everything.
http://forum.xda-developers.com/showthread.php?t=765496
Followed that method, which worked for me before.. everything was going well, until the PC36IMG.zip update. First
Hboot 2.02
S- is still on S-On
Bootloaded - Bypassed
Radio_v2 - Failed PU
Everything else OK
I also get 5 vibrates when it tries to update the Radio.
When I try to boot to recovery, I get the red triangle...
When I try to boot normally, I am stuck on the white HTC EVO 4G screen.
Cant do adb shell or anything.
I have already tried to take the card out, put it in a reader, reformat it, replace the PC36IMG.zip, same.
Now the phone is stuck and unusable. What do to? I am unfortunately, out of town for the moment. Stuck in Chicago with no phone.
Anyone please have any ideas how to get out of this loop?
Okay, so more digging and I finally was able to get myself out of the hole I dugmyself into.
http://forum.xda-developers.com/showthread.php?t=829045
Saved my butt. Just rebooted into recovery and let it stand at the red triangle and continued from step 10.
So, S-Off now.. and flashing to Calkulin's as I type...
I rooted my Nexus 7 with Nexus Root Toolkit without any problems but I've just bought a Nexus 4 and can't seem to root it.
I let it update to Android 4.2.2 then ran NRT (v1.6.3) on my PC. After a few goes the drivers installed and it passed the final driver test so I assume all is well there. I then unlocked it without any trouble but I ran into problems when I came to root it.
It seemed to be going smoothly until it reached "Booting TWRP temporarily" but nothing happened, it just sat in the bootloader screen and didn't move on, although the message changed to "Rooting" and then "Waiting for your device to finish booting back up". In the end I pressed the power button which rebooted the 'phone and appeared to finish the procedure but it hadn't rooted or installed SuperSU or BusyBox.
I tried flashing it back to stock and re-rooting it but it was the same, I even re-locked it and went through the procedure again but it was the same.
Can anyone help please?
:sly:
Sent from my Nexus 4 using Tapatalk 2
SimonP2 said:
I rooted my Nexus 7 with Nexus Root Toolkit without any problems but I've just bought a Nexus 4 and can't seem to root it.
I let it update to Android 4.2.2 then ran NRT (v1.6.3) on my PC. After a few goes the drivers installed and it passed the final driver test so I assume all is well there. I then unlocked it without any trouble but I ran into problems when I came to root it.
It seemed to be going smoothly until it reached "Booting TWRP temporarily" but nothing happened, it just sat in the bootloader screen and didn't move on, although the message changed to "Rooting" and then "Waiting for your device to finish booting back up". In the end I pressed the power button which rebooted the 'phone and appeared to finish the procedure but it hadn't rooted or installed SuperSU or BusyBox.
I tried flashing it back to stock and re-rooting it but it was the same, I even re-locked it and went through the procedure again but it was the same.
Can anyone help please?
Click to expand...
Click to collapse
Yes, uninstall and forget about root kits and look and (most importantly) learn from here http://forum.xda-developers.com/showthread.php?t=2010312.
This is also a good source to read: http://forum.xda-developers.com/showthread.php?t=1469909
Thanks for the suggestions, guys. I still don't know why Nexus Root Toolkit didn't do the job when it worked so well and easily on my Nexus 7 but in the end I used the hippowise.com rooting instructions (using Google Nexus 4 Toolkit) and it worked a treat so I'm a happy bunny again
http://hippowise.com/how-to-unlock-root-and-install-a-custom-recovery-on-a-nexus-4/
I know it's more sensible to do it manually so that I know what has happened but in this case I just wanted the job done as quickly and easily as possible. I'll look into exactly what happened when time permits.
Cheers,
Simon.
^^ Learning opportunity lost.
Ditto, I've heard nothing good about toolkits and never used them, and consequently have never had the weird problrms I hear associated with them. Set up fast boot, setting it up can be a pain sometimes but its a one time thing. Using it is too easy and it never fails.
I do get what you guys mean and I will be interested to look into the procedures to see what's going on and how it unlocks and roots when time permits but, aside from being short of time at the moment, these toolkits are just automating the list of commands that you would issue manually so as long as someone has seen it working on the device and OS that you want, they should be fine so I'm happy to use them and learn more if/when I need to resolve problems. I am techie by nature but I'm not familiar with *nix and the inner workings of Android so it's a lot to study for something that only needs doing occasionally.
Anyway, thanks again for pointing me in the right direction and encouraging me to not be so lazy
SimonP2 said:
I do get what you guys mean and I will be interested to look into the procedures to see what's going on and how it unlocks and roots when time permits but, aside from being short of time at the moment, these toolkits are just automating the list of commands that you would issue manually so as long as someone has seen it working on the device and OS that you want, they should be fine so I'm happy to use them and learn more if/when I need to resolve problems. I am techie by nature but I'm not familiar with *nix and the inner workings of Android so it's a lot to study for something that only needs doing occasionally.
Anyway, thanks again for pointing me in the right direction and encouraging me to not be so lazy
Click to expand...
Click to collapse
To be honest, the learning curve with manual rooting is very straightforward. Heck, I found it quicker to unlock and root manually than through toolkits. You are literally just inputting a few lines into command prompt.
Sent from my Nexus 4 using Tapatalk 2
I can confirm that I have the same problem. Stuck at "Booting TWRP Temporarily" logo, doesn't move... Nexus 7 2012 Grouper 16GB.
Hey Guys,
Hoping someone can help here, I have followed various tutorials I have found on the internet to try and restore my Nexus 7 back to its factory state after it one day decided to never get past the white Google logo.
Inevitably I ended up on this tutorial as the only one where I seemed to get any kind of a link and response with the tablet: blog.laptopmagDOTCOM/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
basically it got as far as trying to Unlock the Bootloader, but it fails to do so. I do get the popup on the tablet asking if I want to unlock it but nothing happens, it remains locked after I click Yes. My command line saying that it Failed.
All other tutorials seem to assume you can access the OS and enable debug mode but of course I cannot. I cannot even do a Factory Reset, every options eventually leading me to a white Google logo.
I also cannot get into recovery mode, im just stuck on the screen with the green android and the option to Start, Recovery mode etc all just lead to the Google logo.
The impression I have gotten from not being able to unlock the bootloader is that there must be a hardware failure? could anyone suggest some black magic I might be able to do to fix it? I realise at some point I should cut my losses. I had also wondered if it was worth buying a new motherboard/logic board?
Would appreciate any help.
Cheers,
Matt.
Have you tried this tools:
http://forum.xda-developers.com/showthread.php?t=1766475
or
http://forum.xda-developers.com/showthread.php?t=1809195
Both are magic tools for nexus 7, please read any explanation carefully!
It may help you :good:
ju1da said:
Have you tried this tools:
http://forum.xda-developers.com/showthread.php?t=1766475
or
http://forum.xda-developers.com/showthread.php?t=1809195
Both are magic tools for nexus 7, please read any explanation carefully!
It may help you :good:
Click to expand...
Click to collapse
Wow.....
Please stop spamming the toolkits.
The op has indicated that there is a hardware issue because the bootloader unlock isn't working.. A stupid toolkit isn't going to fix that. You should are promoting people to use their damn brains and doing it the right way, but laziness prevails, eh?
To the op, sorry but it sounds like you have a corrupt emmc. If the unlock process fails to commit, that's a bad sign.
Sent from my Nexus 5
Also to the op, USB debugging has nothing to do with the bootloader or recovery, only a booted os. Can you boot to recovery from the bootloader?
Sent from my Nexus 5
Asus' unlock tool for M1 is dead (network error, guess they just cut the line for older models). Attached one I had in my backup from who knows how long ago, since I couldn't find any working links anymore.
Trying unlock tool for newer devices throws "Device model is not supported".
Dev. menu option for OEM Unlock is not available in neither of "official" images.
Max Pro's unlock doesn't work for this device.
So am I really stuck with Android 10 Beta release? I guess it is kind of "win" considering this release isn't completely bloated by Asus, but it would still be nice to get TWRP and Lineage on it. Not to mention I really wanted to give the Postmarket try on this device.
I'm more than willing to be lab rat if anyone wants to try.. stuff.. on my device, at this point I wouldn't even mind if it got bricked in progress.
Alright I have not given up on this, yet. I've stumbled upon post from one of the Asus' moderators on their forums:
For ZB555KL, there will no longer be any system updates and maintenance (including server).
Sorry for any inconvenience it may cause.
Click to expand...
Click to collapse
What this means is there is no official way to unlock this phone anymore, as their unlock app has nothing to communicate with.
In the same thread, another user posted this:
I dont know if you are still looking for this but after working on it for hours what you are looking for is:
in fastboot mode type:
fastboot oem enable-unlock-once
will unlock the bootloader for you until the phone is reset. Just have to do it everytime you reboot back into fastboot.
Also if you're flashing recovery, these other 2 commands may prove useful:
fastboot oem reboot-recovery
fastboot oem reboot-recovery-wipe
Cheers!
Click to expand...
Click to collapse
Indeed using this, I was able to flash recovery. Multiple actually: TWRP, stock from step 3 of the post, OrangeFox, stock again.
Why? Well, booting into any recovery leaves me hanging on black screen.
I've tried TWRP, OrangeFox. Nothing. I have found stock recovery image as well, which I have flashed. Got black screen again. BUT. Thanks to the stock recovery image I've figured out it was actually working, since after pressing some buttons randomly (kind of stupid, I know, but I though its bricked at that point anyway) I've managed to wipe data and was presented with fresh startup. I'm thinking both TWRP and OrangeFox worked as well, its the screen that doesn't want to show things for some reason while in recovery.
So if any of you got any ideas why would any recovery present me with blank screen and how should I deal with it, I'm all ears. Or eyes..