Credits:
Click to expand...
Click to collapse
@mauronofrio
@Superboy58
@OnePlus_Team
@Google_Team
Make sure to Backup your Phone Data before Converting your OnePlus 7T!
Click to expand...
Click to collapse
Conversion Requirements
Click to expand...
Click to collapse
A Desktop or Laptop with Windows 10-11 OS
OnePlus OEM Cable Recommended
Make sure you have OnePlus USB Drivers & Bootloader installed properly before you start the Tutorial Highly important before starting. If if not installed properly you will have fastboot adb errors. [Tutorial Linked Below]
Click to expand...
Click to collapse
⭐[GUIDE] How to Properly Install OnePlus 7T Official USB Driver & Bootloader Drivers!
Updated 06/03/23 Download OnePlus USB Drivers❗ 1▫️First Disable Driver Signature Enforcement on your PC. 2▫️Press and hold the Shift key on your keyboard and click the Restart button. 3▫️Choose Troubleshoot > Advanced options > Startup...
forum.xda-developers.com
Turn on USB Debugging in Developer Settings now plug the phone into the PC.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please make sure you have everything required & prepared before you start the Conversion Tutorial
Click to expand...
Click to collapse
[Conversion Tutorial]
Click to expand...
Click to collapse
1Download the Patched MSM download tool & Platform Tools, extract both to your desktop.
Patched MSM Tool Download By Superboy58
Click to expand...
Click to collapse
https://drive.google.com/file/d/1ayMLNbBmwtQYjDWq9-T27iGiuexBG47N/view?usp=drivesdk
Platform Tools Download By Google Team
Click to expand...
Click to collapse
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2Download & Extract 10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip to platform-tools root folder.
OxygenOS 10.0.13 Global Rom Download By mauronofrio
Click to expand...
Click to collapse
https://sourceforge.net/projects/fastbootroms/files/OnePlus%207T/10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip/download
3Run the Patched MsmDownloadTool V4.0.exe with Administrator Privilege now click start.
4Now put the Phone into EDL Mode
Turn the phone off completely! Take your OnePlus Cable plug the the USB side into the PC while leaving the Type C port unplugged from your phone. Now hold vol up & vol down buttons at the same time about 5 secs...while doing that plug the Type C port into your phone immediately
Do not let go of vol up & vol down while plugging the cable into your Phone!
Click to expand...
Click to collapse
MSM Tool should detect & begin the installation process if you entered EDL Mode correctly.
5Once the Patched firmware finishes installing! Your phone will boot up a message that says.
"Your device is corrupt. It cannot be trusted & will not boot" Then it will boot into Fastboot Mode after a few seconds. This is completely Normal.
Click to expand...
Click to collapse
6Now while on the Fastboot Screen, Go to Platform Tools root folder on your PC. Type CMD in the top address bar and hit enter a command prompt will appear.Type this Command: fastboot flashing unlock_critical and hit enter. Now look at your phone and click on UNLOCK THE BOOTLOADER!
7The phone will reboot back into Fastboot Mode & Now your Bootloader will be unlocked
8Remain in Fastboot Mode! Now go back to your PC where you extracted the
10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip files and click on flash-all.bat
9The Phone will install the Global Rom firmware. When finished it will boot up and you will see the
(Hi there) displayed on your Screen! Now hold the power key & turn off the Phone immediately Now put the phone back into Fastboot Mode by holding vol up & down plus power key!
10Keep phone plugged in...go back to your PC and run flash-all.bat one more time! Press Y to format data again. Now it will put your phone into (Fasbootd Mode Recovery Menu) this time & finish installing the Global firmware! The Phone will finally boot up with the (OnePlus Global Boot Animation Logo) indicating the Conversion was successful. It will take a long time to boot up into Android that's normal for the first boot!
Note: If it didn't boot your phone into (Fastbootd Mode) when you clicked on flash-all.bat the 2nd time That's ok. just turn the phone off again. Boot back into Fastboot Mode and try again and click on flash-all.bat once more. If it fails on second Flash you need to update your Bootloader driver!! So go back & check out the USB Driver's Guide https://forum.xda-developers.com/t/...ficial-usb-drivers-bootloader-driver.4558965/
Click to expand...
Click to collapse
11Once Global Firmware is installed successfully, Setup your Phone & skip Wi-Fi setup keep it turned off!!
Download OnePlus7TOxygen_14.O.35_OTA_0350_all_2206171459_e2cf457f577648a3.zip.jar onto your PC. Then rename it to .jar to .zip
Now plug your phone into your PC. Turn USB Debugging on & turn transfer mode on.
Copy OnePlus7TOxygen_14.O.35_OTA_0350_all_2206171459_e2cf457f577648a3.zip from your PC to the (Root System) of your Android.
Now Open Settings -> About device -> Version and tap "Build number" 7 times. This will enable Android's built-in "developer mode".
Go to Settings -> System -> System Updates -> top-right corner button select the cogwheel Select Local Upgrade and now select the OnePlus7TOxygen_14.O.35_OTA_0350_all_2206171459_e2cf457f577648a3.zip & let the Installation Finish.
OxygenOS 11.0.9.1 Global Firmware By OnePlus Team
Click to expand...
Click to collapse
https://oxygenos.oneplus.net/OnePlus7TOxygen_14.O.35_OTA_0350_all_2206171459_e2cf457f577648a3.zip
12After installing OxygenOS 11.0.9.1 make sure to boot into Recovery Mode and perform a Hard Reset!
Power off your device. Press and hold volume down + Power button. (The device will boot into recovery mode).
Select language. Select Wipe data and cache > Erase Everything (Music, pics, etc) > Tap on "This can not be undone, continue?". Now Reboot system from "Reboot" option."
13I recommend locking your bootloader once completed with the guide, unless you plan on rooting or installing custom roms.
Plug your phone into the PC, Turn USB Debugging on then Boot into fastboot mode.
Open a cmd command prompt in platform tools root folder.
Type fastboot flashing lock hit enter.
It will say do you wanna lock your bootloader hit continue
14Last step is to Disable your updates thats if u don't want Android 12 update Notifications! I've made a guide here https://forum.xda-developers.com/t/guide-disable-system-updates-permanently.4592381/
Tutorial Guide written by @xxlMVPlxx
The Benefits of Global/International Firmware Conversion
Click to expand...
Click to collapse
Completely removes T-Mobile Apps and any underlying Software (there aren't a lot, but why not completely gone!)
Use Dual Sim supported by the hardware & the ability to use other carriers.
Get on the faster firmware release schedule of stock Global firmware because it doesn't need to be certified by T-Mobile, which are always generations behinds.
You can now Root your OnePlus 7T & install Magisk & use Magisk Modules.
You can OEM unlock your Bootloader & put TWRP & install Custom Roms if you like.
Conversation will NOT change your Model Number it will remain a "HD1907"
Maybe a noob question, but would there be any downsides to this, such as loosing access to certain radio frequencies?
Birdflyer said:
Maybe a noob question, but would there be any downsides to this, such as loosing access to certain radio frequencies?
Click to expand...
Click to collapse
Nope not at all. It's an upgrade in my opinion better battery life as well. Just dnt upgrade to Android 12 or 13 on a Converted 7T & your golden.
Birdflyer said:
Maybe a noob question, but would there be any downsides to this, such as loosing access to certain radio frequencies?
Click to expand...
Click to collapse
I used metro PCS after conversion & I never lose connection neither does my wifi which is Comcast.
@Birdflyer Did you try to convert over to global yet?
Hello, I am having a lot of trouble with the MSM tool. I can get the phone into edl mode and start the msm tool, but it quickly disconnects the phone ("status of connection" shows "N/A") and the status of communication is "setting firehose communication data transmission ". On the device manager it shows the phone as unknown USB device (device descriptor request failed). Could this be because my phone is on android 12 or is it a problem with the PC? Luckily, this seems to result in nothing happening to the phone, and after plugging it into the charger I can reboot normally
billybobjoe512 said:
Hello, I am having a lot of trouble with the MSM tool. I can get the phone into edl mode and start the msm tool, but it quickly disconnects the phone ("status of connection" shows "N/A") and the status of communication is "setting firehose communication data transmission ". On the device manager it shows the phone as unknown USB device (device descriptor request failed). Could this be because my phone is on android 12 or is it a problem with the PC? Luckily, this seems to result in nothing happening to the phone, and after plugging it into the charger I can reboot normally
Click to expand...
Click to collapse
That means you need to install your OnePlus 7T drivers properly here's the guide https://forum.xda-developers.com/t/...ficial-usb-drivers-bootloader-driver.4558965/
xxlMVPlxx said:
That means you need to install your OnePlus 7T drivers properly here's the guide https://forum.xda-developers.com/t/...ficial-usb-drivers-bootloader-driver.4558965/
Click to expand...
Click to collapse
Ok I had tried that before but just in case I tried it again by uninstalling and reinstalling the drivers, and then I also installed usb drivers through windows update and that seemed to have done it ! Thanks for your help!
billybobjoe512 said:
Ok I had tried that before but just in case I tried it again by uninstalling and reinstalling the drivers, and then I also installed usb drivers through windows update and that seemed to have done it ! Thanks for your help!
Click to expand...
Click to collapse
Lmk if you get it fixed? You could try Optional Updates.. The bootloader driver could be in there, Update & restart PC. If you see it available?
billybobjoe512 said:
Ok I had tried that before but just in case I tried it again by uninstalling and reinstalling the drivers, and then I also installed usb drivers through windows update and that seemed to have done it ! Thanks for your help!
Click to expand...
Click to collapse
You need all 3 of the following drivers. OnePlus USB driver, Bootloader Driver, Qualcomm HS-USB QDLoader driver.
xxlMVPlxx said:
Lmk if you get it fixed? You could try Optional Updates.. The bootloader driver could be in there, Update & restart PC. If you see it available?
Click to expand...
Click to collapse
Yes thank you I got it fixed, I think the bootloader driver wasn't installed correctly so I reinstalled that, and I updated usb drivers through the windows update (these were just the drivers for my PC, not related to the drivers I needed to install to convert the phone). It had some trouble at first connecting to my PC in fastboot but I got it working eventually and now the phone has been converted!
xxlMVPlxx said:
@mauronofrio
@Superboy58
A Desktop or Laptop with Windows 10-11 OS
OnePlus OEM Cable Recommended
⭐[GUIDE] How to Properly Install OnePlus 7T Official USB Driver & Bootloader Drivers!
Updated 06/03/23 Download OnePlus USB Drivers❗ 1▫️First Disable Driver Signature Enforcement on your PC. 2▫️Press and hold the Shift key on your keyboard and click the Restart button. 3▫️Choose Troubleshoot > Advanced options > Startup...
forum.xda-developers.com
View attachment 5853149
[USB Debugging Example]
View attachment 5848755Check the box for always allow!
View attachment 5853287
1Download the Patched MSM download tool & Platform Tools, extract both to your desktop.
https://drive.google.com/file/d/1ayMLNbBmwtQYjDWq9-T27iGiuexBG47N/view?usp=drivesdk
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2Download & Extract 10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip inside Platform Tools Root folder!!!
https://sourceforge.net/projects/fastbootroms/files/OnePlus%207T/10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip/download
3Run the Patched MsmDownloadTool V4.0.exe with Administrator Privilege now click start.
4Now put the Phone into EDL Mode
Turn the phone off completely! Take your OnePlus Cable plug the the USB side into the PC while leaving the Type C port unplugged from your phone. Now hold vol up & vol down buttons at the same time about 5 secs...while doing that plug the Type C port into your phone immediately
MSM Tool should detect & begin the installation process if you entered EDL Mode correctly.
5Once the Patched firmware finishes installing! Your phone will boot up a message that says.
View attachment 5853185
6Now while on the Fastboot Screen, Go to Platform Tools root folder on your PC. View attachment 5853151Type CMD in the top address bar and hit enter a command prompt will appear.View attachment 5853153Put this Command: fastboot flashing unlock_critical and hit enter. Now look at your phone and click on UNLOCK THE BOOTLOADER!View attachment 5853175
7The phone will reboot back into Fastboot Mode & Now your Bootloader will be unlocked
8Remain in Fastboot Mode! Now go back to Platform Tools root folder on your PC where you extracted the
10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip files and click on flash-all.batView attachment 5853235
9The Phone will install the Global Rom firmware. After it boots up to home screen hold power key & turn the phone off...immediately Now put the phone back into Fastboot Mode by holding vol up & down plus power key!
10Keep phone plugged in.. go back to Platform Tools root folder run flash-all.bat one more time! Now it will put your phone into Recovery Mode this time & finish installing the Global firmware! The Phone will finally boot up with the OnePlus Global Splash screen indicating the Conversion was successful. It will take a long time to boot up into Android that's normal for the first boot!
11Once you setup your Phone turn on your wifi download OxygenOS 11.0.9.1 onto your OnePlus7T then copy it from downloads folder to the Root folder of your Android then go to Settings>System>System Updates>Click on the Cogwheel >Local Upgrade
Select your firmware & let the Installation Finish.
If that fails update threw Android System Update.
https://oxygenos.oneplus.net/OnePlus7TOxygen_14.O.35_OTA_0350_all_2206171459_e2cf457f577648a3.zip
12After installing OxygenOS 11.0.9.1 make sure to boot into Recovery Mode and perform a Hard Reset! Clear cache & erase everything. Congratulations your done! Your OnePlus 7T will boot back up, Now setup device setup & connect back to your wifi you are finally done with the Tutorial Guide written by @xxlMVPlxx
Completely removes T-Mobile Apps and any underlying Software (there aren't a lot, but why not completely gone!)
Use Dual Sim supported by the hardware & the ability to use other carriers.
Get on the faster firmware release schedule of stock Global firmware because it doesn't need to be certified by T-Mobile, which are always generations behinds.
You can now Root your OnePlus 7T & install Magisk & use Magisk Modules.
You can OEM unlock your Bootloader & put TWRP & install Custom Roms if you like.
Click to expand...
Click to collapse
I followed everything but my OnePlus7t seems to have lost WIFI functionality, please help!
Ramover3 said:
I followed everything but my OnePlus7t seems to have lost WIFI functionality, please help!
Click to expand...
Click to collapse
That's means you didn't completely convert over! Power the Phone OFF then boot into Fastboot Mode by pressing vol up & vol down plus power at the same time. Then go to Platform Tools folder on your PC & click on flash-all.bat again it should boot your phone into Recovery Mode on the second flash all! Then it will boot your phone into Global Firmware finally & your wifi will be restored.
@Ramover3 You need to re-read over steps 8-12 very important. That's where you messed up.
@Ramover3 Take your time & read over if you still have issues report back thanks.
@Ramover3 Did you get it fixed?
xxlMVPlxx said:
@Ramover3 Did you get it fixed?
Click to expand...
Click to collapse
Flashing is not allowed for Critical Partitions, I get this error when I run the flash-all.bat for the second time.
Ramover3 said:
Flashing is not allowed for Critical Partitions, I get this error when I run the flash-all.bat for the second time.
Click to expand...
Click to collapse
You need to unlock the bootloader first that's step 6-7 you cannot flash a rom with a locked Bootloader that's the results you'll get.
Ramover3 said:
Flashing is not allowed for Critical Partitions, I get this error when I run the flash-all.bat for the second time.
Click to expand...
Click to collapse
Make sure to follow all the instructions from the top. Your skipping ahead of yourself take your time step by step...
xxlMVPlxx said:
You need to unlock the bootloader first that's step 6-7 you cannot flash a rom with a locked Bootloader that's the results you'll get.
Click to expand...
Click to collapse
I unlocked the bootloader, then I followed the next steps. I'm going to restart everything from the beginning and then report back.
Related
For those who are waiting to unlock bootloader but don´t want to lose data this quick guide is intended to do so.
Usually in most of threads out there about unlocking anyone find the typical phrase "unlock bootloader erase all your data" like is advertised in the same MiFlash Unlock tool and for other devices which method to unlock it is through the same fastboot mode by command.
Really unlock bootloader doesn´t erase nothing itself, the problem is at time to reboot to system and here is the issue, if we reboot inmediately then data will gone. (some users of older devices reported that not always this happened BTW)
Steps that I did are the next (maybe some step was unnecesary and I´ll indicate which)
1 - Unlock bootloader as normally through the tool when time it´s came.
2- When it finishes exit the tool, don´t tap on "Reboot device" in the tool, just close the tool.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3- Device stays in fastboot, check bootloader status in fastboot mode by typing
Code:
fastboot oem device-info
View attachment 4637936
4- Extract recovery image fromOrangeFox-R8.3-vince zip inside adb folder and type
Code:
fastboot flash recovery fox.img
(I renamed it fox).
5- Reboot to recovery by typing
Code:
fastboot boot fox.img
.
View attachment 4637937
6- Once in recovery don´t swipe to allow modifications, tap on Read Only.
7- Some drivers will be updated between device and pc, then copy OrangeFox-R8.3-vince zip to internal memory (or if you prefer to an ext. sdcard) if you already don´t have it in your device.
Now flash the zip, I guess that this is necessary to OrangeFox can unpack all the tools in Fox folder onto device.
8- I enabled these options in recovery and flashed magisk, you can enable some additional features.
9 - Then Flashed No+Verity_R5Plus.zip uploaded file (I´m not sure if this step is needed so I enabled before this option and OrangeFox has in-builded this feature but just to made sure, you know..)
10- Reboot normally and you´re done.
Thanks for the info!
I intended to do what you explained in the guide.
Unfortunately, I couldn't go further than step n°1 because I haven't activated the "USB Debugging" function in my phone and this tool requires it in order to unlock the phone.
The thing is my phone (a Redmi Note 5) is currently stuck in the recovery mode so I can't access inside and activate the "USB Debugging" function.
My phone is stuck in this mode since I tried to update it with the official MIUI 10 version. I definitely want to recover my datas before doing anything else so I haven't click on the "WIPE DATAS" option (obviously).
1-Do you know another way to activate the "USB debugging" function without a proper access into the phone and in order to follow your guide afterwards ?
2-Do you know another way to recover my datas before unlocking the bootloader and flashing a new version ?
Thanks !
Thanks for the trick! but we can use another recovery for this method?
I think clicking on 'Reboot' on the unlock tool sends the script to erase all data.... Here's what I did:
1. unlock bootloader normally
2. unplug phone without clicking on 'Reboot' button at the end
3. Force power off by holding power button for about 10s
and when it rebooted.. it went right into system..phone booted normally with the 'unlocked' logo at boot with all my data untouched.
sanijsnj said:
I think clicking on 'Reboot' on the unlock tool sends the script to erase all data.... Here's what I did:
1. unlock bootloader normally
2. unplug phone without clicking on 'Reboot' button at the end
3. Force power off by holding power button for about 10s
and when it rebooted.. it went right into system..phone booted normally with the 'unlocked' logo at boot with all my data untouched.
Click to expand...
Click to collapse
Demoxing said:
Thanks for the trick! but we can use another recovery for this method?
Click to expand...
Click to collapse
Yes, all the trick resides on that, avoid to boot up from fastboot but from a complete shut off state then the order to format data would be deactivated. Newer bootloaders would prevent this but it worth the try.
sanijsnj said:
I think clicking on 'Reboot' on the unlock tool sends the script to erase all data.... Here's what I did:
1. unlock bootloader normally
2. unplug phone without clicking on 'Reboot' button at the end
3. Force power off by holding power button for about 10s
and when it rebooted.. it went right into system..phone booted normally with the 'unlocked' logo at boot with all my data untouched.
Click to expand...
Click to collapse
Do you know if that works with pocophone or newer miui phone?
Dunno.. I only own the redmi5plus
Hello there,
Can someone help me with my questions ? It's not possible for me to unlock bootloader with the tool because my USB debugging function was not activated before I got a problem during the installation of the new MIUI version and let my phone in the recovery mode...
Thanks!
popoFR said:
Hello there,
Can someone help me with my questions ? It's not possible for me to unlock bootloader with the tool because my USB debugging function was not activated before I got a problem during the installation of the new MIUI version and let my phone in the recovery mode...
Thanks!
Click to expand...
Click to collapse
You have first of all to recover your device and then to fix it try again to unlock bootloader.
In recovery do a format data it could be solve it. then set up again all
SubwayChamp said:
You have first of all to recover your device and then to fix it try again to unlock bootloader.
In recovery do a format data it could be solve it. then set up again all
Click to expand...
Click to collapse
Thanks for your answer.
To do what you wrote, I have to wipe datas, right ? The thing is I want to recover all the data from my phone...is there a possibility to do everything without wiping datas ?
popoFR said:
Thanks for your answer.
To do what you wrote, I have to wipe datas, right ? The thing is I want to recover all the data from my phone...is there a possibility to do everything without wiping datas ?
Click to expand...
Click to collapse
The problem is that is a cyclical issue. In order to can boot (presumably) due to a dirty/wrong update you need to format data, if you had have enable USB debugging before then you could flash the same firmware that was previously working well but with USB debugging disabled you can´t.
SubwayChamp said:
The problem is that is a cyclical issue. In order to can boot (presumably) due to a dirty/wrong update you need to format data, if you had have enable USB debugging before then you could flash the same firmware that was previously working well but with USB debugging disabled you can´t.
Click to expand...
Click to collapse
That was my fear...my phone didn't start again after an official update that went wrong...
There is no other possibility in enabling USB debugging with adb for example ?
I'm stuck and have to erase all my datas...?:crying:
popoFR said:
That was my fear...my phone didn't start again after an official update that went wrong...
There is no other possibility in enabling USB debugging with adb for example ?
I'm stuck and have to erase all my datas...?:crying:
Click to expand...
Click to collapse
The first I do with a new device is enable USB debugging and check on OEM unlock bootloader cause mainly the first also sometimes can cause a bootloop on a wrong/failed update and to have more options in a worst scenario, take it like a lesson for the next time.
There are ways to enable USB debugging under adb commands but you will need su permissions for this, there are a way to flash a firmware through recovery using adb sideload but again you will need USB debugging and lastly in R5+ you can flash a rom through MiFlash Tool but in download mode so fastboot never worked for me on a Xiaomi with locked bootloader.
Try this last to see if it works, I don´t think but some time ago that I don´t use this tool, try flashing the same firmware that previously was onto your device using this tool on fastboot moed and checking in the centered option to flash and keep data at the right down of the tool.
is this still working?
sanijsnj said:
I think clicking on 'Reboot' on the unlock tool sends the script to erase all data.... Here's what I did:
1. unlock bootloader normally
2. unplug phone without clicking on 'Reboot' button at the end
3. Force power off by holding power button for about 10s
and when it rebooted.. it went right into system..phone booted normally with the 'unlocked' logo at boot with all my data untouched.
Click to expand...
Click to collapse
hey,
is this trick is still working??
did u try this?
if yes then tell me the exact version in which it works...
sanijsnj said:
I think clicking on 'Reboot' on the unlock tool sends the script to erase all data.... Here's what I did:
1. unlock bootloader normally
2. unplug phone without clicking on 'Reboot' button at the end
3. Force power off by holding power button for about 10s
and when it rebooted.. it went right into system..phone booted normally with the 'unlocked' logo at boot with all my data untouched.
Click to expand...
Click to collapse
Anyone else tried this trick from Sanjisin?
I am on Mi 9t pro (MIUI 11.0.3 global), waiting for 168h timeout for unlock
popoFR said:
That was my fear...my phone didn't start again after an official update that went wrong...
There is no other possibility in enabling USB debugging with adb for example ?
I'm stuck and have to erase all my datas...?:crying:
Click to expand...
Click to collapse
maybe you can try using fastboot recovery, do a backup from there (to sd card) , then reflash to stock, unlock again (this time enable usb debugging), and after that use your backup to get back your data.
zlikovac said:
Anyone else tried this trick from Sanjisin?
I am on Mi 9t pro (MIUI 11.0.3 global), waiting for 168h timeout for unlock
Click to expand...
Click to collapse
did you try it out yourself? haven't unlocked mine yet, no need yet, but just in case for the future
Dxue said:
did you try it out yourself? haven't unlocked mine yet, no need yet, but just in case for the future
Click to expand...
Click to collapse
I missed to pull the cable on time, already phone was rebooting :/ ah well backup restore well semi ok. Not sure will i stay rooted. I only needed root so i could automate cell data, vpn. Used MacroDroid for automation. Eg. when off the home wifi, turn on cellular data, when on again, turn off. When on non home/work wifi, turn on vpn, etc. Now i need some like smart unlock (don't lock phone when on home wifi or when bt watch connected) macro and i am done.
Will stick to MIUI for now, but wish Xiaomi would tweak those few things, so we do not have to root phone.
sanijsnj said:
I think clicking on 'Reboot' on the unlock tool sends the script to erase all data.... Here's what I did:
1. unlock bootloader normally
2. unplug phone without clicking on 'Reboot' button at the end
3. Force power off by holding power button for about 10s
and when it rebooted.. it went right into system..phone booted normally with the 'unlocked' logo at boot with all my data untouched.
Click to expand...
Click to collapse
Has anyone tried this pls? I have an Redmi Note 7 and dont want to lose my data pls
Unlock mi note 5 pro without data loss
Dear sir
I want to unlock my mi note 5 pro any way out please help me I haven't installed anything
Do you want to bootloader and unlock and root your V35? Do you want to do this yourself? Are you feeling the need for some adventure? If you answered yes to these questions, then you are at the right place. The goal with these instructions is to make the process as smooth and pain-free as possible. These instructions are based upon what I know works through firsthand experience and what I have gathered reading. My experience is with an AT&T branded V350AWM. Others also report success. That said, there can still be problems leading to bricked phone so don’t continue if you are not comfortable with the risk. An unavoidable side-effect of bootloader unlocking is that all data on your phone will be erased. Make a back up if you don’t want to lose it permanently.
This is what you will be doing in a nutshell.
Setting the phone into a baseline Oreo conditions
Extraction of abl, laf, and boot partititions
Installation of the engineering abl and erasing the laf's using QFIL
Unlocking the phone
Flashing to Pie and maybe Q in the future if you want to update from Oreo
Generation and installation of a magisk-patched boot image for root
Upon successful completion, you will have a fresh, bootloader unlocked and rooted phone that is otherwise stock.
Preparation and requirements:
On the hardware side, you will need a PC with MS Windows installed either directly or as a virtual machine and a high quality USB cable designed for data transfer. Older USB 2.0 hardware is preferred when working with LG phones. There is a long list of software to install.
Minimal adb and fastboot
Instructions: https://forum.xda-developers.com/showthread.php?t=2317790
Download: https://www.androidfilehost.com/?fid=746010030569952951
The LG mobile drivers, http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Dev-Patched LGUP
Instructions and warnings in post #6 with thanks to @ChazzMatt: https://forum.xda-developers.com/lg-v35/help/att-v35-unlocked-wont-verizon-t3958765
Download with thanks to @tecknight for the software: https://androidfilehost.com/?fid=11410963190603845019
9008 Port Driver:
https://raw.githubusercontent.com/g...alcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip
QPST with QFIIL
Some basic instructions: https://androidmtk.com/use-qpst-flash-tool
Download: https://qpsttool.com/qpst-tool-v2-7-480
Download and install each of these programs on your PC in the listed order.
You are also going to need some super important supporting files that make all of this magic possible.
The V35 engineering abl that will give you fastboot with thanks to @vlad48 for making it available: https://www.androidfilehost.com/?fid=1395089523397895796. Yes,it says V20, ignore it, it is fine. Extract abl_a and abl_b, and append a “.img” extension to each. Note the locations on your PC for future use.
The recently available emergency download (EDL) firehose that makes direct partition flashing possible released by Biao on Telegram. It is available here:
https://androidfilehost.com/?fid=4349826312261705871
or as an attachment in @Xsavi’s similar and earlier instructions for the V40: https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
Note its location for later use.
Troubleshooting:
These instructions assume that your phone boots normally. Even with that there can still be issues due to software drivers and pc-hardware. They can be broadly summarized as a difficulty getting the computer to recognize and communicate with the phone and vice-versa. They arise frequently. If you encounter difficulties, review these troubleshooting tips compiled and written by @ChazzMatt and taken from his V30 WTF instructions.
Look in your ADB folder on your PC and confirm all known Windows file extensions enabled, https://goo.gl/YxLRG5.
Confirm all Windows hidden files and folders are visible, https://goo.gl/1jBKne.
Confirm USB debugging is on in Developer Options, and your PC has authorization for your phone, https://goo.gl/DgojL9.
Install another version of ADB. Install as close to the root of your hard drive as possible. X:\ADB where X is your hard drive.
Re-install LG mobile drivers, https://is.gd/Jbrvx1.
Try another USB cable.
Installing this Windows driver found attached to this post, (Thanks @gazzacbr and @FZZF) https://goo.gl/CqqNZT.
Install Google USB driver, (Thanks @s0lidsneak) https://goo.gl/z2Tahw.
Try another USB port on your computer or try cheap USB 2.0 hub, https://is.gd/gM1mM0.
Reboot the computer.
Try another computer. (THIS usually solves the problem, https://goo.gl/x637H1. Kudos if you find an an old Win7 PC, https://goo.gl/EaGMhs.)
Master Reset (full reset of phone using hardware buttons), https://goo.gl/N4LcLD. Phone will be reset anyway after bootloader unlock. Doing it prior may fix something preventing the command from working.
Step 1: Setting an Oreo baseline:
The engineering files for bootloader unlock of the V35 phone are designed to work with Oreo. If you are an Pie or Q, it is highly recommended that you flash back to Oreo. For those of you with the common AT&T V350AWM model that is not on Oreo, there are a couple of points to consider
AT&T does not release flashable roms. If you are on AT&T Pie or eventually Q, there is no going back unless of course you take the time to make a backup of the rom itself. That is not covered in this guide nor am I aware of a guide on how to do this.
AT&T sim-locks its branded V35’s and the menu to unlock is specific to the AT&T rom. You should strongly consider purchasing of a sim-unlock code and applying it before flashing another rom!
To set the baseline:
If you are already on Oreo perform a master reset. To do this, start by turning the phone off. Then press and hold the power and volume - buttons at the same time until you see the LG logo appear. When the LG log appears, release the power button and then press and hold it again while continuing to press the volume – button. Follow the menus to perform the reset.
If you are on Pie or Q, you are going to flash or cross-flash back to Oreo. The kdz's are available for downloaded from https://lg-firmwares.com/lg-lmv350ulm-firmwares/#tab=firmwares. Reports are that roms can be cross-flashed across V35 models with the exception of the Korean V350N. If you are not familiar with the roms, the favored ones are the Google Fi / North American versions for the V350ULM. Down load the latest Oreo version
https://lg-firmwares.com/downloads-file/18971/V350ULM10i_00_NAO_US_OP_0221, md5sum: 64554877b692601d5906d2bdc9691712To flash the rom, turn the phone off, press and hold the volume – button while connecting it to the computer’s USB. The phone screen should show “Download Mode”. Start-up LGUP on your PC, select the rom kdz, and flash it using “Refurbish”. Do not use any other modes or you will have serious trouble!
Step 2: Partition Extraction, Modification and Bootloader Unlock
Enable “OEM Unlock”: Turn on the phone and go through a minimal set-up process. Next go to Settings→ System→ About Phone→ Software info. Repeatedly tap on “Build Number” until you receive a message that you are now a “Developer”. Next go to Next go to Settings→ System→Developer options. Look for “OEM unlock” and flip the switch to on. Exit the “Settings” menus.
Boot the phone in EDL 9008 mode: The “button dance” to put the phone into EDL mode requires quick hands. To increase the likelihood of success, take the phone out of any case to expose the volume buttons. With the phone fully booted and turned on, connect it to your computer by USB. Press and hold the power and volume – keys at the same time. The phone will likely take a screenshoot, keep holding the buttons, afterwards it will bring up a reboot countdown message. With one second left, start pressing the volume + button while still keeping the power and volume – buttons pressed. The phone will show a black screen and windows with make its connection sound if you succeeded in reaching ECL mode. Release the button immediately. Look at your computer, you should also see an entry in the Windows Device Manager under “Ports” that reads:
“Qualcomm HS-USB QDLoader 9008 (COMXX)”
where XX is the port. The phone will just reboot if you didn’t click the volume + button sufficiently fast. Keep trying, you will eventually succeed. If the screen on the phone does go black and you don't see the phone listed in the Windows Device Manager, then you should check installation of 9008 port driver.
Start and configure QFIL: Go to the Start Menu or whatever passes for it on your Windows computer and fire up QFIL. Survey the screen:
You should see “Qualcomm HS-USB QDLoader 9008 XX” next to “Select Port…”.
There should be small text in the lower right corner that reads “Storage Type:”; Select “ufs”.
There is a subheading near the upper left that reads “Select Build Type”. Tick “Flat Build”.
Now using the “Browse…” button under the “Select Programmer", navigate to the folder that contains the firehose file, “prog_ufs_firehose_Sdm845_lgev40.elf” and select it.
Extract partitions: Click on “Tools” in the menu bar of QFIL. Select “Partition Manager”. You will be asked if you selected the correct firehose. If you did then click OK. A screen will now appear that lists partitions on your phone. Scroll down the list and look for “abl_a”, “laf_a”, “abl_b”, and “laf_b”.
Right click on “abl_a”
Select “Manage Partition Data”
Select “Read Data…”
Open a folder and navigate to location where the extracted file is located. The QFIL “Status” output shows the location and filename. On my PC, it reads:
“C:\Users\whoiam\AppData\Roaming\Qualcomm\QFIIL\COMPORT_XX\ReadData_ufs_xxxxx.bin” where XX is the port number and the “xxxxx” are details about the partition name. Copy the file to a dedicated folder and rename it “abl_a.img”.
Repeat the this process for “laf_a”, “boot_a”, “abl_b”, “laf_b”, and “boot_b” partitions. Note the locations of these files as back-ups and also for the following section on rooting.
Use QFIL to get fastboot:
Write the engineering abl’s: In QFIL, do the following:
Right click on abl_a.
Select “Manage Partition Data”
Select “Load Image”
In the dialog, Navigate to the location of the engineering abl_a.img file you downloaded in the preparation section, select it, and click “Open”.
Repeat this same procedure for abl_b.
Erase laf’s: In QFIL, do the following:
Right click on “laf_a”
Select “Manage Partition Data”
Select “Erase”
Confirm that you want to erase
Repeat for laf_b.
Unplug the phone from USB
Press and hold the power and volume - buttons until the LG V35 boot logo appears. Allow the phone to reboot.
Turn the phone off.
Unlock the bootloader:
Enter fastboot mode: Hold the volume + button and plug in the USB cable. The phone will boot to a series of menus that include “Start” and “Power off”.
Run a command prompt as Administrator. If necessary navigate to the directory where you installed adb.exe and fastboot.exe.
Check that the phone communicates with fastboot: Type “fastboot devices” and press enter. It should return details about your device. It reads “LMV350AWMxxxxxxx fastboot” with my phone.
Bootloader unlock: Type “fastboot oem unlock”. Congratulations if it reports OK, your phone is now unlocked. If it reports failed then try another USB port on your PC, a better/different cable, and potentially even another PC.
Reboot the phone
Step 3: Restore download mode and flash to desired rom:
If the current version of Oreo is where you want to be then skip to Step 4.
If you want to upgrade to Pie or eventually Q, then you need to restore the laf_a, laf_b, abl_a, and abl_b partitions to recover download mode. It should be clear from what you have done above with QFIL how to do this.
Download the kdz of your desired rom. The Google/NAO version of Pie is recommended and available at this link, https://lg-firmwares.com/downloads-file/22230/V350ULM20f_00_NAO_US_OP_0218.
To flash the rom, turn the phone off, press and hold the volume – button while connecting it to the computer’s USB. The phone screen should show “Download Mode”. Start-up LGUP on your PC, select the rom kdz, and flash it using “Refurbish”. Do not use any other modes or you will have serious trouble!
Step 4: Install Magisk for Root:
Re-enter EDL mode with the above button dance procedure
Extract boot_a and boot_b partitions: Click on “Tools” in the menu bar of QFIL. Select “Partition Manager”. You will be asked if you selected the correct firehose. If you did then click OK. A screen will now appear that lists partitions on your phone. Scroll down the list and look "boot_a” and “boot_b”.
Generate a Magisk-patched booted image working directly with the phone:
Download a stable version of Magisk Manager from the official website: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445. It should be saved in the “Download” folder.
In Settings, navigate to Apps & Notifications→ Special access → Install unknown apps. Click on File Manager and set it to allowed.
Open the “File Manager” app and navigate to the Download folder.
Select and install the “MagiskManager-v7.5.1.apk” file keeping in mind that the version numbers may be different.
Connect the phone to USB and place it in file transfer mode.
Copy boot_a.img and boot_b.img to the phone Download folder
Start “MagiskManager” and select “Install”. When presented with the option, tap “Select and Patch a File”.
Navigate to the “Downloads” folder where and select boot_a.img.
There will now be a file named “magisk_patched.img” in the “Downloads” folder. Change its name to magisk_patched_a.img.
Repeat this process with boot_b.img.
Install the Magisk-patched boot images using the PC:
Copy the magisk_patched_a.img and magisk_patched_b to the windows computer.
Put the phone into 9008 EDL mode with the button dance described above.
Start QFIL, configure it as described above, and then click on “Tools” in the menu bar of QFIL and Select “Partition Manager”.
Scroll through the list of partitions and locate boot_a. Right click on it and select “Load Image”. Point it to the magisk_patched_a.img file.
Repeat the previous step for boot_b and load the magisk_patched_b.img file
Reboot your rooted phone.
Step 5: Remove Root Checker: (Added 20200409)
I say with sarcasm that another way that LG has made our lives better was to implement a root-check and monitoring system. Many here are familiar with the root check daemon from the V30. There is a root-check disable twrp package to fix this problem. Installation and use of TWRP for the V35 is tricky. Don't worry, there is another way.
Put the phone in USB debug mode
Connect to your computer
With adb from a command prompt on the computer do the following
adb devices <-- If your devices is properly connect and recognized, adb will respond
List of devices attached
LMV350XXXXXXXXX device
adb shell <-- If you have a shell into the phone you will now see
judyp:/ $
pm uninstall -k --user 0 com.lge.srtc <-- This command removes the root checker, if it succeeds you will get the response:
Success
pm uninstall -k --user 0 com.lge.mlt <-- This command removes the LG monitor, if it succeeds you will get the response:
Success
Happy Rooting!
Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?
THANK YOU for this. Seriously. Really well done. I can't wait to try it if I ever get my phone back into shape where I CAN try it. ?
There are several posts by owners of AT&T branded V35's who cross-flashed to the Korean V350N Pie rom successfully. They were in a rush for Pie and it was released for Korean models first. Still, I have in my notes not to do the reverse, but I can't find the link. Hypothetically, one can recover from about anything using 9008 mode and QFIL provided you have back ups of the partition images of your phone.
fpozar said:
Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?
Click to expand...
Click to collapse
cmrntnnr said:
There are several posts by owners of AT&T branded V35's who cross-flashed to the Korean V350N Pie rom successfully. They were in a rush for Pie and it was released for Korean models first. Still, I have in my notes not to do the reverse, but I can't find the link. Hypothetically, one can recover from about anything using 9008 mode and QFIL provided you have back ups of the partition images of your phone.
Click to expand...
Click to collapse
I was one of those who leaped to the Korean KDZ. Now I am running NAO firmware. Guide looks well written. I might wind up taking the leap. Good job bro!
Thanks, I follow your steps very carfully, and now I have a rooted v35.
Nicely done. Thank yoh for sharing the result.
fpozar said:
Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?
Click to expand...
Click to collapse
vavoo said:
Thanks, I follow your steps very carfully, and now I have a rooted v35.
Click to expand...
Click to collapse
So due to prior.... mishaps, my phone will not boot ("all slots are unbootable!"), and fastboot produces "Flashing Unlock is not allowed" every time the OEM unlock is attempted. What should I do?
I am stuck at Fastboot Mode. It says the "Device state - Unlocked", but when if I choose Start or Power off/on my phone it just goes back into fastboot everytime.
1. I installed and flashed the Pie rom you linked in step 1
2. I turned "Oem unlock" to On.
3. placed the phone in 9008 mode, backed up abl_a, laf_a, boot_a, abl_b, laf_b, and boot_b.
Loaded the img to abl_a and abl_b.
Finally, Erased laf_a and laf_b
4. within fastboot, unlocked bootloader
Any ideas ?
If the phone unlocked, go back into 9008 EDL mode and restore the laf and abl images using your backups. That should get you booting.
dave1567 said:
Any ideas ?
Click to expand...
Click to collapse
1. Download the attached EDL.zip
2. Extract it to a local folder on your PC
3. While your V35 is in fastboot mode plug it to your PC via USB (USB2 port preferred)
4. Double click on RebootEDL.bat
5. Phone will enter 9008 (EDL) mode screen will be black.
6.Using QFIL flash back your PIE abl_a and abl_b
7. Using QFIL flash attached FTM partition from FTMV35PIE.zip.
8. Hold Vol-and power to reboot.
vlad48 said:
1. Download the attached EDL.zip
2. Extract it to a local folder on your PC
3. While your V35 is in fastboot mode plug it to your PC via USB (USB2 port preferred)
4. Double click on RebootEDL.bat
5. Phone will enter 9008 (EDL) mode screen will be black.
6.Using QFIL flash back your PIE abl_a and abl_b
7. Using QFIL flash attached FTM partition from FTMV35PIE.zip.
8. Hold Vol-and power to reboot.
Click to expand...
Click to collapse
I didn't use your bat since it looks like I can still boot into 9008 mode with the button dance method.
Unfortunately, still nothing!
I flashed my abl_a.img and abl_b.img backups I made to the abl_a/b partitions and flashed your FTM_BL.img to my FTM partition, but it didn't seem to do anything except cause some graphical glitches within fastboot menu (everything still functioned though)
Just in case, I re-locked my phone (fastboot oem lock) and started the QFIL process over (flashing with engineered abl_a and abl_b imgs)
Then within fastboot mode, I ran "fastboot oem unlock" a few times because it fails, but finally it went through
Now the phone is unlocked again, but still just always just boots into fastboot mode!
Of course it will boot only to fastboot as you are using engineering abl from Oreo - please understand there is a signature check match which fails and you will not be able to continue booting.
So, in brief, you need to have all partitions on respective bootable slot form either Oreo or Pie kdz version. So you need to be sure that you flashed your PIE abl wither via QFIL or via LGUP.
vlad48 said:
Of course it will boot only to fastboot as you are using engineering abl from Oreo - please understand there is a signature check match which fails and you will not be able to continue booting.
So, in brief, you need to have all partitions on respective bootable slot form either Oreo or Pie kdz version. So you need to be sure that you flashed your PIE abl wither via QFIL or via LGUP.
Click to expand...
Click to collapse
Unfortunately, I don't understand. Thanks for trying to help though.
Anyways, I managed to fix the problem and I'm all set.
- Restored my laf_a and laf_b partitions
- Booted into download mode and re-installed the pie image with LG Up.
- Was now able to boot normally
- Followed the instructions in the guide to get magisk installed and now I'm all set!
Thanks all and hope this helps someone
I scouted my way through these very same steps a couple weeks ago. Soft bricked my device a couple times ? but eventually got her there. Glad too see a dedicated guide is out now. Only problem I've run into is the ctsprofile:fail problem. Been able to fix with spoof pixel fingerprints but it's not ideal. Still looking for solutions if anyone knows anything.
Iantuition said:
So due to prior.... mishaps, my phone will not boot ("all slots are unbootable!"), and fastboot produces "Flashing Unlock is not allowed" every time the OEM unlock is attempted. What should I do?
Click to expand...
Click to collapse
What is the minimum needed for you to enter download mode? I have backups of most partitions i will be happy to share and you can use Qfil to flash those to get to download mode then use LGUP to flash a normal kdz? If so, let me know.
so somehow between qfil and getting fastboot i've got myself in trouble. i dont understand what i did wrong but i got stuck in a fastboot loop and tried following some of the fixes mentioned previously in this thread. when i get back to qfil and try to go to partition manager it wont let me see any of the partitions and shows various sahara errors and fails in the log box. can someone please help idk what to do
Sorry to hear that. The first time I tried to use QFIL I got a Sahara error and could not see partitions. It was resolved by reinstalling the 9008 port driver and then QPST in that order. It happened again later when windows tries to be helpful by automatically reinstalling drivers when the phone is plugged in but with a mode change.
Flowtron3000 said:
so somehow between qfil and getting fastboot i've got myself in trouble. i dont understand what i did wrong but i got stuck in a fastboot loop and tried following some of the fixes mentioned previously in this thread. when i get back to qfil and try to go to partition manager it wont let me see any of the partitions and shows various sahara errors and fails in the log box. can someone please help idk what to do
Click to expand...
Click to collapse
Will this help me sim/carrier unlock my v35awm?
Can you lock the bootloader after this is done and keep root? Need it for banking apps.
Guide updated!!!!!
If you wanna get back to stock ROM and relock bootloader + get OTAs working again, this is the right place!
DISCLAIMER: Relocking bootloader erases all your data/internal storage and (off course) remove TWRP/modules/root, so do a backup of all your data first. Also, I'm not responsible for any bricked devices (phones, SD Cards, etc). I tested it in my XT1955-1 and it worked fine, but we all know that errors might occur.
Finally, let's go to the steps.
Step 1 - Downloading necessary files
Download Android Platform Tools here and then extract it.
Install Motorola Drivers on your PC (download here).
Download the lastest firmware according to your variant/software channel here and extract it in the same folder you had extracted Android Platform Tools.
Download the "Lock Script" here, according to your android version and PC's OS.
For example: if your PC uses Windows as OS, and your phone is in android 10, download the "Lock-10q_windows.bat" file.
Or if you have a Linux distro on your PC and android 9 on your phone, download "Lock-9pie_linux.sh" file.
Place the file inside the platform-tools folder, where the ROM was extracted too.
Step 2 - Preparing your phone
Remove all your google account in device's settings and then go to Developer Options. Enable Android debugging and OEM unlocking (if you can't enable OEM unlocking, you may need to root your device first to get it avaible again (see Rooting thread)).
Power off your phone and put it fastboot mode. Connect it on PC using USB cable.
Step 3 - Installing Stock ROM and re-locking bootloader
Just double click on the Lock.bat/.sh file and it will reflash stock ROM and lock bootloader. Now all you have to do is wait till it finishes. This should take a few minutes to be done.
The phone will boot automatically after the last command is executed.
It seems to be a little hard, but it's easy. If you have any questions, let me know, I'll try to answer ASAP.
Very nice, it's really working! Thanks!
Works on xt1955-4 thanks very much, will the warranty still apply?
piotr1859 said:
Works on xt1955-4 thanks very much, will the warranty still apply?
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Will tell you if warranty is voided.
Sent from my ali using XDA Labs
piotr1859 said:
Works on xt1955-4 thanks very much, will the warranty still apply?
Click to expand...
Click to collapse
Yes, should work fine. Afaik, once you unlock your bootloader, your warranty is avoid, theoretically. But I guess you can send it to service center (if it's needed) with no problems. They don't always check if you have unlocked your bootloader or not.
Warning: Due to some changes in bootloader and people getting hard bricks in February security patch, i don't recommend to relock bootloader in that version, do it in December security patch instead!
Hello guys. I have Motorola Moto G7 Power (XT1955-4). I've tried to put in twrp and a rom, but when I rebooted my device it don't power on anymore. So I've searched many guides to repair. I've used "blankflash" and after many times I was finally power on my device and go in Fastboot Mode. But now there's another problem. When I connect with usb and open CMD and type "adb devices" appear:
LIST OF DEVICES ATTACHED
or
WAITING FOR DEVICES
I tried many things to fix it but nothing work. Now I've uninstalled everything on my pc, drivers too.
Maybe I've installed bad "blankflash"???
How can I fix my troubles?
DarkAngelNoctis said:
Hello guys. I have Motorola Moto G7 Power (XT1955-4). I've tried to put in twrp and a rom, but when I rebooted my device it don't power on anymore. So I've searched many guides to repair. I've used "blankflash" and after many times I was finally power on my device and go in Fastboot Mode. But now there's another problem. When I connect with usb and open CMD and type "adb devices" appear:
LIST OF DEVICES ATTACHED
or
WAITING FOR DEVICES
I tried many things to fix it but nothing work. Now I've uninstalled everything on my pc, drivers too.
Maybe I've installed bad "blankflash"???
How can I fix my troubles?
Click to expand...
Click to collapse
If the device is in fastboot mode only fastboot commands will work
Code:
fastboot getvar all
edit:grammer
Sent from my ali using XDA Labs
sd_shadow said:
If the device is in fastboot mode only fastboot commands work like
Click to expand...
Click to collapse
Ok. Thanks!
LuisLFSS said:
Warning: Due to some changes in bootloader and people getting hard bricks in February security patch, i don't recommend to relock bootloader in that version, do it in December security patch instead!
Click to expand...
Click to collapse
hey would it be safe to use this method on security patch version April1,2020? if not please point me in the right direction.
thanks
darko454 said:
hey would it be safe to use this method on security patch version April1,2020? if not please point me in the right direction.
thanks
Click to expand...
Click to collapse
Yes, it's safe. Now we have blankflash so it's safe
LuisLFSS said:
Yes, it's safe. Now we have blankflash so it's safe
Click to expand...
Click to collapse
ok thanks!
LuisLFSS said:
Yes, it's safe. Now we have blankflash so it's safe
Click to expand...
Click to collapse
Hi, can you send a link to blankflash for XT1955-1?
THANK YOU.
hawkdown77 said:
Hi, can you send a link to blankflash for XT1955-1?
THANK YOU.
Click to expand...
Click to collapse
Yes, join in my group: t.me/motog7brasil
LuisF201707 said:
If you wanna get back to stock ROM and relock bootloader + get OTAs working again, this is the right place!
DISCLAIMER: Relocking bootloader erases all your data/internal storage and (off course) remove TWRP/modules/root, so do a backup of all your data first. Also, I'm not responsible for any bricked devices (phones, SD Cards, etc). I tested it in my XT1955-1 and it worked fine, but we all know that errors might occur.
Finally, let's go to the steps.
Step 1 - Downloading necessary files
Download Android Platform Tools here and then extract it.
Install Motorola Drivers on your PC (download here).
Download the lastest firmware according to your variant/software channel here and extract it in the same folder you had extracted Android Platform Tools.
Step 2 - Preparing your phone
Remove all your google account in device's settings and then go to Developer Options. Enable Android debugging and OEM unlocking (if you can't enable OEM unlocking, you may need to root your device first to get it avaible again (see Rooting thread)).
Power off your phone and put it fastboot mode. Connect it on PC using USB cable.
Step 3 - Installing Stock ROM
If you're already in stock ROM with no modules and stuff installed on it, just skip this and jump to the next step. If you're not, then stay here.
Open CMD (command prompt) in the same folder you had extracted firmware and android platform tools.
Shift+right click and then "Open command window here" or just type CMD in the folder path bar at the top in windows explorer. Run this commands all at once in CMD:
Once it is done, DON'T power on your phone, just leave it as it is and let's go to the last step.
Step 4 - Relocking Bootoader
In cmd, run this commands all at once
Done! The phone will boot automatically after the last command is executed.
It seems to be a little hard, but it's easy. If you have any questions, let me know, I'll try to answer ASAP.
Click to expand...
Click to collapse
There is an bat file out to relsash stock rom with out trying all that stuff in manually
Help
I followed all the steps and managed to block the bootloader but when I turn on the phone I get "start up failed" can someone help me.
I did it in the April 1 patch
JPalomo1997 said:
I followed all the steps and managed to block the bootloader but when I turn on the phone I get "start up failed" can someone help me.
I did it in the April 1 patch
Click to expand...
Click to collapse
Which android version? There's april security patch for android 9 and 10...
roadkill42 said:
There is an bat file out to relsash stock rom with out trying all that stuff in manually
Click to expand...
Click to collapse
I know... I'll update the thread soon
chrisbchrisb85 said:
For step 4 relocking the bootloader what does "run these commands all at once" mean??? As soon as I lock the bootloader I can no longer flash anything else, therefore still stuck with a boot screen warning
Click to expand...
Click to collapse
"run these commands all at once" = copy all the commands and execute them in cmd...
And which android version did you install? because the commands to flash android 10 are different than android 9 ones
Guide updated!!!!!
I removed those annoying commands and put a link to download Scripts that already do everything automatically. Now the guide is simpler and easier
Hello, I downloaded and installed android beta update https://gauss-componentotacostmanua...22/08/03/b5192ec34f094ad9bb76e5554cd69f89.zip from https://www.xda-developers.com/oneplus-7-7t-pro-android-12-oxygenos-12-open-beta-2/amp/ and since then the device is just booting in loops and not going ahead. I get the boot reason error as attached. The boot logo has also changed.
My device did not had developer module enabled nor had I backed up any data from my mobile before installing the update.
I desperately want to recover data from my phone before formatting it. Please assist. Thanks a lot.
kiranlalge said:
Hello, I downloaded and installed android beta update https://gauss-componentotacostmanua...22/08/03/b5192ec34f094ad9bb76e5554cd69f89.zip from https://www.xda-developers.com/oneplus-7-7t-pro-android-12-oxygenos-12-open-beta-2/amp/ and since then the device is just booting in loops and not going ahead. I get the boot reason error as attached. The boot logo has also changed.
My device did not had developer module enabled nor had I backed up any data from my mobile before installing the update.
I desperately want to recover data from my phone before formatting it. Please assist. Thanks a lot.
Click to expand...
Click to collapse
Try to reboot into recovery, then normal reboot.
Did that already. No luck :-(
kiranlalge said:
Did that already. No luck :-(
Click to expand...
Click to collapse
Data must be formatted to boot
HueyT said:
Data must be formatted to boot
Click to expand...
Click to collapse
Sorry I cannot afford to format the device as I'm desperate to recover the data.
Take phone to repair shop to download data via adb commands using laptop
Also try switching slots in fastboot mode: "fastboot set_active other" and then "fastboot reboot"
HueyT said:
Take phone to repair shop to download data via adb commands using laptop
Click to expand...
Click to collapse
I have ADB utilities on my laptop. I connect my device to my laptop via USB cable and then do "adb devices" on the command prompt. It shows no devices. Perhaps this happens because my device was not rooted? Is there any other way I can access files on my device using adb?
HueyT said:
Also try switching slots in fastboot mode: "fastboot set_active other" and then "fastboot reboot"
Click to expand...
Click to collapse
Please can you elaborate a little more on this? Where to switch slots? Can we connect over WhatsApp or a ZOOM call please?
kiranlalge said:
Please can you elaborate a little more on this? Where to switch slots? Can we connect over WhatsApp or a ZOOM call please?
Click to expand...
Click to collapse
Enable USB debugging in developer options
Spoiler
HueyT said:
Enable USB debugging in developer options
Click to expand...
Click to collapse
The device needs to be booted successfully to enable USB debugging. Booting is the fundamental problem. How can I enable USB debugging without booting the device?
The device needs to be booted successfully to see this screen. Booting is the fundamental problem. How can I enable USB debugging without booting the device?
Phone needs to be off. Try holding down vol. Down button, power button til it reboots into bootloader mode while plugged into usb-c to USB-a cable to laptop. Then type "fastboot devices" on laptop while changed into adb subdirectory with "command C:/ prompt"
HueyT said:
Phone needs to be off. Try holding down vol. Down button, power button til it reboots into bootloader mode while plugged into usb-c to USB-a cable to laptop. Then type "fastboot devices" on laptop while changed into adb subdirectory with "command C:/ prompt"
Click to expand...
Click to collapse
I appreciate you trying to help me promptly. Thank you.
I tried doing what you advised. The command did not show anything. Photos attached.
You need to unlock bootloader by using Superboy msmtool, but will lose all data
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
You shouldn't mess with oos12 with locked bootloader as it can lose data
You could try to manually flash each file using fastboot (fastboot devices must show a number so install correct OnePlus and adb drivers for windows 10) --use payload dumper to extract all files from payload.bin from Indian op7t rollback zip below. Just don't do "fastboot -w" as that will format your data
https://oxygenos.oneplus.net/OnePlus7TOxygen_14.I.31_OTA_0310_all_2112101928_downgrade_327348e7ed1f4427.zip
HueyT said:
You could try to manually flash each file using fastboot (fastboot devices must show a number so install correct OnePlus and adb drivers for windows 10) --use payload dumper to extract all files from payload.bin from Indian op7t rollback zip below. Just don't do "fastboot -w" as that will format your data
https://oxygenos.oneplus.net/OnePlus7TOxygen_14.I.31_OTA_0310_all_2112101928_downgrade_327348e7ed1f4427.zip
Click to expand...
Click to collapse
Thank you. I have just started downloading this file (2.6 GB) on my laptop. Yes I am very keen to save my data before formatting. Please can you guide on the next steps to do after the download completes?
I use Windows 7. Is there a link to install correct OnePlus and adb drivers in Windows 7?
kiranlalge said:
Thank you. I have just started downloading this file (2.6 GB) on my laptop. Yes I am very keen to save my data before formatting. Please can you guide on the next steps to do after the download completes?
I use Windows 7. Is there a link to install correct OnePlus and adb drivers in Windows 7?
Click to expand...
Click to collapse
Right OK so I have downloaded the ZIP package and have also managed to extract the payload.bin file. See file contents in the attached image.
Please can you guide on the next steps hereafter? I use Windows 7. Is there a link to install correct OnePlus and adb drivers in Windows 7?
kiranlalge said:
Right OK so I have downloaded the ZIP package and have also managed to extract the payload.bin file. See file contents in the attached image.
Please can you guide on the next steps hereafter? I use Windows 7. Is there a link to install correct OnePlus and adb drivers in Windows 7?
Click to expand...
Click to collapse
I think this is getting closer. I managed to install drivers as in the attached. Please take a look. 3 out of 4 have yellow triangles not sure if that means any issue. The 4th one appears only when I connect the device to laptop via a cable.
Only works on win10/11
HueyT said:
Only works on win10/11
Click to expand...
Click to collapse
OK. I still tried on Windows 7 and I got the attached. If I manage to change the slot from a to b using "https://www.droidwin.com/fix-failed-remote-slot-change-is-not-allowed-in-lock-state/", then will I loose any data? Again, I'm very keen to retrieve my data.
kiranlalge said:
OK. I still tried on Windows 7 and I got the attached. If I manage to change the slot from a to b using "https://www.droidwin.com/fix-failed-remote-slot-change-is-not-allowed-in-lock-state/", then will I loose any data? Again, I'm very keen to retrieve my data.
Click to expand...
Click to collapse
Yes, unlocking BL will wipe data
HueyT said:
Yes, unlocking BL will wipe data
Click to expand...
Click to collapse
Thats sad :-( I'm looking for a solution to retain all my data in a situation where my device is just booting in loops (not reaching the home screen), developer option is disabled and USB debugging is also disabled. Please help.
kiranlalge said:
Thats sad :-( I'm looking for a solution to retain all my data in a situation where my device is just booting in loops (not reaching the home screen), developer option is disabled and USB debugging is also disabled. Please help.
Click to expand...
Click to collapse
All you can do is keep repeating reboot to recovery, normal reboot, reboot to bootloader, reboot to recovery, normal reboot, while praying and hoping that your phone boots up.
kiranlalge said:
Thats sad :-( I'm looking for a solution to retain all my data in a situation where my device is just booting in loops (not reaching the home screen), developer option is disabled and USB debugging is also disabled. Please help.
Click to expand...
Click to collapse
Does "fastboot devices" give you numbers and letters?
HueyT said:
Does "fastboot devices" give you numbers and letters?
Click to expand...
Click to collapse
Yes. It printed the serial no. of my device.
DISCLAIMER:
Please post failures and successes. Keep it relevant, everything else to the DMs please. It makes it easier for others to Q&A. Everyone thanks you for your understanding.
***IF YOU ARE NEW BEWARE!!! BEFORE YOU CHANGE ANYTHING MAKE A BACKUP. LET THIS APPLY TO EVERYTHING. WHENEVER THE OPTION TO BACKUP IS AVAILABLE IT WOULD BE WISE TO DO SO. FAILURE TO BACKUP YOUR DEVICE WILL RESULT IN LOSS OF DATA***
ALL LINKS ALLOWED, APPROVED AND/OR UTILIZED BY XDA. SPECIAL THANKS TO ALL THE DEVS WHO CREATED THE TOOLS WITHOUT WHICH THIS WOULD NOT BE POSSIBLE. I DIDN'T BUILD ANY SOFTWARE MENTIONED IN THIS POST. IF YOU BRICK YOUR PHONE, DO NOT BLAME ME. I'M NOT TELLING YOU HOW TO DO IT, BUT NARRATING A GUIDE TO HOW I DID IT. YOU HAVE BEEN WARNED
REVVL V+ 5G TMOBILE VARIANT ANDROID 11
IT SHOULD BE NOTED THAT SOME PEOPLE ARE REPORTING LOSING WIFI AFTER ROOT, AS HAVE I. I HAVE NOT YET FIGURED OUT HOW TO FIX THIS. I'M THANKFUL FOR ANY ASSISTANCE. FLASHED STOCK BOOT_A DIDN'T FIX IT, ONLY FLASHING BACK TO STOCK ROM. ON ANOTHER IDENTICAL PHONE DIDN'T LOSE WIFI. YOUR GUESS IS AS GOOD AS MINE. LOOKING INTO IT, NO PROMISES
Without further ado, let's start at the unboxing.
1) PREP PHONE:
power on. navigate to settings>about phone and tap "build number" seven times to enable developer options.
navigate to settings>system>developer options and enable "USB Debugging" and "OEM unlock"
FIRST disconnect the device from your comp THEN power the device off.
2) DONWLOAD PYTHON & DRIVERS:
Python
BE SURE TO TICK THE BOX THAT SAYS ADD PYTHON TO PATH and install.
Download and install mediatek drivers from here:
Mediatek USB drivers
Download and install UsbDk from here:
UsbDk
Download MTK client from here:
MTK client
and extract to the desktop. Open the folder and move everything to
C:>Users>[username]>AppData>Local>Programs>Python>Python310
In the 310 directory press Alt + D to highlight your directory path and type CMD and hit enter. This opens a command prompt in the Python310 directory.
In cmd type this command without "":
"python setup.py install"
Go make a sandwich. Preferably turkey with mustard.
When you finish your sandwich, come back and type this command without "":
"python -m pip install -r requirements.txt"
Do not exit the command window.
3) BOOT INTO B ROM MODE:
This is kind of tricky when you don't know it. The screen will will be black. Sometimes, the device will not even vibrate. There's no sunbathing android, no "No Command", no fastboot, no download mode, no recovery- nothing, nada, zip, zilch, goose egg.
Make sure you unplug the device entirely from charger and pc BEFORE you power off. Now that you properly powered off, hold ONLY BOTH volume + - keys while you connect it to your PC. Try to be quick about it. DO NOT TOUCH THE POWER KEY. Continue to hold the volume keys until you know your device connected. When you hear your device connected jingle immediately let go. The screen will remain blacked out and unresponsive. It's normal.
Let's make sure we did it right. Enter the following command without ":
"python mtk e metadata,userdata,md_udc"
Disconnect and power on. If the device has been reset, then you have confirmation.
4) PREP PHONE AGAIN (STEP 1):
5) UNLOCK BOOTLOADER:
Enter the following command without ":
"python mtk da seccfg unlock"
~To relock the bootloader in the future use command "python mtk da seccfg lock". If you flash a custom recovery/ROM and want to return to stock, then you must unroot with magisk first, then flash stock ROM with SP flash tool at the end of this post~
Power on. On the splash screen you will see system type:
"Orange State
Your device is corrupted. Device has been unlocked and cannot be trusted. Press Power key to boot.
Will Reboot in 5 seconds."
This will happen each time you boot the device because your bootloader is now unlocked.
6) PREP PHONE AGAIN (STEP 1):
7) ENABLE ADB FASTBOOT COMMANDS:
Download sdk platform tools here:
sdk platform tools
Extract.
Navigate to the platform tools folder and type Alt+D to highlight directory and type CMD to open a cmd window in platform tools.
Connect device to pc and choose file transfer.
Enter the following command without ":
"adb devices"
A prompt will appear on your phone, click allow.
Enter the following command (again) without ":
"adb devices"
First you'll see a random, arbitrary number. Second time you should see your device serial number and "Authorized", "Allowed", or "Device".
Keep this cmd window open.
8) DOWNLOAD MAGISK AND PATCH BOOT IMG:
Download Magisk from here:
Magisk
Move it to your phone and install. You'll need to allow the installation from unknown sources.
Download firmware from here:
T-Mobile_REVVL_V%252B_5G.zip
Unzip and move boot_a to the downloads folder on your phone.
On your phone, open Magisk and click install and choose boot_a.
Make sure magisk_patched file is in your phone's download folder.
In your platform tools cmd window enter the following command without ":
"adb pull /sdcard/Download/magisk_patched_[numbers].img"
9) ENTER FASTBOOT MODE:
Disconnect device and power off. Hold Vol - and power to enter fastboot mode.
Connect device to PC.
10) ACHIEVE ROOT:
***NOTE: IN THIS STEP YOU MUST LOCATE THE PATCHED FILE ON YOUR PC AND COPY AS PATH. PASTE IT IN THE CMD WINDOW IN PLACE OF "[path to patched file]"***
In the platform tools cmd window enter the following command without ":
"fastboot flash boot [path to patched file]"
Now that you've achieved root, you can play around a little bit. But be careful what you go deleting if you get debloat happy like me and delete your NVRAM & wifi. Just in case you do, here's how to return to stock.
NVRAM backup. This video makes it look easy as pie. (It IS easy)
NVRAM Backup Tutorial
Now we have to bypass DA else SP flash tool will not be able to flash ROM.
Open cmd window and type the following without "":
"python -m pip install pyusb pyserial json5"
Then, update by entering the following command without "":
"python.exe -m pip install --upgrade pip"
Download LIBUSB:
LIBUSB
Run LIBUSB Win 32 filter installer and select Mediatek driver
Enter B ROM mode and connect to PC
Navigate to bypass tool and open "brom.bat"
Close cmd...
Run "flash_tool.exe" in sp flash folder
Options>options>connection tick UART
That's it. Now you can flash with sp flash without encountering error
Here is a helpful link that came from a senior mod:
mtk tool
Download SP Flash tool here:
SP Flash
Extract and launch flash_tool application
Download scatter mt6833 here:
MT6833_scatter.txt
Download bypass tool from here:
bypass tool
download rom2box:
rom2box
Download OTA and use a payload dumper to extract boot and scatter. You can also get DA, but it does nothing. You must bypass DA in order to flash ROM.
OTA
THIS SECTION IS FOR LATER REFERENCING, DISREGARD ANYTHING BELOW THIS
[A13 ota news https://www.t-mobile.com/support/devices/software-updates/t-mobile-revvl-v-plus-android-update]
[Twrp https://www.xda-developers.com/twrp-3-6-0-release-android-11-support/?_ga=2.195721068.1777813512.1675477697-1767133243.1662515191]
~fastboot set_active other
~fastboot flash recovery_a twrp file
~fastboot flash recovery_b twrp file
[Sprout https://dl.twrp.me/sprout/]
https://forum.xda-developers.com/t/guide-porting-twrp-without-source.3843473/
https://www.mediafire.com/download/sxq4cz8bddmr49
https://www.mediafire.com/file/irigs9iviy3sobw/T-Mobile_REVVL_V%2B_5G.zip/file
https://download1526.mediafire.com/ih0pus48i1kg/mwl6h20noutg005/revvplus.zip
[Patched boot_a pending verification https://forum.xda-developers.com/attachments/magisk_patched-25100_hiu69-img.5648347/]
[FLASH STOCK MODEM FILE]
My next guide will be how to use assurance wireless with ANY phone. I'm using assurance wireless on my Oneplus N200 (DE2118).
Hi. I read many posts of yours regarding the REVVL V+ 5G, I was encouraged by your progress, and took comfort that someone else had some of the same struggles that I did. I was able to unlock the bootloader, I was able to root the phone (using an img file posted by someone else here; I hadn't yet read your root recipe), but I was no longer able to connect to wifi. (is this familiar?) In trying to undo the mess, I ended up making my phone unbootable.
I wanted to install stock ROM from scratch. I read your instructions, but there's no scatter file in the ROM that you posted. So I'm confused.
I figured that I could install the stock ROM zip via TWRP; I googled and found a TWRP for "Sprout" (the codename of our device), but for the life of me I couldn't install it on my phone, no matter what I tried.
You're ahead of me here; perhaps you can get me on track. Right now, my phone isn't booting at all.
Thank you!
smuskat said:
Hi. I read many posts of yours regarding the REVVL V+ 5G, I was encouraged by your progress, and took comfort that someone else had some of the same struggles that I did. I was able to unlock the bootloader, I was able to root the phone (using an img file posted by someone else here; I hadn't yet read your root recipe), but I was no longer able to connect to wifi. (is this familiar?) In trying to undo the mess, I ended up making my phone unbootable.
I wanted to install stock ROM from scratch. I read your instructions, but there's no scatter file in the ROM that you posted. So I'm confused.
I figured that I could install the stock ROM zip via TWRP; I googled and found a TWRP for "Sprout" (the codename of our device), but for the life of me I couldn't install it on my phone, no matter what I tried.
You're ahead of me here; perhaps you can get me on track. Right now, my phone isn't booting at all.
Thank you!
Click to expand...
Click to collapse
Hey, I finished the guide. You can return to stock following the guide above. As you may have noticed I edited this message instead of posting again. It's okay, cause I brought good news, right? Cheers
R41N MuTT said:
i totally forgot, yeah, i will look up the proper method to install twrp. it's supposed to be easy. i thought i was going to have to port twrp-and i still might- so i'm looking into it. i need to flash twrp myself. there is supposed to be a way to use rom2box or spflash or twrp or something to make a flashable zip. i don't know if that's a thing. it seems to me somebody needs to build a preinstaller that automatically flashes each img. for you. like a 1 click. if we can get twrp on this, that's the next step. to make a flashable zip. or somehow one click installer. i imagine if i did, it would only work for this phone, but could be modified for similar devices. i know tcl has a software like that. they plug a phone up and click one button. on their end it's one folder and that program does the rest. that program is what i want to write. reverse engineer this shiz and get a complete understanding of it. i know good and well the folks at tcl aren't sitting on a cmd window using adb to flash dozens of duplicate images time and time again for each device they build. it's screw it together, plug it up, click a button and test. they already have all the files preloaded and they have a preinstaller that pretty much instantly flashes the software. damn, wouldn't it sure be nice to have? but i don't foresee anybody leaking it any time soon. maybe if you have the cheese
Click to expand...
Click to collapse
Download TWRP for sprout
Download TWRP Open Recovery for sprout
dl.twrp.me
smuskat said:
Download TWRP for sprout
Download TWRP Open Recovery for sprout
dl.twrp.me
Click to expand...
Click to collapse
Did you see this? https://www.xda-developers.com/twrp-3-6-0-release-android-11-support/
R41N MuTT said:
Did you see this? https://www.xda-developers.com/twrp-3-6-0-release-android-11-support/
Click to expand...
Click to collapse
I looked; our REVVL does not seem to be listed in the list of supported devices.
smuskat said:
I looked; our REVVL does not seem to be listed in the list of supported devices.
Click to expand...
Click to collapse
And may I ask for a clarification, please: You wrote above, "the firmware links i sent you- there should be at least 2 different ones, and an OTA... well, if you open the root folder and type 'scatter.txt' in the search bar it will pop up." In your post, I see 2 links to firmware; one is called https://www.mediafire.com/download/sxq4cz8bddmr49l, and one is called https://www.mediafire.com/file/irigs9iviy3sobw/T-Mobile_REVVL_V%2B_5G.zip/file. I downloaded both. I clicked on the downloaded file, and in the search bar, I searched for "scatter.txt", and got no results. What am i doing wrong? Thanks
smuskat said:
I looked; our REVVL does not seem to be listed in the list of supported devices.
Click to expand...
Click to collapse
It needs to be ported still. Unless it's already ported I'm working on it now. Nightmare. I'm trying to follow a guide on here about porting TWRP... Going slow...
OTA
https://r4---sn-npoldn76.gvt1.com/packages/data/ota-api/package/72d80093722599cd459bca02504f22cbf3421dd2.zip?mh=Rs&pl=21&cm2rm=sn-8qj-i5ozd7r,sn-i3bdr7s&req_id=37ad1f0feba7fd94&cmsv=e&ipbypass=yes&rm=sn-8qj-i5olz7l&redirect_counter=3&cms_redirect=yes&mip=117.4.250.39&mm=34&mn=sn-npoldn76&ms=ltu&mt=1672034446&mv=m&mvi=4
Firmware
T-Mobile REVVL V+ 5G
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Here is the link to the scatter.txt for mt6833 (revvl v+).
MT6833_Android_scatter.txt
Shared with Dropbox
www.dropbox.com
Tmobile just recently announced the release of the a13 update. It's supposed to be before the end of february.
Software Updates
Visit T-Mobile Support for help with phones & internet devices, plans & services, billing, and more!
www.t-mobile.com
Message edited at completion of guide. Irrelevant content removed.
After installing the modified boot img with fastboot my phone bricked and i cant fix it, it just crashes on boot and loops back whenever i try to normal boot.
If there's any help you can offer I'd appreciate it.
vinnie215215 said:
After installing the modified boot img with fastboot my phone bricked and i cant fix it, it just crashes on boot and loops back whenever i try to normal boot.
If there's any help you can offer I'd
Click to expand...
Click to collapse
Edited: guide complete. Try it now.
R41N MuTT said:
When your phone boots up do you see system font on the screen? It should prompt you to press power to boot normally, otherwise it will continue to reboot. It's because the bootloader is unlocked and you must press power to acknowledge this or else the phone will boot loop. Does this help? If not, get another phone and download magisk and try to patch boot_a again. You can use another device to do all those steps to get the file ready. Pull it, plug in your revvl v+ again and try flashing it. You can also try a different copy of the firmware, I linked 3. You can also flash stock boot_a and boot_b and that should get you going. I'm still figuring this device out. I advise you reach out to somebody who has a lot of experience flashing a/b partition scheme devices, namely mediatek. Project oppo. My only other suggestion is to flash the stock firmware using adb fastboot commands. In the forums you can find a guide to flashing a/b... So, just to be clear, recite to me exactly what you did up to the point it boot loops. And tell me is there system type on the screen when it boots?
Click to expand...
Click to collapse
So i Followed the guide exactly and everything seemed to work fine until i flashed the img modified by magisk. Fastboot said it moved and wrote successfully.
Then when i rebooted and hit the power button again to bypass the 'orange' warning instead of starting into a factory reset phone, it flashes the backlight and starts booting again.
Im also unable to get into recovery, fastboot mode is all that works now. I've tried to flash the stock boot_a img but not the boot_b, do you think that would help?
I'm gonna make a new img with my s9 and try that as you suggested.
Edit:
Well i might be handicapped.
I had 2 phones here, the V+ and the 6 pro.
Turns out i did youre walkthrough on the revvl 6 pro. It did unlock it, but obviously when i flashed the boot.img for the V+ it bricked. And i cant find the backup anywhere.
In short thanks for your time, I'm afraid all i did was waste it :\
vinnie215215 said:
So i Followed the guide exactly and everything seemed to work fine until i flashed the img modified by magisk. Fastboot said it moved and wrote successfully.
Then when i rebooted and hit the power button again to bypass the 'orange' warning instead of starting into a factory reset phone, it flashes the backlight and starts booting again.
Im also unable to get into recovery, fastboot mode is all that works now. I've tried to flash the stock boot_a img but not the boot_b, do you think that would help?
I'm gonna make a new img with my s9 and try that as you suggested.
Edit:
Well i might be handicapped.
I had 2 phones here, the V+ and the 6 pro.
Turns out i did youre walkthrough on the revvl 6 pro. It did unlock it, but obviously when i flashed the boot.img for the V+ it bricked. And i cant find the backup anywhere.
In short thanks for your time, I'm afraid all i did was waste it :\
Click to expand...
Click to collapse
Edited to remove irrelevant content. Guide complete. Try it again. If your phone will not hard reboot, try adb reboot bootloader. All activity should cease and your device should promptly enter fastboot.
i started messing with this phone on my own until ididn't have right stock firm. is alot steps get this phone rooted.
contevo said:
i started messing with this phone on my own until ididn't have right stock firm. is alot steps get this phone rooted.
Click to expand...
Click to collapse
I couldn't agree more. Lol. I'm actively editing the content to condense it. I'm also working on porting TWRP. I've done some other things to save a few steps, like patching boot_a and putting it on Dropbox so all you'll have to do is download it and flash it. When a13 OTA gets captured it'll get better
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i get this error when loading the scatter file ad i'm using the latest version
v5.1924
R41N MuTT said:
I couldn't agree more. Lol. I'm actively editing the content to condense it. I'm also working on porting TWRP. I've done some other things to save a few steps, like patching boot_a and putting it on Dropbox so all you'll have to do is download it and flash it. When a13 OTA gets captured it'll get better
Click to expand...
Click to collapse
can you help
pickymarker said:
can you help
Click to expand...
Click to collapse
Currently working on it. I've asked a couple ppl for help. Either they'll post here, or I'll update you. Stand by
okay
can it be done today
/
comm-ents said:
I am able to unlock the bootloader, then my phone just hangs at the boot screen, but I can can lock it again Now it just boots with the orange warning and it doesn't matter after that if it is locked or unlocked
The android version is still 11 with a security update from Dec 5, 2022.
I am just curious if there is a way to revert back to a previous version that might just work like the version listed for download. There could also be differences in the boot file that is in the firmware zip file from what is on my phone so patching and installing a different version won't work.
Maybe just waiting until the next version is releases would be the best option?
Click to expand...
Click to collapse
Perhaps that. In fact, that's what I'm waiting on- the a13 update. I intend to capture the OTA and follow the spflash walkthrough. Then I can update this how to where it'll work for everybody. I have 4 people right now with boot issues after root that go beyond WiFi, and they all 4 can't get spflash to work. It's bugging the crap out of me, I haven't been able to figure out what to do to fix it. I'm still waiting on some other folks I've reached out to, if they ever have the time...