who has a recommendation on the proven root method for nexus s i9020A (att). seeing what happened to wifi xoom early adopter root attempts, i was looking for confirmation no issue with boot.img on the i9020A and device won't brick if using the i9020T root method.
What's wrong with "fastboot oem unlock"?
crachel said:
What's wrong with "fastboot oem unlock"?
Click to expand...
Click to collapse
fastboot oem unlock not in question. looking for confirmation that rooting the att nxs using the tmob root files work.
Related
Hello guys, I'm not a super noob but I can certainly use some advise and suggestions. I was trying to be all smart and try to put CM7 on my phone by rooting the nexus S without having to unlock the bootloader. I've read around and realized that I could do so if my phone is on 2.3.2 or 2.3.1.
So I search around and the following thread:
http://forum.xda-developers.com/showthread.php?t=947950
suggested using Odin to downgrade from 2.3.4 to 2.3.1. After doing the steps I realized that it also unlocked my bootloader. Now does anyone know if there is a way to relock my bootloader if I used the Odin?
I've done some reading and as far as I can tell you can relock your phone using the "fastboot oem relock". but this method only works if you originally used the "fastboot oem unlock" in the first place.
Any suggests?
hamidsani said:
Hello guys, I'm not a super noob but I can certainly use some advise and suggestions. I was trying to be all smart and try to put CM7 on my phone by rooting the nexus S without having to unlock the bootloader. I've read around and realized that I could do so if my phone is on 2.3.2 or 2.3.1.
So I search around and the following thread:
http://forum.xda-developers.com/showthread.php?t=947950
suggested using Odin to downgrade from 2.3.4 to 2.3.1. After doing the steps I realized that it also unlocked my bootloader. Now does anyone know if there is a way to relock my bootloader if I used the Odin?
I've done some reading and as far as I can tell you can relock your phone using the "fastboot oem relock". but this method only works if you originally used the "fastboot oem unlock" in the first place.
Any suggests?
Click to expand...
Click to collapse
The command is actually "fastbook oem lock" and I would think it would work now matter how the bootloader was unlocked. You should at least try it. You just have to make sure you have Android SDK installed and your device drivers installed.
fastboot oem unlock to unlock and wipe your phone, flash cwm recovery, flash cm7.
turn off phone, turn it back on to bootloader and do fastboot oem lock.
Done.
Other than removing the unlock icon from showing what is/are the added benefit(s) of relocking the phone? I am just curious as I unlocked my Nexus S by ADB using the fastboot oem unlock command. Thanks.
Sent from my Nexus S using Tapatalk
As the topic says, what does the unlocking of the bootloader do and why do you have to do it? Also does unlocking the bootloader void the warranty?
Sent from my Nexus S using Tapatalk 2
All your answers are here:
http://www.addictivetips.com/mobile...-bootloader-on-android-phones-complete-guide/
And yes, unlocking the bootloader voids your warranty. But on Nexus is really easy to relock it with fastboot oem lock command.
DeuXGod said:
All your answers are here:
http://www.addictivetips.com/mobile...-bootloader-on-android-phones-complete-guide/
And yes, unlocking the bootloader voids your warranty. But on Nexus is really easy to relock it with fastboot oem lock command.
Click to expand...
Click to collapse
Personally, this confuses me more than before. I understand the concept of a bootloader, but not that a customer rom cannot be loaded without it being unlocked. I'm using an ATT Galaxy S5, which as I understand cannot be unlocked. However, my device is rooted and has a custom rom loaded (Dynamic KAT 4.0 NI2 build).
So what exactly does unlocking the bootloading gain over simply rooting and loading a custom rom such as I have done?
Thanks!
Edit: Crap, just realized this is a really old thread. I'll search further...
Different devices have different methods of rooting, the nexus s is one that you need to unlock the bootloader first, then you can root and/or flash a custom ROM, recovery, kernel, etc
Yes some phone don't need you to unlock bootloader and yes some bootloaders can't be unlocked so you're question is device specific in the sense that every device is different
So my ATT One X is soft bricked and when I run RUU_Evita_UL_Cingular_US-1.82.502 It gives me the customer ID error.
I rooted, unlocked bootloader, and flashed CMR, but it is now no longer rooted and the bootloader is relocked.
I did modify the CID to "11111111" to unlock the bootloader, but without me being rooted I am unable to put the original "mmcblk0p4" back on (idk if that even matters.) I have no backups and absolutely everything is erased.
I did flash the stock recovery img file, but I don't know if it was relevant to international One X or if there is one specifically for ATT One X.
I guess a fix would be making a goldcard, without an sd card somehow....
Thanks for the Help.
Never seen that error before. Have you tried running the 1.85 RUU? I have RUU'd multiple times while still having the SuperCID so I don't think that's the issue.
Sent from my HTC One X using xda premium
_MetalHead_ said:
Never seen that error before. Have you tried running the 1.85 RUU? I have RUU'd multiple times while still having the SuperCID so I don't think that's the issue.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I was actually using the 1.7 RUU
I'll try 1.82 then 1.85. Hopefully that will work.
Thanks for the quick reply! :good:
Have you tried to relocking the boot loader?
fastboot oem lock
Then run ruu.
The ruu will flash the stock recovery.
Sent from my HTC One X using xda premium
Still not going through and getting same error....
Any ideas?
Thanks.
Are in Canada? That would mean u need to use the rogers ruu, not the evita. Or, are u positive u changed your cid to 11111111 and not ROGER001. There were tutorials in the beginning doing this before supercid 11111111 was found. But customer I'd means either, rogers or evita typically. Evita ruu won't work on rogers and vice versa:thumbup:
Sent from my HTC One X using xda premium
18th.abn said:
Are in Canada? That would mean u need to use the rogers ruu, not the evita. Or, are u positive u changed your cid to 11111111 and not ROGER001. There were tutorials in the beginning doing this before supercid 11111111 was found. But customer I'd means either, rogers or evita typically. Evita ruu won't work on rogers and vice versa:thumbup:
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
No. I'm in US on ATT network. And yes I did change the CID to 11111111 because I used that method to unlock my bootloader.
I've tried several RUUs for my phone and still get same error. If I were to verify I had changed the CID I would have to be rooted.
Is it possible to root a soft-bricked device????
What's the error number?
Depending on what it is, there are different fixes.
if you can still do fastboot commands I'd unlock the bootloader again then push the twrp with USB support.
Once you do that you can flash the rom of your choice by copying it to your phone from TWRP.
---------- Post added at 08:51 PM ---------- Previous post was at 08:44 PM ----------
I was stuck with a soft brick when I interrupted the installation of a ROM that was a bad download.
I was able to do what I said in my previous post and it fixed me right up
gunnyman said:
What's the error number?
Depending on what it is, there are different fixes.
if you can still do fastboot commands I'd unlock the bootloader again then push the twrp with USB support.
Once you do that you can flash the rom of your choice by copying it to your phone from TWRP.
Click to expand...
Click to collapse
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.
ArcriusOneX said:
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.[/QUOTEhmm I've never switched my CID back so I am not sure if it will work, but try this
get to the bootloader (power volume down)
from bootloader select fastboot
once in fastboot mode
with phone plugged into usb type
fastboot flash unlocktoken Unlock_code.bin just like you did to unlock the bootloader in the first place just make sure that adb, fastboot, and the unlock.bin file are all in the same directory on your computer
once you are unlocked you should be able to do the rest
Error 131 is related to using the wrong RUU for your CID SuperCID will override this error. If you flashed your CID back to the AT&T one the only RUU you can flash (I think) is the 1.85 one
Click to expand...
Click to collapse
gunnyman said:
ArcriusOneX said:
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.[/QUOTEhmm I've never switched my CID back so I am not sure if it will work, but try this
get to the bootloader (power volume down)
from bootloader select fastboot
once in fastboot mode
with phone plugged into usb type
fastboot flash unlocktoken Unlock_code.bin just like you did to unlock the bootloader in the first place just make sure that adb, fastboot, and the unlock.bin file are all in the same directory on your computer
once you are unlocked you should be able to do the rest
Error 131 is related to using the wrong RUU for your CID SuperCID will override this error. If you flashed your CID back to the AT&T one the only RUU you can flash (I think) is the 1.85 one
Click to expand...
Click to collapse
Yeah I actually was able to unlock the bootloader already. Sorry I spoke too soon!
How do I go about pushing the twrp?
Click to expand...
Click to collapse
ArcriusOneX said:
gunnyman said:
Yeah I actually was able to unlock the bootloader already. Sorry I spoke too soon!
How do I go about pushing the twrp?
Click to expand...
Click to collapse
download it from and follow the directions here http://forum.xda-developers.com/showthread.php?t=1703626
very simple and straightforward
Click to expand...
Click to collapse
gunnyman said:
ArcriusOneX said:
download it from and follow the directions here http://forum.xda-developers.com/showthread.php?t=1703626
very simple and straightforward
Click to expand...
Click to collapse
SUCCESS!!!! :laugh::laugh::laugh:
Thank you so much! You resurrected my phone!
I'm guessing this is similar to CMR?? Looks a lot nicer.
Click to expand...
Click to collapse
ArcriusOneX said:
gunnyman said:
SUCCESS!!!! :laugh::laugh::laugh:
Thank you so much! You resurrected my phone!
I'm guessing this is similar to CMR?? Looks a lot nicer.
Click to expand...
Click to collapse
yeah I like it better myself it's faster.
glad you're all fixed
Click to expand...
Click to collapse
Hi everyone,
I want to root my "One X 3.18 AT&T cws_001" to flash my boot.img because i have a reboot/crash problem. However, to root the device the bootloader must be unlocked, and to unlock the Bootloader it must be rooted Anyone have an idea of how i can resolve this ? Thanks.
darkdean said:
Hi everyone,
I want to root my "One X 3.18 AT&T cws_001" to flash my boot.img because i have a reboot/crash problem. However, to root the device the bootloader must be unlocked, and to unlock the Bootloader it must be rooted Anyone have an idea of how i can resolve this ? Thanks.
Click to expand...
Click to collapse
If your phone is not rooted flashing boot.img doesn't apply to you. If it's completely stock do factory reset in bootloader. If that doesn't work, download and run the 3.18 AT&T RUU EXE file not ZIP file and run it with your phone plugged in.
exad said:
If your phone is not rooted flashing boot.img doesn't apply to you. If it's completely stock do factory reset in bootloader. If that doesn't work, download and run the 3.18 AT&T RUU EXE file not ZIP file and run it with your phone plugged in.
Click to expand...
Click to collapse
I did this but the problem is still here, how can i root it with a locked bootloader please ? or how can i unlock the bootloader whithout root ?
darkdean said:
I did this but the problem is still here, how can i root it with a locked bootloader please ? or how can i unlock the bootloader whithout root ?
Click to expand...
Click to collapse
Rooting will not fix your issue if running the RUU does not. RUU is the software fix for rooted and none rooted phones. So if an RUU does not fix it. It's a hardware issue.
Your phone needs to be operational to root/unlock.
Hello
I have HTC One M7_UL rooted (originally by AT&T). It is rooted, but it is still locked. What can I do?
Thanks in advance
norgematos said:
Hello
I have HTC One M7_UL rooted (originally by AT&T). It is rooted, but it is still locked. What can I do?
Thanks in advance
Click to expand...
Click to collapse
you need a unlock code. on ebay you can find some cheap unlock code
b0unty said:
you need a unlock code. on ebay you can find some cheap unlock code
Click to expand...
Click to collapse
I have the unlock code, but it does not works, because it is for AT&T, and now the phone is rooted.
norgematos said:
I have the unlock code, but it does not works, because it is for AT&T, and now the phone is rooted.
Click to expand...
Click to collapse
well if your M7 is branded by AT&T your bootloader is locked by AT&T
you need to unlock your bootloader first
look on google howto unlock your bootloader
b0unty said:
look on google howto unlock your bootloader
Click to expand...
Click to collapse
Bootloader is unlocked. Actually right now is relocked... I am trying to flash it using fastboot. Anyway, it's wasted time, I downloaded and tried 16 ruu, and I am receiving "signature verify fail" even when I saw my modelid and my cidnum in android-info file. I am confused, I tried using RUU.exe and fastboot using zip file.same result.
By the way, it is S-ON.
Any idea?
norgematos said:
Bootloader is unlocked. Actually right now is relocked... I am trying to flash it using fastboot. Anyway, it's wasted time, I downloaded and tried 16 ruu, and I am receiving "signature verify fail" even when I saw my modelid and my cidnum in android-info file. I am confused, I tried using RUU.exe and fastboot using zip file.same result.
By the way, it is S-ON.
Any idea?
Click to expand...
Click to collapse
Go S-OFF first
LS.xD said:
Go S-OFF first
Click to expand...
Click to collapse
I want to go S-OFF, but I just can access to the bootloader, so I can't use adb... do I can go S-OFF without adb?
No.
Sent from my beloved HTC One S using (most time buggy) Tapatalk
SOLVED
Connected to PC using https://www.youtube.com/watch?v=PUjQnwULGzs
Fixed using http://www.htc1guru.com/downloads/stock-rom-downloads/