Hello, I followed this guide to root my infinix hot 10 x682c but once I got to the last stage of writing the image, my phone started to bootloop. It firsts boots up with the infinix logo and says
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
Then it reboots.
I tried going into recovery mode but it immediately reboots when I do that.
Any help is appreciated.
tripdd said:
Hello, I followed this guide to root my infinix hot 10 x682c but once I got to the last stage of writing the image, my phone started to bootloop. It firsts boots up with the infinix logo and says
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
Then it reboots.
I tried going into recovery mode but it immediately reboots when I do that.
Any help is appreciated.
Click to expand...
Click to collapse
You should list the steps you took to try and get roor.
Tulsadiver said:
You should list the steps you took to try and get roor.
Click to expand...
Click to collapse
I unlocked the bootloader
Installed magisk app
Got a stock boot image from https://forum.hovatek.com/thread-35620.html
Patched it in the magisk app
Then flashed it in fastboot
Boom, boot loop. Any help?
tripdd said:
I unlocked the bootloader
Installed magisk app
Got a stock boot image from https://forum.hovatek.com/thread-35620.html
Patched it in the magisk app
Then flashed it in fastboot
Boom, boot loop. Any help?
Click to expand...
Click to collapse
Did you try to disable verification of the vbmeta ?
tripdd said:
I unlocked the bootloader
Installed magisk app
Got a stock boot image from https://forum.hovatek.com/thread-35620.html
Patched it in the magisk app
Then flashed it in fastboot
Boom, boot loop. Any help?
Click to expand...
Click to collapse
After first unlocking bootloader, did your phone boot up without any problems?
VD171 said:
Did you try to disable verification of the vbmeta ?
Click to expand...
Click to collapse
Uhhhh how do I do that?
Tulsadiver said:
After first unlocking bootloader, did your phone boot up without any problems?
Click to expand...
Click to collapse
Yes, the phone was wiped and in the developer options it said that the bootloader was unlocked. Every thing was fine until I flashed the patched boot image.
tripdd said:
Uhhhh how do I do that?
Click to expand...
Click to collapse
Using fastboot:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
VD171 said:
Using fastboot:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
No I didn’t, but I can’t access fastboot now as I can’t get into recovery mode. The phone just boot loops
tripdd said:
No I didn’t, but I can’t access fastboot now as I can’t get into recovery mode. The phone just boot loops
Click to expand...
Click to collapse
If you just flashed the magisk patched boot.img and you got bootloop, so, just flash the original stock boot.img back and your device will boot again.
And then, you can flash the vbmeta and disable verification.
VD171 said:
If you just flashed the magisk patched boot.img and you got bootloop, so, just flash the original stock boot.img back and your device will boot again.
And then, you can flash the vbmeta and disable verification.
Click to expand...
Click to collapse
Here is the thing, I can’t access fastboot when I try to go to recovery mode, the phone immediately reboots
tripdd said:
Here is the thing, I can’t access fastboot when I try to go to recovery mode, the phone immediately reboots
Click to expand...
Click to collapse
I'm sorry. I mean using the SP FLASH TOOL.
VD171 said:
I'm sorry. I mean using the SP FLASH TOOL.
Click to expand...
Click to collapse
Okay I tried to flash the boot image in sp flash, but now it errors out with
“ERROR : STATUS_SEC_AUTH_FILE_NEEEDED (0xC0030012)
[HINT]:
Please select a valid authentication file or ask for help.”
Do you know where I can get that?
Oh wait, when I try to download again after it fails I get instead:
“ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001)
[HINT]:
Please retry the operation:
1.remove battery and usb cable;
2.press download “botton”(that’s actually what it said) on flash tool;
3.pressing download volume down and plug in usb cable and download without battery.”
That’s some grammar right there. Any ideas?
tripdd said:
Okay I tried to flash the boot image in sp flash, but now it errors out with
“ERROR : STATUS_SEC_AUTH_FILE_NEEEDED (0xC0030012)
[HINT]:
Please select a valid authentication file or ask for help.”
Do you know where I can get that?
Click to expand...
Click to collapse
You need the properly DA (download-agent) file specific for your device.
tripdd said:
Oh wait, when I try to download again after it fails I get instead:
“ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001)
[HINT]:
Please retry the operation:
1.remove battery and usb cable;
2.press download “botton”(that’s actually what it said) on flash tool;
3.pressing download volume down and plug in usb cable and download without battery.”
That’s some grammar right there. Any ideas?
Click to expand...
Click to collapse
Just simple try to boot/reboot your device.
Once is enough.
VD171 said:
You need the properly DA (download-agent) file specific for your device.
Click to expand...
Click to collapse
I looked everywhere I couldn’t find them. The closest I got was this. But sill, it didn’t have the hot 10. Do you know where I can get it?
VD171 said:
Just simple try to boot/reboot your device.
Once is enough.
Click to expand...
Click to collapse
it’s boot looping... it already rebooted about a hundred times and counting now. If you mean the pc, then yeah I already rebooted it too. No luck.
If you are facing the error "STATUS_BROM_CMD_STARTCMD_FAIL" just (try) to reboot the device once.
I didn't mean to boot the system, I mean try to reboot.
It will refresh the download mode.
VD171 said:
If you are facing the error "STATUS_BROM_CMD_STARTCMD_FAIL" just (try) to reboot the device once.
I didn't mean to boot the system, I mean try to reboot.
It will refresh the download mode.
Click to expand...
Click to collapse
Tried that already
Okay so after some digging around, it turns out that there was an exploit for some mtk chips and someone made a bypass utility based on it. After using it I used sp flash boot again and everything worked flawlessly this time.
Now, my phone hasn’t exactly booted it’s stuck on the x os animation but at least now I can get into recovery mode. Thanks so much to everyone who help out!
Just flash the whole rom again.
If the device keep in bootloop, probably you will need to erase userdata.
Good luck
Related
Are there any tools around for rooting Spectrum on the R7Plusf?
W1F1 said:
How am I able to root project spectrum on the Oppo R7 Plus?
Thanks in advance!
Click to expand...
Click to collapse
Hello, W1F1. There is no way at this point in time to root Project Spectrum on Oppo R7Plus as TWRP isnt compatible. They changed a lot when they made Project Spectrum. For now there is no TWRP. So there is no way to root. It's Fastboot is also set to non-root access making is hard to use the command (fastboot flash recovery _TWRP-HERE_) but not impossible to flash the stock recovery and then ColorOS to get back to safety (by safety I mean CyanogenMod 14.1 [OFFICIAL] or AICP [UNOFFICIAL]). All you need to do is ask and I'll give you the links.
EximusCode said:
Hello, W1F1. There is no way at this point in time to root Project Spectrum on Oppo R7Plus as TWRP isnt compatible. They changed a lot when they made Project Spectrum. For now there is no TWRP. So there is no way to root. It's Fastboot is also set to non-root access making is hard to use the command (fastboot flash recovery _TWRP-HERE_) but not impossible to flash the stock recovery and then ColorOS to get back to safety (by safety I mean CyanogenMod 14.1 [OFFICIAL] or AICP [UNOFFICIAL]). All you need to do is ask and I'll give you the links.
Click to expand...
Click to collapse
Thanks for the reply! So I could use stock recovery to get back to a version of color os that has fastboot enabled, and then get TWRP and then cyanogen mod from there?
W1F1 said:
Thanks for the reply! So I could use stock recovery to get back to a version of color os that has fastboot enabled, and then get TWRP and then cyanogen mod from there?
Click to expand...
Click to collapse
Bingo my friend. If you want the links you need only ask. :good:
EximusCode said:
Bingo my friend. If you want the links you need only ask. :good:
Click to expand...
Click to collapse
The links would be fantastic, thanks so much!
W1F1 said:
The links would be fantastic, thanks so much!
Click to expand...
Click to collapse
Will post them ASAP
Thanks!
W1F1 said:
Thanks!
Click to expand...
Click to collapse
Recovery:http://goo.gl/1AdXkD
ROM:https://s3.amazonaws.com/public.opp...olorOS/Specified_ColorOS_R7plusf_full_014.zip
0. Move all files to external MicroSD card *rename the ROM to update.zip*
1. Flash the recovery.img to recovery partition. With (fastboot flash recovery "recovery.img) *remember to put the recovery.img file in the ADB and Fastboot file for easier transfer*
2. Reboot into the system recovery and select Update, then go to where you put your ROM and select it
3. Wait for it to flash and then reboot
4. Your reboot will hang. Leave it do that for about 5 minutes, then reboot into fastboot mode again.
5. Seeing as you are now on a ROM with an unlocked bootloader you will be able to now flash TWRP recovery with the command (fastboot flash recovery "TWRPRECOVERYNAME") *I used TWRPRECOVERYNAME as an example as to where the recovery file needs to go. You should also have this in the ADB and Fastboot folder*
EximusCode said:
Will post them ASAP
Click to expand...
Click to collapse
I'm sorry but I can't seem to download from app.box, even after creating an account. Could you please upload the recovery to somewhere else like google drive?
EDIT: Whoops disregard that I managed to download it.
W1F1 said:
I'm so so sorry but I can't seem to download from app.box, even after creating an account. Could you please upload the recovery to somewhere else like google drive?
Sorry again.
EDIT: Sorry disregard that I managed to download it.
Click to expand...
Click to collapse
Hope it works for you like it did for me :good:
EximusCode said:
Recovery:http://goo.gl/1AdXkD
ROM:https://s3.amazonaws.com/public.opp...olorOS/Specified_ColorOS_R7plusf_full_014.zip
0. Move all files to external MicroSD card *rename the ROM to update.zip*
1. Flash the recovery.img to recovery partition. With (fastboot flash recovery "recovery.img) *remember to put the recovery.img file in the ADB and Fastboot file for easier transfer*
2. Reboot into the system recovery and select Update, then go to where you put your ROM and select it
3. Wait for it to flash and then reboot
4. Your reboot will hang. Leave it do that for about 5 minutes, then reboot into fastboot mode again.
5. Seeing as you are now on a ROM with an unlocked bootloader you will be able to now flash TWRP recovery with the command (fastboot flash recovery "TWRPRECOVERYNAME") *I used TWRPRECOVERYNAME as an example as to where the recovery file needs to go. You should also have this in the ADB and Fastboot folder*
Click to expand...
Click to collapse
Ok I'm still having an issue. The flashing of the recovery goes through successfully but when I try to enter recovery mode it simply shows the Oppo logo and the screen goes black. Like it's been doing with all the recovery's that I've tried. If I try the "fastboot boot recovery.img" it has this error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.485s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.553s
W1F1 said:
Ok I'm still having an issue. The flashing of the recovery goes through successfully but when I try to enter recovery mode it simply shows the Oppo logo and the screen goes black. Like it's been doing with all the recovery's that I've tried. If I try the "fastboot boot recovery.img" it has this error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.485s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.553s
Click to expand...
Click to collapse
After flashing recovery, type (fastboot reboot) Before you press enter, hold down the Volume - button (on the phone) and simultaneously press enter. You should then be able to boot to stock recovery
JUST REMEMBER TO NOT BOOT BACK INTO SPECTRUMOS. This will reset the recovery partition as it locks it on boot
EximusCode said:
After flashing recovery, type (fastboot reboot) Before you press enter, hold down the Volume - button (on the phone) and simultaneously press enter. You should then be able to boot to stock recovery
JUST REMEMBER TO NOT BOOT BACK INTO SPECTRUMOS. This will reset the recovery partition as it locks it on boot
Click to expand...
Click to collapse
Sadly no all it does is show the Oppo logo, and then when it should show the recovery screen it just goes black. I think it's something to do with the DTB error before.
W1F1 said:
Sadly no all it does is show the Oppo logo, and then when it should show the recovery screen it just goes black. I think it's something to do with the DTB error before.
Click to expand...
Click to collapse
Please give me some more time. I will find some more info. I will be back to you as soon as I have found some more.
EximusCode said:
Please give me some more time. I will find some more info. I will be back to you as soon as I have found some more.
Click to expand...
Click to collapse
Thank you. I have looked around a lot and I believe creating a new recovery img using the dt from here might work: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/716
Please let me know if you find something.
W1F1 said:
Thank you. I have looked around a lot and I believe creating a new recovery img using the dt from here might work: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/716
Please let me know if you find something.
Click to expand...
Click to collapse
You could very well try that and it work. I have limited knowledge when it comes to development of ROMs and Recoveries so I'm not too sure how you will fair, it may take a bit of trial and error. Tell me how you go with it
EximusCode said:
You could very well try that and it work. I have limited knowledge when it comes to development of ROMs and Recoveries so I'm not too sure how you will fair, it may take a bit of trial and error. Tell me how you go with it
Click to expand...
Click to collapse
Update:
Bad news: Unfortunately my phone is now stuck in a boot loop.
Good news: Using a recovery provider by the user "Ricky" on the first page of this thread: http://community.oppo.com/en/forum.php?mod=viewthread&tid=46395&extra=&page=1 I have been able to flash the stock recovery and it is now working. Because of the boot loop problem I am reinstalling Spectrum through recovery to try and get out of that, then hopefully I will be able to flash back to Color OS if the boot loop stops.
W1F1 said:
Update:
Bad news: Unfortunately my phone is now stuck in a boot loop.
Good news: Using a recovery provider by the user "Ricky" on the first page of this thread: http://community.oppo.com/en/forum.php?mod=viewthread&tid=46395&extra=&page=1 I have been able to flash the stock recovery and it is now working. Because of the boot loop problem I am reinstalling Spectrum through recovery to try and get out of that, then hopefully I will be able to flash back to Color OS if the boot loop stops.
Click to expand...
Click to collapse
Is it just the boot animation continuously playing? If so, this is when you need to turn off your phone and right as the screen goes off press and hold the volume + button. This will put you back in fastboot. Once you are there flash the TWRP recovery. After that hold the volume - and type fastboot reboot. This will boot you to TWRP recovery
EximusCode said:
Is it just the boot animation continuously playing? If so, this is when you need to turn off your phone and right as the screen goes off press and hold the volume + button. This will put you back in fastboot. Once you are there flash the TWRP recovery. After that hold the volume - and type fastboot reboot. This will boot you to TWRP recovery
Click to expand...
Click to collapse
All good, I erased data in recovery and now it's working. Now to flash back to Color OS in recovery.
W1F1 said:
All good, I erased data in recovery and now it's working. Now to flash back to Color OS in recovery.
Click to expand...
Click to collapse
Okay, good luck
Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.
lgstylus2root said:
Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.
Click to expand...
Click to collapse
I personally feel installing twrp offians twrp and flashing magisk is easyer
rob420p said:
I personally feel installing twrp offians twrp and flashing magisk is easyer
Click to expand...
Click to collapse
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.
lgstylus2root said:
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.
Click to expand...
Click to collapse
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.
rob420p said:
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.
Click to expand...
Click to collapse
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Go to the pa ROM page and use that twrp that's offians twrp.the best guild ive seen n is type in customdriod mi a2 lite twrp and that page is the best in my opinion to follow I'll see if I can get a link for the page in a minute
Won't let me simend the link
rob420p,
Please provide links.
rob420p said:
Won't let me simend the link
Click to expand...
Click to collapse
Would you be capable of private messaging me the link?
I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.
lgstylus2root said:
I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.
Click to expand...
Click to collapse
I have followed this guide but it would always result in the installed version of TWRP not installing correctly, and the system mentioning "The System has been destroyed, Press power button to shut down"
How can i resolve this?
I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY
marstonpear said:
I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY
Click to expand...
Click to collapse
I figured out how to do it either way, thank you for your efforts however!
lgstylus2root said:
I figured out how to do it either way, thank you for your efforts however!
Click to expand...
Click to collapse
You can add the links to the main thread so that people can see :good:
Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks
max-damage said:
Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks
Click to expand...
Click to collapse
Search before asking : https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.
max-damage said:
I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.
Click to expand...
Click to collapse
I'm stuck with the same problem.
Booting with patched_boot.img (made on my own or downloaded from this forum) make the phone not starting, blocked on white screen.
Have you already solved?
lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....
Winchester316 said:
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....
Click to expand...
Click to collapse
I believe we can I have heard reports offains 3.3.3. Twrp can do it I haven't tryed yet.but I did have twrp with root running on the march update but I'm on pa now
Hello, newbie here..
Need help!! My phone keeps booting to TWRP whenever I turned it on, connected it to PC, or even when I connected it to my charger.
It happened after I mistakenly uninstalled a system app (it is an app named Freeshare). I thought it was just a sharing app like MiDrop or ShareIt, but clearly that was a mistake.
Now I just can't seem to boot into the system, not even able to enter into the download mode.
I've tried a method that I found in here, like entering a code in TWRP terminal (it was "dd if blablabla", i forgot. Lol), to no avail.
Haven't tried to flash the stock rom or stock boot since I can't find any zip Stock Rom for my phone (my phone is Gome Fenmmy Note).
Does anyone have an idea or know how to fix it?
Thanks in advance
Did you flash MISC partition?
Give a try on this (plese, method #2 only): https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Or you can try to FORMAT the misc partition inside the TWRP.
Or did you flash TWRP to boot partition ??
TWRP needs to be flashed to RECOVERY partition.
If you flash TWRP to boot partition, your device will boot forever to recovery.
If yes, you need to flash the original stock boot.img
VD171 said:
Did you flash MISC partition?
Give a try on this (plese, method #2 only): https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Or you can try to FORMAT the misc partition inside the TWRP.
Click to expand...
Click to collapse
But before i mistakenly uninstalled the system app, my phone is completely fine. No twrp bootloop when i rebooting hte phone. The bootloop happened after I uninstalled a system app.
But thanks anyway. Will try this after I got home.
disegiooo said:
But before i mistakenly uninstalled the system app, my phone is completely fine. No twrp bootloop when i rebooting hte phone. The bootloop happened after I uninstalled a system app.
But thanks anyway. Will try this after I got home.
Click to expand...
Click to collapse
You don't need to uninstall a system app for disabling it completely.
If you've uninstalled a system app, you've modified your system.
1. Did you unlock bootloader?
2. Did you flash vbmeta with disabled verification?
3. Did you root your device?
4. Did you debloat your device?
You can't modify your system before the answer for all questions be YES.
Probably you need to flash the SYSTEM again.
(Only system should be enough.)
VD171 said:
You don't need to uninstall a system app for disabling it completely.
If you've uninstalled a system app, you've modified your system.
1. Did you unlock bootloader?
2. Did you flash vbmeta with disabled verification?
3. Did you root your device?
4. Did you debloat your device?
You can't modify your system before the answer for all questions be YES.
Probably you need to flash the SYSTEM again.
(Only system should be enough.)
Click to expand...
Click to collapse
For questions 1,3,4 the answer is YES. For question 2, I'm not really sure.
Okay, so I need to flash the system again. Can I just flash the system.img through TWRP? Since it won't enter fastboot or download mode. Since once I connect my turned off phone to PC, it will immediately reboot to TWRP.
Sorry, if I'm asking too much. Please be patience.
disegiooo said:
For questions 1,3,4 the answer is YES. For question 2, I'm not really sure.
Okay, so I need to flash the system again. Can I just flash the system.img through TWRP? Since it won't enter fastboot or download mode. Since once I connect my turned off phone to PC, it will immediately reboot to TWRP.
Sorry, if I'm asking too much. Please be patience.
Click to expand...
Click to collapse
Are you sure you can't enter in fastboot mode?
I'm not sure, but I think to flash system using TWRP you need to convert sparse image to regular image using simg2img first.
VD171 said:
Are you sure you can't enter in fastboot mode?
I'm not sure, but I think to flash system using TWRP you need to convert sparse image to regular image using simg2img first.
Click to expand...
Click to collapse
VD171 said:
Are you sure you can't enter in fastboot mode?
I'm not sure, but I think to flash system using TWRP you need to convert sparse image to regular image using simg2img first.
Click to expand...
Click to collapse
Well, I haven't tried to enter fastboot using adb yet since the phone will automatically turn on and boot into TWRP if i connect it to PC using usb cable. Is it possible to enter fastboot using adb eventhough the phone isn't turned off and in TWRP mode?
I see, so i need to convert the image into regular image first. Got it.
I'll try all of your suggestions. Hope it worked.
disegiooo said:
Well, I haven't tried to enter fastboot using adb yet since the phone will automatically turn on and boot into TWRP if i connect it to PC using usb cable. Is it possible to enter fastboot using adb eventhough the phone isn't turned off and in TWRP mode?
I see, so i need to convert the image into regular image first. Got it.
I'll try all of your suggestions. Hope it worked.
Click to expand...
Click to collapse
Yes.
Enter in twrp.
Plug usb cable.
Type "adb devices" and check your device is detected.
And then try "adb reboot bootloader"
VD171 said:
Yes.
Enter in twrp.
Plug usb cable.
Type "adb devices" and check your device is detected.
And then try "adb reboot bootloader"
Click to expand...
Click to collapse
Hello, sorry for late reply. Yes my phone now able to enter the fastboot mode. Then what should i do next to flash my stock rom? I can't turn off my phone
disegiooo said:
Hello, sorry for late reply. Yes my phone now able to enter the fastboot mode. Then what should i do next to flash my stock rom? I can't turn off my phone
Click to expand...
Click to collapse
If you can enter in fastboot mode, you can flash the rom easily.
But it requires unlocked bootloader.
If your bootloader is locked, you need to flash using SP FLASH TOOL.
Just download the stock rom, extract it and flash using any of the flashing script (if available).
Good luck
VD171 said:
If you can enter in fastboot mode, you can flash the rom easily.
But it requires unlocked bootloader.
If your bootloader is locked, you need to flash using SP FLASH TOOL.
Just download the stock rom, extract it and flash using any of the flashing script.
Good luck
Click to expand...
Click to collapse
Alright, my phone bootloader is unlocked. Then how do I flash the stock rom?
Sorry, I'm completely a noob.
disegiooo said:
Alright, my phone bootloader is unlocked. Then how do I flash the stock rom?
Sorry, I'm completely a noob.
Click to expand...
Click to collapse
I suggest you to watch some videos in youtube.
Certainly, it helps alot.
VD171 said:
It's same for all xiaomi devices.
I suggest you to watch some videos in youtube.
Certainly, it helps alot.
If you don't know how to flash manually using fastboot, try MiFlash:
Click to expand...
Click to collapse
Thank you very much. Managed to flash the stock rom safely.
Once again, thank you for your help! May God bless you
disegiooo said:
Thank you very much. Managed to flash the stock rom safely.
Once again, thank you for your help! May God bless you
Click to expand...
Click to collapse
Good job, my friend
You are welcome.
God bless you too
About disabling preinstalled apps, try to perform this in command line:
pm disable-user --user 0 com.android.chrome(Change com.android.chrome to desired package name to disable.)
I recently updated to MIUI v12.5.1.0.RCDMIXM using a recovery zip through TWRP. A few days later I decided to flash Magisk by patching the boot.img from the same zip and flashed using fastboot.
Everything worked fine until I rebooted to recovery using the Magisk app. Now it's stuck at the TWRP splash screen, can't even reboot or enter fastboot with power and volume buttons because it will always try to boot to TWRP.
What do I need to do to fix this?
This is where I got the TWRP
Just erase/format the MISC partition.
This partition holds a "go to recovery" parameter.
VD171 said:
Just erase/format the MISC partition.
This partition holds a "go to recovery" parameter.
Click to expand...
Click to collapse
Okay, but how exactly can I do that? It's been stuck like this since last night and won't go to fastboot with vol keys..
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
VD171 said:
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
Click to expand...
Click to collapse
TWRP is stuck at the state in the picture I sent.
I'll try using SP Flash, but I think I remember that Xiaomi devices have SLA auth to prevent unauthorized flashing using SP Flash. Will your scatter file work without it?
VD171 said:
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
Click to expand...
Click to collapse
I just realized that the zip file or any other version does not include a stock recovery.img...
Do you have the Global v12.5.1.0 stock recovery? Or I could just use any version like vbmeta?
The phone's battery just drained, if I try to plug it would try to boot into twrp again so I kept it unplugged since I need it to be turned off for SP Flash
Reyproject said:
TWRP is stuck at the state in the picture I sent.
I'll try using SP Flash, but I think I remember that Xiaomi devices have SLA auth to prevent unauthorized flashing using SP Flash. Will your scatter file work without it?
Click to expand...
Click to collapse
Exactly.
You need to bypass EDL auth:
[GUIDE] How To bypass authentication and flash in EDL with NO auth for FREE
Thanks to: chaosmaster / k4y0z: GitHub / XDA xyzz / xyz`: GitHub / XDA Dinolek: GitHub / XDA How to install: 1. Download the attached file: VD171_MTK-bypass.zip. 2. Extract the file and open the folder. 3. Run and install python...
forum.xda-developers.com
Reyproject said:
I just realized that the zip file or any other version does not include a stock recovery.img...
Do you have the Global v12.5.1.0 stock recovery? Or I could just use any version like vbmeta?
The phone's battery just drained, if I try to plug it would try to boot into twrp again so I kept it unplugged since I need it to be turned off for SP Flash
Click to expand...
Click to collapse
You said "fastboot", so you need the fastboot ROM.
SP flash tool does NOT need the device to be turned off, it just need to REBOOT.
If you try to flash while a reboot to another reboot, it will works perfectly.
Which magisk did you flash? 23 is not working for 9A
yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
Magisk V23.0 is the BEST MAGISK EVER !
yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
It does tho, i've been using it since the first use of this phone (12 and 12.5)
Applewubs said:
It does tho, i've been using it since the first use of this phone (12 and 12.5)
Click to expand...
Click to collapse
Are you still in 12.5? Do you also use a custom recovery in that version?
Just managed to access a laptop and got to fix the situation. Turns out I can still use adb even though TWRP is stuck on the logo screen.
First tried the `fastboot erase misc` command but misc partition doesn't exist on the device.
Tried `fastboot continue` but won't let me use the command and `fastboot reboot` just makes it go to recovery and get stuck again.
I flashed Orange Fox Recovery and it was still stuck at it's splash screen. So I went back to fastboot and for some reason `fastboot reboot` worked now and booted to system, further restarts are normal now.
Now I'm curious, why won't custom recoveries work with MIUI 12.5? When I tried accessing root, every folder (ex. system) is in this format [1;34system[0m, does it have something to do with that?
Still trying to get the stock recovery, but there's no fastboot rom file for this version yet...
yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
Magisk v23 works just fine, just patch the boot.img file of your ROM version and flash it with custom recovery or fastboot.
Reyproject said:
Are you still in 12.5? Do you also use a custom recovery in that version?
Click to expand...
Click to collapse
Theres one TWRP that doesnt have a splashscreen, in that one just block and unblock the screen while on recovery and it'll work fine. BUT your internal storage isn't going to be accesible, its encrypted and (for some reason) on 12.5 twrp cant unlock the storage, you'll have to do everything on your sdcard
Reyproject said:
Just managed to access a laptop and got to fix the situation. Turns out I can still use adb even though TWRP is stuck on the logo screen.
First tried the `fastboot erase misc` command but misc partition doesn't exist on the device.
Tried `fastboot continue` but won't let me use the command and `fastboot reboot` just makes it go to recovery and get stuck again.
I flashed Orange Fox Recovery and it was still stuck at it's splash screen. So I went back to fastboot and for some reason `fastboot reboot` worked now and booted to system, further restarts are normal now.
Now I'm curious, why won't custom recoveries work with MIUI 12.5? When I tried accessing root, every folder (ex. system) is in this format [1;34system[0m, does it have something to do with that?
Still trying to get the stock recovery, but there's no fastboot rom file for this version yet...
Click to expand...
Click to collapse
I thinks its because they cant unlock the storage, they keep trying and just keeps stuck on trying.
i tried rooting my tablet and probly failed miserably but now it wont boot at all i tried factory reset from recovery mode nothing works
S/N: HA1AM1X7
blocky3321 said:
i tried rooting my tablet and probly failed miserably but now it wont boot at all i tried factory reset from recovery mode nothing works
S/N: HA1AM1X7
Click to expand...
Click to collapse
Do you have an error message on your bootloader screen?
V0latyle said:
Do you have an error message on your bootloader screen?
Click to expand...
Click to collapse
This is what i boot in to every time i turn on the device and if i press start i puts me back here
blocky3321 said:
This is what i boot in to every time i turn on the device and if i press start i puts me back here
Click to expand...
Click to collapse
No error message. Hm. What exactly did you do to get to this point?
V0latyle said:
No error message. Hm. What exactly did you do to get to this point?
Click to expand...
Click to collapse
i tried to root my device i patched boot(using magisk) that i got from lenovos rescue thing and flashed it that didnt work so as a sugestion from LSS4181 in this post i did this
You need to edit out vbmeta.img / vbmeta_system.img to actually disable verification. Change the byte at offset 123 from 0x00 to 0x03.
Another way is to use the following command when flashing vbmeta. You may need to use a relatively newer version of fastboot binary to get it work.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Click to expand...
Click to collapse
and after flashing everything its like this
blocky3321 said:
i tried to root my device i patched boot(using magisk) that i got from lenovos rescue thing and flashed it that didnt work so as a sugestion from LSS4181 in this post i did this
and after flashing everything its like this
Click to expand...
Click to collapse
Are you able to reflash the factory firmware?
V0latyle said:
Are you able to reflash the factory firmware?
Click to expand...
Click to collapse
Ok i can using qpst right?
blocky3321 said:
Ok i can using qpst right?
Click to expand...
Click to collapse
To be honest I have zero experience with Lenovo devices; I'm familiar with ADB and Magisk but I'm not familiar with QPST/QFIL.
Can u not use fastboot?
Arealhooman said:
Can u not use fastboot?
Click to expand...
Click to collapse
now no it doesnt show up in fastboot devices
But you can get into fastboot mode? Try draining it and powering it and getting into fastboot
Arealhooman said:
But you can get into fastboot mode? Try draining it and powering it and getting into fastboot
Click to expand...
Click to collapse
Thats the thing i get in to that no matter what i plugit in to charge it goes to the boot loader and it does it instantly no waiting time or the message that the bootloader is unlocked straight in to the bootloader
blocky3321 said:
Thats the thing i get in to that no matter what i plugit in to charge it goes to the boot loader and it does it instantly no waiting time or the message that the bootloader is unlocked straight in to the bootloader
Click to expand...
Click to collapse
This is fastboot. Does your device show up in "fastboot devices"? Make sure you have an up-to-date fastboot binary for the purpose.
For modern Linux distros you should already have the rules necessary. If not, try run fastboot commands using sudo or as root and see if the device would appear.
On the other hand, I noted that in some cases the fastboot interface may have problems responding. In that case, reboot bootloader, then run your fastboot flash commands as soon as the device restarts.
Install RSA from Lenovo.
Following the instruction to rescue your unit as well as getting boot.img for patching
Moreover, install latest Android Platform Tools
Copy boot.img to your unit and patch with Magisk, and copy the patched_boot.img back to host PC.
Then reboot in fastbootd (adb reboot fastboot) and flash patched_boot.img
LSS4181 said:
This is fastboot. Does your device show up in "fastboot devices"? Make sure you have an up-to-date fastboot binary for the purpose.
For modern Linux distros you should already have the rules necessary. If not, try run fastboot commands using sudo or as root and see if the device would appear.
On the other hand, I noted that in some cases the fastboot interface may have problems responding. In that case, reboot bootloader, then run your fastboot flash commands as soon as the device restarts.
Click to expand...
Click to collapse
It does not show up in fastboot and i have quite new adb and fastboot installed
blocky3321 said:
It does not show up in fastboot and i have quite new adb and fastboot installed
Click to expand...
Click to collapse
Well, get newest. Check drivers.
Arealhooman said:
Well, get newest. Check drivers.
Click to expand...
Click to collapse
ok got somewhere got back recovery but still goes back to the screen in the picture. Any way to flash the whole firmware.
blocky3321 said:
but still goes back to
Click to expand...
Click to collapse
Open Windows terminal, connect tablet to PC with adb/fastboot drivers installed.
Enter command:
fastboot set_active other
and again:
fastboot set_active other
then:
fastboot reboot
It might help.
f1tm0t said:
Open Windows terminal, connect tablet to PC with adb/fastboot drivers installed.
Enter command:
fastboot set_active other
and again:
fastboot set_active other
then:
fastboot reboot
It might help.
Click to expand...
Click to collapse
nope still doesnt work
V0latyle