Database Develop

Stuck in boot up screen

ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks

JWACK72 said:
ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks
Click to expand...
Click to collapse
What device do you have, XT1095, XT1097, etc? And you are not able to boot into the bootloader using vol down + power correct?

It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP

JWACK72 said:
It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP
Click to expand...
Click to collapse
If it boots to fastboot, it's not dead. Just reflash the recovery and you're good to go.
Sent from my XT1095 using Tapatalk

Was there a resolution for this? I'm having a similar problem. I'm not sure how I got to this status, but here's what I'm dealing with:
Device: XT1095
Bootloader: Unlocked
Rooted, ROM - Resurrection Remix, TWRP
Turning on the phone reaches the RR bootsplash and proceeds to bootloop.
When holding down the power and volume down, it will enter fastboot.
When I try to open TWRP recovery, it'll show the blue TWRP screen and just sit there.
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks

bibbin said:
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks
Click to expand...
Click to collapse
Do you have a USB-OTG device plugged in while trying to start TWRP? If so remove it, you can mount it after TWRP starts if this helps.
Have you tried a different build of TWRP? I'm currently using the one built by invisiblek, one of the CM devs for the victara. It was built and posted on December 8th and is here: http://www.invisiblek.org/twrp/twrp_2.8.7.0-0624b8bd_victara.img
Have you tried flashing the stock recovery to see if that will start? If it does, you could use the factory reset option there and then try reinstalling TWRP. (TWRP has a settings directory in /sdcard and maybe that is corrupted.)
There have been a few people posting with this problem but I've not seen a definitive fix for it.

Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.

bibbin said:
Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.
Click to expand...
Click to collapse
That's interesting, the TWRP Manager has never worked correctly for me although it's been a long time since I've tried it.
To flash manually, you actually need fastboot which is usually installed along with adb. If you open a command window, and type in fastboot and it runs, the rest is pretty easy. If it doesn't run, this thread has the 15 second ADB/Fastboot installer, select to install it system-wide: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Download the recovery image, rename the file to twrp.img, then open a command window in the folder where you downloaded it (type cmd then Enter in the address line at the top of the folder window.)
When the command window is open and the phone is in bootloader mode and connected to the computer with the USB cable, enter the command "fastboot device" (without the quotes) If everything is working it will list the serial number of your phone.
Then enter "fastboot flash recovery twrp.img" (without the quotes) to start the flashing process, ignore the size mismatch message. It will only take a few seconds to complete.
Use the volume down key to highlight recovery, then volume up to select it. Hopefully TWRP will boot up and you'll be good to go!

Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?

bibbin said:
Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?
Click to expand...
Click to collapse
Reflash stock rom from fastboot.
Sent from my XT1095 using Tapatalk

UPDATE: Thanks all. Well, after fiddling around with various methods of reinstalling TWRP, I managed to get it reinstalled and all is back to normal now.

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!

[RECOVERY] Unofficial TWRP 3.3.1-0 recovery for Xiaomi Redmi (olive)

There is now an official version available (xda post). Go use that.

Thanks for your work
---------- Post added at 10:43 PM ---------- Previous post was at 10:37 PM ----------
seprode said:
I compiled TWRP for my own Redmi 8 (olive) and thought I would share. Based on the devicetree for the Redmi 8a (olivelite) by milankragujevic.
I have the global variant with a Tianma display. I can't test if it works on any other variant, use with precaution.
I used it successfully to flash the xiaomi.eu rom and magisk.
You can find the device tree on my GitHub: here
And the image in the release section: here
Installation:
Unlock Bootloader if not already done (Official Tool)
Boot in to fastboot (Powerbutton + volume down)
Run fastboot flash recovery recovery.img (for Windows use Minimal ADB and Fastboot)
Boot in to recovery (Powerbutton + volume up)
If something breaks you can use MiFlash and the stock fastboot rom to go back to reset your phone (phone will also be locked again) or use fastboot to flash the stock recovery (can also be found in the stock fastboot rom).
You can download the fastboot rom here.
Click to expand...
Click to collapse
How can I know if my device Tianma display or not?

yamabokra1 said:
How can I know if my device Tianma display or not?
Click to expand...
Click to collapse
Go in to the phone app and dial *#*#6484#*#*. Under 1 and then LCD you can then find the manufacturer.
I don't know if it actually matters. I read here that it affects devices when using the Redmi 8a recovery. Since I forked the code and have a Tianma display I can't really look in to the problem.

