Related
After installing twrp using the one click root method, it restarted my V20 and I ended up in recovery mode (TWRP) and unable to boot into the OS. It seems I only have access to fastboot, download mode, and TWRP at this moment. I tried flashing the partitions with twrp, but twrp isn't realing my SD card for some odd reason, and I don't believe theres another way to move the file directly to the phone. I've been trying to work with "LG FlashTool" for hours, and keep getting the same error. Is there a reliable way to flash the OS through download mode? Thanks!
There is currently no way to flash those .tot images. What happens when you try to boot, where does it get stuck?
In TWRP you can connect to a PC and access the storage. Did you try moving the files that way?
slayerh4x said:
There is currently no way to flash those .tot images. What happens when you try to boot, where does it get stuck?
In TWRP you can connect to a PC and access the storage. Did you try moving the files that way?
Click to expand...
Click to collapse
I apologize for not checking my XDA notifications frequently enough.
I was able to copy over the .img system, boot, and recovery files to my internal storage when I was booted into TWRP then flashed them in TWRP.
Thanks for the help!
KingofPineCones said:
I apologize for not checking my XDA notifications frequently enough.
I was able to copy over the .img system, boot, and recovery files to my internal storage when I was booted into TWRP then flashed them in TWRP.
Thanks for the help!
Click to expand...
Click to collapse
I tried doing this and my system rebooted back into TWRP. Where did you get the files? Also did you ever get the encryption unsuccessful error? Whenever I install a system image or nandroid backup my phone reboots into TWRP.
crazyc78 said:
I tried doing this and my system rebooted back into TWRP. Where did you get the files? Also did you ever get the encryption unsuccessful error? Whenever I install a system image or nandroid backup my phone reboots into TWRP.
Click to expand...
Click to collapse
The encryption unsuccessful error was mentioned in the original TWRP form, you're just supposed to tap cancel and ignore it. It seems to happen every time you boot into TWRP. As for the .IMG files, I forgot where I got these but as soon as I find the post I'll be sure to give the creator credit. These worked perfectly for my H918.
Link to .zip file with the .img file-
https://drive.google.com/file/d/0B53iMlcsyyiKenAtT2k5STl0Umc/view?usp=drivesdk
(On mobile app or else I would've embedded it)
Boot into TWRP and push them through ADB into your device, then flash with TWRP. Make sure to flash system and recovery together, THEN REBOOT. If you flash system or recovery apart then reboot it might not work. I pushed them to /data/ and it worked for me. system.img is about 4GB if I remember correctly, so that one took a long time to push through ADB, about an hour and a half, just be prepared to wait a bit. Good luck!
KingofPineCones said:
The encryption unsuccessful error was mentioned in the original TWRP form, you're just supposed to tap cancel and ignore it. It seems to happen every time you boot into TWRP. As for the .IMG files, I forgot where I got these but as soon as I find the post I'll be sure to give the creator credit. These worked perfectly for my H918.
Link to .zip file with the .img file-
https://drive.google.com/file/d/0B53iMlcsyyiKenAtT2k5STl0Umc/view?usp=drivesdk
(On mobile app or else I would've embedded it)
Boot into TWRP and push them through ADB into your device, then flash with TWRP. Make sure to flash system and recovery together, THEN REBOOT. If you flash system or recovery apart then reboot it might not work. I pushed them to /data/ and it worked for me. system.img is about 4GB if I remember correctly, so that one took a long time to push through ADB, about an hour and a half, just be prepared to wait a bit. Good luck!
Click to expand...
Click to collapse
Thanks I appreciate the response, I was able to get my phone up and running by flashing a deodexed rom.
What are the commands to flash the stock system, boot image and recovery through fastboot? Is that what you used?
KingofPineCones said:
The encryption unsuccessful error was mentioned in the original TWRP form, you're just supposed to tap cancel and ignore it. It seems to happen every time you boot into TWRP. As for the .IMG files, I forgot where I got these but as soon as I find the post I'll be sure to give the creator credit. These worked perfectly for my H918.
Link to .zip file with the .img file-
https://drive.google.com/file/d/0B53iMlcsyyiKenAtT2k5STl0Umc/view?usp=drivesdk
(On mobile app or else I would've embedded it)
Boot into TWRP and push them through ADB into your device, then flash with TWRP. Make sure to flash system and recovery together, THEN REBOOT. If you flash system or recovery apart then reboot it might not work. I pushed them to /data/ and it worked for me. system.img is about 4GB if I remember correctly, so that one took a long time to push through ADB, about an hour and a half, just be prepared to wait a bit. Good luck!
Click to expand...
Click to collapse
So I downloaded this file you have in the reply... How can I flash the files in the zip through Fastboot? This currently is the only thing I can boot into to modify the system. The phone boots fine, but I cannot use ADB because it won't authorize the device. I have repeatedly tried killing the ADB server and restarting it, changed the USB ports to no avail... At this point, I cannot boot into TWRP even though it should be operational still.
andrewjt19 said:
So I downloaded this file you have in the reply... How can I flash the files in the zip through Fastboot? This currently is the only thing I can boot into to modify the system. The phone boots fine, but I cannot use ADB because it won't authorize the device. I have repeatedly tried killing the ADB server and restarting it, changed the USB ports to no avail... At this point, I cannot boot into TWRP even though it should be operational still.
Click to expand...
Click to collapse
Which TWRP version do you have? Is it RC8 or above? If its not then you are stuck until the TOT files can be used in LG UP or if we get a KDZ (Havent checked recently if a KDZ is available).
If you do there is a fail safe in TWRP (RC8 and above) that you boot to the LG factory reset and go through with it, TWRP does not execute the command and just boots to TWRP.
DarkestSpawn said:
Which TWRP version do you have? Is it RC8 or above? If its not then you are stuck until the TOT files can be used in LG UP or if we get a KDZ (Havent checked recently if a KDZ is available).
If you do there is a fail safe in TWRP (RC8 and above) that you boot to the LG factory reset and go through with it, TWRP does not execute the command and just boots to TWRP.
Click to expand...
Click to collapse
I'm running the latest version of TWRP not the RC8.
andrewjt19 said:
I'm running the latest version of TWRP not the RC8.
Click to expand...
Click to collapse
ONLY USE THIS METHOD IF YOU HAVE TWRP RC8 OR ABOVE INSTALLED!!!!! OTHERWISE YOU WILL ACTUALLY FACTORY RESET YOUR DEVICE!!!!!
While the device is powered off, press and hold Vol - and Power button. When you see the LG logo quickly release only the power button and re-press and hold the power button (Never let go of the Vol - button) This will boot you into the LG Factory reset screen. ONLY USE THIS METHOD IF YOU HAVE TWRP RC8 OR ABOVE INSTALLED!!!!! OTHERWISE YOU WILL ACTUALLY FACTORY RESET YOUR DEVICE!!!!! Choose yes to both options and you will be rebooted into TWRP. TWRP intercepts this command and ignores the factory reset part.
Will definitely give a shot. Thanks. I'll report back when I get to do it...
what are commands to flash the sys files
I have a LG K20 plus with t mobile as the carrier. I believe the model should be TP260. I mistakenly restored a twrp backup from a metro pcs phone that I got from this site coincidentally. Now my phone drops calls and data frequently and shows metro pcs on bootup vs tmobile. I have a kdz file but it won't flash because it now also thinks the model is MP260...not TP260 and says it's a mismatch. Any ideas on how I can get a restore for tmobile to try to reset the phone?
Just bumping
i could use a restore too. I installed super SU root and lost access to android pay. I wasnt to try that magisk root
I restored mine with the linked files.
install LG driver (uninstall any other drivers first)
install LGUP
remove battery from phone and replace
hold volume up key
insert USB while holding down volume up key
phone will boot to download mode
drivers will find phone
run UPPERCUT.exe
UPPERCUT.exe will launch LGUP with phone connected. if phone is not connected try again.
in LGUP lower window browse to TP26010k_00_0316.kdz
choose UPGRADE option in LGUP
click START in LGUP
factory ROM and Recovery will be installed, bootloader will still be unlocked
https://drive.google.com/open?id=0BygTApD1iNSSb3pCcU9RRlV1MVE
magisk can be installed using the same method as superSU. Mine is working along with AndroidPay
colemanimal said:
I restored mine with the linked files.
install LG driver (uninstall any other drivers first)
install LGUP
remove battery from phone and replace
hold volume up key
insert USB while holding down volume up key
phone will boot to download mode
drivers will find phone
run UPPERCUT.exe
UPPERCUT.exe will launch LGUP with phone connected. if phone is not connected try again.
in LGUP lower window browse to TP26010k_00_0316.kdz
choose UPGRADE option in LGUP
click START in LGUP
factory ROM and Recovery will be installed, bootloader will still be unlocked
https://drive.google.com/open?id=0BygTApD1iNSSb3pCcU9RRlV1MVE
magisk can be installed using the same method as superSU. Mine is working along with AndroidPay
Click to expand...
Click to collapse
You were able to install TWRP after this process with the TP26010k_00_0316.kdz?
I am on TP26010E and don't want to upgrade to TP26010k if TWRP cannot be flashed as it has been stated here.
Yeah, you have to perform OEM unlock again, but I have been able to flash TWRP after flashing the previously attached .kdz with the LGUP tool
colemanimal said:
I restored mine with the linked files.
install LG driver (uninstall any other drivers first)
install LGUP
remove battery from phone and replace
hold volume up key
insert USB while holding down volume up key
phone will boot to download mode
drivers will find phone
run UPPERCUT.exe
UPPERCUT.exe will launch LGUP with phone connected. if phone is not connected try again.
in LGUP lower window browse to TP26010k_00_0316.kdz
choose UPGRADE option in LGUP
click START in LGUP
factory ROM and Recovery will be installed, bootloader will still be unlocked
https://drive.google.com/open?id=0BygTApD1iNSSb3pCcU9RRlV1MVE
magisk can be installed using the same method as superSU. Mine is working along with AndroidPay
Click to expand...
Click to collapse
Can I install this kdz from twrp and install supersu?
no, you have to use LGUP tool. This is a LG image that will flash everything including your recovery partition, and not a flashable ROM image.
You flash root through TWRP, you use LGUP for kdz as the user above said rom flashing and kdz flashing are two different things
See this post which reflects the new kdz available https://forum.xda-developers.com/showpost.php?p=73690098&postcount=3
Just a Heads up there is a new version out, as of 9/01/17
MP26010r_00_0817.kdz
download link
https://lg-firmwares.com/lg-mp260-firmwares/
Click to expand...
Click to collapse
I flashed the modded ROM for MetroPCS, and couldn't flash kdz file because my phone was identified as MP260, instead of TP260.
I wiped the phone and re-locked the bootloader, and the phone would only boot into download mode, It gave a message about it being corrupted.
I took it back to TMO, and the sales people thought it was a virus, and replaced the device.
I've made a TWRP backup for anyone who runs into the same problem. This will fix your problem, so you can use the flash tools available for this device.
NOTE: I also provided Root tools and instructions for those Rooting for the first time.
1. Power off device, plug into computer, then hold volume up for download mode and let COM drivers install, you may need to change COM port to 41, through device manager.
2. In LGUP, choose upgrade or FOTA upgrade.
2. Once you flash firmware, you'll have to hit reset once or twice to get rid of the encryption failure notification.
3. Enjoy rooting your device again if you so choose.
ROOTING:
NOTE: Must have ADB & Fastboot setup already.
First you must unlock your bootloader.
1. In about phone settings, tap build number 6x to get developer settings, enable adb debugging and OEM unlock. Now plug into your computer.
2. Boot into Fastboot mode.
A. Open command prompt and type: adb reboot-bootloader.
B. Next type: fastboot oem unlock.
WARNING: You'll be prompted to factory reset device to protect your data. Your chance to turn back, if your brave then continue. Your device will factory reset, and you'll have to perform the first step again and you'll be ready to root.
1. To flash TWRP, plug into computer, then in command line navigate to where you have your recovery.img
A. adb reboot-bootloader
B. fastboot flash recovery recovery.img
2. Pull battery and manually boot into recovery,
A. volume+down as soon as you see LG, release then press again quickly and hold, follow the steps provided.
3. Hit cancel for the encryption notice, and swipe to modify system.
4. You must format device to get rid of encryption message, so choose format and it will ask you to type, yes.
5. Stay in recovery and flash the no-encryption.zip, and Magisk, if you choose to use it for your SU manager. Stay in recovery.
6. Reboot into recovery, and then set up your TWRP environment.
7. Enjoy Root:laugh:
NOTE: If you decide to root again, try using Magisk for SU management. Magisk's mods are excellent, and can run along side Xposed. If you choose Magisk, do not flash SuperUser.zip
TWRP STOCK BACKUP
https://mega.nz/#F!a59RBICD!kOisA-eOxviWK07Dn182FA
LG tools w/ Latest kdz
https://mega.nz/#F!b9sWDBwR!LjhrhZgYXB-BNHUWE11tJw
Sent from my K20 Plus using XDA Labs
Question I have a metropcs k20 version.Can I flash the t-mobile Rom with any problems.Thanks
Rican39 said:
Question I have a metropcs k20 version.Can I flash the t-mobile Rom with any problems.Thanks
Click to expand...
Click to collapse
You could probably flash the TWRP back up. After that your device would be Identified as TP260, by the flash tools and you'd end up with the same issue I had, when you decided to go back to stock, so make a TWRP backup on external memory. The KDZ file most likely won't flash because it performs a DLL check, to match device with firmware.
blas4me said:
You could probably flash the TWRP back up. After that your device would be Identified as TP260, by the flash tools and you'd end up with the same issue I had, when you decided to go back to stock, so make a TWRP backup on external memory. The KDZ file most likely won't flash because it performs a DLL check, to match device with firmware.
Click to expand...
Click to collapse
Thanks for reply.And info
does anyone have an mp 260 zip rom for twrp before boot?
5(/!p7 kiddie said:
does anyone have an mp 260 zip rom for twrp before boot?
Click to expand...
Click to collapse
I've got backup after unlock Bootloader and before root. Pretty sure it's got recovery on it. I always make a backup asap. It's the mp26010t (I had the November patch but some reason after root it says Oct).
Is that what you need?
Pm me if this is what you need and I'll send you a link
I have a Metro LG K20 Plus phone and want to change the firmware to T-Mobile. I have not been successful doing this as I always get invalid firmware, because LG UP recognizes the phone as a metro phone. Is there a way to succeed in getting the T-Mobile firmware on the phone?
thanks in advance.
lg k20 plus tmobil
lgup recognizes my model correctly as lg-tp260 on [com41] but it just sits there initializing for eternity. With my model highlighted I select it and I keep getting the error "LGUP cant load the model [C:\Program Files(x86)\LG Electronics\LGUP\model\com. I have installed lg air drive, lg bridge, lgup8994.dll, lgup for store. I desperately need to get this thing back to stock, I have the AICP rom installed but I dont like it. it was a mistake, if anyone can help I would appreciate it.
stovo06 said:
I've got backup after unlock Bootloader and before root. Pretty sure it's got recovery on it. I always make a backup asap. It's the mp26010t (I had the November patch but some reason after root it says Oct).
Is that what you need?
Click to expand...
Click to collapse
Could you PM me this link to the Metro PCS stock backup, if you still have it?
Rooted LG V20 owner here, but still running stock rom. Nowadays, my most important apps won't run because my phone is rooted. The apps check for that, and complain that my phone is rooted and won't let me use them. I've tried using apps like "Hide my root" so I can keep my phone rooted, but those apps just give me errors about being unable to find the su binary and what not. And I can't seem to fix them, or rather, don't even want to try. I'm just so tired of constantly having to deal with technical issues like this... So I decided today I would bend over and accept the latest OTA update, which would most likely make me lose root and also permanently make me unable to root my phone again.
Only problem is, now my phone is stuck in a boot loop, where it always boots into TWRP. I can't decrypt the data partition, which is the first thing TWRP asks me to do. Entering the long numeric PIN I used to encrypt it (using the stock ROM encryption feature) doesn't work, so I have no clue how else to decrypt it. Thing is, I'm not sure if I even need to decrypt it. I just want my phone to boot back up normally.
I tried to reflash the "debloated" H9180s image I had saved from last time I updated my phone, wiped the cache/dalvik, and rebooted, but the boot loop remains. Presumably this is because I couldn't decrypt "data" partition first(?). Then I tried some advice from some other threads, such as this one, and this one), but nothing has worked so far. I can't reinstall twrp because when I boot in fastboot mode, adb can't see my device even though fastboot can (apparently that's due to a patch from the manufacturer to prevent users from rooting their phones). Deleting any of the fota or misc folders didn't help either (most of them weren't there, but the one I did find and deleted had no effect).
Can anyone help me get my phone to boot again? I am open to any solution, whether it keeps root or not, as long as I still have my data and apps. Hoping to eventually get rid of root or figure out how to hide it so I can use certain important apps again. But that's a later step in the process.
EDIT: I forgot to mention that holding the volume down button and the power key when booting my phone has NEVER once worked ever since I have owned this phone. The only way I've ever been able to boot into TWRP (prior to my boot loop) was to plug it into my Macbook and run "adb boot recovery." So any solution with the "volume down and power button" combo isn't going to help. Curious why this has been an issue, too.
fronzee88 said:
Rooted LG V20 owner here, but still running stock rom. Nowadays, my most important apps won't run because my phone is rooted. The apps check for that, and complain that my phone is rooted and won't let me use them. I've tried using apps like "Hide my root" so I can keep my phone rooted, but those apps just give me errors about being unable to find the su binary and what not. And I can't seem to fix them, or rather, don't even want to try. I'm just so tired of constantly having to deal with technical issues like this... So I decided today I would bend over and accept the latest OTA update, which would most likely make me lose root and also permanently make me unable to root my phone again.
Only problem is, now my phone is stuck in a boot loop, where it always boots into TWRP. I can't decrypt the data partition, which is the first thing TWRP asks me to do. Entering the long numeric PIN I used to encrypt it (using the stock ROM encryption feature) doesn't work, so I have no clue how else to decrypt it. Thing is, I'm not sure if I even need to decrypt it. I just want my phone to boot back up normally.
I tried to reflash the "debloated" H9180s image I had saved from last time I updated my phone, wiped the cache/dalvik, and rebooted, but the boot loop remains. Presumably this is because I couldn't decrypt "data" partition first(?). Then I tried some advice from some other threads, such as this one, and this one), but nothing has worked so far. I can't reinstall twrp because when I boot in fastboot mode, adb can't see my device even though fastboot can (apparently that's due to a patch from the manufacturer to prevent users from rooting their phones). Deleting any of the fota or misc folders didn't help either (most of them weren't there, but the one I did find and deleted had no effect).
Can anyone help me get my phone to boot again? I am open to any solution, whether it keeps root or not, as long as I still have my data and apps. Hoping to eventually get rid of root or figure out how to hide it so I can use certain important apps again. But that's a later step in the process.
EDIT: I forgot to mention that holding the volume down button and the power key when booting my phone has NEVER once worked ever since I have owned this phone. The only way I've ever been able to boot into TWRP (prior to my boot loop) was to plug it into my Macbook and run "adb boot recovery." So any solution with the "volume down and power button" combo isn't going to help. Curious why this has been an issue, too.
Click to expand...
Click to collapse
In twrp go to mount and make sure system is mounted, then try rebooting
Sent from my LG-H910 using XDA Labs
cnjax said:
In twrp go to mount and make sure system is mounted, then try rebooting
Click to expand...
Click to collapse
It still boots into TWRP.
fronzee88 said:
It still boots into TWRP.
Click to expand...
Click to collapse
Did you try restoring a back up
Sent from my LG-H910 using XDA Labs
cnjax said:
Did you try restoring a back up
Click to expand...
Click to collapse
I made a backup with TWRP before attempting the original update that caused this issue, but I am doubting the integrity of that backup, because I was not able to decrypt the "data" partition before making the backup. So I backed up the data partition in the encrypted state, but I am not sure if that is restorable or not. Instead, I just tried reflashing the ROM.
When I navigated to the TWRP backups folder where the backup was supposed to have been saved, I couldn't find the (most recent) backup, so I am not sure if I can actually restore anything, should the need arise.
While in TWRP:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1
That will wipe the flags that are forcing a reboot into recovery that is trying to apply the OTA.
Once that is done, if you want to return your phone to stock, flash any 10p or higher KDZ. If you don't have download mode, there is a zip in the lafsploit thread that you can flash to get download mode back.
-- Brian
runningnak3d said:
While in TWRP:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1
That will wipe the flags that are forcing a reboot into recovery that is trying to apply the OTA.
Click to expand...
Click to collapse
I wasn't able to get connect with my laptop from adb (unauthorized message) but I did enter the dd command in a terminal directly in twrp itself (Advanced > Terminal). It worked!!! Thank you, thank you, thank you! Whew.
If you weren't able to connect with adb, then you are running a bad copy of TWRP (3.1). That build has issues. You need to upgrade to TWRP 3.2 -- but glad you are back up and running.
-- Brian
runningnak3d said:
If you weren't able to connect with adb, then you are running a bad copy of TWRP (3.1). That build has issues. You need to upgrade to TWRP 3.2 -- but glad you are back up and running.
Click to expand...
Click to collapse
Good to know. Thanks!
runningnak3d said:
If you weren't able to connect with adb, then you are running a bad copy of TWRP (3.1). That build has issues. You need to upgrade to TWRP 3.2 -- but glad you are back up and running.
Click to expand...
Click to collapse
I'm having trouble finding the latest official TWRP download for LG V20 T-Mobile (H918). The device isn't listed on their official site. Any suggestions on how to upgrade?
TWRP 3.2: https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
-- Brian
runningnak3d said:
if you want to return your phone to stock, flash any 10p or higher KDZ. If you don't have download mode, there is a zip in the lafsploit thread that you can flash to get download mode back.
Click to expand...
Click to collapse
I'm not sure what you mean by "download" mode, but my other question is: Will flashing a KDZ cause me to lose all my data? If so, how can I make a backup of all my data if the "data" partition is encrypted? I can't get TWRP to decrypt it even when entering the correct PIN that I normally use to unlock my encrypted phone upon regular bootup.
Note that Titanium Backup is not an option if I'm planning to unroot my phone.
Yes, flashing a KDZ wipes your phone.
If your data partition is encrypted, the only way to backup your data is from within the OS (copy to SD card) or use LG backup.
Btw the reason you arnt able to get into recovery via the buttons is because you were doing it wrong, its not hold power and volume down, its actually hold volume down, press power until the screen turns on, then (still holding vol down) tap the power button (either once at exactly the right time, or repeatedly which works more consistantly) until a screen appears asking if you want to factory reset. saying yes (via the volume and power buttons) twice boots twrp if installed, else it boots the stock recovery and wipes the phone.
runningnak3d said:
While in TWRP:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1
That will wipe the flags that are forcing a reboot into recovery that is trying to apply the OTA.
Once that is done, if you want to return your phone to stock, flash any 10p or higher KDZ. If you don't have download mode, there is a zip in the lafsploit thread that you can flash to get download mode back.
-- Brian
Click to expand...
Click to collapse
The same thing happened to me but on my V10. Would this command work on that phone?
Hello ALL!
I normally don't message much because usually I can find most of my problems can be fixed by searching threads online. However, this particular case for me has been exhausting because through trial and error I have been unsuccessful in getting my 6T to boot into any rom normally.
I went from a stock T-Mobile to International version to LOS. The reason I did what I did was because I could get a IMEI or SIM to register on LOS. That worked fine on OOS 9.0.11. but as soon a I flash the latest LOS, no sim, bootloader, or IMEI detection.
I was rooted and unlocked. Now I am neither.
While on LOS, someone on another forum suggested to erase the persist partition and reflash to get the sim imei back so the phone would get service, when the phone rebooted it still didn't work and then the second time it rebooted it always gets stuck on the boot screen and never boots into the OS.
I tried to repair and reflash but was unsuccessful.
Since doing all of that, Ive reflashed using msm tool and although that was successful for OOS 9.0.11 and T-Mobile stock rom. It gets stuck on the boot screens for both.
I flashed LOS on A & B so I don't have a stock recovery.
I can't ADB anymore. I can only seem to connect via FASTBOOT but cannot seem to flash anything because the BOOTLOADER is now LOCKED.
How can I get this phone back to its original state? What ever the persist partition is. Removing it had made the phone non-bootable.
What can I do to fix? I greatly appreciate any help to get the phone operational again.
Thank you all!
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
- Go to the thread linked above and download the latest OOS (.13) stable.
- Download latest Magisk.
- Have the latest TWRP .img downloaded and on-hand, you will use a few times as well as the installer .zip.
- Be sure to have adb/fastboot installed.
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
- Put your phone into fastboot mode (reboot to bootloader).
- Go to the folder you downloaded in the first step and run the "flash all.bat".
- Ignore errors. If it's get stuck for more than 45 seconds, just hit enter to keep it going.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP.
- In TWRP, go to Reboot and changed the boot partition to the one NOT CURRENTLY enabled. In other words, switch boot partitions.
- Reboot bootloader.
- Go to the folder you downloaded in the first step and run the "flash all.bat" again.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP again.
- Move Magisk installer and TWRP installer from steps two and three onto the internal memory of your device.
- Flash TWRP, reboot recovery to make sure it sticks.
- Flash Magisk for root.
- Wipe dalvik and reboot system.
You will have the latest stable OOS on both partitions at this point! I literally just did this yesterday. Good luck!
..Cory.. said:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
- Go to the thread linked above and download the latest OOS (.13) stable.
- Download latest Magisk.
- Have the latest TWRP .img downloaded and on-hand, you will use a few times as well as the installer .zip.
- Be sure to have adb/fastboot installed.
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
- Put your phone into fastboot mode (reboot to bootloader).
- Go to the folder you downloaded in the first step and run the "flash all.bat".
- Ignore errors. If it's get stuck for more than 45 seconds, just hit enter to keep it going.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP.
- In TWRP, go to Reboot and changed the boot partition to the one NOT CURRENTLY enabled. In other words, switch boot partitions.
- Reboot bootloader.
- Go to the folder you downloaded in the first step and run the "flash all.bat" again.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP again.
- Move Magisk installer and TWRP installer from steps two and three onto the internal memory of your device.
- Flash TWRP, reboot recovery to make sure it sticks.
- Flash Magisk for root.
- Wipe dalvik and reboot system.
You will have the latest stable OOS on both partitions at this point! I literally just did this yesterday. Good luck!
Click to expand...
Click to collapse
Thank you but how can I flash if my bootloader is locked? Everything I try fails.
I guess the real question is: How can I get the phone to turn on OEM UNLOCK so I can fastboot unlock the Bootloader if it wont boot up the OS?
Is there a way to fix it via the msmdownload tool? Custom file maybe? I've tried the files 9.0.11 & 12 OOS files and all I get is the boot screen white ball logo circling the red ball - stuck in loop and same with stock t-mobile rom.
My friend, sounds like you need to restore your EFS partitions
... I'm trying to figure out how the hell you successfully flashed MSM tool in EDL mode and not have ALL your partitions restored. That tool is supposed to literally write the phone as it came out of the box. Also I think there are different MSM tools for each device respectively, you did use the T-Mobile one right?
Causical said:
My friend, sounds like you need to restore your EFS partitions
... I'm trying to figure out how the hell you successfully flashed MSM tool in EDL mode and not have ALL your partitions restored. That tool is supposed to literally write the phone as it came out of the box. Also I think there are different MSM tools for each device respectively, you did use the T-Mobile one right?
Click to expand...
Click to collapse
My thoughts exactly. So, when it was on LOS I erased the persist partition and that really messed things up. So yes, how can I restore the partition back with a locked bootloader? Every time I've used MSM tool it fixes everything. This time no such luck. I flashed 9.0.11 & 12 and then I did the T-Mobile version. All only boot to the boot screen and hang. In doing so, I wasn't thinking if that failed and it locks the bootloader, then what? I saw an old video somewhere on a oneplus 2 or 3 where the person used the msm tool 3.0 and fixed a bricked locked bootloader phone. Similar to the fastboot method of reformatting. In the msm tool folder he had all the image files for all the partitions not sure if that the same thing as msm tool 4.0 with just one ops image file?
Anyway, is there a way to unlock the bootloader without booting into the OS? Or a way to restore the partitions via msm tool?
defcondoc said:
My thoughts exactly. So, when it was on LOS I erased the persist partition and that really messed things up. So yes, how can I restore the partition back with a locked bootloader? Every time I've used MSM tool it fixes everything. This time no such luck. I flashed 9.0.11 & 12 and then I did the T-Mobile version. All only boot to the boot screen and hang. In doing so, I wasn't thinking if that failed and it locks the bootloader, then what? I saw an old video somewhere on a oneplus 2 or 3 where the person used the msm tool 3.0 and fixed a bricked locked bootloader phone. Similar to the fastboot method of reformatting. In the msm tool folder he had all the image files for all the partitions not sure if that the same thing as msm tool 4.0 with just one ops image file?
Anyway, is there a way to unlock the bootloader without booting into the OS? Or a way to restore the partitions via msm tool?
Click to expand...
Click to collapse
Try this and tell me if it works.
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
_Masked_ said:
Try this and tell me if it works.
Click to expand...
Click to collapse
Yes, I did try that. That is what I just flashed with the msm tool. Gets stuck on the OOS boot animation.
Causical said:
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
Click to expand...
Click to collapse
Looks like the MSM tool. I'm going to give 9.0.13 a try but I'm thinking I may have the same problem.
Causical said:
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
Click to expand...
Click to collapse
Tried 9.0.13. Still gets stuck on OOS boot animation screen. There's got to be something to flash to fix this.
So you're booting EDL mode then flashing the MSM tool that exactly matches the way your phone came stock? At this point I would discontinue trying to convert it to international or upgrade the OS to a more recent version or any of that. I would focus on strictly flashing it to exactly the way you bought it.
Causical said:
So you're booting EDL mode then flashing the MSM tool that exactly matches the way your phone came stock? At this point I would discontinue trying to convert it to international or upgrade the OS to a more recent version or any of that. I would focus on strictly flashing it to exactly the way you bought it.
Click to expand...
Click to collapse
Yes. I did flash the stock T-Mobile ROM via the MSM tool. Freezes at the pink T-Mobile boot screen. Pretty sure the partitions need to be fixed but I thought the MSM tool would do that? I guess not. Is there a more advanced MSM tool where I can see what's being partitioned or is the MSM tool not doing any partitioning and that's why the phone is having the boot problem?
defcondoc said:
Yes. I did flash the stock T-Mobile ROM via the MSM tool. Freezes at the pink T-Mobile boot screen. Pretty sure the partitions need to be fixed but I thought the MSM tool would do that? I guess not. Is there a more advanced MSM tool where I can see what's being partitioned or is the MSM tool not doing any partitioning and that's why the phone is having the boot problem?
Click to expand...
Click to collapse
I know this is a stupid question but have you tried a factory reset in recovery mode? I know its a stupid question but I did not see it asked or noted.
Scott said:
I know this is a stupid question but have you tried a factory reset in recovery mode? I know its a stupid question but I did not see it asked or noted.
Click to expand...
Click to collapse
No stupid questions and I don't mind repeating answers to questions. I have tried that, but it does nothing. I get wipe cache or reboot to fastboot or reboot to recovery. When I choose system wipe, it takes 1 second to finish. It reboots and it gets stuck on the boot screen. Ever since persist partition was deleted it just freezes on startup and now that the bootloader is locked I cant seem to get anything to work. MSM tool I thought was supposed to fix this sort of thing but it has failed. Someone must know a way to get back into the OS so I can turn on OEM Unlock.
How do you know your bootloader is locked?
Causical said:
How do you know your bootloader is locked?
Click to expand...
Click to collapse
Fastboot says bootloader is locked. Shows it on the fastboot screen. Wont let me transfer any files from pc to phone. I can start the transfer process but it fails.
defcondoc said:
Fastboot says bootloader is locked. Shows it on the fastboot screen. Wont let me transfer any files from pc to phone. I can start the transfer process but it fails.
Click to expand...
Click to collapse
So you're able to enter EDL mode with a locked bootloader? How do you know your computer is seeing your device in EDL mode?
I'm going to place this here for myself for now. I'm just trying to understand your situation a little better, but this is just for later.... maybe, depending on your answer. https://forum.xda-developers.com/an...how-to-reboot-to-edl-fastboot-t3394292/page12
ALSO; If you don't mind can you link the thread that contains the original discussion where your problem began?
Causical said:
So you're able to enter EDL mode with a locked bootloader? How do you know your computer is seeing your device in EDL mode?
I'm going to place this here for myself for now. I'm just trying to understand your situation a little better, but this is just for later.... maybe, depending on your answer. https://forum.xda-developers.com/an...how-to-reboot-to-edl-fastboot-t3394292/page12
ALSO; If you don't mind can you link the thread that contains the original discussion where your problem began?
Click to expand...
Click to collapse
The point of EDL is to get around any restrictions or issues with the device, so yes, you can boot to EDL while locked. Your link will not help much because he can already get to EDL. Not to mention he will have no ADB access. Whatever he does, he has to fix it in EDL.
OP: Are you up and running yet? I am willing to try copying out my partition and sending to you.
Let me know...
---------- Post added at 08:12 PM ---------- Previous post was at 08:08 PM ----------
Wait, I just realized that my persist.img would not work because he has no way to flash it.
Nevermind.
So I unlocked bootloader on my redmi note 7.
Then I flashed twrp and rooted my device.
Then I flashed pixel experience but it stuck on the Google logo after reboot. I tried factory reset in twrp but it didn't work.
So I restored the backup I did before flashing pixel experience.
And then my phone stuck on bootloop.
So I booted into fastboot mode and flashed the fastboot rom and it worked. I have successfully unbricked my device.
But now it shows "find device storage corrupted your device is unsafe now"
Everything works fine except I can't turn on find device and also can't install miui ota updates via twrp.
(And also when flashing twrp for the first time when I reboot it showed the stock recovery because I hadn't flashed disable dm-verify because when I am in twrp and try to mount my system to my computer my phone doesn't show up in the computer. So first I copied the disable dm-verify file then again flashed twrp then booted into twrp and then flashed disable dm-verify. I don't know if it is necessary to format data when flashing twrp. Maybe that's why the problem occured. I don't know.)
Please help.
Thank you.
Extract persist.img from official fastboot rom and replace the existing persist in Orangefox.
At least it helped me.
Persist.img flash through recovery gonna fix the problem but forget about Netflix and L1!!
Personally speaking had that problem with corrupted message pop up every time i reboot my device and when i flashed the persist.img through OrangeFox recovery i lost L1 forever (and there is no turning back).
If you wanna try that method i highly suggest you to Backup your Persist Partition first.
Yes, but isn't the original persist partition already lost, when you get the "storage corrupted" message?
Lucky-thirteen said:
Yes, but isn't the original persist partition already lost, when you get the "storage corrupted" message?
Click to expand...
Click to collapse
I tried may hours to define the problem's source but i think that's unclear in every situation. Others say that's a persist.img corruption while others had that problem with Mi Account corruption, etc.
Mine corrupted message came when i tried to flash Global Official MIUI in a EU variant device through normal process that doesn't engage any kind of Persist partition rewrite.
I had a backup of persist.img and flashed original from EU fastboot file and finally after that I repatch my old persist.img. The first time i did that process my device and L1 worked properly (even that spam message disappeared) but after a long time that I tried same process for same problem i completely lost my L1 [strange af!].
So, a safe process to try now is to flash back the official fastboot image of your variant (Erase + Lock [for L1]) through MiFlash tool and check that corruption message if it goes away (be careful to flash the correct fastboot image or you will get a a bricked device).
In conclusion it's Extremely advisable to keep a full backup of your partitions and especially Persist partition if you wanna flash Roms and generally unlock bootloader!
I use twrp recovery
I don't know about orange fox recovery
Strange51 said:
I use twrp recovery
I don't know about orange fox recovery
Click to expand...
Click to collapse
Always use OrangeFox for Lavender here is the link (download and test with latest R10.1_02-Stable)