Related
Hey all,
Sorry for the extremely basic question, I have just been away from Android and flashing ROMs for so long I forgot some really basic stuff. I have a Verizon developer edition with the bootloader unlocked and am currently on Eclipse 3.1.2. I kept getting a Verizon OTA notification and ignoring it, but the other night I accidentally pressed the update button. Now my device keeps rebooting into TWRP. I am kinda glad because I was putting off updating for way too long. So I have a few options as I understand it.
1) Use fastboot files to update to the latest version (4.4.4). I can't find developer edition SBFs (http://sbf.droid-developers.org/phone.php?device=0), do I just use the standard Verizon version?
2) Restore the stock ROM backup I made with TWRP and just use the Verizon OTA.
Is there a downside to either one? Is either one inherently better?
Thanks in advance guys, my life has been pretty heavy recently and I can't believe I lost this basic knowledge.
I_EAT_BABIES said:
Hey all,
Sorry for the extremely basic question, I have just been away from Android and flashing ROMs for so long I forgot some really basic stuff. I have a Verizon developer edition with the bootloader unlocked and am currently on Eclipse 3.1.2. I kept getting a Verizon OTA notification and ignoring it, but the other night I accidentally pressed the update button. Now my device keeps rebooting into TWRP. I am kinda glad because I was putting off updating for way too long. So I have a few options as I understand it.
1) Use fastboot files to update to the latest version (4.4.4). I can't find developer edition SBFs (http://sbf.droid-developers.org/phone.php?device=0), do I just use the standard Verizon version?
2) Restore the stock ROM backup I made with TWRP and just use the Verizon OTA.
Is there a downside to either one? Is either one inherently better?
Thanks in advance guys, my life has been pretty heavy recently and I can't believe I lost this basic knowledge.
Click to expand...
Click to collapse
There is nothing different about the Dev edition SBF vs. the regular XT1060 SBF. Use the standard Verizon version.
Definitely use Option 1. You are at risk of bricking if you choose option 2.
Normally, I would say just SKIP the command "fastboot erase userdata" (to preserve all of your data and apps), but since you are on a custom ROM, you may have issues. You can try it anyways -- if anything goes wrong, just flash the entire SBF again, INCLUDING the fastboot erase userdata command (which will erase everything) and all well be well.
Make sure you use mfastboot instead of regular fastboot.
samwathegreat said:
There is nothing different about the Dev edition SBF vs. the regular XT1060 SBF. Use the standard Verizon version.
Definitely use Option 1. You are at risk of bricking if you choose option 2.
Normally, I would say just SKIP the command "fastboot erase userdata" (to preserve all of your data and apps), but since you are on a custom ROM, you may have issues. You can try it anyways -- if anything goes wrong, just flash the entire SBF again, INCLUDING the fastboot erase userdata command (which will erase everything) and all well be well.
Make sure you use mfastboot instead of regular fastboot.
Click to expand...
Click to collapse
Thanks man! I was going to use RSD for the SBF files, is that not a good idea?
I_EAT_BABIES said:
Thanks man! I was going to use RSD for the SBF files, is that not a good idea?
Click to expand...
Click to collapse
Perfectly fine...but it will erase everything.
Unless, of course you unzip the SBF, edit the XML file with notepad (or similar) and remove the entire line that says "erase userdata".
samwathegreat said:
Perfectly fine...but it will erase everything.
Unless, of course you unzip the SBF, edit the XML file with notepad (or similar) and remove the entire line that says "erase userdata".
Click to expand...
Click to collapse
Hmm, I think I'll just leave it in there and get a perfectly clean install. Thanks for the help man, I cam back in to my room to restore to my old backup and read your response. You potentially saved me from bricking my advice. Thanks!
I_EAT_BABIES said:
Hmm, I think I'll just leave it in there and get a perfectly clean install. Thanks for the help man, I cam back in to my room to restore to my old backup and read your response. You potentially saved me from bricking my advice. Thanks!
Click to expand...
Click to collapse
You are welcome. A few other thoughts: the potential to brick only comes if either the bootloader or partition table are mismatched. This can happen during a failed OTA install.
In addition to that, even if you DID restore the twrp backup successfully, you still couldn't take the OTA. Remember: STOCK recovery is required to accept any OTAs. It would have continued to boot-loop.
Once you finish with RSD Lite, just use fastboot to flash custom recovery back on. Use the latest version of TWRP, find it here: http://techerrata.com/browse/twrp2/ghost
Just: fastboot flash recovery twrp_file_name.img
Then, IMMEDIATELY afterwards, type: fastboot reboot-bootloader
Next, VOL DOWN to highlight recovery, and VOL UP to boot into it.
If you don't immediately boot into TWRP after flashing it, it won't "stick" (we don't know why...but as long as you do this, it will stick permanently, or until you flash something else to recovery).
As you probably already know, as soon as you go to exit TWRP it will offer to root for you.
Good Luck! Update us to success.
P.S. -- Sent you a PM.
I tried this with the VZW imgs and now I get the unlocked bootloader warning. I don't recall getting that before, thoughts?
I assume it's because the imgs are not developer edition ones.
onepoint said:
I tried this with the VZW imgs and now I get the unlocked bootloader warning. I don't recall getting that before, thoughts?
I assume it's because the imgs are not developer edition ones.
Click to expand...
Click to collapse
The unlocked warning is no big deal I get it on my 4.4.3 GSM Developer Edition.
onepoint said:
I tried this with the VZW imgs and now I get the unlocked bootloader warning. I don't recall getting that before, thoughts?
I assume it's because the imgs are not developer edition ones.
Click to expand...
Click to collapse
Nope, it's not. Likely, you had flashed a new logo.bin that "masked" the unlocked bootloader warning. Once again, the images are no different. Not one single byte different. None.
If you dislike (I like it, personally) the unlocked BL message, simply flash a replacement logo.bin.
See here for details: http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
I realize that it says it is for 4.4.3, but it should be fully compatible with 4.4.4 as well.
And one more time: EVEN THE DEV EDITION shows the "unlocked bootloader message" when unlocked. Completely normal. Only flashing a replacement logo.bin will prevent it from showing up.
Hi all:
After upgrading my unlocked-but-still-rooted Turbo to Motorola stock Marshmallow, my Android Pay no longer works; I get the message about Android not be able to verify etc. From what I understand, SafetyNet now checks for unlocked bootloaders, not just root. Also, from what I understand, Sultanxda found a workaround by modifying the Android kernel, which they have working on the OP3.
Does anyone know if anyone is working on this for the original Turbo, and/or could someone kindly point me in the right direction?
Thanks in advance.
Workaround info: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/
phraxen said:
Hi all:
After upgrading my unlocked-but-still-rooted Turbo to Motorola stock Marshmallow, my Android Pay no longer works; I get the message about Android not be able to verify etc. From what I understand, SafetyNet now checks for unlocked bootloaders, not just root. Also, from what I understand, Sultanxda found a workaround by modifying the Android kernel, which they have working on the OP3.
Does anyone know if anyone is working on this for the original Turbo, and/or could someone kindly point me in the right direction?
Thanks in advance.
Workaround info: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/
Click to expand...
Click to collapse
Some of the CM-based ROMs floating around address this issue, but there is no way to use stock marshmallow with an unlocked bootloader and pass safetynet. So if you want android pay, your options are to stay on SU4TL-49 or install one of the CM-based ROMs that have implemented a workaround.
I got around this issue by using my credit card company's app instead of Android Pay. It allows me to do wireless payments everywhere Android Pay is accepted, but it only checks for root. It does not use safetynet.
Too late for you now, but recently someone in this forum updated to Marshmallow radio, but did NOT flash the Marshmallow bootloader. They were already using custom ROM. Others using that ROM who flashed Marshmallow bootloader no longer pass safetynet, but that person does. The conclusions is an unlocked Marshmallow bootloader or newer is what Safetynet looks for?
And yes, I've flashed both Marshmallow bootloader and radios over both my daily XT1225. I could only test the theory by breaking out my new-in-box third Quark, which have for emergency back-up -- and is which still probably on Kitkat.
While I previously had the older Google Wallet, Android Pay for me is not as important as controlling my own phone as I please. My phones will always be rooted. And in the Moto Quark, unlocking the bootloader is necessary for permanent root, whereas it's not necessary in some other phones -- like LG. But whatever needs to be done to root my phones, I will. And if Android Pay is not possible, so be it. I always carry my wallet when I go out somewhere. Pulling out my phone, pulling out my wallet, what's the difference?
phraxen said:
Hi all:
After upgrading my unlocked-but-still-rooted Turbo to Motorola stock Marshmallow, my Android Pay no longer works; I get the message about Android not be able to verify etc. From what I understand, SafetyNet now checks for unlocked bootloaders, not just root. Also, from what I understand, Sultanxda found a workaround by modifying the Android kernel, which they have working on the OP3.
Does anyone know if anyone is working on this for the original Turbo, and/or could someone kindly point me in the right direction?
Thanks in advance.
Workaround info: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/
Click to expand...
Click to collapse
So actually there is a way to get safetynet working again. All you have to do is flash the SU4TL-49 bootloader and wipe cache. I'll be posting the bootloader separately when I get a chance, but if you don't want to wait that long, download the full firmware package here: https://mega.nz/#!i84inDgI!IM_A_IpLlKfGpC90S2DPB6g9t8rVkhO8heE4o_WpdMI, extract bootloader.img and flash using fastboot.
fastboot flash motoboot bootloader.img
fastboot erase cache
EDIT: Here is a flashable zip that will flash the bootloader for you for those who are so inclined. Make sure to wipe cache and dalvik/art cache in TWRP afterwards: https://mega.nz/#!6logEaIQ!q8qPJw65Upt38Hxiu1JyxErmwbgL7CBzuGzzPC0C9pQ
EDIT 2: And here is the bootloader.img taken from the SU4TL-49 package if fastboot is your weapon of choice: https://mega.nz/#!iogRGIrQ!ixpZGw1cR90jLxe9r8EAt76SGNoSqVqSv1iu0v14QCc
TheSt33v said:
So actually there is a way to get safetynet working again. All you have to do is flash the SU4TL-49 bootloader and wipe cache. I'll be posting the bootloader separately when I get a chance, but if you don't want to wait that long, download the full firmware package here: https://mega.nz/#!i84inDgI!IM_A_IpLlKfGpC90S2DPB6g9t8rVkhO8heE4o_WpdMI, extract bootloader.img and flash using fastboot.
fastboot flash motoboot bootloader.img
Remember to wipe cache afterwards.
Click to expand...
Click to collapse
I'm confused... isn't that downgrading the bootloader?
ChazzMatt said:
I'm confused... isn't that downgrading the bootloader?
Click to expand...
Click to collapse
Yes it is. And as long as your bootloader is unlocked, no harm no foul. I thought that downgrading the bootloader was the one thing that you couldn't do even if it was unlocked, but I just did it and I'm passing safetynet now, so I guess I was wrong.
If anyone wants proof I'm on the SU4TL-49 bootloader, I can take a picture when I get home. I don't know of a way to get a picture of the bootloader screen using only my phone.
TheSt33v said:
Yes it is. And as long as your bootloader is unlocked, no harm no foul. I thought that downgrading the bootloader was the one thing that you couldn't do even if it was unlocked, but I just did it and I'm passing safetynet now, so I guess I was wrong.
Click to expand...
Click to collapse
Learn something new everyday. Wow.
You just can't downgrade a locked bootloader, eh?
Thank you!
When I get home will try Lollipop bootloader on my XT1225.
The custom ROM guys will love this, then.
ChazzMatt said:
Learn something new everyday. Wow.
You just can't downgrade a locked bootloader, eh?
Thank you!
When I get home will try Lollipop bootloader on my XT1225.
The custom ROM guys will love this, then.
Click to expand...
Click to collapse
I seem to remember trying this a long time ago using TWRP, and TWRP was unable to flash the older bootloader. It works fine through fastboot though. I'm going to do some more investigation when I'm not at work to see if I can get TWRP to do this. That would be easier for most people.
Also, I thought the latest iSu already got around this issue. That's what BHB's command line patch thing is for. But it will certainly make things easier!
TheSt33v said:
I seem to remember trying this a long time ago using TWRP, and TWRP was unable to flash the older bootloader. It works fine through fastboot though. I'm going to do some more investigation when I'm not at work to see if I can get TWRP to do this. That would be easier for most people.
Also, I thought the latest iSu already got around this issue. That's what BHB's command line patch thing is for. But it will certainly make things easier!
Click to expand...
Click to collapse
I was on the latest bootloader and just flashed the .47 bootloader because of major radio issues. I flashed from TWRP and have been doing it since the .49 update.
gumbi2647 said:
I was on the latest bootloader and just flashed the .47 bootloader because of major radio issues. I flashed from TWRP and have been doing it since the .49 update.
Click to expand...
Click to collapse
Interesting. I've noticed that TWRP randomly has issues with flashing things on my phone for some reason, and a reboot often fixes the issue. Maybe I just got unlucky that one time, but if that's the case, I'll have a flashable SU4TL-49 bootloader up a few minutes after I get home.
TheSt33v said:
Interesting. I've noticed that TWRP randomly has issues with flashing things on my phone for some reason, and a reboot often fixes the issue. Maybe I just got unlucky that one time, but if that's the case, I'll have a flashable SU4TL-49 bootloader up a few minutes after I get home.
Click to expand...
Click to collapse
IF you can flash through TWRP, then clearing caches is no problem in TWRP. IF we must use ADB, please include instructions to also clear caches that way, in any write-up -- if that's what you mean?
Or you do you mean flash bootloader in ADB, then immediately boot into TWRP and clear caches -- before booting back to system?
ChazzMatt said:
IF you can flash through TWRP, then clearing caches is no problem in TWRP. IF we must use ADB, please include instructions to also clear caches that way, in any write-up -- if that's what you mean?
Or you do you mean flash bootloader in ADB, then immediately boot into TWRP and clear caches -- before booting back to system?
Click to expand...
Click to collapse
ADB is not involved. Only fastboot.
The way I did it on my phone (XT1254 unrooted, unlocked, 100% stock MM) exactly was this:
1. Make note of BL version on bootloader screen.
2. fastboot flash motoboot bootloader.img using the SU4TL-49 bootloader.
3. Reboot bootloader
4. Confirm that the BL version has changed (it did)
5. Reboot to system.
6. Tried safetynet (failed)
7. Reboot to stock MM recovery menu
8. Wipe cache, reboot to system
9. Tried safetynet (passed), added a bunch of cards in Android Pay without issue
I'm assuming that wiping cache using other methods will be just as effective, but I don't know that for sure.
TheSt33v said:
ADB is not involved. Only fastboot.
The way I did it on my phone (unrooted, unlocked, 100% stock MM) exactly was this:
1. Make note of BL version on bootloader screen.
2. fastboot flash motoboot bootloader.img using the SU4TL-49 bootloader.
3. Reboot bootloader
4. Confirm that that BL version has changed (it did)
5. Reboot to system.
6. Tried safetynet (failed)
7. Reboot to stock MM recovery menu
8. Wipe cache, reboot to system
9. Test safetynet (passed)
I'm assuming that wiping cache using other methods will be just as effective, but I don't know that for sure.
Click to expand...
Click to collapse
Which version of TWRP are you using? I heard the 04 update has some issues. I have been on 03 forever.
gumbi2647 said:
Which version of TWRP are you using? I heard the 04 update has some issues. I have been on 03 forever.
Click to expand...
Click to collapse
04, so that could be it.
I post this around XDA, new bootloader add a new prop line
it add
[ro.boot.flash.locked]: [0]
And I patch that with this
https://www.androidfilehost.com/?fid=745425885120696423
with will change that to
[ro.boot.flash.locked]: [1]
Just use adb command
Code:
getprop | grep ro.boot.flash.locked
to check.
and then cts will not fail so is not really need to downgrade for now, There is the chance that Moto will change the boot.img so it can't boot on old bootloader, that did not happens yet on quark but others Moto device is need latest bootloader with latest ROM.
But then again may never be a update from Moto to this device.
So as long Moto did not make another patch flash this in TWRP and test with latest bootloader
https://www.androidfilehost.com/?fid=745425885120696423
of course that will not fix any other CTS fail like xposed or ROOT
So let me know if that helps if not it may be somethings else that can also be patched.
TheSt33v said:
So actually there is a way to get safetynet working again. All you have to do is flash the SU4TL-49 bootloader and wipe cache. I'll be posting the bootloader separately when I get a chance, but if you don't want to wait that long, download the full firmware package here: https://mega.nz/#!i84inDgI!IM_A_IpLlKfGpC90S2DPB6g9t8rVkhO8heE4o_WpdMI, extract bootloader.img and flash using fastboot.
fastboot flash motoboot bootloader.img
fastboot erase cache
Click to expand...
Click to collapse
Thanks for this. I'll give it a shot and let you know how it turns out.
bhb27;70506510So as long Moto did not make another patch flash this in TWRP and test with latest bootloader
[url said:
https://www.androidfilehost.com/?fid=745425885120696423[/url]
of course that will not fix any other CTS fail like xposed or ROOT
So let me know if that helps if not it may be somethings else that can also be patched.
Click to expand...
Click to collapse
Thanks! Flashing that works just fine. So now we have 2 options.
bhb27 said:
I post this around XDA, new bootloader add a new prop line
it add
[ro.boot.flash.locked]: [0]
And I patch that with this
https://www.androidfilehost.com/?fid=745425885120696423
with will change that to
[ro.boot.flash.locked]: [1]
Just use adb command
Code:
getprop | grep ro.boot.flash.locked
to check.
and then cts will not fail so is not really need to downgrade for now, There is the chance that Moto will change the boot.img so it can't boot on old bootloader, that did not happens yet on quark but others Moto device is need latest bootloader with latest ROM.
But then again may never be a update from Moto to this device.
So as long Moto did not make another patch flash this in TWRP and test with latest bootloader
https://www.androidfilehost.com/?fid=745425885120696423
of course that will not fix any other CTS fail like xposed or ROOT
So let me know if that helps if not it may be somethings else that can also be patched.
Click to expand...
Click to collapse
That worked for me. I was able to add a debit card without getting the error.
Thanks to you and TheSt33v.
ChazzMatt said:
IF you can flash through TWRP, then clearing caches is no problem in TWRP. IF we must use ADB, please include instructions to also clear caches that way, in any write-up -- if that's what you mean?
Or you do you mean flash bootloader in ADB, then immediately boot into TWRP and clear caches -- before booting back to system?
Click to expand...
Click to collapse
Have you tried this using TWRP and if so did everything go well
Sent from my XT1254 using Tapatalk
joekitch said:
Have you tried this using TWRP and if so did everything go well
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I have not personally tried it yet. Someone else can answer if they have?
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.
For Complete Root howto please read this post
==============================================================
Quick root howto for Realme X2
What is written below is for both CN and EU versions, but the files attached are for CN only!
Please pay attention that files attached are version-specific
Credits: Magisk (@topjohnwu), TWRP for Realme X2 (@mauronofrio)
Unlock the bootloader with a help of apk file
Install Magisk manager apk to your stock system
Enter fastboot mode and perform there:
fastboot flash --disable-verification vbmeta vbmeta.img
fastboot flash boot magisk_patched.img
fastboot reboot
EDIT/NOTE
In order to have Magisk out of Core Only Mode:
boot into TWRP, mount SYSTEM in RW mode and from the computer perform
Code:
adb shell "cat /system/build_19771.prop >> /system/build.prop"
adb reboot
For EU version (RMX1993) you should replace 19771 with 19672 in the filename.
EDIT 2
I attach here a file with A.13 version boot image patched for magisk. Of course, you should change the file name in the howto above, the line with fastboot flash boot ...
In the next few days I hope to provide more detailed Root howto, thus there will be no dependency on any files from here for the next version releases.
EDIT 3
Here comes the next version A.14. Please find the corresponding file attached. vbmeta.img stays identical for all versions.
Thanku
通过我的 RMX1991 上的 Tapatalk发言
I've tested it. I passed it perfectly
通过我的 RMX1991 上的 Tapatalk发言
---------- Post added at 10:51 PM ---------- Previous post was at 10:50 PM ----------
怎样才能在twrp 里刷入magisk ？
通过我的 RMX1991 上的 Tapatalk发言
Does using this disable the fingerprint scanner?
gwiqu said:
Does using this disable the fingerprint scanner?
Click to expand...
Click to collapse
Of course. Even before this, when bootloader is unlocked, it stops working
Does the 1993 version need a different vbmeta?
surferbyter said:
Does the 1993 version need a different vbmeta?
Click to expand...
Click to collapse
vbmeta.img files are identical in the current ROMs for CN (A.12) and EU (A.15)
yakovpol said:
Of course. Even before this, when bootloader is unlocked, it stops working
Click to expand...
Click to collapse
Is there any way to have the finger print scanner back?
yakovpol said:
vbmeta.img files are identical in the current ROMs for CN (A.12) and EU (A.15)
Click to expand...
Click to collapse
Excellent, I have already tried the root without installing the twrp. then waiting for better times I restored stock locking up the bootloader. Here on the forum regarding the root guides, there are two and there is some confusion for a neophyte who wants to try his hand at mod. It would need only one clear and complete, perhaps integrating it with the procedure for restoring stock if one wanted to go back. For now I'm working like crazy, for example tonight night shift. but as soon as I have some time I will try to make a draft.
Unlocking guide with:
links and steps to follow for using the tool, (deep start test)
commands for dump recovery stock, (dd if)
links to files and commands for the flash of vbmeta and magisk,
link to the file and commands for the TWRP flash.
Guide to stock recovery with:
links and commands for the recovery stock flash,
link to the official rom to flash with the recovery stock,
Command to lock the bootloader,
links and steps for using the tool, (exit from the deep test)
in the end they would put the XDA threads links to any custom roms, for example starting from this one.
surferbyter said:
Excellent, I have already tried the root without installing the twrp. then waiting for better times I restored stock locking up the bootloader. Here on the forum regarding the root guides, there are two and there is some confusion for a neophyte who wants to try his hand at mod. It would need only one clear and complete, perhaps integrating it with the procedure for restoring stock if one wanted to go back. For now I'm working like crazy, for example tonight night shift. but as soon as I have some time I will try to make a draft.
Unlocking guide with:
links and steps to follow for using the tool, (deep start test)
commands for dump recovery stock, (dd if)
links to files and commands for the flash of vbmeta and magisk,
link to the file and commands for the TWRP flash.
Guide to stock recovery with:
links and commands for the recovery stock flash,
link to the official rom to flash with the recovery stock,
Command to lock the bootloader,
links and steps for using the tool, (exit from the deep test)
in the end they would put the XDA threads links to any custom roms, for example starting from this one.
Click to expand...
Click to collapse
Thank you for good advice! I am a hobbyist, not a professional. I have numerous obligations too. But I shall do my best.
I tried the deeptest apk, and when I enter start the in-depth test, the phone reboots, enters the fastboot mode for 1 second and the reboots again normally. What's the issue here?
wasi006 said:
I tried the deeptest apk, and when I enter start the in-depth test, the phone reboots, enters the fastboot mode for 1 second and the reboots again normally. What's the issue here?
Click to expand...
Click to collapse
Evidently, you did not succeed with entering fastboot. Check if OEM unlock is enabled in Developer Settings and try again with DeepTesting app
Happiest new is that Fingerprint is working after bootloader unlocking (After A13 Update).
mishal.sarwar1 said:
Happiest new is that Fingerprint is working after bootloader unlocking (After A13 Update).
Click to expand...
Click to collapse
Is this true can anyone confirm this on Indian Variant I restricted myself from buying this phone because I read that in realme phones the Fingerprint will stop working after unlocking the bootloader. If that's not the case I'll buy myself one :laugh:
njaya95 said:
Is this true can anyone confirm this on Indian Variant I restricted myself from buying this phone because I read that in realme phones the Fingerprint will stop working after unlocking the bootloader. If that's not the case I'll buy myself one :laugh:
Click to expand...
Click to collapse
Realme Authority is now concern about it. You can wait for a while or can buy it.
I don't know about indian varient. Chinese one is now working great with unlocked bootloader.
mishal.sarwar1 said:
Realme Authority is now concern about it. You can wait for a while or can buy it.
I don't know about indian varient. Chinese one is now working great with unlocked bootloader.
Click to expand...
Click to collapse
I mean the fp??? Is it working or not???
njaya95 said:
I mean the fp??? Is it working or not???
Click to expand...
Click to collapse
Its working on Chinese one but not tested on Indian varrient, but it should work.
narshi shukla said:
Its working on Chinese one but not tested on Indian varrient, but it should work.
Click to expand...
Click to collapse
Thanks for the reply bro, will buy the phone when it's back in stock.
For A14 please
Can anyone confirm if the fingerprint is still working after unlocking bootloader for A14?
It will make a huge difference for me
Hello to eveyone.
I have been searching the forum for a spefic guide to:
Unlock bootloader
install TWRP
flash magisk
To my beloved lg v40 from Sprint that I sucessfully crossflashed to the Korean firmware that has android 10.
Now my phone's information is the following:
Software version: V409NUA30b
Model number: LM-V409NUA (used to be V405UA)
Again, im running android 10. I just want to root it so I can control the processor to get a better performance in gaming (dolphin emulator).
Thanks in advance for any help...
quote:
Hi man, thanks for your quick answer. Sorry that I posted my question in the wrong section. I wasn't sure if it had to be posted here or in Q&A, Ur right! I just picked the wrong option.
Yes! My phone has the software version V409NUA30b, it is the latest I could find when I decided to flash it to my phone I was happy with it until I found out that somehow the phone limits the processor's performance when it gets to certain temperature specifically when I use dolphin or cirtra emulators, tha's why i want to root it. But it seems It cannot be done unless you install TWRP, which also needs to have the bootloader unlocked.
I believe I won't get any OTA updates due to crossflashing and also because I am based in the republic of Panama.
I read the thread you are refering to and I saw that the files given to use QFIL are for Oreo and also the author suggested that they are not supposed to work with Pie, even though some people has been able to use them.
That is why I thought that the guide did no apply to my phone.
I am going to follow your advice and post this question in the right place.
If you know anything else, please do not hesitate in letting me know.
thanks again!
/quote
So, first, the guide you're referring to does have a few Pie files attached to it, but that's because the author was on Pie when he wrote it. The procedure he describes works for all versions of android, including Q.
So it certainly does apply, just be sure to save off your own abl and laf partitions prior to writing over them or erasing them. And also your boot partition, and for good measure, save ftm, fsg, modem, modemst1 and modemst2, they contain specific imei and s/n info for your specific / individual phone.
Also, there will never again be updates, lg is out of phone business, so forget that
check this thread for some additional info and files you will need. I'd suggest use lgup to go to 30f, that way you'll at least have the last security patch available.
cheers
AsItLies said:
quote:
Hi man, thanks for your quick answer. Sorry that I posted my question in the wrong section. I wasn't sure if it had to be posted here or in Q&A, Ur right! I just picked the wrong option.
Yes! My phone has the software version V409NUA30b, it is the latest I could find when I decided to flash it to my phone I was happy with it until I found out that somehow the phone limits the processor's performance when it gets to certain temperature specifically when I use dolphin or cirtra emulators, tha's why i want to root it. But it seems It cannot be done unless you install TWRP, which also needs to have the bootloader unlocked.
I believe I won't get any OTA updates due to crossflashing and also because I am based in the republic of Panama.
I read the thread you are refering to and I saw that the files given to use QFIL are for Oreo and also the author suggested that they are not supposed to work with Pie, even though some people has been able to use them.
That is why I thought that the guide did no apply to my phone.
I am going to follow your advice and post this question in the right place.
If you know anything else, please do not hesitate in letting me know.
thanks again!
/quote
So, first, the guide you're referring to does have a few Pie files attached to it, but that's because the author was on Pie when he wrote it. The procedure he describes works for all versions of android, including Q.
So it certainly does apply, just be sure to save off your own abl and laf partitions prior to writing over them or erasing them. And also your boot partition, and for good measure, save ftm, fsg, modem, modemst1 and modemst2, they contain specific imei and s/n info for your specific / individual phone.
Also, there will never again be updates, lg is out of phone business, so forget that
check this thread for some additional info and files you will need. I'd suggest use lgup to go to 30f, that way you'll at least have the last security patch available.
cheers
Click to expand...
Click to collapse
Thanks again man.
So i was able to update to V4009NUA30f. Thank you for letting me know there was a new version.
I followed the process to unlock the bootloader but somehow I am unable to get into bootloader / fastboot mode. When I flash the v35eng.img to the abl_a it seems to be ok according to Qfill. But my bootloader does not seem to exist in the phone.
I tried to boot the phone into bootloader using adb reboot bootloader but it only restarts the phone.
Do you have an idea what could be wrong?
Thanks!
pichulo said:
Thanks again man.
So i was able to update to V4009NUA30f. Thank you for letting me know there was a new version.
I followed the process to unlock the bootloader but somehow I am unable to get into bootloader / fastboot mode. When I flash the v35eng.img to the abl_a it seems to be ok according to Qfill. But my bootloader does not seem to exist in the phone.
I tried to boot the phone into bootloader using adb reboot bootloader but it only restarts the phone.
Do you have an idea what could be wrong?
Thanks!
Click to expand...
Click to collapse
yes, yer flashing it to the inactive slot. The thing about the v35 eng abl, when you have it flashed (to the correct slot), your phone won't boot. It will only be able to go to fastboot.
In your case, the phone is booting, so you have to be flashing v35 eng abl to the wrong slot. It's the other one that's active.
cheers
AsItLies said:
yes, yer flashing it to the inactive slot. The thing about the v35 eng abl, when you have it flashed (to the correct slot), your phone won't boot. It will only be able to go to fastboot.
In your case, the phone is booting, so you have to be flashing v35 eng abl to the wrong slot. It's the other one that's active.
cheers
Click to expand...
Click to collapse
OK! So I guess we are talking about the abl_b, right!?
Also, I saw in the other link you sent me the twrp+boot image. Once I unlock the bootloader and flash my back up abl file, then I would have to flash it (the twrp+boot) to the abl_b slot again right!?
pichulo said:
OK! So I guess we are talking about the abl_b, right!?
Also, I saw in the other link you sent me the twrp+boot image. Once I unlock the bootloader and flash my back up abl file, then I would have to flash it (the twrp+boot) to the abl_b slot again right!?
Click to expand...
Click to collapse
No no no. You never flash an image to an incorrect partition. Abl partitions get abl images, boot partitions get boot images. Don't mix them up!