[How To] "lock" bootloader and revert to stock for warranty exchange - Atrix 4G General

I did this to my own Motorola Atrix 4g running rom: HB 2.3.4 oc 1.3ghz ext4 with the newest cwm installed
***i take no responsibility if this messes up your phone. I just did it to mine tonight before the replacement arives and wanted to help anyone else worried about being charged $399 for unlocking our bootloader
1) you need to download
//www35.megaupload.com/files/70b7d352e9514672c426f9dda58d3f6e/AUTOMATIC_UNLOCK_V4.2.zip
just incase something goes wrong you can unbrick it
2) RSD lite 5.3.1
//crackflashers.com/b16/Atrix/RSDLite5.3.1.msi
3) Newest moto update 2.3.4
//gitbrew.org/~dasmoover/android/atrix/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
boot into rsd mode and flash the official update using rsd lite, it will stop at 100% but never finish. once you see the at&t logo you can unplug if it takes forever and just wait for it to load.
after you will no longer have cwm or the "unlocked" text at boot, but all your data will still be on the phone so dont forget to wipe after.
***link #1 is only if you have problems booting after using rsd lite (i didnt need it)
EDIT_____-----____-
before doing anything, i did open up the .bat file named MAIN in the unzipped, "automatic unlock" folder. i tested out all the relevant options such as "restore to stock" and "repair boot error". I never actually used the software, but maybe just installing and initializing it was what it took to break through

steevquinn said:
I did this to my own Motorola Atrix 4g running rom: HB 2.3.4 oc 1.3ghz ext4 with the newest cwm installed
***i take no responsibility if this messes up your phone. I just did it to mine tonight before the replacement arives and wanted to help anyone else worried about being charged $399 for unlocking our bootloader
1) you need to download
//www35.megaupload.com/files/70b7d352e9514672c426f9dda58d3f6e/AUTOMATIC_UNLOCK_V4.2.zip
just incase something goes wrong you can unbrick it
2) RSD lite 5.3.1
//crackflashers.com/b16/Atrix/RSDLite5.3.1.msi
3) Newest moto update 2.3.4
//gitbrew.org/~dasmoover/android/atrix/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
boot into rsd mode and flash the official update using rsd lite, it will stop at 100% but never finish. once you see the at&t logo you can unplug if it takes forever and just wait for it to load.
after you will no longer have cwm or the "unlocked" text at boot, but all your data will still be on the phone so dont forget to wipe after.
***link #1 is only if you have problems booting after using rsd lite (i didnt need it)
Click to expand...
Click to collapse
And this didn't brick ur phone.
Sent from my MB860 using XDA App

anupash said:
And this didn't brick ur phone.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
amazingly, no

AFAIK the bootloader is still unlocked, it just doesn't show the "UNLOCKED" in the bootscreen anymore and reflashes/ overwrites CWM with the original ANDROID RECOVERY.

There are already several threads about this. You cannot relock the bootloader, only hide "unlocked" the boot logo screen.

But if I have already hard bricked my phone? what to do? it shows nothing ... the battery is charged

CaelanT said:
There are already several threads about this. You cannot relock the bootloader, only hide "unlocked" the boot logo screen.
Click to expand...
Click to collapse
^ This!
10char

I want to do a best buy warranty exchange (screen got lil bit scratch)....and would this method hide the "UNLOCKED" from the booting screen....is there any other method that you can hide the unlocked from the boot screen...reason being if they decide to just replace the screen and give it back the same phone...i dont wanna go through all the work....thank you...

CaelanT said:
There are already several threads about this. You cannot relock the bootloader, only hide "unlocked" the boot logo screen.
Click to expand...
Click to collapse
so...can u install custom roms: no. does it say unlocked at boot: no. so therefor it is unlocked for our purposes. The only way to unlock again is to rerun pudding. dont worry about what you've read elsewhere, im telling you this works.what other reason do u need to lock it for other than return. its people like you that cause misinformation. I did it, it works, now getting a new phone for free
---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------
rockbio said:
I want to do a best buy warranty exchange (screen got lil bit scratch)....and would this method hide the "UNLOCKED" from the booting screen....is there any other method that you can hide the unlocked from the boot screen...reason being if they decide to just replace the screen and give it back the same phone...i dont wanna go through all the work....thank you...
Click to expand...
Click to collapse
dude, it takes 7 minutes...a lot of work? lol just get it done and be safe. you can always go back to before, or fix a bricked device if needed
---------- Post added at 11:35 AM ---------- Previous post was at 11:29 AM ----------
TinyRK said:
AFAIK the bootloader is still unlocked, it just doesn't show the "UNLOCKED" in the bootscreen anymore and reflashes/ overwrites CWM with the original ANDROID RECOVERY.
Click to expand...
Click to collapse
its not unlocked. you have none of the features of an unlocked phone after this process. there is no such thing as a software fuse - theres always a way to go back. remember when they said it would be impossible to have a full bootloader unlock??? a couple weeks later, what do you know, "pudding" shows up. dont post on stuff you have never tried. like they say i'll believe it when i see it.

lol.
hey OP do this.
$ sudo ./moto-fastboot oem lock
... INFOOEM lock is not implemented
or fastboot oem lock
lol.
oh ya btw. http://forum.xda-developers.com/showthread.php?t=1211198
http://forum.xda-developers.com/showthread.php?t=1260127
http://forum.xda-developers.com/showthread.php?t=1254029
http://forum.xda-developers.com/showthread.php?t=1168255

