I recently tried to install multirom but it kinda messed up, Now I can't either do fastboot boot recovery.img or fastboot flash recovery.img cause none of them works. I also tried to recover stock firmware but it didn't help. any help is appreciated.
I can boot into stock recovery via fastboot boot recovery.img but cannot boot a twrp or cwm.
Not loaded in recovery mod.
I flashed through fastboot nv-recovery-st-wx-na-wf-4.1.0 firmware
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
In rekaveri does not go, the firmware is loaded.
I tried to flash twrp-3.0.2-2-shieldtablet.img, but also does not go into it. Just shows nvidia inscription.
What prompt do? It is necessary to go to recovery!
I flashed
nv-recovery-image-shield-tablet-factory.zip most original firmware.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
I Nvidia after saying there's this
http://image.prntscr.com/image/64bb18f99d25468bb78aec67f7bd6fea.png
But it comes to recovery
http://image.prntscr.com/image/72805a63767148bab377a90d9b415623.png
everything is skewed
I flashed
twrp-2.8.7.0-shieldtablet
http://image.prntscr.com/image/836e3e3e40b94874b5a361a7f59d5b3b.png
What do I need to do?
I really need, if you not defective tablet (sent you to replace) 16 GB and a not new version of the tablet k1, please download the I
/dev/block/mmcblk0p24
If you have a version of the tablet with 16 GB and the battery b01, please copy me the file
/dev/block/mmcblk0p24 me it is very necessary. Without it, the tablet does not work.
PLS!!
It must be copied from the advanced> file manager from twrp
So recently i wanted to unroot, relock the bootloader and go back to factory condition. I flashed xposed too but i just deleted the app so idk if its still up?!
Unroot worked with supersu.
But then i wanted to relock the bootloader with the "Multi Tool 8".After relocking the bootloader I couldnt boot in my system so i Unlocked it again and booted into android 7!
Sadly i wanted to relock the bootloader so much, that i wiped /vendor and all other things except system and sd card in TWRP.
If i want to boot into system now , i cant. Either with bootloader unlocked or locked.
Only things i can do is going into fastboot mode or access eRecovery.
ADB and Fastboot Commands are working.
I tried to Rollback my device but its not working. What should I do now?
Sorry for my Bad englisch. My main Language is German.
1. Download honor 8 firmware from huawei firmware finder
2. Extract system.img, boot.img, recovery,img with huawei extractor tool
3. Unlock bootloader
4. Flash system.img, boot.img, recovery.img with fastboot with commands fastboot flash system system.img, fastboot flash boot boot.img,fastboot flash recovery recovery.img
4. Boot to recovery mode and factory reset and wait
5. Done. Now it should boot into the system.
Elkkooz said:
1. Download honor 8 firmware from huawei firmware finder
2. Extract system.img, boot.img, recovery,img with huawei extractor tool
3. Unlock bootloader
4. Flash system.img, boot.img, recovery.img with fastboot with commands fastboot flash system system.img, fastboot flash boot boot.img,fastboot flash recovery recovery.img
4. Boot to recovery mode and factory reset and wait
5. Done. Now it should boot into the system.
Click to expand...
Click to collapse
I will Look into that tomorrow.
Do I need TWRP recovery for the factory reset? Because in Stock Recovery i cant factory reset.
So I would flash system boot and TWRP instead of original recovery?
i cant factory reset!
Flashed system, boot and recovery successful.
But when i want to factory reset it stops by 16%
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:
I accidentally did "fastboot flash boot recovery.img" when trying to flash the stock recovery and now it just boots into recovery all the time. I was able to reflash TWRP so I can boot into that and I've restored the Boot partition from the backup I made but that didn't help, so I tried restoring the vendor image and system image, which didn't help either. Then I tried restoring the individual backups I made of the dtbo, EFS, modem, persists and recovery+vbmeta but it still boots into TWRP when I try to boot into system.
I hope someone can help me fix this, as I bought it to give to my brother for his birthday in a couple of weeks!
I note that the recovery.img is 65,536KB, which is the same size as my backed up boot.emmc.win but obviously they're not the same thing.
EDIT: OK, panic over! I wiped System and installed the A20 ROM from the ozip and it's working again now. Phew!
May I ask if how did you do that?
I think we almost have the same situation but rather different reason..Please help
doveman said:
I accidentally did "fastboot flash boot recovery.img" when trying to flash the stock recovery and now it just boots into recovery all the time. I was able to reflash TWRP so I can boot into that and I've restored the Boot partition from the backup I made but that didn't help, so I tried restoring the vendor image and system image, which didn't help either. Then I tried restoring the individual backups I made of the dtbo, EFS, modem, persists and recovery+vbmeta but it still boots into TWRP when I try to boot into system.
I hope someone can help me fix this, as I bought it to give to my brother for his birthday in a couple of weeks!
I note that the recovery.img is 65,536KB, which is the same size as my backed up boot.emmc.win but obviously they're not the same thing.
EDIT: OK, panic over! I wiped System and installed the A20 ROM from the ozip and it's working again now. Phew!
Click to expand...
Click to collapse
can you teach us how you fixed it?
Download the last Firmware, this is one for QPST also extracted
"Realme_5i_RMX2030_EX_11_C.79_220121_QPST.zip"
than extract it and open the Terminal and change to Firmware dir with cd "PATH" now you flash the follow Images
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash metadata metadata.img
fastboot flash dtbo dtbo.img
fastboot flash splash splash.img
fastboot flash persist persist.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
now device starts normaly and is up to date, your back on StockROM