Have you got MTP working while at TWRP? I can't seem to get it right, Windows don't see my phone (adb and fastboot are working). While using adb-sideload I've got error that my mi-globe.zip rom cannot be installed through that method
------ EDIT -----
So, I flashed fastboot stock ROM and recovery. Then flashed this recovery. Booted into stock ROM, copied my custom ROM, rebooted into recovery and still couldn't install - after half of the installation process TWRP shouted that it couldn't mount /system partition. How did you get it to work? And thanks for work!

pulka103 said:
Have you got MTP working while at TWRP? I can't seem to get it right, Windows don't see my phone (adb and fastboot are working). While using adb-sideload I've got error that my mi-globe.zip rom cannot be installed through that method
------ EDIT -----
So, I flashed fastboot stock ROM and recovery. Then flashed this recovery. Booted into stock ROM, copied my custom ROM, rebooted into recovery and still couldn't install - after half of the installation process TWRP shouted that it couldn't mount /system partition. How did you get it to work? And thanks for work!
Click to expand...
Click to collapse
Can you check your LCD is it Tianma display?
"Go in to the phone app and dial *#*#6484#*#*. Under 1 and then LCD you can then find the manufacturer."

pulka103 said:
Have you got MTP working while at TWRP?
Click to expand...
Click to collapse
I recompiled TWRP with MTP enabled and it seems to show up as a device but i can't access data from the device.
I installed the image via a sd-card, but usb-otg or adb push should also work.
pulka103 said:
TWRP shouted that it couldn't mount /system partition.
Click to expand...
Click to collapse
Okay I changed the default mounting point of the system partition. Try again with the new image.

yamabokra1 said:
Can you check your LCD is it Tianma display?
"Go in to the phone app and dial *#*#6484#*#*. Under 1 and then LCD you can then find the manufacturer."
Click to expand...
Click to collapse
I do have a Tianma display. Problem isn't with controls but with the TWRP itself in my case.
Just tried new image, same problem "Checking /system. /system is not mounted! Trying to mount /system RW. /system cannot be mounted. [...] Installation will be aborted."
I am using Mi-Globe right now, gonna try with "clean" Xiaomi.eu.
And still can't access storage through Windows Explorer (but device itself is seen, tested with adb).

So Xiaomi.eu installed kinda. No errors and stuff but won't boot up. After one try it just goes back into TWRP. Using V11.0.3.0 for HM8 (as described by Xiaomi.eu)

luckily, mine has TIANMA display, I'll try while my rm8 is unlocked, thanks bro

@seprode, Reading your post and seen your work, I decided and today I ordered a Redmi 8 (olive) for my self , too.
I am very thankful that there are people like you, pioneers, who open the path, for all of us to follow.
Thank you again for what you are doing for us.
I hope, soon enough, some developer will pay attention to our new phone and , maybe , we will be also able to see new Android (Q ?) roms for it.
I am active involving so far in Samsung NOTE 2(exynos) and Note 4 (snapdragon) and also Xiaomi Redmi 5 plus community
I will do my best and see, if any of these groups will be able , in the future, to do something for our little brother here.
But the path you have open, is the very important first step to it.
KUDOS
:good::good:

@pulka103 You want to try again? I made some changes and got MTP working.

seprode said:
I compiled TWRP for my own Redmi 8 (olive) and thought I would share. Based on the devicetree for the Redmi 8a (olivelite) by milankragujevic.
I have the global variant with a Tianma display. I can't test if it works on any other variant, use with precaution.
I used it successfully to flash the xiaomi.eu rom and magisk.
You can find the device tree on my GitHub: here
And the image in the release section: here
Installation:
Unlock Bootloader if not already done (Official Tool)
Boot in to fastboot (Powerbutton + volume down)
Run fastboot flash recovery recovery.img (for Windows use Minimal ADB and Fastboot)
Boot in to recovery (Powerbutton + volume up)
.
Click to expand...
Click to collapse
Thank for your work !
What about vbmeta as mentioned at milankragujevic ?
And do we need something against dm_verity ?
Edit:
I did the described "simple" way and it works !!!
No need to flash anything else !!!
Great job, Thanks again :good:

