Hello guys, first of all thanks for taking the time to at least read this. Anyways, I have been stuck since yesterday on Oreo, I wanted to give it a try so I flashed that unbranded firmware through HWOTA and then flashed the Oreo update. But the thing is the performance was so bad, I immediately wanted to go back to Nougat, so then I tried flashing that unbranded firmware again, but apparently the partitions changed on Oreo, so I wasn't able to flash TWRP, I then ran "fastboot flash recovery_ramdisk twrp.img" not sure about the command, but yeah. And it ****ed everything up, whenever I reboot my phone I'm greeted with the "error mode" message and then my phone boots back up to Oreo.
I tried everything, i'm out of ideas, so I'd really appreciate it if one of you could help me go back to stock, because I just got that phone and it pisses me off that I already messed it up.
Thanks in advance.
I think you missed a parameter for fastboot command. You need to indicate which partition you want to flash the file to. It should be:
fastboot flash recovery yourtwrp.img
There is a generic recovery updated (don't remember if from the equivalent Mate or Honor devices) which works for our device and should handle Oreo partitions with success.
Related
Ok, so lets start from the beginning.
I have a OnePlus 3t and I have been trying for the whole day to get multirom up and running.
Made a couple of mistakes in the beginning (nothing serious) although i decided to use the unbrick tool to fully clean it.
After successfully cleaning it I booted, skipped thru the setup, went to developer settings, enabled oem unlocking and verified the computer signature.
Went to fastboot mode unlocked oem, and flashed TWRP like this:
Code:
fastboot flash recovery TWRP.img
fastboot boot TWRP.img
It all went well, then in twrp I copied a backup from my pc (that I made previously) and restored it.
And here comes the actual problem. Whenever I try to boot into TWRP it is just a black screen and a the LED is white.
Only way to boot into TWRP is by typing
Code:
fastboot boot TWRP.img
while in fastboot
Does anyone have a clue on this one?
(Sorry if grammar isn't perfect)
TheGamer14 said:
Ok, so lets start from the beginning.
I have a OnePlus 3t and I have been trying for the whole day to get multirom up and running.
Made a couple of mistakes in the beginning (nothing serious) although i decided to use the unbrick tool to fully clean it.
After successfully cleaning it I booted, skipped thru the setup, went to developer settings, enabled oem unlocking and verified the computer signature.
Went to fastboot mode unlocked oem, and flashed TWRP like this:
Code:
fastboot flash recovery TWRP.img
fastboot boot TWRP.img
It all went well, then in twrp I copied a backup from my pc (that I made previously) and restored it.
And here comes the actual problem. Whenever I try to boot into TWRP it is just a black screen and a the LED is white.
Only way to boot into TWRP is by typing
Code:
fastboot boot TWRP.img
while in fastboot
Does anyone have a clue on this one?
(Sorry if grammar isn't perfect)
Click to expand...
Click to collapse
Update: Just booted into recovery by using
Code:
fastboot boot TWRP.img
and now I'm unauthorized in adb
The unbrick tool flashes an old firmware that won't start twrp. You need to update the firmware to a newer version. Try this firmware zip and report please:
http://forum.xda-developers.com/showpost.php?p=70145090&postcount=41
sniperle said:
The unbrick tool flashes an old firmware that won't start twrp. You need to update the firmware to a newer version. Try this firmware zip and report please:
http://forum.xda-developers.com/showpost.php?p=70145090&postcount=41
Click to expand...
Click to collapse
Downloading and trying rn
sniperle said:
The unbrick tool flashes an old firmware that won't start twrp. You need to update the firmware to a newer version. Try this firmware zip and report please:
http://forum.xda-developers.com/showpost.php?p=70145090&postcount=41
Click to expand...
Click to collapse
I somehow made everything even worse so using the unbrick kit again.
Should I OTA update when in system?
Just tried doing a OTA and while it was rebooting it WIPED the data by some reason.
So now it is basically a clean install that needs a OTA that probably will wipe it again...
Ok just tried it again and it seems to actually update. Gonna report back soon
TheGamer14 said:
Just tried doing a OTA and while it was rebooting it WIPED the data by some reason.
So now it is basically a clean install that needs a OTA that probably will wipe it again...
Click to expand...
Click to collapse
So it seems like if you try to update while having a pc attached wipes the data?
This is really weird
sniperle said:
The unbrick tool flashes an old firmware that won't start twrp. You need to update the firmware to a newer version. Try this firmware zip and report please:
http://forum.xda-developers.com/showpost.php?p=70145090&postcount=41
Click to expand...
Click to collapse
YESSS I'm finally able to boot into twrp TNX SO MUCH
Glad to hear you aced this. Just for further explansion:
The OS update does a firmware update too.
I took the firmware from the 3.5.4 flash zip from oneplus.
Hello all..
my name is daniel, i have an H9L. My H9L has been rooted and installed TWRP. I want to install a ROM called LineAgeOS, before that I have backed up the data. and I started to reset my H9L, when I wanted to install a ROM there was a problem, because the difference in my processor failed to install the ROM. and I hit it wrong, I restarted my H9L, now my H9L is on without a stock ROM, and it is strange that my TWRP is not working, just stuck in the TEAMWIN logo, can anyone help me to restore my H9L the original state, my H9L only works in the FASTBOOT MODE state, I tried to flash my H9L with ADB DRIVER but failed, I tried to flash with MICRO SD and made the dload folder but failed at 5%, what have I confused, is there anyone here who can help my problem, THANK YOU.
DjPangau said:
Hello all..
my name is daniel, i have an H9L. My H9L has been rooted and installed TWRP. I want to install a ROM called LineAgeOS, before that I have backed up the data. and I started to reset my H9L, when I wanted to install a ROM there was a problem, because the difference in my processor failed to install the ROM. and I hit it wrong, I restarted my H9L, now my H9L is on without a stock ROM, and it is strange that my TWRP is not working, just stuck in the TEAMWIN logo, can anyone help me to restore my H9L the original state, my H9L only works in the FASTBOOT MODE state, I tried to flash my H9L with ADB DRIVER but failed, I tried to flash with MICRO SD and made the dload folder but failed at 5%, what have I confused, is there anyone here who can help my problem, THANK YOU.
Click to expand...
Click to collapse
Have you tried Erecovery to restore stock?
On the bootloader unlocked warning screen press and hold volume+ for 3 secs.
Needs to use WiFi.
Try yo reflash twrp in fastboot mode. The command is fastboot flash recovery_ramdisdisk twrp. Img
Before you have to put twrp. img in the adb folder
I'm experiencing the same problem after trying to root my h9l through twrp the mistake I made is that I flashed the image in a wrong partition.
I can only access a fastboot mode with frp and phone unlocked, it cannot even display a charging screen. Once plugged it keeps on rebooting and hangs on error screen,
I have tried to flash kernel,ramdisk, recover_ramdisk and system images all on their respective partition, the flashing went well, but the phone didn't respond.
I've tried to flash boot.IMG (some one posted for h9l,) into Boot partition, but it revealed an error.
Any one please help what should I do to brings by device back to lite
Got official notification and have installed Pie (9.0.1.163) on my VTR-L09C432 P10.
Downloaded the Full OTA (9.0.1.163), extracted the RECOVERY_RAMDIS.img, patched with Magisk 7.1.1 and flashed using fastboot to the recovery_ramdisk partition. When rebooted with Vol+ have root. Played around with Pie and have decided to revert back to Oreo.
HiSuite (v9.0.3.300_OVE) did offer me rollback to 8.0.0.365. So I have decided to pursue this option. The firmware download went OK (100%), the programing went OK (100%) and the phone rebooted, as said the popup, but ... it was still on Pie as before.
Decided to try to "upgrade" via eRecovery. It wasn't able to determine and download any package. So I tried factory reset. No error, but it seems to do nothing. The phone rebooted and the situation is: Pie works, Magisk reports root 18.1 and root apps work.
From this moment I am unable to enter fastboot. The phone just boots normally with Magisk root. As I have just written eRecovery is present but is useless (can't download an upgrade package and can'r factory reset).
Advice?
Should I try writing from a term using dd the extracted RECOVERY_RANDISK.img and ERECOVERY_RAMDISK.img ? This way will loose root (Magisk) but don't know if it "resolve" access to fastboot and "fix" eRecovery.
EDIT:
No reply so decided to go ahead with what I thought was happening. I didn't know that a firmware upgrade (or downgrade) needs recovery to complete. I thought erecovery was the key.
So when I used HiSuite to rollback to Oreo what happened was it downloaded the Oreo firmware, uploaded it to the phone, prepared for a firmware flash and did a reboot. The firmware downgrade was supposed to happen in recovery but since the recovery code was changed by Magisk the flashing was never happening.
The same when from erecovery I tried to do a factory reset. Seems that erecovery just prepares things but recovery code does the actual reset. And once again I was observing that nothing was happening. The phone was simply root booting exactly as the Magisk code is supposed to do.
So I just flashed (from a term) the original recovery_ramdisk.img. After reboot got the factory reset welcome screen.
Of course got back fastboot.
Hope this can be of of help someone is a similar situation
Dude can you please guide us how to actually use DD command.
edit: I did this a different way. much easier & safer for less experienced users.
1. Open magisk manager. At the bottom of the first screen there is a button "UNINSTALL". Press uninstall & click "restore images".
2. Magisk will remove itself and restore your original boot image. Worked for me
Trying to flash TWRp after unlocking bootloader. First time i tried it, said successful but booted to MIUI recovery
2nd time i tried said again successful, booted to TWRP, formatted data.
Phone then wouldnt reboot to TWRP. Instead it going straight to fastboot. I keep trying to flash again, every time saying successful, then it just boots to fastbooot, not recovery. Any ideas, phones dead at the minute
Tones1971 said:
Trying to flash TWRp after unlocking bootloader. First time i tried it, said successful but booted to MIUI recovery
2nd time i tried said again successful, booted to TWRP, formatted data.
Phone then wouldnt reboot to TWRP. Instead it going straight to fastboot. I keep trying to flash again, every time saying successful, then it just boots to fastbooot, not recovery. Any ideas, phones dead at the minute
Click to expand...
Click to collapse
The best way to recover the phone in your situation is to fastboot flash MIUI.
Get the latest MIUI fastboot ROM for your phone from here
https://xiaomifirmwareupdater.com/miui/raphael/
Install it using this guide from the official MIUI forums
https://c.mi.com/oc/miuidownload/detail?guide=2
If you see a blank page on a mobile browser, set it to view in desktop mode, for this page.
Make sure in step 5 you change the option at the bottom of the Mi Flash Tool to 'clean all' before hitting the Flash button.
MIUI will restore stock recovery when it reboots, so you need to do something to fix this. Flashing Magisk or a custom ROM will automatically preserve TWRP.
If you plan to keep MIUI and do not want Magisk, then you need to flash the vbmeta patcher from here
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
You need to flash TWRP, then immediately boot into TWRP.
Code:
fastboot flash recovery <path to twrp>
fastboot oem reboot-recovery
At this point you need to flash something in order to preserve TWRP (either a new custom ROM, Magisk, or the vbmeta patcher)
Cheers. You know this is all familiar. Pretty sure i had the same trouble 3 years ago with my mi mix 2
Anyway, lots of hiccups on the way along with this solution. Got to the point now where it says its flashing but it never stops.
EDIT: Bit more research, shortened the path names. Got an error. Commented out device name, got a different error. Switched to USB 2.0 port an FINALLy im back up and running.
Thank you so much for the help.
My phone keeps getting stuck on fastboot mode.
I'll flash the standard MIUI ROM using the MiFlash Tool, then I flash a custom recovery and a custom ROM(EvolutionX in this case), everything works and I can set up my phone, but as soon as I reboot I can no longer boot into android or recovery. i've tried flashing multiple recoveries using fastboot and straight up booting a recovery using "fastboot boot recovery.img" but it still always go to fastboot. The only solution is to start the process all over again, and obviously that's just not an option since I can never turn my phone off after that.
Any tips?
I think I got it solved, at least I got it to reboot into Android and TWRP.
I used this guide, but I'll write the steps I took here in case you're having the same issue. I wound up using xiaomi.eu MIUI rom, but it shouldn't matter what you use, I'll assume you're stuck in fastboot.
Do "fastboot flash vendor vendor.img", you get this vendor.img from the fastboot version of the official MIUI ROM, after you decompress the .tar.gz it should be in the "images" folder
Do "fastboot flash recovery twrp.img" then "fastboot boot twrp.img", this should flash twrp as your recovery and then boot into it, for some reason it only worked with the official twrp, not orange fox.
Assuming you got into TWRP you should now flash the latest firmware(I got mine from xiaomifirmwareupdater.com) make sure you download just the firmware not the entire rom, mine was named something like fw_raphael_miui... .zip
Format data (not wipe, format, it's a separate option in TWRP), it should ask you to type yes, so do that.
Flash whatever ROM you want
Hopefully this helps you, I hate finding forum posts marked "solved" but with no instructions. I also tried the "vbmeta_dv_shivsom.img" method some threads mentioned but it didn't work
Here's a pastebin of the guide I used in case the original link goes down
You can get all the files I mentioned from xiaomifirmwareupdater.com and the official TWRP site
Out of all that, the one instruction that solves it is the format data step. This is the magic step required. You always need to do this when flashing over MIUI.
Flashing vendor was totally irrelevant.
This will tell you what you need to do.
Simple Guide to flashing successfully
Here's a quick guide to some of the basics. Which recovery. ---------------------------- Use the latest from here. https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363/post79823568 Do not use Orange...
forum.xda-developers.com
Thanks a lot man! I'm having this issue and it is beyond annoying. I've lost so much time with this BS.
Edit: Does not help actually
I just had the same problem with my Lamentablet.
I was trying stuff up and restarted it in fastboot mode and got stuck there.
So, ways to deal with it:
adb reboot recovery
rebooted the tablet in recovery mode. All I had then was to press the power button to activate Reboot. Solved! From now on it boots normally.
Meanwhile I had discovered that by typing
fasboot continue
the tablet would resume, but at the next reboot cycle, power down + up cycle or reboot after a crash, the tablet would reboot into fastboot mode...
And I found this out when it crashed (it's not called a Lamentablet for nothing!).
Luckily I had a PC with Linux around. It didn't have the software installed but drivers were already in the Kernel and installing adb and fastboot was a matter of mere seconds. If I didn't have an easily ready PC at hand, this tablet would have become a brick until plugged in and rebooted...
OMG Thanks dude.... I'm literally working to installing custom rom on redmi 7a from stock rom but I don't know what reason that make my phone always stuck on fastboot when format data, before this was fine.
Osga21 said:
I think I got it solved, at least I got it to reboot into Android and TWRP.
I used this guide, but I'll write the steps I took here in case you're having the same issue. I wound up using xiaomi.eu MIUI rom, but it shouldn't matter what you use, I'll assume you're stuck in fastboot.
Do "fastboot flash vendor vendor.img", you get this vendor.img from the fastboot version of the official MIUI ROM, after you decompress the .tar.gz it should be in the "images" folder
Do "fastboot flash recovery twrp.img" then "fastboot boot twrp.img", this should flash twrp as your recovery and then boot into it, for some reason it only worked with the official twrp, not orange fox.
Assuming you got into TWRP you should now flash the latest firmware(I got mine from xiaomifirmwareupdater.com) make sure you download just the firmware not the entire rom, mine was named something like fw_raphael_miui... .zip
Format data (not wipe, format, it's a separate option in TWRP), it should ask you to type yes, so do that.
Flash whatever ROM you want
Hopefully this helps you, I hate finding forum posts marked "solved" but with no instructions. I also tried the "vbmeta_dv_shivsom.img" method some threads mentioned but it didn't work
Here's a pastebin of the guide I used in case the original link goes down
You can get all the files I mentioned from xiaomifirmwareupdater.com and the official TWRP site
Click to expand...
Click to collapse
thanks bro. flashing vendor after a format from twrp did the good