steevquinn said:
so...can u install custom roms: no. does it say unlocked at boot: no. so therefor it is unlocked for our purposes. The only way to unlock again is to rerun pudding. dont worry about what you've read elsewhere, im telling you this works.what other reason do u need to lock it for other than return. its people like you that cause misinformation. I did it, it works, now getting a new phone for free
---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------
dude, it takes 7 minutes...a lot of work? lol just get it done and be safe. you can always go back to before, or fix a bricked device if needed
---------- Post added at 11:35 AM ---------- Previous post was at 11:29 AM ----------
its not unlocked. you have none of the features of an unlocked phone after this process. there is no such thing as a software fuse - theres always a way to go back. remember when they said it would be impossible to have a full bootloader unlock??? a couple weeks later, what do you know, "pudding" shows up. dont post on stuff you have never tried. like they say i'll believe it when i see it.
Click to expand...
Click to collapse
Unlocking the bootloader burns a software fuse in the bootloader. Same with the 4.9.51 update. That is what caused a lot of hard bricks. You cannot reflash the bootloader unless through nvflash with the SBK and a engineering cable, That would be the only way to patch the software fuses. This might remove the unlocked text at bootup and inhibit you from flashing roms, but the bootloader fuse is still blown, leaving proof of an unlocked bootloader.
Sent from my PG86100 using xda premium

And there's no way they can tell the phone has been unlocked when you return it? I'm thinking of exchanging my phone today. Currently unlocked and rooted.

archer75 said:
And there's no way they can tell the phone has been unlocked when you return it? I'm thinking of exchanging my phone today. Currently unlocked and rooted.
Click to expand...
Click to collapse
you can hide the "unlocked" but if they fastboot oem your phone lol then you're OOL.
I highly doubt they do though :T tbh..

darkamikaze said:
lol.
hey OP do this.
$ sudo ./moto-fastboot oem lock
... INFOOEM lock is not implemented
or fastboot oem lock
lol.
oh ya btw. http://forum.xda-developers.com/showthread.php?t=1211198
http://forum.xda-developers.com/showthread.php?t=1260127
http://forum.xda-developers.com/showthread.php?t=1254029
http://forum.xda-developers.com/showthread.php?t=1168255
Click to expand...
Click to collapse
why would i do that? i already sent my phone back, and there is absolutely no reason to relock a device for personal use. as soon as at&t recieves it, I imagine they turn it on, make sure it boots and no damage has been done. then they notify u that they recieved the phone and u are no longer the owner of it. Im sure as soon as the phone boots to the welcome screen without any weird things to indicate you have modified the phone, to at&t your phone is locked and unmodified. long before they test the phone for referbishing purposes, your account hold has been released and no one will ever know at one point their new, refurbished device was one a modded android with an unlocked bootloader, (Mod edit: Cease the abusive behavior)

armonwilson888 said:
Unlocking the bootloader burns a software fuse in the bootloader. Same with the 4.9.51 update. That is what caused a lot of hard bricks. You cannot reflash the bootloader unless through nvflash with the SBK and a engineering cable, That would be the only way to patch the software fuses. This might remove the unlocked text at bootup and inhibit you from flashing roms, but the bootloader fuse is still blown, leaving proof of an unlocked bootloader.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
No such thing as a software fuse, and if there were you could reverse it because it is software.
From IBM who developed eFuse technology:
" The patented technology, called "eFUSE," combines unique software algorithms and microscopic electrical fuses to produce chips that can regulate and adapt their own actions in response to changing conditions and system demands."
Nuff said!

steevquinn said:
why would i do that? i already sent my phone back, and there is absolutely no reason to relock a device for personal use. as soon as at&t recieves it, I imagine they turn it on, make sure it boots and no damage has been done. then they notify u that they recieved the phone and u are no longer the owner of it. afterwards, they flash all the memory and send it to be tested "thoroughly"(lol) for any internal damage before having the glass replaced and a new shell put on
Click to expand...
Click to collapse
that command will show you that your phone is still unlocked. that's why
anyway. believe us or not. but you cannot relock an unlocked device.

darkamikaze said:
that command will show you that your phone is still unlocked. that's why
anyway. believe us or not. but you cannot relock an unlocked device.
Click to expand...
Click to collapse
When you say 'device' are you only referring to Atrix?
Cus ya know.. you can relock the Xoom... just saying....
http://forum.xda-developers.com/showthread.php?t=967065
http://www.droid-life.com/2011/03/11/how-to-re-lock-the-motorola-xoom-bootloader-to-receive-updates/

CaelanT said:
No such thing as a software fuse, and if there were you could reverse it because it is software.
From IBM who developed eFuse technology:
" The patented technology, called "eFUSE," combines unique software algorithms and microscopic electrical fuses to produce chips that can regulate and adapt their own actions in response to changing conditions and system demands."
Nuff said!
Click to expand...
Click to collapse
so...your saying youve seen somewhere that says the atrix has IBMs "efuse" technology, or that it just exists to prove me wrong?
---------- Post added at 03:25 PM ---------- Previous post was at 03:21 PM ----------
TinyRK said:
WOW!
Real mature.
We just said, that the BL isn't locked. No reason to act like a kiddo and be offensive.
Grow up!
So letting others believe, that you're right is not correct, since the BL is not "re-locked."
I once did exactly what OP mentioned in the 1st post.
The UNLOCK disappeared, but the BOOTLOADER was still unlocked.
Click to expand...
Click to collapse
I said for our purposes (returning a defective unit) that the bootloader is effectivly locked. when in the process of returns does the step of running moto fast boot come into play? if that were so then the at&t techs would need to know the equivalent fastboot software for every single android phone.....HA! I doubt $9/hr at&T techs have any clue about this stuff unless they are into it on their own time