seprode said:
I compiled TWRP for my own Redmi 8 (olive) and thought I would share. Based on the devicetree for the Redmi 8a (olivelite) by milankragujevic.
I have the global variant with a Tianma display. I can't test if it works on any other variant, use with precaution.
I used it successfully to flash the xiaomi.eu rom and magisk.
You can find the device tree on my GitHub: here
And the image in the release section: here
Installation:
Unlock Bootloader if not already done (Official Tool)
Boot in to fastboot (Powerbutton + volume down)
Run fastboot flash recovery recovery.img (for Windows use Minimal ADB and Fastboot)
Boot in to recovery (Powerbutton + volume up)
If something breaks you can use MiFlash and the stock fastboot rom to go back to reset your phone (phone will also be locked again) or use fastboot to flash the stock recovery (can also be found in the stock fastboot rom).
You can download the fastboot rom here.
Click to expand...
Click to collapse
I have a problem and maybe some of you can help me. I flashed last recovery.img. After flashing phone reboot itself and boot to system. Next, perform reboot to recovery and it boot to mi-recovery, not twrp. Then I cant boot to system. I have to flash again and then it boot to system.
===EDIT====
Ok, I managed this. After "fastboot flash recovery recovery.img" you have to type "fastboot reboot"

Great Great work I hope you continue updating. Thank you ?

good afternoon, this twrp this worked on redmi 8 olive, if it worked I will for now, obg and thank you already.: D

Ok, so ive tried to install latest xiaomi.eu rom for the redmi olive after flashing twrp, following all the steps from here and other posts, and all I get was reboot everytime. how do i go back to stock? miflash is not working and i dont find any .img to flash back

seprode said:
@pulka103 You want to try again? I made some changes and got MTP working.
Click to expand...
Click to collapse
hey man i fixed up novatek touchscreens on a repack version of your twrp i will include here
Download also i did a PR on your github with the needed changes so your next version will have this fix

Thank for twrp i hope it works on my device but what about custom rom wee need to custom rom ..miui contains lots of ads so that we need some good custom room..and brother replay me as soon as possible.

[email protected] said:
Thank for twrp i hope it works on my device but what about custom rom wee need to custom rom ..miui contains lots of ads so that we need some good custom room..and brother replay me as soon as possible.
Click to expand...
Click to collapse
you should try miui eu

unlock Bootloader
how can i unlock Bootloader for Redmi 8 with out Official Tool

Help! Got bootloop after flashing permissiver_v5 in Evo X Rom (A2)

Hello! Hoping someone can help and guide me in fixing my A2's bootloop. I already searched many forums online, but still no luck.
I flashed a permissiver_v5.zip in Evolution X Rom hoping that it will solve the random reboots, and I got bootloop. I successfully flashed the July stock rom through Miflash, hoping to boot into system, but still bootloop. I flashed the stock firmware and persist zip too in TWRP, but I also got mount persist error. I also need to use fastboot boot twrp.img to get into Twrp since it will disappear after clicking reboot recovery. I tried EDL, but then I got not enough storage error in Miflash.
Hopefully somebody can help me with steps!
LATEST UPDATE:
With the help of KevMetal, I can now use my phone after a week of being hardbricked. At first, my device can't boot to the bootloader or recovery, so what I did was to press the volume down and power button for some time and my phone was detected by the PC. So my device booted to EDL by itself, no need to open the phone. Then I used the 2018 version of MiFlash Tool and flashed the V.10.0.17 of stock Pie ROM from here: https://forum.xda-developers.com/mi-...-t3824849/amp/
After that, I flashed the persist.zip provided by KevMetal (browse in this thread) in recovery since I can't sideload the zip, and it worked fine. I then booted to system and finally there was no bootloop.
I then noticed that the IMEI was gone, so I tried to fix through some guides online but this one worked for me. https://medium.com/@shekhawatkoki/fi...1-2ed533548d32

Ronaldendoma said:
Hello! Hoping someone can help and guide me in fixing my A2's bootloop. I already searched many forums online, but still no luck.
I flashed a permissiver_v5.zip in Evolution X Rom hoping that it will solve the random reboots, and I got bootloop. I successfully flashed the July stock rom through Miflash, hoping to boot into system, but still bootloop. I flashed the stock firmware and persist zip too in TWRP, but I also got mount persist error. I also need to use fastboot boot twrp.img to get into Twrp since it will disappear after clicking reboot recovery. I tried EDL, but then I got not enough storage error in Miflash.
Hopefully somebody can help me with steps!
Click to expand...
Click to collapse
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs

KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you so much for your reply. I really appreciate it. I admit that I am really wrong in flashing that permissiver zip. I just hoped that it will solve my random reboot issue, from this tutorial: https://www.google.com/url?sa=t&sou...BMAB6BAgCEAE&usg=AOvVaw2suOu9rYeTps71AvKuZbrA
So now, I already downloaded OrangeFox-R10.1_1-Stable-jasmine_sprout.zip for recovery and persist_restorer_6x.zip from the Telegram group, which is universal persist according to them.
But I just have some questions:
1. Do I need to wipe both a and b in recovery or use command fastboot -w before flashing the stock ROM?
2. After flashing stocK ROM in Miflash tool, it will start to boot to system, but in this case, bootloop, so am I right to press buttons to forcibly go to bootloader?
3. For #7 (boot to recovery), this means fastboot boot recovery.img?
4. For #9, if adb sideload doesn't work, can I flash persist in recovery instead?

Ronaldendoma said:
Thank you so much for your reply. I really appreciate it. I admit that I am really wrong in flashing that permissiver zip. I just hoped that it will solve my random reboot issue, from this tutorial: https://www.google.com/url?sa=t&sou...BMAB6BAgCEAE&usg=AOvVaw2suOu9rYeTps71AvKuZbrA
So now, I already downloaded OrangeFox-R10.1_1-Stable-jasmine_sprout.zip for recovery and persist_restorer_6x.zip from the Telegram group, which is universal persist according to them.
But I just have some questions:
1. Do I need to wipe both a and b in recovery or use command fastboot -w before flashing the stock ROM?
2. After flashing stocK ROM in Miflash tool, it will start to boot to system, but in this case, bootloop, so am I right to press buttons to forcibly go to bootloader?
3. For #7 (boot to recovery), this means fastboot boot recovery.img?
4. For #9, if adb sideload doesn't work, can I flash persist in recovery instead?
Click to expand...
Click to collapse
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs

KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
KevMetal said:
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you again.
I tried adb sideload before but was stuck at 0%, I missed something. I'll update here for the result once I can be back to PC.

