Could someone help me verify if I have an unsigned atrix? Is there any advantage to any of you dev guys? Thanks
I feel like I might have one as welll, I have a load of options in the bootloader including bypasses
Sent from my MB860 using XDA App
hankpunk said:
Could someone help me verify if I have an unsigned atrix? Is there any advantage to any of you dev guys? Thanks
Click to expand...
Click to collapse
sgtmedeiros said:
I feel like I might have one as welll, I have a load of options in the bootloader including bypasses
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=13570564&postcount=510
But, I wonder why you suspect that anyway. If you bought it used from an AT&T employee who says he had it from before the phone came out, then you might want to test it. If you bought it new, I would not count on it.
To the second poster, if the "bootloader" you are talking about is the fastboot menu, you're not talking about anything special there.
We all have those options to bypass the baseband processor (BP) so I'm not sure if they mean so much. You can paste the output of the top windows when you RSD.
However, if you've flashed a signed bootloader (from any of the signed .sbfs available... ie, any of them or from any OTA) you will have essentially "un-deved" your device. The bootloader will refuse to flash un-signed .sbfs from now on. So a dev phone which has been flashed with consumer/OTA updates is no longer a dev phone.
If you haven't, the top panel in RSD could be informative, or the contents of your boot and recovery partitions (mmcblk0p11 and mmcblk0p10) You should dd them and paste links to them or send to someone for checking whether they are signed. There are dumps of other dev devices we can check against.. If confirmed, a dev device is probably worth something to someone. You can also test by hex-editing a few bytes in your recovery partition (change some 0xFF to 0x00 in junk regions) and then you will get "failure to boot 2" when you go to android recovery. That's because your bootloader checked the hash after the last signature in the recovery partition and said: "no way, the hash of the data does not match what is expected"
lurchbyrep said:
http://forum.xda-developers.com/showpost.php?p=13570564&postcount=510
Click to expand...
Click to collapse
Neat! I had assumed because I got "secure: no" when I do "fastboot getvar all" that it wasn't meaningful. But "fastboot getvar secure" says "secure: yes" so uh, thanks a lot for the consistency, fastboot. However, maybe this means you could still flash your bootloader back to an unsigned one (had you accidentally 'signed' your dev device with a bootloader that checks signatures) using fastboot (which seems fairly useless on our consumer devices.) That would be great, so perhaps what I just wrote in the previous post isn't true (that unsigned->signed is irreversible.)
lurchbyrep said:
But, I wonder why you suspect that anyway. If you bought it used from an AT&T employee who says he had it from before the phone came out, then you might want to test it. If you bought it new, I would not count on it.
Click to expand...
Click to collapse
Agreed. Unless you bought it on e-bay, you should probably already know from where you got your phone (AT&T, Nvidia, Motorola?) why it's a dev phone... and if you didn't get it in a strange way, it's almost certainly locked like the rest of ours.
eval- said:
We all have those options to bypass the baseband processor (BP) so I'm not sure if they mean so much. You can paste the output of the top windows when you RSD.
However, if you've flashed a signed bootloader (from any of the signed .sbfs available... ie, any of them or from any OTA) you will have essentially "un-deved" your device. The bootloader will refuse to flash un-signed .sbfs from now on. So a dev phone which has been flashed with consumer/OTA updates is no longer a dev phone.
If you haven't, the top panel in RSD could be informative, or the contents of your boot and recovery partitions (mmcblk0p11 and mmcblk0p10) You should dd them and paste links to them or send to someone for checking whether they are signed. There are dumps of other dev devices we can check against.. If confirmed, a dev device is probably worth something to someone. You can also test by hex-editing a few bytes in your recovery partition (change some 0xFF to 0x00 in junk regions) and then you will get "failure to boot 2" when you go to android recovery. That's because your bootloader checked the hash after the last signature in the recovery partition and said: "no way, the hash of the data does not match what is expected"
Click to expand...
Click to collapse
eval-, I'm pretty sure kholk said flashing his dev Atrix did not lock his bootloader. Recently, however, he said he purposely signed the SBK in order to test a possible method of unlock. I could be remembering wrong, but I'm sure PAuly has it all in his irc log.
I was also on irc at the time. He said you can lock / unlock with the SBK and the dev SBK was all zeros with a one at the end.
Sent from my MB860 using XDA App
jysue said:
I was also on irc at the time. He said you can lock / unlock with the SBK and the dev SBK was all zeros with a one at the end.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Sure, but my point is that I was under the impression that flashing a dev Atrix does not automatically lock the bootloader. Is this wrong, eval-?
About the Fastboot and bypass options, guys... jesus... we've been over this.
I seriously doubt anyone here has a magically unlocked bootloader for a magical random reason. Not trying to be an ass, but it's aggravating because it's already an irritating enough issue.
If anyone does have one and it somehow benefits the community, spank my ass and call me Susan.
Moved to proper forum
lurchbyrep said:
Sure, but my point is that I was under the impression that flashing a dev Atrix does not automatically lock the bootloader. Is this wrong, eval-?
Click to expand...
Click to collapse
I don't know. My understanding is the bootloader from signed .sbf files checks the signatures on boot/recovery partitions (so, no new kernels, no easy customization), and also doesn't play nice when you want to update back to an unsigned system VIA RSD. Perhaps on a dev device you can then just overwrite the bootloader back to an unsigned one via nvflash or fastboot, instead of RSD. Don't know if the bootloader determines the 'dev' or consumer status of the device before checking signatures on partitions. Also never had a device I can do much with nvflash/fastboot on, so my understanding is probably incomplete
Related
We can no longer unlock your bootloader with codes. Please do not ask me or ash for bootloader unlock codes. We can not help you.
This thread is now here for historical purposes representing times when people were free to do what they wanted with their devices. Fsck yourself with a rake, Verizon.
The bootloader has been unlocked. Let's get our freaking root on.
Disclaimer: Read through these instructions in their entirety. If these don't make sense to you, you do not need to be rooting your phone. Nobody here has the time required to teach you how to use cmd in Windows. We will not baby step you through how to use ClockworkMod Recovery. Root is not a mythical land with fairies and unicorns where nothing ever goes bad. If you don't know how to properly install a driver in Windows, you probably don't need an Android device to begin with, let alone a rooted one.
These instructions are intentionally left vague. Do your research on these terms. Understand what you are doing before you do it.
tldr: if you fsck your phone up, it's on you and only you.
Easy Way (YRMV!)
This is by far the easiest method. You will have to read between the lines here. I will not detail all the steps. Please record your experiences in this thread and let me know how it all goes! We're all still learning. This is basically copied from Bin4ry's CWMR Thread so thanks go to him! The easy steps below assume a lot of basic knowledge steps. Like unlocking the bootloader. If you're unsure of what to do, you probably shouldn't be doing it.
Download the CWM recovery from multiupload
Boot off of that file (DO NOT FLASH): fastboot boot recoveryPLAY.img
Copy this to your memory card and flash it with the booted recovery
Reboot and test root
Second Method: Advanced User Instructions
Unlock your bootloader. Check out Ash's thread: thread
Download Doom's all in one kernel from here
Use fastboot to "hot boot" the kernel: fastboot boot boot.img
Your phone may or may not boot. It doesn't matter. Let it be for a while, then power it off.
Doom's kernel will have rooted your stock system.
If You're On A Mac...
Or maybe just need some general help with some more detailed insturctions than are labeled here, check out the awesome post that Cubsfan3493 made for everyone. He's even got a downloadable PDF with pictures. Go give him some thanks at his post!
Is the R800x running 2.3.2 or 2.3.3. There's reports that Gingerbreak and alternatives are no longer working in 2.3.3.
It's running 2.3.2 right now. OTA updates say its up to date. I'm trying to figure out if I'm just having a generic issue with the breaks (like memory cards for example) or if Verizon maybe patched the exploit in their 2.3.2 build.
I have tried pretty much everything as well, I really hope some dev's start to pop their noises in here as I am a bit sad about the activity so far
I've been trying to root mine as well. The discussion I've been having is in this thread
http://forum.xda-developers.com/showthread.php?t=1097856
I'll keep an eye on both threads, but I have had no luck so far.
I'm guessing it's something they fixed in the final Verizon build before release. Curious... What's your build #? Mine is 3.0.A.2.184.
Sent from my R800a using XDA App
axiomjunglist said:
I'm guessing it's something they fixed in the final Verizon build before release. Curious... What's your build #? Mine is 3.0.A.2.184.
Click to expand...
Click to collapse
Yes i think verizon fixed the exploit gingerbreak uses before releasing the handset in the usa. When i was on build number 3.0.A.2.184 (uk xplay R800i) it rooted in like 30 seconds.
But in the new update 3.0.1.A.0.145 the exploit has been fixed. So all devices around the world have been left unrootable (for now ) the devs will figure away out.
I think the uk version 2.3.3 build 3.0.1.A.0.145 has been rooted (for unlocked bootladers) http://forum.xda-developers.com/showthread.php?t=1098736 So if your bootloader is unlocked soon it maybe possible. If its locked your stuck waiting with the rest of us for a rooting method on locked devices.
I saw you updated from another post, did you lose root access after the update?
Sent from my R800a using XDA App
axiomjunglist said:
I'm guessing it's something they fixed in the final Verizon build before release. Curious... What's your build #? Mine is 3.0.A.2.184.
Click to expand...
Click to collapse
build number - 3.0.E.2.89
A shame they didn't let us all have unlocked bootloaders.
axiomjunglist said:
I saw you updated from another post, did you lose root access after the update?
Click to expand...
Click to collapse
Yes i did. But the fixes added in the update are worth loosing root, for the time being . Being unable to root only applies to people with a locked bootloader. But im guessing devs from the arc and play forum are possibly looking for ways to root with a locked bootloader
Yeah I have the option to unlock my bootloader but don't want to just yet. I'll hold off on the update until a new version of gingerbreak arrives
Sent from my R800a using XDA App
For the record, it seems like the bootloader is unlockable on the R800x. Fastboot is totally accessible by the same means and the oem unlock command is recognized, the phone is responsive, it's just looking for a key, the same as the GSM counterpart. The only difference is that the Verizon version doesn't have an IMEI (or does it.... since it does have a sim card slot....), just an ESN. So obviously you can't obtain an unlock key from this number.
Mills00013 said:
For the record, it seems like the bootloader is unlockable on the R800x. Fastboot is totally accessible by the same means and the oem unlock command is recognized, the phone is responsive, it's just looking for a key, the same as the GSM counterpart. The only difference is that the Verizon version doesn't have an IMEI (or does it.... since it does have a sim card slot....), just an ESN. So obviously you can't obtain an unlock key from this number.
Click to expand...
Click to collapse
Wonder if you pop a pre-paid SIM in the slot (or try a friend's AT&T/T-Mobile SIM) and disabled the CDMA radio if you could get an IMEI to pop up on the keypad using *#06#. Might work? I have no clue... and you'd still have to send it to SE and hope they clear it.
I have a few SIMs here that I could try. Ill see what I come up with in a little bit. My gut is telling me that Verizon probably has the SIM slot firmware disabled. Thats only because they havn't officially mentioned it anywhere. In fact, the slot itself is actually hidden by a piece of plastic that you have to remove. One wouldnt have any idea it was there unless you were looking for it and even then you feel like you're breaking your phone to access it.
I also considered hooking it up to QPST to see if it would grab some serial numbers out of the device. Can anyone confirm if this is a qualcomm chip inside the phone?
I just tried a T-mo and an AT&T SIM, neither give me any sort of insertion notification or acknowledgement that they are present. So I'd say the slot is firmware disabled. But it should still have an IMEI, right? That would be programmed by Qualcomm out of the factory before Ericsson would have even installed it. Or am I taking crazy pills?
do a ADB devices on your phone it gives what I think is a IMEI number and if you put the first 14 in on sony's site it gives you a unlock code, i am to much of a wussy to try it tho lol.
b00sted said:
do a ADB devices on your phone it gives what I think is a IMEI number and if you put the first 14 in on sony's site it gives you a unlock code, i am to much of a wussy to try it tho lol.
Click to expand...
Click to collapse
more than willing to be take a chance on mine. i ran adb devices. got code. first 14 digits (minus the b) sent to sony and got an unlock code.
next steps i'm confused on. how do i boot to fastboot mode? i tried holding menu key and inserting usb... didnt' seem to do anything...
ran
9. In the cmd windows type in fastboot.exe -i 0x0fce getvar version
and it did nothing just sat there (waiting for device).
Is there an indication you are in fastboot mode? should 0fce be different on our phones? any ideas?
EDIT: its hold search, not menu, got it to fastboot mode and got response.. trying now. will post results
EDIT 2 : and fail.
ace518 said:
more than willing to be take a chance on mine. i ran adb devices. got code. first 14 digits (minus the b) sent to sony and got an unlock code.
next steps i'm confused on. how do i boot to fastboot mode? i tried holding menu key and inserting usb... didnt' seem to do anything...
ran
9. In the cmd windows type in fastboot.exe -i 0x0fce getvar version
and it did nothing just sat there (waiting for device).
Is there an indication you are in fastboot mode? should 0fce be different on our phones? any ideas?
EDIT: its hold search, not menu, got it to fastboot mode and got response.. trying now. will post results
EDIT 2 : and fail.
Click to expand...
Click to collapse
ya I just tried too and fail :/ #sadpanda
Neither the adb devices nor the fastboot devices codes have anything to do with the IMEI number.
Enviado desde mi R800i usando Tapatalk
I am willing to donate towards the first person that can get root and CWM on this!
So guys I really wanna unlock the bootloader and flash some roms but this is my third atrix. Im using the 14 day grace period very very graciously. Anyways first atrix kept locking up- exchanged. Second one I tried to unlock it with pudding. Did the rsd thing with the. Sbf file and I was doing it. Then toward the end it failed. Complete brick- exchanged.
Anyways is there something else I should do, possibly a different route? Im using an AT&T atrix. Thanks.
Wait for official release and get it officially unlocked?
Sent from my MB860 using XDA Premium App
tsouza said:
Wait for official release and get it officially unlocked?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I can wait for the release, but are they unlocking it with it. For sure?
Well, IMO better hope for it than risk another brick...
Sent from my MB860 using XDA Premium App
tsouza said:
Well, IMO better hope for it than risk another brick...
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
True. Very true.
magicriggs said:
So guys I really wanna unlock the bootloader and flash some roms but this is my third atrix. Im using the 14 day grace period very very graciously. Anyways first atrix kept locking up- exchanged. Second one I tried to unlock it with pudding. Did the rsd thing with the. Sbf file and I was doing it. Then toward the end it failed. Complete brick- exchanged.
Anyways is there something else I should do, possibly a different route? Im using an AT&T atrix. Thanks.
Click to expand...
Click to collapse
I think you might have returned the first 2 prematurely.
1st one probably could have factory reset or flashed a new sbf
2nd one was probably a fixable soft brick.
So I'd say you're safe, but up to you as there's always a risk.
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/showthread.php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/showthread.php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Sent from my MB860 using Tapatalk
magicriggs said:
I can wait for the release, but are they unlocking it with it. For sure?
Click to expand...
Click to collapse
not sure. i got a leaked 4.5.91 build, it's not unlocked (although early beta does). you still have to flash the pudding img yourself.
delect this post
The returns were genuine. I did a factory reset on the first one and it still kept locking up, on the wake up. Had to pull battery out to turn back on. Multiple times. Second one was a complete brick. I couldn't get into rsd, wouldn't turn on and computer didn't recognize it in any mode. Im pretty familiar with rsd, used it with OG and X but this one got me walking om egg shells.
magicriggs said:
The returns were genuine. I did a factory reset on the first one and it still kept locking up, on the wake up. Had to pull battery out to turn back on. Multiple times. Second one was a complete brick. I couldn't get into rsd, wouldn't turn on and computer didn't recognize it in any mode. Im pretty familiar with rsd, used it with OG and X but this one got me walking om egg shells.
Click to expand...
Click to collapse
hmm you are very unlucky then. You're the only one to hard brick from pudding. Probably advise you not to do anything with your phone.
Jnewell05 said:
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
Click to expand...
Click to collapse
im on build number 4_1.8.3 and i check for updates and it says my device is up to date. any
ideas?
magicriggs said:
im on build number 4_1.8.3 and i check for updates and it says my device is up to date. any
ideas?
Click to expand...
Click to collapse
4.1.83 is a great point to unlock the bootloader. DO NOT install the 4.5.91 OTA udpate, too risky to hard brick if you flashed an sbf. Of course, you don't have to sbf back anymore, but I would steer way clear of that when there are perfectly good options available. Only use customized ones like Kenneth's or the CherryBlur ROM. More will start flowing soon.
So what your advising is not to even unlock it. All I really want is volume wake.
magicriggs said:
So what your advising is not to even unlock it. All I really want is volume wake.
Click to expand...
Click to collapse
That's the exact opposite of what I'm advising. I knew I was taking some level of risk when I unlocked, but it's a risk well worth taking. Very, very low failure rate. Recoverable. But I can't accept the risk for your phone.
OSNPA said:
That's the exact opposite of what I'm advising. I knew I was taking some level of risk when I unlocked, but it's a risk well worth taking. Very, very low failure rate. Recoverable. But I can't accept the risk for your phone.
Click to expand...
Click to collapse
Oh gotcha. Thanks for the info.
Jnewell05 said:
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/showthread.php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/showthread.php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
i used update.zip ..did not flash back to 1.83...update.zip (blur 1.83 etc etc) was from leaked moto servers...i have new bootloader cause my andriod recovery is different...of course BL is locked....can i still unlock??
I recently unlocked my phone and rooted, I tried to flash CM7 Beta everything went well except when i rebooted it got stuck at the dual core screen. After trying everything, I decided to flash back to stock since cm7 wouldn't boot. My question is now that I flashed back to stock do I need to re-unlock my device? Does it stay unlocked? Can I just root it and retry CM7 again?
it happens to me too im reading on the forum but i dont think the bootloaders remain unlock cuz when u do the process it say that in the warnings
No one knows?
I read that once you unlocked you are unlocked forever because when you unlock it kills a fuse but you can cover up the 'unlocked' message so the average joe (such as ATT or Best Buy employee) wouldn't know you unlocked for insurance purposes.
I've also read posts though, like you, that state that it does re-lock the bootloader, so I am confused! I dont want to try flashing again though and end up with a hard-brick!
only installing official roms after unlocking will re-lock your phone or brick it. so if you can no longer see 'unlocked' when you turn your phone on then you will need to re-unlock the bootloader.
before installing any custom roms you need to do a backup. after that, do a full wipe/factory reset, wipe cache & wipe dalvik cache. then install your custom rom, reboot, wait anything up to 10 minutes, and voila!
theres no 'fuse' that needs blowing to unlock the phone, by the way. its all software based, and it can be re-locked providing that there is freely available software that allows you to do so!
Sent from my MB860 using XDA App
konna280 said:
only installing official roms after unlocking will re-lock your phone or brick it. so if you can no longer see 'unlocked' when you turn your phone on then you will need to re-unlock the bootloader.
theres no 'fuse' that needs blowing to unlock the phone, by the way. its all software based, and it can be re-locked providing that there is freely available software that allows you to do so!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Might want to do some reading and research. This has all been discussed previously in a couple of threads with links supporting a hardware unlock. Nobody has provided any proof of a software only unlock as of yet. Would appreciate if you posted where you got your information.
Cheers!
konna280 said:
only installing official roms after unlocking will re-lock your phone or brick it. so if you can no longer see 'unlocked' when you turn your phone on then you will need to re-unlock the bootloader.
before installing any custom roms you need to do a backup. after that, do a full wipe/factory reset, wipe cache & wipe dalvik cache. then install your custom rom, reboot, wait anything up to 10 minutes, and voila!
theres no 'fuse' that needs blowing to unlock the phone, by the way. its all software based, and it can be re-locked providing that there is freely available software that allows you to do so!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
+1
Can you provide a link that this is indeed a software lock?...
Sent from my GT-I9000 using xda premium
CaelanT said:
Might want to do some reading and research. This has all been discussed previously in a couple of threads with links supporting a hardware unlock. Nobody has provided any proof of a software only unlock as of yet. Would appreciate if you posted where you got your information.
Cheers!
Click to expand...
Click to collapse
Sorry, when i say software based i mean the use of software (using programs to flash files) to modify hardware. hardware based unlocking would mean having to modify hardware, such as soldering or other means of modifying/replacing components.
konna280 said:
Sorry, when i say software based i mean the use of software (using programs to flash files) to modify hardware. hardware based unlocking would mean having to modify hardware, such as soldering or other means of modifying/replacing components.
Click to expand...
Click to collapse
Soo..
You start a new thread about a topic that already has 17 threads dedicated to it.
You clearly dont understand how the current unlocking process works.
You claim to know of a new sw unlock, but even after being asked a few times will not elaborate or give a link or other info about it.
And your making up your own terms depending on what makes sence to you.
That settles it. You win the lolthread of the day, and were not laughing with you.
let's simplify:
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
This unlocks the bootloader through the use of software, does it not?
http://tinyurl.com/6gwycaq (explains what a bootloader is)
Plus... I didn't start the thread. You might need to do a little reading on that.
I've clearly unlocked, rooted, and installed a new ROM on my atrix (i initially used the gingerbreak app to root it, but decided to change the ROM at a later date, so unlocked it fully)
I don't claim to know of a sw unlock. I merely stated that software is used (RSD lite, drivers etc) to carry out the unlocking procedure.
Oh, by the way, it's "WE'RE not laughing with you" (not very nice ) and "YOU'RE making up your own terms". Little bit of research for you, if you want
konna280 said:
...
theres no 'fuse' that needs blowing to unlock the phone, by the way. its all software based, and it can be re-locked providing that there is freely available software that allows you to do so!
...
Click to expand...
Click to collapse
I think you're mistaken, it's a hardware lock. There has not been a software only solution shown. Since I have gone through the steps you described, and then re-unlocked my bootloader, the two processes were different (unlocking vs. re-unlocking), meaning that something changed when I unlocked the bootloader.
http://en.wikipedia.org/wiki/Antifuse#Antifuses_in_integrated_circuits
Trust me, this stuff is in all the ICs that you use.
Ok then, i apologize for not doing my research
I just ASS-U-MEd that if it can be re-locked then there is no modification taking place to the hardware itself (such as blown fuses - I'll admit though I only recently heard about eFuse's/Antifuse's as I've never dealt with them before, and therefore didn't know that the Atrix had them)
Thanks for the info.
lockety lock lock lock Lmfao
Im still laughing. No apostraphes needed.
WiredPirate said:
Im still laughing. No apostraphes needed.
Click to expand...
Click to collapse
nvm lol
10char
reunlocking is the same presedure which you did before. just you dont need to do the fastboot unlock oem.i did it and reunlock 2.3.4 telstra
This probably is not important, as I've already upgraded to CM9 and using it happily as a daily driver. I've been thinking about buying the Asus Transformer Infinity (TF700) and was reading about the tool to unlock the bootloader. I do understand that the "boot" area of the NVRAM is un-writable, and to allow this to be writable is to chance having that section of memory fubar, meaning no boot, meaning bricked device, etc.
Anyway, when I started coming up to speed on CM9 and reading most all of the pertinent threads, I don't recall reading anything on a locked bootloader for the NT. I rooted, prepared a bootable SD card with the .zip file, boot image and a few other files. Easy, but no unlock code or anything. So did that process unlock the bootloader and overwrite it with CM 9 files?
On a similar note, where does one find a memory map of the NT, showing where the bootloader and other partitions are? IE, I'd expect that the bootloader would take up the first block of memory, with other areas defined after that.
The bootloader is not locked (on the roms) Bauwks has unlocked it for us.
NookTabletsPower said:
The bootloader is not locked (on the roms) Bauwks has unlocked it for us.
Click to expand...
Click to collapse
If the original NT had a locked bootloader, then the process of flashing an new ROM was able to circumvent that?
georgia boy said:
I don't recall reading anything on a locked bootloader for the NT. .
Click to expand...
Click to collapse
Start reading!
http://forum.xda-developers.com/showthread.php?t=1480586
NookTabletsPower said:
The bootloader is not locked (on the roms) Bauwks has unlocked it for us.
Click to expand...
Click to collapse
The bootloader was never unlocked, as far as I'm aware. There was a flaw found that allowed the developers to bypass the bootloader and load custom images, including a new bootloader (cyanoboot).
Hello guys,
I've been trying to root this phone since i've bought it, problem is every option i read on the web doesnt work because phone's bootloader is locked, and all methods get to this point when u have to unlock ur phone bootloader but in order to do that u have to get in the phone bootloader wich is locked. So who the hell is giving advices like these i dont know. Problem is that i am motivated to still root it, nothing its impossible.
So i am asking, did anyone from EU, with the EU ROM (full of mallware) MIUI 8, managed to unlock its bootloader and then managed to root it ?! please lets discuss here the options that work and the options that didnt work so we can make it through and solve this problem, everything thats on web at this moment 27-11-2016 doesnt work on the False EU MIUI 8.
Thanks.
CatalinSava said:
Hello guys,
I've been trying to root this phone since i've bought it, problem is every option i read on the web doesnt work because phone's bootloader is locked, and all methods get to this point when u have to unlock ur phone bootloader but in order to do that u have to get in the phone bootloader wich is locked. So who the hell is giving advices like these i dont know. Problem is that i am motivated to still root it, nothing its impossible.
So i am asking you did anyone from EU, with the EU ROM (full of mallware) MIUI 8, managed to unlock its bootloader and then managed to root it ? please lets discuss here the options that work and the options that didnt work so we can make it through and solve this problem, everything thats on web at this moment 27-11-2016 doesnt work on the False EU MIUI 8.
Thanks.
Click to expand...
Click to collapse
Not posibble without unlocked bootloader. Even the pre-rooted China Developer rom needs phone with unlocked bootloader. Good luck with unlocking the bootloader.
EU ROM full of malware?!?! Where did you get that idea? Completely false.
Anyway as said, yes you do need to unlock bootloader. Impossible any other way, because the system has dm-verity (similar to HTC S-On) which prevents modification to /system. So if you can't modify system or boot partition then you can't put Superuser binaries anywhere. Unlocked bootloader allows to put Superuser on boot pertition.
Sent from my Redmi Note 4 using Tapatalk
CosmicDan said:
EU ROM full of malware?!?! Where did you get that idea? Completely false.
Anyway as said, yes you do need to unlock bootloader. Impossible any other way, because the system has dm-verity (similar to HTC S-On) which prevents modification to /system. So if you can't modify system or boot partition then you can't put Superuser binaries anywhere. Unlocked bootloader allows to put Superuser on boot pertition.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Can't we just flash a recovery-that can disable dm-verity using SP Flash and root the phone that way?
I am guessing not because no one has said it works
I'm getting rly impatient because I still havent got my bootloader unlock request approved yet lol
asusm930 said:
Can't we just flash a recovery-that can disable dm-verity using SP Flash and root the phone that way?
I am guessing not because no one has said it works
I'm getting rly impatient because I still havent got my bootloader unlock request approved yet lol
Click to expand...
Click to collapse
No because dm-verity is enabled/set in the kernel (ramdisk on boot partition), and if you modify the boot partition with a locked bootloader then it won't boot
Locked bootloader = prevents boot partition from being tampered with
dm-verity = set in boot partition, prevents system partition from being tampered with
So you simply need to unlock bootloader, there is just no other way to exploit the device (no possible attack vector). The device is very secure, like all Marshmallow devices.
So what is this false EU firmware you speak of? Obviously not the xiaomi.eu one because that requires unlocked bootloader.
You can flash global stable via SP Flash Tool, that's your best bet while waiting for bootloader unlock. If it's taking more than 1 week then you can contact official support or something via en.miui.com forum (its down at the moment for some reason).
CosmicDan said:
No because dm-verity is enabled/set in the kernel (ramdisk on boot partition), and if you modify the boot partition with a locked bootloader then it won't boot
Locked bootloader = prevents boot partition from being tampered with
dm-verity = set in boot partition, prevents system partition from being tampered with
So you simply need to unlock bootloader, there is just no other way to exploit the device (no possible attack vector). The device is very secure, like all Marshmallow devices.
So what is this false EU firmware you speak of? Obviously not the xiaomi.eu one because that requires unlocked bootloader.
You can flash global stable via SP Flash Tool, that's your best bet while waiting for bootloader unlock. If it's taking more than 1 week then you can contact official support or something via en.miui.com forum (its down at the moment for some reason).
Click to expand...
Click to collapse
have you atempted to see what actually happens when a bootloader is unlocked? Like what does the miunlocker do/flash on the phone?
---------- Post added at 05:20 AM ---------- Previous post was at 05:04 AM ----------
CosmicDan said:
No because dm-verity is enabled/set in the kernel (ramdisk on boot partition), and if you modify the boot partition with a locked bootloader then it won't boot
Locked bootloader = prevents boot partition from being tampered with
dm-verity = set in boot partition, prevents system partition from being tampered with
So you simply need to unlock bootloader, there is just no other way to exploit the device (no possible attack vector). The device is very secure, like all Marshmallow devices.
So what is this false EU firmware you speak of? Obviously not the xiaomi.eu one because that requires unlocked bootloader.
You can flash global stable via SP Flash Tool, that's your best bet while waiting for bootloader unlock. If it's taking more than 1 week then you can contact official support or something via en.miui.com forum (its down at the moment for some reason).
Click to expand...
Click to collapse
I'm gonna try to flash a twrp recovery using this guide http://en.miui.com/thread-371349-1-1.html
and replace the recovery file with TWRP. Will report if it works
Yea it doesnt work haha
CosmicDan said:
No because dm-verity is enabled/set in the kernel (ramdisk on boot partition), and if you modify the boot partition with a locked bootloader then it won't boot
Locked bootloader = prevents boot partition from being tampered with
dm-verity = set in boot partition, prevents system partition from being tampered with
So you simply need to unlock bootloader, there is just no other way to exploit the device (no possible attack vector). The device is very secure, like all Marshmallow devices.
So what is this false EU firmware you speak of? Obviously not the xiaomi.eu one because that requires unlocked bootloader.
You can flash global stable via SP Flash Tool, that's your best bet while waiting for bootloader unlock. If it's taking more than 1 week then you can contact official support or something via en.miui.com forum (its down at the moment for some reason).
Click to expand...
Click to collapse
Hey can you upload you miunlock tool folder here? Want to see if the miunlock tool downloaded anything that enabled the bootloader unlock
asusm930 said:
Hey can you upload you miunlock tool folder here? Want to see if the miunlock tool downloaded anything that enabled the bootloader unlock
Click to expand...
Click to collapse
You can download it for free, just search for MiFlash - it's not a secret tool or anything.
Attempting to see what actually happens...? Even if I had the skills to reverse engineer MediaTek security, I wouldn't do it.
You're trying to do such simple things to trick the system but you need to realize that this hardware has been verified by Google themselves as secure and safe enough for Android Pay and SafetyNet and such. It *can not* be easily cracked, accept it.
Replacing recovery.img with TWRP? Seriously? How dumb do you think these companies are? Sorry for being rude but you really are just being silly.
You are wasting your own time, and now mine too... Sorry but I'm going to unsubscribe now because these questions are just getting silly.
Sent from my Redmi Note 4 using Tapatalk
CosmicDan said:
You can download it for free, just search for MiFlash - it's not a secret tool or anything.
Attempting to see what actually happens...? Even if I had the skills to reverse engineer MediaTek security, I wouldn't do it.
You're trying to do such simple things to trick the system but you need to realize that this hardware has been verified by Google themselves as secure and safe enough for Android Pay and SafetyNet and such. It *can not* be easily cracked, accept it.
Replacing recovery.img with TWRP? Seriously? How dumb do you think these companies are? Sorry for being rude but you really are just being silly.
You are wasting your own time, and now mine too... Sorry but I'm going to unsubscribe now because these questions are just getting silly.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Man, I did not know that xiaomi actually put that much effort on making their mediatek phones actually google levels of secure.
Was always under the impression that they sorta skimped out on their mediatek lines (as they had before).
Now I'll just not try to unlock it unofficially lol
asusm930 said:
Man, I did not know that xiaomi actually put that much effort on making their mediatek phones actually google levels of secure.
Was always under the impression that they sorta skimped out on their mediatek lines (as they had before).
Now I'll just not try to unlock it unofficially lol
Click to expand...
Click to collapse
They had before sure, but in the recent year or so (since they started actually locking bootloaders) things changed - they want to target international market too.
Only reason the devices are not sold globally is because of some Mediatek patent/legal battle or something, not too sure (it's literally the only reason why they have snapdragon "pro" versions). But the device has a global firmware sold in Taiwan and some other places, and it is Google CTS certified (preinstalled with Google Play) and, since it's Marshmallow, requires all kinds of Google-approved security measures these days, which a lot of countries need legally too, so yeah.
Glad you understand. I read that if it takes too long to get unlock code, you should try/already be flashed on China dev ROM - so do that if you have not already.
Have you tried the unlocking link on this link? http://xiaomi-mi.com/redmi-note-4/