I have read around the forums a lot in my free time(I have lots) and from my understanding: the reason we can't flash the NS loader is because, the efuse/s won't accept the signature from it. Is it possible to switch the signatures(or like a small part of the data inside the file) is make it seem like its the HS loader? Don't hate on me to much, but this seem like it could work? maybe?
Nope.
The ONLY way is to get the efuse to flip, or use a root kit and trick the phone into thinking it is an NS and not an HS, then flash the NS BL from some built in CMW recovery in the root kits image.
Good luck.
jimbridgman said:
Nope.
The ONLY way is to get the efuse to flip, or use a root kit and trick the phone into thinking it is an NS and not an HS, then flash the NS BL from some built in CMW recovery in the root kits image.
Good luck.
Click to expand...
Click to collapse
There's some post on using the external sd to trick it into working is there any news on that ???
darth_nihar said:
There's some post on using the external sd to trick it into working is there any news on that ???
Click to expand...
Click to collapse
Yes, that was tested many moons ago. The issue is getting the NS bootloader to boot. Even by trying to boot off the sdcard with the NS bootloader the efuse is still checked to see if it is truly an NS phone.
The root kit method with the NS bootloader to trick it to think the efuse was set to NS, gave me another brick. That was the last bootloader trick I had up my sleeve before I quit trying to unlock the bootloader on the A2.
Not sure if anyone has tried anything else since then though.
jimbridgman said:
Yes, that was tested many moons ago. The issue is getting the NS bootloader to boot. Even by trying to boot off the sdcard with the NS bootloader the efuse is still checked to see if it is truly an NS phone.
The root kit method with the NS bootloader to trick it to think the efuse was set to NS, gave me another brick. That was the last bootloader trick I had up my sleeve before I quit trying to unlock the bootloader on the A2.
Not sure if anyone has tried anything else since then though.
Click to expand...
Click to collapse
Damn MOTO and its policies..........
Related
I've seen many different rooting methods for the nexus s but unfortunately they don't allow rooting without unlocking the bootloader like the samsung vibrant allows is there anyway I can root my phone without unlocking the bootloader?
why I don't want to unloack the boot loader because I'm fine with the stock ROM on my nexus s. I was really into installing ROMs and things with my Vibrant but the Nexus S feels really complete so I feel like I don't need to unlock my boot loader
Also for the first time I have decent signal in my house after switiching from my blackberry to android so I don't wanna change my baseband and my battery life is good too so I don't want to mess with the kernel
Really? You posted in the same incorrect forum twice with the same question cut and pasted. Nice work!
Sent from my PC36100 using XDA Premium App
You know you can re-lock the bootloader with a fastboot command, right? And the little open lock goes away.
i'm sorry i accidentally reposted i pmed the moderator right away because i didn't know how to delete the post and this is the right section its a question...
i just have one question i can relock right but if i do unlock the bootloader will it change my kernel or baseband settings? i really couldn't care about the warranty and such
it's like opening the door....if you do nothing inside, nothing will happen
yes i get that but i can't flash back to the original recovery as of now and so no changes to the kernel and baseband alright thanks!!
also is there some sort of a "ODIN" availabale for nexus s because thats what I used to always flash my samsung vibrant back to stock. will OTA updates be affected if I root and unlock the bootloader?
anishs said:
also is there some sort of a "ODIN" availabale for nexus s because thats what I used to always flash my samsung vibrant back to stock. will OTA updates be affected if I root and unlock the bootloader?
Click to expand...
Click to collapse
Yes you can use Odin with Nexus S, but consider it the last resort because normally you can do everything via adb and fastboot -- that's the advantage of having a Google phone.
For OTA updates, I'm pretty sure it will not work because OTA update requires stock recovery but rooting requires you to flash a custom recovery.
suksit said:
Yes you can use Odin with Nexus S, but consider it the last resort because normally you can do everything via adb and fastboot -- that's the advantage of having a Google phone.
For OTA updates, I'm pretty sure it will not work because OTA update requires stock recovery but rooting requires you to flash a custom recovery.
Click to expand...
Click to collapse
thanks for that reply it explained everything can you just tell me if flashing a custom recovery change my baseband or kernel that's all i need to know now
@anishs no
Sent from my Nexus S using XDA App
thanks to everyone for helping a noob with a nexus s
Hey guys I have been reading through this forum and I think I get most stuff now. There is only one thing confusing me, when talking about bootloaders and unlocking them, everyone says its irreversible and you loose warranty and drm keys.
My question is, why? Can't we just backup it with CWM or similar? Can't we just make a backup when we receive the device from factory and then if we need warranty for something can't we just flash back and put everything original, including bootloader and stuff?
Thank you
shamelessly dumping to first page
Your warranty is never truly lost. Just remember, if they can't turn it on, they don't know it was rooted.
lowandbehold said:
Your warranty is never truly lost. Just remember, if they can't turn it on, they don't know it was rooted.
Click to expand...
Click to collapse
thank you, but my curiosity extends to the technical level, not just in the practical sense
gtype said:
thank you, but my curiosity extends to the technical level, not just in the practical sense
Click to expand...
Click to collapse
Ok, well the technical answer is once you unlock it, it can't be locked. Recovery does not back up your bootloader. A better alternative is flashing a different bootloader. There are some phones where the engineering bootloader used by OEM devs is available, so you can always go back to the stock bootloader.
EDIT: Actually now that I think about it, you can make a backup. I honestly have not dealt much with Samsung phones, so I am not sure if it is the same. But when you first root an HTC you take an initial image, which you store on your SD card or computer and you use it to unroot. When you unroot using that method it sets your bootloader back to factory. Also when you use a factory image, such as a PDxx.img and flash that through hboot, it gives you a stock bootloader as well.
lowandbehold said:
Ok, well the technical answer is once you unlock it, it can't be locked. Recovery does not back up your bootloader. A better alternative is flashing a different bootloader. There are some phones where the engineering bootloader used by OEM devs is available, so you can always go back to the stock bootloader.
Click to expand...
Click to collapse
isnt the bootloader in the boot partition?
gtype said:
isnt the bootloader in the boot partition?
Click to expand...
Click to collapse
Yes, the bootloader and the kernel are in the boot partition.
lowandbehold said:
Yes, the bootloader and the kernel are in the boot partition.
Click to expand...
Click to collapse
sorry if I'm being thick, but since the bootloader is part of the partition, what stops me from backuping all the partitions, unlock the bootloader, and then after some time flash the original dumped stuff?
gtype said:
sorry if I'm being thick, but since the bootloader is part of the partition, what stops me from backuping all the partitions, unlock the bootloader, and then after some time flash the original dumped stuff?
Click to expand...
Click to collapse
Hey, you can try it. That is a very sensitive partition to mess with. The main issue is, how many times have you flashed a ROM and for some reason it just doesnt flash right and you get a boot loop? Easy fix, wipe everything, reflash, good to go. If you flash the bootloader and reboot your phone and something went wrong with the flash...you have a hard brick. No coming back, period. So, experiment wisely. It is the same thing with flashing through terminal. If you get 1 space, 1 character wrong in the command line...hard brick.
actually I don't own a smartphone yet, but I'm going to soon. Since I'm well versed in Linux I was checking out the Android OS in general and that question popped up in my mind and I just couldn't find any info about it. Does that make kernel flashing dangerous too, since it's in the same partition as the bootloader?
gtype said:
actually I don't own a smartphone yet, but I'm going to soon. Since I'm well versed in Linux I was checking out the Android OS in general and that question popped up in my mind and I just couldn't find any info about it. Does that make kernel flashing dangerous too, since it's in the same partition as the bootloader?
Click to expand...
Click to collapse
No, kernel flashing is fine. A bad flash just ends in a bootloop, no big deal. Bootloaders and radios..those are the ones you have to be careful with.
lowandbehold said:
No, kernel flashing is fine. A bad flash just ends in a bootloop, no big deal. Bootloaders and radios..those are the ones you have to be careful with.
Click to expand...
Click to collapse
Alright, thank you very much.
Actually, it just struck me, why is it dangerous if it doesn't flash properly, the recovery partition is separate and you can make the device boot from it right?
gtype said:
Alright, thank you very much.
Actually, it just struck me, why is it dangerous if it doesn't flash properly, the recovery partition is separate and you can make the device boot from it right?
Click to expand...
Click to collapse
I am assuming you could if you have one backed up. But when a bootloader doesn't flash right and you get a brick, you can't even get into recovery. Most of the time the phone won't even power on. Because booting into recovery requires the bootloader.
lowandbehold said:
I am assuming you could if you have one backed up. But when a bootloader doesn't flash right and you get a brick, you can't even get into recovery. Most of the time the phone won't even power on. Because booting into recovery requires the bootloader.
Click to expand...
Click to collapse
I see. Thanks a lot for your time
gtype said:
I see. Thanks a lot for your time
Click to expand...
Click to collapse
Hey, no problem. Just sitting here on the front end of my 12 hour shift..nothing better to do!
lowandbehold said:
Hey, no problem. Just sitting here on the front end of my 12 hour shift..nothing better to do!
Click to expand...
Click to collapse
New question, if you are still around. What exactly is a locked bootloader? Is it just a bool in the bootloader code? Where are the DRM keys and why are they lost?
gtype said:
New question, if you are still around. What exactly is a locked bootloader? Is it just a bool in the bootloader code? Where are the DRM keys and why are they lost?
Click to expand...
Click to collapse
It depends on the device. A bootloader is usually unlocked by an unlock.bin for that device. I'm not an expert on bootloaders though...
dmeadows013 said:
It depends on the device. A bootloader is usually unlocked by an unlock.bin for that device. I'm not an expert on bootloaders though...
Click to expand...
Click to collapse
I was talking physically, like are the keys in the bootloader, is S_OFF etc bool variables etc. I guess I'll try to dig it up somewhere. thanks
gtype said:
New question, if you are still around. What exactly is a locked bootloader? Is it just a bool in the bootloader code? Where are the DRM keys and why are they lost?
Click to expand...
Click to collapse
A locked bootloader doesn't allow you to change key parts of the system such as a kernel. So you can still root your phone, but all of the custom ROM's have to use the stock kernel. So if you are on a gingerbread stock ROM, you can't run Ice cream sandwich because you can't change kernels. The DRM keys are what is used to encrypt the bootloader, so if you unlock the bootloader the keys are lost.
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
killboredom said:
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
Click to expand...
Click to collapse
I think that's right. It's ridiculous that by locking things down and preventing us from unlocking bootloader Verizon actually causes bricks of this nature to occur. If you had an unlocked bootloader you'd be 100% fine right now.
Sent from my Nexus 7
There is a way. I posted in previous forum.
Use fastboot
Fastboot wipe cache
Fastboot wipe user data
Try this if not pm me and I will help you out one on one
That should fix your issue
Sent from my XT1080 using xda app-developers app
phositadc said:
I think that's right. It's ridiculous that by locking things down and preventing us from unlocking bootloader Verizon actually causes bricks of this nature to occur. If you had an unlocked bootloader you'd be 100% fine right now.
Sent from my Nexus 7
Click to expand...
Click to collapse
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
codito said:
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
Click to expand...
Click to collapse
Ha...well there is that But what fun would that be?
The sad part is that the manufacturers could care less about giving us an unlocked bootloader. Android is a great ecosystem to play with and learn with and improve with. It's the carriers that are so paranoid about taking any tiny dent in their enormous profits that want to keep us locked out. So shame on them.
But, to be fair, I know the risks of the world we live in and this is my first brick in four Android phones, so I'm fine with it.
codito said:
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
Click to expand...
Click to collapse
My point was merely that it's somewhat ironic that, by trying to prevent bricks by locking bootloaders, Verizon actually causes some bricks that would be avoided with an unlocked bootloader.
Not saying anything about whether what he was doing is right or wrong, or whether Verizon prevents more bricks than it causes.
Sent from my Nexus 7
Edit: but you've got to wonder. Are you more likely to brick using one of these crazy complicated methods we have to use to get around Verizon security? Or using fastboot OEM unlock + flash superuser. I bet per hundred rooted phones, less Nexus's (and other unlockable phones) are bricked than phones that are tightly locked down. Pure speculation of course.
killboredom said:
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
Click to expand...
Click to collapse
It sounds like you're actually stuck partially on JB, partially on KK, hence why you're bootlooping. I had a very similar issue when I tried to install the KK update through update.zip .......... after a couple hours, I finally got it back up and running.
My method - use the Method 2 Manual flash steps I posted in Dev section here - http://forum.xda-developers.com/showthread.php?t=2580060
Let me know if it works. I had problems at first, but that should cover it. Getting system to flash was actually the hardest part
I just got the OTA for Kit Kat. I know it's early still, but has anyone found a root method yet?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Serial_Noob said:
I just got the OTA for Kit Kat. I know it's early still, but has anyone found a root method yet?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Only if your bootloader is unlocked will you get root on KK.
There is no known exploit to gain root on locked bootloader devices with KK. KK patched a lot of security holes and exploits, including the Sqlite tethering hack.
I wouldn't hold my breath on getting root and there is no way to preserve root across the OTA. The last root exploit found (the safe patch or whatever it was called) will break the OTA update, requiring you to flash back to a stock image of whatever version you were running at the time (9.18 or 9.30).
Could you please give a link for root package for unlocked BL? I've got such a lucky phone
uh, search for SuperSu pretty sure youll find it here....
stanislavshulgin said:
Could you please give a link for root package for unlocked BL? I've got such a lucky phone
Click to expand...
Click to collapse
It's always available from the SuperSU thread located here: http://forum.xda-developers.com/showpost.php?p=23427715&postcount=1
But, here is the direct link to the download (which is in the thread I mentioned above): http://download.chainfire.eu/supersu
Oh god, I'm an idiot -______-'''
Thanks guys!
iBolski said:
Only if your bootloader is unlocked will you get root on KK.
There is no known exploit to gain root on locked bootloader devices with KK. KK patched a lot of security holes and exploits, including the Sqlite tethering hack.
I wouldn't hold my breath on getting root and there is no way to preserve root across the OTA. The last root exploit found (the safe patch or whatever it was called) will break the OTA update, requiring you to flash back to a stock image of whatever version you were running at the time (9.18 or 9.30).
Click to expand...
Click to collapse
Until there is root, I won't take the update. If that means 4.1.2 forever, so be it.
The only thing that grinds my @$$ is that I bought the phone a year into its life and took one too many OTAs without unlocking the bootloader first. And from what I understand, there's no turning back.
I do have a Motorola factory cable, though. It saved me a couple of times with my Droid X2. I haven't seen anything about using it on the RAZR HD -- do you know if it's usable for this phone?
Serial_Noob said:
I do have a Motorola factory cable, though. It saved me a couple of times with my Droid X2. I haven't seen anything about using it on the RAZR HD -- do you know if it's usable for this phone?
Click to expand...
Click to collapse
I suggest it should work too
Serial_Noob said:
Until there is root, I won't take the update. If that means 4.1.2 forever, so be it.
The only thing that grinds my @$$ is that I bought the phone a year into its life and took one too many OTAs without unlocking the bootloader first. And from what I understand, there's no turning back.
I do have a Motorola factory cable, though. It saved me a couple of times with my Droid X2. I haven't seen anything about using it on the RAZR HD -- do you know if it's usable for this phone?
Click to expand...
Click to collapse
i have a factory adapter, it does work on this phone.
im curious as to why you asked about it?
it will not let you downgrade to unlock the bootloader if thats where you were going with this.
bweN diorD said:
i have a factory adapter, it does work on this phone.
im curious as to why you asked about it?
it will not let you downgrade to unlock the bootloader if thats where you were going with this.
Click to expand...
Click to collapse
Yeah, unfortunately that's exactly where I was going. I kind of figured if it would someone would have mentioned it by now. But I've never seen it mentioned in the RAZR forums and had to wonder.
So i got the notif to update to the latest OTA today and when i tried to i got an error....
i checked superSU and it said that my phone was no longer rooted... and now when i try to do over the rooting process, i.e unlock the bootloader and root... its not working, im using the oneplus one toolbox version 3, i had originally used 2....
when i click unlock bootloader, all the phone does is reboot... which is strange seeing as i know it basicall factory resets the phone after unlocking... anyone have this problem? need help
If you were rooted before, you don't need to re-unlock your bootloader as its already unlocked.
Just go into recovery and flash SuperSU.
Stop using toolkits. Its pretty obvious that you aren't aware of what you're doing and you're just pressing buttons hoping stuff will work.
zephiK said:
If you were rooted before, you don't need to re-unlock your bootloader as its already unlocked.
Just go into recovery and flash SuperSU.
Stop using toolkits. Its pretty obvious that you aren't aware of what you're doing and you're just pressing buttons hoping stuff will work.
Click to expand...
Click to collapse
um, no, you couldnt be farther from the truth.. as i have rooted devices already manually.
Also, please disregard this post, i switched the usb port i was using and everything is working now, my front port is faulty...apparently.
JohanXDash said:
um, no, you couldnt be farther from the truth.. as i have rooted devices already manually.
Also, please disregard this post, i switched the usb port i was using and everything is working now, my front port is faulty...apparently.
Click to expand...
Click to collapse
If you were already previously rooted, your phone doesn't magically relock its bootloader. The only way for that to happen is if you manually relocked the bootloader which is bad practice if you're relocking your bootloader when its already unlocked. It serves no purpose to relock your bootloader if you did relock it, just leave it unlocked.
You don't have to go through the whole rooting process if your bootloader was already unlocked. All you had to do was flash SuperSU in recovery to reobtain root.
And don't use toolkits, you honestly don't learn anything at all but to click a button and hope it works. Because there is a chance that it will not work and then consequences will be set in place and then you'll have to rely on users who manually input commands on their phone via fastboot because you're not sure how to do it.