Related
hi Guys
I'm in the forum for a very long time as an assistant helper now it has got me hard I have an Axon 10 Pro with curly boot loader and trying to flash a TWRP I have somehow the device or SotA and SlotB have shrunk. The Axon Bootet permanently in 0.5 second cycle and also a FULL Restot or FULL Flash with EDL Tool has not changed anything. Likewise, a new flash about fastboot with the command (fastboot flash boot_a boot.img) the same for boot_b then try with fastboot command (fastboot boot twrp.img) Recovery to start without success fastboot erase boot_a and boot_b has also flashing new but it does not start. Always bootloop:crying::crying::crying::crying:
the Axon 10 pro is back because he had no backup of all we had from my Axon 10 pro made a backup with the edl tool (Backup all) and have then copied his efs backup purely and then this with then on the Axon 10 flashed the Axon 10 pro is now back
Where did you get the twrp from?
From udev
On his donload page
https://forum.xda-developers.com/showpost.php?p=80156866&postcount=3
I had a bootloop issue as well and even though I reflashed using the EDL tool, it doesn't erase and the errors remained, but when I entered EDL mode and reflashed using the Xiaomi Flash Tool, storage was completely erased and the device was flashed cleanly and booted correctly.
I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success
jbeaulieu said:
I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success
Click to expand...
Click to collapse
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.
jim262 said:
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.
Click to expand...
Click to collapse
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?
jbeaulieu said:
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?
Click to expand...
Click to collapse
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.
jim262 said:
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.
Click to expand...
Click to collapse
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?
jbeaulieu said:
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?
Click to expand...
Click to collapse
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Ah, okay. I have the US version - A2020U. Unless I'm mistaken, it looks like there isn't a full EDL zip file available for my version yet, so I might be stuck
There were EDL files up, but apparently they were taken down for some reason.
in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431
Chris axon 7 said:
in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431
Click to expand...
Click to collapse
Thanks for sharing these. @Unjustified Dev do you happen to know if the 1.6 2020G EDL would be able to be flashed to a 2020U model to recover from a brick? Or if not, is there a place to obtain the proper files, either here on the forums or via PM?
jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Please share us the EDL file for the Chinese version.
has anyone found the US EDL file yet?
Futility's Forgotten Soldier said:
has anyone found the US EDL file yet?
Click to expand...
Click to collapse
Still waiting. I'm stuck on the EU version.
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
BillyWroth said:
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
Click to expand...
Click to collapse
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
CriGiu said:
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
Click to expand...
Click to collapse
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
BillyWroth said:
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
Click to expand...
Click to collapse
hello, im having maybe a similiar case with my phone (in this case its a MI A3) i installed "succefully" evolution x 6.3 on my phone and everthing was ok with a few bugs, the only problem was that mi cannot connect to internet, so i decided to restart the phone and now my phone just don't turn on, the power button don't respond and i cannot start up my phone and its just a black screen, if u remeber ¿can u pass the tutorial that u saw on reddit? maybe it can help me
Success is disgusted by some people, and will not share any files for free in the future.
johnny886 said:
These materials can only be used for ROG Phone 5S_ZS676KS, and ROG Phone 5_ZS673KS cannot be used. I will release the materials for ROG 5 separately.
If your ROG Phone 5S ZS676KS only has edl mode (port 9008), then this tool can help you repair your phone through edl mode.
Or if you want to modify COUNTRY, flash the firmware of WW, you don't need to apply to unlock the Bootloader,
you don't need ROOT, just follow me.
1.Connect the phone to the computer through the USB port on the left, enter the fastboot mode,
and then open "Reboot-to-edl.bat" to enter the edl mode. Or enter fastboot oem enter-dload in cmd.
2.You must flash in the ENG firmware that I modified. If you find the firmware online,
you may lose your fingerprint and IMEI after flashing.
Method 1: The phone enters edl mode, and when you see port 9008 in the device manager,
open the ENG folder--open "0-update_image_EDL.bat"
Method 2: The phone enters edl mode, and after you see port 9008 in the device manager, use the XiaoMiFlash tool to flash in.
Method 3: The phone enters edl mode, and after you see port 9008 in the device manager,flash in through the QPST tool.
3.After flashing in the firmware and successfully booting up, be sure to back up your phone partition files. If your phone's fingerprint is lost or IMEI is lost,
it can be restored to normal. If you don't have a backup, it will be very troublesome.
Double-click to open "Backup.bat", it will automatically back up your phone partition files, you need to save these files, follow-up will definitely help you.
Include these 10 files：“persist.img factory.img modemst1 modemst2 asuskey4 fsg fsgCA fsc fsgCA2 fsgCA3”
Normally, you don’t need to restore these files. If your fingerprint or imei is lost and you need to restore these files to your phone,
please flash the ENG firmware, then put these 10 files into the ROG 5S folder, and double-click to open " Restore.bat" can be restored to your phone.
4.If your machine is an global version, after backing up and saving 10 files, directly enter the fastboot mode, open the WW folder-open "flash_raw_and_wipe_data.cmd" to flash the WW firmware, and successfully repair your ROG 5S.
If your machine is the CN version, and you want to flash into the WW Firmware, but don’t want to unlock the BootLoader, you can use WinHex to open the persist.img you just backed up,
find COUNTRY, change CN to WW and save it, and you can directly restore it to your phone through the dd command Inside, there is no need to unlock or install magisk.
Double click to open"Open-Cmd.bat",Then enter the commands one by one
adb push persist.img /sdcard/
adb shell
su
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
Then enter the fastboot mode, open the WW folder-open "flash_raw_and_wipe_data.cmd" to flash the WW firmware.
File Downlaod Link：https://drive.google.com/file/d/10kp_87NukXt1XnTJ819I3Y0lH7vIB5T2/view?usp=sharing
YouTube:
I have also studied Hardwaresub Services for a long time, ROG1/ROG2/ROG3 only need to modify COUNTRY, CN to WW, and then flash into the global version,
there will be no such prompt. In addition to modifying COUNTRY, ROG 5 also needs to modify asuskey4.
In this partition, clear the imei, then there is no prompt. But I can’t do anything with ROG 5S.
This machine verifies modemst1 and modemst2. I tried it for a long time, but I couldn’t get rid of the prompt except for the whitelist.
If your ROG3/ROG5/ROG5S is the CN version, but you have flashed the WW firmware, you cannot unlock the Bootloader, or you are prompted to unlock successfully, but the Bootloader is still not unlocked after restarting, you can write the correct SSN and ISN of the phone Go to asuskey4, then restore to the phone partition, and then use the official unlocking tool to unlock it.
Click to expand...
Click to collapse
Sir Please Make For Rog 5 Im Stuck On this
johnny886 said:
If your ROG3/ROG5/ROG5S is the CN version, but you have flashed the WW firmware, you cannot unlock the Bootloader, or you are prompted to unlock successfully, but the Bootloader is still not unlocked after restarting, you can write the correct SSN and ISN of the phone Go to asuskey4, then restore to the phone partition, and then use the official unlocking tool to unlock it.
Click to expand...
Click to collapse
All of us, unfortunate owners of the tencent relocked ROG5, would be grateful if you could elaborate the following bits-
- Writing down SSN & ISN
- Going to asuskey4
- Restoring phone partition
Much appreciate your contribution here pal!
Can you share the WinHex version you're using?
I'm unable to get the same view you are seeing to find "Country".
@johnny886
Thanks!
Hi,
I don't reboot to edl
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
no root,
no unlock bl.
CN rog5s
Thanks
BirtyAs said:
Hi,
I don't reboot to edl
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
no root,
no unlock bl.
CN rog5s
Thanks
Click to expand...
Click to collapse
Wrong fastboot. Reboot to the bootloader, not fastbootd
I am having some issues getting it to work.
I currently have it bricked to the point of only showing up as a Qualcomm HS-USB QDLoader 9008 port .
I keep getting a sahara error after the program tries to run the firehose program.
Can you please help me with this problem.
Thank you.
So I managed to download the program via the 0_update_image_edl.bat file with my phone in EDL mode. However, my phone restarted and it is stuck on the republic of gamers logo.
I wonder why it isn't working. Is there something I am missing or does it take a long while to actually load everything during the first reboot after installation?
Edit:
It was my specific phone acting up and nothing to do with your firmware. I am not sure why I had to keep switching between the bottom and side port to get it to work but I eventually got my phone working using the files you provided. Thank you so much for these files, if not for you, my phone would still be bricked.
It seems like I am always finding something new, even when I have access to my phone now.
My storage is only 64 gb out of the 256 gb it normally has. Any idea how to fix this issue?
Edit, found the fix.
Step 1. I had to ensure that I made a back up of the 10 files stated in the instructions. This is important as not having these files will probably brick a phone.
Step 2. I deleted the extra partitions by setting the "erase all before download" and "reset after download" under "configuration" in the qfil app. Then I did the installation process using qfil.
It did not install correctly, but it was not the point of the process, the point was to delete all hidden partitions.
This deletes the 10 files from the phone as well (I think) and this is why the 10 files are important.
Step 3. I put my phone into edl mode via the reboot to edl .bat file you provided.
Step 4. I used the 0-update_image_edl.bat file to do the first part of the firmware installation process.
It rebooted and showed the page of the phones information. I thought this meant it kept all it's information, but this is a lie.
Step 5. At this point I placed all 10 files in the same folder as the restore.bat file
Step 6. I pressed the restore.bat file and it installed the 10 files.
Step 7. I then proceeded to do the second part of the installation by pressing the "flash_raw_and_wipe_data" file under "ww"
This installed the firmware and rebooted my phone. Now I have all my storage back.
//////////////////////////////
Note:
If the process above doesn't work for someone else. The thing that might have fix my phone could have been changing the setting in the "partition setting" under "configuration" in the "qfil app" that actually deleted the other partitions.
I think I set "customize physical partition" and "active partition number" to 1.
I did this right after saving my 10 files and before using the qfil app to attempt to install the first part of the firmware installation to my phone. This process would replace step 2. on this post.
twistedumbrella said:
Wrong fastboot. Reboot to the bootloader, not fastbootd
Click to expand...
Click to collapse
Thank you very much. I successfully swiped into ww and now I am trying to change COUNTRY. thx
What Winhex version are you using? I can't find the Country in the one im using. just showing the offset with a bunch of numbers.
Donlavon1 said:
What Winhex version are you using? I can't find the Country in the one im using. just showing the offset with a bunch of numbers.
Click to expand...
Click to collapse
Same question I had. Later using the Universal R/W script - I went via Root explorer and changed the text file.
JazonX said:
Same question I had. Later using the Universal R/W script - I went via Root explorer and changed the text file.
Click to expand...
Click to collapse
Need WinHex Professional Edition
No more booting possible, only the android logo flashes briefly, also no restart bootloader or recovery mode possible! what can I do?? thanks
MG4711 said:
No more booting possible, only the android logo flashes briefly, also no restart bootloader or recovery mode possible! what can I do?? thanks
Click to expand...
Click to collapse
I had something similar happen.
Does the computer register it as a device that can be seen or connected? If it DOES NOT CONNECT TO THE PC AT ALL, let it sit on the android logo while it is connected to the computer. In about 15 to 20 minutes it should reboot into a recovery mode like state and the PC will pick it up, something that didn't work when you attempted to use the androids power and volume buttons. It should say a few things and have about 2 options that say
1. delete files
2. reattempt
DO NOT SELECT ANY OF THOSE OPTIONS!!!
Instead, keep the phone plugged in and do not turn off the phone. Place it back into edl mode using adb or the "Reboot-to-edl.bat" file and attempt to reinstall the first portion of the firmware using the "0-update_image_EDL.bat" file.
(Note: You might need to mess with the device manager settings on your PC for the phone. The phone needs to have the ADB Driver to reboot to edl. After your phone gets into EDL mode, you may need to then set your phone to run with the qualcomm driver on your PC's device manager setting to allow you update the image edl. )
then after that fully installs, go to the next step which is the backing up the 10 files. This is the "Backup.bat" file.
This is important. If you fail to do this, you could end up bricking your phone as installing new firmware has a possibility of deleting your phones identity "IEMI" and without this info, your phone will not work. Make sure you keep this file even after you fully installed your software.
After downloading those 10 files. Go to the next step which is. pressing the "flash_raw_and_wipe_data.cmd" file in the WW folder.
(NOTE:
If this doesn't work, it probably means the IEMI information was deleted. Do not pay attention to what is shown on the android screen itself, the battery life and all the info on the screen is incorrect!! It might say something like you have 6000 mah of battery when in actuality you have 5 mah of battery. You will probably have to redo the installation and press the " Restore.bat" file after fully installing using the "0-update_image_EDL.bat" file. If you already have the 10 files, you do not have to resave the 10 files, as you already have them all.
In order to use the restore bat file. All 10 files have to be in the same folder as the "restore.bat" file, prior to pressing the "restore.bat" file.)
Trash.umu said:
I had something similar happen.
Does the computer register it as a device that can be seen or connected? If it DOES NOT CONNECT TO THE PC AT ALL, let it sit on the android logo while it is connected to the computer. In about 15 to 20 minutes it should reboot into a recovery mode like state and the PC will pick it up, something that didn't work when you attempted to use the androids power and volume buttons. It should say a few things and have about 2 options that say
1. delete files
2. reattempt
DO NOT SELECT ANY OF THOSE OPTIONS!!!
Instead, keep the phone plugged in and do not turn off the phone. Place it back into edl mode using adb or the "Reboot-to-edl.bat" file and attempt to reinstall the first portion of the firmware using the "0-update_image_EDL.bat" file.
(Note: You might need to mess with the device manager settings on your PC for the phone. The phone needs to have the ADB Driver to reboot to edl. After your phone gets into EDL mode, you may need to then set your phone to run with the qualcomm driver on your PC's device manager setting to allow you update the image edl. )
then after that fully installs, go to the next step which is the backing up the 10 files. This is the "Backup.bat" file.
This is important. If you fail to do this, you could end up bricking your phone as installing new firmware has a possibility of deleting your phones identity "IEMI" and without this info, your phone will not work. Make sure you keep this file even after you fully installed your software.
After downloading those 10 files. Go to the next step which is. pressing the "flash_raw_and_wipe_data.cmd" file in the WW folder.
(NOTE:
If this doesn't work, it probably means the IEMI information was deleted. Do not pay attention to what is shown on the android screen itself, the battery life and all the info on the screen is incorrect!! It might say something like you have 6000 mah of battery when in actuality you have 5 mah of battery. You will probably have to redo the installation and press the " Restore.bat" file after fully installing using the "0-update_image_EDL.bat" file. If you already have the 10 files, you do not have to resave the 10 files, as you already have them all.
In order to use the restore bat file. All 10 files have to be in the same folder as the "restore.bat" file, prior to pressing the "restore.bat" file.)
Click to expand...
Click to collapse
I have now sent the device back, now I get the rog 5 s and would like to flash it in German? are there any good instructions? Thank you for your help!!
MG4711 said:
I have now sent the device back, now I get the rog 5 s and would like to flash it in German? are there any good instructions? Thank you for your help!!
Click to expand...
Click to collapse
One of the languages for the ROG 5s WW version is Deutsch (Deutschland) or what we normally call german in the US.
There seems to be other forms of Deutsch as well. When initiating the phone, select Duetsch (Deutschland) to run it in the German language or go to settings - accessibility - Language - Duetsch (Duetschland)
Trash.umu said:
One of the languages for the ROG 5s WW version is Deutsch (Deutschland) or what we normally call german in the US.
There seems to be other forms of Deutsch as well. When initiating the phone, select Duetsch (Deutschland) to run it in the German language or go to settings - accessibility - Language - Duetsch (Duetschland)
Click to expand...
Click to collapse
I have to flash a ww version first, the original firmware is china and english
MG4711 said:
I have to flash a ww version first, the original firmware is china and english
Click to expand...
Click to collapse
The original post on this thread talks about the process of installing WW on a china phone. I recommend following the video that Johnny posted in his original post.
johnny886 said:
These materials can only be used for ROG Phone 5S_ZS676KS, and ROG Phone 5_ZS673KS cannot be used. I will release the materials for ROG 5 separately.
ROG Phone 5 ZS673KS Please see here:https://forum.xda-developers.com/t/...ootloader-to-modify-country-cn-to-ww.4353865/
If your ROG Phone 5S ZS676KS only has edl mode (port 9008), then this tool can help you repair your phone through edl mode.
Or if you want to modify COUNTRY, flash the firmware of WW, you don't need to apply to unlock the Bootloader,
you don't need ROOT, just follow me.
1.Connect the phone to the computer through the USB port on the left, enter the fastboot mode,
and then open "Reboot-to-edl.bat" to enter the edl mode. Or enter fastboot oem enter-dload in cmd.
2.You must flash in the ENG firmware that I modified. If you find the firmware online,
you may lose your fingerprint and IMEI after flashing.
Method 1: The phone enters edl mode, and when you see port 9008 in the device manager,
open the ENG folder--open "0-update_image_EDL.bat"
Method 2: The phone enters edl mode, and after you see port 9008 in the device manager, use the XiaoMiFlash tool to flash in.
Method 3: The phone enters edl mode, and after you see port 9008 in the device manager,flash in through the QPST tool.
3.After flashing in the firmware and successfully booting up, be sure to back up your phone partition files. If your phone's fingerprint is lost or IMEI is lost,
it can be restored to normal. If you don't have a backup, it will be very troublesome.
Double-click to open "Backup.bat", it will automatically back up your phone partition files, you need to save these files, follow-up will definitely help you.
Include these 10 files：“persist.img factory.img modemst1 modemst2 asuskey4 fsg fsgCA fsc fsgCA2 fsgCA3”
Normally, you don’t need to restore these files. If your fingerprint or imei is lost and you need to restore these files to your phone,
please flash the ENG firmware, then put these 10 files into the ROG 5S folder, and double-click to open " Restore.bat" can be restored to your phone.
4.If your machine is an global version, after backing up and saving 10 files, directly enter the fastboot mode, open the WW folder-open "flash_raw_and_wipe_data.cmd" to flash the WW firmware, and successfully repair your ROG 5S.
If you cannot flash the firmware in fastboot mode, the prompt: fastboot error CID () Mapping wrong Xrom!
You can Double click to open"Open-Cmd.bat",Then enter the commands, enter fastboot -v flash all xx.raw
xx.raw is the firmware on your computer, for example: fastboot -v flash all C:\Users\johnny\Desktop\ROG5\WW\WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw
ASUS:
version display asus fastboot version and list support project.
-v flash all : disable asus raw id checking.
-g flash all : disable repartition.
-C flash all : disable CRC_<partition>.
If your machine is the CN version, and you want to flash into the WW Firmware, but don’t want to unlock the BootLoader, you can use WinHex to open the persist.img you just backed up,
find COUNTRY, change CN to WW and save it, and you can directly restore it to your phone through the dd command Inside, there is no need to unlock or install magisk.
Double click to open"Open-Cmd.bat",Then enter the commands one by one
adb push persist.img /sdcard/
adb shell
su
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
Then enter the fastboot mode, open the WW folder-open "flash_raw_and_wipe_data.cmd" to flash the WW firmware.
File Downlaod Link：https://drive.google.com/file/d/10kp_87NukXt1XnTJ819I3Y0lH7vIB5T2/view?usp=sharing
YouTube:
I have also studied Hardwaresub Services for a long time, ROG1/ROG2/ROG3 only need to modify COUNTRY, CN to WW, and then flash into the global version,
there will be no such prompt. In addition to modifying COUNTRY, ROG 5 also needs to modify asuskey4.
In this partition, clear the imei, then there is no prompt. But I can’t do anything with ROG 5S.
This machine verifies modemst1 and modemst2. I tried it for a long time, but I couldn’t get rid of the prompt except for the whitelist.
If your ROG3/ROG5/ROG5S is the CN version, but you have flashed the WW firmware, you cannot unlock the Bootloader, or you are prompted to unlock successfully, but the Bootloader is still not unlocked after restarting, you can write the correct SSN and ISN of the phone Go to asuskey4, then restore to the phone partition, and then use the official unlocking tool to unlock it.
Click to expand...
Click to collapse
If i do this am i able to update my firmware from Asus or am i stuck with the modified one?
So I purchased a tmobile op8 and it arrived yesterday, after setting up the phone and network unlocking (which happened basically instantaneously after applying for it which i found odd), I am currently trying to unlock bootloader in the hopes of converting it to the international firmware. I am on software version 11.0.5.7.IN55CB
The problem I am facing is that whenever i try to do "adb devices" while the phone is powered on it works and lists it, but when the phone is in fastboot mode it does not list the device. Also when i do "fastboot oem get_unloock_code" it gets stuck at waiting for devices. I have read through numerous posts both here and on the op forums talking about this and some listed solutions such as going into windows optional updates and updating google bootloader or something, while others said to check that bootloader is unlocked (i did both and didnt work). Any tips? Also, could someone please link to the correct adb and driver downloads as I am getting mixed results when searching which is the correct download.
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Thanks, worked like a charm. Now to wait 7 business days fml
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
PrivyetCyka said:
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
Click to expand...
Click to collapse
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
i have t-m version and i have converted it to international software firmware also gets changed but by your self you won't be able to get 2 sim support because there is only one imei in phone. all the rom's work exacly the same as they do on global version not a single difference currently running a12 aex rom no problems at all
DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
d.tat said:
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
Click to expand...
Click to collapse
Can this be done without TWRP or does this have to be done after I root?
DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
no root needed to install or boot into twrp
d.tat said:
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
Click to expand...
Click to collapse
Ok, thanks for clarification
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
DamianF7 said:
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
Click to expand...
Click to collapse
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged in and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery.
2. Flash recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery NAMEOFFILE.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Use this command "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks for the reply man. Believe it or not this is exactly what I did lol. Got it working again and am now rooted on international oos 11.
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
SilverZero said:
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
Click to expand...
Click to collapse
Glad you got it man, worth all the trouble to get to a clean version of OOS without T-MO's junk and spying xD
FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged on and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
nmuntz said:
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
Click to expand...
Click to collapse
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
FoxyDrew said:
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
Click to expand...
Click to collapse
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
nmuntz said:
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
Click to expand...
Click to collapse
I've never seen that MSM tool, but the one I use doesn't have any Sprint files at all. Not sure where you found that MSM but use this one for future reference.
No you don't need to flash global before a ROM.
Hello community,
I kind of ruined my phone into this CrashDump Mode state. Which prevents me from using my phone at all. I'm pretty sure it is 'bricked.
I hope someone could give me some guidance to fix my phone again.
What do I want:
I wish to have the original OxygenOS back on my phone (stock).
What caused the problem:
My goal was to root my phone by unlocking the bootloader, installing Magisk and flashing the ROM from Magisk. Unfortunately, after doing all of this successfully there were some issues. One of them being slow restarts. It could take up to 20 minutes for the phone to start. Other than that it made the phone quite unusable as the media sound didn't work neither did the wifi and microphone. Making me unable to listen to anything but also couldn't make calls. For that reason I decided to unroot the phone again. I used the in-app Magisk full uninstall button to do so. After doing this, the phone didn't boot anymore. It was stuck at the boot loader unlock warning screen. So I figured I had to flash my latest version of OxygenOS on the phone. I grabbed a guide to do this manually on the XDA forums. However, this was a guide for Android 10 I believe. So it didn't seem to flash all the image files I saw listed after doing the payload extractor. This resulted in my phone booting up to the CrashDump Mode. As there were no guides for the version 11.0.5.1, I decided to use a tool listed here on the forums: https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/ However, this is only for version 10 instead of 11. This also didn't seem to work.
Steps done:
Unlocked bootloader:
- Basically by just using: "fastboot oem unlock"
This went successfully.
Rooted the phone:
- Installed Magisk and my boot.img on my phone.
- Created an .img with Magisk.
- Ported the created .img to my pc.
- rooted the phone with fastboot by flashing the .img on my phone for boot_a and boot_b
This went successfully, the phone was rooted.
Unrooting and stock recovery:
- Used the uninstall button within the Magisk app on the phone.
- Tried to manually flash the OxygenOS version 11.0.5.1 on my phone. Note: only a few images were then as they were the only ones listed in a guide.
- Tried the tool listed above.
This all failed.
Phone details:
OnePlus 7 Pro - European - Last version used: 11.0.5.1
Index of /list/Unbrick_Tools/OnePlus_7_Pro/EU_GM21BA/R
Juuuul said:
Hello community,
I kind of ruined my phone into this CrashDump Mode state. Which prevents me from using my phone at all. I'm pretty sure it is 'bricked.
I hope someone could give me some guidance to fix my phone again.
What do I want:
I wish to have the original OxygenOS back on my phone (stock).
What caused the problem:
My goal was to root my phone by unlocking the bootloader, installing Magisk and flashing the ROM from Magisk. Unfortunately, after doing all of this successfully there were some issues. One of them being slow restarts. It could take up to 20 minutes for the phone to start. Other than that it made the phone quite unusable as the media sound didn't work neither did the wifi and microphone. Making me unable to listen to anything but also couldn't make calls. For that reason I decided to unroot the phone again. I used the in-app Magisk full uninstall button to do so. After doing this, the phone didn't boot anymore. It was stuck at the boot loader unlock warning screen. So I figured I had to flash my latest version of OxygenOS on the phone. I grabbed a guide to do this manually on the XDA forums. However, this was a guide for Android 10 I believe. So it didn't seem to flash all the image files I saw listed after doing the payload extractor. This resulted in my phone booting up to the CrashDump Mode. As there were no guides for the version 11.0.5.1, I decided to use a tool listed here on the forums: https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/ However, this is only for version 10 instead of 11. This also didn't seem to work.
Steps done:
Unlocked bootloader:
- Basically by just using: "fastboot oem unlock"
This went successfully.
Rooted the phone:
- Installed Magisk and my boot.img on my phone.
- Created an .img with Magisk.
- Ported the created .img to my pc.
- rooted the phone with fastboot by flashing the .img on my phone for boot_a and boot_b
This went successfully, the phone was rooted.
Unrooting and stock recovery:
- Used the uninstall button within the Magisk app on the phone.
- Tried to manually flash the OxygenOS version 11.0.5.1 on my phone. Note: only a few images were then as they were the only ones listed in a guide.
- Tried the tool listed above.
This all failed.
Phone details:
OnePlus 7 Pro - European - Last version used: 11.0.5.1
Index of /list/Unbrick_Tools/OnePlus_7_Pro/EU_GM21BA/R
Click to expand...
Click to collapse
This is how I go back to stock
You can use MSM tool to revert OOS, or you can try this step:
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage or otg drive. Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots
In your case skip to number 2 and after booting to TWRP then format data then install twrp
hammered58 said:
This is how I go back to stock
You can use MSM tool to revert OOS, or you can try this step:
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage or otg drive. Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots
In your case skip to number 2 and after booting to TWRP then format data then install twrp
Click to expand...
Click to collapse
Hey,
Thanks for your reply! I currently don’t have twrp on my phone but I could look at it. Do you have a link for MSM tool as download and possibly a guide?
Juuuul said:
Hey,
Thanks for your reply! I currently don’t have twrp on my phone but I could look at it. Do you have a link for MSM tool as download and possibly a guide?
Click to expand...
Click to collapse
You actually boot into TWRP it does not have to be installed,, you install it once you boot into it plus you would probably need a otg because you do not have a OS . Here's a link to the Msm tools
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7_Pro/Global_GM21AA/
There are several great write ups on how to use and install msm tool right here in the op7p forum I will see what I can find and post later
[OP7PRO][LATEST OOS 11.0.5.1 GM21AA/GM21BA] Collection of unbrick tools
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com