KevMetal said:
you are messing up ..stop ..
1.boot into fastboot
2. flash stock rom with miflash
3. boot back to fastboot
4. download orange fox or pitch black recovery that actually supports persist flashing
5. join global mi a2 telegram group download relevant persist like if mi a2 or mi x6 and on android 9 or 10
6. put it in adb folder
7. boot recovery ( don't flash)
8. in recovery activate sideload adb option
9. in command window run :adb sideload persist.zip ( persist must have this name in adb folder )
10. now reboot your phone
*in the beginning it will bootloop four or five times ..just leave it
***suddenly your phone will be back to new
***stop flashing permissver and other crap
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
KevMetal said:
no install stock using miflash but don't wipe anything ..for this to work well don't install the recovery ..just boot
fastboot boot recovery.img
then using the adb sideload option you can flash the zip from your computer without decryting the internal storage
you can flash magisk the same way ..then you will have stock rooted with persist restored but without custom recovery and your device will remain encrypted ..
if you want custom recovery and install custom rom you can wipe and install but for stock don't do it ..flash persist and magisk from adb sideload without decrypting
2.yeah enter bootloader / fastboot with power button and volume button
4. it will work if done correctly ...if you want to flash from internal storage you will have to wipe and format data to decrypt internal syorage
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Thank you again.
I tried adb sideload before but was stuck at 0%, I maybe missed something. I'll update here for the result once I can be back to PC.

Ronaldendoma said:
Thank you again.
I tried adb sideload before but was stuck at 0%, I maybe missed something. I'll update here for the result once I can be back to PC.
Click to expand...
Click to collapse
ok yeah must be a mistake ..
do you understand that first you enter fastboot and boot the orange fox recovery ..only then you start the adb ..
BUT REMember first you need to toggle or activate adb from orange fox recovery (maybe you forgot this ? )
another thing it is very slow so wait very long
another thing the zip you want to flash must be in the adb folder and have the name you use
so
rename persist to persist.zip and put it in adb folder ..then put magisk zip and rename to magisk.zip :
adb sideload persist.zip
adb sideload magisk.zip
Sent from my wayne using XDA Labs

here is a photo where you need to activate adb
Sent from my wayne using XDA Labs

KevMetal said:
ok yeah must be a mistake ..
do you understand that first you enter fastboot and boot the orange fox recovery ..only then you start the adb ..
BUT REMember first you need to toggle or activate adb from orange fox recovery (maybe you forgot this ? )
another thing it is very slow so wait very long
another thing the zip you want to flash must be in the adb folder and have the name you use
so
rename persist to persist.zip and put it in adb folder ..then put magisk zip and rename to magisk.zip :
adb sideload persist.zip
adb sideload magisk.zip
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
I need to wait more, I think. Before this thread, I tried to adb sideload in TWRP but it took somewhat long and still 0%, so I just cancelled since I ran out of time.

KevMetal said:
here is a photo where you need to activate adb
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Regarding persist.zip, I am now confused because I asked in the group if the file persist_restorer_6x.zip is universal (either pie or 10, wayne or jasmine), they said yes, and another one said no. I searched in the group and found persist_restorer_a2.zip. I checked both files and they have the same filesize and contents.
So is there a thing like a universal persist for a2/6x, either for pie or 10? Or like what you said, only relevant persist depending on the os and device?

techieboy2020 said:
Regarding persist.zip, I am now confused because I asked in the group if the file persist_restorer_6x.zip is universal (either pie or 10, wayne or jasmine), they said yes, and another one said no. I searched in the group and found persist_restorer_a2.zip. I checked both files and they have the same filesize and contents.
So is there a thing like a universal persist for a2/6x, either for pie or 10? Or like what you said, only relevant persist depending on the os and device?
Click to expand...
Click to collapse
it is the same device.. so it is cross compatible ..it might just give an error if it checks the build prop ..obviously flash the A2..pie or q will just maybe be updated version or not but bettrr to flash corresponding if it exists
Sent from my wayne using XDA Labs

KevMetal said:
it is the same device.. so it is cross compatible ..it might just give an error if it checks the build prop ..obviously flash the A2..pie or q will just maybe be updated version or not but bettrr to flash corresponding if it exists
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
I see. I can't access my PC yet, but what if I still got bootloop after trying those steps, what must I do next? I'm worried for step #10.
Regarding the persist.zip, can you please check the zips below? The two have the same filesize and files inside, so maybe the two are just the same.

techieboy2020 said:
I see. I can't access my PC yet, but what if I still got bootloop after trying those steps, what must I do next? I'm worried for step #10.
Regarding the persist.zip, can you please check the zips below? The two have the same filesize and files inside, so maybe the two are just the same.
Click to expand...
Click to collapse
those are empty and won't work ..use this
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
Sent from my wayne using XDA Labs

KevMetal said:
those are empty and won't work ..use this
https://www.dropbox.com/s/mimt4go8fert44c/persist good.zip?dl=0
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Ok thank you so much. Will try this tomorrow.
Regarding the state of my device, I can't boot to system because of bootloop. If I press power and volume +, I got no command. If I press power and volume -, fastboot mode. My device's bootloader is already unlocked, and can be detected through fastboot.

techieboy2020 said:
Ok thank you so much. Will try this tomorrow.
Regarding the state of my device, I can't boot to system because of bootloop. If I press power and volume +, I got no command. If I press power and volume -, fastboot mode. My device's bootloader is already unlocked, and can be detected through fastboot.
Click to expand...
Click to collapse
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs

KevMetal said:
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
Got it. So the zip is compatible for either Pie or Android 10?
What's the best version for Miflash tool? I tried the newer version but it can't detect my device, and only the older version can detect. But it seems that the older version can't be trusted also since I still got persist error before.
For #10, my device will bootloop 4 to 5 times. So will it automatically turn off and on again until it will successfully boot? How long does it normally boot?

UPDATE:
KevMetal said:
you don't need to boot to system ...just boot the revovery and flash the zip ..
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
UPDATE:
So I flashed the Pie Rom (V.10.0.17.0) in the MiFlash Tool (v. 2016.04.01.0) and the flashing was successful. The device turned on and only remained at the Android One logo and turned off again. This repeated for another time and I then forced my device to fastboot mode through the buttons. I then flashed the latest Orange Fox Recovery and it was successful. Now, I checked the recovery and persist can't be mounted (can't put a check on the box), but I still continued to adb sideload mode. The sideloading for persist.zip started, but was stuck at 10%. I waited more and decided to disconnect and try to flash the zip on the device instead. I checked the active slot and it was b, so I thought changing to a will be able to mount persist. I thought that if I remain at b, I will still get mount persist error. I clicked "boot to recovery" and the screen turned off. After a while, the screen remained off and I tried to use the button combinations, and the screen was totally black (no fastboot, logo, animation, or even some light, etc). It's completely black, but I noticed that the device was still hot after a few minutes. I connected my device to the PC again and the MiFlash tool detected my device as Com10. I flashed the rom again but the flashing was not successful. I tried to uninstall the drivers and still, there is no hope for reflashing the rom (it's now detected as com4). If I try to use power combinations, the PC will make sounds like when you connect/ disconnect a device, meaning, my phone can still be detected by my PC. So is there still a hope for my phone?

