Database Develop

Oneplus 3 decryption Ultimate guide

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!

Huawei eRecovery : "Getting package info failed". Honor 9 Lite

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 ?

[GUIDE] [WIKI] [Realme XT] Unlocking, Unbricking, Custom recovery, GSI guide and more

Realme XT Wiki
For convenience : https://www.androidfilehost.com/?w=files&flid=304989
First things first.
DISCLAIMER : Use this guide at your own risk. I won't be responsible for you bricking your device due to following this guide. It's also necessary to back up your data before you attempt anything.
Realme XT is not really a developer friendly device as they claim to be for the following reasons.
- Bootloader restricts flashing critical partitions and certain fastboot options are disabled like
Code:
fastboot boot recovery.img
- The flash tool is only available to service centres.
- Kernel sources are not actively updated by realme.
- Nil response to developer's queries.
Code:
[B][U]Table of contents :[/U][/B]
- Unlocking the bootloader
- Unbrick guide
- TWRP guide
- Upgrade guide
- Downgrade guide
- Project Treble for Realme XT
- Links
For unlocking the bootloader, follow the official instrutions from here :
https://c.realme.com/in/post-details/1184740422732218368
As of 28/03/20, you can unlock the bootloader in Realme UI. The official guide for XT is still not updated by realme, but the bootloader unlock app tool that was released for realme3pro works for XT.
UNBRICK GUIDE FOR REALME XT : (FASTBOOT)
Most bricks that happen with devices are softbricks. This means you can boot into stock recovery using key combination or you can access fastboot.
Hardbricks are where your device basically does nothing no matter what you do.
If you are on Color OS 6 or realme UI on locked bootloader :
- Switch off your device
- Press volume up + power button hold it until it finishes starting up.
- You will see the recovery menu now
- Press online update and connect it to wifi and follow instructions
If you are on color os 6 on unlocked bootloader :
Prerequisite:
1. You need to have unlocked bootloader
2. Platform tools setup and added to system environmental variables under windows
OR
Just install this : https://forum.xda-developers.com/showthread.php?t=2317790
Since custom ROMS don't deal with critical partitions, there is very less chance that the critical partitions are messed up. Majority of the times you would be fine with just flashing the boot image, system image, vendor image, vbmeta.
Instructions for color os 6 (Android pie firmware) :
Download the stock pie A16 fastboot image from the links section and extract it :
Just flash by executing the following commands :-
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash dtbo dtbo.img
fastboot flash oppo_sec oppo_sec.img
fastboot flash modem modem.img
fastboot flash splash splash.img
fastboot flash DRIVER DRIVER.img
fastboot reboot
If you are on Realme UI on unlocked bootloader :
Prerequisite :
Download the stock Realme UI fastboot image from the links section and extract it :
Note : The zip file has other partitions too. Hopefully, you shouldn't need them.
Just flash the boot,system,vendor and vbmeta by executing the following commands
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash dtbo dtbo.img
fastboot flash oppo_sec oppo_sec.img
fastboot flash modem modem.img
fastboot flash splash splash.img
fastboot flash DRIVER DRIVER.img
fastboot reboot
Guide to Custom Recovery:
Prerequisite:
1. You need to have unlocked bootloader
2. Platform tools setup and added to system environmental variables under windows
OR
Just install this : https://forum.xda-developers.com/showthread.php?t=2317790
TWRP Recovery
Orangefox Recovery
Instructions to install TWRP recovery:
Run this command
Code:
fastboot flash recovery TWRP.img
You can install orangefox recovery by flashing it via TWRP recovery or by extracting the recovery.img from orangefox recovery.zip file.
Upgrade guide :
You can always find the latest update from here : https://www.realme.com/in/support/software-update
Upgrading from android pie to android 10 carries the risk of bricking your device. Be it locked or unlocked. Thus proceed with caution and ONLY use stock recovery to update from android pie to android 10.
If you are on locked bootloader,
Step 1 :Simply download the update of your choice from the Links section and try to open it in stock file manager.
Note : If it doesn't show the update option in stock file manager, just rename the file from *.zip to *.ozip and try again
Step 2 : Press reboot immediately after the flashing is done
Step 3 (Very important) : Pray that everything works. Bricks can happen to anyone.
If you are on unlocked bootloader,
Step 1:In case you already have TWRP working on pie, simply flash the official stock android pie A16 through twrp and let it boot.
Step 2:Now, let it fully boot into the system
Step 3: Go to stock file manager and follow similar instructions as is for locked bootloader that's written above.
Downgrade guide :
Prerequisite:
In case you are in realme UI (Android 10) and want to roll back to android pie for any reason, you need to backup your data and flash stock pie A16 via TWRP
Step 0 : Back up your data and download stock A16 firmware from the links section below
Step 1 : Go to TWRP and flash stock pie
Step 2 : Flash stock pie again
Step 3 : Format data and reboot
Project Treble for Realme XT :-
You could refer here for what works and what doesn't
https://github.com/phhusson/treble_experimentations/wiki/realme-XT
Prerequisite :
1. You need to have unlocked bootloader
2. Platform tools setup and added to system environmental variables under windows
OR
Just install this : https://forum.xda-developers.com/showthread.php?t=2317790
3. You need to be on realme UI (Android 10)
Typically, you could install GSI without even using TWRP.
Step 1: Download any A/B arm64 GSI of your choice
Step 2: Erase userdata using the command
Code:
fastboot -w
Step 3: Flash system.img using fastboot command
Code:
fastboot erase system && flash system system.img
Step 4: Flash RUI vbmeta with flags
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Optional : Flashing TWRP helps with installing magisk and device specific treble fixes and is highly recommended.
USEFUL LINKS :
Recovery (Both stock and TWRP), Fastboot images and Official Updates
https://www.androidfilehost.com/?w=files&flid=304989
Realme XT Android 10 C01 (Realme UI)
https://download.c.realme.com/osupdate/RMX1921EX_11_OTA_1010_all_yuEH87qmmZhw.ozip
Realme XT Android pie A16
https://download.c.realme.com/osupdate/RMX1921EX_11_OTA_0160_all_CcmkxwAnmByA.ozip
Realme XT stock vbmeta Android 10 C01 (Realme UI)

