Related
Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
UPDATED:
After some testing the problem only occurs when i take back up for all partitions which isn't mandatory, but when i take back for (system, boot, data) which is enough for working backup and the restoring process is flawless
I did not disable security (PIN code) and restoring was successful
Short answer:
Only take backup for data, system, boot
R1skNt said:
Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
Click to expand...
Click to collapse
Sounds great, but it doesn't work for me. I posted the following comment in another thread:
----------------------------------
I'm having the same problem. I simply cannot restore a TWRP backup. It always produces an error 255.
No, I do not have any "999" folder/files, nor do I have any lockscreen security. I also do not have parallel apps or anything involving multi-user.
I'm extremely experienced at flashing ROMs, as well as performing Nandroids and restoring them.
Nothing I've done is working. As I said, I simply cannot restore the data partition. That's when I get the 255 error. System restores fine, but that's it.
Any ideas?
----------------------------------
Thank you,
Peter
R1skNt said:
Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
Click to expand...
Click to collapse
What about security? Did you have to disable all security before the backup?
I did not disable security (PIN code) and restoring was successful.
R1skNt said:
I did not disable security (PIN code) and restoring was successful.
Click to expand...
Click to collapse
These are the backup settings that I am using. Can you please tell me if you use the same, or if not please share the ones you are using.
lollyjay said:
These are the backup settings that I am using. Can you please tell me if you use the same, or if not please share the ones you are using.
Click to expand...
Click to collapse
Please see the 1st post (update)
PeterGuru said:
Sounds great, but it doesn't work for me. I posted the following comment in another thread:
----------------------------------
I'm having the same problem. I simply cannot restore a TWRP backup. It always produces an error 255.
No, I do not have any "999" folder/files, nor do I have any lockscreen security. I also do not have parallel apps or anything involving multi-user.
I'm extremely experienced at flashing ROMs, as well as performing Nandroids and restoring them.
Nothing I've done is working. As I said, I simply cannot restore the data partition. That's when I get the 255 error. System restores fine, but that's it.
Any ideas?
----------------------------------
Thank you,
Peter
Click to expand...
Click to collapse
For what it's worth, I think I found a solution to why I couldn't restore the data partition. I can't explain why, but now it's working.
Previously, and historically, whenever I did a restore, I always wiped my device: system, data, boot.
This time; however, I did not wipe the device. I simply did the restore and everything worked. Therefore, the problem is somehow associated with the wipe.
Peter
I did a nanroid backup (boot, system, data only as per the instructions) of 5.1.8, rooted with magisk 16.6, ROM, installed lineage OS, than restored my backed up OOS ROM the restore process completed successfully but got stuck on boot logo, flashed magisk again along with the custom kernel but all to no joy, keeps bootlooping, however lineage restored fine and booted, any help be much appreciated, cheers.
joemossjr said:
You guys are crazy and I feel I need to answer your questions. So here we go. So just becuase there's multiple partitions doesn't mean you can dual boot or set up other things. So the way it works is the userdata partition is one partition. There are 2 system partitions for seamless updates two boot partitions for seamless and two firmware slots. In theory yes you can have two roms on both slots. Will they work? No. They will both use the same userdata partitions. So it will be incompatible.now you could in theory have lineage on one slot and oos on the other and if you ever want to go back just format userdata and fastboot --set-active=other to get to the other slot. But that doesn't really seem like a good idea. If you guys have other questions feel free to ask me!
Click to expand...
Click to collapse
This is from another thread here, my understanding is you have to format userdata partition, but please read it by self.
Bonito77 said:
This is from another thread here, my understanding is you have to format userdata partition, but please read it by self.
Click to expand...
Click to collapse
totally irrelevant to this thread, cheers.
"fastboot boot twrp.img
cannot load 'twrp.img': No such file or directory"
What is wrong?
bannannn said:
"fastboot boot twrp.img
cannot load 'twrp.img': No such file or directory"
What is wrong?
Click to expand...
Click to collapse
I assume you're in the directory twrp.img is in and are using the img file instead of the zip file? Also you renamed the img file to twrp.img?
after 6 hours of head banging . i stumbled across this thread. and i got my renovate backup. Since new to oneplus 6 have shifted from samsung S9+. The first post correctly resolved my headache. I have learned.
1. Only Backup sytem , data, boot other partitions of twrp restore needed. not need to restore others
2. Had to format the internal storage as it become fully corrupted with lot of folders with strange names
3. Had to re install full OOS rom zip then boot into sytem
4. reflash twrp via fastboot, install twrp offical .img from twrp.
5 NO WIPES( I think wiping system and then restoring vendor and other partitions was creating issues)
6 Only Restoring Boot , System, Data. and then straight away booting back phone to system worked perfect. didnt require to flash magisk
thanks a lot for this thread OP. :good:
i am an experienced flasher. but i guess to comeback to oxygen OS from other roms you have to install stock full OOS Rom again.
kingwicked said:
after 6 hours of head banging . i stumbled across this thread. and i got my renovate backup. Since new to oneplus 6 have shifted from samsung S9+. The first post correctly resolved my headache. I have learned.
1. Only Backup sytem , data, boot other partitions of twrp restore needed. not need to restore others
2. Had to format the internal storage as it become fully corrupted with lot of folders with strange names
3. Had to re install full OOS rom zip then boot into sytem
4. reflash twrp via fastboot, install twrp offical .img from twrp.
5 NO WIPES( I think wiping system and then restoring vendor and other partitions was creating issues)
6 Only Restoring Boot , System, Data. and then straight away booting back phone to system worked perfect. didnt require to flash magisk
thanks a lot for this thread OP. :good:
i am an experienced flasher. but i guess to comeback to oxygen OS from other roms you have to install stock full OOS Rom again.
Click to expand...
Click to collapse
I followed your guide. But I'm stuck at the boot animation...
RheinPirat said:
I followed your guide. But I'm stuck at the boot animation...
Click to expand...
Click to collapse
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse
I was on 9.0.2
I restored the phone with the MSM tool and updated the ROM to 9.0.2 via manual system update like before.
Question:
Is it not possible to restore the whole system? Or only Data like you said under point 8?
Do I need verity? Because I think my phone is encrypted (flashed never a verity file)
Could I restore the whole system from a full TWRP (all partitions included) - only select data, system?
restoring system and other never worked for me. always failed. but only restoring data partition always worked
when you restore only data. your all apps. settings messages everything will restore even magisk modules.
im not sure about encrypted because. encrypted phone when restoring twrp messed up my whole internal memory. and i had no choice but to wipe it.
so there is no issue with no verity. as it helps not to scramble the internal memory of your device and you wull not loose any data or get stuck on qualcomm dump mode
but remember the steps to verity when installed on already used rom with data. you have to format data to remove encryption
only restoring data is the best option. you can try without no verity to restore i think may work but follow all options i mentioned
but i dont recommend to use with no verity.since using no verity i have never got to wipe my internal memory
I've bricked my device twice after trying to restore and always resorted to just a clean flash of stock using the MSMDownloadTool... wish I'd found this thread sooner as you just solved my third backup restore soft-brick!
I'll also remember to just backup system/data/boot going forward...
Thanks!
kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse
Thanks buddy, It worked like a charm.
About the pin removal, as you siad there is a good tutorial in below link which can be used.
https://www.howtogeek.com/240657/how-to-fix-pin-errors-after-restoring-from-twrp-android-backups/
Thank you!!!
You saved my phone (and life).
I can confirm your procedure is working with my back up made on 10.3.2 using a usb c key.
I just restored the DATA. Nothing else!
Thank you so much!
kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse
/* *** Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included in this ROM/KERNEL
* before flashing it! YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will laugh at you.
* BOOM! goes the dynamite
*/
I have a Moto E5 plus XT1924-5 (rhannah) in my possession. It is the only device in which this guide has been tested. I should serve for the rest of the rhannah and others moto e5 without problems.
My cust LATAM and the compilation version is OPP27.91-25. Do not make the fast route if you do not have exactly the same device with that same compilation number or if you do not know exactly what you are doing.
The guide is divided into parts. First how to backup everything. Then how to root with magisk (for that there is fast and slow way)
What do you need.
- 1 Moto e5 Plus
- 1 Micro Sd card (minimum 4gb)
- Usb Cable
- Adb and fastboot drivers installed
-. Read the complete guide before to understand what they are doing (5 minutes, no bricks)
- 1 Brain.
- Comprehensive reading
FIRST STAGE (COMMON). BACKUP OF EVERYTHING.
Our phone have its own TWRP, works relatively well, except that it does not allow decrypting and therefore mounting the data partition and internal storage.
The steps.
1.- You open the bootloader. Look at any guide to open bootloader in Motorola, it has not science and is common for all motorala phones
2.- Download the Moto e5 play (james) TWRP (https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323)
3.- We put the phone in fastboot. For this, we activate the USB debugging and with the connected phone we write in a CMD "adb reboot-bootloader"
4.- In fastboot we write in our CMD "fastboot boot twrp_james.img". This will start our phone in TWRP without permanently flashing the recovery (for no reason to flash it)
5.- The recovery will take something to start and it will ask us for our key to decrypt data. We need to press cancel as the recovery will fail even with the correct key. DONT MOUNT SYSTEM WITH RW PERMISSION
6.- Go to the backup section, we choose as our destination SD and we backup
ALL except data and cache.
7.- Restart the cell phone and we put our backup in one or more safe place (the misfortunes happen)
With this we already have a backup of boot and system so we will not have problems if we make mistakes later
SECOND STAGE (THE DIFFICULT ROUTE) Patching our own boot.img for magisk
1.- In android we download and install he last magisk manager APK (available in my google drive account https://drive.google.com/open?id=1XD7Q7NXmchTNsSJ-oqt2TOXO8osroVJp)
2.- We open it, we go to setting and in "Update Channel" we activate the beta channel of updates (THE DEVICE WILL ENTER IN BOOTLOOP WITHOUT WITHOUT THIS STEP)
3.- In the main screen of magisk we are going to install, we accept to install the version of magisk 16.7 or superior (by no reason a lower one) and we go to "Patch boot image file", we select the file boot.emmc.win of our backup and We wait for you to patch our boot. (sdcard/TWRP/ Backups /ZL5223F3V8 / DATE /)
4.- Magisk will generate a patched boot in /internalstorage/MagiskManager/patched_boot.img
5.- Copy patched_boot.img to our computer, put the phone in fastboot mode and flash the patched_boot.img with the command fastboot flash boot patched_boot.img, and later restart the phone.
Ready!. Magisk perfectly installed our phone. In my case, safety.net passes without problems.
Second stage. (The easy way). SAFE ONLY in the variants indicated
0- Open bootloader
1.- Make the backups (iam not responsable of this)
2.- put the phone in fastboot mode
3.- Flash my boot.img patched for magisk "fastboot flash boot patched_boot.img"
Moto e5 plus XT1924-5 OPP27.91-25
https://drive.google.com/file/d/1XHtV1rI1cDPQCAw8otuBRxeSzNBzKWQn/view?usp=sharing
Moto e5 plus XT-1924-8 (Thanks Arslan_Rulex)
http://www.mediafire.com/file/zu9mefxd397nr1f/patched_boot.img/file
Moto e5 plus XT1924-7 (MetroPCS) (Thanks theUsualSuspexx)
https://drive.google.com/open?id=1UzP5NEBLD3_ex_zU2EoijVFs1uiGBEMI
Backups TWRP
Moto e5 plus rhannah xt1924-5 (OPP27.91-25.) Include twrp backup of rooted boot partition with system partition, and untouched boot partition (separated)
https://drive.google.com/open?id=1Vu0CvgBc0QeSxWOLyRgcMykvJ9ckgQy_
I hope you send yours, since there is only one fastboot image for this phone.
Thanks a lot, now im root in my e5 plus OPP27.91-41, via THE DIFFICULT ROUTE. the easy route give me a softbrick, :highfive:
folken2003 said:
Thanks a lot, now im root in my e5 plus OPP27.91-41, via THE DIFFICULT ROUTE. the easy route give me a softbrick, :highfive:
Click to expand...
Click to collapse
What rom are you using bike friend e5?
Rodneyy said:
What rom are you using bike friend e5?
Click to expand...
Click to collapse
the stock rom
In case I want to download and install an OTA update, is it possible to undo this by uninstalling Magisk (and its modules, Exposed, etc.) and reinstall the old boot.img via TWRP? Or would that brick the device?
Hinterecke said:
In case I want to download and install an OTA update, is it possible to undo this by uninstalling Magisk (and its modules, Exposed, etc.) and reinstall the old boot.img via TWRP? Or would that brick the device?
Click to expand...
Click to collapse
In theory, reinstalling your unmodified stock boot image will remove all traces of systemless root. On OTA installations with most Moto devices, the update.zip performs a number of checksums in order to verify that certain partitions are unaltered. Your /recovery, /boot, /system, /oem, and /vendor partitions are typically included in these checksums. Even if these partitions have never been altered, an OTA will nevertheless fail if any of the aforementioned partitions have ever been mounted as r/w, even if they were not altered or modified. So, if you've ever mounted any of these partitions as r/w via TWRP, your OTA will fail, but the likelihood of a brick is extremely slim. The best way to prepare your device for an OTA is to flash a full factory firmware package via fastboot or RSD Lite. RELOCKING THE BOOTLOADER IS NEVER NECESSARY ON A MOTO DEVICE FOR INSTALLING AN OTA UPDATE.
Alternatively, you may use a UTF-8 encoding capable file editor to remove checksums from your captured OTA package. Then, you can flash it with TWRP even on a rooted device.
So to fully answer your question, you would want to install stock recovery and boot image via fastboot, not TWRP, since the OTA will fail with a custom recovery. The OTA will need to be installed via stock recovery, not TWRP.
I used @avilav 's rooting method he described over here and didn't install TWRP because it would be useless, I actually read the big warning, so still on stock recovery.
Don't have the factory firmware for my rhannah XT-1924-1 (reteu) either so flashing that is not much of an option. Maybe I should just leave it this way cause most MOTO updates, for the cheaper devices, are mostly just security updates, no new features, software, etc.
MotoJunkie01 said:
In theory, reinstalling your unmodified stock boot image will remove all traces of systemless root. On OTA installations with most Moto devices, the update.zip performs a number of checksums in order to verify that certain partitions are unaltered. Your /recovery, /boot, /system, /oem, and /vendor partitions are typically included in these checksums. Even if these partitions have never been altered, an OTA will nevertheless fail if any of the aforementioned partitions have ever been mounted as r/w, even if they were not altered or modified. So, if you've ever mounted any of these partitions as r/w via TWRP, your OTA will fail, but the likelihood of a brick is extremely slim. The best way to prepare your device for an OTA is to flash a full factory firmware package via fastboot or RSD Lite. RELOCKING THE BOOTLOADER IS NEVER NECESSARY ON A MOTO DEVICE FOR INSTALLING AN OTA UPDATE.
Alternatively, you may use a UTF-8 encoding capable file editor to remove checksums from your captured OTA package. Then, you can flash it with TWRP even on a rooted device.
So to fully answer your question, you would want to install stock recovery and boot image via fastboot, not TWRP, since the OTA will fail with a custom recovery. The OTA will need to be installed via stock recovery, not TWRP.
Click to expand...
Click to collapse
+1 .If you never mount system rw before backup you should not have problems. It is not necessary to do it with this way of rooting, and in theory if you make a backup system-image you should not have problems , since that is a bit-by-bit backup
help me
folken2003 said:
Thanks a lot, now im root in my e5 plus OPP27.91-41, via THE DIFFICULT ROUTE. the easy route give me a softbrick, :highfive:
Click to expand...
Click to collapse
como lo hiciste?
mickeynews said:
como lo hiciste?
Click to expand...
Click to collapse
RTFM
I have the Boost Mobile (Sprint) version which shows as XT1924-8 in the Hardware tab in settings. It has the Snapdragon 435 1.4Ghz octacore w/ 3GB ram 32GB rom. I was able to follow these steps to unlock the bootloader, fastboot into TWRP, did a backup, install magisk manager, patch the boot image and then flash it via fastboot. I might try to get unltd tethering working but for now WOOOOOO-HOOOOOO, this was a rush!
reaper-death said:
I have the Boost Mobile (Sprint) version which shows as XT1924-8 in the Hardware tab in settings. It has the Snapdragon 435 1.4Ghz octacore w/ 3GB ram 32GB rom. I was able to follow these steps to unlock the bootloader, fastboot into TWRP, did a backup, install magisk manager, patch the boot image and then flash it via fastboot. I might try to get unltd tethering working but for now WOOOOOO-HOOOOOO, this was a rush!
Click to expand...
Click to collapse
That's excellent news. You are encouraged to start a rooting tutorial thread for the xt1924-8. By the way, upload me a system image and boot image from a TWRP backup of your device and I'll compile a TWRP flashable stock ROM for the device.
MotoJunkie01 said:
That's excellent news. You are encouraged to start a rooting tutorial thread for the xt1924-8. By the way, upload me a system image and boot image from a TWRP backup of your device and I'll compile a TWRP flashable stock ROM for the device.
Click to expand...
Click to collapse
Sure, I'm uploading the files to mediafire and should be up in a little while.
As for the tutorial basically I did ALMOST everything. I didn't flash twrp and I didn't flash noverity. I did get stuck with no boot when I flashed the patched boot img but figured it out (update channel wasn't set to beta). To fix that boot issue I restarted back to the bootloader then booted twrp and then restored just my boot image from the backup. Then I did the magisk patching and then flashed it and this time I got root.
reaper-death said:
Sure, I'm uploading the files to mediafire and should be up in a little while.
As for the tutorial basically I did ALMOST everything. I didn't flash twrp and I didn't flash noverity. I did get stuck with no boot when I flashed the patched boot img but figured it out (update channel wasn't set to beta). To fix that boot issue I restarted back to the bootloader then booted twrp and then restored just my boot image from the backup. Then I did the magisk patching and then flashed it and this time I got root.
Click to expand...
Click to collapse
Ok. Got it. You basically followed standard protocol based on the tutorial for other variants.
Cool. Once you get me the files I should be able to cook up the ROM and post sometime tomorrow. Thanks for your efforts and your feedback. This will help other members with your variant.
Ok, here is the link:
http://www.mediafire.com/?6862xg60zi8ai
Edit: I also was able to pull the stock recovery img using the XDA TWRP app in android.
c̶a̶n̶ ̶s̶o̶m̶e̶o̶n̶e̶ ̶p̶l̶e̶a̶s̶e̶ ̶u̶p̶l̶o̶a̶d̶ ̶t̶h̶e̶ ̶m̶e̶t̶r̶o̶p̶c̶s̶ ̶o̶r̶ ̶t̶ ̶m̶o̶b̶i̶l̶e̶ ̶T̶W̶R̶P̶ ̶b̶a̶c̶k̶u̶p̶?̶ ̶t̶h̶a̶n̶k̶s̶
hi how do you install the twrp backup you posted
seantello97 said:
hi how do you install the twrp backup you posted
Click to expand...
Click to collapse
Just like any twrp backup. Put it in your twrp/backups/*your phone's serial number*/*put backup here*
Stuck in bootloader
Hi thanks for that. I flashed Magisk on my e5 plus and rebooted but it takes me to bootloader every time. any ideas?
Hi the boot.img isn't showing up where i put it
This TWRP recovery is compiled from source & not official yet
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Prerequisites
1. Unlocked bootloader.
Bugs
1. No bugs
2. If you have found a bug, please consider posting it to my GitHub Issues.
Instructions
1. Go to the fastboot mode.
2. Download the recovery.img and transfer it to the adb folder.
3. Open the cmd/terminal and change directory into the adb folder.
4. Now confirm/check that device is connected by typing:-
Code:
fastboot devices
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
Code:
fastboot flash recovery twrp-name.img
BooM ! TWRP flashed successfully.
6. Now unplug your device and then hold power button untill the phone turned off,after that press power button while holding vol down(-) button simultaneously and you will boot into TWRP recovery mode.
Enjoy !
Downloads
Official TWRP Website : https://twrp.me/umidigi/onemax.html
GitHub Release : Here (release name : TWRP-UMIDIGI-One_Max)
Version Information
ROM OS Version: 8.1.x Oreo
Source Code: Device Tree
Based On: TWRP
Credits
Omni Team for minimal TWRP source
@chankruze (myself) for device tree and compilation.
SUPPORT
Official Telegram Group
Official Telegram Channel
Hey ! Good job ! I tried building my own TWRP today but then noticed someone already did it ! Does encryption work ? I cant seem to decrypt the partition after flashing your TWRP.
EDIT : Couldn't wait, ended up formatting with encryption disabled via a zip + magisk
I've then proceeded to flash some GSI for Android 9 (even tried Q Beta 3) and if we want 9.0 one day, some heavy work will be needed : Cellular doesn't work; other than that, it all seems fine to me, camera is only 12mpx, front is 13mpx. Haven't tested more, i'm back to stock
EDIT 2: After comparing camera from stock and gsi, GSI wins easily. The camera is not as slow as stock.
Are there any decent ROMs yet for this phone? LineageOS would be fantastic.
@kgoerbig not to my knowledge. Maybe I'll try porting a 9.0 GSI soon.
I'm not sure if this is helpful or not, but Umidigi posts stock ROM on there forum. Can ROMs be ported based on there code? Or is it more complicated then that?
https://community.umidigi.com/m/?a=viewthread&tid=18692
_cab13_ said:
Hey ! Good job ! I tried building my own TWRP today but then noticed someone already did it ! Does encryption work ? I cant seem to decrypt the partition after flashing your TWRP.
EDIT : Couldn't wait, ended up formatting with encryption disabled via a zip + magisk
I've then proceeded to flash some GSI for Android 9 (even tried Q Beta 3) and if we want 9.0 one day, some heavy work will be needed : Cellular doesn't work; other than that, it all seems fine to me, camera is only 12mpx, front is 13mpx. Haven't tested more, i'm back to stock
EDIT 2: After comparing camera from stock and gsi, GSI wins easily. The camera is not as slow as stock.
Click to expand...
Click to collapse
I have tested LineageOS 16.0 GSI Android 9.0 (and many others ...) and it works well, even GSM and Camera.
The only thing I cannot have is a complete root : I install Magisk 19.3 correctly, but applications cannot get root permission (Titanium Backup cannot have su permission)
Hi to all!!!
I've unlocked bootloader, flashed twrp in post but when I power Off and On+Vol - my device doesn't power up...
Also if I make fastboot reboot recovery, my device reboot in fastboot mode again...
What's wrong??? I would test Descendant_ThreeDotZero_arm64_aonly rom!!!!
Pls Help me!!!!
silviuss82 said:
Hi to all!!!
I've unlocked bootloader, flashed twrp in post but when I power Off and On+Vol - my device doesn't power up...
Also if I make fastboot reboot recovery, my device reboot in fastboot mode again...
What's wrong??? I would test Descendant_ThreeDotZero_arm64_aonly rom!!!!
Pls Help me!!!!
Click to expand...
Click to collapse
If you use the stock boot.img with an GSI system image, it will not boot, you must first flash Magisk.zip before reboot!
It will disable dm-verity, and you can boot after.
If it continue reboot in bootloader mode, use spflashtool to flash a stock rom and all will be right
Or if you have a TWRP backup, restore all partitions except boot/recovery/cache/system/data and you can boot
@ dreambo Can you make a writeup of properly unlocking the bootloader/rooting? Or did you use these methods?
https://community.umidigi.com/forum.php?mod=viewthread&tid=17376
https://www.youtube.com/watch?v=xM_M5XP--Z8&t=176s
I should be receiving my Umidigi One Max in a day or so, and do not want to bork anything up! I have SPflash installed both on a Win10 laptop, and on a Ubuntu Linux machine.
dreambo said:
If you use the stock boot.img with an GSI system image, it will not boot, you must first flash Magisk.zip before reboot!
It will disable dm-verity, and you can boot after.
If it continue reboot in bootloader mode, use spflashtool to flash a stock rom and all will be right
Or if you have a TWRP backup, restore all partitions except boot/recovery/cache/system/data and you can boot
Click to expand...
Click to collapse
kgoerbig said:
@ dreambo Can you make a writeup of properly unlocking the bootloader/rooting? Or did you use these methods?
https://community.umidigi.com/forum.php?mod=viewthread&tid=17376
https://www.youtube.com/watch?v=xM_M5XP--Z8&t=176s
I should be receiving my Umidigi One Max in a day or so, and do not want to bork anything up! I have SPflash installed both on a Win10 laptop, and on a Ubuntu Linux machine.
Click to expand...
Click to collapse
You do not need to unlock you phone, mine is rooted with Magisk and have TWRP installed without unlock bootloader.
Just use spflashtool to flash a stock rom, but replace the recovery by TWRP and the boot.img by magisk_patched.img one.
Here how I do exactly:
1- in my running stock rom, I install MagiskManager and install Magisk by choosing the last option (patch existing boot.img)
2- give it your stock boot.img (extracted from stock rom) and it create for you /sdcard/Download/magisk_patched.img
3- use this to replace your stock boot.img and use also TWRP.img to replace stock recovery.img and flash the whole rom with SPFlashTool
Can you backup with TWRP with a locked bootloader? Isn't write access blocked with a locked bootloader?
dreambo said:
You do not need to unlock you phone, mine is rooted with Magisk and have TWRP installed without unlock bootloader.
Just use spflashtool to flash a stock rom, but replace the recovery by TWRP and the boot.img by magisk_patched.img one.
Here how I do exactly:
1- in my running stock rom, I install MagiskManager and install Magisk by choosing the last option (patch existing boot.img)
2- give it your stock boot.img (extracted from stock rom) and it create for you /sdcard/Download/magisk_patched.img
3- use this to replace your stock boot.img and use also TWRP.img to replace stock recovery.img and flash the whole rom with SPFlashTool
Click to expand...
Click to collapse
kgoerbig said:
Can you backup with TWRP with a locked bootloader? Isn't write access blocked with a locked bootloader?
Click to expand...
Click to collapse
If you can run the TWRP with a locked bootloader (and you can in case of umidigi one max) you can do any thing
dreambo said:
If you can run the TWRP with a locked bootloader (and you can in case of umidigi one max) you can do any thing
Click to expand...
Click to collapse
One last question. =)
Which boot file from stock did you use to patch with?
Downloadable from: https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
UMIDIGI One Max V1.0
or
UMIDIGI One Max E V1.0
kgoerbig said:
One last question. =)
Which boot file from stock did you use to patch with?
Downloadable from: https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
UMIDIGI One Max V1.0
or
UMIDIGI One Max E V1.0
Click to expand...
Click to collapse
I have used the European one, UMIDIGI One Max E V1.0
So I just received my One Max today. I was able to patch the boot image, and root the phone. I also, installed TWRP, but I'm running into an issue. From TWRP, I formatted with a normal wipe, It asked "Do you want to do this, it wipes data encryption Etc". I typed yes, and it did it's thing. Rebooted. Setup my basic settings on the phone. I rebooted back into TWRP, and it immediatly asked for a "decryption" password. It also won't allow me to mount internal partitions or sdcard. This even after I rooted via a patched boot file, and verified root access while booted in android (with root verify app). What am I doing wrong for TWRP to gain access to storage?
"Couldn't wait, ended up formatting with encryption disabled via a zip + magisk"
How did you format without encryption? I try to format from TWRP, type 'yes' , to verify, and encryption is still active. I'd like to disable encryption, so that I can properly backup everything from TWRP.
kgoerbig said:
So I just received my One Max today. I was able to patch the boot image, and root the phone. I also, installed TWRP, but I'm running into an issue. From TWRP, I formatted with a normal wipe, It asked "Do you want to do this, it wipes data encryption Etc". I typed yes, and it did it's thing. Rebooted. Setup my basic settings on the phone. I rebooted back into TWRP, and it immediatly asked for a "decryption" password. It also won't allow me to mount internal partitions or sdcard. This even after I rooted via a patched boot file, and verified root access while booted in android (with root verify app). What am I doing wrong for TWRP to gain access to storage?
Click to expand...
Click to collapse
Search in xda forum a zip that you can flash with TWRP before installing the Magisk zip from TWRP.
its name is disable_dm_verity????.zip, it disable in the boot.img the encryption.
After that format the data partition (format and not wipe, it's important!) and reboot normally, and your data partition will not be encrypted
dreambo said:
Search in xda forum a zip that you can flash with TWRP before installing the Magisk zip from TWRP.
its name is disable_dm_verity????.zip, it disable in the boot.img the encryption.
After that format the data partition (format and not wipe, it's important!) and reboot normally, and your data partition will not be encrypted
Click to expand...
Click to collapse
I eventually found all the correct files to remove encryption. I also installed AOSP. I'm kind of torn between the stock and AOSP. AOSP has better performance, but one annoying aspect is that I cannot find anywhere in the settings to switch the navigation buttons in AOSP (Back button is on the far left, I like it on the right side). Seems trivial, but it's annoying. I can now fully backup & restore in TWRP, which makes life a lot easier.
kgoerbig said:
I eventually found all the correct files to remove encryption. I also installed AOSP. I'm kind of torn between the stock and AOSP. AOSP has better performance, but one annoying aspect is that I cannot find anywhere in the settings to switch the navigation buttons in AOSP (Back button is on the far left, I like it on the right side). Seems trivial, but it's annoying. I can now fully backup & restore in TWRP, which makes life a lot easier.
Click to expand...
Click to collapse
Which AOSP ? where do you found it ?
dreambo said:
Which AOSP ? where do you found it ?
Click to expand...
Click to collapse
This thread:
https://forum.xda-developers.com/android/development/umidigi-one-max-custom-rom-modding-t3942521
This Rom
https://github.com/phhusson/treble_experimentations/releases
Do a complete backup of stock from TWRP onto microsd or USB first! System, data, modem, nvram partitions etc. That way you can restore from TWRP, and not lose os, data, or nvram (IMEI).
Specifically, system-arm64-aonly-gapps-su.img.xz
1. Download and extract file you downloaded, onto your phone.
2. Do a format (type yes)
3. Install from TWRP as "image".
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery
3. Latest adb & fastboot files
4. Stock ROM ZIP files
5. Stock Recovery [OPTIONAL]
Custom Recovery Method:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_*.zip /sdcard or MTP
3. Wipe data, cache & dalvik (format data if stuck at boot animation)
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip. Your device will have Stock Recovery with Stock ROM. Finally Reboot.
Fastboot Method:
Note: Following process formats internal storage, so backup the internal storage files. If your device is in Stock ROM & somehow system partition is messed up just flash only system.
1. Download required Fastboot files
2. If downloaded 7z files, extract system.img file.
3. Enter
Code:
fastboot -w && fastboot erase system && fastboot flash recovery recovery.img && fastboot flash boot boot.img && fastboot flash vbmeta vbmeta.img && fastboot flash dtbo dtbo.img && fastboot flash system system.img && fastboot reboot
4. It takes a while to flash System partition, have patience.
5. Device reboots to system if everything is flashed successfully.
Stock Recovery Method:
1. Download Stock ROM OZIP Files & Stock Recovery
2. Copy *.ozip to sdcard or internal storage.
2. Goto fastboot & enter fastboot flash recovery recovery.img
3. Reboot to recovery, wipe (1st option). Then go back to main menu Install from storage locate the *.ozip file & install.
I'm sorry, but this doesn't work for me..stuck with the rooted but uninstalled magisk OS.. :'(
ceesiama said:
I'm sorry, but this doesn't work for me..stuck with the rooted but uninstalled magisk OS.. :'(
Click to expand...
Click to collapse
zip isn't installed successfully? can you also send screenshot, so I can help you.
4j17h said:
zip isn't installed successfully? can you also send screenshot, so I can help you.
Click to expand...
Click to collapse
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
ceesiama said:
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
Click to expand...
Click to collapse
ok no problem, so what do you want to know about? Clear data, cache, dalvik after or before flashing stock zip it won't bootloop. Yes, since device is decrypted lock screen doesn't work. Coming to Magisk, yes that method is not reliable. I have figured out 100% working way which works for everyone & doesn't fail anytime. Maybe I will make a new guide soon or ...Mod edit: Link to Telegram removed
4j17h said:
ok no problem, so what do you want to know about? Clear data, cache, dalvik after or before flashing stock zip it won't bootloop. Coming to Magisk, yes that method is not reliable. I have figured out 100% working way which works for everyone & doesn't fail anytime. Maybe I will make a new guide soon or ...Mod edit: Link to Telegram removed
Click to expand...
Click to collapse
I'm sorry I mistyped in the above comment, when i followed your method, zip installed successfully but it bootlooped into stock recovery everytime. I hope that clarifies a bit. I''ll be very grateful if you can help me..
ceesiama said:
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
Click to expand...
Click to collapse
Try install magisk manager, maybe ur device still rooted
haditriw said:
Try install magisk manager, maybe ur device still rooted
Click to expand...
Click to collapse
no that's not how magisk works in Realme 3 Pro, if device is restarted there will be no magisk. You need to goto fastboot then goto recovery, it boots to system. We have magisk. Yes this method tricky. I am going to publish new guide, it will be simple & straight forward.
Bricked/ Bootlooping
4j17h said:
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery or Pitch Black Recovery
3. Latest adb & fastboot files
4. Stock ROM zip files: RMX1851_A15
5. Stock Recovery [OPTIONAL]
Follow the below steps:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_A15.zip /sdcard or MTP
3. Wipe data, cache & dalvik
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip, Reboot to System. You get the stock Recovery & stock ROM.
Previous Firmware: RMX1851_A14 Google Drive || AndroidFileHost || Mega Cloud storage
Note: This guide will be updated in coming days with fastboot flash files & custom recovery flashable files with latest versions.
Click to expand...
Click to collapse
pls help me, im stuck on bootlooop :'(
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
4j17h said:
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery or Pitch Black Recovery
3. Latest adb & fastboot files
4. Stock ROM zip files: RMX1851_A15
5. Stock Recovery [OPTIONAL]
Follow the below steps:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_A15.zip /sdcard or MTP
3. Wipe data, cache & dalvik
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip, Reboot to System. You get the stock Recovery & stock ROM.
Previous Firmware: RMX1851_A14 Google Drive || AndroidFileHost || Mega Cloud storage
Note: This guide will be updated in coming days with fastboot flash files & custom recovery flashable files with latest versions.
Click to expand...
Click to collapse
pls help me, im stuck on bootloop :'(
malakaz27 said:
pls help me, im stuck on bootlooop :'(
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
pls help me, im stuck on bootloop :'(
Click to expand...
Click to collapse
I have seen you have started a new thread of bootloop. Is this because you flashed one of these stock zip? you were going back to stock from los?
this method worked perfectly fine for me. i tried both lineage os roms available and both of them caused bootloop or end up destroying boot. so thanks to developer for making this zip file.
4j17h said:
I have seen you have started a new thread of bootloop. Is this because you flashed one of these stock zip? you were going back to stock from los?
Click to expand...
Click to collapse
hi i am stuck in bootloop after flashing all stuff in fastboot guide
leo77g said:
hi i am stuck in bootloop after flashing all stuff in fastboot guide
Click to expand...
Click to collapse
bootloop to recovery? have you tried fastboot -w usually this should boot to system or else flash stock recovery, wipe full. This should definitely get back the device to system.
4j17h said:
bootloop to recovery? have you tried fastboot -w usually this should boot to system or else flash stock recovery, wipe full. This should definitely get back the device to system.
Click to expand...
Click to collapse
formatting worked and thanx for help )
Moderators' Announcement: I've removed the links to Telegram and references to it. This is not a development thread, and support is to be provided through XDA. Many posts proved this has not been the case!
You may be asking, "Why was my Telegram or Whatsapp thread closed?"
Well, it's just becoming too much.
Going forward, we will only allow one Telegram chat link on a development thread by the ROM's developer and only if thorough support is still provided in the ROM thread on XDA.
All discussion channels, photography channels, whatnot channels will be strongly discouraged and removed with immediate effect. Please reference the forum rules:
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
Also, we now have an official XDA Discord Server. We would encourage you to try it out.
Announcing the Official XDA-Developers Discord Server
FYI
Thanks,
The Moderation Team
Click to expand...
Click to collapse
Need Help
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
ResSetOk said:
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
Click to expand...
Click to collapse
since your bootloader is locked, all you can do is wipe full data or flash back P2Q then format & then flash Q2P.
4j17h said:
since your bootloader is locked, all you can do is wipe full data or flash back P2Q then format & then flash Q2P.
Click to expand...
Click to collapse
I did Wipe before and after firmware, on P2Q is stitched without problems, but under firmware in Q2P in recovery writes, that not managed wipe userdata. The data was not encrypted, the password is not asked.
do you have video for Fastboot Method ?
[No message]
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
User699 said:
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
Click to expand...
Click to collapse
It didnt work, "failed to decrypt data" i typed the right password
#JKTheBaskieBoy said:
It didnt work, "failed to decrypt data" i typed the right password
Click to expand...
Click to collapse
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
the correct and recommend way to install TWRP is
Flash TWRP
Erase userdata partition <~ it's important to do this as soon as possible since booting your device would just encrypt everything again
Format userdata partition
by doing this you would be able to access data partition files and folder would not be random letters.
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Sorry for the late reply. Earlier i just gave up on installing the custom ROM and continued with my stock from. Today a tried again, installed TWRP and turns out it is not showing random letters now. its all regular storage. i didn't even do anything to decrypt it lol it just fixed itself. Now I will install the room myself. Thank you for your help though
Ah sh** here we go again. So i installed the custom rom successfully and everything worked fine, the TWRP too. but when I tried to flash a magisk patched image (the image that I used to root my phone in MIUI) then it got stuck in the boot screen. I had to flash the stock fastboot rom again.. And as expected from my piece of **** that xiaomi calls a phone, TWRP will show encrypted folders, and does not ask for a password. Same problem. Rooted my phone again, using the magisk root image, and it worked like usual, the phone rooted. Now i am stuck again in this bs. I guess I will wait for about 4-5 days and continue using the phone like normal. Maybe it will work again this time. I will try your method here first
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Okay i tried wiping the data, cache and dalvik but it shows a huge essay of "error opening xxx/xxxx" in red text. Data wipe failed.
See you after like 4-5 days... hopefully
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
#JKTheBaskieBoy said:
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
Click to expand...
Click to collapse
I like that you keep trying and finding a solution, even though you had to invest hours to make it work!
Let's hope it will work if you update the OS though – I'd actually suggest a backup of all of your data before you do an update in the future, just to be safe!
#JKTheBaskieBoy said:
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
Click to expand...
Click to collapse
tell me how to turn off a smartphone with a non-working sensor?
you can still use adb push command from pc to transfer files to your phone :
adb push "nameoffile" /sdcard
(place the file in your adb folder) I was able to root a phone that had this issue using this technique.
I think u should flash dm verity becoz when i flashed the rom and flashed dm verity it worked fine