Related
Hello, I'm kind of new at this (this is my first post) so be gentle
So, the last few days I've been trying to install a new rom on my phone (Redmi Note 4X) and the problems started with the model. I only seem to find Redmi Note 4 roms, and as I've come to find, mine is supposed to be the mido one (correct me if I'm wrong though). I have unlocked the bootloader, I have installed and enabled the fastboot on my phone, so the next step was to install the latest TWRP.
There came more problems; I tried doing this through the app and it just wouln't flash it. So I found a guide on how to root my phone and install a new recovery through adb and I followed it. It didn't work. I couldn't find the right twrp version for my phone. When I finally did realise my phone needed mido, I found the latest from the TWRP website. It wouldn't load through adb again. I found a thread about a fixed mido version, which finally worked for me. But my brother who was helping me, and isn't as much of a noob as I am (he has flashed rom and recoveries many times on his Nexus 5X), decided that I necessarily need the latest twrp if I'm going to flash a new rom, so he flashed the new twrp through the old one, and soft bricked my phone (I think). So I'm searching for a guide to unbrick it. (Which I can't seem to find to work at least).
To conclude;
I have unlocked my bootloader
I have access to the fastboot
I tried to flash a recovery
I failed many times, but I managed it
I flashed the latest twrp and bricked my phone
I don't have access to the recovery
My phone is still on a bootloop
I am not sure about which phone model I have
Help!
Thanks in advance.
1. Just check your phone model on its box. If its Snapdragon version (Mido), then just install it via fastboot. (code: fastboot flash recovery twrp-midoxx.img). If you are success, then try to reboot to recovery (fastboot boot twrpmido-xx.img). After booted, then you just manage to rom.zip you want to install. If you don't have it, then download it before from your PC and push it to your phone. Or just enable Mtp checklis from TWRP n copy that file to your internal phone/sdcard. Wipe all/factory reset except internal storage. Then you dan install rom.zip normally. N reboot. (Note: if you are on MIUI and wanted to always stay on it, just flash the file called lazyflasher.zip. n' wipe cache n art cache only then reboot). Flashing custom recovery on stock MIUI Will manage the device Going to bootloop)
2. If you have mediatek version (nikel), searching the fastboot Rom from miui website and flash it normally via fastboot. (SP Flash tool)
Warning: flash the wrong rom file into wrong phone Will make your device brick. So becarefull n knowing what model/code name you have.
Dyt199412syam said:
1. Just check your phone model on its box. If its Snapdragon version (Mido), then just install it via fastboot. (code: fastboot flash recovery twrp-midoxx.img). If you are success, then try to reboot to recovery (fastboot boot twrpmido-xx.img). After booted, then you just manage to rom.zip you want to install. If you don't have it, then download it before from your PC and push it to your phone. Or just enable Mtp checklis from TWRP n copy that file to your internal phone/sdcard. Wipe all/factory reset except internal storage. Then you dan install rom.zip normally. N reboot. (Note: if you are on MIUI and wanted to always stay on it, just flash the file called lazyflasher.zip. n' wipe cache n art cache only then reboot). Flashing custom recovery on stock MIUI Will manage the device Going to bootloop)
2. If you have mediatek version (nikel), searching the fastboot Rom from miui website and flash it normally via fastboot. (SP Flash tool)
Warning: flash the wrong rom file into wrong phone Will make your device brick. So becarefull n knowing what model/code name you have.
Click to expand...
Click to collapse
Hello and thanks for the reply. I have the snapdragon version, but all I'm asking is how am I supposed to flash the lazyflasher without accessing the recovery? Through adb?
fionik said:
Hello and thanks for the reply. I have the snapdragon version, but all I'm asking is how am I supposed to flash the lazyflasher without accessing the recovery? Through adb?
Click to expand...
Click to collapse
Firstly, enter fastboot mode on your device. Connecting to pc and flashing the twrp for mido. "fastboot flash recovery twrp-mido.img". Then boot to it using " fastboot boot twrp-mido.img". Then you will enter the recovery (twrp) in a second. Copy the lazyflasher into your phone (enable mtp first in Mount option in twrp) that you downloaded from pc. Just flash the lazyflasher.zip and reboot.
And why you don't want to flash lazyflasher when it very easy to flash it using recovery twrp? adb? You mean android debugging? Actually, you cant flash a .zip file into your system partition except through fastboot mode. However, fastboot mode (in cmd) only recognize a .img file. I just try to tell you the easier method to make your device boot up.
Dyt199412syam said:
Firstly, enter fastboot mode on your device. Connecting to pc and flashing the twrp for mido. "fastboot flash recovery twrp-mido.img". Then boot to it using " fastboot boot twrp-mido.img". Then you will enter the recovery (twrp) in a second. Copy the lazyflasher into your phone (enable mtp first in Mount option in twrp) that you downloaded from pc. Just flash the lazyflasher.zip and reboot.
And why you don't want to flash lazyflasher when it very easy to flash it using recovery twrp? adb? You mean android debugging? Actually, you cant flash a .zip file into your system partition except through fastboot mode. However, fastboot mode (in cmd) only recognize a .img file. I just try to tell you the easier method to make your device boot up.
Click to expand...
Click to collapse
As I said above, I can only access the fastboot, and I get errors in the adb when I try to flash the twrp image.
fionik said:
As I said above, I can only access the fastboot, and I get errors in the adb when I try to flash the twrp image.
Click to expand...
Click to collapse
Share your error please.
Try fastboot boot twrp.img
Ok, I am new to this. My op3 was on oxygen os 5.0.8. I first unlocked my bootloader, then flashed twrp, and through twrp i have flashed Magisk 18.1. Then I cleared data, dalvik and cache and started a reboot. I am now in a bootloop, tried to uninstall Magisk through the uninstaller, but still i am in a bootloop. So please help me with the bootloop or guide me on how to get back to stock rom and recovery.
N1mbus17 said:
Ok, I am new to this. My op3 was on oxygen os 5.0.8.
Click to expand...
Click to collapse
Hello, have you tried flashing the stock boot image from fastboot?
I donno how to flash stock boot image with fastboot, can i flash that img with twrp?
N1mbus17 said:
I donno how to flash stock boot image with fastboot, can i flash that img with twrp?
Click to expand...
Click to collapse
What happens when you place your stock boot image somewhere you can access from TWRP and try?
If you want to try fastboot method:
Download the version of OxygenOS you’re currently on
Extract the contents of the ZIP file from Step 1
Copy/move the boot.img file to the same directory as your ADB/Fastboot tools
Launch a Command Prompt, Terminal or PowerShell in that directory
Boot the OnePlus 3 into Fastboot Mode
Connect the OnePlus 3 to the PC with a USB cable
Type the following into the Command Prompt, Terminal or PowerShell. . .
Code:
fastboot flash boot boot.img
. . .then press Enter on the keyboard
Wait for the boot IMG file to be sent and written
Then press the Power button on the OnePlus 3 to reboot back into Android
adapted from https://www.androidexplained.com/oneplus-5-stock-kernel/
united_we_stand said:
What happens when you place your stock boot image somewhere you can access from TWRP and try?
If you want to try fastboot method:
Download the version of OxygenOS you’re currently on
Extract the contents of the ZIP file from Step 1
Copy/move the boot.img file to the same directory as your ADB/Fastboot tools
Launch a Command Prompt, Terminal or PowerShell in that directory
Boot the OnePlus 3 into Fastboot Mode
Connect the OnePlus 3 to the PC with a USB cable
Type the following into the Command Prompt, Terminal or PowerShell. . .
Code:
fastboot flash boot boot.img
. . .then press Enter on the keyboard
Wait for the boot IMG file to be sent and written
Then press the Power button on the OnePlus 3 to reboot back into Android
adapted from Link
Click to expand...
Click to collapse
Ok I will try this method, but what will happen to twrp if I flash through fastboot, will it get removed and replaced by stock recovery?
N1mbus17 said:
Ok I will try this method, but what will happen to twrp if I flash through fastboot, will it get removed and replaced by stock recovery?
Click to expand...
Click to collapse
Hi! in the following command
Code:
fastboot flash boot boot.img
fastboot is the tool
flash is the operation
boot is the destination partition
and boot.img is the source
so to answer your question, TWRP should remain unaffected, as it should reside on your recovery partition
united_we_stand said:
Hi! in the following command
Code:
fastboot flash boot boot.img
fastboot is the tool
flash is the operation
boot is the destination partition
and boot.img is the source
so to answer your question, TWRP should remain unaffected, as it should reside on your recovery partition
Click to expand...
Click to collapse
Ok i did a wipe on cache, dalvik and system, flashed the official os zip file with TWRP and i am still stuck in a bootloop. I haven't tried your method yet where you flash the boot.img as it's just 15mb while the zip file is 1.5gb. What am i missing here? Is my TWRP recovery installing the os zip file correctly? I am stuck.
This is what i have done till now:
Unlocked my bootloader
Flashed official TWRP (twrp-3.2.3-1)
Then cleared data, cache, dalvik and flashed Magisk
Rebooted and got stuck in a bootloop
Used magisk uninstaller but didn't work
Downloaded official Oxygen OS 5.0.8 and then went to twrp, wiped dalvik, cache, data, system and then flashed the zip file.
Rebooted and still stuck in a bootloop
I am now scared that this phone won't startup. Please provide a solution.
Ok, i have followed the mega unbrick guide for oneplus 3 and it has finally come out of the bootloop, it's now updating to the latest oxygen os. Sadly i donno what went wrong the 1st time i tried to root with Magisk, maybe the oreo on the op3 doesn't support magisk. If it's possible can you guide me into rooting the phone with magisk, as most of the tutorials are old and for marshmallow rom and recovery. Thanks.
So it's my second attempt to flash lineage os (unofficial) on my Realme XT. First time I was a little careless and bricked my device (had to go to the service center for that). Second time I took all the precautions still I'm having almost same problem, but this time its not yet bricked.
I unlocked the bootloader. It went fine.
Flashed unofficial TWRP and booted back to stock os.
When I tried booting to TWRP again I realized it was reset back to stock recovery. So I flashed it again and made backup of all the partitions (stupidly on internal storage). Booted back to system to check that backup is showing on internal storage. Again booted to TWRP and wiped everything except internal storage, flashed lineage and gapps. Wiped dalvik/cache rebooted to system. I was greeted with system partition destroyed error screen.
I flashed vbmeta.img via fastboot, the error was gone but still i was not able to boot to lineage. (I directly flashed vbmeta.img via fastboot. Didn't use the "fastboot --disable-verity --disable-verification" command.)
Now I'm having a different kind of problem.
I can boot into TWRP but I can not boot to system (lineage os). Can't go back to stock as well because the internal storage is encrypted i think (all the folders have random names). After flashing vbmeta.img (via fastboot) now I am not able to connect my phone via fastboot.
Without fastboot TWRP backup is the only option for me to get it back in a working state. If anyone reading this has stock color os with TWRP, It would be great help if you could give me a TWRP backup of system.
Also, I would ilke to know where I messed up while unlocking/flashing, so that I can avoid this in the future.
Okay I managed connect it via fastboot again and flashed the stock fastboot image but it didn't help. I'm still stuck at fastboot mode and can boot to TWRP as well but not to system.
While flashing system.img and vendor.img i'm getting error "Invalid sparse file format at header magi".
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
naushad.016 said:
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
Click to expand...
Click to collapse
There is a flashable twrp stock rom.. in guides section. Flash it in twrp.
Thanks I'll try that!
naushad.016 said:
Okay I managed connect it via fastboot again and flashed the stock fastboot image but it didn't help. I'm still stuck at fastboot mode and can boot to TWRP as well but not to system.
While flashing system.img and vendor.img i'm getting error "Invalid sparse file format at header magi".
Click to expand...
Click to collapse
How you managed to get fastboot ?
naushad.016 said:
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
Click to expand...
Click to collapse
You cannot flash the StockRomXYZ.ozip file directly via TWRP or OrangeFox recovery but if you want to flash COLOR OS then use this link - https://forum.xda-developers.com/realme-xt/how-to/official-ota-update-rmx1921ex11-11-26-t3993041 to download and flash directly otherwise convert the .ozip file into .zip file before flashing. Try the steps mentioned in the link to convert - https://forum.xda-developers.com/realme-2-pro/how-to/convert-ozip-to-zip-installing-stock-t4065277 . After conversion, copy the .zip into storage and always use the Clean Flash method to flash the firmware.
Hope you got it.
Hello dear people !! ^^
Since we have in a short time Android 10
We don't have recovery for it.. Sadly enough but..
I found this on a chinese forum and make a guide of it.
I don't own the Xperia 1.. Not yet but next week i have one,
So i hope all you people understand this guide because i
explained it as far i can do it.
----------------------
.. Requirements ..
Unlocked bootloader
Xperia 1 Or 5
Android 10
Knowledge howto flash
----------------------
Important !!: rename your patched boot.img what you did
with magisk to kernel.img in put it in this zip Here
1: Remember to back up all your data
2: Make a clean install of the firmware,
!! don't boot after flashing !!
3: Turn the phone into fastboot mode
and connect and type this command in cmd window:
fastboot flash boot twrp-xperia1.img
Here the fastboot twrp file
4: fastboot this command of vbmeta:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Here the vbmeta file
5: Press and hold the volume down and power at the same time,
release the powerbutton but keep
pressing volume down button till you enter twrp.
6: Copy the 3 zips:
The boot.zip where your own kernel.img is inside
what you did at the beginnig of these steps
twrp-Xperia1-3.3.x.zip: Here
Magisk-v20.1.zip: Here
to the phone storage, and flash in twrp
7: Start it up and done
Note: If you encountered
damaged internal storage, format internal memory in twrp
and all went just fine.
... Credits ...
M-Rom
Res
This doesn't lead to success with an Xperia 5. Once you try to boot into TWRP at step 5, you got a note that the device is corrupt and will shut down in 5 seconds.
Thanks ASap people try this I will install and try it! Know bug? Is this still in very testing version? For the moment I don't want to touch my device.
The clean install is necessary? Any incompatibilities with some magisk modules? Im currently using: smali patcher, taichi, youtube vanced
Why isn't there a Thread in the Xperia 5 Forums? Just found this out of Luck...
Instructions are also bit confusing... Where is the vbmeta.img from? Google? And why do i need a boot.img if we have already a TWRP boot.img? Will the one boot.img not replace the other?
Flashing a new Firmware makes also no sense if you just do "fastboot -w" to erase all Userdata. (If coming from a clean Firmware like i do, or You do right after unlocking Your Device)
Edit: So in a nutshell
-We do boot up the twrp boot.img to be able to flash Zips!?
-We do flash vbmeta to unsecure our booting!?
-We do flash our own boot.img with the Zip that the Device can work right!?
-We do flash the TWRP Zip which edits our Ramdisks to add TWRP
-We do flash Magisk (Optional!?) for only Root? Or also needed Kernel changes!?
Would be nice to also make links to XperiFirm and UnSin to get the boot images...
You could also edit the boot.zip script for "magisk_patched.img" so users don't have to rename it
Just want to support that btw. Thanks for Your work anyways!
---------- Post added at 15:47 ---------- Previous post was at 15:07 ----------
Xperia 5 booted well into TWRP but it freezes everytime i start a flash or wipe. Got the storage to work with fastboot -w after flashing the twrp and vbmeta images. Adb Sideload does also not work. Looking forward to a working version!
TWRP unable to flash zips
Well, the title says it all. I can flash the twrp image, but it freezes when flashing zips or starting sideload. I'm using a J9110. I understand you're not supporting here, but just in case you had some tips. Oh and by the way, hoi vanuit Leiden
EDIT: Found the fix: don't change the language to english before opening twrp, and it will flash just fine!
xperia 5 fix plz
I've installed this, it work but boot in chinese and cant load the usb mtp driver on my pc, I cant move the boot.zip to flash, had it put on sd card, cant find the sd card on this crappy twrp, for me is a no. I'd just stick with patched boot until something better will work.
mtp should work if you follow every instruction and boot twrp in chinese.
Having the same issue as others... it appears as though the internal storage is encrypted, but I have no lock screen enabled in the ROM. No Passwords or Fingerprint either. Tried wiping data from within TWRP froze the system. Performed a wipe from within ROM, and now the ROM shows internal data folders as though they're encrypted. Need a pinch of help here.
This method has problem if 55.1.A.3.149 is flashed. The "Start" screen freeze with no touchscreen function on reboot after the procedures completed.
Is there any update to this?
Hopefully with 3.4 will bring a more stable twrp. It includes changes for devices updated to Android 10
I hope can teach how to get your patched boot.img
It's not too much complex to make it work
download firmware from xperiFirm
unsign the boot.sin to get boot.img for your xperia 1
flash the twrp.img to your boot slot_a/b
boot into twrp
install the boot.img, twrp.zip, magisk.zip
now everything works
benben233 said:
I hope can teach how to get your patched boot.img
Click to expand...
Click to collapse
It's not too hard to get one
Get the origin boot.img from xperiFirm, twrp.zip
boot into any twrp on any device
backup your own boot paritition
install the boot.img, twrp one by one
then backup the boot partition, you get the patched-boot.img
Tenhow.XDA said:
download firmware from xperiFirm
unsign the boot.sin to get boot.img for your xperia 1
flash the twrp.img to your boot slot_a/b
boot into twrp
install the boot.img, twrp.zip, magisk.zip
now everything works
Click to expand...
Click to collapse
On latest android 10 and fw .28 it works ? @Tenhow.XDA
Any sign of Android 11 TWRP for Xperia 1?
MrMmmkay said:
Any sign of Android 11 TWRP for Xperia 1?
Click to expand...
Click to collapse
No
Hi, I'm having some issues trying to install the newest update of A10.
I was on A9 with unlocked bootloader, root and twrp of recovery.
I first tried to install the .rar image via recovery but I couldn't find in the memory, but I already wiped system vendor and data.
So when I rebooted to try if the file was there or not, there was no recovery anymore.
Now I'm trying to flash the newest rom via fastboot but through the flash_all.bat it gives me fastboot tz_a error, so I'm trying to install a recovery through fastboot using this guide https://forum.xda-developers.com/mi-a3/how-to/basic-guide-to-flash-recovery-rom-via-t3989603 but of course it doesn't work and when I reboot it doesn't enter the recovery but always in fastboot (even tho I press the + button).
What should I do now? Is there anyway to erase everything and install a clean OS from 0 just from fastboot? (Without the flash_all or miflash because it doesn't work)
P.S. I don't care about the data, I've done a backup of all my important files before
Thanks for the help
Sapper Morton said:
First, you have to understand what you did. You wiped your system and vendor image, and didn't installed a newer one afterwards, you didn't wiped your recovery (it's inside boot partition).
Further, .rar files will not be flashed through TWRP, .zip must be used instead, with proper format, there must be a compatible flash script inside.
You can't access your recovery, just because you wiped system; inside your bootloader there's a component responsible to manage the slots, bootctl and by default if it detects a corrupted or invalid system partition, it will always boot onto bootloader mode.
As for the tz_a error, you must unlock critical partitions flashing, just because, tz is a critical partition, thus, run in Fastboot:
Code:
fastboot flashing unlock_critical
If you want to know your current state, use:
Code:
fastboot oem device-info
Your current slot is blocked by bootctl, but this doesn't mean your inactive is too, so, use:
Code:
fastboot set_active other
And reboot into TWRP again, that is, if you do have it installed in your inactive slot.
Fastboot/ADB and other tools, you will find it in here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
If you want to restore using recovery firmware, please do the favor, and read the post below:
https://forum.xda-developers.com/showpost.php?p=82595733&postcount=379
Click to expand...
Click to collapse
Thanks for the help but I managed to get into the recovery and install the rom via fastboot, the thing I was missing was a recovery working for Android10 (even though I remember recovery doesn't have nothing to do witg the installed OS), so I managed to install the recovery and root, and everything went fine after a few tries between various guides. Probably my partitions now are all messed up, but if I boot normally it goes into system (slot A), if I boot into recovery it goes into twrp and also works fastboot. Probably I also installed the OS on slot b, but I don't care as long the first partition works well