Help!!
I am on coloros 6 (a16) and i have unlocked bootloader (twrp not installed) so how can i update it to rui. Via stock file manager method or just install twrp in a16 and flash rui(c_02) ozip in twrp. So, Which will be a better and safe way to update and avoid bricking the phone according to you.

mehtakush007 said:
I am on coloros 6 (a16) and i have unlocked bootloader (twrp not installed) so how can i update it to rui. Via stock file manager method or just install twrp in a16 and flash rui(c_02) ozip in twrp. So, Which will be a better and safe way to update and avoid bricking the phone according to you.
Click to expand...
Click to collapse
Use the stock recovery for update and wait for official OTA.

Reset Device
My device is locked and now i forgot my password and when i am trying to wipe data from realme ui recovery its asking for password again is there anyway to bypass that security and reset my device please help i cant go to sevice centers right now due to lockdown in my country.

Leamusex said:
My device is locked and now i forgot my password and when i am trying to wipe data from realme ui recovery its asking for password again is there anyway to bypass that security and reset my device please help i cant go to sevice centers right now due to lockdown in my country.
Click to expand...
Click to collapse
So u must wait for that. . Me waiting for tutorial to downgrade realme ui to a16 or. How to unlock bootloader with realmeui firmware.

Leamusex said:
My device is locked and now i forgot my password and when i am trying to wipe data from realme ui recovery its asking for password again is there anyway to bypass that security and reset my device please help i cant go to sevice centers right now due to lockdown in my country.
Click to expand...
Click to collapse
Unfortunately no. you must input password or your data is a lost cause.

krizhiel said:
So u must wait for that. . Me waiting for tutorial to downgrade realme ui to a16 or. How to unlock bootloader with realmeui firmware.
Click to expand...
Click to collapse
The tutorial is already there in the wiki. Although make sure you backup your data first.

PS C:\adb> fastboot flash recovery C:\adb\TWRP_RMX1921_pjgowtham_290320.img
sending 'recovery' (65536 KB)...
it did not flash it just stayed there forever

I have bricked my device. I have a bootloop. Combinations of keys don't work, recovery doesn't show up. Bootloader is locked. Can anyone help?

dmmas21 said:
I have bricked my device. I have a bootloop. Combinations of keys don't work, recovery doesn't show up. Bootloader is locked. Can anyone help?
Click to expand...
Click to collapse
Same problem i have..Any help please..

dmmas21 said:
I have bricked my device. I have a bootloop. Combinations of keys don't work, recovery doesn't show up. Bootloader is locked. Can anyone help?
Click to expand...
Click to collapse
You locked manually?

akashavel said:
You locked manually?
Click to expand...
Click to collapse
yes, me too. And now i have hardbrick and dont know how to fix this without service centre

bro Did You fixed it ?

I am on RMX1921_11_C.04 is there anyway to install custom recovery?

I bought a realme xt and upgraded it to realme ui version c04 but I get some random crash reports I don't know what is it they just randomly pop up 1-2 times per day along with a screenshot I am uploading those please can someone check.