steevquinn said:
so...your saying youve seen somewhere that says the atrix has IBMs "efuse" technology, or that it just exists to prove me wrong?
---------- Post added at 03:25 PM ---------- Previous post was at 03:21 PM ----------
I said for our purposes (returning a defective unit) that the bootloader is effectivly locked. when in the process of returns does the step of running moto fast boot come into play? if that were so then the at&t techs would need to know the equivalent fastboot software for every single android phone.....HA! I doubt $9/hr at&T techs have any clue about this stuff unless they are into it on their own time
Click to expand...
Click to collapse
read
https://motorola-global-portal.cust...378/~/atrix---bootloader-mode-(efuse)-rooted*
Also, All Motorola would need to do is image the boot partition and hash that file and compare it to a hash of stock bootloader.. Two different hashes would be a dead give away that something was done to the bootloader.
Do they do that for every single return that comes in the door?? Most likely not. The probably reflash all their stuff back to it and leave it at that.
That being said.. you are arguing a failing point. The bootloader is still locked. Change the title of the thread to how to fool ATT if you have an unlocked bootloader and perhaps people will stop giving you **** about it.

steevquinn said:
so...your saying youve seen somewhere that says the atrix has IBMs "efuse" technology, or that it just exists to prove me wrong?
Click to expand...
Click to collapse
Motorola uses Efuse technology. Now I'm done with all these bootloader threads. Appears some of you will never listen, but offer no constructive arguments yourselves. I've done lots of homework myself. I'm not shooting from the hip. Believe what you wish!
Cya!
Assimilated via WinBorg 4G

Related

[Q] How can I LOCK my Bootloader?

