Think i have rally buggered up and update, was going to try out the havoc rom, when i went to flash it i was told i needed to update vendor to v12 so i flashed the official miui vendor v12 rom, rebooted and now im stuck in a fastboot loop. i think my mistake was following the instructions on the havoc rom and wiping system, data, dalvik and cache without the havoc rom flashed.
this worked for me:
from https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
Full credits to @ SivSomRao (telegram handle, since no xda)
So, when I screwed my phone trying recoveries, I got stuck in FastBoot. no matter what I did, even Power + Vol Up got me to fastboot, and I had just wiped my OS, so I had nothing to boot into.
This happens when you wipe your SYSTEM and/or VENDOR partitions and choose reboot recovery, or flash an incompatible recovery.
After a lot of stressful minutes, scared half out of my mind. A guy named @Shivsom helped me.
Basically what he made me do was, Download his file vbmeta_dv_shivsom.img that is given below in attachments.
Then copy the twrp.img file and vbmeta_dv_shivsom.img file to my adb Folder.
Open the Command prompt in that folder, by clicking on the address bar of File Explorer and typing > cmd > then Enter
Type the instructions
Code:
fastboot flash vbmeta vbmeta_dv_shivsom.img
Then type, (Since my twrp image file was re-named to twrp.img, if you haven't done so, do it)
Code:
fastboot flash recovery twrp.img
Then press and hold Power and Volume Up till you feel the haptic feedback see the TWRP recovery[/QUOTE]
I was OverJoyed when this worked. However, every time I entered recovery, I was met with the fastboot logo again, Therefore, I just repeated the process I did when I first unlocked my bootloader via twrp in the tutorial above, which was, I went to manage partitions and formatted my data, wiped my rom, and did the same steps as in the tutorial when I first got my orange fox.
Now use twrp interface, copy orangefox.zip to my phone via PC, then flash that zip. Then go to settings > manage partitions > data > format data > type 'yes'. Then quickly flash a vendor, then a flash ROM (normal clean flash, tutorial given above) and then boot the ROM.
This was a nasty disaster. Glad I got through it.
Right so I tried LR-twrp (it's in Chinese, but I can change the language to English) . PitchBlack and PitchBlack-old Both broke my phone to get stuck in fastboot mode no matter what I did. .
HENCE I conclude that for all Xiaomi devices, OrangeFox [OFX] is the best recovery. TWRP is suited for Samsung.
The moral of this story is
Do not wipe vendor and/or system.
The is very little need to wipe either of these.
When you flash a ROM, the install will wipe system, as part of the process, before flashing the ROM
When you flash a vendor file, the install will wipe vendor, as part of the process, before flashing the vendor file.
I have no idea why we have all the devs giving instructions to wipe these partitions as part of the process to install a ROM. It looks like it's a case of them all copying and pasting each other, so it's getting added to the installation instructions of each ROM that comes along.
A few years back, there was some instances where wiping system became necessary, though I can no longer remember the details. Suddenly everyone was saying that a normal clean flash was no longer enough and we should all be blitzing all partitions when installing a new ROM. It feels like this mentality is still present, even though it is absolutely not required.
In future, when installing a new ROM, stick with the factory reset in TWRP, it's all that is needed. There is a very good reason it is on the first page of the wipe menu in TWRP. Doing ordinary installs there should be no reason to go into the advanced wipe menu.
Robbo.5000 said:
The moral of this story is
Do not wipe vendor and/or system.
The is very little need to wipe either of these.
When you flash a ROM, the install will wipe system, as part of the process, before flashing the ROM
When you flash a vendor file, the install will wipe vendor, as part of the process, before flashing the vendor file.
I have no idea why we have all the devs giving instructions to wipe these partitions as part of the process to install a ROM. It looks like it's a case of them all copying and pasting each other, so it's getting added to the installation instructions of each ROM that comes along.
A few years back, there was some instances where wiping system became necessary, though I can no longer remember the details. Suddenly everyone was saying that a normal clean flash was no longer enough and we should all be blitzing all partitions when installing a new ROM. It feels like this mentality is still present, even though it is absolutely not required.
In future, when installing a new ROM, stick with the factory reset in TWRP, it's all that is needed. There is a very good reason it is on the first page of the wipe menu in TWRP. Doing ordinary installs there should be no reason to go into the advanced wipe menu.
Click to expand...
Click to collapse
Thank you for this type of answer. I was trying use all the instructions to wipe, but all the time I got brick (fastboot loop) in my Mi 9 SE. Not problem when usign the first page of the wipe.
Related
Hello all,
After following a few possibly outdated threads I was following this tutorial I found using google search (probably should have checked around for the all in one toolkit first):
http://forum.xda-developers.com/showthread.php?t=2182792
Since I looked at a bunch of ROM reviews I thought I'd try SlimRoms. So as per the suggestions under step 3, I skipped to step 4. I then followed the SlimRom instructions. I flashed Gapps successfully, but got a failed message when trying to flash the ROM. So I thought I'd just go to step 3 again. At this point I tried to reboot and got the following message
"Your device does not appear to be rooted. Install SuperSU now?..."
I choose to install and that's when my problem started. I was stuck at the htc loading screen. The following thread seemed like it would help, but since I installed the TWRP recovery 'm not sure where to find where to erase the cache and side load ROM for one.
http://forum.xda-developers.com/showthread.php?t=2280230
I may have a learned a lesson, but still don't want to give up on taking a stab at having a rooted phone. I'd like to get better at it, so thanks for any and all advice.
Also sorry if the question sounds a little incoherent, I'm kinda tired and frustrated at the moment.
G1N0 said:
Hello all,
After following a few possibly outdated threads I was following this tutorial I found using google search (probably should have checked around for the all in one toolkit first):
http://forum.xda-developers.com/showthread.php?t=2182792
Since I looked at a bunch of ROM reviews I thought I'd try SlimRoms. So as per the suggestions under step 3, I skipped to step 4. I then followed the SlimRom instructions. I flashed Gapps successfully, but got a failed message when trying to flash the ROM. So I thought I'd just go to step 3 again. At this point I tried to reboot and got the following message
"Your device does not appear to be rooted. Install SuperSU now?..."
I choose to install and that's when my problem started. I was stuck at the htc loading screen. The following thread seemed like it would help, but since I installed the TWRP recovery 'm not sure where to find where to erase the cache and side load ROM for one.
http://forum.xda-developers.com/showthread.php?t=2280230
I may have a learned a lesson, but still don't want to give up on taking a stab at having a rooted phone. I'd like to get better at it, so thanks for any and all advice.
Also sorry if the question sounds a little incoherent, I'm kinda tired and frustrated at the moment.
Click to expand...
Click to collapse
Here are the installation instructions for SlimRoms:
- Download latest SlimRoms and latest gapps and put them on your sd card
- Download latest TWRP recovery put in your adb/fastboot folder and boot into Recovery
- Flash TWRP in bootloader/FASTBOOT USB:
Code:
fastboot flash recovery <recovery_name.img>
fastboot erase cache
fastboot reboot-recovery
- In TWRP choose Advanced in Wipe Section and wipe dalvik, cache, system and data
- Flash ROM
- Flash Gapps
- Reboot, setup and enjoy.
majmoz said:
Here are the installation instructions for SlimRoms:
- Download latest SlimRoms and latest gapps and put them on your sd card
- Download latestTWRP recovery put in your adb/fastboot folder and boot into Recovery
- Flash TWRP in bootloader/FASTBOOT USB:
Code:
fastboot flash recovery <recovery_name.img>
fastboot erase cache
fastboot reboot-recovery
- In TWRP choose Advanced in Wipe Section and wipe dalvik, cache, system and data
- Flash ROM
- Flash Gapps
- Reboot, setup and enjoy.
Click to expand...
Click to collapse
Thanks much man. I tried this but kept getting this error in trying to wipe dalvik and cache. So after several different attempts (rebooting, recovery, etc.) I decided to just format data. I then used the adb sideload feature in TWRP to try putting the zips back onto the sd card. Several frustrating failed attempts due to CP continuously telling me device not found. Finally, after making sure not to let my phone rest, I was able to get both on and then rebooted in TWRP. Ta da! I finally got past the HTC Logo screen and saw the sweet SlimKat logo. Now I'm just waiting for it to connect to service.
I never thought I'd be able to comprehend all this as I just started learning today, but thanks to you folks at XDA I'm (hopefully) starting to benefit. Hope to keep learning from you all. Thanks again.
I'm what you'd call a super noob at this stuff and I've got my poor little SP in a crazy bootloop... I've tried LITERALLY EVERYTHING the internet has told me to try; wiping every cache out there, flashing custom roms, stock roms, you name it. It began when I just got CWM (don't ask me why it happened then, I have no clue why) and this is even BEFORE I put a ROM on! (I was all ready to put a ROM after getting CWM but bootloop happened).
Note: I have CWM recovery, I think I have lost my stock recovery, if I try some ROMS (ex. CM 12) they give me this error 7, once I found certain ROMS (PACMAN ROM, unofficial stock ROM) that would flash and install, they did but still left me with a bootloop, I have tried wiping so many caches it's not even funny, I've tried flashing the original firmware, nothing works... so I'm here for help.
I have looked at every google link and every method possible in trying to fix this thing! I really can't afford a new phone and I just love this one too much... please help!
farahtasnim said:
I'm what you'd call a super noob at this stuff and I've got my poor little SP in a crazy bootloop... I've tried LITERALLY EVERYTHING the internet has told me to try; wiping every cache out there, flashing custom roms, stock roms, you name it. It began when I just got CWM (don't ask me why it happened then, I have no clue why) and this is even BEFORE I put a ROM on! (I was all ready to put a ROM after getting CWM but bootloop happened).
Note: I have CWM recovery, I think I have lost my stock recovery, if I try some ROMS (ex. CM 12) they give me this error 7, once I found certain ROMS (PACMAN ROM, unofficial stock ROM) that would flash and install, they did but still left me with a bootloop, I have tried wiping so many caches it's not even funny, I've tried flashing the original firmware, nothing works... so I'm here for help.
I have looked at every google link and every method possible in trying to fix this thing! I really can't afford a new phone and I just love this one too much... please help!
Click to expand...
Click to collapse
please state your current bootloader status. Is it unlocked or still locked?
TechnoSparks said:
please state your current bootloader status. Is it unlocked or still locked?
Click to expand...
Click to collapse
I have unlocked my bootloader. Thank you for replying!
farahtasnim said:
I have unlocked my bootloader. Thank you for replying!
Click to expand...
Click to collapse
Splendid! Knowing that your BL state is unlocked, this will make the whole process A LOT easier!
http://forum.xda-developers.com/xperia-sp/development/ubl-twrp-f2fs-support-xperia-sp-huashan-t3150230
Please go to the above link to get TWRP. Also, please keep in mind that TWRP is now the only still supported recovery around. CWM and PhilZ are both really outdated and no longer maintained due to the introduction of Cyanogen Recovery which is very minimal in features.
Once you get yourself the download, extract the files from the zip and get the twrp.img file. We will need this to flash into the boot partition of Xperia SP, granting you a direct boot into recovery once it is flashed. Please then copy the original zip to your sd card, as we will be flashing the original zip via TWRP later to give you access to TWRP in the future.
Using your preferred tool, flash the twrp.img file into the boot partition.
Connect your Xperia SP via fastboot. Make sure SP is shut down, hold volume up key and connect the SP with your computer.
If you're using a fastboot tool via command prompt, the command would be
fastboot flash boot twrp.img
If you're using flashtool, hit the lightning icon in the toolbar, select fastboot mode. Then select "Select kernel to flash". Make sure the file type is "img" else you won't able to find your TWRP img file. Navigate to mentioned img file and select it.
Afterwards, when flashing complete, you may insert sdcard and start the device. It will boot directly into TWRP as we flashed a recovery to the boot partition.
Clean wipe data, cache, dalvik cache, system. You may leave internal storage.
Flash the ROM zip you acquired (make sure file integrity is checked beforehand!) then the TWRP zip earlier. Flashing the TWRP zip grants you a persisting recovery, as explained in the linked thread.
You may now reboot and enjoy
this is what i've done.
lenovo k3 note with twrp 2.8.7.2_K3_CUOCO92 and rom K3_LOLLIPOP_5.0_ROW_v1.12
i wanted to install one of the latest nougat rom. so i downloaded a twrp 3.1.1.1 made for the k3 note. i flashed the image from my old twrp and replaced choosing the RECOVERY partition.
Flashed ok, i tested a rom, AospExtended-v4.4-aio_otfp-20170708-1051- i flashed it and it worked.
OK BUT.............. i did not wipe the data partition because i received AN ERROR. the new nougat rom was ok but it was a superdirty flash with all the old apps that were crashing. what to do?
i enter into twrp, i REMEMBER that i had the data partition ENCRYPTED so i format it and after doing this i was able to do every wipe i want, included data.
OH PERFECT...... THIS IS WHAT I THOUGHT. i made a full wipe of the rom wiping 4 thinkg : data , internal storage, cache and dalvik cache.
reboot and BOOM. black screen. i press 3 or times the power button and the creen goes on... i am into twrp. from this moment i never returned to see my SYSTEM!
i tested other roms, same problem. i thought it was a twrp problem.... so i installed from the twrp an IMAGE of other twrp... i tested 2 or 3 other twrps specific for my phone k3 note.
I HAD LITTLE BENEFITS with another one.... just because when i press to reboot into system... the phone reboots into twrp AND I CAN SEE IT because the screen is ON, whilst with the "latest" twrp i found...... despites the flashing procedure was ALL CORRECT without errors, at the reboot i always entered into twrp...... BUT INTO A BLACK SCREEN MODE, like if the screen was on...touch enabled, but OFF backligt, and the only way to revive it it is to press power 2 or 3 times, to see the home of the twrp.
i've also found that on MOUNT.......... i always see SYSTEM unflagged, ok i flag it, reboot into system, actually reboot into twrp and system is UNflagged, i try the same thing ALSO flagging READ ONLY...... , idem reboot, twrp.
SEEMS THAT i cannot boot to system anymore. but..... if the twrp was fault, why for the first time let me flash the phone? i really entered into the nougat rom! i found all my old apps and files, but of course it was a DIRTY FLASH, i just wanted to make some wipes.....re flashi the rom.... but oddly i missed the possibility to return anymore to the system.
what could i do at the moment?
how to flash a original image? how to see if this recovery is ok? i donkt 'know where to find my answers......
ah last thing, while into the recovery i was always able to transfer files from pc to phone, but from minutes i am NO MORE ABLE to see the internal memory of the phone.
my computer does not see anything!!! so i am fukked i think....... i did not make anything different.
i only made a lot of wipes... a lot of flashing a lot of testin into recovery. i was able to see it from my pc and put new files through pc. now NO.
solved. i flashed with flash tools an old original firmware android 5.0, then i flased latest twrp with flashtool.... and then flashed the zip of a custom rom.
BL
if u have backup then restore ur stock version or reeboot??
Hello guys
I tried to flash my K20 Pro today with a custom ROM and somehow ended up with a bootloop (I wiped everything pretty much, Data, Vendor (which was probably the mistake, dunno), System, caches, all that). So, I went ahead and flashed the stock ROM through the MiFlash tool, and I can use the stock ROM. After that, I flash TWRP and repeat the process. Wipe, flash, reboot. And I get the bootloop.
Bootloader is unlocked as should be.
Anyone know what's causing this and what I can do to fix it?
Thanks in advance
EDIT: Just noticed that after this last attempt where it bootlooped into the recovery, everything's encrypted, don't know if that helps but it's there.
Format data
camp70 said:
Format data
Click to expand...
Click to collapse
Had it running on the fastboot MIUI ROM, flashed TWRP, wiped caches, system and data. Then data again. Storage shows up in 3 "partitions" and I can't paste files to them. When I try to reboot back to TWRP it just goes to fastboot and after reflashing TWRP, it still will boot to fastboot instead of the just flashed recovery. Using fastboot oem reboot-recovery if that helps.
After the wipe, doing fastboot boot twrp.img will fire up a "Failed to load/authenticate boot image: Load Error"
Format is not the same that wipe
From MIUI
Install TWRP.
Boot TWRP.
Go to wipe menu and factory reset.
Return to wipe menu and select format data.
At no point do you need to go into the advanced wipe menu.
Return to the main menu.
Go to boot menu.
Select (re)boot recovery to allow TWRP to correctly mount the newly formatted data partition.
Copy across the files you want to flash, then flash them.
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