techieboy2020 said:
UPDATE:
So I flashed the Pie Rom (V.10.0.17.0) in the MiFlash Tool (v. 2016.04.01.0) and the flashing was successful. The device turned on and only remained at the Android One logo and turned off again. This repeated for another time and I then forced my device to fastboot mode through the buttons. I then flashed the latest Orange Fox Recovery and it was successful. Now, I checked the recovery and persist can't be mounted (can't put a check on the box), but I still continued to adb sideload mode. The sideloading for persist.zip started, but was stuck at 10%. I waited more and decided to disconnect and try to flash the zip on the device instead. I checked the active slot and it was b, so I thought changing to a will be able to mount persist. I thought that if I remain at b, I will still get mount persist error. I clicked "boot to recovery" and the screen turned off. After a while, the screen remained off and I tried to use the button combinations, and the screen was totally black (no fastboot, logo, animation, or even some light, etc). It's completely black, but I noticed that the device was still hot after a few minutes. I connected my device to the PC again and the MiFlash tool detected my device as Com10. I flashed the rom again but the flashing was not successful. I tried to uninstall the drivers and still, there is no hope for reflashing the rom (it's now detected as com4). If I try to use power combinations, the PC will make sounds like when you connect/ disconnect a device, meaning, my phone can still be detected by my PC. So is there still a hope for my phone?
Click to expand...
Click to collapse
all of this couldn't happen if you only flashed permissiver ..what rom did you previously flash in slot b
anyway doesn't matter ..boot to fastboot with buttons ..boot ..NOT FLASH orange fox recovery
do all wipes
format data
install custom rom
install magisk
install persist
reboot to other standby slot ..
do all wipes
format data
install custom rom
install magisk
install persist
then reboot and phone will boot
use a latest custom rom Q with gapps included ....
follow all the instructions ..not only some ..don change them ..if it fails message me with screenshot
but the 10% problem over usb is a hardware , computer or most likely cable problem ..get a new cable ..or maybe you changed or damaged your screen improperly ..
anyway try the above
also download the most newest copy of miflash and use that to install drivers and flash if you want to flash stock and flash the latest stock amdroid ..
if your phone doesn't go into fastboot it is cos it is bricked in edl mode ..so flash latest stock with latest miflash ..
THEN FLASH PERSIST BY ONLY BOOTINGBrecovery
did you try to convert this A2 to Wayne amd triggered arb ? that could be why flashing stock pie goes to edl mode
Sent from my wayne using XDA Labs

Just FYI:
Since 10.0.2.0 till now I thought that persist.img is version-insensitive, as I flashed persist.img taken from 8.1 ROM into couple of versions of 9.0 without any problems (via my method published in "Guides...").
Last week I noticed that compass is "showing south", and tried to flash various versions of persist.img into active 11.0.12.0 - and was surprised to encounter "white screen of eternal booting" with non-native version of persist.img. So finally had to flash persist.img taken from 11.0.12.0 fastboot ROM image.
(Btw, my problem with compass seems to have 2 sides -1st is somewhat very big deviation at homeplace, and 2nd is that only 1st magnetic sensor is being calibrated while second magnetic sensor is not being calibrated by means I used).