Hey guys,
I want to unlock my bootloader so that I could try some of the awesome ROMs the devs have made/ported to the RAZR M.
I wanted to find out if I could RELOCK my bootloader in the case of needing to take it back to Verizon or Motorola in the case of it being damaged or something. I know how to unroot on the RAZR and how to do it all on my Nexus 7, just cant find hardly anything for this phone.
Thanks in advanced!!!
lukkypuggy said:
Hey guys,
I want to unlock my bootloader so that I could try some of the awesome ROMs the devs have made/ported to the RAZR M.
I wanted to find out if I could RELOCK my bootloader in the case of needing to take it back to Verizon or Motorola in the case of it being damaged or something. I know how to unroot on the RAZR and how to do it all on my Nexus 7, just cant find hardly anything for this phone.
Thanks in advanced!!!
Click to expand...
Click to collapse
Nope it's impossible to relock and once it's unlocked all your warranties are void
Sent from my XT907 using Tapatalk 2
Is this true for any device? Or just certain ones at this point?
Because I can Relock my Nexus 7 and my DROID Incredible just fine, in fact Verizon has accepted one of my former phones that was previously rooted and had the bootloader unlocked, then all was returned to stock of course.
lukkypuggy said:
Is this true for any device? Or just certain ones at this point?
Because I can Relock my Nexus 7 and my DROID Incredible just fine, in fact Verizon has accepted one of my former phones that was previously rooted and had the bootloader unlocked, then all was returned to stock of course.
Click to expand...
Click to collapse
It's specific to this line of devices so far (RAZR HD, RAZR MAXX HD, RAZR M, ATRIX HD). The unlock method (both on the dev. and consumer phones) invloves blowing a physical fuse in the phone which cannot be repaired. Google qfuse if you want to learn more.
Coronado is dead said:
It's specific to this line of devices so far (RAZR HD, RAZR MAXX HD, RAZR M, ATRIX HD). The unlock method (both on the dev. and consumer phones) invloves blowing a physical fuse in the phone which cannot be repaired. Google qfuse if you want to learn more.
Click to expand...
Click to collapse
thanks!
yes! it is!
lukkypuggy said:
thanks!
Click to expand...
Click to collapse
was unlocked now its fn locked and stuck in ap!!!
Yeah, I can confirm that Motorola released an update or something that relocked my previously unlocked boot loader (before anyone asks, yes it was definitely unlocked before ). Unfortunately the update failed on my phone and now I'm stuck in AP Fastboot with an error about "downgraded security version" and "update got_main version failed" errors.
So yeah, definitely possible for Motorola to relock the boot loader.
Attached is a picture of what it looks like now. I don't know of any SBF that would work to fix this.
phantomsniper773 said:
Yeah, I can confirm that Motorola released an update or something that relocked my previously unlocked boot loader (before anyone asks, yes it was definitely unlocked before ). Unfortunately the update failed on my phone and now I'm stuck in AP Fastboot with an error about "downgraded security version" and "update got_main version failed" errors.
So yeah, definitely possible for Motorola to relock the boot loader.
Attached is a picture of what it looks like now. I don't know of any SBF that would work to fix this.
Click to expand...
Click to collapse
Well, that picture speaks for itself, but I have to imagine that your situation is the exception, not the rule. It almost looks like somehting else went wrong with it. The qfuse is a physical fuse from what I have read, so maybe it got bridged, or the system isn't even making it to that check because of some other error.
Very strange indeed.
Coronado is dead said:
Well, that picture speaks for itself, but I have to imagine that your situation is the exception, not the rule. It almost looks like somehting else went wrong with it. The qfuse is a physical fuse from what I have read, so maybe it got bridged, or the system isn't even making it to that check because of some other error.
Very strange indeed.
Click to expand...
Click to collapse
Unless the tiny update did something with the bootloader to possibly IGNORE the qfuse state and simply keep it encrypted, blown qfuse or not. Maybe the final 'hurrah' from Verizon to try to kill off the Razr M development. Kinda reminds me of what they did with the Droid X and Droid 2 when they released the system version .621.. the ONLY thing the update did, was patch the current root methods and change the bootloader a tiny bit (version didn't even change) so it couldn't SBF to ANY previous build. TONS of Droid Xs and 2s were bricked until eventually a 621 SBF was released, and after forever, another root method.
EDIT: I found This thread which describes the same situation, but SBFing back to an earlier version seems to fix it. Apparently, the latest OTA REQUIRES a locked bootloader, unless flashed by other means (possibly TWRP or manual fastboot of img files?)
Skreelink said:
Unless the tiny update did something with the bootloader to possibly IGNORE the qfuse state and simply keep it encrypted, blown qfuse or not. Maybe the final 'hurrah' from Verizon to try to kill off the Razr M development. Kinda reminds me of what they did with the Droid X and Droid 2 when they released the system version .621.. the ONLY thing the update did, was patch the current root methods and change the bootloader a tiny bit (version didn't even change) so it couldn't SBF to ANY previous build. TONS of Droid Xs and 2s were bricked until eventually a 621 SBF was released, and after forever, another root method.
EDIT: I found This thread which describes the same situation, but SBFing back to an earlier version seems to fix it. Apparently, the latest OTA REQUIRES a locked bootloader, unless flashed by other means (possibly TWRP or manual fastboot of img files?)
Click to expand...
Click to collapse
Interesting theory. I personally had to RSD back to 4.1.2 (q66) to install since I had removed the Audio Level Warning apk (which just restores stock apps, kernel, boot image and boot animation but leaves data intact). I then let the update installer run on its own with the stock recovery and it remained unlocked.
Coronado is dead said:
Well, that picture speaks for itself, but I have to imagine that your situation is the exception, not the rule. It almost looks like somehting else went wrong with it. The qfuse is a physical fuse from what I have read, so maybe it got bridged, or the system isn't even making it to that check because of some other error.
Very strange indeed.
Click to expand...
Click to collapse
Yeah, I've only seen this occur on the few devices that had the update fail. I think it's striclty a software thing because it goes back to unlocked after the indviduals were able to recover the phone.
RikRong said:
Yeah, I've only seen this occur on the few devices that had the update fail. I think it's striclty a software thing because it goes back to unlocked after the indviduals were able to recover the phone.
Click to expand...
Click to collapse
Confirming my dad's phone is still unlocked after the update. He didn't do anything with root but I did manage to convince him to root and unlock. Updated yesterday and he's still unlocked. It's gotta be related to the flash failures...
EDIT: stock recovery too...
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Confirming my dad's phone is still unlocked after the update. He didn't do anything with root but I did manage to convince him to root and unlock. Updated yesterday and he's still unlocked. It's gotta be related to the flash failures...
EDIT: stock recovery too...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, possibly. Does anyone know if RSDLite works with a locked boot loader? I tried it earlier and it wouldn't flash, giving an error about GPT partition or something. I didn't really look into it much though, because my phone is still under warranty.
phantomsniper773 said:
Yeah, possibly. Does anyone know if RSDLite works with a locked boot loader? I tried it earlier and it wouldn't flash, giving an error about GPT partition or something. I didn't really look into it much though, because my phone is still under warranty.
Click to expand...
Click to collapse
RSD will work, but you'll only be able to flash the most recent update.

Tired of Waiting for 4.4 OTA

Hi Everyone i got a Quite new Nexus 4.
Im tired of waiting for the OTA and decided to move on to flash in the Factory Images.
As ive been reading on alot of places it says it ruins my warranty. but according to the EU Directives it does not ruin my Hardware Warranty.
So what would you do? would you open the bootloader flash in 4.4 and lock the bootloader. is there anyway the Serviceman can see that only the bootloader been opened if i lock it directly afterwards?
best regards.
Not sure what you mean about the bootloader. Yes u can unlock and lock the bootloader. After you lock it back; no there is not to tell if it was unlocked. If you want to upgrade to 4.4; follow this guide.
badboy47 said:
Not sure what you mean about the bootloader. Yes u can unlock and lock the bootloader. After you lock it back; no there is not to tell if it was unlocked. If you want to upgrade to 4.4; follow this guide.
Click to expand...
Click to collapse
I mean People have had trouble when they have been at a Official Servicecenter.
Apparently the servicecenter said that the customer have had a open bootloader then locked it before going to repair, so the Servicecenter refused to repair the phone.
I dont know if its a myth or not?
so its 100 % secure not damaging any hardware just unlocking the bootloader with nexus toolkit.
Eastliin said:
Hi Everyone i got a Quite new Nexus 4.
Im tired of waiting for the OTA and decided to move on to flash in the Factory Images.
As ive been reading on alot of places it says it ruins my warranty. but according to the EU Directives it does not ruin my Hardware Warranty.
So what would you do? would you open the bootloader flash in 4.4 and lock the bootloader. is there anyway the Serviceman can see that only the bootloader been opened if i lock it directly afterwards?
best regards.
Click to expand...
Click to collapse
I don't know a damn thing about EU Directives. But, I've never heard of google refusing to honor a warranty on a Nexus because the bootloader was unlocked. That's kind of expected on a Nexus, and that's why google makes it so easy to do. It's not like other phones that need to utilize some exploit to do it. There is very little that can go wrong. And it can almost always be fixed by flashing another factory image again.
If it was me, I would have unlocked the bootloader the day I bought it, because unlocking it will wipe your data now. There is no way around that. But if I were you, yes I would unlock it and install whatever you want to. Locking it up again is an option. But if you want to unlock again later, you will have to wipe data, again.
iowabeakster said:
I don't know a damn thing about EU Directives. But, I've never heard of google refusing to honor a warranty on a Nexus because the bootloader was unlocked. That's kind of expected on a Nexus, and that's why google makes it so easy to do. It's not like other phones that need to utilize some exploit to do it. There is very little that can go wrong. And it can almost always be fixed by flashing another factory image again.
If it was me, I would have unlocked the bootloader the day I bought it, because unlocking it will wipe your data now. There is no way around that. But if I were you, yes I would unlock it and install whatever you want to. Locking it up again is an option. But if you want to unlock again later, you will have to wipe data when you unlock in the future.
Click to expand...
Click to collapse
here is a link to the directive im talking about.
http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu
I do wipes from time to time to keep the phone fresh so thats noo worries at all for me.
so for me its just getting toolkit, open bootloader, flash 4.4 then lock the bootloader no harm done?
Eastliin said:
here is a link to the directive im talking about.
http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu
I do wipes from time to time to keep the phone fresh so thats noo worries at all for me.
so for me its just getting toolkit, open bootloader, flash 4.4 then lock the bootloader no harm done?
Click to expand...
Click to collapse
I also don't know anything about toolkits, I use linux and adb/fastboot (nerd).
But yes, unlock booloader, flash the new factory images, and relock it again if you want. Like I said, unlocking a Nexus is not some taboo process to google. Simply unlocking it won't void your warranty.
They only way you can void your warranty is abuse (dropping it, getting it wet, etc) , or installing BAD software that causes the hardware to malfunction. If you are installing google's factory images, you have nothing to worry about.
iowabeakster said:
I also don't know anything about toolkits, I use linux and adb/fastboot (nerd).
But yes, unlock booloader, flash the new factory images, and relock it again if you want. Like I said, unlocking a Nexus is not some taboo process to google. Simply unlocking it won't void your warranty.
They only way you can void your warranty is abuse (dropping it, getting it wet, etc) , or installing BAD software that causes the hardware to malfunction. If you are installing google's factory images, you have nothing to worry about.
Click to expand...
Click to collapse
ye i will follow a guide,
i know its ok to unlock bootloader by google, but LG that does the repair in sweden screams NONO haha
Eastliin said:
ye i will follow a guide,
i know its ok to unlock bootloader by google, but LG that does the repair in sweden screams NONO haha
Click to expand...
Click to collapse
actualy google says to unlock,flash and then relock for"security purposes".
opssemnik said:
actualy google says to unlock,flash and then relock for"security purposes".
Click to expand...
Click to collapse
Thats fun haha, you got a link of where they state that?
Eastliin said:
Thats fun haha, you got a link of where they state that?
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images?hl=pt-BR
"After restoring a factory image,lock the bootloader for security reasons." almost at bottom of page, after all the images. on instructions part.
opssemnik said:
https://developers.google.com/android/nexus/images?hl=pt-BR
"After restoring a factory image,lock the bootloader for security reasons." almost at bottom of page, after all the images. on instructions part.
Click to expand...
Click to collapse
so with that link LG cant screw me at all! when it comes to repairing a phone.
Thx alot!
Eastliin said:
so with that link LG cant screw me at all! when it comes to repairing a phone.
Thx alot!
Click to expand...
Click to collapse
^, they tried to screw with me, but as i know lg here in brasil, i carried a book of "consumers defense code", i showed them the link,and the guy from the service center had to get my n4 and fix for no fee (my screen was broken, and no touch, but the screen broke because of overheating).

Root on Nexus 6p, is it safe?

I ask this because the qfuse controversy and having the biometric sensor, maybe rooting this device is not safe as it is in the previous nexus, what do you think?
Quetzalcoalt_Lp said:
I ask this because the qfuse controversy and having the biometric sensor, maybe rooting this device is not safe as it is in the previous nexus, what do you think?
Click to expand...
Click to collapse
I'm rooted, q-fuse is still intact, fingerprint scanner still works, I haven't tried to use android pay yet.
Quetzalcoalt_Lp said:
I ask this because the qfuse controversy and having the biometric sensor, maybe rooting this device is not safe as it is in the previous nexus, what do you think?
Click to expand...
Click to collapse
I'm rooted and have no problems. I've heard Android pay will work on stock rom with systemless root, but have not tested it yet. I get my us bank card soon and will sign up then.
then i guess ill root today, thank you!
Quetzalcoalt_Lp said:
then i guess ill root today, thank you!
Click to expand...
Click to collapse
Just follow heisenbergs guide in the general stickies as some stuff is new on the 6p like the fastboot commands and the updated tools from the sdk. You will also want to have a stock copy of the vendor partition and the ems partition or whatever it's called. It's covered in the guide. Happy Flashing!
http://forum.xda-developers.com/showthread.php?p=62924043
You will not lose Nexus Imprint (fingerprint) functionality by rooting. The Qfuse will not blow when you unlock or root. Android Pay probably won't work if you root, but some people claim it does work. Any modifications to /system will cause it to fail.
fury683 said:
You will not lose Nexus Imprint (fingerprint) functionality by rooting. The Qfuse will not blow when you unlock or root. Android Pay probably won't work if you root, but some people claim it does work. Any modifications to /system will cause it to fail.
Click to expand...
Click to collapse
Nothing breaks after root if you use the new systemless root.
Just one more thing, do you guys know how to remove the splash screen when phone boots once rooted? it says something like "Your device software can't be checked for corruption. Please lock the bootloader."
Quetzalcoalt_Lp said:
Just one more thing, do you guys know how to remove the splash screen when phone boots once rooted? it says something like "Your device software can't be checked for corruption. Please lock the bootloader."
Click to expand...
Click to collapse
I am not 100% sure on this because I asked a while back. But I am fairly certain there is currently no way to remove that splash screen with the warning. If I am mistaken, please let me know as I would also like to remove mine.
Quetzalcoalt_Lp said:
Just one more thing, do you guys know how to remove the splash screen when phone boots once rooted? it says something like "Your device software can't be checked for corruption. Please lock the bootloader."
Click to expand...
Click to collapse
. It's something Google is doing now. It just warns of the system state. Here is the page
https://support.google.com/nexus/answer/6185381?hl=en
thesticks00 said:
I am not 100% sure on this because I asked a while back. But I am fairly certain there is currently no way to remove that splash screen with the warning. If I am mistaken, please let me know as I would also like to remove mine.
Click to expand...
Click to collapse
It must be a way, maybe flashing a modified boot.img or something.
Gizmoe said:
. It's something Google is doing now. It just warns of the system state. Here is the page
https://support.google.com/nexus/answer/6185381?hl=en
Click to expand...
Click to collapse
Yes, it's only a notification, it does nothing, but I would want to remove it since is pretty ugly xd.
Quetzalcoalt_Lp said:
It must be a way, maybe flashing a modified boot.img or something.
Yes, it's only a notification, it does nothing, but I would want to remove it since is pretty ugly xd.
Click to expand...
Click to collapse
It's in the bootloader. Don't mess with the bootloader. Just ignore it for the 5 seconds it shows up during the once or twice a week you reboot.
akellar said:
It's in the bootloader. Don't mess with the bootloader. Just ignore it for the 5 seconds it shows up during the once or twice a week you reboot.
Click to expand...
Click to collapse
Maybe with a custom kernel or something you make the BL think you are not rooted or unlocked.
But yes, I wont touch the BL.
I'm pretty sure that I read somewhere that the fuse is actually blown before it the device is even shipped out...
EDIT: I found what I read...
Quote #1
The QFuse is actually an array of different bits that control several different things on the device. In this case, we're talking about the Qualcomm secure boot fuse, which is actually blown at the factory (hence it always being enabled) to prevent an insecure bootloader from being run. It does not track any modifications to the phone other than that, so whatever you decide to do, the bootloader will always read the same thing. I think people are confusing this with Samsung Knox, which is specifically made for tracking modifications and storing them for warranty purposes.
Click to expand...
Click to collapse
Quote #2
Much of Qualcomm's security architecture is implemented using QFuses, which are software-programmable fuses that allow one-time configuration of device settings and cryptographic materials such as hashes or keys. Because of their physical nature, once a QFuse has been blown, it is impossible to "unblow" it to revert its original value.
If the FORCE_TRUSTED_BOOT QFuse is blown, as is the case on all production Motorola devices, each stage of the boot chain is cryptographically verified to ensure only authorized bootloader stages may be run. In particular, the PBL ("Primary Bootloader"), which resides in mask ROM, verifies the integrity of the SBL1 ("Secondary Bootloader") via a SHA1 hash. Each stage of the boot chain verifies the next stage using RSA signatures, until finally Motorola's APPSBL ("Application Secondary Bootloader"), "MBM", is loaded and run.
Click to expand...
Click to collapse
Quote #3
So it would seem the Qfuse has nothing to do with unlocking the bootloader. It's just a way to set cryptographic keys in the hardware for verifying the authenticity of the bootloader, in a manner that makes it impossible to change the keys. In other words, once the fuse is blown the keys can't phyically be changed or overwritten. Presumably Google has the key and can sign new bootloader images correctly, so that when there is an update to the bootloader it will be verified properly by the chipset.
Click to expand...
Click to collapse
Just close your eye's for a few seconds!
People that ask this question should stick to Crapple...
Sent from my Nexus 6P using Tapatalk

How to Root a HTC one (M8) in 2016 For beginners - (first time posting)

I have just recently started my journey into rooting, I've been in research mode for about a week trying to learn as much as I can but it's SO overwhelming trying to keep up with all the old and new techniques - trying to find out what is the best method to use.
Before discovering this place I asked a few questions on reddit and was able to get a cheat sheet on all the terms one needs for rooting:
https://www.reddit.com/r/androidroo...ingroot_considered_true_rooting_where_is_the/
and while browsing Xda I found this short guide:
http://forum.xda-developers.com/htc-one-m8/help/how-to-root-htc-one-m8-android-6-0-t3420748
However both of theses sets of instructions miss out a few starting points.
I've watched a few videos on how to root a htc but they've all been made around the time of the phones release, and as we all know each year things get bigger and better in computing, so new techniques might have arrived. So I wanted to ask here what are the full sets of instructions to root a htc one m8 in 2016, starting from watch software to use to back up your phone, how to unlock the bootloader, etc... and using whatever new rooms and kernels people have been using and would recommend.
My aim is, with your help, to make this post a place beginners can go to learn how to do their first root. thankyou in advance.
My phone:
service provider: Orange/EE (UK)
Android: 6.0 (Marshmallow I think)
HTC sense version: 7.0
Sofware number: 6.12.61.4
I've just rooted my phone unlocking the bootloader yesterday. I haven't gone S-off yet.
I'm coming from Samsung phones so things are a little different for me too. I followed this guide which covers everything you can and will need to gain full root on an m8
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
to get root apps to have all the ability they have elsewhere you need to cover 3 steps
1) unlock the bootloader, which will make some partitions accessible, but writing to the system partition is still blocked apart from via custom recovery (the phone reboots when you try to write into the system partition without "full root").
2) root. fairly obvious what that is.
3) gain S-off, which makes system partition accessible outside of the custom recovery. the phone can be enjoyed the same as any other rooted device at this stage. **this can only be done one way, and that one single way isn't free.**
you want to have all the stages mentioned in that link covered apart from the last firmware guide which is more optional.
How are you getting S-off that isn't free? I had S-off within a week of owning my phone back when it was new, and I'm on Verizon, they are the devil when it comes to modding anything. Have you looked into Sunshine?
hello guys,im looking forward rooting my m8,is there any method to root my phone without void my warranty?(i mean if i unroot my phone will still be on warranty?)
ieatabiscuit said:
How are you getting S-off that isn't free? I had S-off within a week of owning my phone back when it was new, and I'm on Verizon, they are the devil when it comes to modding anything. Have you looked into Sunshine?
Click to expand...
Click to collapse
the "not free" S-off I'm referring to is sunshine, unless things have changed (if they have I'll be delighted).
3mel said:
the "not free" S-off I'm referring to is sunshine, unless things have changed (if they have I'll be delighted).
Click to expand...
Click to collapse
Just rechecked into it to refresh my memory, as I've been S-off so long I forgot the method I had used. It was in the pre-Sunshine days. I used Firewater to get S-off (thought Sunshine sounded odd to me for some reason). Didn't cost me anything but a couple minutes of my time. Hope that helps. I wouldn't want to pay for S-off either, it's not really something that I think many people would want to do...
---------- Post added at 06:53 AM ---------- Previous post was at 06:47 AM ----------
GreiverX said:
hello guys,im looking forward rooting my m8,is there any method to root my phone without void my warranty?(i mean if i unroot my phone will still be on warranty?)
Click to expand...
Click to collapse
If you have a way to revert it and become S-on again (assuming you're S-off also) I would say you could hide the fact it's been rooted by unrooting and removing any root apps, but don't quote me on that. I rooted back when mine was new, and never looked back at the warranty. Now my phone would have had the warranty expire anyway, so it still doesn't matter. When in doubt, assume the warranty to be void upon rooting, but research a way to revert if it's possible. Not like we have to bother with KNOX at least.
only way is USD $25 for sunshine....can't S-OFF it without other ways.
WingZer0n said:
only way is USD $25 for sunshine....can't S-OFF it without other ways.
Click to expand...
Click to collapse
then why does firewater say different?
grrmisfit said:
then why does firewater say different?
Click to expand...
Click to collapse
firewater doesn't work anymore unfortunately. Only way to get S-Off now is sunshine @ USD 25.
3mel said:
I've just rooted my phone unlocking the bootloader yesterday. I haven't gone S-off yet.
I'm coming from Samsung phones so things are a little different for me too. I followed this guide which covers everything you can and will need to gain full root on an m8
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
to get root apps to have all the ability they have elsewhere you need to cover 3 steps
1) unlock the bootloader, which will make some partitions accessible, but writing to the system partition is still blocked apart from via custom recovery (the phone reboots when you try to write into the system partition without "full root").
2) root. fairly obvious what that is.
3) gain S-off, which makes system partition accessible outside of the custom recovery. the phone can be enjoyed the same as any other rooted device at this stage. **this can only be done one way, and that one single way isn't free.**
you want to have all the stages mentioned in that link covered apart from the last firmware guide which is more optional.
Click to expand...
Click to collapse
Hi I can't root mine . Every time I try to get token it says that it's a incorrect file batch path or something like that? Do you know what the problem is?
Nebster7 said:
Hi I can't root mine . Every time I try to get token it says that it's a incorrect file batch path or something like that? Do you know what the problem is?
Click to expand...
Click to collapse
Please stop making new posts in different threads. It won't get your issue fixed any faster. It just confuses those trying to help you, leaving incomplete bits of info here and there. Just stick to one thread, specifically the one where I am already trying to help you.
redpoint73 said:
Please stop making new posts in different threads. It won't get your issue fixed any faster. It just confuses those trying to help you, leaving incomplete bits of info here and there. Just stick to one thread, specifically the one where I am already trying to help you.
Click to expand...
Click to collapse
Sorry. I have my issue fixed now as I just needed to type cmd on the top of the window to get token to unlock bootloader token. Flashed aicp 14.0 working excellent. Much faster, better battery oh only arm 9.0 pico seemed like the best gapps as I tried other ones didn't work. Man it took a lot of searching to do this as things are posted all over the place
---------- Post added at 02:56 AM ---------- Previous post was at 02:38 AM ----------
Nebster7 said:
Sorry. I have my issue fixed now as I just needed to type cmd on the top of the window to get token to unlock bootloader token. Flashed aicp 14.0 working excellent. Much faster, better battery oh only arm 9.0 pico seemed like the best gapps as I tried other ones didn't work. Man it took a lot of searching to do this as things are posted all over the place
Click to expand...
Click to collapse
Just one thing my PC doesn't see my phone now.???
Nebster7 said:
Just one thing my PC doesn't see my phone now.???
Click to expand...
Click to collapse
Meaning what exactly? Doesn't see storage (did you select the option on the phone to allow data transfer?) or adb or fastboot? Booted to the custom ROM, or something else (bootloader, recovery)?
When asking for help, please give as much information as possible. One sentence is really never enough info to go on.

