Related
Im reverting back to android 6.0 for my k1
But when i go to flash userdata its says userdata isnt found
And i look in the zip and it wasnt there so i downloaded again and it still wasnt there any suggestions
1 more thing nvidias instrucrions say to
Fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
And rhats it do i reboot after blob?
Cause someone elses tutorial says to
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
Tjeres an extra command?
Which do i use?
Thx
Iceek1 said:
Im reverting back to android 6.0 for my k1
But when i go to flash userdata its says userdata isnt found
And i look in the zip and it wasnt there so i downloaded again and it still wasnt there any suggestions
1 more thing nvidias instrucrions say to
Fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
And rhats it do i reboot after blob?
Cause someone elses tutorial says to
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
Tjeres an extra command?
Which do i use?
Thx
Click to expand...
Click to collapse
Don't worry, that one isn't included in the latest Nougat builds as well and they still flash normally.
Just proceed without that
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:
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
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY
WARNING
Proceed at your own risk. I am not responsible for any damage to your device.
Performing the instructed steps below will completely replace the existing firmware on your device, including bluetooth, WiFi and radio firmware.
Do not proceed unless you are absolutely certain your device is the T-Mobile GM1915 Model
Flashing Android 11 will remove TWRP if installed, and custom recovery will no longer be available.I have temporarily removed instructions for flashing this firmware until I can test it further.
FIRMWARE DETAILS
Version Name: OnePlus7ProTMOOxygen_11_2104261207
Version: OnePlus7ProTMOOxygen_11.O.20_GLO_020_2104261207
Security Patch Level: 2021-04-01
OOS Version: 11.0.1.2.GM31CB
DOWNLOADS
GM1915_11.0.1.2.GM31CB.zip (2.6GB) - md5: 2bb808a07052d5b240e3c8d3dfaf95ac
If you have any problems with the downloads or process, please reply to the thread and tag me. Thanks!
weakNPCdotCom said:
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY
WARNING
Proceed at your own risk. I am not responsible for any damage to your device.
Performing the instructed steps below will completely replace the existing firmware on your device, including bluetooth, WiFi and radio firmware.
Do not proceed unless you are absolutely certain your device is the T-Mobile GM1915 Model
Flashing Android 11 will remove TWRP if installed, and custom recovery will no longer be available.Now that Oxygen OS 11 has been pushed OTA to devices, some of us trying to revert back to stock TMO firmware may not want to revert to Android 10.
This guide will flash TMO 11.0.1.2 firmware to your device, reverting it to stock and updating it to Android 11
FIRMWARE DETAILS
Version Name: OnePlus7ProTMOOxygen_11_2104261207
Version: OnePlus7ProTMOOxygen_11.O.20_GLO_020_2104261207
Security Patch Level: 2021-04-01
OOS Version: 11.0.1.2.GM31CB
INSTRUCTIONS
If you are going to root: Have a copy of Magisk Manager v23 downloaded to your PC.
Option A: Manual Flash (Recommended)
Download GM1915_11.0.1.2.GM31CB.zip
Extract contents to your fastboot directory or a directory of your choice
For root, replace the extracted boot.img with the boot.img file in the "magisk_patched-OOS-11.0-boot" directory
Execute the following fastboot commands in order. Make sure you specify the path to the extracted images if they were not extracted to your fastboot directory
Code:
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
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 cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.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 hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash odm_a odm.img
fastboot flash odm_b odm.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 tz_a tz.img
fastboot flash tz_b tz.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 xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
fastboot erase ddr
If you are converting from a non TMO ROM, this step is required. Otherwise it is optional.
Code:
fastboot erase userdata
Reboot your device. Developer Options and USB Debugging may need to be re-enabled on first boot.
If you flashed the patched boot image for root, copy the Magisk Manager v23 apk to your device and install it. Run the app to make sure magisk is being detected properly.
Option B: Fastboot Update
*I have not tested this method*
Download GM1915_11.0.1.2.GM31CB_UPDATE.zip
Extract contents to your fastboot directory or a directory of your choice
Execute one of the following fastboot commands
Wipe Data (Required if coming from a non TMO ROM):
Code:
fastboot -w update images.zip
Keep Data:
Code:
fastboot update images.zip
OPTIONAL for root, execute the following
Code:
fastboot flash boot_a /magisk-patched-OOS-11.0-boot/boot.img
fastboot flash boot_b /magisk-patched-OOS-11.0-boot/boot.img
Reboot your device. Developer Options and USB Debugging may need to be re-enabled on first boot.
If you flashed the patched boot image for root, copy the Magisk Manager v23 apk to your device and install it. Run the app to make sure magisk is being detected properly.
DOWNLOADS
GM1915_11.0.1.2.GM31CB.zip (2.6GB) - md5: 2bb808a07052d5b240e3c8d3dfaf95ac
GM1915_11.0.1.2.GM31CB_UPDATE.zip (2.6GB) - md5: 12d8a57c1d56e0079bf4375513c1ece6
If you have any problems with the downloads or process, please reply to the thread and tag me. Thanks!
Click to expand...
Click to collapse
Question I owned the T-Mobile variant OnePlus 7 pro which is converted to the international variant running android 11 will this procedure work for me ?
Wouldn't work on my TMobile oneplus 7 pro with bootloader unlocked I get the error sending abl_a okay writing abl_a failed (remote: flashing is not allowed for critical partitions I'm currently on converted international international latest Android 11 update
mjb337 said:
Wouldn't work on my TMobile oneplus 7 pro with bootloader unlocked I get the error sending abl_a okay writing abl_a failed (remote: flashing is not allowed for critical partitions I'm currently on converted international international latest Android 11 update
Click to expand...
Click to collapse
that's strange, I am able to flash abl fine.
I'm also having this issue.
mjb337 said:
Wouldn't work on my TMobile oneplus 7 pro with bootloader unlocked I get the error sending abl_a okay writing abl_a failed (remote: flashing is not allowed for critical partitions I'm currently on converted international international latest Android 11 update
Click to expand...
Click to collapse
And unfortunately there's no way to get TWRP on Android 11 at the moment. Not sure about how else to go about flashing
weakNPCdotCom said:
that's strange, I am able to flash abl fine.
Click to expand...
Click to collapse
Strange it wouldn't work for me my bootloader plus my device have been carrier unlocked for almost two years and I'm converted to the international variant as well I've never had a problem with flashing I guess it's not for me I'll probably convert back to TMobile just to test there update
mjb337 said:
Question I owned the T-Mobile variant OnePlus 7 pro which is converted to the international variant running android 11 will this procedure work for me ?
Click to expand...
Click to collapse
If you have converted to international for all intents and purposes you now have a GSM1917 international. You can install Derpfest and all the other "regular roms". If you do the "manual method" where you flash each partition you should be good to go.
greytheVIIth said:
I'm also having this issue.
And unfortunately there's no way to get TWRP on Android 11 at the moment. Not sure about how else to go about flashing
Click to expand...
Click to collapse
Not true anymore. If this rom uses "fbev2" which apparently most true android 11 rom's do then nebrassy released a version a couple of days back that works just fine with android 11....I linked to it in the derpfest thread and posted install instructions which should work here as well. Even if you get twrp installed you probably still don't want to install the rom's via twrp...just do manual method and then use twrp for backup's etc.
weakNPCdotCom said:
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY
WARNING
Proceed at your own risk. I am not responsible for any damage to your device.
Performing the instructed steps below will completely replace the existing firmware on your device, including bluetooth, WiFi and radio firmware.
Do not proceed unless you are absolutely certain your device is the T-Mobile GM1915 Model
Flashing Android 11 will remove TWRP if installed, and custom recovery will no longer be available.Now that Oxygen OS 11 has been pushed OTA to devices, some of us trying to revert back to stock TMO firmware may not want to revert to Android 10.
This guide will flash TMO 11.0.1.2 firmware to your device, reverting it to stock and updating it to Android 11
FIRMWARE DETAILS
Version Name: OnePlus7ProTMOOxygen_11_2104261207
Version: OnePlus7ProTMOOxygen_11.O.20_GLO_020_2104261207
Security Patch Level: 2021-04-01
OOS Version: 11.0.1.2.GM31CB
INSTRUCTIONS
If you are going to root: Have a copy of Magisk Manager v23 downloaded to your PC.
Option A: Manual Flash (Recommended)
Download GM1915_11.0.1.2.GM31CB.zip
Extract contents to your fastboot directory or a directory of your choice
For root, replace the extracted boot.img with the boot.img file in the "magisk_patched-OOS-11.0-boot" directory
Execute the following fastboot commands in order. Make sure you specify the path to the extracted images if they were not extracted to your fastboot directory
Code:
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
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 cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.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 hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash odm_a odm.img
fastboot flash odm_b odm.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 tz_a tz.img
fastboot flash tz_b tz.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 xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
fastboot erase ddr
If you are converting from a non TMO ROM, this step is required. Otherwise it is optional.
Code:
fastboot erase userdata
Reboot your device. Developer Options and USB Debugging may need to be re-enabled on first boot.
If you flashed the patched boot image for root, copy the Magisk Manager v23 apk to your device and install it. Run the app to make sure magisk is being detected properly.
Option B: Fastboot Update
*I have not tested this method*
Download GM1915_11.0.1.2.GM31CB_UPDATE.zip
Extract contents to your fastboot directory or a directory of your choice
Execute one of the following fastboot commands
Wipe Data (Required if coming from a non TMO ROM):
Code:
fastboot -w update images.zip
Keep Data:
Code:
fastboot update images.zip
OPTIONAL for root, execute the following
Code:
fastboot flash boot_a /magisk-patched-OOS-11.0-boot/boot.img
fastboot flash boot_b /magisk-patched-OOS-11.0-boot/boot.img
Reboot your device. Developer Options and USB Debugging may need to be re-enabled on first boot.
If you flashed the patched boot image for root, copy the Magisk Manager v23 apk to your device and install it. Run the app to make sure magisk is being detected properly.
DOWNLOADS
GM1915_11.0.1.2.GM31CB.zip (2.6GB) - md5: 2bb808a07052d5b240e3c8d3dfaf95ac
GM1915_11.0.1.2.GM31CB_UPDATE.zip (2.6GB) - md5: 12d8a57c1d56e0079bf4375513c1ece6
If you have any problems with the downloads or process, please reply to the thread and tag me. Thanks!
Click to expand...
Click to collapse
Thank you very much!!!
saved my phone <3
Hi. This rom supports dual sim?
kobebryant said:
Hi. This rom supports dual sim?
Click to expand...
Click to collapse
This is a stock firmware package. Also, it is NOT a TRWP flashable zip. I can make one of those if twrp actually works now.
famewolf said:
Not true anymore. If this rom uses "fbev2" which apparently most true android 11 rom's do then nebrassy released a version a couple of days back that works just fine with android 11....I linked to it in the derpfest thread and posted install instructions which should work here as well. Even if you get twrp installed you probably still don't want to install the rom's via twrp...just do manual method and then use twrp for backup's etc.
Click to expand...
Click to collapse
Would it be possible for you to link me to the source of that TWRP build? I would like to get it on my phone.
Also, that would allow me to build a flashable zip of this firmware.
famewolf said:
Not true anymore. If this rom uses "fbev2" which apparently most true android 11 rom's do then nebrassy released a version a couple of days back that works just fine with android 11....I linked to it in the derpfest thread and posted install instructions which should work here as well. Even if you get twrp installed you probably still don't want to install the rom's via twrp...just do manual method and then use twrp for backup's etc.
Click to expand...
Click to collapse
I found nebrassy's twrp image, but it still does not support decryption.
Also, when I booted to it, it messed up my entire system. The phone was no longer able to boot to android and when I reflashed my boot image it started crashing on boot.
I am looking into how to get this working properly.
weakNPCdotCom said:
I found nebrassy's twrp image, but it still does not support decryption.
Also, when I booted to it, it messed up my entire system. The phone was no longer able to boot to android and when I reflashed my boot image it started crashing on boot.
I am looking into how to get this working properly.
Click to expand...
Click to collapse
If you didn't find the post where he specifically says "here is the fbev2 version" then you didn't install the right one. He has SEVERAL versions of twrp.
TWRP-3.5.1-guacamole-FBEv2-Nebrassy-3.img | by Nebrassy for OnePlus 7 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
famewolf said:
If you didn't find the post where he specifically says "here is the fbev2 version" then you didn't install the right one. He has SEVERAL versions of twrp.
Click to expand...
Click to collapse
i assumed that the filename "TWRP-3.5.1-guacamole-FBEv2-Nebrassy" indicated it was FBEv2 xD
weakNPCdotCom said:
i assumed that the filename "TWRP-3.5.1-guacamole-FBEv2-Nebrassy" indicated it was FBEv2 xD
Click to expand...
Click to collapse
See previous file link since the -3 in it means you might have an older version.
*update* Found actual post: https://forum.xda-developers.com/t/...eamwin-recovery-project.4289455/post-85197387
famewolf said:
See previous file link since the -3 in it means you might have an older version.
*update* Found actual post: https://forum.xda-developers.com/t/...eamwin-recovery-project.4289455/post-85197387
Click to expand...
Click to collapse
yeah, that says "only use if you are on a custom rom and other builds dont work for you"
it ended up soft-bricking my phone
weakNPCdotCom said:
yeah, that says "only use if you are on a custom rom and other builds dont work for you"
it ended up soft-bricking my phone
Click to expand...
Click to collapse
Both Derpfest and Yaap work well with fbev2 and are Android 11 based on AOSP. I'm sorry that happened to you. In future you should use "Fastboot BOOT twrp.img" to boot recovery without replacing the existing recovery...then if it didn't work all you'd need to do if force the phone to power off via holding down vol up and power for several seconds. Still not sure how you soft bricked because I tried installing it in recovery on a non compatible rom and all it did was startup and show available storage as 0. It showed no files...once i upgraded the rom then it worked fine.
If you pay attention to with slot you are booting to and flashing to ,it will help out slot. This will always leave you a option to repair. By just switching to the opposite slot to boot to recovery. If you don't know the command then you should really learn fastboot --help. It's all the same as Python.
Hi, do you have the 11.0.1.3 update as well ? I can't install it through OTA, installation keeps failing for whatever reason...
Pluginbaby00 said:
Hi, do you have the 11.0.1.3 update as well ? I can't install it through OTA, installation keeps failing for whatever reason...
Click to expand...
Click to collapse
I have the extracted payload, but im not sure if it's actually usable on the GM1915. I can upload it if you need it, but there are several partitions you cant flash and the system image is not in the proper sparse format.
Now that I have my IMEI numbers restored, I am going to again attempt to flash LineageOS over my stock Android 9.
Let's say I want the latest revision of LineageOS 18, I understand that this is the required system image;
lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite.img.xz
I also know a vbmeta file is required. This is where I get confused and suspect it's the reason I always get bootloop when flashing.
Do I need a stock vbmeta, a modified vbmeta or a blank vbmeta? I have quite the collection.
Also do I add flags;
--disable-verity
and / or
--disable-verification
Now last, but not least, is my sequence of flashing correct?
fastboot flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system system.img
fastboot erase userdata
fastboot reboot
I appreciate your time and help.
probably stock vbmeta will work, or get the one in TWRP page for Nokia 2.2