KevMetal said:
all of this couldn't happen if you only flashed permissiver ..what rom did you previously flash in slot b
anyway doesn't matter ..boot to fastboot with buttons ..boot ..NOT FLASH orange fox recovery
do all wipes
format data
install custom rom
install magisk
install persist
reboot to other standby slot ..
do all wipes
format data
install custom rom
install magisk
install persist
then reboot and phone will boot
use a latest custom rom Q with gapps included ....
follow all the instructions ..not only some ..don change them ..if it fails message me with screenshot
but the 10% problem over usb is a hardware , computer or most likely cable problem ..get a new cable ..or maybe you changed or damaged your screen improperly ..
anyway try the above
also download the most newest copy of miflash and use that to install drivers and flash if you want to flash stock and flash the latest stock amdroid ..
if your phone doesn't go into fastboot it is cos it is bricked in edl mode ..so flash latest stock with latest miflash ..
THEN FLASH PERSIST BY ONLY BOOTINGBrecovery
did you try to convert this A2 to Wayne amd triggered arb ? that could be why flashing stock pie goes to edl mode
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
So I was able to use another laptop, and I managed to install adb, drivers, and MiFlash Tool. The 2018 version can now detect my phone, and I can now at least boot into fastboot. But my flashing is still not successful because I got stuck at system.img. The laptop freezes and I already tried to free up space in C: drive.

Question No TWRP folder

I have flashed TWRP to recovery (on my unlocked Redmi Note 10 Pro) and can access it no problem. But I have no TWRP folder on my phone and cannot see one when connected to my computer.
I have reflashed to try to fix it, but no change. I found a thread where the suggested terminal commands but I would need to root my phone and I don't think that is something I should be doing. Any suggestions?

31272809 said:
I have flashed TWRP to recovery (on my unlocked Redmi Note 10 Pro) and can access it no problem. But I have no TWRP folder on my phone and cannot see one when connected to my computer.
I have reflashed to try to fix it, but no change. I found a thread where the suggested terminal commands but I would need to root my phone and I don't think that is something I should be doing. Any suggestions?
Click to expand...
Click to collapse
I think you can't access internal storage in case of encryption.
Google about decryption pros cons ... if you're fine with decryption check out dfe in our forum

Laptapper said:
I think you can't access internal storage in case of encryption.
Google about decryption pros cons ... if you're fine with decryption check out dfe in our forum
Click to expand...
Click to collapse
I read about that but I thought I'd see 0MB or weird filenames while looking at the filesystem in TWRP recovery and neither is the case. I did have to enter my password the first time I used TWRP and I have never been asked for it since.

31272809 said:
I read about that but I thought I'd see 0MB or weird filenames while looking at the filesystem in TWRP recovery and neither is the case. I did have to enter my password the first time I used TWRP and I have never been asked for it since.
Click to expand...
Click to collapse
Which recovery you've installed? Try newest orange fox

Laptapper said:
Which recovery you've installed? Try newest orange fox
Click to expand...
Click to collapse
So I had twrp 3.6_11-sweet installed. I just flashed Orange fox (the latest stable version) to recovery, and then I could no longer access recovery - it just restarted to flashboot. I had this problem when I tried to flash the Pixel Experience image too.
So I flashed TWRP to recovery again and everything is back to normal. But the problem is that I can’t use TWRP because there’s no folder installed.

31272809 said:
So I had twrp 3.6_11-sweet installed. I just flashed Orange fox (the latest stable version) to recovery, and then I could no longer access recovery - it just restarted to flashboot. I had this problem when I tried to flash the Pixel Experience image too.
So I flashed TWRP to recovery again and everything is back to normal. But the problem is that I can’t use TWRP because there’s no folder installed.
Click to expand...
Click to collapse
How you exactly flashed recovery?
Orange fox is working quite good....

Laptapper said:
How you exactly flashed recovery?
Orange fox is working quite good....
Click to expand...
Click to collapse
So I put the phone in fastboot mode -> connected to PC with usb -> check connection in cmd (fastboot devices) -> fastboot flash recovery "recovery_orange fox.img" -> power+up
And I get sent back to the fastboot screen
I must be doing something wrong but I have watched videos and read instructions and I don't know what it is.

