Related
Hi all,
A while ago I rooted my Z3C and flashed a custom ROM. Today I wanted to update to a new version and I messed up very bad. I always was a die-hard flasher so I did things as always. Downloaded the ROM as usual, wiping as usual (I always wipe everything). Tried to install the new ROM and got the message that it can't mount /system. Looked this up and it seems that Sony got a kernel protection for /system and /cache, which I didn't know.
But now the actual problem. For some reason my system partition did got wiped, as result I can only acces recovery. But I still can't flash ROMs due the kernel protection. I tried to sideload the RICDefeat to disable the protection but this didn't work. Also tried to go back to stock with the EMMA tool but this didn't work either as the application doesn't detect the phone.
Anyone has a good idea what I can do now? I didn't backup my system partition, but I guess it doesn't matter as I don't have R/W for system.
So I assume you didn't unlock your bootloader before you tried flashing a custom ROM? Which Recovery do you use?
If you hold volume up while the phone boots up (enter fastboot), does it detect your phone there?
Did you install the proper z3c driver and does your device show up in device manager (maybe as unknown?) ?
This guide might help even if you don't want to root but flash a fresh firmware: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
MyPictures said:
So I assume you didn't unlock your bootloader before you tried flashing a custom ROM? Which Recovery do you use?
If you hold volume up while the phone boots up (enter fastboot), does it detect your phone there?
Did you install the proper z3c driver and does your device show up in device manager (maybe as unknown?) ?
This guide might help even if you don't want to root but flash a fresh firmware: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Click to expand...
Click to collapse
Sorry, I should have mentioned this.
Bootloader is unlocked by the Sony website. For recovery i use XZDual, but for some reason I can only acces TWRP.
Fastboot is detectable and all drivers are installed correctly. Normally it wouldn't been a problem, but I also didn't have my system authorized for ADB as I just upgraded to W10.
You could try to flash cyanogenmod over fastboot now and see what happens (hope you backed up your TA partition first). I usually just prepare the flashtool (select image and press flash so it waits for device), then I hold down volume down and plug in the USB cable.
First I used to have some issues because of Windows driver signature enforcing but after disabling that it seemed to be fine.
Ohh and: Does TWRP print a log when you try to mount /system ? It might help to flash a kernel in fastboot then (could extract the cyanogenmod one from the zip [boot.img]), not too sure since I havent used a Sony Frimware for months now.
MyPictures said:
You could try to flash cyanogenmod over fastboot now and see what happens (hope you backed up your TA partition first). I usually just prepare the flashtool (select image and press flash so it waits for device), then I hold down volume down and plug in the USB cable.
First I used to have some issues because of Windows driver signature enforcing but after disabling that it seemed to be fine.
Ohh and: Does TWRP print a log when you try to mount /system ? It might help to flash a kernel in fastboot then (could extract the cyanogenmod one from the zip [boot.img]), not too sure since I havent used a Sony Frimware for months now.
Click to expand...
Click to collapse
I am trying now as I typ this. The only log I get from TWRP is that it can't mount system.
@ edit: Didn't help. Still getting message that system isn't readable/writeable.
Braindamage1989 said:
I am trying now as I typ this. The only log I get from TWRP is that it can't mount system.
@ edit: Didn't help. Still getting message that system isn't readable/writeable.
Click to expand...
Click to collapse
Did you try to go in TWRP and repair/change /system ? Also make sure you dont have the rm -rf option selected instead of properly formatting.
TWRP needed
Many people still have problems with bringing the device back to the ROM and Recovery stock, so once and for all I decided to make a simple post guide:
This is the backup.
https://mega.nz/#F!dQJAAJiT!9GCaOUGCjiahuNBkEbKIZQ
ONLY FOR P8 LITE 2017 [PRA-LX1C55] (but you can try with another branded or unbranded same device)
I do not feel responsible for any problems.
1: Put the ''BACKUPS'' folder in a new folder called ''TWRP'' in external_sd then reboot to TWRP.
2: In TWRP; Wipe cache and Dalvik cache, data and system. (Also Vendor if it was previously flashed)
3: Click on the restore option and select the backup; swipe and wait. When the installation finishes in my case, if an error appears you do not have to worry, you only need this backup to restore the original ROM and recovery after with eRecovery.
4: Reboot the device and when it shows the ''initial unlocked bootloader screen'', press vol +; it boot on eRecovery.
5: In eRecovery, if it shows erase data click on it firstly, if not, click directly on download and install fw and rom on the first option.
6: Insert your wifi password, and wait for the download of rom and recovery . An Italian TIM Branded c55b105 will be downloaded .
Installation performs automatic recovery, and twrp recovery will be overwritten.
Do not worry if you restart a couple of times, if all goes well you will have to wait for the device to boot and everything will be restored, if you want, you can also relock the bootloader.
I hope I can solve your problem:laugh::laugh::laugh:.
you are awesome!
you saved me! thanks!!!!!!:good::fingers-crossed:
SandXFX said:
you saved me! thanks!!!!!!:good::fingers-crossed:
Click to expand...
Click to collapse
Fr0nK said:
Click to expand...
Click to collapse
can someone give me a stock bakcup for pra-lx2
dazokevin28 said:
can someone give me a stock bakcup for pra-lx2
Click to expand...
Click to collapse
None here has lx2 version sorry , but you can also try this guide to back stock fw (without download lx1 fw obv)
GreenScreen problem
Hello, tried to perform that solution, but encounter a major problem.
In 2nd point I did wiped the Vendor as well (cause was using the haky's LinOS 14.1 previously);
then restored files from your backup (get warning "createTarFork() process ended with ERROR=255" at the end), and reboot.
Then some wierd stuff shows up - instead of any Huawei logo or unlocked bootload screen - I've got GreenScreen witch 2 rectangles (Blue&Red).
But it enters eRecovery; so yet without any worries tried to start recovery over there - "Getting package info failed" made that impossible.
And now I'm bricked a little bit - cause can not enter TWRP, can not flash the TWRP again, only thing that is possible - the eRecovery mode.
Anyone have any ideas how ot unbrick it?
<!-- Edit -->
Sorry for troubles, as just realized the steps made my phone locked again, so "fastboot oen unlock [...]" it again, and now everything is like before.
<!-- Edit2 -->
Already installed SlimOS and everything seems just fine. Therefore the spectacular GreenScreen still showing up every rebooting, even though I did wiped eveything (every single position) in TWRP since then. x)
Would be greatfull for any informations about this phenomenon.
Sixter said:
Hello, tried to perform that solution, but encounter a major problem.
In 2nd point I did wiped the Vendor as well (cause was using the haky's LinOS 14.1 previously);
then restored files from your backup (get warning "createTarFork() process ended with ERROR=255" at the end), and reboot.
Then some wierd stuff shows up - instead of any Huawei logo or unlocked bootload screen - I've got GreenScreen witch 2 rectangles (Blue&Red).
But it enters eRecovery; so yet without any worries tried to start recovery over there - "Getting package info failed" made that impossible.
And now I'm bricked a little bit - cause can not enter TWRP, can not flash the TWRP again, only thing that is possible - the eRecovery mode.
Anyone have any ideas how ot unbrick it?
<!-- Edit -->
Sorry for troubles, as just realized the steps made my phone locked again, so "fastboot oen unlock [...]" it again, and now everything is like before.
<!-- Edit2 -->
Already installed SlimOS and everything seems just fine. Therefore the spectacular GreenScreen still showing up every rebooting, even though I did wiped eveything (every single position) in TWRP since then. x)
Would be greatfull for any informations about this phenomenon.
Click to expand...
Click to collapse
unfortunately I have not encountered this problem
to restore the phone check here
https://forum.xda-developers.com/p8...uide-unbrick-huawei-p8-lite-2017-pra-t3713574
regards
Plz upload as a single zip, not a whole folder on mega .
Can someone give me a stock back up for PRA-LX1C432B### Single Sim please and thanks
Fr0nk0 said:
TWRP needed
Many people still have problems with bringing the device back to the ROM and Recovery stock, so once and for all I decided to make a simple post guide:
This is the backup.
https://mega.nz/#F!dQJAAJiT!9GCaOUGCjiahuNBkEbKIZQ
ONLY FOR P8 LITE 2017 [PRA-LX1C55] (but you can try with another branded or unbranded same device)
I do not feel responsible for any problems.
1: Put the ''BACKUPS'' folder in a new folder called ''TWRP'' in external_sd then reboot to TWRP.
2: In TWRP; Wipe cache and Dalvik cache, data and system. (Also Vendor if it was previously flashed)
3: Click on the restore option and select the backup; swipe and wait. When the installation finishes in my case, if an error appears you do not have to worry, you only need this backup to restore the original ROM and recovery after with eRecovery.
4: Reboot the device and when it shows the ''initial unlocked bootloader screen'', press vol +; it boot on eRecovery.
5: In eRecovery, if it shows erase data click on it firstly, if not, click directly on download and install fw and rom on the first option.
6: Insert your wifi password, and wait for the download of rom and recovery . An Italian TIM Branded c55b105 will be downloaded .
Installation performs automatic recovery, and twrp recovery will be overwritten.
Do not worry if you restart a couple of times, if all goes well you will have to wait for the device to boot and everything will be restored, if you want, you can also relock the bootloader.
I hope I can solve your problem:laugh::laugh::laugh:.
Click to expand...
Click to collapse
thanks for your tread it's very helpfully but i flashed the oeminfo only without restore everything just the oeminfo backup i changed in img mode and i flashed with twrp and done. I reboot to eRecovery mode, connect to WiFi and done i installed the firmware pra-lx1c55b105 with success TIM firmware
thanks for your great job ?
jalel25 said:
thanks for your tread it's very helpfully but i flashed the oeminfo only without restore everything just the oeminfo backup i changed in img mode and i flashed with twrp and done. I reboot to eRecovery mode, connect to WiFi and done i installed the firmware pra-lx1c55b105 with success TIM firmware
thanks for your great job
Click to expand...
Click to collapse
Nice to hear. :fingers-crossed:
I am on stock rom, rooted with magisk, and I cannot seem to get this phone decrypted. Every time I try to format data in twrp, I get an error, and I get stuck in a bootloop to recovery. Is there a step(s) I am missing here? I've tried looking through the forum but all I've seen are the same instructions on formatting data.
Use Advanced Wipe, select all except sdcard. Then flash any custom rom you like. Flash Magisk too. Reboot. After reboot try running your custom rom os for a few. Then go back to twrp, do it again advanced wipe except sdcard. Reboot. See if it decrypt now.
Note: Make sure you backup everything in it first before doing so. Goodluck
Sent from my XT1805 using Tapatalk
jdesignz said:
Use Advanced Wipe, select all except sdcard. Then flash any custom rom you like. Flash Magisk too. Reboot. After reboot try running your custom rom os for a few. Then go back to twrp, do it again advanced wipe except sdcard. Reboot. See if it decrypt now.
Note: Make sure you backup everything in it first before doing so. Goodluck
Sent from my XT1805 using Tapatalk
Click to expand...
Click to collapse
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
L4ndon said:
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
Click to expand...
Click to collapse
UPDATE:
I tried to redo the process again, just to verify the process, and I am still having the same network issues. I have 3g every once in a while, but its iffy and I no longer have LTE.
L4ndon said:
Well, I tried it, it booted, but it doesnt detect my sim card, and I have no service. I am still not decrypted as well, I am afraid to format data because of the fact that in the past it has put me into a recovery bootloop.
Click to expand...
Click to collapse
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
IT WORKED! Thank you so much. This was the post I needed, it really helps when everything is put in a step by step format, I am not the best when it comes to this stuff, the only reason I wanted a custom rom was to be able to use wifi tether, being on sprint makes that hard. But now that i have the first step down hopefully everything else goes this smooth. Thank you so much again!
Well, as long as you have done backup with twrp you have nothing to worry about.
Sent from my XT1805 using Tapatalk
L4ndon said:
IT WORKED! Thank you so much. This was the post I needed, it really helps when everything is put in a step by step format, I am not the best when it comes to this stuff, the only reason I wanted a custom rom was to be able to use wifi tether, being on sprint makes that hard. But now that i have the first step down hopefully everything else goes this smooth. Thank you so much again!
Click to expand...
Click to collapse
Doing things the right way always works! Trouble is finding that right way (heed my warning about bad info in these threads - there is a lot of it - as you found out). Just so happens I also know how to splain things to users, I've done it for something like 25+ years (yeah, I am old - make that experienced). Tethering - used to be ya add a build.prop entry to allow it, but that was many years ago and most of not all enable it by default now.
Anyways, enjoy the ride. It may be a little bumpy, but it's the bumps that keep ya awake!
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
THX for that, got stuck in recovery process (loop).
I followed your instructions, but need of stock recovery.
My Path :
Backup DATA (w/o /media/)
Manually Backup Media with TWRP to Ext.SD
FORMAT /Data (use the DATA Button in TWRP), in my case it showed Errors, i ignored it and did it once again - this time it worked.
flashed Magisk
ended up in Recovery Loop - flashed stock recov. via FASTBOOT, reboot
a rainbow lightning circle turned up, said " DELETING", device rebooted by itself.
Now the Phone boots to Android, shut it down, restart with PWR BUTOON + VOL DOWN pressed to access bootloader and flash twrp again with FASTBOOT ( fastboot flash recovery nameoftheimage.img ENTER).
Now u can restore /DATA TWRP Backup and then the manually part - in my case that worked.
THX!
//EDIT
After first boot, i noticed missing write permissions for most Apps - so i decided to Reset SELinux via TWRP, worked !
te amo hice format data con r15 y al parecer se soluciono todo son lo maximo cauros
Phazmos said:
1 - forget the instructions given by the other kid - all wrong (like a lot, if not most, of the info given in theg5s plus threads.
2 - use twrp r15 - found in the forums, I think 16 is listed but I know 15 works. You must boot to twrp once after installing twrp or it'll get replaced with stock.
3 - you must format data to decrypt. Wiping only removes data - not the encryption
4 - I've never used magisk, but pretty sure it removed the encrypting flags when installed. I use su and no problems with stock - I've done it and know it works.
5 - download stock firmware, to fix booting to recovery you'll need stock recovery, and it's handy to have just in case.
What to do - install above twrp recovery - format data partition - install su - reboot. Done. If it is rebooting to recovery (which it shouldn't as long as you do boot to recovery after installing it) - flash stock recovery, reboot normally, then do the twrp install routine again.
Report back with details. No details - no help.
Click to expand...
Click to collapse
still sim not showing on my device which is xt1804
Never had the problem so can't help.
Hi guys. I tried to see other threads but I haven't fint anything. Probably there is but I'm beginner and I don't understand so much Anyway this is the problem:
model LLD-L31
build number LLD-L31 8.0.0.133(C432)
FPR unlocked
bootloader unloced
I tried to install root(Magisk-v16.4) in my device. So I unlocked bootloader, installed TWPR(Pretorian80 2.3.1) successfully but this error "Failed to unmount '/system'(Device or resource busy)" appeared. So I try to format data by recovery hoping that it could be able to read partitions after that. I couldn't yet flash file.Zip so I tried to upgrade Twpr in latest version installing it in recovey ramdisk.
After that I'm not able anymore to get into twpr cause this error appered:
[Func NO : 11 (recovery image) Error NO : 2 (load failed!)
Now, I fortunatly turn on the phone, using it with no problems. I can enter in fastboot and eRecovery. I tried to swipe data/reset but the same error appears.
Can I fix it easily? Tell me if you have any tips, thank you:good:
scugnizz said:
Hi guys. I tried to see other threads but I haven't fint anything. Probably there is but I'm beginner and I don't understand so much Anyway this is the problem:
model LLD-L31
build number LLD-L31 8.0.0.133(C432)
FPR unlocked
bootloader unloced
I tried to install root(Magisk-v16.4) in my device. So I unlocked bootloader, installed TWPR(Pretorian80 2.3.1) successfully but this error "Failed to unmount '/system'(Device or resource busy)" appeared. So I try to format data by recovery hoping that it could be able to read partitions after that. I couldn't yet flash file.Zip so I tried to upgrade Twpr in latest version installing it in recovey ramdisk.
After that I'm not able anymore to get into twpr cause this error appered:
[Func NO : 11 (recovery image) Error NO : 2 (load failed!)
Now, I fortunatly turn on the phone, using it with no problems. I can enter in fastboot and eRecovery. I tried to swipe data/reset but the same error appears.
Can I fix it easily? Tell me if you have any tips, thank you:good:
Click to expand...
Click to collapse
Hi, Not familiar with that Version of TWRP, can you link please?
Failure to unmount system usually means you have system set as "read only", try to change within twrp (when you get a working version flashed).
You say you tried to update TWRP to latest edition, exactly what edition did you flash?
Anyway eRecovery will rescue the phone back to when first turned on.
Sparkrite said:
Hi, Not familiar with that Version of TWRP, can you link please?
Failure to unmount system usually means you have system set as "read only",try to change within twrp (when you get a working version flashed).
You say you tried to update TWRP to latest edition, exactly what edition did you flash?
Anyway eRecovery will rescue the phone back to when first turned on.
Click to expand...
Click to collapse
Hi man thank you for your answer.
I flashed this versionhttps://dl.twrp.me/surnia/twrp-3.2.3-0-surnia.img.html
,try to change within twrp (when you get a working version flashed).
Click to expand...
Click to collapse
I can't enter anymore within TWPR, only in stock recovery.
What made you flash that version, where does it say its for the H9L ?
Try either of these, I use V.01 :-
https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
Make sure you use the following command "fastboot flash recovery_ramdisk NAME.img"
When flashed, issue "fastboot reboot" while holding down Vol+, when bootloader page blanks immediately remove USB lead and continue to hold Vol+ until TWRP appears.
TWRP may stall for a while on LOGO page, be patient.
What made you flash that version, where does it say its for the H9L ?
Click to expand...
Click to collapse
I'm dumb man that's all:silly:
Anyway it's fixed now, I love you (thanks put, at least).
Failure to unmount system usually means you have system set as "read only",try to change within twrp
Click to expand...
Click to collapse
Last thing if you can..
On mount section the option mount system partition read-only is disactivated but, at opening, error appears in the same way so I don't know how to disable it definitively
Try formatting Data and then reboot to TWRP (recovery).
Man I'm a disaster:crying:
I formatted but I also had the brilliant idea to delete the whole system, without creating any backup by twpr, obviously. So now I have no OS in my device:good:
I had look for stock firmware with Firmware Finder and I have find one whit these files(bottom photo). Which have I to download?
Then I'll probably follow this thread(https://forum.xda-developers.com/9-lite/help/os-installed-t3787136) to continue. Is it right??
At this stage you are probably better off using eRecovery to bring your phone back to full stock.
From off press and hold Vol Up and connect USB, wait for eRecovery and select "Download latest version and recovery".
Needs WiFi.
savior
scugnizz said:
savior
Click to expand...
Click to collapse
Ah Great, good to hear.
Now, go and flash TWRP and Magisk, but follow the instructions EXACTLY !
Hi,
I bought a new phone and thought I would get in to custom ROMs again. Mostly to get rid of bloatware. However, after following multiple guides I'm still no where closer to achieving my goals. The phone is a MI 9.
I found there's a lot of different steps depending on guide but most of the once I've tried does the following:
* Unlock bootloader, working
* Installing twrp via fastboot, working
* Deleting data in twrp, working
* Transfering a rom.zip file (depending on rom), working via usb cable
* Some guides recommends to install disable force Encryption via another zip file transferred from the computer, however, that seems to not be necessary, tried i few times
* Installing rom via twrp, seems to work
* In some guides you then need to remove cache, working
* Rebooting from twrp, working
After these steps I find myself in one of three different cases,
1. Phone is stuck in fastboot, have to reflash it with MIflash and global MIUI rom to get phone to work again
2. Phone in boot loop, logo shows up, phone waits for awhile, phone reboots, logo shows up
3. Phone boots up, logo is shown, phone reboots into twrp
I've also tried both XiaoMiTool and XiaoMiTool V2,
XiaoMiTool seems to write the global ROM to the phone whatever I choose (Have tried Xiaomi.eu and LineageOS 17)
XiaoMiTool V2, fails in second to last step, it wants to remove some cache before the installation in twrp is done.
Things I've not tried:
* Moving file to twrp with adb instead, should not make a difference
* Installing magisk
Now, I'm a bit afraid my phone will get hard bricked, have reinstalled the OS 20 times the last day to test different approaches and steps. Nothing seem to work. Does anyone have a proven method working in 2020?
Another way to go might be to just get rid of the commercials, run a different launcher to get app list and get rid of the bloatware. This is not really what I want but I can live with it.
As you can hear I'm about to just throw in the towel and give up. But I've heard a lot good about the xda forums so I thought it might be worth a try even though I do understand if no one has time or energy to help out a newbie.
Help please!
Edit: I do realize I've accidentally put this under Guides and not Q&A. I find no way of moving it nor deleting the thread so I guess some moderator will have to come help. Sorry for this.
Do you use latest TWRP for Mi9? TWRP from Mauronofrio works fine for me.
When you say "Deleting data in twrp", does this mean you did Format Data (confirm by typing "yes")? Or just wipe?
Poslano z mojega MI 9 z uporabo Tapatalk
mxxt01 is right. You have to format the data partition or else you will run into a bootloop.
I followed the guide here but I did not flash magisk since I don't need root.
Basically what I did was;
1. Unlock bootloader
2. Reboot to load the OS but skip the initial setup
3. Reboot to fastboot/bootloader
4. Flash TWRP (use the latest beta from Mauronofrio)
5. Immediatly press Vol Up + Power button to boot TWRP
6. Sideload the firmware to /tmp/
7. Format the data partition and type yes to continue
8. Factory reset
9. Flash firmware from within TWRP
10. Factory reset again (you can skip this if you don't want to)
11. Reboot
And that is how I did it.
mxxt01 said:
Do you use latest TWRP for Mi9? TWRP from Mauronofrio works fine for me.
When you say "Deleting data in twrp", does this mean you did Format Data (confirm by typing "yes")? Or just wipe?
Poslano z mojega MI 9 z uporabo Tapatalk
Click to expand...
Click to collapse
I have tried both Formatting data, this generally makes all folders have gibberish names and by going to advanced wipe, choosing data, some guides also wants you to delete Dalvik, Cache and System. I have tried both in the same go and one or the other. Does not seem to make a difference. But from the response below I get that it's formatting the data and typing yes that is the way to go(?)
TWRP version 3.3.1-0
sangbuana said:
mxxt01 is right. You have to format the data partition or else you will run into a bootloop.
I followed the guide here but I did not flash magisk since I don't need root.
Basically what I did was;
1. Unlock bootloader
2. Reboot to load the OS but skip the initial setup
3. Reboot to fastboot/bootloader
4. Flash TWRP (use the latest beta from Mauronofrio)
5. Immediatly press Vol Up + Power button to boot TWRP
6. Sideload the firmware to /tmp/
7. Format the data partition and type yes to continue
8. Factory reset
9. Flash firmware from within TWRP
10. Factory reset again (you can skip this if you don't want to)
11. Reboot
And that is how I did it.
Click to expand...
Click to collapse
Could you describe step 6 in more detail please?
This is what I get if I try sideloading my phone:
adb push xiaomi.eu_multi_MI9_V11.0.5.0.QFACNXM_v11-10.zip /tmp/
adb server is out of date. killing...
* daemon started successfully *
I guess it's important to not get the firmware in the SD-card folder since that will be wiped if I format the data, this might be where I fail.
Step 6 is to type adb push rom.zip /tmp/
I renamed the zip file to rom.zip so that I don't typo when typing.
Sent from my MI 9 using Tapatalk
In any case you should flash a current (11.0.6.0 or younger) fastboot ROM (.tgz extention). Recovery ROMs (.zip extention) don't reset the phone as deep as fastboot ROMs do.
After that you'd best flash vbmeta.img before TWRP, see #1 for more details.
Cheers
Toscha
From personal experience of using xiaomi.eu's ROM, I never did install vbmeta.img or dmverity, since that particular rom is based on the official beta Chinese MIUI ROMs, and the latest TWRP from Mauronofrio supports decryption. Not sure about other ROMs though.
Just to be safe, just download the stock fastboot ROM as a backup just in case anything goes wrong. Always remember to NOT lock your bootloader when flashing back to stock, in case your persist partition gets corrupted, you can flash it to recover.
ZevSwe said:
I have tried both Formatting data, this generally makes all folders have gibberish names and by going to advanced wipe, choosing data, some guides also wants you to delete Dalvik, Cache and System. I have tried both in the same go and one or the other. Does not seem to make a difference. But from the response below I get that it's formatting the data and typing yes that is the way to go(?)
TWRP version 3.3.1-0
Could you describe step 6 in more detail please?
This is what I get if I try sideloading my phone:
adb push xiaomi.eu_multi_MI9_V11.0.5.0.QFACNXM_v11-10.zip /tmp/
adb server is out of date. killing...
* daemon started successfully *
I guess it's important to not get the firmware in the SD-card folder since that will be wiped if I format the data, this might be where I fail.
Click to expand...
Click to collapse
Like written by toscha42 you should flash the latest fastboot stock rom (tgz) for your phone first, as after all the attempts you have made your phone is probably kind of ****ed up... Do not lock bootloader.
What I do and it works for me, starting from stock ROM.
1. Unlock bootloader (you already done that)
2. Flash in fastboot latest TWRP for your device (I use Mauronofrio)
3. After flashing disconnect the phone and push VOLUME UP + POWER to enter from fastboot directly to TWRP recovery
4. Format data with yes
5. Reboot to recovery
6. Flash xiaomi.eu custom rom for your device with USB OTG (usb otg is the easiest way I guess as you don't need to move the rom to internal storage)
7. Reboot to recovery
8. Wipe cache and dalvik cache
8. Reboot to system
And that's all.
Poslano z mojega MI 9 z uporabo Tapatalk
toscha42 said:
In any case you should flash a current (11.0.6.0 or younger) fastboot ROM (.tgz extention). Recovery ROMs (.zip extention) don't reset the phone as deep as fastboot ROMs do.
After that you'd best flash vbmeta.img before TWRP, see #1 for more details.
Cheers
Toscha
Click to expand...
Click to collapse
Can't seem to find any fastboot ROMS, neither of xiaomi.eu or LineageOs 17. Where can I find this? https://xiaomi.eu/community/threads/20-1-16.54300/
If I understood correctly vbmeta.img unlockes secure boot. Not sure why that is needed or what problems it might create. Did some googling but found nothing. What is this used for? If it's important, why is it not in any guides I found?
ZevSwe said:
Can't seem to find any fastboot ROMS, neither of xiaomi.eu or LineageOs 17. Where can I find this? https://xiaomi.eu/community/threads/20-1-16.54300/
If I understood correctly vbmeta.img unlockes secure boot. Not sure why that is needed or what problems it might create. Did some googling but found nothing. What is this used for? If it's important, why is it not in any guides I found?
Click to expand...
Click to collapse
Fastboot STOCK Xiaomi ROM.
To be flashed with MiFlash. Do not lock bootloader.
http://c.mi.com/oc/miuidownload/detail?device=1700361
Poslano z mojega MI 9 z uporabo Tapatalk
Fastoot ROMs are only available for official MIUI ROMs and has tgz as their filename extensions. They are flashable only using Mi Flash tools or equivalent. Custom ROMs has zip and they are flashable using recovery.
Correct me if I'm wrong, vbmeta.img is for verified boot. I was running on official MIUI ROM and I wanted to have TWRP recovery, but stock recovery would come back after every reboot. So I flashed a modified version of vbmeta.img available on the web, to disable verified boot, and TWRP would persist in the recovery partition. Have a read on Verified Boot here.
mxxt01 said:
Fastboot STOCK Xiaomi ROM.
To be flashed with MiFlash. Do not lock bootloader.
http://c.mi.com/oc/miuidownload/detail?device=1700361
Poslano z mojega MI 9 z uporabo Tapatalk
Click to expand...
Click to collapse
Hmm okay, but the phone is already working with the stock ROM, my whole idea is to switch to something else. What do you mean with do not lock bootloader?
sangbuana said:
Fastoot ROMs are only available for official MIUI ROMs and has tgz as their filename extensions. They are flashable only using Mi Flash tools or equivalent. Custom ROMs has zip and they are flashable using recovery.
Correct me if I'm wrong, vbmeta.img is for verified boot. I was running on official MIUI ROM and I wanted to have TWRP recovery, but stock recovery would come back after every reboot. So I flashed a modified version of vbmeta.img available on the web, to disable verified boot, and TWRP would persist in the recovery partition. Have a read on Verified Boot here.
Click to expand...
Click to collapse
Right, well I wish to switch to another ROM so installing MIUI Global ROm will not help.
I'm able to install TWRP without touching verfiedboot at all and get it to work even after reboot so that is not a problem. If that is what verifiedboot does I believe I can skip that?
ZevSwe said:
Hmm okay, but the phone is already working with the stock ROM, my whole idea is to switch to something else. What do you mean with do not lock bootloader?
Click to expand...
Click to collapse
than try once again by following my steps in post #8
You can skip flashing vbmeta and just follow mxxt01's steps.
Sent from my MI 9 using Tapatalk
sangbuana said:
You can skip flashing vbmeta and just follow mxxt01's steps.
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
That seems to have made the trick! Thanks so much!
I've been following this thread because I was having the same problems as ZevSwe, multiple attempts at installing roms with no success. I've been using phones/tablets with custom roms for years so I have some experience but not with this device.
I'll be trying the steps in post #8 later today but I have a question about twrp that's buggin me. I have been taking full twrp backups to a usb stick before installing and just reinstalling when the custom rom didn't work but the last few times the reinstall failed at about 98% complete and I've had to reinstall stock from scratch.
Any idea why a twrp backup would fail on reinstall? Is there something I could have inadvertantly done to cause this issue? Playing with roms is fun and easy when you've got a twrp backup to fall back on but a pain in the $#^ when it doesn't restore. Any thoughts would be appreciated before I give it another go.
thecdn said:
I've been following this thread because I was having the same problems as ZevSwe, multiple attempts at installing roms with no success. I've been using phones/tablets with custom roms for years so I have some experience but not with this device.
I'll be trying the steps in post #8 later today but I have a question about twrp that's buggin me. I have been taking full twrp backups to a usb stick before installing and just reinstalling when the custom rom didn't work but the last few times the reinstall failed at about 98% complete and I've had to reinstall stock from scratch.
Any idea why a twrp backup would fail on reinstall? Is there something I could have inadvertantly done to cause this issue? Playing with roms is fun and easy when you've got a twrp backup to fall back on but a pain in the $#^ when it doesn't restore. Any thoughts would be appreciated before I give it another go.
Click to expand...
Click to collapse
Since you noted that you have been doing a backup to a USB stick, it could be the USB stick is failing.
Honestly, all the installation guides for custom Roms i came across on XDA in the recent years are complete garbage. It fills like copy pasted from a guide that has been copypasted from a copypasted thread which has been copypasted and never worked.
For me, this guide works just fine. I just had to find the files for my Mi 9 instead of the k20 Pro. I would upload them for you but my upload speed is garbage.
https://www.youtube.com/watch?v=w_u_w6SrTDY&t=249s
I have flashed a lot of ROMs custom and official, fastboot and recovery. Never had any problems, the steps is here in thread.
Just remember 2 thing:
1. If you have ROM which using encryption, you must format data, because wipe will not remove encryption and you will see gibberish names
2. If you wipe system (which is mean less, because every ROM flash will do that, when you flash it, but many people insist in wiping it) then you must flash a ROM without reboot or you will stuck in fastboot and only option to repair is to flash official fastboot ROM (Non official fastboot ROMs, don't exist).