Related
Hi all.
If you are here, then you have likely experienced issues with custom ROMs not detecting SIM, or you are still experiencing this issue.
I have a XT1562 UK Single-SIM model and have had this problem with EVERY ROM I have tried and it was getting so frustrating.
Over the last few weeks, I have flashed custom ROMs based on CM13 and all have presented the SIM not detected issue. A simple fix was to pop-out the SIM module and reinsert - more often than never, the SIM was detected. Then I would restart (as is often the case with a custom setup) and alas, the SIM was not detectable.
After trying various suggestions from developers, nothing was working until I happened to flash a dualSIM firmware and I haven't looked back. I can now flash EVERY CM13-based ROM with successful SIM detection BUT it takes a few extra steps to get to that stage.
Here are the things you need:
This firmware
This fix
A custom ROM of your choice (Highly recommend crDroid or Temasek)
GAPPS of your choice - I would recommend this
TWRP
Okay - the solution (confirmed working and reliable):
1. Unpack the Firmware into it's own folder
2. Copy across the files to Fastboot folder
3. Restart phone into bootloader (power off first then hold power and volume down)
4. In the Fastboot folder hold shift and right click.
5. Select "open command window here"
6. Connect phone via USB to computer and in command window enter the following commands 1 by 1 making sure "[okay]" is displayed each time:
if nothing happens on screen, then simply use your volume keys on the phone to restart the bootloader
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
7. Once completed restart phone and setup as normal.
8. When setup is complete, restart phone into bootloader.
9. Flash TWRP
10. Restart phone into recovery
11. in TWRP, factory reset then flash ROM and GAPPS and DualSIMFix
12. Restart phone and setup. If SIM shows not detected, press "skip" and it should detect after WiFi setup.
Voila! You can now confidently flash ANY CM13-based custom ROM with the added assurance of SIM detection. IF, however, you flash a ROM and SIM is NOT detected, then simply reflash the DualSIMFix.
If this solution works for you, please give credit where it's due - thank me using the thumbs-up icon below AND vote in the poll at the head of this thread
So, you want to say, that i need to flash stock DS ROM
and after that i'll can flash any custom CM13 based ROM and SIM will be detected?
perfectsense72 said:
So, you want to say, that i need to flash stock DS ROM
and after that i'll can flash any custom CM13 based ROM and SIM will be detected?
Click to expand...
Click to collapse
It has worked for me and I have tried everything that has been recommended. Just by determined trial-and-error I have found my solution.
Just to reiterate
and my intention is to generate enough interest to further assist developers of the CM13 custom ROMs.
Click to expand...
Click to collapse
Can you write a sequence of actions? What nuances?
perfectsense72 said:
Can you write a sequence of actions? What nuances?
Click to expand...
Click to collapse
I fastboot flashed XT1562_LUX_RETASIA_DS_6.0_MPD24.65-18.1 (here ); flashed ROM; flashed GAPPS and then flashed DualSIMFix (from here)
I've tested reboots and SIM is detected each time.
I am assuming you know how to flash a stock image - if not let me know.
I am assuming you know how to flash a stock image - if not let me know
Click to expand...
Click to collapse
From PC by fastboot in stock recovery mode, right?
Did you perform any wipe between flashing stocj ROM and flashing CM13 based ROM?
perfectsense72 said:
From PC by fastboot in stock recovery mode, right?
Did you perform any wipe between flashing stocj ROM and flashing CM13 based ROM?
Click to expand...
Click to collapse
Follow this:
1. Unpack the Firmware into it's own folder
2. Copy across the files to Fastboot folder
3. Restart phone into bootloader (power off first then hold power and volume down)
4. In the Fastboot folder hold shift and right click.
5. Select "open command window here"
6. Connect phone via USB to computer and in command window enter the following commands 1 by 1 making sure "[okay]" is displayed each time:
if nothing happens on screen, then simply use your volume keys on the phone to restart the bootloader
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
7. Once completed restart phone and setup as normal.
8. When setup is complete, restart phone into bootloader.
9. Flash TWRP
10. Restart phone into recovery
11. in TWRP, factory reset then flash ROM and GAPPS and DualSIMFix
12. Restart phone and setup. If SIM shows not detected, press "skip" and it should detect after WiFi setup.
13. Enjoy - but please let me know if not quite right.
@perfectsense72 - once you are able to confirm fully working, then I'll amend the OP to reflect necessary details for successful detection, etc. Thanks for trying this.
Thank you, i'll try tomorrow.
I can't confirm your problems with single sim modem.
I have german single sim and had problems after flashing french dual sim stock image and then flash cm13 roms.
Sometimes the boot was fine with detected sim and sometimes without detected sim and with random reboots of the device.
After flashing back a single sim stock and completly boot the stock then flash again crdroid no problems appeared again. All fine with detected sim on every boot.
For now I'm using Pac-ROM (LP) and have no problem, I'll try CrDroid soon and I'll let you know.
Jeso said:
Sometimes the boot was fine with detected sim and sometimes without detected sim and with random reboots of the device.
Click to expand...
Click to collapse
This is what I'm aiming to avoid for those with issues such as this. Every firmware flash produced an error on flashing bootloader. The only one to not present me with the error is the 18.1 DS retasia.
This has, I believe, been the key to my issues as well as other users. I can flash any official firmware and use it perfectly well, it's just the custom MM ROMs that are problematic.
moozer said:
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Does it lock the bootloader?
(Sorry for noob question)
axxx007xxxz said:
Does it lock the bootloader?
(Sorry for noob question)
Click to expand...
Click to collapse
No - this just re-introduces the stock bootloader for the firmware
So, it's working. Flash Unoficial CM13 after stock DS asian and no problem, both simcards a detected.
Thanks, moozer.
perfectsense72 said:
So, it's working. Flash Unoficial CM13 after stock DS asian and no problem, both simcards a detected.
Thanks, moozer.
Click to expand...
Click to collapse
You're welcome. Checked rebooting the phone? SIM remains?
You can now flash custom ROMs to your heart's content. No need to fart around with firmware flashes. All that you need to check is SIM detection on setup and if necessary flash the SIMfix.
^^
Yes, SIM remains after reboot, everything is OK
Thanks a lot! Worked perfectly for me aswell. Currently running ResurrectionRemix and I've had no problems with the sim card since.
help my phone's dead stuck at Qualcomm crash dump mode:crying:
dogman.jp said:
help my phone's dead stuck at Qualcomm crash dump mode:crying:
Click to expand...
Click to collapse
What were you trying to do before this happened. What rom are you using.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I had the same issue but I could actually boot into GSIs. Although it would reboot into the crash dump screen after the phone went to sleep.
Flashing stock 5.1.11 did temporarily fix it but as soon as I installed any custom rom, the issue would return.
Thankfully there's a solution:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Long story short, some file got corrupted or something and nothing besides an EDL flash can fix it. You need to enter EDL ( power off the phone, hold volume up for 10 seconds and connect it to the pc while still holding vol up ) and if your PC recognizes the phone as qcom 9008 or something like that, open up the program and let it flash all the stuff onto the phone.
After it's done, the issue should be solved.
I had this issue while I was trying to port roms. What I did was go to fastboot, boot twrp, flash OOS OTA.
Edit: Now I'm dead stuck at crash dump mode. I cant boot TWRP over fastboot it goes back to crash dump mode and I dont have windows machine so I cant use MSM tool I will try fastboot OOS installer now.
Edit2: I managed to boot the phone now. I have followed the following way:
1. I have dumped the Beta 3's payload.bin with: python payload_dumper.py payload.bin
2. I have flashed the following partitions through fastboot:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash fw_4j1ed_a fw_4j1ed.img
fastboot flash fw_4j1ed_b fw_4j1ed.img
fastboot flash fw_4u1ea_a fw_4u1ea.img
fastboot flash fw_4u1ea_b fw_4u1ea.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
And it works after that. If you can't dump the files, I can upload them for you.
The bad thing is, you can't install custom rom, custom kernel, install twrp or do anything that makes Oneplus Oneplus... This needs to be fixed as soon as possible.
ereneren564 said:
I had this issue while I was trying to port roms. What I did was go to fastboot, boot twrp, flash OOS OTA.
Edit: Now I'm dead stuck at crash dump mode. I cant boot TWRP over fastboot it goes back to crash dump mode and I dont have windows machine so I cant use MSM tool I will try fastboot OOS installer now.
Edit2: I managed to boot the phone now. I have followed the following way:
1. I have dumped the Beta 3's payload.bin with: python payload_dumper.py payload.bin
2. I have flashed the following partitions through fastboot:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash fw_4j1ed_a fw_4j1ed.img
fastboot flash fw_4j1ed_b fw_4j1ed.img
fastboot flash fw_4u1ea_a fw_4u1ea.img
fastboot flash fw_4u1ea_b fw_4u1ea.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
And it works after that. If you can't dump the files, I can upload them for you.
The bad thing is, you can't install custom rom, custom kernel, install twrp or do anything that makes Oneplus Oneplus... This needs to be fixed as soon as possible.
Click to expand...
Click to collapse
all you had to do was flash boot and done!
are you trying to boot recovery img ? I got that problem too. but it fixed by using this command "flastboot flash boot twrpname.img" . then press volume up button till u got the recovery options and press power. after u booted up into the twrp , flash the twrp zip. reboot to recovery again just to make sure that the twrp already installed. then flash magisk. reboot. done! sorry 4 bad english
dogman.jp said:
help my phone's dead stuck at Qualcomm crash dump mode:crying:
Click to expand...
Click to collapse
I had that issue last night - I flashed OB3 - and flashed a kernel that worked on OB1/OB2.
I used the MSM download tool but doing that you lose everything. I tried the fastboot flashing method of OOS but had no success.
Did you get it flashing OB3? Then TWRP or a kernel?
https://forum.xda-developers.com/showpost.php?p=77628189&postcount=438
You could also try changing active slots
fastboot --set-active=x
"x" being a or b for the respective slot
Ther's a problem with recovery and some other stuff. You can solve the problem with a patched boot with recovery. You can find it in the blu stark trade!
go here https://forum.xda-developers.com/one...-beta-t3818853
download Beta 3 Patched Boot from here https://drive.google.com/open?id=1TD...NoBAReZVZlir0U
reboot to fastboot and type
fastboot flash boot beta3_patched_boot.img
reboot normally and rooted
when open goto magisk and flash from the app the 17.1.zip
Easiest way is flashing recovery from fastboot mode with command fastboot flash boot recovery.img. After that reboot recovery, wipe, install rom & recovery reboot system :good:
_MartyMan_ said:
Easiest way is flashing recovery from fastboot mode with command fastboot flash boot recovery.img. After that reboot recovery, wipe, install rom & recovery reboot system :good:
Click to expand...
Click to collapse
did you try it? because the latest beta doesnt boot and goes to soft brick menu
check here https://forum.xda-developers.com/showpost.php?p=77628189&postcount=438
you need to flash latest OB3 blu_twrp 9.85 patched boot
Hi, your links are truncated.
Could you correct them ?
Thank you.
didicola said:
did you try it? because the latest beta doesnt boot and goes to soft brick menu
check here https://forum.xda-developers.com/showpost.php?p=77628189&postcount=438
you need to flash latest OB3 blu_twrp 9.85 patched boot
Click to expand...
Click to collapse
okay I did
fastboot flash boot boot_op6_ob3_twrp.img
Now afterwards I can't even go into the fastboot, and rarely I can get into TWRP. I can't even boot normally. Sorry I am a noob, what should I do? When I try to start the phone it gets stuck on "the boot loader is unlocked"-screen.
Since I can't use fastboot or boot normally, can I flash stock through twrp? and if yes can you link me to the correct file?
EDIT: ok I used this https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and I lost all my data, but whatever, im just glad my phone still works
Before you try to use the Qualcomm way,
You can try to boot into the fastboot (power + volume plus without plugging in the USB cable) and flash the unofficial twrp which is from blu_spark.
https://forum.xda-developers.com/devdb/project/?id=27466#downloads
I met this problem when I tried to install official twrp after I installed the OxygenOS9 BATE3.
I think this problem is because of some conflicts between the twrp and the OS (I guess)
My friend told me that I should try to flash another recovery.
And I tried to flash the unofficial from blu_spark and it finally works.
Thanks, Blu_Spark.
Even if it still isn't work, you can try to flash the official recovery from the OnePlus.
I will be happy if it works for you.
MrSteelX said:
all you had to do was flash boot and done!
Click to expand...
Click to collapse
I am facing the same issue with OB4
I also tried the fasrtboot flashing method.
But on that thread, one of the steps is to Fastboot boot twrp
and later adb commands to be executed in twrp mode.
But I CANNOT go into recovery on OB4
please hlep
HannibalLecter said:
I am facing the same issue with OB4
I also tried the fasrtboot flashing method.
But on that thread, one of the steps is to Fastboot boot twrp
and later adb commands to be executed in twrp mode.
But I CANNOT go into recovery on OB4
please hlep
Click to expand...
Click to collapse
I had the same issue last night with the 9.0 stable. U downloaded the modified TWRP from BluSpark, that booted just fine and flashed the installer. All is well now
Azhar_Fahry said:
are you trying to boot recovery img ? I got that problem too. but it fixed by using this command "flastboot flash boot twrpname.img" . then press volume up button till u got the recovery options and press power. after u booted up into the twrp , flash the twrp zip. reboot to recovery again just to make sure that the twrp already installed. then flash magisk. reboot. done! sorry 4 bad english
Click to expand...
Click to collapse
hummmmm......flash twrp to boot?It's make me device to loop CrashDump Mode X-X
493Arceus said:
hummmmm......flash twrp to boot?It's make me device to loop CrashDump Mode X-X
Click to expand...
Click to collapse
Is there any solution for this? I had to revive my OP6 with the fastboot stock rom and now I am unable to fastboot into TWRP. Also end up in crash dump mode.
Edit: OK flashing Blu Spark TWRP image fixed the problem.
shiverz07 said:
Is there any solution for this? I had to revive my OP6 with the fastboot stock rom and now I am unable to fastboot into TWRP. Also end up in crash dump mode.
Edit: OK flashing Blu Spark TWRP image fixed the problem.
Click to expand...
Click to collapse
Flashed this Blu Spark TWRP modded but stuch on Blu Spark logo
When I'm trying to boot normaly after (long press on power menu to shutdown), stuck on the first screen "The boot loader is unlocked and software ..."
desperate..........:crying:
Story: I bought US version Z3 Play open market model from B&H. I could unlock the bootloader according to Motorola Developer site, but I encountered problem to root and I have struggled half day to make root done from booting TWRP to patching boot.img.
Eventually, I bit the bullet and make a step up to update to Pie bu downloading RETAIL ROM instead of RETUS. This time I patched the updated boot.img and I got success.
Prerequisite:
Full RETAIL Pie ROM
https://mirrors.lolinet.com/firmware/moto/beckham/official/RETAIL/
Bootloader unlocked
It's recommended to flash in Linux (I used Ubuntu) as I didn't have luck with Windows
Main battery should be full and supplied battery module should be at least 50% (you can charge battery module with 9V PD charger)
Some typing (all fastboot commands typed as ./fastboot)
Be aware some components will be flashed in b partition. Failure to do it will cause bootloop
./fastboot erase userdata is optional, but it is recommended to avoid unexpected trouble
Steps:
1. Download the Pie ROM and extract to somewhere you know (you can drag and drop the file into terminal window).
2. Copy the boot.img to the phone and let Magisk Manager to patch it, and copy the patched_boot.img to where you can locate.
3. Backup your personal data just in case
4. Prepare USB C cable
5. Enter bootloader. Turn the phone off, press and hold both volume down and power button together, and connect you phone to host computer. (You phone should show USB conmected)
6. Enter the following commands
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Click to expand...
Click to collapse
7. After the phone has booted up, wait until it completed the update process. Now you have to go back to bootloader for rooting.
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
Booting process takes much longer, but it's one process until you update ROM and regain root again.
8. Run Magisk Manager to check root status
This is what I did to manually update to Pie and root it. Your milage may vary.
Good luck
Will this work on the amazon version?
CrimsonSaber5G said:
Will this work on the amazon version?
Click to expand...
Click to collapse
If the bootloader can be unlocked, it's likely
Will this still allow you to get OTAs or will it break it?
crazyjimbo said:
Will this still allow you to get OTAs or will it break it?
Click to expand...
Click to collapse
I used to flash stock on my rooted z3play, then take the OTA . For some reason that's not possible anymore. I really need the latest OTA to sideload it. I tried many different roms 8.1 and 9.0
Hi guys. If you can't install ROMs, this is your place to ask. Please be detailed, mention: ROM, build, your variant and firmware version. And tell us your specific issue.
Here's a guide on how to do it, and I'll link you to the files needed for the procedure:
1. If you're using a Google account, remove it in Settings > Accounts and factory reset. Else, skip this step.
2. Unlock your bootloader following Motorola's instructions. Google it, it'll be easy to find and follow.
3. Download:
. Fastboot tools/Minimal ADB & Fastboot or your prefered fastboot program for PC.
. A firmware image for your variant
. ROM you want to install
. GApps (optional): http://opengapps.org/
. Magisk (optional): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And the next files:
TWRP (img) & TWRP installer (zip): https://androidfilehost.com/?w=files&flid=299042
copypartitions.zip: https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
You'll need an SD card to store the files needed for installing the ROM, since internal storage won't be usable temporarily.
4. Hold power + volume down until you reach bootloader (fastboot mode).
In your extracted firmware folder open a terminal and flash your firmware files with these commands:
----------------------------------------------------------------------
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot set_active a
fastboot reboot-bootloader
sleep 5
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 5
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.2
fastboot flash vendor_b vendor.img_sparsechunk.0
fastboot flash vendor_b vendor.img_sparsechunk.1
fastboot flash vendor_b vendor.img_sparsechunk.2
fastboot flash oem_a oem.img
fastboot flash oem_b oem.img
fastboot oem fb_mode_clear
fastboot reboot-bootloader
--------------------------------------------------------------------
Don't worry if any error message appears.
5. Place TWRP .img file into your fastboot folder, and do "fastboot boot TWRP.img" - replace TWRP with file's real name, but it should be the IMG file's name, not the zip file's name. With TWRP booted, now check if the screen actually responds. If it doesn't, just turn your phone off, get into fastboot mode again, and boot TWRP until it works.
6. With that solved, now just copy copypartitions.zip to your sdcard (called external_sd in your phone) and install it. Also copy to your external_sd, just to save time, your ROM and TWRP's installer. And Magisk or GApps if you'll need them.
7. Reboot to bootloader, and do "fastboot -w".
8. "fastboot boot" TWRP again, flash ROM, and flash TWRP's installer (zip file). Boot system.
9. Reboot to bootloader, select recovery mode and flash Magisk/GApps if you need them.
10. Reboot to system, and enjoy
Any questions, feel free to ask 'em in the comments. Hope it works!
P.S.: OmniROM has its own recovery (TWRP is a recovery). So, keep that in mind and don't flash TWRP's zip in Omni if you want it to boot.
Also, if you want, you can try OrangeFOX. It's a cute TWRP replacement that has some interesting features. Worth checking out.
TL;DR:
1. Remove your Google account
2. Flash firmware with the set of commands attached.
3. "Fastboot boot" TWRP and flash copypartitions.zip.
4. Go to bootloader mode and do "fastboot -w".
5. Boot TWRP, flash ROM and TWRP's installer
5.1. Boot system
(optional) 6. Open recovery mode and flash Magisk/GApps.
-----------------------------------------------------------------------------------
Download:
. Fastboot tools/Minimal ADB & Fastboot or your prefered fastboot program for PC.
. A firmware image for your variant
. ROM you want to install
. GApps (optional): http://opengapps.org/
. Magisk (optional): https://forum.xda-developers.com/app...mless-t3473445
. TWRP (img) & TWRP installer (zip): https://androidfilehost.com/?w=files&flid=299042
. copypartitions.zip: https://drive.google.com/file/d/1oir...t2eSGKt0F/view
You'll need an SD card to store the files needed for installing the ROM, since internal storage won't be usable temporarily.
All ROMs posted in XDA are actually working in this device.
Thank you for creating this thread. People need to get used to this A/B partition format. This is the proper forum to discuss these issues, not in the development section.
Using these instructions:
crDroid -> bootloop
bootleggers rom -> bootloop
lineageos -> bootloop
ressurection remix -> bootloop
Twrp is screaming at me "Failed to mount /data partition "invalid argument"
I noticed your instructions fail to mention you need to run through the setup process of android, then run fastboot -w, then run twrp format data as fastboot -w will (using retus and amz stock rom) create a "raw" partition table and so on. None of the current roms can handle this and will bootloop.
These incomplete instructions will waste people's time and cause problems.
Please reconsider the purpose of this thread. It is the developers responsibility to add a filesystem check during rom flash and write working instructions. Currently only bootleggers instructions will work to any capacity due to their inbuilt sanity checks.
derek12213 said:
Using these instructions:
crDroid -> bootloop
bootleggers rom -> bootloop
lineageos -> bootloop
ressurection remix -> bootloop
[...]
Click to expand...
Click to collapse
Hey. like I said at the beggining of the thread, it's not possible to help you without giving specifics. Give that info and I'll help you.
I made this thread because this steps worked to dozens of users, and I'm not joking. Literally. They are not incomplete since they worked for everyone. Search for our group in Telegram if you think it's not true. We might be able to help you there too.
TWRP screams "Failed to mount /data partition", that's why internal storage won't work temporarily until you flash a ROM. Could that be better? Of course. But still the procedure works.
"I noticed your instructions fail to mention you need to run through the setup process of..." Nope. There's no need for that. That's why I didn't mentioned it, because I've tried lots of ROMs and never needed to do that.
Also, do you have latest fastboot? Some users had issues because of using older versions of that program.
But yeah, I'm not some friend who can go to your house and see what you've got. So, we need information. I won't be able to help you further if you don't do your part. Tell me what you've got please.
Flash to stock -> fine
follow your instructions for any rom -> bootloop
from stock flashed metropcs rom per crDroid developers recomendation (I am amz fw)
flash all that commands using metropcs firmware (crDroid said to use this one, I am AMZ fw, tried AMZ fw and RETUS fw and it doesnt matter, same result)
fastboot boot twrp
twrp flash copy partitions
reboot bootloader
fastboot -w
boot twrp
flash rom flash twrp
reboot system
bootloop
output of twrp and fastboot during the process :
Erasing 'userdata' OKAY [ 0.117s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
install rom zip and twrp zip (downloaded your versions)
could not mount /data and unnable to find crypto footer
failed to mount /data invalid argument
unable to recreate /data/media folder
updating partition details...
failed to mount /data invalid argument
...done
unable to mount storage
failed to mount /data invalid arugment
Full selinux support is present
unable to mount /data/media/TWRP/.twrp
after flashing twrp says
Failed to mount /data invalid argument
...done
Your guide says " Boot system."
I am interpreting this as reboot system
Bootloop
All roms.
I dont install gapps because I dont need spyware. I would use stock if I wanted to be spyed on 24/7.365
I dont install magisk outside of booting a magisk patched boot img to modify hosts for less CONSTANT TRACKING
Hey, did you read my last reply, as well as the first line of this thread? Where I require specifically to give me some info first to be able to help you. I'm like trying to help a question mark... try to follow a simple rule.
In step 9, you're doing "fastboot boot" to TWRP, or you're actually going to recovery mode? We need to know if TWRP install actually works. Even if you won't use any Magisk or GApps, check if it is actually installed AND working.
I've also heard of users that had issues booting of the first time a ROM with TWRP installed. Maybe just do the procedure until you have to flash a ROM, and boot the system instead of installing TWRP. And flash TWRP after the ROM already booted and it's running.
Also, how much time should pass for you to consider for a ROM to be bootlooping?
Well, both fastboot -w and TWRP mount /data errors are the same thing. Fastboot isn't able to format it properly, so data is not mounted by TWRP. Like I said before, it's a temporal thing that's fixed when flashing the ROM. Don't worry about that.
But please, I don't know if you do this on purpose, you're not following even a simple request stated at the beggining of the thread. Please answer that to keep the conversation going, I won't reply you any further if you don't do your part.
derek12213 said:
Flash to stock -> fine
follow your instructions for any rom -> bootloop
from stock flashed metropcs rom per crDroid developers recomendation (I am amz fw)
flash all that commands using metropcs firmware (crDroid said to use this one, I am AMZ fw, tried AMZ fw and RETUS fw and it doesnt matter, same result)
fastboot boot twrp
twrp flash copy partitions
reboot bootloader
fastboot -w
boot twrp
flash rom flash twrp
reboot system
bootloop
output of twrp and fastboot during the process :
Erasing 'userdata' OKAY [ 0.117s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
install rom zip and twrp zip (downloaded your versions)
could not mount /data and unnable to find crypto footer
failed to mount /data invalid argument
unable to recreate /data/media folder
updating partition details...
failed to mount /data invalid argument
...done
unable to mount storage
failed to mount /data invalid arugment
Full selinux support is present
unable to mount /data/media/TWRP/.twrp
after flashing twrp says
Failed to mount /data invalid argument
...done
Your guide says " Boot system."
I am interpreting this as reboot system
Bootloop
All roms.
I dont install gapps because I dont need spyware. I would use stock if I wanted to be spyed on 24/7.365
I dont install magisk outside of booting a magisk patched boot img to modify hosts for less CONSTANT TRACKING
Click to expand...
Click to collapse
Dude, I had the same issue as you, couldn't load any roms, no matter what guide I followed, it always bootlooped. Turned out to be my microSD was causing it. I followed Life_goes_on's solution on this thread (post #74):
https://forum.xda-developers.com/g7-power/development/rom-resurrection-remix-t3994687/page8
Substituted 'fastboot erase userdata' for 'fastboot -w' and took out my microSD before booting it up and it worked.
I'm using the MetroPCS version on RETUS firmware.
BETA215 said:
Hey, did you read my last reply, as well as the first line of this thread? Where I require specifically to give me some info first to be able to help you. I'm like trying to help a question mark... try to follow a simple rule.
In step 9, you're doing "fastboot boot" to TWRP, or you're actually going to recovery mode? We need to know if TWRP install actually works. Even if you won't use any Magisk or GApps, check if it is actually installed AND working.
I've also heard of users that had issues booting of the first time a ROM with TWRP installed. Maybe just do the procedure until you have to flash a ROM, and boot the system instead of installing TWRP. And flash TWRP after the ROM already booted and it's running.
Also, how much time should pass for you to consider for a ROM to be bootlooping?
Well, both fastboot -w and TWRP mount /data errors are the same thing. Fastboot isn't able to format it properly, so data is not mounted by TWRP. Like I said before, it's a temporal thing that's fixed when flashing the ROM. Don't worry about that.
But please, I don't know if you do this on purpose, you're not following even a simple request stated at the beggining of the thread. Please answer that to keep the conversation going, I won't reply you any further if you don't do your part.
Click to expand...
Click to collapse
After i flash rom and twrp I can go to twrp by holding volume down and pwr then selecting recovery at that point or can boot it via fastboot. I think that it changes parition (from a to b) during this process so I always use twrp to reboot to recovery even if I am not flashing gapps or magisk to rule out problems.
---------- Post added at 12:38 AM ---------- Previous post was at 12:11 AM ----------
framila said:
Dude, I had the same issue as you, couldn't load any roms, no matter what guide I followed, it always bootlooped. Turned out to be my microSD was causing it. I followed Life_goes_on's solution on this thread (post #74):
https://forum.xda-developers.com/g7-power/development/rom-resurrection-remix-t3994687/page8
Substituted 'fastboot erase userdata' for 'fastboot -w' and took out my microSD before booting it up and it worked.
I'm using the MetroPCS version on RETUS firmware.
Click to expand...
Click to collapse
bootloop
Alright I figured it out. It was my sdcard. I did everything using the Dave Chappelle method and it fixed it.
Dave Chappelle method:
1- remove sd card. In fact just remove the whole tray.
2- go back to stock, boot it, do whatever you gotta do. There is a thread on how to go back to stock, follow those instructions, its beyond the scope of the Dave Chappelle method.
3- go to bootloader with vol+pwr held
get your copypartitions.zip, your rom.zip, and twrp.img and twrp.zip in a folder. I like sybers twrp mod but whatever use official doesnt matter.
fastboot boot twrp
wait 3 seconds
adb push copypartitions.zip /tmp/
go to twrp install and go up a level, click copypartitions.zip, and install it. /tmp/ is memory, our phone has enough ram to do this.
adb shell
cd /tmp/
rm copypartitions.zip
# you dont have to do above, but we dont want too much stuff in memory, rebooting SHOULD clear memory, but I havent used android extensively they may have windows hibernate thing or whatever.
exit
adb reboot bootloader
fastboot boot twrp.img
adb push rom.zip /tmp/
go to twrp install and go up a level, click rom.zip, and install it. /tmp/ is memory, our phone has enough ram to do this.
adb shell
cd /tmp/
rm rom.zip
exit
adb push twrp.zip /tmp/
go to twrp install and go up a level, click twrp.zip, and install it. /tmp/ is memory, our phone has enough ram to do this.
adb shell
cd /tmp/
rm twrp.zip
exit
twrp select reboot bootloader
wait a tic
fastboot erase userdata
select recovery and boot
alright so at this point I am good because I dont want gapps or magisk I am done. I would boot a modified boot partition once a month and install adaware hosts modifications, then reboot. I dont want to be walking around with root or google proprietary code. I would then select reboot, make sure slotb is selected, and reboot system.
If you want gapps, then you flash your gapps at this point. I discourage you from doing so and encourage microg for google maps or whatever google service you actually need. I also discourage the idea of walking around with "hot" root. Where you can grant an application root at any time. It is trivial to write an application that modifies what the screen is displaying to trick you into accidentally granting root permissions.
Great guide! We really needed one. Btw you don't necessarily need a SD card to install zips, you can install them directly from your computer by sideloading them with adb on twrp. You can do that by going into twrp, then to Advanced and press on ADB Sideload, now on adb type in: "adb sideload thezipyouwanttoinstall.zip" and twrp will start installing that zip.
BETA215 said:
Hi guys. If you can't install ROMs, this is your place to ask. Please be detailed, mention: ROM, build, your variant and firmware version. And tell us your specific issue.
Here's a guide on how to do it, and I'll link you to the files needed for the procedure:
1. If you're using a Google account, remove it in Settings > Accounts and factory reset. Else, skip this step.
2. Unlock your bootloader following Motorola's instructions. Google it, it'll be easy to find and follow.
3. Download:
. Fastboot tools/Minimal ADB & Fastboot or your prefered fastboot program for PC.
. A firmware image for your variant
. ROM you want to install
. GApps (optional): http://opengapps.org/
. Magisk (optional): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And the next files:
TWRP (img) & TWRP installer (zip): https://androidfilehost.com/?w=files&flid=299042
copypartitions.zip: https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
You'll need an SD card to store the files needed for installing the ROM, since internal storage won't be usable temporarily.
4. Hold power + volume down until you reach bootloader (fastboot mode).
In your extracted firmware folder open a terminal and flash your firmware files with these commands:
----------------------------------------------------------------------
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot set_active a
fastboot reboot-bootloader
sleep 5
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 5
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.2
fastboot flash vendor_b vendor.img_sparsechunk.0
fastboot flash vendor_b vendor.img_sparsechunk.1
fastboot flash vendor_b vendor.img_sparsechunk.2
fastboot flash oem_a oem.img
fastboot flash oem_b oem.img
fastboot oem fb_mode_clear
fastboot reboot-bootloader
--------------------------------------------------------------------
Don't worry if any error message appears.
5. Place TWRP .img file into your fastboot folder, and do "fastboot boot TWRP.img" - replace TWRP with file's real name, but it should be the IMG file's name, not the zip file's name. With TWRP booted, now check if the screen actually responds. If it doesn't, just turn your phone off, get into fastboot mode again, and boot TWRP until it works.
6. With that solved, now just copy copypartitions.zip to your sdcard (called external_sd in your phone) and install it. Also copy to your external_sd, just to save time, your ROM and TWRP's installer. And Magisk or GApps if you'll need them.
7. Reboot to bootloader, and do "fastboot -w".
8. "fastboot boot" TWRP again, flash ROM, and flash TWRP's installer (zip file). Boot system.
9. Reboot to bootloader, select recovery mode and flash Magisk/GApps if you need them.
10. Reboot to system, and enjoy
Any questions, feel free to ask 'em in the comments. Hope it works!
P.S.: OmniROM has its own recovery (TWRP is a recovery). So, keep that in mind and don't flash TWRP's zip in Omni if you want it to boot.
Also, if you want, you can try OrangeFOX. It's a cute TWRP replacement that has some interesting features. Worth checking out.
Click to expand...
Click to collapse
Is there an orange Fox recovery for Moto G7 power?
Ljw4884 said:
Is there an orange Fox recovery for Moto G7 power?
Click to expand...
Click to collapse
Yes and it's absolutely amazing!
You can find it here
@BETA215, I see some folks mentioning bootloops. I personally had many many bootloops before I found out that TWRP/ ROM flashing on this device does not play nice with exFAT filesystem. maybe a note about that in the OP? formatting my SDcard to VFAT resolved all my issues, when it was ExFAT I couldn't get anything past the boot logo
I've just spent the past 10 days trying to root my phone and use a custom ROM working (and detecting SIM card and most important functions). But it's always problem after problem after problem and at this point, I'm ready to give up. I feel broken. I'm at the point where I'd literally pay someone to take control and do it for me. I just can't do it no matter how much I learn, always a new problem and now I'm stuck at this one and I just can't take it anymore. Swear to god, I will pay .
Deleted
SIM Card issue and no gapps?
Hi,
I installed Havoc OS on my moto g7 power XT1955-5, using these steps:
1) Switched off device
2) Volume down+Power to go in bootloader
3) CMD: fastboot erase userdata (maybe useless)
4) CMD: fastboot boot "C:\...\twrp.img" (or orangefox.img)
5) On Slot B mount "system" then wipe and format (maybe useless)
6) On Slot A mount "system" then wipe and format
7) Flash copy-partition-AB.zip
8) Flash Havoc ROM
9) Reboot -> Recovery
10) Flash GApps
11) Reboot -> Bootloader
13) CMD: fastboot erase userdata
14) CMD: fastboot reboot
(from time to time the message: failed to mount /data (invalid argument) popped up, and I don't know why)
However, havoc installed. I don't think Gapps installed though, because all I see in the os that is google related is a searchbar for apps only, gallery go, and the file manager. I used the "arm, 9.0, nano" options from the Gapps website, but when I flashed it, it said no changes were made. Did Gapps flash properly? If it didn't, how do you flash it properly? (I would expect the google play store to be in there somewhere, perhaps I need to get a heavier Gapps than nano?)
More importantly though, the OS says there is no sim card. I am on T-mobile, and calling and texting worked when I used lineage OS.
Does anyone have any advice of how to fix any of these issues? Again, my end goal is to have havoc os with the play store, and have the sim card working to make calls and texts.
Thank you one million to who ever can answer this.
Octodad said:
I've just spent the past 10 days trying to root my phone and use a custom ROM working (and detecting SIM card and most important functions). But it's always problem after problem after problem and at this point, I'm ready to give up. I feel broken. I'm at the point where I'd literally pay someone to take control and do it for me. I just can't do it no matter how much I learn, always a new problem and now I'm stuck at this one and I just can't take it anymore. Swear to god, I will pay .
Click to expand...
Click to collapse
Hey I literally am feeling the same way!! I know it's been a few months, but if you are still working on it, would you like to share knowledge and see if we can help each other?
timba123 said:
MetroPCS Moto G Power .I can't flash anything. And it oem locked. Is there any way to flash a stock partition ? Like Samsung's pit file
Click to expand...
Click to collapse
Try rsd light check into it might b what u looking for
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using payload dumper. If you haven't done any of these things yet, there are plenty of other guides out there on how to do them.
Steps:
1. Reboot your device to the bootloader (power off, then hold volume up + power) and connect it to USB.
2. The following command will wipe your device. I found this to be necessary to recover my OnePlus 9:
Code:
fastboot -w
3. Now flash the following files:
Code:
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
4. Now reboot into userspace fastboot, aka fastbootd. If you don't do this, the remaining files cannot be flashed:
Code:
fastboot reboot fastboot
5. Flash the remaining files:
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
6. Final reboot:
Code:
fastboot reboot
7. If everything worked your phone should now boot into OxygenOS.
Note:
The files will be flashed to your currently active boot slot. If any of them fail to flash, switch to the other slot and start over from the beginning. I wasn't able to flash odm, product, system, system_ext and vendor to slot a, and had to use slot b instead. To check current slot:
Code:
fastboot getvar current-slot
To switch slots:
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
Use this guide at your own risk. I take no responsibility if you brick your device, set it on fire, or otherwise mess it up as a result of any of the above steps. That being said, it worked for me using 11.2.2.2.LE25AA available from the official OnePlus support website.
If you want, you can do the flashing easily with powershell, rather than running each command one after the other. Here is what I did:
1. Have fastboot.exe in your path, or in the same folder as all your extracted images. Open powershell and navigate to the folder with your boot images. Connect your phone to USB.
2. This will wipe your device! Reboot to the bootloader and run:
Code:
fastboot -w
3. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'boot|cpucp|dtbo|modem|oplusstanvbk|oplus_sec|qweslicstore|shrm|splash|vbmeta|vbmeta_vendor|vbmeta_system|vendor_boot|vm-bootsys'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
4. Run:
Code:
fastboot reboot fastboot
5. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'abl|aop|bluetooth|devcfg|dsp|featenabler|hyp|imagefv|keymaster|multiimgoem|qupfw|tz|uefisecapp|xbl|xbl_config|product|system|system_ext|vendor|odm'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
6. Run:
Code:
fastboot reboot
7. Proceed to boot normally.
The commands in steps 3 and 5 get a list of all files in the current directory with the .img extension, filter them to the correct ones to flash, and then flash them one after another.
If someone wants, I can probably throw together a script to run the whole process start to finish.
Edit: script attached. I've (unfortunately) had the opportunity to test it and fix all the bugs. So it works. You will need to have fastboot.exe accessible in your system PATH to run it.
Slikkster2k said:
If you want, you can do the flashing easily with powershell, rather than running each command one after the other. Here is what I did:
1. Have fastboot.exe in your path, or in the same folder as all your extracted images. Open powershell and navigate to the folder with your boot images. Connect your phone to USB.
2. Reboot to the bootloader and run:
Code:
fastboot -w
This will wipe your device!
3. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'boot|cpucp|dtbo|modem|oplusstanvbk|oplus_sec|qweslicstore|shrm|splash|vbmeta|vbmeta_vendor|vbmeta_system|vendor_boot|vm-bootsys'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
4. Run:
Code:
fastboot reboot fastboot
5. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'abl|aop|bluetooth|devcfg|dsp|featenabler|hyp|imagefv|keymaster|multiimgoem|qupfw|tz|uefisecapp|xbl|xbl_config|product|system|system_ext|vendor|odm'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
6. Run:
Code:
fastboot reboot bootloader
7. Proceed to boot normally.
The commands in steps 3 and 5 get a list of all files in the current directory with the .img extension, filter them to the correct ones to flash, and then flash them one after another.
If someone wants, I can probably throw together a script to run the whole process start to finish.
Click to expand...
Click to collapse
That would be helpful indeed. Would this script run on mac as well?
Not unless there's a version of PowerShell for macs (there is for Linux, but I don't know if it's compatible).
@Slikkster2k: I tried your tutorial. At first it did not work...serveral errors occure during copying one file. On the second run I had to change the slot, than it runs through.
But now I am in a boot loop, during starting the oxygen.
While wiping I got this message:
Code:
fastboot: error: Cannot generate image for userdata
Which version of the OS did you use?
I tried to install the actual european rom (11.2.3.3) on my indian device from china but this obviously did not work. Do you have any suggestions for me?
AxelM said:
@Slikkster2k: I tried your tutorial. At first it did not work...serveral errors occure during copying one file. On the second run I had to change the slot, than it runs through.
But now I am in a boot loop, during starting the oxygen.
While wiping I got this message:
Code:
fastboot: error: Cannot generate image for userdata
Which version of the OS did you use?
I tried to install the actual european rom (11.2.3.3) on my indian device from china but this obviously did not work. Do you have any suggestions for me?
Click to expand...
Click to collapse
I used 11.2.2.2.LE25AA as I said in the original post (this is the global variant, which matches my device). I am not sure if this works for cross-flashing, or if it's possible to cross-flash an Indian phone to EU. Have you tried restoring the Indian ROM? Does that work?
You're getting an actual boot loop? The error I was getting (and the reason I had to restore) was the phone booting to the bootloader or fastbootd (depending on the slot I tried) instead of Oxygen, because it couldn't mount the user partition due to encryption. In fastbootd an error was reported (I forget the exact one) which made me suspect it was a partition mounting issue. At no point was my phone actually boot looping, even during partial/failed flashes.
I've never encountered the error with fastboot -w, but I only did that on my phone once. From some searching online, it can be caused by an old version of the platform tools, so did you download the latest version?
@Slikkster2k: First of all, thank you for providing help
In deed, what worked was the indian first version. This i could flash and from there on everything works. Up to OS and than installing the latest european os. Now everything ist fine...
The error while whiping did not occure while using the indian version...so no clue why...
But now it works for me, thank you!
AxelM said:
@Slikkster2k: First of all, thank you for providing help
In deed, what worked was the indian first version. This i could flash and from there on everything works. Up to OS and than installing the latest european os. Now everything ist fine...
The error while whiping did not occure while using the indian version...so no clue why...
But now it works for me, thank you!
Click to expand...
Click to collapse
Glad to hear you got it working!
PowerShell script added to second post. Totally untested, but I tried to make it as idiot proof as possible.
Slikkster2k said:
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using payload dumper. If you haven't done any of these things yet, there are plenty of other guides out there on how to do them.
Steps:
1. Reboot your device to the bootloader (power off, hold volume up + power) and connect it to USB.
2. The following command will wipe your device. I found this to be necessary to recover my OnePlus 9:
Code:
fastboot -w
3. Now flash the following files:
Code:
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
4. Now reboot into userspace fastboot, aka fastbootd. If you don't do this, the remaining files cannot be flashed:
Code:
fastboot reboot fastboot
5. Flash the remaining files:
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
6. Reboot back into the bootloader:
Code:
fastboot reboot bootloader
7. You should now be able to continue booting normally by pressing the power button.
Note:
The files will be flashed to your currently active boot slot. If any of them fail to flash, switch to the other slot and start over from the beginning. I wasn't able to flash odm, product, system, system_ext and vendor to slot a, and had to use slot b instead. To switch slots:
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
Use this guide at your own risk. I take no responsibility if you brick your device, set it on fire, or otherwise mess it up as a result of any of the above steps. That being said, it worked for me using 11.2.2.2.LE25AA available from the official OnePlus support website.
Click to expand...
Click to collapse
My phone has been weird for a week or so occasionally freezing up and saying system ui has crashed or something so I followed these instructions last night to completely wipe and reset everything (after backing up). It worked perfectly!
My only suggestion would be for step 7 to be:
fastboot reboot
Since we're already using fastboot it's just quicker and less fiddly than using the power button
toyanucci said:
That would be helpful indeed. Would this script run on mac as well?
Click to expand...
Click to collapse
Windows offered now to add to MAC - https://support.apple.com/en-us/HT201468
toyanucci said:
My phone has been weird for a week or so occasionally freezing up and saying system ui has crashed or something so I followed these instructions last night to completely wipe and reset everything (after backing up). It worked perfectly!
My only suggestion would be for step 7 to be:
fastboot reboot
Since we're already using fastboot it's just quicker and less fiddly than using the power button
Click to expand...
Click to collapse
Thanks, updated OP.
ok i kind of bricked my phone using this and i need a little help PLEASE?
Ok i tried the fist 2 steps 1. fastboot -w than the first list of commands using cmd with admin rights it worked...i think but it did load everything without issues...now i go to do the "fastboot reboot fastboot"
and now my phone is stuck on a black screen with nothing and i just hear the chime windows makes when you disconnect and reconnect a device..... and in the Device manager this comes up for 10 seconds than goes away for 5 than comes back NON STOP
i cant adb i cant do anything please help !
I'm not sure if this will help you, but I had a lot of issues initially running this. First off you need to use the Oneplus drivers, I don't think the qualcom driver will work the same way. I could be wrong, but that's what I did. Secondly, you need to force install the driver because Windows doesn't like it.
Here are the steps I took.
1. Uninstall any old drivers.
2. Install the newest Oneplus Drivers from here https://oneplususbdrivers.com/
3. Extract the zip file and run the installer like normal
4. Once the installer finishes, you'll need to reboot your machine and bring up the Startup settings (hold down shift and reboot (keep holding down shift until you get a screen with options)) Then click advanced and startup settings and hit restart after that. Once the machines starts up, on the first boot you will have a bunch of options. Choose option 7 "disabling driver signature enforcement" mode.
5. Once Windows launches and you login, go back into the device manager and follow these steps:
right click the device --> update driver
Browse my computer for drivers
Let me pick from a list of available drivers on my computer
Show all Devices --> Next
Have Disk (Button)
Navigate to where you installed Oneplus drivers (Default: C:\Program Files (x86)\OnePlus USB Drivers)
Select "OnePlus_android_winusb.inf"
Select "Oneplus Android Bootloader Interface" and then just hit next/OK until it installs.
You might need to reboot after doing the above, but this worked for me.
----------------------------------------
The above should get your drivers working properly in all modes (adb, fastbootd, bootloader, normal)
One other issue that I ran into when I was using the powershell script was that I was seeing intermittent errors. After trial and error I realized that Windows was picking up a different version of fastboot. I was initially using the minimal adb/fastboot files, but if you compare those to the ones listed in the first post in the "SDK Platform Tools", they are very different from each other, so you need to make sure you use the SDK Platform Tools version. The minimal ADB/Fastboot version will NOT work.
After I got those 2 things ironed out, the powershell script ran without a hiccup and my phone is stock and booting without an issue.
I know I'm late to respond to this thread, but I hope someone finds this information helpful!
Mine keeps trying this and it isn't running and or rebooting into Fastbootd when the script is ran. Should I just try and invoke this manually? I've tried that as well an I'm seeming to get errors left and right with no resolve.
I'd say try it manually and see where the errors happen. Does it boot into fastbootd at all?
Good work
toyanucci said:
I'd say try it manually and see where the errors happen. Does it boot into fastbootd at all?
Click to expand...
Click to collapse
Actually, I ended up making my phone hard bricked to the point where it doesn’t even turn on at this point. I’m just going to send it in for repair, which is nothing short of being due to my stupidity.
ilikepie___ said:
Actually, I ended up making my phone hard bricked to the point where it doesn’t even turn on at this point. I’m just going to send it in for repair, which is nothing short of being due to my stupidity.
Click to expand...
Click to collapse
It's probably stuck in edl mode. Nothing on the screen, no vibration or anything but it shows up in device manager when connected to a computer?
Try the man tool mentioned Here that worked for me.
toyanucci said:
It's probably stuck in edl mode. Nothing on the screen, no vibration or anything but it shows up in device manager when connected to a computer?
Try the man tool mentioned Here that worked for me.
Click to expand...
Click to collapse
I’ll give it a shot, yeah it doesn’t do anything. Can’t see a display or anything on the screen.