Related
Ok guys, this is a sureshot guide for
PROBLEM
* anyone wanting to decrypt their op3 but stuck at 1+ boot screen(Or not able to boot any custom ROMs.) and only able to restore twrp backups
* After using fastboot format userdata twrp and about phone shows only 32gb phone memory(where the hell is my rest of 32gb )
* Fastboot format userdata resulting in Stuck at boot screen or simply an unbrick trick to return to Stock OOS in unencrypted stage
SOLUTION
1. Use method 2 of Mega unbrick guide to restore your phone to stock partitions found here
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
2. After the flashing is complete do not reboot the phone instead reboot directly into bootloader.
3. In fastboot mode flash modded twrp 3.0.2.22 using command ''fastboot flash recovery recovery.img'' found here
http://forum.xda-developers.com/devdb/project/?id=15934#downloads
4. Reboot directly into twrp and using mtp mode copy latest elemental x kernel or bluspark kernel zip for OOS and SYSTEM supersu.zip into the internal storage. System supersu.zip here OR directly proceed to step 8
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
5. Now flash system supersu.zip and directly after that kernel.zip
6. Now again reboot to recovery directly and from twrp boot into system.
7. After boot up you system should be decrypted. You can check in security settings.
8.Reboot recovery and flash required firmware + modem zip found here
http://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
9.wipe data +cache +dalvik +system
10. Flash any rom of your choice and go flashoholic, use multirom or whatever you want.
Pheww. Thanks.
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Ashtrix said:
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Click to expand...
Click to collapse
anything... even multirom works flawless.
I will give this a try, Or will try to Flash the EX then perform parts of this since they support Kexec, to see what works, I have data and lot of apps working them again is a real pita with my schedule...
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
ach3fck said:
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
Click to expand...
Click to collapse
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
nikhilsnigam said:
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
Click to expand...
Click to collapse
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
ach3fck said:
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
Click to expand...
Click to collapse
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
nikhilsnigam said:
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
Click to expand...
Click to collapse
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
ach3fck said:
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
Click to expand...
Click to collapse
your bootloader doesn't get locked
nikhilsnigam said:
your bootloader doesn't get locked
Click to expand...
Click to collapse
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
ach3fck said:
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
Click to expand...
Click to collapse
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
nikhilsnigam said:
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
Click to expand...
Click to collapse
Yeah, i know that, thanks a lot, will try later all of this since i have no time now, will report how it went.Thanks!
Have my Mi 8 about a week, loving it BUT as the bootloader is unlocked I couldn't use Google Pay so I decided to install TWRP and get the Xiaomi.eu ROM.
I just installed TWRP and tried backing up the phone, but I got an error saying it Can not create the folder. I reinstalled TWRP, thinking maybe there was an issue with the first install but now it's stuck in a recovery boot loop. It loads to the MI screen with the unlocked icon but doesn't get to the powered by android, it goes straight into recovery.
The Rom is not on the device and I thought maybe could install it through the recovery but if I have the phone plugged into the laptop (Windows 10) and go into recovery, the touch screen on the phone doesn't work and the phone keeps rebooting itself.
I can also get into Fastboot and the device is detected by miFlash.
What should I do next, I don't trust my instincts. Any advice would be much appreciated. I'm currently downloading the Global Rom off Xiaomi (going to take a while on my 3mb broadband) and hoping I can flash that with miFlash tool, good or bad idea??
U can use otg usb and put the rom on it.
Boot to twrp and wipe data (the one that ask you to say yes? Than install the rom(choose one for recovery flashing not fastboot)
gm007 said:
U can use otg usb and put the rom on it.
Boot to twrp and wipe data (the one that ask you to say yes? Than install the rom(choose one for recovery flashing not fastboot)
Click to expand...
Click to collapse
Cheers for the reply! Unfortunately I don't have an adapter to put the rom on the phone. I'll order one now, always good to have for situations like this.
Any other way of getting the phone up and running sooner? If not, no problem, I'll just have to wait for the adapter.
cherbe.3 said:
Cheers for the reply! Unfortunately I don't have an adapter to put the rom on the phone. I'll order one now, always good to have for situations like this.
Any other way of getting the phone up and running sooner? If not, no problem, I'll just have to wait for the adapter.
Click to expand...
Click to collapse
Sure there must be a fastboot method but didn't tried it yet, i had this phone 3 days ago
Not sure if after formatting data and reboot to twrp you can copy the rom from pc to phone.
One more thing if you use fastboot method be sure not to relock the bootloader cause you may brick ur phone.
If you want to install xiaomi.eu rom dont just wipe data but you have to format data then type yes. Reboot to twrp again. And at twrp recopy the xiaomi.eu rom.
Sent from my MI 8 using Tapatalk
Flash last MIUI global dev. Flash twrp. Wipe only data. Transfer Rom to phone. Flash Xiaomi eu Rom. Done
ariekumbang said:
If you want to install xiaomi.eu rom dont just wipe data but you have to format data then type yes. Reboot to twrp again. And at twrp recopy the xiaomi.eu rom.
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
the only right answer, all other are more or less useless.
you need to wipe data, then format data (confirm with yes)
after that, hold power+up to reboot in twrp again
(or go to mainmenu and choose reboot to recovery),
connect your Mi8 with Usb cable to PC and copy the xiaomi.eu rom to your mi8
and then flash it.
gm007 said:
One more thing if you use fastboot method be sure not to relock the bootloader cause you may brick ur phone.
Click to expand...
Click to collapse
Oh yes, thank you for the reminder, that slipped my mind with this whole mess.
ariekumbang said:
If you want to install xiaomi.eu rom dont just wipe data but you have to format data then type yes. Reboot to twrp again. And at twrp recopy the xiaomi.eu rom.
Click to expand...
Click to collapse
Cheers for the advice, I'll make sure to format before installing. Only issue now is that I can't get the rom onto the phone to install it. Do you reckon if I format the data through TWRP it will then allow me to copy over the rom onto the device? Currently, unless in fastboot, the laptop doesn't recognise the device - constantly reboots the phone causing it to connect and disconnect.
SPOCK_VULKAN said:
Flash last MIUI global dev. Flash twrp. Wipe only data. Transfer Rom to phone. Flash Xiaomi eu Rom. Done
Click to expand...
Click to collapse
I like the sound of this solution but I have a few questions/need clarification as this mess has made me doubt myself (no issue flashing my previous phone mi5)
I downloaded the Global rom from here: http://en.miui.com/download-346.html#523 (just want clarification this is the official rom) I have the latest version of the miFlash. Am I right in thinking, put phone into fastboot, launch tool, locate unzipped rom folder, select 'Clean all' (and not save user data / clean all and lock (presume this means bootloader)) and click Flash??
And then do I start again, flash TWRP and hope it works?
deepblue2000 said:
the only right answer, all other are more or less useless.
you need to wipe data, then format data (confirm with yes)
after that, hold power+up to reboot in twrp again
(or go to mainmenu and choose reboot to recovery),
connect your Mi8 with Usb cable to PC and copy the xiaomi.eu rom to your mi8
and then flash it.
Click to expand...
Click to collapse
If I do this (wipe data and format) will the laptop detect the device to allow me to move the rom onto the phone, currently it doesn't (well it loops between connecting and disconnecting when in TWRP, no issue detecting in fastboot)
normally if twrp is launched, you can copy files as usual from pc to your Mi8
should be a stable connection.. (Win7/10 or any other Win)
if it keeps connecting/disconnecting you can try an other usb port.
do you use the right twrp ?
https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-0-mi-8-t3837745
and you enabled usb debugging in settings before you flashed twrp ?
(I think without it will not work, even to flash twrp it is needed, so you did it)
deepblue2000 said:
the only right answer, all other are more or less useless.
you need to wipe data, then format data (confirm with yes)
after that, hold power+up to reboot in twrp again
(or go to mainmenu and choose reboot to recovery),
connect your Mi8 with Usb cable to PC and copy the xiaomi.eu rom to your mi8
and then flash it.
Click to expand...
Click to collapse
deepblue2000 said:
normally if twrp is launched, you can copy files as usual from pc to your Mi8
should be a stable connection.. (Win7/10 or any other Win)
if it keeps connecting/disconnecting you can try an other usb port.
do you use the right twrp ?
https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-0-mi-8-t3837745
and you enabled usb debugging in settings before you flashed twrp ?
(I think without it will not work, even to flash twrp it is needed, so you did it)
Click to expand...
Click to collapse
I've tried several USB ports and different cables, no luck getting it to connect.
No the TWRP installed is 3.2.1-0611-XIAOMI8, yours uses the code name and seems to be a newer version and more legit, I'm going to flash that onto the phone. I presume do it the way I did it before - fastboot, shift right click to get to cmd line...etc.
I did indeed enable usb debugging when I installed it originally.
By the way, thanks so much for your help, I'm lost without my phone - it was love at first sight
Fastboot Flashing Code
Code:
Fastboot boot Twrp.img
Flash the recovery img again inside twrp and reboot to recovery again and it will stay.
If u are new to twrp, format data in twrp and reboot to recovery again and flash this file https://androidfilehost.com/?fid=3700668719832238534 after that u can flash the rom.
If u have already twrp installed, just flash the img in twrp
Click to expand...
Click to collapse
Actually I'm confused now, is this probably where I went wrong in the first place.
Boot the TWRP img and then flash it through TWRP, I've never done it this way before (have I been doing this worng all along?)
and whats the other file about? Disable_Dm-Verity_FEC_v1.1.zip
Sorry about all the questions
you can flash/update twrp inside twrp itself, but you dont need it.
I never used any tools or bat files, just normally installed adb,
and put the twrp.img in the same folder.
then open cmd:
fastboot flash recovery twrp.img
to boot into twrp again:
fastboot boot twrp.img
never heard from this fec1.1 zip, so ignore it.
you should go to the xiaomi.eu forum for help,
https://xiaomi.eu/community/threads...ing-xiaomi-eu-8-8-30.46378/page-2#post-444327
there are the steps posted what to do
deepblue2000 said:
you can flash/update twrp inside twrp itself, but you dont need it.
I never used any tools or bat files, just normally installed adb,
and put the twrp.img in the same folder.
then open cmd:
fastboot flash recovery twrp.img
to boot into twrp again:
fastboot boot twrp.img
never heard from this fec1.1 zip, so ignore it.
you should go to the xiaomi.eu forum for help,
https://xiaomi.eu/community/threads...ing-xiaomi-eu-8-8-30.46378/page-2#post-444327
there are the steps posted what to do
Click to expand...
Click to collapse
Right, so I got TWRP 3.2.3 installed and seems to be working (not disconnecting and reconnecting) BUT the phone is still not recognsed - It says unspecified in the devices . I ran through the ADB set up, all installed including drivers but still no phone showing up. I hate windows 10 and drivers, can't get them to play nice (or it's me)
I had never any problems with Win10 x64,
I dnever installed any driver for my Mi5/6 and now 8,
win10 detects everything automatically, if you have installed any driver, maybe just
uninstall them and restart win10
deepblue2000 said:
I had never any problems with Win10 x64,
I dnever installed any driver for my Mi5/6 and now 8,
win10 detects everything automatically, if you have installed any driver, maybe just
uninstall them and restart win10
Click to expand...
Click to collapse
AND WE'RE IN!!! THANK YOU, THANK YOU!! If you were here I'd hug you and get you a drink.
Forget my above nonsense and babble, PC wasn't happy with whatever was going on, once I got brave enough and actually followed your instructions in all fell into place!!
So conclusion -
I had the wrong TWRP (3.2.3 is needed)
PC didn't like whatever was happening without the OS
Wiped and formatted through TWRP - Phone was recognised
Dragged Xiaomi.eu rom over - copied perfectly
Flashed rom - successful and the wiped cache again to be safe
Rebooted and my smile came back the moment I saw the 'powered by android' icon
Went through set up and I'm back in.
Mi 8 - bootloop and locked device, no system, help?
Hi guys,
I did a pretty much bad thing on my phone, I've just bought it 2 weeks ago and I was loving the phone, my phone is unlocked but today I was rooting to install google camera with night sight and I don't know why my twpr was really weird, when pressing install all the folder that was showing was very different from youtube videos about mi 8 root and even compared to my old devices, it was showing folders like licence and others, but the weirdest was inside the sdcard folder that was showing a lot of unnamed folders(like this: 54u3hu6ijj4!ji5), the thing got worse when I've flashed magisk and the phone got stuck on bootloop, after that tried to flash a stock global rom from official Mi website on fastboot mode using Mi Flash Toll, what I did wrong is that I didn't see that the Lock option was ticked and than I pressed to flash, everything was going good when my device showed a message saying that the Miui wasn't compatible with my phone. After that I've tried to install TWPR again but my phone was locked by the Mi flash toll and know my device is without system and unlocked. I've also tried to unlock but is saying that my account is not bound to my device, so I have no idea what to do, I'm gonna never root any phone ever, worse thing I did.
Can Anybody know what I can do to unlock the phone?
Sorry about my English, that's not my native language.
So, I have a Global version Mi 9.
Since the Global Beta is now gone, I want to use Xiaomi.eu ROM.
I unlocked bootloader, I flash TWRP, then I even flash the Disable Force Encryption, but every single time I reboot, the recovery reverts back to MI Recovery 3.0.
What am I doing wrong ?
AFAIK, MIUI installs her own recovery after a reboot.
I always download ROM and enter TWRP to flash ROM !
Currently speaking, MI9 TWRP without the other TWRP mod, such as OrangeFox to ensure TWRP won't be replaced by Mi recovery after OTA updated.
I see a magisk app - "TWRP A/B Retention script" may be current solution to help you keep TWRP after OTA but it must be flashed again after OTA updated every time.
Ataemonus said:
So, I have a Global version Mi 9.
Since the Global Beta is now gone, I want to use Xiaomi.eu ROM.
I unlocked bootloader, I flash TWRP, then I even flash the Disable Force Encryption, but every single time I reboot, the recovery reverts back to MI Recovery 3.0.
What am I doing wrong ?
Click to expand...
Click to collapse
You do not understand.
TWRP is NOT replaced after OTA, it is replaced after rebooting, immediately, after flashing it, before I can even upload the .zip file with the custom ROM to install it.
Ataemonus said:
You do not understand.
TWRP is NOT replaced after OTA, it is replaced after rebooting, immediately, after flashing it, before I can even upload the .zip file with the custom ROM to install it.
Click to expand...
Click to collapse
After flashing twrp, are you using fastboot boot twrp? If so, you need instead to use buttons, not the fastboot commands. Flash twrp, then hold vol up and power together until the phone reboots and vibrates, then let go of power but keep holding vol up. That should make twrp stick
reg66 said:
After flashing twrp, are you using fastboot boot twrp? If so, you need instead to use buttons, not the fastboot commands. Flash twrp, then hold vol up and power together until the phone reboots and vibrates, then let go of power but keep holding vol up. That should make twrp stick
Click to expand...
Click to collapse
Exactly.
1) Boot into fastboot
2) fastboot flash recovery twrp.img
3) fastboot reboot (immediately after device reboot, in black screen, hold VOL+ button)
4) TWRP logo will appears
Yes, I can boot to TWRP, but one time only. I use the volume up button after flashing to enter TWRP.
I need to format the data partition, before I upload the .zip file, and after I format the data partition and I reboot the phone, no more TWRP, MI Recovery 3.0 again.
In the end, I managed to install the xiaomi.eu ROM, but only by pushing the file into the tmp folder and not rebooting after I format the data partition.
Strange how MIUI enforces their own recovery software over TWRP, I had no such issues with the Mi 6, two years ago.
Ataemonus said:
Yes, I can boot to TWRP, but one time only. I use the volume up button after flashing to enter TWRP.
I need to format the data partition, before I upload the .zip file, and after I format the data partition and I reboot the phone, no more TWRP, MI Recovery 3.0 again.
In the end, I managed to install the xiaomi.eu ROM, but only by pushing the file into the tmp folder and not rebooting after I format the data partition.
Strange how MIUI enforces their own recovery software over TWRP, I had no such issues with the Mi 6, two years ago.
Click to expand...
Click to collapse
Which twrp you using?
I tried pretty much all I could find, but settled on 3.3.0-35 from here : https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825
Ataemonus said:
I tried pretty much all I could find, but settled on 3.3.0-35 from here : https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825
Click to expand...
Click to collapse
Yep, that one should deffo be fine, not sure why it's not sticking and you're having the issues, sorry bud
As I said, sorted in the end, now on Xiaomi.eu 9.8.1.
Must have been the latest MIUI beta 9.6.27 that was so ... aggressive with the recovery software
Ataemonus said:
I tried pretty much all I could find, but settled on 3.3.0-35 from here : https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825
Click to expand...
Click to collapse
Install twrp twice in fastboot
having a similar problem, can't install TWRP, the fastboot flash works, no errors, but when I log in ON+VOL UP it comes always MI recovery
claudioita said:
having a similar problem, can't install TWRP, the fastboot flash works, no errors, but when I log in ON+VOL UP it comes always MI recovery
Click to expand...
Click to collapse
Try this.
- Reboot to fastboot
- Flash TWRP
- Disconnect USB cable
- Press and hold Vol+ and power button until TWRP boots
I followed the guide posted here.
sangbuana said:
Try this.
- Reboot to fastboot
- Flash TWRP
- Disconnect USB cable
- Press and hold Vol+ and power button until TWRP boots
I followed the guide posted here.
Click to expand...
Click to collapse
You used twrp for Mi9TPRO or mi 9?
Is your link correct?
claudioita said:
You used twrp for Mi9TPRO or mi 9?
Is your link correct?
Click to expand...
Click to collapse
I am using a Mi 9 (Cepheus), and the TWRP that I am using is from Mauronofrio, version 3.3.1-52. The post to that TWRP is here.
sangbuana said:
Try this.
- Reboot to fastboot
- Flash TWRP
- Disconnect USB cable
- Press and hold Vol+ and power button until TWRP boots
I followed the guide posted here.
Click to expand...
Click to collapse
no it does not work
---------- Post added at 09:15 PM ---------- Previous post was at 08:46 PM ----------
sangbuana said:
Try this.
- Reboot to fastboot
- Flash TWRP
- Disconnect USB cable
- Press and hold Vol+ and power button until TWRP boots
I followed the guide posted here.
Click to expand...
Click to collapse
This worked
https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
now shall I keep read only or allow modifications?
Bit late so not sure if the issue is still prevalent, but did you try flashing TWRP from within TWRP itself?
That's what I did, flashing TWRP within fastboot, then rebooting to enter TWRP (I use buttons for this), then moving the TWRP img to internal storage and use the install function within TWRP to flash the image.
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.
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.