Related
Hi guys I have a XT926
Since my phone was updated to KK I had problems .
I wonder if you can give back to JB.
But I have not unlocked the booltoader
Since I could never unlock and less with KK
I did the Factory data Reset. but still giving me problems
Thanks for your attention
FrederickIV said:
Hi guys I have a XT926
Since my phone was updated to KK I had problems .
I wonder if you can give back to JB.
But I have not unlocked the booltoader
Since I could never unlock and less with KK
I did the Factory data Reset. but still giving me problems
Thanks for your attention
Click to expand...
Click to collapse
cant be done, period.
Is it possible downgrade from KK to JB with unlocked bootloader
by the House of Moto and proper XML file?
Regards
Rafal
rafjak said:
Is it possible downgrade from KK to JB with unlocked bootloader
by the House of Moto and proper XML file?
Regards
Rafal
Click to expand...
Click to collapse
Yes.
But, here's something even better. With the new Towelroot for locked bootloaders on KK, once rooted, you can then use Motopocalypse and unlock your bootloader.
Nice going, Motorola! With the KK update, someone must have pulled in the old code to allow the exploit to unlock the bootloader (that was patched as of 9.18) to work. Way too funny, but I'm sure many people out there are bowing to Motorola for this, even though I'm sure it wasn't supposed to happen like this! :silly:
So, those of you with locked bootloaders, go root RIGHT NOW and UNLOCK those bootloaders. You're warranty was voided as soon as you rooted, so what harm is there in unlocking it as well? That means when the next OTA comes out (not sure when, but it will probably be soon since I got a new email for a new soak test), it means root will definitely be broken for those with locked bootloaders. With an unlocked bootloader, you'll be able to sideload SU onto your phones when the new OTA comes out, so better to be safe than sorry.
Good to know...
iBolski said:
Yes.
But, here's something even better. With the new Towelroot for locked bootloaders on KK, once rooted, you can then use Motopocalypse and unlock your bootloader.
Nice going, Motorola! With the KK update, someone must have pulled in the old code to allow the exploit to unlock the bootloader (that was patched as of 9.18) to work. Way too funny, but I'm sure many people out there are bowing to Motorola for this, even though I'm sure it wasn't supposed to happen like this! :silly:
So, those of you with locked bootloaders, go root RIGHT NOW and UNLOCK those bootloaders. You're warranty was voided as soon as you rooted, so what harm is there in unlocking it as well? That means when the next OTA comes out (not sure when, but it will probably be soon since I got a new email for a new soak test), it means root will definitely be broken for those with locked bootloaders. With an unlocked bootloader, you'll be able to sideload SU onto your phones when the new OTA comes out, so better to be safe than sorry.
Click to expand...
Click to collapse
.... but now can you tall me how to get back to JB, please?
Big Fat Droid said:
.... but now can you tall me how to get back to JB, please?
Click to expand...
Click to collapse
Well, technically there is no going back.....you can use SamuriHL's HouseOfMoto...with the JB FXZ files to generate the scripts, and then use the Universal script to flash....this will flash everything EXCEPT the tz and gpt partitions, at that point you should be able to flash a JB ROM.
You cannot downgrade tz and gpt so dont waste your time trying...
Big Fat Droid said:
.... but now can you tall me how to get back to JB, please?
Click to expand...
Click to collapse
use this [guide] to flash kk, root, unlock the bootloader, go back to jb, and root again. http://forum.xda-developers.com/showthread.php?t=2789743
So can i or cant i downgrade tz and gpt ?
Big Fat Droid said:
So can i or cant i downgrade tz and gpt ?
Click to expand...
Click to collapse
nope never not even when unlocked.
Ok i recieved my galaxy s3 in the mail today and look up how to root it.I found a very easy way by using towel root with supper something to do some binary configuring so it would be a good root.Any way after my device was rooted i decided to get CWM so i could install a custom rom.I tried odin but when i tried it it failed to flash.So then i went on the play store and got rom manager and installed it through there.I then tried to get into CWM and saw this message "Verizion has detected 3rd party software bring it to a verizion shop" something like that.Anyway idk what to do now.Do i unlock the bootloader now? is the bootloader even the problem? if i unlock the bootloader will my device be okay and will i be able to get into CWM? i really need help its been a while since i rooted the last time i rooted it was a samsung galaxy player 5.0 and i was able to get CWM and root i digress.Thanks in advance.
im running 4.2.2
Nitrosolid said:
Ok i recieved my galaxy s3 in the mail today and look up how to root it.I found a very easy way by using towel root with supper something to do some binary configuring so it would be a good root.Any way after my device was rooted i decided to get CWM so i could install a custom rom.I tried odin but when i tried it it failed to flash.So then i went on the play store and got rom manager and installed it through there.I then tried to get into CWM and saw this message "Verizion has detected 3rd party software bring it to a verizion shop" something like that.Anyway idk what to do now.Do i unlock the bootloader now? is the bootloader even the problem? if i unlock the bootloader will my device be okay and will i be able to get into CWM? i really need help its been a while since i rooted the last time i rooted it was a samsung galaxy player 5.0 and i was able to get CWM and root i digress.Thanks in advance.
im running 4.2.2
Click to expand...
Click to collapse
Your going to be upset but you have a locked bootloader. You cannot have custom recovery or most custom roms. I suggest you return it if these things are important to you and get an at&t or t mobile s3 because neither of them have locked bootloaders
Datboi459 said:
Your going to be upset but you have a locked bootloader. You cannot have custom recovery or most custom roms. I suggest you return it if these things are important to you and get an at&t or t mobile s3 because neither of them have locked bootloaders
Click to expand...
Click to collapse
I'm almost sure the att version has a locked bootloader also. Att phones for the most part are similar to VZW ones
Sent from my Nexus 5
ShapesBlue said:
I'm almost sure the att version has a locked bootloader also. Att phones for the most part are similar to VZW ones
Sent from my Nexus 5
Click to expand...
Click to collapse
What S3 device doesnt have a locked boot loader?
Datboi459 said:
Your going to be upset but you have a locked bootloader. You cannot have custom recovery or most custom roms. I suggest you return it if these things are important to you and get an at&t or t mobile s3 because neither of them have locked bootloaders
Click to expand...
Click to collapse
Yeah your right.I really wanted to get a custom rom and over clock do all this nice stuff and make my device as awesome as i can make it.i hate verizion and any carrier who locks bootloaders :/.i guess im just gonna un-root it and try to get it back the way it was.Do you know how i can get that verizion message to go away and unroot?
Nitrosolid said:
What S3 device doesnt have a locked boot loader?
Click to expand...
Click to collapse
The t-mobile and sprint version for sure have unlocked bootloaders
Datboi459 said:
The t-mobile and sprint version for sure have unlocked bootloaders
Click to expand...
Click to collapse
That's true but I'm not sure about the att one
Sent from my Nexus 5
ShapesBlue said:
That's true but I'm not sure about the att one
Sent from my Nexus 5
Click to expand...
Click to collapse
The at&t galaxy s3 bootloader is unlocked. They started locking the bootloader when the s4 came out: http://www.ubergizmo.com/2013/08/att-stops-unlocked-bootloader-support/
Datboi459 said:
The at&t galaxy s3 bootloader is unlocked. They started locking the bootloader when the s4 came out: http://www.ubergizmo.com/2013/08/att-stops-unlocked-bootloader-support/
Click to expand...
Click to collapse
Right its an older baseband/update that's unlocked just like the VZW S3 running 4.1.2 was unlock able but newer versions are not unlockable
Sent from my Nexus 5
ShapesBlue said:
Right its an older baseband/update that's unlocked just like the VZW S3 running 4.1.2 was unlock able but newer versions are not unlockable
Sent from my Nexus 5
Click to expand...
Click to collapse
On the AT&T S3 (i747) once you take the 4.3 update (MJB) the bootloader is restricted in that you can not down grade it, or any subsequent updates. (It is my daily driver phone)
It is not locked in the sense that you are prohibited from rooting, flashing custom recoveries, custom ROMs, etc. Once you upgrade to the NE4 bootloader and modem you must keep the version numbers for the bootloader and modem matched. It is possible to run custom JB roms on the KK bootloader and modem, although you may need to edit the updater script to get the custom recovery to flash the rom. People are running JB, KK, and LP ROMs on firmware from 4.3 upwards. These ROM are TW mods, AOSP, CM, and CM derivatives.
dawgdoc said:
On the AT&T S3 (i747) once you take the 4.3 update (MJB) the bootloader is restricted in that you can not down grade it, or any subsequent updates. (It is my daily driver phone)
It is not locked in the sense that you are prohibited from rooting, flashing custom recoveries, custom ROMs, etc. Once you upgrade to the NE4 bootloader and modem you must keep the version numbers for the bootloader and modem matched. It is possible to run custom JB roms on the KK bootloader and modem, although you may need to edit the updater script to get the custom recovery to flash the rom. People are running JB, KK, and LP ROMs on firmware from 4.3 upwards. These ROM are TW mods, AOSP, CM, and CM derivatives.
Click to expand...
Click to collapse
That's pretty much how it was on the VZW S3, after the 4.1.2 update there was no going back
Sent from my Nexus 5
ShapesBlue said:
That's pretty much how it was on the VZW S3, after the 4.1.2 update there was no going back
Sent from my Nexus 5
Click to expand...
Click to collapse
I agree with you about the no going back.
The big difference is that the AT&T S3 can install the custom recovery or ROM of your choice even if you have taken all of the OTA updates. It is not limited to two or three "safe" ROMs.
Anyhow, all of this is off topic of the thread.
dawgdoc said:
I agree with you about the no going back.
The big difference is that the AT&T S3 can install the custom recovery or ROM of your choice even if you have taken all of the OTA updates. It is not limited to two or three "safe" ROMs.
Anyhow, all of this is off topic of the thread.
Click to expand...
Click to collapse
Ah no worries there. It is what it is. I'd rather just have an unlocked bootloader and not have to fiddle with specific things. I'm loving my Nexus and wouldn't go back to a Samsung right now if I was paid to do it
Sent from my Nexus 5
ShapesBlue said:
Ah no worries there. It is what it is. I'd rather just have an unlocked bootloader and not have to fiddle with specific things. I'm loving my Nexus and wouldn't go back to a Samsung right now if I was paid to do it
Sent from my Nexus 5
Click to expand...
Click to collapse
My wish is that a Nexus had a removable battery and an external sdcard >> the perfect device. ;-D
dawgdoc said:
My wish is that a Nexus had a removable battery and an external sdcard >> the perfect device. ;-D
Click to expand...
Click to collapse
Its not as bad as it sounds. I've gotten use to it not having either. Solid device overall
Sent from my Nexus 5
Plzzz help!!!!!!!!!!!!!!!!!!!!!!
you can't
K.V.K said:
Plzzz help!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
well my friend sry but you can't restore this code
most of devices like samsung,motorola etc they have.... lets say a key for the bootloader(is the door) and this key if you root your device
breaks and the half key stays inside the door hole to reminds you that the key is broken(the devicesis root/unlockbootloader).
so if you root any motorola device the code state goes
automatically 2 and stays like this,you can flash again the stock rom and relock the bootloader sure
but the code stays 2 for ever.
i hope to help you
moto g XT1541 stock rom 6.0.1 lockbootloader
bromoxitos said:
well my friend sry but you can't restore this code
most of devices like samsung,motorola etc they have.... lets say a key for the bootloader(is the door) and this key if you root your device
breaks and the half key stays inside the door hole to reminds you that the key is broken(the devicesis root/unlockbootloader).
so if you root any motorola device the code state goes
automatically 2 and stays like this,you can flash again the stock rom and relock the bootloader sure
but the code stays 2 for ever.
i hope to help you
moto g XT1541 stock rom 6.0.1 lockbootloader
Click to expand...
Click to collapse
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
yeap
acejavelin said:
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
Click to expand...
Click to collapse
YEAAA we say the same think,but i use an othey way to say it.
i say in the end you can relock the bootloader (more or less) when i say this i mean that you put some partitions back in boot loader
so when you flash the stock rom you can take any ota update,but the main bootloader is unlock always.
i know that form my old moto g2gen, moto x2013!!!
bromoxitos said:
YEAAA we say the same think,but i use an othey way to say it.
i say in the end you can relock the bootloader (more or less) when i say this i mean that you put some partitions back in boot loader
so when you flash the stock rom you can take any ota update,but the main bootloader is unlock always.
i know that form my old moto g2gen, moto x2013!!!
Click to expand...
Click to collapse
You could relock the bootloader on older Motos, but not anymore... Actually, it can be relocked but it will never report as locked or relocked, it will always be reported as unlocked. I don't how to be more plain in describing this.
And yes, you can take an OTA when unlocked, as long as you have a stock ROM and recovery and your bootloader is the correct version for your ROM. If your bootload and ROM are out of sync (ie. you have a Marshmallow bootloader and a Lollipop ROM), if your bootloader and ROM are out of sync, you could potentially get into a hard bricked situation.
ohh!!
acejavelin said:
You could relock the bootloader on older Motos, but not anymore... Actually, it can be relocked but it will never report as locked or relocked, it will always be reported as unlocked. I don't how to be more plain in describing this.
And yes, you can take an OTA when unlocked, as long as you have a stock ROM and recovery and your bootloader is the correct version for your ROM. If your bootload and ROM are out of sync (ie. you have a Marshmallow bootloader and a Lollipop ROM), if your bootloader and ROM are out of sync, you could potentially get into a hard bricked situation.
Click to expand...
Click to collapse
not any more? damn....yea we say the same think,sry for my english,yea i khow what you talking about i brick my moto x like this!!! any way.
ty for the new info about bootloader.
you was 100%
were you a clear,thanks a lot,and i hope to help him
Once I sent my hard bricked phone to Motorola. I had unlocked the bootloader and done the stupid mistake of sideloading an older version and upgrading to a newer, but still older version. When it came back, it said it was Status Code 0.
Wonder how they did it.
yagyaxt1068 said:
Once I sent my hard bricked phone to Motorola. I had unlocked the bootloader and done the stupid mistake of sideloading an older version and upgrading to a newer, but still older version. When it came back, it said it was Status Code 0.
Wonder how they did it.
Click to expand...
Click to collapse
They flash the eMMC chip (internal storage chip) directly... If you could get the right image you could possibly do it yourself with a few hundred to thousand dollar investment in a proper JTAG flashing unit.
Key would be getting the right Image, this would be far more than just a normal stock fastboot image, and is probably generated on the fly per device due to differences in serial number, IMEI, etc. These types of images don't get leaked out.
acejavelin said:
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
Click to expand...
Click to collapse
ok so what if you have never root unlocked, did nothing but use as intended to be.. never trying to do anything to it. wtf would i have a code 2 status then? care to sum that up for me.. cause 100% my situation.
wiytboi said:
ok so what if you have never root unlocked, did nothing but use as intended to be.. never trying to do anything to it. wtf would i have a code 2 status then? care to sum that up for me.. cause 100% my situation.
Click to expand...
Click to collapse
You unlocked the bootloader... It doesn't matter if you actually changed anything else or not. Once it's been done, this status code can never go back to 0. If the status code is 2 and you didn't unlock the bootloader, then someone else did.
acejavelin said:
You unlocked the bootloader... It doesn't matter if you actually changed anything else or not. Once it's been done, this status code can never go back to 0. If the status code is 2 and you didn't unlock the bootloader, then someone else did.
Click to expand...
Click to collapse
No I didn't.. I don't even know how to.. I just found out about recovery mode.. Wait wait before i say that.. How do you unlock boot loader? Turning developer mode on? Going to recovery menu? I've never hard reset it.. Just soft or doing new device. You said it could work fine for a while then shirt out? Like guy I bought from did and then I bought used for couple years and then went tits up?
wiytboi said:
No I didn't.. I don't even know how to.. I just found out about recovery mode.. Wait wait before i say that.. How do you unlock boot loader? Turning developer mode on? Going to recovery menu? I've never hard reset it.. Just soft or doing new device. You said it could work fine for a while then shirt out? Like guy I bought from did and then I bought used for couple years and then went tits up?
Click to expand...
Click to collapse
You unlock the bootloader with a series of steps that includes submitting a code to Motorola and getting an unlock code back... Performing it forces a factory reset as well. It's not something you can do by accident.
The issue with Status Code 2 was that an official update could have detected that and refused to update properly or done something worse... That never happened.
If everything is working fine, the status being 2 isn't important, it just means the previous owners had unlocked the bootloader and likely rooted or otherwise modified the phone.
I was given an AT&T I337 that had been operator unlocked by a friend. I took it back to NF1 ROM using Heimdall, acquired root with Towelroot and then used Safestrap to boot custom recovery. However, it seems that there is still no way to unlock the bootloader and install other than TW ROMs fully utilizing the phone? I came across an old thread where someone hinted that he had cracked the bootloader encryption but it seemed to fizzle out into nothing.
Am I correct in the understanding above? If so, I will put the phone away since this will not meet my needs.
hga89 said:
I was given an AT&T I337 that had been operator unlocked by a friend. I took it back to NF1 ROM using Heimdall, acquired root with Towelroot and then used Safestrap to boot custom recovery. However, it seems that there is still no way to unlock the bootloader and install other than TW ROMs fully utilizing the phone? I came across an old thread where someone hinted that he had cracked the bootloader encryption but it seemed to fizzle out into nothing.
Am I correct in the understanding above? If so, I will put the phone away since this will not meet my needs.
Click to expand...
Click to collapse
The bootloader is locked and cannot be unlocked. You are stuck with custom TW ROMS only. There was an exploit for the Android 4.2.2 jelly bean firmware that allowed custom ROMS and recovery, but the flaw was patched in later firmware builds and if you try to roll back to the 4.2.2 firmware you will brick your phone.
StoneyJSG said:
The bootloader is locked and cannot be unlocked. You are stuck with custom TW ROMS only. There was an exploit for the Android 4.2.2 jelly bean firmware that allowed custom ROMS and recovery, but the flaw was patched in later firmware builds and if you try to roll back to the 4.2.2 firmware you will brick your phone.
Click to expand...
Click to collapse
Thank you, then the information I gleaned was indeed correct. I will have to put this phone aside since I wanted to run LineageOS on it and it needed to be encrypted as well...
Hello just a few minutes ago I manually searched for updates from the system setting (have auto update off) and realized I had an update so I took it. I've taken updates OTA before with no issues however this time it basically completely factory data reset my phone and also what's more bizarre is it removed my bootloader unlock that I had gotten way back when the phone was first released. I have never installed custom firmware or even rooted the device but I did get my bootloader unlocked using a paid service that I found about here. I have a snapdragon model note 20 ultra 5g. I am so confused why this time around the OTA affected these things. I have included a screenshot of the OTA I took. Can anyone tell me what happened to my bootloader unlock I've had for like 6 months ?
Do you have a U or a UI device? If so I think Samsung changed the bootloader from version 1 to version 2 and that might be why you lost it. Checkout the last 2 pages of this thread here where you might be able to get more clarification.
Whenever you lock or unlock your bootloader, you device will factory reset.
When you took the update, it updated the bootloader to version 2.
Since your unlock was not an official one, it relocked your bootloader in the process.
This is what caused the wipe.
Yup. You're not supposed to take ota updates with unofficial unlocked bootloader.
Not even sim unlock.
coilbio said:
Yup. You're not supposed to take ota updates with unofficial unlocked bootloader.
Not even sim unlock.
Click to expand...
Click to collapse
Is there such a thing as an official bootloader unlock?
shpotik said:
Is there such a thing as an official bootloader unlock?
Click to expand...
Click to collapse
Nope. Not for US versions.
Why did you unlock the bootloader if you haven't ever rooted or flashed custom?
*Detection* said:
Why did you unlock the bootloader if you haven't ever rooted or flashed custom?
Click to expand...
Click to collapse
It sounded like a good idea at the time.