My device bootloop'ed after following your downgrade tutorial. Tried boot unbrick it like your tutorial to no avail

Anyone who is now used to with this device and have done all these steps from Unlocking bootloader to flashing recoveries to installing custom & Stock Roms, can you please tell me what are the senarios in which this device can brick and only restored by Realme service center? I mean what possible error we can make that gives error of boot/recovery destroyed and only needs to visit realme service center?
I am very new to realme, before getting started with unlocking bootloader, i want to be sure about my steps, actually all i need is to use titanium backup for old data transfer of apps, my phone records etc, and most importantly using viper4android. This is all i am going to do after unlocking bootloader.

Raju Sah said:
Same problem i have..Any help please..
Click to expand...
Click to collapse
A reply this late isnt probably useful. But for others who refer this thread, once locked, it can be saved only by flashtool if you cant access stock recovery.

Fastboot commands not working
Hey there.
I am using realme xt with realme UI and i tried to unlock the bootloader. The bootloader is unlocked successfully but the fastboot commands arent working now on the device. This is whats happened while relocking the bootloader and same error for flashing recovery.
D:\Root\platform-tools>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
f40db298 device
D:\Root\platform-tools>adb reboot bootloader
D:\Root\platform-tools>fastboot devices
f40db298 fastboot
D:\Root\platform-tools>fastboot flashing lock
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
D:\Root\platform-tools>fastboot flashing lock
< waiting for any device >
^C
D:\Root\platform-tools>fastboot devices
D:\Root\platform-tools>
this also happened while flashing recovery also. And I am kind of stuck i cant relock the bootloader and cant install custom recovery to root the device.
Kindly, guide me to solve this problem. Thanks in Advance.

Hi, anybody can help me? I want to sell my phone so i wanted to flash stock rom and lock the bootloader. But i dont find any post or something like that to do so... Do you know how can i flash the stock rom and relock the bootloader like we can do with xiaomi phones?

Question [Solved] Unable to install EU ROM :/

Hi everyone, and a happy new year
I need some light please, i don't understand what i'm doing wrong :/
To follow this post, i can't install EU ROM anymore (via TWRP) and i don't know why...
1) i flash the EEA Global via MiFlashTool, all ok
2) i make sure to unlock bootloader, all ok
3) i flash TWRP (official 3.6), all ok
Finally i want to flash 12.5.20.0, or 12.5.17.0 of EU ROM via TWRP/install, the process end up nicelly, no error so reboot, now everytime /data is lost, so it only boot on twrp and nothing is here anymore, need to go back at 1)
That is so frustrating :/
Can anyone enlight me please ?

did you format data after flashing 12.5.20.0

marcel112 said:
did you format data after flashing 12.5.20.0
Click to expand...
Click to collapse
nope, i need to ?
(if i format data, then i'll need to reflash the rom, right ?)

Only fastboot Version available right now bro. Already using it.

If you want to flash 12.5.20 it's impossible to use TWRP.. it's android 12 and fastboot only

marcel112 said:
If you want to flash 12.5.20 it's impossible to use TWRP.. it's android 12 and fastboot only
Click to expand...
Click to collapse
Thanks both of you !
Ok, but when i see files like 12.5.20.0 with a twrp flashing procedure labelled Mi11 Ultra, that let me think i can do it that way, it's misleading, at least :/
So, i flashed the latest 12.6 xiaomi eu rom and it worked
New problem, i then try to use twrp to flash magisk, i do fastboot boot twrp.img and then, /data lost again, so impossible to flash magisk :/
I tried both 3.6 official and 3.5.1 unofficial
p.s.: never set security pin/pass or whatever atm, so it's not a problem with the password

why do you want to try twrp to flash magisk?
copy the boot file from fastboot / images folder to your phone.
boot system, open magisk app, choose install, and search the boot file, patch. once patched, copy the file to the fhe pc.
reboot to fastboot
just type fastboot flash boot yourpatchedbootfile.img
you can type fastboot flash boot and drag the patched file to fastboot line

marcel112 said:
why do you want to try twrp to flash magisk?
copy the boot file from fastboot / images folder to your phone.
boot system, open magisk app, choose install, and search the boot file, patch. once patched, copy the file to the fhe pc.
reboot to fastboot
just type fastboot flash boot yourpatchedbootfile.img
you can type fastboot flash boot and drag the patched file to fastboot line
Click to expand...
Click to collapse
Oh my god, i totally forgot this method
Thank you very much, seems to work !
Solved

Question stuck at bootlogo after installing gsi

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.