So I unlocked the bootloader and then rooted my phone using the guide from The Unlockr. Now when I boot up my N1, I get to the screen with the still Nexus logo and a lock under it. It will sit there and not do anything else.
What is going on?
How can I get my phone working right again?
When I go to recovery, it will show the X with the lock under it and then it will go black and do nothing...
It does not seem that you have unlocked it yet. Try to do it via ADB and fastboot
What are the exact steps you did?
After unlocking bootloader did you install a custom recovery and flash a Rom?
I first set up ADB on my computer.
Then I rooted my phone with Superboot.
I followed these steps:
http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
To me, it sounds like the installed superboot isn't compatible with your Nexus One. And also note that that guide was from early 2010, around which Froyo was around.
Try looking for a more up-to-date guide.
Related
I have a brand new bootloader unlocked Nexus One which is stuck at the boot logo (not the animated one, the static four-colour X).
Out of the box, all I did was:
1) Power up holding the trackball to get to the bootloader screen
2) Plug the phone into a USB port
3) Run fastboot oem unlock
The phone then started to reboot, and it's been stuck since then. At the boot screen, the unlocked padlock is underneath the X logo. It doesn't even get to the animated X.
I've tried flashing Amon Ra's recovery image (which I think worked) and booting into it, but it also hangs before the animated X.
What else can I try to unbrick this phone?
From what i understand is once you OEM UNLOCK it actually wipes the WHOLE phone, and from there you flash recovery image, then flash a rom to it.. to boot up..
If looking something that is close to stock but will lot of goodies, try Enomthers ROM
Unlocking the bootloader doesn't overwrite either the boot or the system image, so it should boot with the stock images as normal, just with the unlocked padlock on boot.
Running fastboot boot ~/path/to/stock/systemimage/system.img yields no success either.
try installing new rom like cyanogen 6 or enom's 2.11.1
alisdair said:
I have a brand new bootloader unlocked Nexus One which is stuck at the boot logo (not the animated one, the static four-colour X).
Out of the box, all I did was:
1) Power up holding the trackball to get to the bootloader screen
2) Plug the phone into a USB port
3) Run fastboot oem unlock
The phone then started to reboot, and it's been stuck since then. At the boot screen, the unlocked padlock is underneath the X logo. It doesn't even get to the animated X.
I've tried flashing Amon Ra's recovery image (which I think worked) and booting into it, but it also hangs before the animated X.
What else can I try to unbrick this phone?
Click to expand...
Click to collapse
you could of went this route without unlocking your bootloader.
http://forum.xda-developers.com/showthread.php?t=736271
Amritttt said:
try installing new rom like cyanogen 6 or enom's 2.11.1
Click to expand...
Click to collapse
i cant do anything. adb mode say device not found. i have nonrooted Nexus One. cant connect to PC cant do anything. Any solution.
bagi576 said:
i cant do anything. adb mode say device not found. i have nonrooted Nexus One. cant connect to PC cant do anything. Any solution.
Click to expand...
Click to collapse
Making sure you have correct driver installed
Sent from my Nexus one using xda app-developers app
taodan said:
Making sure you have correct driver installed
Sent from my Nexus one using xda app-developers app
Click to expand...
Click to collapse
i've installed uninstalled many time. no luck.
bagi576 said:
i've installed uninstalled many time. no luck.
Click to expand...
Click to collapse
Which OS do you currently using for your PC? Don't use Windows 8
this is what i tried to do: wanted to flash a new rom from my original froyo. read through the guide and got it rooted and installed rom manager and in turn installed recovery. booted into recovery and made a backup. tried installing a rom but it wouldnt let me so at the end installed RA recovery instead. i was able to flash a different rom. mpw tried to boot to recovery to get stock rom it display just the android and exlamation mark.
i can get into bootloader but in recovery wont show a thing as if it lost the recovery program.
tried installing sdk but adb wont see the phone.
SDK version 9, windows vista
Any ideas?
You have the stock recovery...
Read the wiki. Follow the guide for unroot/restore, using passimg method and FRG33. Start again rooting (though you probably want to read a bit more first, and make sure you can connect via adb and fastboot BEFORE you mess with stuff)...
Sent from my Nexus One using XDA App
issue is i cant connect through adb or fastboot since i dont have the debug mode before it all went
You don't need adb or fastboot to follow the unroot/restore guide. I was simply suggesting that you make sure it works before you try and root again.
Unroot/restore.
Get adb and fastboot working.
Play with phone.
Sent from my Nexus One using XDA App
how can i get adb/fastboot working. i went through the guide and dozens of other websites.
adb doesnt see a phone connected even though under device manager it shows an android device.
Install the drivers when in fastboot mode, and you'll have fastboot. It's not adb.
fastboot won't help you unless your bootloader is unlocked. adb you won't get, unless you install a ROM and enable debug, or install a custom recovery - which, again, you won't be able to install without unlocked bootloader. adb doesn't work in bootloader mode, you should have found that in at least one of the "dozen guides".
So, you have 2 options:
1) you have unlocked bootloader or you want to unlock bootloader - in that case, enter the bootloader, connect usb, install fastboot drivers, install custom recovery with fastboot.
2) you don't want to unlock bootloader - then follow the correct advice given to you in danger-rat's posts above.
So, you have 2 options:
1) you have unlocked bootloader or you want to unlock bootloader - in that case, enter the bootloader, connect usb, install fastboot drivers, install custom recovery with fastboot.
2) you don't want to unlock bootloader - then follow the correct advice given to you in danger-rat's posts above.[/QUOTE]
ok problem solved and thanks. all along the dll file for fastboot was in platform-tools instead of tool within the sdk hence why fastboot never worked. unlocked the bootloader and recovered my old image. incase anyone else have this issue.
thanks
I tried following this guide to downgrade to 4.2.2 so that I could root my AT&T device.
I was able to adb and fastboot into the device. And I flashed the ATT CU update with fastboot.
After that the device constantly reboots after reaching the M logo screen,
I can boot into the bootloader, and I can send fastboot commands, but not any adb commands.
I also cannot load any of the options in the bootloader (Recovery, Factory, etc), they simply reboot the phone.
I don't care what version of Android I go to as long as it gives me a working phone. Please help!
Thanks.
Edit: I was able to recover my phone by flashing the 4.4 update. I would like to know where I went wrong, so that I could possibly still do the downgrade>root>upgrade path.
UberSprode said:
I tried following this guide to downgrade to 4.2.2 so that I could root my AT&T device.
I was able to adb and fastboot into the device. And I flashed the ATT CU update with fastboot.
After that the device constantly reboots after reaching the M logo screen,
I can boot into the bootloader, and I can send fastboot commands, but not any adb commands.
I also cannot load any of the options in the bootloader (Recovery, Factory, etc), they simply reboot the phone.
I don't care what version of Android I go to as long as it gives me a working phone. Please help!
Thanks.
Edit: I was able to recover my phone by flashing the 4.4 update. I would like to know where I went wrong, so that I could possibly still do the downgrade>root>upgrade path.
Click to expand...
Click to collapse
You know there's a way to unlock your bootloader for $43ish. Many success stories. Your phone playing life would improve greatly.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Just got my 3t and went to do the full upgrade (non-rooted) to 4.0.1 which hung the device.
I can get into recovery mode but all that does is leave the android logo on.
I can get fastboot to recognize the device, but whenever I try do anything other than device I get FAILED since it isn't rooted
And I tried the bricked directions but all that gets is a 258 error as soon as it tries to install cache.img
Any thoughts other than banging my head against the wall that I can try?
Can you tell us what you did step by step?
What recovery do you have?
Is your bootloader locked or unlocked?
USB Debugging and OEM Unlock options enabled in Developer mode?
Did you try the upgrade through sideload or recovery?
Was it a full install or OTA?
Where did you download the files from?
There is an excellent thread about how to do the install step by step.
Follow this and you should be fine.
https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Hope that helps!
So, I ****ed up.
Earlier this night i hard bricked my device while trying to uninstall Magisk. Used a guide that worked and was back on stock OOS 3.5.0.
In the old Oxygen OS I installed TWRP. But the thing with the recovery was that you needed to boot recovery from the command line with the command
Code:
fastboot boot twrp.img
. If I booted into recovery in any other way the screen is just black and never boots.
When I tried to install OOS 4.0.1 I got error code 7. Googled it and it just told me to relock the bootloader and install the OTA instead.
I relocked it, and when it was done I got the prompt to fill in the password to start Android. But the thing was I did not use any security options, no fingerprint or pin code. So zero luck there. And now I can't boot into recovery because I didn't flash the stock recovery because I'm a retard, so when I'm trying to boot recovery it's just black. So I have no chance to come back. Please help...
So this is not a hard brick. It's a brick for sure, but a Hard Brick is where you cannot boot up your phone whatsoever.
Now, assuming from the vague details you've provided, you can boot into the normal boot logo screen? You should be able to get into fastboot, but if you can't since you've not mentioned it, there are still ways of getting your device back into OOS.
If you can get your device into Fastboot;
1. Boot into FB
2. Unlock your bootloader
3. Reflash TWRP
4. Boot into TWRP
5. Flash ROM of your choice.
If you can't get into Fastboot;
Use this thread ( https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306)
OR use this one if you want the updated tools and follow the instructions on the above Thread (https://forum.xda-developers.com/oneplus-3t/help/ultra-brick-oreo-firmware-ob16-nougat-t3689356)
What you need to know;
Never lock your bootloader when you have a Third Party recovery or ROM installed.
Never interrupt the unbrick process.
Please do a search here on XDA before you post a new thread. There have been similar issues solved multiple times on this Forum.
Good luck!
thes3usa said:
So this is not a hard brick. It's a brick for sure, but a Hard Brick is where you cannot boot up your phone whatsoever.
Now, assuming from the vague details you've provided, you can boot into the normal boot logo screen? You should be able to get into fastboot, but if you can't since you've not mentioned it, there are still ways of getting your device back into OOS.
If you can get your device into Fastboot;
1. Boot into FB
2. Unlock your bootloader
3. Reflash TWRP
4. Boot into TWRP
5. Flash ROM of your choice.
If you can't get into Fastboot;
Use this thread ( https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306)
OR use this one if you want the updated tools and follow the instructions on the above Thread (https://forum.xda-developers.com/oneplus-3t/help/ultra-brick-oreo-firmware-ob16-nougat-t3689356)
What you need to know;
Never lock your bootloader when you have a Third Party recovery or ROM installed.
Never interrupt the unbrick process.
Please do a search here on XDA before you post a new thread. There have been similar issues solved multiple times on this Forum.
Good luck!
Click to expand...
Click to collapse
Thank you for your reply, I tried to do the method with the MSMDownload thing yesterday, but the computer did not recognize the device. It was late in the night (5am) so I went to bed. This morning I took my other computer and plugged my phone in, it recognized it and I was able to fully recover the phone!
avveawesome said:
When I tried to install OOS 4.0.1 I got error code 7. Googled it and it just told me to relock the bootloader and install the OTA instead.
Click to expand...
Click to collapse
This isn't good idea. As already noted, never relock the bootloader on this device with TWRP, root, etc. It should only be relocked after returning to full stock condition.
Also, never install an incremental OTA when you have TWRP (root, etc.), only the full update zips should be used in that case.
Try to stick to these forums for advice. Maybe the guidance your found above is not specific to this device?