31272809 said:
So I put the phone in fastboot mode -> connected to PC with usb -> check connection in cmd (fastboot devices) -> fastboot flash recovery "recovery_orange fox.img" -> power+up
And I get sent back to the fastboot screen
I must be doing something wrong but I have watched videos and read instructions and I don't know what it is.
Click to expand...
Click to collapse
Sounds ok
But without the quotes and no spaces, means change the file name like cmd:
fastboot flash recovery orangefox.img

Laptapper said:
Sounds ok
But without the quotes and no spaces, means change the file name like cmd:
fastboot flash recovery orangefox.img
Click to expand...
Click to collapse
I renamed the file but same result - it cycles through back to fastboot instead of recovery.
I don't understand. It's like it only accepts the twrp image, but even that doesn't install right.

31272809 said:
I renamed the file but same result - it cycles through back to fastboot instead of recovery.
I don't understand. It's like it only accepts the twrp image, but even that doesn't install right.
Click to expand...
Click to collapse
Please make a pc screenshot from flashing progress
You've switched on developer option usb debugging?

Laptapper said:
Please make a pc screenshot from flashing progress
You've switched on developer option usb debugging?
Click to expand...
Click to collapse
Here's the screenshot. Inbetween flashing recoveryorangefox.img and twrp.img I have tried to reboot into recovery and I have been sent back to fastboot.
Yes, usb debugging is on in the settings.

31272809 said:
Here's the screenshot. Inbetween flashing recoveryorangefox.img and twrp.img I have tried to reboot into recovery and I have been sent back to fastboot.
Yes, usb debugging is on in the settings.
Click to expand...
Click to collapse
Check out here
How to Enter Recovery Mode ? Volume Up and Power enabling Fastboot
Today I flashed EU RoM 13.0.4 to my Redmi Note 10 pro . Phone is working fine but I installed orange recovery and the process completed successfully on pc . When I press power and volume up it going to Fastboot mode instead of recovery mode. How...
forum.xda-developers.com
And take the files which there are downloadable
Try after flashing to boot via hardware keys and also via adb.
If both not working, I think you have to flash fastboot image via PC miflash and boot it to switch developer usb debugging on and restart to fastboot mode and flash twrp again.....

31272809 said:
Here's the screenshot. Inbetween flashing recoveryorangefox.img and twrp.img I have tried to reboot into recovery and I have been sent back to fastboot.
Yes, usb debugging is on in the settings.
Click to expand...
Click to collapse
One more idea, before starting from scratch:
After flashing twrp disconnecting usb and then rebooting to recovery by pressing power and vol+ until you'll see the logo and feel the vibration

Why don't you test the recovery using fastboot boot? My recommendation is never to flash any recovery before successfully having it started manually once.
My personal approach is, never to install any recovery but only boot it in case it is needed. Disadvantage is that you need to be near a computer if you want to run it.

fastboot flash recovery twrp-3.6.0_11-0-sweet.img
fastboot boot twrp-3.6.0_11-0-sweet.img

Ashle said:
fastboot flash recovery twrp-3.6.0_11-0-sweet.img
fastboot boot twrp-3.6.0_11-0-sweet.img
Click to expand...
Click to collapse
Hi all, there's been some progress but I'd like your advice before continuing. I have my preferred ROM (Pixel Experience, zipped) copied to my SD card and I can see my SD card under Install option on TWRP. My phone data has been formatted (using the twrp Wipe option). Should I try installing from the SD card? I'm nervous since I know missing steps was warned against in the installation instructions.

1. Wipe Data/Cache
2. Format Data (yes)
3. Flash ROM Pixel Experience.zip
4. Reboot System

Ashle said:
1. Wipe Data/Cache
2. Format Data (yes)
3. Flash ROM Pixel Experience.zip
4. Reboot System
Click to expand...
Click to collapse
Is 1 included in 2, or should I do something else as well?
If I'm okay to move to step 3, do I reboot to recovery or reboot into (hopefully) my new ROM?

Copy Pixel Experience.zip to sdcard
reboot to recovery
All over TWRP
1. Wipe Data/Cache
2. Format Data (yes)
3. Flash ROM Install Pixel Experience.zip
4. Reboot System

Ashle said:
Copy Pixel Experience.zip to sdcard
reboot to recovery
All over TWRP
1. Wipe Data/Cache
2. Format Data (yes)
3. Flash ROM Install Pixel Experience.zip
4. Reboot System
Click to expand...
Click to collapse
It didn't work.