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 ((((
Followed these instuctions:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
My phone is now stuck at the google logo and will not go past. After rooting and clockwork i was not able to load anything else but i would not boot.
Please help.. Thank You
seriously? there is like 4 threads on how to root it, and you go with one that you shouldnt.. lol
it had pictures.. lol
all the threads on here talk about specific phone models and i wasnt sure so i just went with it... Bad choice on my part..
hopefully someone can help
load up fastboot and try to get to recovery if you can then awesome.. try wiping everything and see if that fixes anything
Pull the battery, hold volume up and power and follow this post to get into recovery. Then like shabby penguin said, when you get into recovery wipe everything and you should be good to go. Again, the post I linked you to is the proper way to root the 4g...
http://forum.xda-developers.com/showpost.php?p=13570498&postcount=5
i can get into recovery and i wiped the phone, but still doesnt help.
opie2l said:
i can get into recovery and i wiped the phone, but still doesnt help.
Click to expand...
Click to collapse
Oh, guess I didnt catch that.
ok your best bet it to go into fastboot and flash the clockworkmod 3.0.2.4
did you do the oem unlock command?
yeah i did the oem unlock.
ok well assuming you followed the directions from this guy, then you have a diff bootimg on there i can toss a few files that may fix it, but no garuntees...
seriously tho
(You should see that “LOCK STATE” says “UNLOCKED”, meaning your Nexus S is rooted.)
Click to expand...
Click to collapse
is posted on his site.. that would be a good indicator to me to stop listening to anything he said.. he then later in the comments was trying to help someone and told them if usb wasnt working then use a microsd adapter to put the files on..
yeah i am kicking my self in the a$$. Is there anyway do just get it back to stock?
well have you tried flashing a kernel? if it gets to bootani then its usually rom erros, freezing at spalsh screens is generally kernel images
is it possible to load a kernel when i cant see the phones memory from the computer???
someone has to have some idea of to fix this...
just got me to stock unrooted phone.. please
yes, download this
boot into fastboot and type in fastboot flash boot /path/to/natarchy.img
replace /path/to with where its located.. this should get you rollin again
thank you... thank you... thank you!!!!!!!!
i have learned my lesson and i wont stray from the xda forum next time.
Again thank you
I have a similiar issue as OP...I tried to flash netarchy kernel with kernal manager and then phone rebooted and got stuck at google logo.
I have installed SDK...google drivers, but when I try to flash the kernel I get waiting for device in command prompt. Same error when I type "fastboot oem unlock"
Any ideas?
Skillz1318 said:
I have a similiar issue as OP...I tried to flash netarchy kernel with kernal manager and then phone rebooted and got stuck at google logo.
I have installed SDK...google drivers, but when I try to flash the kernel I get waiting for device in command prompt. Same error when I type "fastboot oem unlock"
Any ideas?
Click to expand...
Click to collapse
Waiting for device means Windows does not recognize phone. Reinstall drivers.
ok sounds like a driver issue, i used pdanet to install the drivers i needed. try fastboot devices, if it doesnt show anything then your phone isnt connected
Ok used my mac and was able to get cwm recovery on device. I could mount it. Now how can I flash back to stock. I9020A att 3G version. Booting now I see google and a lock.
Thanks everyone!
I updated my android to 4.3. since then I lost the root permissions. The phone shows as being unlocked when I start it up. when I have tried different programs or apps, I can't get the permissions back. One program I have tried, sorry, don't remember the name, said it was going to reboot the phone, but that never happened. I used it with my older version of android and it worked fine.
When I got into recovery mode, I the the android robot with the red !, saying no command.
I wanted to see if anyone knew what might be going on and what I could do to get back my permissions.
Thanks
jrwn said:
I updated my android to 4.3. since then I lost the root permissions. The phone shows as being unlocked when I start it up. when I have tried different programs or apps, I can't get the permissions back. One program I have tried, sorry, don't remember the name, said it was going to reboot the phone, but that never happened. I used it with my older version of android and it worked fine.
When I got into recovery mode, I the the android robot with the red !, saying no command.
I wanted to see if anyone knew what might be going on and what I could do to get back my permissions.
Thanks
Click to expand...
Click to collapse
Android 4.3 contains security fixes that require root to be updated. Download the SuperSu v1.55 zip from http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip and copy the file to the Nexus' internal storage. Reboot the phone to recovery and install UPDATE-SuperSU-v1.55.zip from Clockworkmod or TWRP, then reboot the phone. You should now be able to grant privileges to the apps that require root access.
BobWalker said:
Reboot the phone to recovery and install UPDATE-SuperSU-v1.55.zip from Clockworkmod or TWRP, then reboot the phone. You should now be able to grant privileges to the apps that require root access.
Click to expand...
Click to collapse
The big issue I am running into is when I try to go to recovery, I get the dead android and "no command" error.
jrwn said:
The big issue I am running into is when I try to go to recovery, I get the dead android and "no command" error.
Click to expand...
Click to collapse
you updated stock, so you now have the stock recovery, thats the "dead" android. flash a custom recovery via fastboot, then flash the supersu su binaries via your new custom recovery. youll be fine, make sure to stay away from root toolkits or you will nwver learn anything, like this. this is such a basic thing to know to do, yet people that use root toolkits dont know.
OK, I'll have to try that tonight or over the next couple of days when I have a chance. Thank you.
jrwn said:
OK, I'll have to try that tonight or over the next couple of days when I have a chance. Thank you.
Click to expand...
Click to collapse
if you dont know how, read a little. its really easy. its a matter of typing one line into a command window
OK, I've tried it, but it doesn't seem as if the computer is communicating with the phone. I have also tried one of the auto programs to do it, but it gets stuck at "waiting for device." If I reboot the device and try to get into recovery mode, I just get a dead android saying "no command" I can't get any other options to try to reset the devices back to factory settings.
I have tried the reset option in the settings menu, but It still saves information and doesn't take the phone back to 4.2, which is what I first had.
I'm hoping someone has some ideas on what I can do. On the other hand, I am planning on upgrading my wife's phone. I might just get a new one, and give her this one, although I'm not sure if I want to get a nexus, maybe a different one this time.
jrwn said:
OK, I've tried it, but it doesn't seem as if the computer is communicating with the phone. I have also tried one of the auto programs to do it, but it gets stuck at "waiting for device." If I reboot the device and try to get into recovery mode, I just get a dead android saying "no command" I can't get any other options to try to reset the devices back to factory settings.
I have tried the reset option in the settings menu, but It still saves information and doesn't take the phone back to 4.2, which is what I first had.
I'm hoping someone has some ideas on what I can do. On the other hand, I am planning on upgrading my wife's phone. I might just get a new one, and give her this one, although I'm not sure if I want to get a nexus, maybe a different one this time.
Click to expand...
Click to collapse
install the right drivers. and dont use one of those "auto" programs, thats why you dont know what you are doing now.
simms22 said:
install the right drivers. and dont use one of those "auto" programs, thats why you dont know what you are doing now.
Click to expand...
Click to collapse
I did try to do it manually, the phone didn't respond. This is why I also tried a program. You are correct, I don't know what to do from this point.
jrwn said:
I did try to do it manually, the phone didn't respond. This is why I also tried a program. You are correct, I don't know what to do from this point.
Click to expand...
Click to collapse
you need to get the driver installed to your computer, fastboot as well. when its all ready, open fastboot and a command window then and type.. fadtboot devices. then itll see your device(or not if the driver isnt installed). when it sees your device, you need fastboot flash your recovery.. fastboot flash recovery recoveryname.img. then you need to flash the latest su binaries via your recovery(latest supersu will work).
Hi all,
As mentioned in the title, an update from LG came for my 802 and suddenly, it booted and entered TWRP.
Now, it always goes back to TWRP. Anyone knows how I can solve this or boot normally again?
Thx,
Xiribi
TWRP, that's the problem.
Custom recovery and OTA will be end like this.
Easy fix here
Xenovias said:
TWRP, that's the problem.
Custom recovery and OTA will be end like this.
Easy fix here
Click to expand...
Click to collapse
Will this reset the phone?
Don't want to lose all the data
Xenovias said:
TWRP, that's the problem.
Custom recovery and OTA will be end like this.
Easy fix here
Click to expand...
Click to collapse
but when i do this fix is the ota update then installed?
Edit: the update is not installed but how do i get that update installed whit cwm or other recovery?
Xenovias said:
TWRP, that's the problem.
Custom recovery and OTA will be end like this.
Easy fix here
Click to expand...
Click to collapse
Unfortunatelly this did not solve the problem.
Keeps in a bootloop now and nothing happen.
Anyone remenbers where I can find the ADB thread to restore the phone?
When I try now I get an error that the ADB shell is is error: closed.
I'm looking for a way to put an image back on the phone.
THX guys.
Xiribi said:
Unfortunatelly this did not solve the problem.
Keeps in a bootloop now and nothing happen.
Anyone remenbers where I can find the ADB thread to restore the phone?
When I try now I get an error that the ADB shell is is error: closed.
I'm looking for a way to put an image back on the phone.
THX guys.
Click to expand...
Click to collapse
Use the terminal command if you can't use ADB... might work?
That's what I did, because AT&T stops giving you the option to not update after a couple times, and then I got stuck like you.
http://forum.xda-developers.com/showthread.php?t=2582142
please learn to search and read before doing stuff on your precious phone
FiendFyre said:
Use the terminal command if you can't use ADB... might work?
That's what I did, because AT&T stops giving you the option to not update after a couple times, and then I got stuck like you.
Click to expand...
Click to collapse
i did use the terminal and got into the boot loop.
Cannot perform any operation trough command because it gives me an error saying that the adb shell is error closed.
I'm now trying something else with some LG tools I found here. Hope it works, if it does, I'll repost the link here.
Xiribi said:
i did use the terminal and got into the boot loop.
Cannot perform any operation trough command because it gives me an error saying that the adb shell is error closed.
I'm now trying something else with some LG tools I found here. Hope it works, if it does, I'll repost the link here.
Click to expand...
Click to collapse
I'm not sure what happened for you, because the terminal command worked for me... maybe you mistyped it, or maybe you had a slightly different problem or something. Not sure.
Guys,
I finnaly managed to have my device working.
Trough ADB shell and then trough ADB I was able to copy a downloaded ROM (FLEX rom) to the device and installed it.
After a couple of hours, all is OK.
THANK YOU ALL FOR THE HELP AND INFO!!! (PS: sorry for the caps)
Hi All,
I realise you guys must be sick of these kind of posts but just thought that one of you would be able to point me in the right direction before I do something else wrong!
I was rooted on d802, Cloudy 3.3 with TWP 2.8.6.1 installed. I was trying to get magisk to work but after flashing the various zips etc I left my phone for a few minutes and a toddler came along and swiped the install superSU prompt on TWRP that comes up before rebooting :/:/:/.
So now I am stuck in this "[720] Fastboot mode started". When I plug it into my computer I get a few other things popping up and on device manager it comes up as "Android Bootloader Interface", Device type Kedacom USB Device.
Before messing around with all these things I made a full backup with TWRP so if I can just get back to that I am hoping I will just be able to restore it? At the moment I am unable to get to recovery mode, it just keeps rebooting quickly showing the LG logo and proceeding to fastboot mode. I have tried the holding down power and vol d button but it happens so fast and doesnt seem to do anything.
Where should I go from here? There seem to be a lot of different methods and various things, the more I search the more ways I find!! What is best in my particular situation?
Also could somebody definitively tell me if Magisk will work with cloudy 3.3? I can find no mention anywhere on the internet of someone saying they have done it/got it to work.
amishra123 said:
Where should I go from here?
Click to expand...
Click to collapse
Hi!
This way > http://forum.xda-developers.com/lg-g2/help/fixing-fastboot-mode-started-t2930963
And if it doesn't work I would make this > http://forum.xda-developers.com/lg-g2/help/noob-friendly-recovery-download-mode-t3112805
And you can find a list with all fixes right here > http://forum.xda-developers.com/showpost.php?p=63327417&postcount=4
Good luck!
Thank you very much for your prompt reply !!
I kept trying with the power and volume down and managed to somehow get back into recovery, and then I recovered using the backup!! All back to normal now !
I've since updated to the latest twrp and that all went smoothly aswell.
Any word on whether magisk V9 will work with cloudy g2 3.3 ? I'm tempted to give it another go...
Use the unsu zip , uninstall xposed using the zip , then flash magisk , phh superuser and finally the cbump. I'm really tempted to try again but not sure if it was doing that , that messed it up last time or if it was twrp trying to install super su (Im quite sure it is probably the latter though). Any thoughts ?
EDIT: incase this helps anyone else, I think what I did was to keep the power and vol down held for a long time , if I remember correctly it seemed to cycle a few times through logo and then the fastboot screen until it finally switched off. Prior to this as soon as I thought it was off it would just start again. This time though it went through into the factory reset screen and then recovery.
amishra123 said:
All back to normal now !
Click to expand...
Click to collapse
Nice to here that. :good:
amishra123 said:
Any word on whether magisk V9 will work with cloudy g2 3.3 ?
Click to expand...
Click to collapse
That's a question for the CloudyRom-thread. I bet you're not the first with this question.