Related
I've searched and found variations on these questions in other posts, but I didn't come across any pertaining quite to my situation, so I wanted advice before I do something wrong and brick my phone.
I have a Sprint Moto X, unlocked & rooted, running 4.2.2 (I think pre-camera update). I'd like to upgrade to stock Sprint Lollipop (when it comes out) & stay unlocked & rooted.
My understanding of the steps that need to be taken:
1. Unroot my device
2. Re-lock my device
3. Flash TWRP and boot to recovery
4. Flash stock Sprint Lollipop
5. Unlock, then re-root device
Is any of this extraneous, or am I leaving anything out? Do I need to upgrade to KitKat before going to Lollipop?
I also have Xposed installed and I have tweaked the PRL on my device ... this shouldn't complicate the upgrade, right?
Relocking is useless, and unless you know what you're doing, flashing stock updates in custom recovery shouldn't be done. You don't necessarily need to unroot either, just make sure all stock system files are still in place.
Sent from my Moto X
imnuts said:
Relocking is useless, and unless you know what you're doing, flashing stock updates in custom recovery shouldn't be done. You don't necessarily need to unroot either, just make sure all stock system files are still in place.
Sent from my Moto X
Click to expand...
Click to collapse
i have a sprint X and if i am going to update this is how i have allways done it with no issues at all.
you can leave your bootloader unlocked that is no a issue. but i always take OTA's and you cant take a OTA with a modded system. so i allways just flash my stock firmware package. that way it removes my custom recovery. Root, and all Xposed changes. Then i take the OTA and just reinstall TWRP, then SuperSU then what ever else you want.
this is the safest way i have found to update, the nice thing about Unlocked Sprint phones is we can easily Root are phones via TWRP and SuperSu.
just my .02 you can do it how ever you like but this is how i am going to do it when the OTA finally comes out if it ever does.
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358
You'll have to unlock the bootloader. No way around it.
Should I be nervous about unlocking the bootloader?
Didn't my Samsung phone come with it already unlocked?
Should you be nervous? Google the pros and cons then decide for yourself.
No phone nor tablet comes with an unlocked bootloader.
I have an XT1053 and just recently unlocked the bootloader through the Motorola site. I waited until now because my original warranty just expired and knew that unlocking the bootloader would void my warranty. I wanted to unlock the bootloader under 4.4.4 because I didn't know if there would be any problems once Lollipop was offered as an update. The unlock process went very smoothly and took only a few minutes. You probably already know that unlocking wipes your phone, so be prepared to reinstall apps and other files. I have not rooted yet because I'll probably wait to do that after the Lollipop OTA comes around. Even then, I may not root because I'm really pretty happy with the phone as it is. For me, unlocking the bootloader was just of way of preserving the future option to root.
stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app
mac1996 said:
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
Do you have fastboot?
if yes, go to your phone bootloader.
Connect to your computer by USB.
Type the following in cmd. (place your recovery img file in fastboot directory)
fastboot flash recovery (your recovery name).img
Sent from my XT1053 using XDA Free mobile app
Check the sticky threads. There's only a year and halfs worth of information available to you here and all over the rest of the internet.
stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
At any point after unlocking the bootloader... To flash recovery, did you do the following...
Start the phone in Fastboot/Bootloader mode.. then from the PC type...
mfastboot flash recovery YourRecovery.img
mfastboot reboot-bootloader
Follow onscreen directions to use vol down key and highlight recovery, then use vol up to select/enter recovery. Once in recovery you can reboot the phone and proceed with whatever you want.
Failure to reboot-bootloader and entering recovery immediately after flashing recovery (i.e. doing something else first) can result in the recovery not sticking.
4.4.4
a year old post by dray_jr says the following:
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
Click to expand...
Click to collapse
can someone explain this to me? I got my phone around august 2014, it came with 4.4.3 and right now I'm on 4.4.4.
If I use the motorola website and follow their bootloader unlock steps am I fine? will I have any brick issues stated from the quote above?
Thread
Nevermind guys, found the perfect thread for 4.4.4 root!
Thread: http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
Final question: I don't have to install supersu root if i install CM12 once i get into TWRP recovery am i correct? (since cms come rooted)
Would flashing a JB kernel (and only the kernel) work to root it as described here?: http://forum.xda-developers.com/crossdevice-dev/sony/guide-xperia-kitkat-4-4-4-rooting-t3003520
Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?
nhizzat said:
Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?
Click to expand...
Click to collapse
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...
dagoban said:
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...
Click to expand...
Click to collapse
I don't proclaim to know the ins and outs of all things android, but I do know this.. Just because a phone has android 4.4.4 doesn't mean its the same 4.4.4 with the same exact flaws and vulnerabilities, susceptible to the same exact root processes. Its why an exploit to root one phone, often doesn't work to root another.
In the case of the Moto X with a locked bootloader, JCASE has come out with many processes exploiting vulnerabilities for Android and the Apps on the Moto X to not only root it, but disable its write protection. As new OTA's have patched an exploit, he came out with other ways.
Starting wth 4.4.2, the vulnerability in the bootoader to disable write protection has been patched.
Jcase's Sunshine tool works on the X with 4.4.3 and lower, and only SOME with 4.4.4. It needs temp root first, etc. For whatever reason, we don't have a way to even temp root the 2013 X on 4.4.4 enough to allow Sunshine to do its work. And despite being asked many times, Jcase pretty much said in the Sunshine discussion threads that v3.0 wont have Moto X 4.4.4 support (unless he changed his mind and I missed it). Yet sunshine and its root processes, etc work on other phones (HTC) with 4.4.4.
But back to the thread you link...
On the X, due to its security measures, with a locked bootloader, you can only flash the Moto signed ROM for your phone. Nothing else. Because of this, you can't flash a custom recovery. To flash items, we use mFastboot and RSDLite. They need the img files, or bin files. If we make our own, they wont be signed, so they wont flash to a phone with a locked bootloader. And you can't package them into a flashable ZIP because stock recovery looks for the Moto digital signature (which we don't have and can't fake), and you can't install TWRP/CWM/Philz/etc to flash that way. So if you manage to pull the JB kernel out of the Moto SBF file, you wont be able to flash it.
Due to write protection on the 2013 X, any changes made to /System and a few other places, will be lost at power off/on. In other words, if you do manage to flash it (or push via adb), it wont stick due to write protection.
We've seen people try and manipulate their phone by trying to DOWNGRADE their ROM. Well, this doesn't work either. GPT.BIN (partition table), and Motoboot.img (bootloader, TZ, and a few other things) get in the way. Even on an X with an Unlocked bootloader, you can't downgrade these parts. Enough who attempted this have ended up bricking their phone immediately, or with later taking an OTA. Sure you can try to flash just system.img, and while that has less risk for bricking, people who have tried this were still not able to use the older Root Exploits (that worked if you hadn't upgraded already). People have tried flashing everything but GPT.BIN and MotoBoot.img. Again, it didn't help with rooting. Not to mention with a missmatched system.img or other parts, features on the phone may not always work properly (going Settings -> Security comes to mind), and you are at risk of bricking should you take an OTA update.
Since that process exploits a vulnerability, and its out there (so the vulnerability is in the public), I'm sure if it worked or was possible, JCASE, Beaups, or others would have put something together.
Now, back on topic of the XT1053... it has an Unlockable bootloader. Unlocking the bootloader disables write protection, and allows you to flash non-moto stuff. So unlocking the bootloader, flashing TWRP, reboot bootloader, enter TWRP and root, is quick, easy, effective, and doesn't rely on vulnerabilities on the phone to be exploited so patches/updates haven't got in the way. Plus you don't have to wait for someone to find them and create a repeatable process.
Hello, I have upgraded to 5.0.2. via OTA a few days ago. My phone was RetEU .23, and the update notification that 5.0.2. became so annoying, so I decided to give it a shot. Lollipop is a disappointment for me, battery drain issues, lagging all over the menus, slow dialer, the phone was running better with KK installed, so I want to return back to 4.4.4.
Unfortunately there is no clear opinion whether this could be done, some say that when you have 5.0.2. bootloader installed with the OTA, you cannot go back, others say that it is no problem to do so. Really confusing.
Anyone tried to go back to 4.4.4. after getting the OTA? Could you please share how did you do so? Unlocking the bootloader and flashing one of the 4.4.4 stock ROMs from the General Section?
dub_1 said:
Hello, I have upgraded to 5.0.2. via OTA a few days ago. My phone was RetEU .23, and the update notification that 5.0.2. became so annoying, so I decided to give it a shot. Lollipop is a disappointment for me, battery drain issues, lagging all over the menus, slow dialer, the phone was running better with KK installed, so I want to return back to 4.4.4.
Unfortunately there is no clear opinion whether this could be done, some say that when you have 5.0.2. bootloader installed with the OTA, you cannot go back, others say that it is no problem to do so. Really confusing.
Anyone tried to go back to 4.4.4. after getting the OTA? Could you please share how did you do so? Unlocking the bootloader and flashing one of the 4.4.4 stock ROMs from the General Section?
Click to expand...
Click to collapse
Hello,
i actually switched from 5.0.2 back to KK 4.4.4 from Pizza_dox
when your bootloader is unlocked and you have TWRP installed
follow these instructions
1, go do a factory reset
2, go to advanced wipe and select :dalvik cache/system/data/internal storage/cache
when you did that there is no system on your phone so when you restart you will be going into an endless bootloop.
3, go press install and select the Microkat.zip file from Pizza_Dox
when that is done you have agian kitkat on your device
i think there some other methods but this is how i did it succesfully.
Also dont forget to make a backup because you will lose everything.
Gerriitw said:
Hello,
i actually switched from 5.0.2 back to KK 4.4.4 from Pizza_dox
when your bootloader is unlocked and you have TWRP installed
follow these instructions
1, go do a factory reset
2, go to advanced wipe and select :dalvik cache/system/data/internal storage/cache
when you did that there is no system on your phone so when you restart you will be going into an endless bootloop.
3, go press install and select the Microkat.zip file from Pizza_Dox
when that is done you have agian kitkat on your device
i think there some other methods but this is how i did it succesfully.
Also dont forget to make a backup because you will lose everything.
Click to expand...
Click to collapse
Thanks for your comment. I actually plan to go back to the stock 4.4.4. I have a basic idea of bootloader and things but not deep into this and have never done it before. From what I have read , I will have to:
1. First I need to unlock the bootloader, as per the instructions in the Moto website.
2. Then I will need to do a factory reset. (settings-secuirity-factory reset or some other way of doing this?)
3. Download 4.4.4 firmware + script.
4. Start up with Power+VolDown buttons and have bootloader menu on screen
5. Run the downloaded script from its .bat file.
6. Wait for some time for the flashing to end, then have stock 4.4.4
Please correct me if something is wrong or missed.
dub_1 said:
Thanks for your comment. I actually plan to go back to the stock 4.4.4. I have a basic idea of bootloader and things but not deep into this and have never done it before. From what I have read , I will have to:
1. First I need to unlock the bootloader, as per the instructions in the Moto website.
2. Then I will need to do a factory reset. (settings-secuirity-factory reset or some other way of doing this?)
3. Download 4.4.4 firmware + script.
4. Start up with Power+VolDown buttons and have bootloader menu on screen
5. Run the downloaded script from its .bat file.
6. Wait for some time for the flashing to end, then have stock 4.4.4
Please correct me if something is wrong or missed.
Click to expand...
Click to collapse
What i did...
Download the correct kk stock rom
Setup my drivers and mfastboot correctly (simple fast boot works too)
Unlocked bootloader. (Voids warranty coz gives bootloader status 3)
Reboot in bootloader now...
Flash all files of kitkat except gpt.bin and motoboot.bin (they never flash for me lol )
Flash all other files (i typed filenames manually)
Fastboot reboot
Ps - no matter what i do..i have not been able to lock my bootloader once i downgraded from 5.0.2 to 4.4.4
Locking bootloader works well on 5.0.2
doctor_droid said:
What i did...
Download the correct kk stock rom
Setup my drivers and mfastboot correctly (simple fast boot works too)
Unlocked bootloader. (Voids warranty coz gives bootloader status 3)
Reboot in bootloader now...
Flash all files of kitkat except gpt.bin and motoboot.bin (they never flash for me lol )
Flash all other files (i typed filenames manually)
Fastboot reboot
Ps - no matter what i do..i have not been able to lock my bootloader once i downgraded from 5.0.2 to 4.4.4
Locking bootloader works well on 5.0.2
Click to expand...
Click to collapse
well guess im gonna try - but no need to do, as makes no difference except to downgrading.... So best off unlocked
simply use the 4.4.4 link in my signature and pick firmware 2 or B called DSDSALL to go back to 4.4.4 .23 ret(xx)
So, it has been confirmed by several forums that when you have officially received the 5.0.2 OTA download update, you cannot go back to KK.
It has something to do with the new L bootloader. I guess that there is no way of doing this, up to now at least. Don't know if someone has tried and succeeded.
When you have flashed the 5.0.2. OTA however, you can have KK installed back, as most of the users on xda.
dub_1 said:
So, it has been confirmed by several forums that when you have officially received the 5.0.2 OTA download update, you cannot go back to KK. FALSE
It has something to do with the new L bootloader. I guess that there is no way of doing this, up to now at least. Don't know if someone has tried and succeeded. FALSE
When you have flashed the 5.0.2. OTA however, you can have KK installed back, as most of the users on xda.
Click to expand...
Click to collapse
YES you can install kitkat see my signature you NEED a unlocked boot loader
I have been up / down and sideways with ALL 4 versions ( 3 kitkat 1 Lollipop) of XT1068 firmware 50+ installs , a few soft bricks - also installed a few custom roms - gone back to lollipop and kitkat from these too.
see my signature for 4.4.4 and 5.0.2 firmware xt1068
reefuge said:
YES you can install kitkat see my signature you NEED a unlocked boot loader
I have been up / down and sideways with ALL 4 versions ( 3 kitkat 1 Lollipop) of XT1068 firmware 50+ installs , a few soft bricks - also installed a few custom roms - gone back to lollipop and kitkat from these too.
see my signature for 4.4.4 and 5.0.2 firmware xt1068
Click to expand...
Click to collapse
Cheers mate. Already installed stock 4.4.4.
Does it make sense to relock the bootloader?
dub_1 said:
Cheers mate. Already installed stock 4.4.4.
Does it make sense to relock the bootloader?
Click to expand...
Click to collapse
no absolutely not....... boot logo warning still comes up ...warranty still void and strangely if been to 5.0.2 and back to 4.4.4 it wont relock
but you can relock if on 5.0.2
Successful downgrade from 5.0.2 to 4.4.4
Dear All,
Pls help me in downgrading from 5.0.2 to 4.4.4 on my XT1068 Dual Sim Indian Version.
I need to know whether we can return to 4.4.4 without unlocking bootloader and is rooting needed.
Pls let me know your experience in a noob friendly way.
TIA... :angel:
dub_1 said:
Cheers mate. Already installed stock 4.4.4.
Does it make sense to relock the bootloader?
Click to expand...
Click to collapse
What exactly did you do? His signature is gone...
Good Morning all,
When I first time received my Nexus 6, unlocked the bootloader and Rooted with the app for windows Nexus Root Toolkit by Wugfresh, I did not change it to any custom recovery, I left it on stock the rom and I did not install any custom recovery as well., everything is on stock, I just I rooted it.
I've read a lot of things about partitions, downgrades, even OEM Locks and OEM Unlock Bootloaders and people have bricked many devices that I'm afraid to brick it, I'm confused know what steps to follow in order to properly update from lollipop 5.01 to 5.1
I'm on Android 5.01 and received the OTA to update to 5.1, but afraid to press the button in my nexus 6 where it says System Update Available
Should I continue to update with the OTA that I received even if I'm rooted? or should I do it manually with the Nexus Root Toolkit?
What do I need exactly to check / verify before I try to update my device and not brick it?
Please advise
rayosx said:
Good Morning all,
When I first time received my Nexus 6, unlocked the bootloader and Rooted with the app for windows Nexus Root Toolkit by Wugfresh, I did not change it to any custom recovery, I left it on stock the rom and I did not install any custom recovery as well., everything is on stock, I just I rooted it.
I've read a lot of things about partitions, downgrades, even OEM Locks and OEM Unlock Bootloaders and people have bricked many devices that I'm afraid to brick it, I'm confused know what steps to follow in order to properly update from lollipop 5.01 to 5.1
I'm on Android 5.01 and received the OTA to update to 5.1, but afraid to press the button in my nexus 6 where it says System Update Available
Should I continue to update with the OTA that I received even if I'm rooted? or should I do it manually with the Nexus Root Toolkit?
What do I need exactly to check / verify before I try to update my device and not brick it?
Please advise
Click to expand...
Click to collapse
Do not re-lock the bootloader, do not try to downgrade the bootloader. Do not Flash CM12 from the 3/13/2015(not available to download anyways). You should be ok.
If you have stock recovery, sounds like you can flash the OTA...but that is up to you.
Can you describer your system. You said it is STOCK rooted. Did you unlock bootloader? Never flashed anything before?
idtheftvictim said:
Do not re-lock the bootloader, do not try to downgrade the bootloader. Do not Flash CM12 from the 3/13/2015(not available to download anyways). You should be ok.
If you have stock recovery, sounds like you can flash the OTA...but that is up to you.
Can you describer your system. You said it is STOCK rooted. Did you unlock bootloader? Never flashed anything before?
Click to expand...
Click to collapse
Thanks on helping me out,
I'm attaching two shots so you can see all what I have, I have never flashed a custom ROM, just rooted using the wugfresh app for windows,
Also I have in developer options usb debug on and unlocked oem with a check mark.
Again, if you check everything above, I'm on 5.01 and I don't know if just pressing OTA system update button to update from the phone shall brick my phone whether I am rooted, or do I have to be with no root to proceed from there?
Please advice
Sent from my Nexus 6 using XDA Free mobile app
rayosx said:
Thanks on helping me out,
I'm attaching two shots so you can see all what I have, I have never flashed a custom ROM, just rooted using the wugfresh app for windows,
Also I have in developer options usb debug on and unlocked oem with a check mark.
Again, if you check everything above, I'm on 5.01 and I don't know if just pressing OTA system update button to update from the phone shall brick my phone whether I am rooted, or do I have to be with no root to proceed from there?
Please advice
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Looks like you should be fine to install the OTA with no worries.
Please note: I in NO WAY take responsibility for anything that happens to your phone though....sorry...have to put disclaimer
idtheftvictim said:
Looks like you should be fine to install the OTA with no worries.
Please note: I in NO WAY take responsibility for anything that happens to your phone though....sorry...have to put disclaimer
Click to expand...
Click to collapse
Lucky me that I did not press the button to do it through OTA, read below
Can I still take an OTA after I unlock and root?
Answer: On Lollipop, No. On KitKat, yes (sometimes) – if you haven’t made any other system level modifications.
With Lollipop, the OTA update process checks the entire system blob. That means if just one small thing is different about the system partition the OTA will fail. Since rooting itself (regardless of the method: manual/toolkit) installs Superuser as a system app and su binaries to the system partition it inherently breaks OTA’s.
So how should you update a rooted Lollipop device?
1. Wait for the official factory package from google to be released for the build you would like to update to.
2. Backup your apps + data, as a safe measure – in case you end up having to wipe data.
3. Use “Flash Stock + Unroot” and check “No-wipe mode” (to avoid a data wipe).
That’s it. Afterwards you can re-root.
I have the Amazon variant of the 16gb Blu R1 HD. I installed TWRP with the Unlock Tool for all versions tutorial (https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333) on this forum and also removed ads. I would like to get back to the stock bootloader and image for my phone, to receive OTA updates and have the original experience, I am alright with having the ads back, I would just like my phone the exact same way it came from the factory. I know the updated roms will be ported and etc. I would like it back as the way it came, ads and all. (I'm aware I will not get my warranty back.) I read this tutorial: https://forum.xda-developers.com/r1-hd/how-to/firmware-amazon-blu-r1-hd-t3428197 but I'm not sure if it will work with TWRP, I'm confused whether or not fastboot works with TWRP installed. I would also like the bootloader to be locked again as well, I'm not sure whether or not flashing stock firmware would do this. If anyone could help explain this to me or point me to a tutorial somewhere it would be appreciated. I searched through the forum for similar entries, I didn't find anything for the R1 HD specifically, and entries for other phones on removing twrp/flashing stock recovery didn't seem to make sense. I apologize if I missed another post concerning this issue. Thanks.
Ladyslayer said:
I have the Amazon variant of the 16gb Blu R1 HD. I installed TWRP with the Unlock Tool for all versions tutorial (https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333) on this forum and also removed ads. I would like to get back to the stock bootloader and image for my phone, to receive OTA updates and have the original experience, I am alright with having the ads back, I would just like my phone the exact same way it came from the factory. I know the updated roms will be ported and etc. I would like it back as the way it came, ads and all. (I'm aware I will not get my warranty back.) I read this tutorial: https://forum.xda-developers.com/r1-hd/how-to/firmware-amazon-blu-r1-hd-t3428197 but I'm not sure if it will work with TWRP, I'm confused whether or not fastboot works with TWRP installed. If anyone could help explain this to me or point me to a tutorial somewhere it would be appreciated. I searched through the forum for similar entries, I didn't find anything for the R1 HD specifically, and entries for other phones on removing twrp/flashing stock recovery didn't seem to make sense. I apologize if I missed another post concerning this issue. Thanks.
Click to expand...
Click to collapse
this is not quite a normal request.
any and all changes done to your phone are done at your own risk, no guarantee that the process will be "safe". and no guarantee the end result will be as expected.
I can upload stock system, boot, and recovery images.
download them, unzip the file. put the 3 .img files to the phone.
reboot phone to twrp.
select install, browse to the folder you loaded files to, you should not see the file yet. Select flash image in lower part of screen. Now select system.img, on next screen select system and swipe to confirm.
when done do same for boot.img to boot
then recovery to recovery
when all three are done do a wipe(factory reset)
this should bring you back to prime v6.1
be advised that re-locking the boot loader has potential of bricking the pone so it is not advised to do it.
also on all the early versions there are reports that after ota update with unlocked bootloader it caused a bootloop most times it was recoverable by performing "oem unlock" again.
once booted to v6.1 I suspect there will be proper update notice. but if not here is a list of the official update download links.
6.1 to 6.4
http://hwfotadown.mayitek.com/ota/r....4_GENERIC_6.0_20160710-00151468612925207.zip
6.4 to 6.5
http://hwfotadown.mayitek.com/ota/r....5_GENERIC_6.0_20160729-21551470255454500.zip
6.5 to 6.6
http://hwfotadown.mayitek.com/ota/r....6_GENERIC_6.0_20160823-20201472826184648.zip
7.4.2 to 8.4
http://hwfotadown.mayitek.com/ota/r..._V8.4_GENERIC_6.0_20170505-18551493981392.zip
17 to 21
http://hwfotadown.mayitek.com/ota/r...RIC_6.0_20170505-17451495815395129/update.zip
==>>V6.1 images.zip
.
.
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
kfn said:
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
Click to expand...
Click to collapse
well you can go back to locked but it is tricky. Think of it like this.
unlocking , allows anything you put on phone to try and load.
when you re-lock it only properly signed images are allowed to load.
so you can potentially lock yourself out of allowing phone to boot up, so the warning is more relevant when trying to go back to a locked state.
kfn said:
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
Click to expand...
Click to collapse
Sorry guys I have yet to try it out, I don't have a lot of time and am a little nervous to bite the bullet. @kfn, did you follow the guidelines in the above post to restore to original condition or a different set of instructions from somewhere else? Btw any suggestions on how to back up pretty much everything? Sorry Noob here obviously.
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
kfn said:
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
Click to expand...
Click to collapse
Which version update was it?
I can't be certain about the 8.4 or 21 updates, but older ones when that happened you needed to boot into fastboot mode and do oem unlock again.
kfn said:
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
Click to expand...
Click to collapse
Did you re-lock the bootloader or was this because of an unlocked bootloader?
It was a quite a while ago, got 3 partitions from ColtonDRG's thread:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I downloaded from his website, I believe they were 6.1 versions.
At the time 7.4.2 was current firmware, I think phone rebooted few times taking OTA updates. And yes 'fastboot oem unlock' trick worked to get rid off bootloop.
I presume fastboot oem lock might relock bootlader but got scared to try it because of bootloop.
kfn said:
It was a quite a while ago, got 3 partitions from ColtonDRG's thread:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I downloaded from his website, I believe they were 6.1 versions.
At the time 7.4.2 was current firmware, I think phone rebooted few times taking OTA updates. And yes 'fastboot oem unlock' trick worked to get rid off bootloop.
I presume fastboot oem lock might relock bootlader but got scared to try it because of bootloop.
Click to expand...
Click to collapse
Do you still have the phone? Have you done the OTA updates since then with an unlocked bootloader?
did not try another OTA, put back modified ROM and disabled OTA.
Here post #312 with similar unanswered question about relocking bootloader, it is unclear for me if another OTA would properly relock it without bricking.
https://forum.xda-developers.com/r1...tock-rom-6-5-flashed-via-twrp-t3455532/page32
@mrmazak, do you know whether or not installing OTA updates would relock the bootloader? Wouldn't it be possible to do fastboot OEM lock and then do OTA updates without the risk of a bootloop? Noob question: does locking the bootloader reset the phone as well? I seem to have read something about this but I can't remember.
Ladyslayer said:
@mrmazak, do you know whether or not installing OTA updates would relock the bootloader? Wouldn't it be possible to do fastboot OEM lock and then do OTA updates without the risk of a bootloop? Noob question: does locking the bootloader reset the phone as well? I seem to have read something about this but I can't remember.
Click to expand...
Click to collapse
The update has not relocked the bootloader before.
Let me clearify a little.
There are three things I know that get changed when doing OEM unlock
1. Unlock status changed to a yes
2. Secure status changed to a no
3. Warranty status changes to no
After an ota #2 above( secure ) changes back to yes
This conflict is what makes the boot loop. As far as I know.
I do not know what it does when put back to lock and you do an ota.
I think each time you change, lock or unlock it needs to be reset the phone.
mrmazak said:
The update has not relocked the bootloader before.
Let me clearify a little.
There are three things I know that get changed when doing OEM unlock
1. Unlock status changed to a yes
2. Secure status changed to a no
3. Warranty status changes to no
After an ota #2 above( secure ) changes back to yes
This conflict is what makes the boot loop. As far as I know.
I do not know what it does when put back to lock and you do an ota.
I think each time you change, lock or unlock it needs to be reset the phone.
Click to expand...
Click to collapse
Wouldn't it change number one to a no, and two to a yes? What is the likelihood of a bootloop out bricking the phone if I re-lock the bootloader or do an OTA with the bootloader relocked? Isn't that the same as doing a normal OTA with a phone that had no changes from factory version, just the warranty status is a no and that's it?
Ladyslayer said:
Wouldn't it change number one to a no, and two to a yes? What is the likelihood of a bootloop out bricking the phone if I re-lock the bootloader or do an OTA with the bootloader relocked? Isn't that the same as doing a normal OTA with a phone that had no changes from factory version, just the warranty status is a no and that's it?
Click to expand...
Click to collapse
I do not know for sure. And there fore cannot recommend to do it. In the event something goes wrong and bootloader is locked, you cannot use fastboot to flash a repair, there fore MY opinion is the same "DO NOT relock bootloader". If something goes wrong it will be a brick.
Run stock version un modified all you want but if you unlocked I do not think you should relock. My opinion, do as you want.