Related
How do I uninstall TWRP and unroot my Honor 9 Lite so i can update the phone to LLD-L31 8.0.0.128(C432) with face unlock?
I have already locked bootloader.
When i reboot the phone it automatically brings me to eRecovery and when i "Download latest version and recovery" it says "Getting package info failed". Please help
OmaroOmaro said:
How do I uninstall TWRP and unroot my Honor 9 Lite so i can update the phone to LLD-L31 8.0.0.128(C432) with face unlock?
I have already locked bootloader.
Click to expand...
Click to collapse
Looks like you "played" a bit to much with your phone. There is no official TWRP yet and no official Firmware Image. So, this looks very bad for you to get out of this again.
Maybe try HiSuite from Huawei or MultiTool
https://forum.xda-developers.com/devdb/project/dl/?id=28734
Probably this could help as long as you can connect via ADB or HDB from HiSuite.
Good luck...
Hey, I've faced the exact same issue. After playing even a bit more, I manged to revert my device (LLD-L31) back to stock.
I've uploaded all the files I used, for you.
It passes SafetyNet check successullfy!
Download required files here
Here is was I did:
Format data using TWRP (Wipe -> Format data)
Enter fastboot mode (Connect to PC, power+ VolDown)
fastboot flash ramdisk ramdisk.emmc.win
fastboot flash kernel kernel.emmc.win
fastboot flash system SYSTEM.img
fastboot reboot
Click to expand...
Click to collapse
Please tell me, if it worked!
Note:
The SYSTEM.img is extracted from the UPDATE.APP from this site.
Kernel and ramdisk are from a LOS-15.1 TRWP backup. Not sure if they're required, but it didn't work for me without flashing them.
error while extracting update.app
hello sir, I'm getting this error while extracting update.app.. recovery ramdisk.img invalid header crc - Expected: 18707 Got:56582
creativeanand said:
hello sir, I'm getting this error while extracting update.app.. recovery ramdisk.img invalid header crc - Expected: 18707 Got:56582
Click to expand...
Click to collapse
Why exactly do you need to extrac the update.app? I've already uploaded all required files and linked them in my previous post.
Also, which program did you use? Which operating system did you use?
now my phone is looping
MateUserHHTT said:
Why exactly do you need to extrac the update.app? I've already uploaded all required files and linked them in my previous post.
Also, which program did you use? Which operating system did you use?
Click to expand...
Click to collapse
now my phone is looping on off, on of
and i can't go to fastboot
creativeanand said:
now my phone is looping on off, on of
and i can't go to fastboot
Click to expand...
Click to collapse
In order for me to help you, I need to know exactly what you did.
So what did you do before your phone went into bootloop? (And don't worry, my Honor 9 lite has been in bootloops 100 of times, we can fix that! )
And how did you try to enter fastboot?
Make sure your phone is connected to a computer via USB!
Then press and hold Volume DOWN and Power button until phone reboots.
Release power when you see the blue honor screen.
Release volume down key, when you are in fastboot.
MateUserHHTT said:
In order for me to help you, I need to know exactly what you did.
So what did you do before your phone went into bootloop? (And don't worry, my Honor 9 lite has been in bootloops 100 of times, we can fix that! )
And how did you try to enter fastboot?
Make sure your phone is connected to a computer via USB!
Then press and hold Volume DOWN and Power button until phone reboots.
Release power when you see the blue honor screen.
Release volume down key, when you are in fastboot.
Click to expand...
Click to collapse
after flash shall i wipe data/ factory reset?
creativeanand said:
after flash shall i wipe data/ factory reset?
Click to expand...
Click to collapse
Again, I need to know whay you did!
You don't necessarily need to factory reset after a flash. But it probably won't make things worse.
But if you are switching the ROM (stock to a custom Rom) you indeed have to format data in twrp.
MateUserHHTT said:
Again, I need to know whay you did!
You don't necessarily need to factory reset after a flash. But it probably won't make things worse.
But if you are switching the ROM (stock to a custom Rom) you indeed have to format data in twrp.
Click to expand...
Click to collapse
i unlocked my phone bcoz the sound of h9l was lower then Redmi note 5 so i wanted to boost the sound with aris sound system and dolby atmos app.
after flashing 'SUPERSU' phone was not starting freeze at honor logo and then i wiped & rested in twrp...
now i did fastboot as you said now eRecovery is asking download latest version, wipe data/ f rest, reboot, shoutdown what shall i do now,,....thank you for helping
creativeanand said:
i unlocked my phone bcoz the sound of h9l was lower then Redmi note 5 so i wanted to boost the sound with aris sound system and dolby atmos app.
after flashing 'SUPERSU' phone was not starting freeze at honor logo and then i wiped & rested in twrp...
now i did fastboot as you said now eRecovery is asking download latest version, wipe data/ f rest, reboot, shoutdown what shall i do now,,....thank you for helping
Click to expand...
Click to collapse
Ok, now I can help you.
First of all, install TWRP. Use img2 (the experimental test build) if img #1 just stucks at the TWRP screen and won't enter the recovery.
Tell me when you succeed
You can get TWRP from here
https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
MateUserHHTT said:
Ok, now I can help you.
First of all, install TWRP. Use img2 (the experimental test build) if img #1 just stucks at the TWRP screen and won't enter the recovery.
Tell me when you succeed
You can get TWRP from here
https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
Click to expand...
Click to collapse
i did now?
creativeanand said:
i did now?
Click to expand...
Click to collapse
Great!
Now just follow my instructions from my earlier post
Make sure to put the files you download in the same folder as you run fastboot commands, so fastboot can find these files.
Good luck!??
MateUserHHTT said:
Great!
Now just follow my instructions from my earlier post
Make sure to put the files you download in the same folder as you run fastboot commands, so fastboot can find these files.
Good luck!
Click to expand...
Click to collapse
i did as you said .. now phone is not starting stoped at huawei eRecovery
whan i go to twrp phone reboots itshalf after 10sec
If you can boot to bootloader
and bootloader = unlocked
and FRP = unlock
then you can reset the phone to stock-rom
you need download with HuaweiFirmwareFinder 1 FULL-Update from YOUR build
i see in FF "LLD-L31C432B131 FullOTA-MF
download the 3 files, extract with HuaweiUpdateExtractor
- ramdisk.img
- recovery_ramdis.img
- system.img
the extractor do automatik for all *.img 1 *.img.header
copy this 6 files to your ADB-Folder
For reset to stock-rom
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
after this reboot the phone, eRecovery format low-level "data", phone reboot and start as "new" phone (initial settings)
before you do this you can do 1 test :
- fastboot flash recovery_ramdisk recovery_ramdis.img
why?
format low-level "data" work ONLY with stock-recovery, NOT with TWRP
after this is your "data" encrypt !
Only 1 TWRP work with encrypt/decrypt : https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
if phone work set PIN for Screen-open (this PIN need TWRP by start for encrypt/decrypt "data")
if you need, you can now flash recovery_ramdisk TWRP.img
if you need install OTA-Updates : if OTA-Update on your phone "install update now ?" answer "NO, later" and
- fastboot flash recovery_ramdisk recovery_ramdis.img (stock-recovery)
and install Update now.
if all work and you need : flash TWRP
i hope you understand this "way"
the advantage : you can install with TWRP OR flash developer-system.img and if anything not work - reset phone to stock-rom
i use ONLY TWRP with encrypt. this is security-question. if phone lost - data is encrypt !
TWRP without encrypt work only
- boot to TWRP
- format data
- boot from TWRP to TWRP
- data have now NO encrypt
Doesn't Android use FBE by default since Android O, so the data is always encrypted no matter what TWRP was used?
JamesBott said:
If you can boot to bootloader
and bootloader = unlocked
and FRP = unlock
then you can reset the phone to stock-rom
you need download with HuaweiFirmwareFinder 1 FULL-Update from YOUR build
i see in FF "LLD-L31C432B131 FullOTA-MF
download the 3 files, extract with HuaweiUpdateExtractor
- ramdisk.img
- recovery_ramdis.img
- system.img
the extractor do automatik for all *.img 1 *.img.header
copy this 6 files to your ADB-Folder
For reset to stock-rom
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
after this reboot the phone, eRecovery format low-level "data", phone reboot and start as "new" phone (initial settings)
before you do this you can do 1 test :
- fastboot flash recovery_ramdisk recovery_ramdis.img
why?
format low-level "data" work ONLY with stock-recovery, NOT with TWRP
after this is your "data" encrypt !
Only 1 TWRP work with encrypt/decrypt : https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
if phone work set PIN for Screen-open (this PIN need TWRP by start for encrypt/decrypt "data")
if you need, you can now flash recovery_ramdisk TWRP.img
if you need install OTA-Updates : if OTA-Update on your phone "install update now ?" answer "NO, later" and
- fastboot flash recovery_ramdisk recovery_ramdis.img (stock-recovery)
and install Update now.
if all work and you need : flash TWRP
i hope you understand this "way"
the advantage : you can install with TWRP OR flash developer-system.img and if anything not work - reset phone to stock-rom
i use ONLY TWRP with encrypt. this is security-question. if phone lost - data is encrypt !
TWRP without encrypt work only
- boot to TWRP
- format data
- boot from TWRP to TWRP
- data have now NO encrypt
Click to expand...
Click to collapse
sir shall i go to service center i have warrenty
creativeanand said:
sir shall i go to service center i have warrenty
Click to expand...
Click to collapse
By unlocking the bootloader you've void your warranty.
They will probably charge you for the repair.
What happens if you install this version of TWRP?
It's on Chinese, click the little icon in the top right corner and select "English".
If it doesn't crash, try this one.
Make sure to follow the correct steps for flashing.
fastboot flash recovery_ramdisk [filename.img]
fastboot flash reboot
QUICKLY unplug USB and before it fully reboots, hold press Volume up key
If it fails, check out this guide:
https://forum.xda-developers.com/9-lite/how-to/guide-unbrick-device-recover-bootloop-t3772563
My hon or 9 lite is in teaming page and it won't open I have tried to update via erecOvery but it won't work and I cannot go to recovery mode please help me.
@Prabin99
what you build ?
what have you do before start the update ?
have you anything flashed ?
Hello! Hoping someone can help and guide me in fixing my A2's bootloop. I already searched many forums online, but still no luck.
I flashed a permissiver_v5.zip in Evolution X Rom hoping that it will solve the random reboots, and I got bootloop. I successfully flashed the July stock rom through Miflash, hoping to boot into system, but still bootloop. I flashed the stock firmware and persist zip too in TWRP, but I also got mount persist error. I also need to use fastboot boot twrp.img to get into Twrp since it will disappear after clicking reboot recovery. I tried EDL, but then I got not enough storage error in Miflash.
Hopefully somebody can help me with steps!
LATEST UPDATE:
With the help of KevMetal, I can now use my phone after a week of being hardbricked. At first, my device can't boot to the bootloader or recovery, so what I did was to press the volume down and power button for some time and my phone was detected by the PC. So my device booted to EDL by itself, no need to open the phone. Then I used the 2018 version of MiFlash Tool and flashed the V.10.0.17 of stock Pie ROM from here: https://forum.xda-developers.com/mi-...-t3824849/amp/
After that, I flashed the persist.zip provided by KevMetal (browse in this thread) in recovery since I can't sideload the zip, and it worked fine. I then booted to system and finally there was no bootloop.
I then noticed that the IMEI was gone, so I tried to fix through some guides online but this one worked for me. https://medium.com/@shekhawatkoki/fi...1-2ed533548d32
Ronaldendoma said:
Hello! Hoping someone can help and guide me in fixing my A2's bootloop. I already searched many forums online, but still no luck.
I flashed a permissiver_v5.zip in Evolution X Rom hoping that it will solve the random reboots, and I got bootloop. I successfully flashed the July stock rom through Miflash, hoping to boot into system, but still bootloop. I flashed the stock firmware and persist zip too in TWRP, but I also got mount persist error. I also need to use fastboot boot twrp.img to get into Twrp since it will disappear after clicking reboot recovery. I tried EDL, but then I got not enough storage error in Miflash.
Hopefully somebody can help me with steps!
Click to expand...
Click to collapse
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you so much for your reply. I really appreciate it. I admit that I am really wrong in flashing that permissiver zip. I just hoped that it will solve my random reboot issue, from this tutorial: https://www.google.com/url?sa=t&sou...BMAB6BAgCEAE&usg=AOvVaw2suOu9rYeTps71AvKuZbrA
So now, I already downloaded OrangeFox-R10.1_1-Stable-jasmine_sprout.zip for recovery and persist_restorer_6x.zip from the Telegram group, which is universal persist according to them.
But I just have some questions:
1. Do I need to wipe both a and b in recovery or use command fastboot -w before flashing the stock ROM?
2. After flashing stocK ROM in Miflash tool, it will start to boot to system, but in this case, bootloop, so am I right to press buttons to forcibly go to bootloader?
3. For #7 (boot to recovery), this means fastboot boot recovery.img?
4. For #9, if adb sideload doesn't work, can I flash persist in recovery instead?
Ronaldendoma said:
Thank you so much for your reply. I really appreciate it. I admit that I am really wrong in flashing that permissiver zip. I just hoped that it will solve my random reboot issue, from this tutorial: https://www.google.com/url?sa=t&sou...BMAB6BAgCEAE&usg=AOvVaw2suOu9rYeTps71AvKuZbrA
So now, I already downloaded OrangeFox-R10.1_1-Stable-jasmine_sprout.zip for recovery and persist_restorer_6x.zip from the Telegram group, which is universal persist according to them.
But I just have some questions:
1. Do I need to wipe both a and b in recovery or use command fastboot -w before flashing the stock ROM?
2. After flashing stocK ROM in Miflash tool, it will start to boot to system, but in this case, bootloop, so am I right to press buttons to forcibly go to bootloader?
3. For #7 (boot to recovery), this means fastboot boot recovery.img?
4. For #9, if adb sideload doesn't work, can I flash persist in recovery instead?
Click to expand...
Click to collapse
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
KevMetal said:
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you again.
I tried adb sideload before but was stuck at 0%, I missed something. I'll update here for the result once I can be back to PC.
KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
KevMetal said:
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you again.
I tried adb sideload before but was stuck at 0%, I maybe missed something. I'll update here for the result once I can be back to PC.
Ronaldendoma said:
Thank you again.
I tried adb sideload before but was stuck at 0%, I maybe missed something. I'll update here for the result once I can be back to PC.
Click to expand...
Click to collapse
ok yeah must be a mistake ..
do you understand that first you enter fastboot and boot the orange fox recovery ..only then you start the adb ..
BUT REMember first you need to toggle or activate adb from orange fox recovery (maybe you forgot this ? )
another thing it is very slow so wait very long
another thing the zip you want to flash must be in the adb folder and have the name you use
so
rename persist to persist.zip and put it in adb folder ..then put magisk zip and rename to magisk.zip :
adb sideload persist.zip
adb sideload magisk.zip
Sent from my wayne using XDA Labs
here is a photo where you need to activate adb
Sent from my wayne using XDA Labs
KevMetal said:
ok yeah must be a mistake ..
do you understand that first you enter fastboot and boot the orange fox recovery ..only then you start the adb ..
BUT REMember first you need to toggle or activate adb from orange fox recovery (maybe you forgot this ? )
another thing it is very slow so wait very long
another thing the zip you want to flash must be in the adb folder and have the name you use
so
rename persist to persist.zip and put it in adb folder ..then put magisk zip and rename to magisk.zip :
adb sideload persist.zip
adb sideload magisk.zip
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
I need to wait more, I think. Before this thread, I tried to adb sideload in TWRP but it took somewhat long and still 0%, so I just cancelled since I ran out of time.
KevMetal said:
here is a photo where you need to activate adb
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Regarding persist.zip, I am now confused because I asked in the group if the file persist_restorer_6x.zip is universal (either pie or 10, wayne or jasmine), they said yes, and another one said no. I searched in the group and found persist_restorer_a2.zip. I checked both files and they have the same filesize and contents.
So is there a thing like a universal persist for a2/6x, either for pie or 10? Or like what you said, only relevant persist depending on the os and device?
techieboy2020 said:
Regarding persist.zip, I am now confused because I asked in the group if the file persist_restorer_6x.zip is universal (either pie or 10, wayne or jasmine), they said yes, and another one said no. I searched in the group and found persist_restorer_a2.zip. I checked both files and they have the same filesize and contents.
So is there a thing like a universal persist for a2/6x, either for pie or 10? Or like what you said, only relevant persist depending on the os and device?
Click to expand...
Click to collapse
it is the same device.. so it is cross compatible ..it might just give an error if it checks the build prop ..obviously flash the A2..pie or q will just maybe be updated version or not but bettrr to flash corresponding if it exists
Sent from my wayne using XDA Labs
KevMetal said:
it is the same device.. so it is cross compatible ..it might just give an error if it checks the build prop ..obviously flash the A2..pie or q will just maybe be updated version or not but bettrr to flash corresponding if it exists
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
I see. I can't access my PC yet, but what if I still got bootloop after trying those steps, what must I do next? I'm worried for step #10.
Regarding the persist.zip, can you please check the zips below? The two have the same filesize and files inside, so maybe the two are just the same.
techieboy2020 said:
I see. I can't access my PC yet, but what if I still got bootloop after trying those steps, what must I do next? I'm worried for step #10.
Regarding the persist.zip, can you please check the zips below? The two have the same filesize and files inside, so maybe the two are just the same.
Click to expand...
Click to collapse
those are empty and won't work ..use this
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
Sent from my wayne using XDA Labs
KevMetal said:
those are empty and won't work ..use this
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Ok thank you so much. Will try this tomorrow.
Regarding the state of my device, I can't boot to system because of bootloop. If I press power and volume +, I got no command. If I press power and volume -, fastboot mode. My device's bootloader is already unlocked, and can be detected through fastboot.
techieboy2020 said:
Ok thank you so much. Will try this tomorrow.
Regarding the state of my device, I can't boot to system because of bootloop. If I press power and volume +, I got no command. If I press power and volume -, fastboot mode. My device's bootloader is already unlocked, and can be detected through fastboot.
Click to expand...
Click to collapse
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
KevMetal said:
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Got it. So the zip is compatible for either Pie or Android 10?
What's the best version for Miflash tool? I tried the newer version but it can't detect my device, and only the older version can detect. But it seems that the older version can't be trusted also since I still got persist error before.
For #10, my device will bootloop 4 to 5 times. So will it automatically turn off and on again until it will successfully boot? How long does it normally boot?
UPDATE:
KevMetal said:
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
UPDATE:
So I flashed the Pie Rom (V.10.0.17.0) in the MiFlash Tool (v. 2016.04.01.0) and the flashing was successful. The device turned on and only remained at the Android One logo and turned off again. This repeated for another time and I then forced my device to fastboot mode through the buttons. I then flashed the latest Orange Fox Recovery and it was successful. Now, I checked the recovery and persist can't be mounted (can't put a check on the box), but I still continued to adb sideload mode. The sideloading for persist.zip started, but was stuck at 10%. I waited more and decided to disconnect and try to flash the zip on the device instead. I checked the active slot and it was b, so I thought changing to a will be able to mount persist. I thought that if I remain at b, I will still get mount persist error. I clicked "boot to recovery" and the screen turned off. After a while, the screen remained off and I tried to use the button combinations, and the screen was totally black (no fastboot, logo, animation, or even some light, etc). It's completely black, but I noticed that the device was still hot after a few minutes. I connected my device to the PC again and the MiFlash tool detected my device as Com10. I flashed the rom again but the flashing was not successful. I tried to uninstall the drivers and still, there is no hope for reflashing the rom (it's now detected as com4). If I try to use power combinations, the PC will make sounds like when you connect/ disconnect a device, meaning, my phone can still be detected by my PC. So is there still a hope for my phone?
techieboy2020 said:
UPDATE:
So I flashed the Pie Rom (V.10.0.17.0) in the MiFlash Tool (v. 2016.04.01.0) and the flashing was successful. The device turned on and only remained at the Android One logo and turned off again. This repeated for another time and I then forced my device to fastboot mode through the buttons. I then flashed the latest Orange Fox Recovery and it was successful. Now, I checked the recovery and persist can't be mounted (can't put a check on the box), but I still continued to adb sideload mode. The sideloading for persist.zip started, but was stuck at 10%. I waited more and decided to disconnect and try to flash the zip on the device instead. I checked the active slot and it was b, so I thought changing to a will be able to mount persist. I thought that if I remain at b, I will still get mount persist error. I clicked "boot to recovery" and the screen turned off. After a while, the screen remained off and I tried to use the button combinations, and the screen was totally black (no fastboot, logo, animation, or even some light, etc). It's completely black, but I noticed that the device was still hot after a few minutes. I connected my device to the PC again and the MiFlash tool detected my device as Com10. I flashed the rom again but the flashing was not successful. I tried to uninstall the drivers and still, there is no hope for reflashing the rom (it's now detected as com4). If I try to use power combinations, the PC will make sounds like when you connect/ disconnect a device, meaning, my phone can still be detected by my PC. So is there still a hope for my phone?
Click to expand...
Click to collapse
all of this couldn't happen if you only flashed permissiver ..what rom did you previously flash in slot b
anyway doesn't matter ..boot to fastboot with buttons ..boot ..NOT FLASH orange fox recovery
do all wipes
format data
install custom rom
install magisk
install persist
reboot to other standby slot ..
do all wipes
format data
install custom rom
install magisk
install persist
then reboot and phone will boot
use a latest custom rom Q with gapps included ....
follow all the instructions ..not only some ..don change them ..if it fails message me with screenshot
but the 10% problem over usb is a hardware , computer or most likely cable problem ..get a new cable ..or maybe you changed or damaged your screen improperly ..
anyway try the above
also download the most newest copy of miflash and use that to install drivers and flash if you want to flash stock and flash the latest stock amdroid ..
if your phone doesn't go into fastboot it is cos it is bricked in edl mode ..so flash latest stock with latest miflash ..
THEN FLASH PERSIST BY ONLY BOOTINGBrecovery
did you try to convert this A2 to Wayne amd triggered arb ? that could be why flashing stock pie goes to edl mode
Sent from my wayne using XDA Labs
Just FYI:
Since 10.0.2.0 till now I thought that persist.img is version-insensitive, as I flashed persist.img taken from 8.1 ROM into couple of versions of 9.0 without any problems (via my method published in "Guides...").
Last week I noticed that compass is "showing south", and tried to flash various versions of persist.img into active 11.0.12.0 - and was surprised to encounter "white screen of eternal booting" with non-native version of persist.img. So finally had to flash persist.img taken from 11.0.12.0 fastboot ROM image.
(Btw, my problem with compass seems to have 2 sides -1st is somewhat very big deviation at homeplace, and 2nd is that only 1st magnetic sensor is being calibrated while second magnetic sensor is not being calibrated by means I used).
KevMetal said:
all of this couldn't happen if you only flashed permissiver ..what rom did you previously flash in slot b
anyway doesn't matter ..boot to fastboot with buttons ..boot ..NOT FLASH orange fox recovery
do all wipes
format data
install custom rom
install magisk
install persist
reboot to other standby slot ..
do all wipes
format data
install custom rom
install magisk
install persist
then reboot and phone will boot
use a latest custom rom Q with gapps included ....
follow all the instructions ..not only some ..don change them ..if it fails message me with screenshot
but the 10% problem over usb is a hardware , computer or most likely cable problem ..get a new cable ..or maybe you changed or damaged your screen improperly ..
anyway try the above
also download the most newest copy of miflash and use that to install drivers and flash if you want to flash stock and flash the latest stock amdroid ..
if your phone doesn't go into fastboot it is cos it is bricked in edl mode ..so flash latest stock with latest miflash ..
THEN FLASH PERSIST BY ONLY BOOTINGBrecovery
did you try to convert this A2 to Wayne amd triggered arb ? that could be why flashing stock pie goes to edl mode
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
So I was able to use another laptop, and I managed to install adb, drivers, and MiFlash Tool. The 2018 version can now detect my phone, and I can now at least boot into fastboot. But my flashing is still not successful because I got stuck at system.img. The laptop freezes and I already tried to free up space in C: drive.
Hi, today I tried using the Realme Flash tool for X2 Pro but it bricked my phone. Based on the flash tools error logs it shows this
"~~Medium~~ UnZipFloHelper Delete temp file exception:The process cannot access the file 'C:\Users\Michael\AppData\Roaming\realmeFlashTools\temp\system.img' because it is being used by another process."
seems like a windows problem but I cant find any reference on the web. I tried restarting my PC but it didn't solve my problem.Any suggestions how to fix this? thank you!
Realme flash tool decrypt and extract the ofp to C:\Users\Michael\AppData\Roaming\realmeFlashTools \temp .This seem to be windows permission issue .
Try to run as administer the realme flash tool and try again. Also you can flash unpacked ozip trough fastboot manually, It will be very similar to flashing with realme flash tool .
or965 said:
Realme flash tool decrypt and extract the ofp to C:\Users\Michael\AppData\Roaming\realmeFlashTools \temp .This seem to be windows permission issue .
Try to run as administer the realme flash tool and try again. Also you can flash unpacked ozip trough fastboot manually, It will be very similar to flashing with realme flash tool .
Click to expand...
Click to collapse
Thank you it worked! I tried run as admin the flash tool and deleted .IMG file it also seems that an Virtual image program is holding to it so I disabled it.
I have installed oxygen os built 4 in my x2 pro device but i didnt like the interface so i decided to return to realme ui and i have installed realme ui2.0 on my device thrugh twrp custom recovery but after install it suddenly switch off and it goes to a boot loop. now i can't enter into my recovery mode, i can't flash twrp, i can only enter in fastboot mode. please give any solution , i need my phone to back like normal...
Rinku390 said:
I have installed oxygen os built 4 in my x2 pro device but i didnt like the interface so i decided to return to realme ui and i have installed realme ui2.0 on my device thrugh twrp custom recovery but after install it suddenly switch off and it goes to a boot loop. now i can't enter into my recovery mode, i can't flash twrp, i can only enter in fastboot mode. please give any solution , i need my phone to back like normal...
Click to expand...
Click to collapse
Hi, ( if your problem is not resolved at this time )
If you want you can try this procedure
Enter fastboot
- don't know if a fastboot erase " boot + system + vendor" can help
Flash stock recovery
Enter recovery and format data
Reboot bootloader
Flash full stock rom ~5Gb ( not the OTA ~3GB) with the realme flash tool
LoVerMaKi said:
Hi, ( if your problem is not resolved at this time )
If you want you can try this procedure
Enter fastboot
- don't know if a fastboot erase " boot + system + vendor" can help
Flash stock recovery
Enter recovery and format data
Reboot bootloader
Flash full stock rom ~5Gb ( not the OTA ~3GB) with the realme flash tool
Click to expand...
Click to collapse
i have a same problem here. but i cant flash stock rom on fastboot flashing img files will loop back into bootloader and realme flash tool says "CANNOT FIND CENTRAL DIRECTORY" PLEASE HELP ME
Rinku390 said:
I have installed oxygen os built 4 in my x2 pro device but i didnt like the interface so i decided to return to realme ui and i have installed realme ui2.0 on my device thrugh twrp custom recovery but after install it suddenly switch off and it goes to a boot loop. now i can't enter into my recovery mode, i can't flash twrp, i can only enter in fastboot mode. please give any solution , i need my phone to back like normal...
Click to expand...
Click to collapse
i have a same problem here. but i cant flash stock rom on fastboot flashing img files will loop back into bootloader and realme flash tool says "CANNOT FIND CENTRAL DIRECTORY" PLEASE HELP ME
Rinku390 said:
I have installed oxygen os built 4 in my x2 pro device but i didnt like the interface so i decided to return to realme ui and i have installed realme ui2.0 on my device thrugh twrp custom recovery but after install it suddenly switch off and it goes to a boot loop. now i can't enter into my recovery mode, i can't flash twrp, i can only enter in fastboot mode. please give any solution , i need my phone to back like normal...
Click to expand...
Click to collapse
did you fix your phone?
i am at same problem here please please please answer me.
please share the procedur to fix if you have fixed
PETER.PARKER said:
i have a same problem here. but i cant flash stock rom on fastboot flashing img files will loop back into bootloader and realme flash tool says "CANNOT FIND CENTRAL DIRECTORY" PLEASE HELP ME
Click to expand...
Click to collapse
Hi,
Flashtool says some error that not relevant. If the rom is not adaptable for the phone, the error msg is not really clear.
Here is some link. I cant help you more.
You need to dl the c27.ofc (full stock rom).
rom and flash tool
ofc extractor
Option 1 try flash the c27 with flashtool.
Option 2
. Extract the ofc with MCT OFP Extractor .boot in flashboot and flash the boot/recovery (maybe try all img one by one if it pass) i use google for the correct syntax for each img file
. try boot in recovery et format data
. Reboot in fastboot and reflash the ofc with flashtool
You need to experiment to find the correct proces for your problem.
Hf gl
LoVerMaKi said:
Hi,
Flashtool says some error that not relevant. If the rom is not adaptable for the phone, the error msg is not really clear.
Here is some link. I cant help you more.
You need to dl the c27.ofc (full stock rom).
rom and flash tool
ofc extractor
Option 1 try flash the c27 with flashtool.
Option 2
. Extract the ofc with MCT OFP Extractor .boot in flashboot and flash the boot/recovery (maybe try all img one by one if it pass) i use google for the correct syntax for each img file
. try boot in recovery et format data
. Reboot in fastboot and reflash the ofc with flashtool
You need to experiment to find the correct proces for your problem.
Hf gl
Click to expand...
Click to collapse
I downloaded and flashed that c27 rom with realme flash tool it successfully completed the flashing process but nothing new it loops back into bootloader im literally pissed rigt now
Detail info about my problem "https://forum.xda-developers.com/t/...evice-state-unlocked-secure-boot-yes.4330817/"
Rinku390 said:
I have installed oxygen os built 4 in my x2 pro device but i didnt like the interface so i decided to return to realme ui and i have installed realme ui2.0 on my device thrugh twrp custom recovery but after install it suddenly switch off and it goes to a boot loop. now i can't enter into my recovery mode, i can't flash twrp, i can only enter in fastboot mode. please give any solution , i need my phone to back like normal...
Click to expand...
Click to collapse
i am facing same problem,is your problem resolved ,please help
JKD23 said:
Thank you it worked! I tried run as admin the flash tool and deleted .IMG file it also seems that an Virtual image program is holding to it so I disabled it.
Click to expand...
Click to collapse
Please tell me how you did?
I have flashed TWRP to recovery (on my unlocked Redmi Note 10 Pro) and can access it no problem. But I have no TWRP folder on my phone and cannot see one when connected to my computer.
I have reflashed to try to fix it, but no change. I found a thread where the suggested terminal commands but I would need to root my phone and I don't think that is something I should be doing. Any suggestions?
31272809 said:
I have flashed TWRP to recovery (on my unlocked Redmi Note 10 Pro) and can access it no problem. But I have no TWRP folder on my phone and cannot see one when connected to my computer.
I have reflashed to try to fix it, but no change. I found a thread where the suggested terminal commands but I would need to root my phone and I don't think that is something I should be doing. Any suggestions?
Click to expand...
Click to collapse
I think you can't access internal storage in case of encryption.
Google about decryption pros cons ... if you're fine with decryption check out dfe in our forum
Laptapper said:
I think you can't access internal storage in case of encryption.
Google about decryption pros cons ... if you're fine with decryption check out dfe in our forum
Click to expand...
Click to collapse
I read about that but I thought I'd see 0MB or weird filenames while looking at the filesystem in TWRP recovery and neither is the case. I did have to enter my password the first time I used TWRP and I have never been asked for it since.
31272809 said:
I read about that but I thought I'd see 0MB or weird filenames while looking at the filesystem in TWRP recovery and neither is the case. I did have to enter my password the first time I used TWRP and I have never been asked for it since.
Click to expand...
Click to collapse
Which recovery you've installed? Try newest orange fox
Laptapper said:
Which recovery you've installed? Try newest orange fox
Click to expand...
Click to collapse
So I had twrp 3.6_11-sweet installed. I just flashed Orange fox (the latest stable version) to recovery, and then I could no longer access recovery - it just restarted to flashboot. I had this problem when I tried to flash the Pixel Experience image too.
So I flashed TWRP to recovery again and everything is back to normal. But the problem is that I can’t use TWRP because there’s no folder installed.
31272809 said:
So I had twrp 3.6_11-sweet installed. I just flashed Orange fox (the latest stable version) to recovery, and then I could no longer access recovery - it just restarted to flashboot. I had this problem when I tried to flash the Pixel Experience image too.
So I flashed TWRP to recovery again and everything is back to normal. But the problem is that I can’t use TWRP because there’s no folder installed.
Click to expand...
Click to collapse
How you exactly flashed recovery?
Orange fox is working quite good....
Laptapper said:
How you exactly flashed recovery?
Orange fox is working quite good....
Click to expand...
Click to collapse
So I put the phone in fastboot mode -> connected to PC with usb -> check connection in cmd (fastboot devices) -> fastboot flash recovery "recovery_orange fox.img" -> power+up
And I get sent back to the fastboot screen
I must be doing something wrong but I have watched videos and read instructions and I don't know what it is.
31272809 said:
So I put the phone in fastboot mode -> connected to PC with usb -> check connection in cmd (fastboot devices) -> fastboot flash recovery "recovery_orange fox.img" -> power+up
And I get sent back to the fastboot screen
I must be doing something wrong but I have watched videos and read instructions and I don't know what it is.
Click to expand...
Click to collapse
Sounds ok
But without the quotes and no spaces, means change the file name like cmd:
fastboot flash recovery orangefox.img
Laptapper said:
Sounds ok
But without the quotes and no spaces, means change the file name like cmd:
fastboot flash recovery orangefox.img
Click to expand...
Click to collapse
I renamed the file but same result - it cycles through back to fastboot instead of recovery.
I don't understand. It's like it only accepts the twrp image, but even that doesn't install right.
31272809 said:
I renamed the file but same result - it cycles through back to fastboot instead of recovery.
I don't understand. It's like it only accepts the twrp image, but even that doesn't install right.
Click to expand...
Click to collapse
Please make a pc screenshot from flashing progress
You've switched on developer option usb debugging?
Laptapper said:
Please make a pc screenshot from flashing progress
You've switched on developer option usb debugging?
Click to expand...
Click to collapse
Here's the screenshot. Inbetween flashing recoveryorangefox.img and twrp.img I have tried to reboot into recovery and I have been sent back to fastboot.
Yes, usb debugging is on in the settings.
31272809 said:
Here's the screenshot. Inbetween flashing recoveryorangefox.img and twrp.img I have tried to reboot into recovery and I have been sent back to fastboot.
Yes, usb debugging is on in the settings.
Click to expand...
Click to collapse
Check out here
How to Enter Recovery Mode ? Volume Up and Power enabling Fastboot
Today I flashed EU RoM 13.0.4 to my Redmi Note 10 pro . Phone is working fine but I installed orange recovery and the process completed successfully on pc . When I press power and volume up it going to Fastboot mode instead of recovery mode. How...
forum.xda-developers.com
And take the files which there are downloadable
Try after flashing to boot via hardware keys and also via adb.
If both not working, I think you have to flash fastboot image via PC miflash and boot it to switch developer usb debugging on and restart to fastboot mode and flash twrp again.....
31272809 said:
Here's the screenshot. Inbetween flashing recoveryorangefox.img and twrp.img I have tried to reboot into recovery and I have been sent back to fastboot.
Yes, usb debugging is on in the settings.
Click to expand...
Click to collapse
One more idea, before starting from scratch:
After flashing twrp disconnecting usb and then rebooting to recovery by pressing power and vol+ until you'll see the logo and feel the vibration
Why don't you test the recovery using fastboot boot? My recommendation is never to flash any recovery before successfully having it started manually once.
My personal approach is, never to install any recovery but only boot it in case it is needed. Disadvantage is that you need to be near a computer if you want to run it.
fastboot flash recovery twrp-3.6.0_11-0-sweet.img
fastboot boot twrp-3.6.0_11-0-sweet.img
Ashle said:
fastboot flash recovery twrp-3.6.0_11-0-sweet.img
fastboot boot twrp-3.6.0_11-0-sweet.img
Click to expand...
Click to collapse
Hi all, there's been some progress but I'd like your advice before continuing. I have my preferred ROM (Pixel Experience, zipped) copied to my SD card and I can see my SD card under Install option on TWRP. My phone data has been formatted (using the twrp Wipe option). Should I try installing from the SD card? I'm nervous since I know missing steps was warned against in the installation instructions.
1. Wipe Data/Cache
2. Format Data (yes)
3. Flash ROM Pixel Experience.zip
4. Reboot System
Ashle said:
1. Wipe Data/Cache
2. Format Data (yes)
3. Flash ROM Pixel Experience.zip
4. Reboot System
Click to expand...
Click to collapse
Is 1 included in 2, or should I do something else as well?
If I'm okay to move to step 3, do I reboot to recovery or reboot into (hopefully) my new ROM?
Copy Pixel Experience.zip to sdcard
reboot to recovery
All over TWRP
1. Wipe Data/Cache
2. Format Data (yes)
3. Flash ROM Install Pixel Experience.zip
4. Reboot System
Ashle said:
Copy Pixel Experience.zip to sdcard
reboot to recovery
All over TWRP
1. Wipe Data/Cache
2. Format Data (yes)
3. Flash ROM Install Pixel Experience.zip
4. Reboot System
Click to expand...
Click to collapse
It didn't work.
Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation
WolfHRB said:
Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation
Click to expand...
Click to collapse
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
lewmur said:
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.
Click to expand...
Click to collapse
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
WolfHRB said:
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
Click to expand...
Click to collapse
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible
kevinco1 said:
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible
Click to expand...
Click to collapse
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
What exact GSI and build are you trying to install? There are only a few that are compatible, otherwise you're not gonna have any other luck flashing
I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?
stradfred said:
I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?
Click to expand...
Click to collapse
Make sure you are only trying to flash arm64 builds for this device
Both 19.1-20230418 and 20.0-20230324 do install properly but there's certain bugs that make them unfit to be used as a daily driver.
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218
stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
You left out the step to format data and factory wipe.
lewmur said:
You left out the step to format data and factory wipe.
Click to expand...
Click to collapse
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.
kevinco1 said:
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218
Click to expand...
Click to collapse
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.
stradfred said:
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.
Click to expand...
Click to collapse
TWRP and fastboot can't handle the encrypted data partition. So you need to format it. Current versions of LOS re-encrypt it as soon as you boot to system. And you can't use dm-verity on this model, so you can't disable it.
stradfred said:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.
Click to expand...
Click to collapse
Did you try this build before or after the realization you had left out the steps to wipe and factory reset?
Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.
mrspeccy said:
Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.
Click to expand...
Click to collapse
If you mean you used the "Install" button in TWRP to flash, then that is your mistake. The "Install" button only has the option to flash the "Super" partition and not the "System". You need to use "Fastboot" to flash the system image. I flashed from CWD2 which is even later than CWC1, so that shouldn't be a problem. If it was, then TWRP wouldn't have worked. I'm running LOS 20 20300507 bgN.
No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).
mrspeccy said:
No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).
Click to expand...
Click to collapse
There are only certain LOS builds that work with this device, you're wasting your time if you are blindly flashing random ones.
Refer to earlier posts to confirm which ones do work. And like @lewmur just reported the newest build 20300507 bgN does flash successfully
The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?
mrspeccy said:
The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?
Click to expand...
Click to collapse
You must do a clean flash. The purpose of formatting the data partition is to get rid of the encryption. TWRP can't handle the encryption. And LOS will re-encrypt it the first time you boot to system. As to extracting the kernel from CWA3, I don't advise doing that. It could hard brick the tablet.