My Advice to All Owners - Enable Bootloader Unlocking Before It Bricks

... if you read the article below and feel that you do not need this security feature.
I bricked my phone for the first time in years of messing with custom ROM, upgrades and embedded software development.
All because I was not aware of this:
https://android.gadgethacks.com/new...ting-before-modding-anything-android-0167840/
In my case, I was complacent to think that as long as I am not loading custom ROM, I would not need to unlock bootloader on my Mate8 - code integrity is for your own good, right?
In the end the OTA bricked my phone. I went as far as getting the unlocker code after the fact from Huawei - but guess what, it is useless now because I had not enabled that developer option when the phone was working.
TLbonchef1234 said:
... if you read the article below and feel that you do not need this security feature.
I bricked my phone for the times in years of messing with custom ROM, upgrades and embedded software development.
All because I was not aware of this:
https://android.gadgethacks.com/new...ting-before-modding-anything-android-0167840/
In my case, I was complacent to think that as long as I am not loading custom ROM, I would not need to unlock bootloader on my Mate8 - code integrity is for your own good, right?
In the end the OTA bricked my phone. I went as far as getting the unlocker code after the fact from Huawei - but guess what, it is useless now because I had not enabled that developer option when the phone was working.
Click to expand...
Click to collapse
Never even considered this...I'm not one to root, screw around other than a factory update, but maybe unlocking it, updating and when
finished, lock it again?
Personally, my phone NEVER leaves my sight, plus I don't carry around "nude selfies" or any of that garbage, plus I use an 8 digit pin
code, and fingerprint, so on the off chance it would get stolen, I doubt anything of value is on it. I don't do banking or anything else from
it either.
TLbonchef1234 said:
... if you read the article below and feel that you do not need this security feature.
I bricked my phone for the first time in years of messing with custom ROM, upgrades and embedded software development.
All because I was not aware of this:
https://android.gadgethacks.com/new...ting-before-modding-anything-android-0167840/
In my case, I was complacent to think that as long as I am not loading custom ROM, I would not need to unlock bootloader on my Mate8 - code integrity is for your own good, right?
In the end the OTA bricked my phone. I went as far as getting the unlocker code after the fact from Huawei - but guess what, it is useless now because I had not enabled that developer option when the phone was working.
Click to expand...
Click to collapse
so i tried to upgrade my mate 8 c636180 to 211... and i am guessing with what you said might have happened to me too. i did not enable the oem bootloader... and now i cannot even use DLOAD to upgrade the phone.. always to erecovery.... so are you SOL? have you tried anything?
i have used DC phoenix... but no luck...
there is another option on DC unlocker... it says unlock factory reset setting? or something like that... but i have to buy another 15 credits... i am wondering if that would solve anything...
initialdwiko said:
so i tried to upgrade my mate 8 c636180 to 211... and i am guessing with what you said might have happened to me too. i did not enable the oem bootloader... and now i cannot even use DLOAD to upgrade the phone.. always to erecovery.... so are you SOL? have you tried anything?
i have used DC phoenix... but no luck...
there is another option on DC unlocker... it says unlock factory reset setting? or something like that... but i have to buy another 15 credits... i am wondering if that would solve anything...
Click to expand...
Click to collapse
Based on my understanding of the article I quoted, I have exhausted my ((soft fix) means. Fastboot wont help and no way to boot alternate image from SD (only from device memory). I dont think DC can do magic in this case.
I started to look into replacing the board - not as bad as I thought originally as there are screws instead of glue. Just need to do a bit more research because the disassembling video says there are a few small parts that are not supposedly re-usable.
TLbonchef1234 said:
Based on my understanding of the article I quoted, I have exhausted my ((soft fix) means. Fastboot wont help and no way to boot alternate image from SD (only from device memory). I dont think DC can do magic in this case.
I started to look into replacing the board - not as bad as I thought originally as there are screws instead of glue. Just need to do a bit more research because the disassembling video says there are a few small parts that are not supposedly re-usable.
Click to expand...
Click to collapse
DC Phoenix should work I used and did same thing was able to get out DC unlocker won't work
---------- Post added at 12:47 AM ---------- Previous post was at 12:45 AM ----------
michael0617 said:
DC Phoenix should work I used and did same thing was able to get out DC unlocker won't work
Click to expand...
Click to collapse
I just found an update.app file that was close to mine paid fee then it took firmware in fast boot mode after it finished I unplugged restart and it worked
michael0617 said:
DC Phoenix should work I used and did same thing was able to get out DC unlocker won't work
---------- Post added at 12:47 AM ---------- Previous post was at 12:45 AM ----------
I just found an update.app file that was close to mine paid fee then it took firmware in fast boot mode after it finished I unplugged restart and it worked
Click to expand...
Click to collapse
Cool. Perhaps I should give it try. But, according to the article I quoted, this lock is fairly new. Did you fix a brick on Mate 8 specifically, or older an older model? And did you NOT have Bootloader Unlocked enabled (not the unlock action itself) in Dev Option prior (which was the main point of my post)?
I had nothing unlocked... it was completely untouched. I bought it and start using it. Did not activate any of the dev options to oem Unlock. I am wondering if you using D.C. Phoenix had all the options unlocked?
---------- Post added at 05:48 AM ---------- Previous post was at 05:45 AM ----------
michael0617 said:
DC Phoenix should work I used and did same thing was able to get out DC unlocker won't work
---------- Post added at 12:47 AM ---------- Previous post was at 12:45 AM ----------
I just found an update.app file that was close to mine paid fee then it took firmware in fast boot mode after it finished I unplugged restart and it worked
Click to expand...
Click to collapse
I used 211 to do the Phoenix and after it does what it is supposed to do... it tells me to restart and it should work... but same thing... I am wondering if it's that firmware you are talking about... needs to be the same? I had l29-c636180
Try DC Phoenix Method 2 using factory firmware flash using NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_A ndroid_6.0_EMUI_4.0.dgtks file, this method will put your Mate 8 as new with a Chinese firmware, then you can follow installing the firmware for your phone version using DLOAD method. Ask for support on dc-unlocker forum.
pvitruvian said:
Try DC Phoenix Method 2 using factory firmware flash using NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_A ndroid_6.0_EMUI_4.0.dgtks file, this method will put your Mate 8 as new with a Chinese firmware, then you can follow installing the firmware for your phone version using DLOAD method. Ask for support on dc-unlocker forum.
Click to expand...
Click to collapse
oh my!!! thank you so much! i did what you said and i was able to fix my problem.. i updated that firmware.. then UPDATE.APP 211 to it and it worked! now my phone is working properly again! thank you so much!!! but now i have a MATE 9!!! hahahahahah time to sell my mate 8! thanks again man!! you are the best!
hey OP! you should definitely try using DC phoenix method 2... it worked out for me. cost me 15 more credits though... because i wasted 72 hours contemplating on what to do.

Categories

Resources