Related
Hi, guys
By my stupidity my mate s marshmallow downgrade to lolipop.Now I am in CRR-UL00185B303(Andoid 5.1.1)
I try many things to go forward ..i failed many times .even stuck my phone also(thanks my old TWRP backup ).Aalo I lost my lost my security settings..iam not able to lock the phone by pin or finger print
Any body can give any suggestion..I have one marshmallow TWRP backup ..but that fails at the end of data backup..I dont know why.If i can go back to B114 also good ,,then i can update to B146 then update to marshmallow..
Lot of thanks in advance..
Try a factory reset for finger print
All,
Please do not discuss nor recommend using someone else's TWRP backup on your device. You're just asking for a phone brick to occur.
If any further discussion arises, then this thread will be closed. No questions .
-snickler
[/COLOR]
snickler said:
All,
Please do not discuss nor recommend using someone else's TWRP backup on your device. You're just asking for a phone brick to occur.
If any further discussion arises, then this thread will be closed. No questions .
-snickler
Click to expand...
Click to collapse
With All Due Respect
I Dont think that would be the case ... i was kinda stuck on a chinese crr-L09 firmware with my model being crr-ul00 Middle east . and i used a twrp backup from a european crr-l09 and then managed to get back to my stock crr-ul00 middle east firmware :laugh:
andromodgod said:
[/COLOR]
With All Due Respect
I Dont think that would be the case ... i was kinda stuck on a chinese crr-L09 firmware with my model being crr-ul00 Middle east . and i used a twrp backup from a european crr-l09 and then managed to get back to my stock crr-ul00 middle east firmware :laugh:
Click to expand...
Click to collapse
That may be the case for certain situations, but if there's a case of many people bricking their phones over some info found on here that they think SHOULD work without it properly being tested over dozens of situations, that wouldn't be good at all.
snickler said:
That may be the case for certain situations, but if there's a case of many people bricking their phones over some info found on here that they think SHOULD work without it properly being tested over dozens of situations, that wouldn't be good at all.
Click to expand...
Click to collapse
i can´t remember where i´ve found those information. i had bookmarked the bing-translated site some time ago but then deleted it since it ended in some nonsense discussion.
it was mostly about an "update" to MM, where people tried to change the phone localization from UL00 to L09 and update to B303 but failed and then used the MM TWRP Backups of some others.
Some ended in an bootloop and others had a corrupt system with FRP lock. I couldn´t tell if this happened because of corrupted backup files or because the users f****** up the recovery process.
Bing couldn´t translate everything to make sense.
They were lucky that they made a backup of the original system and so they were able to get back a fully funktional system.
i just wanted to warn you
I was running the L09C432B303 MM Beta and tried a method to rollback to B145, it was the method where you get a B114 Full OTA and flash the system.img, recovery.img, cust.img and boot.img however it didnt work I I restored my TWRP backup, however since then my version number in settings shows as
CRR-L09C900B303
Does anyone know how to get this back to C432??
i have rollback now and its realy easy.
make fallow:
install adb
download fallow:
HuaweiUpdateExtractor and Firmware 145 (when you will update 303 too)
Bring your phone in fastboot mode (make it of and hold power down and power)
install and open Huawei Update Extractor and open the FW 145
extract fallow data:
boot.img
cust.img
recovery.img
system.img
rename it so how i have named it and flash it with adb to your Phone
fastboot flash cust cust.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
When you will stay at 145 you can make now a Hardreset in recovery mode when you will update to MM let it boot to lollipop and go to update manual / local and update your Phone with MM update.zip
when its down go to recovery and reset your phone.
Ready
wolfsstolz said:
i have rollback now and its realy easy.
make fallow:
install adb
download fallow:
HuaweiUpdateExtractor and Firmware 145 (when you will update 303 too)
Bring your phone in fastboot mode (make it of and hold power down and power)
install and open Huawei Update Extractor and open the FW 145
extract fallow data:
boot.img
cust.img
recovery.img
system.img
rename it so how i have named it and flash it with adb to your Phone
fastboot flash cust cust.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
When you will stay at 145 you can make now a Hardreset in recovery mode when you will update to MM let it boot to lollipop and go to update manual / local and update your Phone with MM update.zip
when its down go to recovery and reset your phone.
Ready
Click to expand...
Click to collapse
That isnt a rollback - you'll find that when on B145 you cant activate security settings such as fingerprint ID. All it does it allow you to reinstall MM Beta Update...nothing more
brumgav said:
I was running the L09C432B303 MM Beta and tried a method to rollback to B145, it was the method where you get a B114 Full OTA and flash the system.img, recovery.img, cust.img and boot.img however it didnt work I I restored my TWRP backup, however since then my version number in settings shows as
CRR-L09C900B303
Does anyone know how to get this back to C432??
Click to expand...
Click to collapse
Fixed.....I think my downloads were corrupting on my laptop...finally fixed by downloading full B145 firmware...extracting boot.img, recovery.img, cust.img, userdata.img, system.img using the huaweiupdateextractor tool and flashing them via fastboot, once that completed I used the same firmware to by putting in /dload/ folder and when that completed I flashed the b303 update...now my region is back to C432 and I updated to B321 version on MM
Difference?
brumgav said:
Fixed.....I think my downloads were corrupting on my laptop...finally fixed by downloading full B145 firmware...extracting boot.img, recovery.img, cust.img, userdata.img, system.img using the huaweiupdateextractor tool and flashing them via fastboot, once that completed I used the same firmware to by putting in /dload/ folder and when that completed I flashed the b303 update...now my region is back to C432 and I updated to B321 version on MM
Click to expand...
Click to collapse
That´s interesting, however anyone knows what´s the difference between C432(Europe) and C900(Global)?.
I´m asking because I updated C432B145 to MM and ended up in C900B303(now on C900B321). Only issue so far is that LTE band 4 is not working, but don´t know if it was before updating to 6.0, as I was using the phone in Europe(LTE B3/B7).
rickylambert said:
That´s interesting, however anyone knows what´s the difference between C432(Europe) and C900(Global)?.
I´m asking because I updated C432B145 to MM and ended up in C900B303(now on C900B321). Only issue so far is that LTE band 4 is not working, but don´t know if it was before updating to 6.0, as I was using the phone in Europe(LTE B3/B7).
Click to expand...
Click to collapse
Only difference I could see was more options available in mobile data settings for your data plan
hi u can help me for make to downgrade from "beta marshmallow" to "lollipop" with mate's please
maurocasto said:
hi u can help me for make to downgrade from "beta marshmallow" to "lollipop" with mate's please
Click to expand...
Click to collapse
It's not yet possible...read the forum that you're posting in
hi guys,
yesterday i installed the oreo beta on my VTR-L29 but then i brickedd it *cry*. unfortunateley the unbrick methods found here in the forum don't work because the oreo update made some changes in the system file structure...
has anyone an idea what to do?
maybe someone can provide me a recovery image for twrp? (one for oreo, otherwise it wont work) so i can give this a try...
after over 10 hours of fiddeling around a found a really easy solution:
most of you know HWOTA helps with this, but the "normal" version wont work after flashing oreo. but this version is flashed via twrp and is still working!
but you will need a oreo compatible twrp, which you can find here
i know the links are to mate 9 software, but since the p10 and mate 9 are nearly identical, it works on the p10 as well
can you post the step by step guide?
i am on oreo 8.0.0.046 and want to flash another version, or downgrade to nougat because few things don't work on this version
i dont know if downgrading works, i just reflashed the latest oreo.
accordingly to the first link it should work, just flash the TWRP from the second link and then follow the instructions from the first link.
johdost said:
i dont know if downgrading works, i just reflashed the latest oreo.
accordingly to the first link it should work, just flash the TWRP from the second link and then follow the instructions from the first link.
Click to expand...
Click to collapse
failed install twrp- error find twrp 3.0.3, and i replaced to oero mate 9 recovery....
EDIT: success - problem was on the computer
johdost said:
i dont know if downgrading works, i just reflashed the latest oreo.
accordingly to the first link it should work, just flash the TWRP from the second link and then follow the instructions from the first link.
Click to expand...
Click to collapse
i did sucsses to install twrp but on the second step, when i press on install on twrp, the phone restart to erocovey and failed to find the files. what am i doing wrong?
i think that i am stuck with that version forever....
if you reboot to erecovery, you have not successfully installed twrp. you have to install it with "fastboot flash recovery_ramdisk <path to twrp>"
johdost said:
if you reboot to erecovery, you have not successfully installed twrp. you have to install it with "fastboot flash recovery_ramdisk <path to twrp>"
Click to expand...
Click to collapse
you misunderstood me.
i do have twrp, i created HWOTA8 folder on sd card, copied hwota8 update zip, MHA_RECOVERY8 No check and the 3 files that i renamed as it said. after that, from twrp i clicked on hwota8 update zip and begin flash, the phone reboot to stock recovery and failed to install - "files don't found".
please help me fegure out what's the problem.
thanks
t.h.i said:
you misunderstood me.
i do have twrp, i created HWOTA8 folder on sd card, copied hwota8 update zip, MHA_RECOVERY8 No check and the 3 files that i renamed as it said. after that, from twrp i clicked on hwota8 update zip and begin flash, the phone reboot to stock recovery and failed to install - "files don't found".
please help me fegure out what's the problem.
thanks
Click to expand...
Click to collapse
EDIT : the process is sucsses, but its the same version.... 8.0.0.046
Bricked, no TWRP access, any ideas?
Hi.
I know this about a P10, I have a P10 Plus (VKY-L29C605), but the process should be similar, I think.
I bricked my phone after succesfully upgrading from B174 to B321 using HWOTA. After which I decided, since I was at it, to flash the Hyperplus Kernel. This led to a bootloop. To fix it I decided to just go ahead and HWOTA B321 all over again and get over it, and would have probably gone just fine, except I decided to rebrand (C605 > C432) while I was doing that, silly (no, stupid) mistake. This led to the brick I am currently expriencing, I have no recovery access, erecovery or TWRP.
So now I am left trying to unbrick the phone. I extracted the UPDATE.APP for both update_all_hw.zip and update.zip using the Huawei Extractor Tool with no difficulty, except unbricking methods ask for boot.img, which I could not find, so I went along without it and flashed: cust.img, recovery_ramdisk.img (using fastboot recovery_ramdisk command for Oreo), and system.img. All of the commands completed succesfully, but no shebang, still bricked and no recovery access. I figure this has to do with the rebrand as the result after executing the command "fastboot getvar vendorcountry" shows the rebrand pulled through (hw/eu 432).
I am currently downloading HWOTA8.zip (3GB worth of download) to see if I can do something it. I am also downloading the L29C432B360 OTA-FULL, since I believe I am not getting any progress becuase I used the updates for L29C605B321.
The kind people at funkyhuawei told me they could fix it with their tool, but I don't have the money for that right now.
I will post updates, but any ideas would be greatly appreciated.
Many of us have posted over this in the last couple of days. Seems like Funky Huawei unbrick tool was the mehtod to get it work for me. You could try that!
or use dc-phoenix for me it worked (= in the moment i try to capture the usb ports kommunikation so i have the tool with the aktual firmware longer for 3 days :silly:
would first give dc a try 20 bucks for 3 days is ok i think (=
johdost said:
hi guys,
yesterday i installed the oreo beta on my VTR-L29 but then i brickedd it *cry*. unfortunateley the unbrick methods found here in the forum don't work because the oreo update made some changes in the system file structure...
has anyone an idea what to do?
maybe someone can provide me a recovery image for twrp? (one for oreo, otherwise it wont work) so i can give this a try...
Click to expand...
Click to collapse
Must download some software for your phone, unzip update.zip, decompile UPDATE.APP to .iso files, (like recovery.iso, system, iso, vendor iso, boot iso) use fastboot and 10 minuts job, I brik my device over 10 thimes, and repair it.
So I was able to get the C432B360 firmware and I flashed it, but no I can't enter recovery mode because the battery is low (red lightning bolt/red led flash). Anybody know how to charge or force recovery mode boot from fastboot?
If anyone needs, can use my DC-Phoenix account, I don`t need it anymore.
Your username is: cesedy
Your password is: dnL4eHEm
Greting
ure3808 said:
Must download some software for your phone, unzip update.zip, decompile UPDATE.APP to .iso files, (like recovery.iso, system, iso, vendor iso, boot iso) use fastboot and 10 minuts job, I brik my device over 10 thimes, and repair it.
Click to expand...
Click to collapse
Greeting,
Can you explain the procedure of how to do it?
Thank you
Today, I had successfully updated my L09-C432 (rebranded to L29) to Oreo. I decide to keep going and try to root using the magisk method present in the guide section.
During that process, I had several error, so I decided to flash the ramdisk. I all went downhill from there, impossible to restore any of the images I had on TWRP. Eventually I tried following HWOTA but for some reason. TWRP for oreo is not recognize by ADB on my system, I then decided to launch the upgradeoreo.zip according to this method as I had the files on my SD-card prior. Which led me to be unable to get into fastboot.
I am now left with the following error>
ERROR MODE:
Attention!
Please update system again
green android of death
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
All I have left at this point is a functional fastboot,
I have tried:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash kernel kernel.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash ramdisk ramdisk.img
All of which complete successfully but none of them help me get forward. I am left with the same error.
All of which were extracted from the UPDATE.APP of the OREO update I had successfully completed on my phone.
Concerning TWRP:
fastboot flash recovery twrp.img (nougat version) fails.
fastboot flash recovery twrp.img (oreo version) succeeds but I am left with the same error.
fastboot flash recovery twrp.img (HWOTA8 version) succeds but left with the same error.
I have wandered the forums and tried a diversity of suggestion none of them seemed to work in my case.
What are your suggestion to fix this problem?
Any help you can provide is much appreciated.
I can probably find a way to pop my SD_Card into my laptop if necessary.
Same problem here, I have tried multi_tool 8 without any success. Maybe someone you can share a TWRP backup?
I was wondering if the dload method could be an option? Which firmware to use in that case?
There is Huawei official service ROM for P10 Lite and P10 Plus. Cannot find for P10.
Do you think the Funky Huawei unbrick tool would resolve this (($$$, but cheaper than a non-warranty repair...)
If so would I just use the circa 4 GByte update.app file from the update.zip firmware file, rather than the smaller update.app from update_all_hw.zip?
grockstar said:
Do you think the Funky Huawei unbrick tool would resolve this (($$$, but cheaper than a non-warranty repair...)
If so would I just use the circa 4 GByte update.app file from the update.zip firmware file, rather than the smaller update.app from update_all_hw.zip?
Click to expand...
Click to collapse
I tried the dload method that is a no go. Besides the other option DC-phoenix (which is a pay mehtod as well ) I feel like these are our last resort.
grockstar said:
Do you think the Funky Huawei unbrick tool would resolve this (($$$, but cheaper than a non-warranty repair...)
If so would I just use the circa 4 GByte update.app file from the update.zip firmware file, rather than the smaller update.app from update_all_hw.zip?
Click to expand...
Click to collapse
And yes you should use the 4.3GByte update.app file. Are you trying the tool? If so, let us know how it works out! It is the next step for me.
martindoublem said:
And yes you should use the 4.3GByte update.app file. Are you trying the tool? If so, let us know how it works out! It is the next step for me.
Click to expand...
Click to collapse
Well, I coughed up the cash to FunkyHuwawei and have made some progress....
After using their unbrick tool, I now have access to eRecovery, and am pondering the best way to fully flash the ROM.
The Funky Huawei eRecovery method doesn't seem to work (I did change my router's DNS as instructed), and I'm hesitant to try the manual update method again given the issues people seem to be having with it.
Any suggestions?
grockstar said:
Well, I coughed up the cash to FunkyHuwawei and have made some progress....
After using their unbrick tool, I now have access to eRecovery, and am pondering the best way to fully flash the ROM.
The Funky Huawei eRecovery method doesn't seem to work (I did change my router's DNS as instructed), and I'm hesitant to try the manual update method again given the issues people seem to be having with it.
Any suggestions?
Click to expand...
Click to collapse
Well I guess I am going to fork up the cash too. ($100 in one day for him, not bad eh?)
Can you restore TWRP? maybe you can follow the HWOTA method without the first couple of steps? Also, can you not recover using the dload method then or just download the software from the recovery?
Well I can confirm, the fix worked splendidly, it got me in erecovery where I was able to delete the userdata (unfortunate but perhaps necessary).
Then a couple of reboots and I am back in an Android. So happy!
martindoublem said:
Well I guess I am going to fork up the cash too. ($100 in one day for him, not bad eh?)
Can you restore TWRP? maybe you can follow the HWOTA method without the first couple of steps? Also, can you not recover using the dload method then or just download the software from the recovery?
Click to expand...
Click to collapse
So it looks like the unbrick tool actualy installed the full ROM correctly - I can't have been giving it enough time to boot.
However the first time it booted the DPI was screwy just as it was after I mistakenly flashed the P10+ Oreo ROM (maybe the data partition hadn't been wiped). But a quick factory reset and all's well, and I'm over the moon to have rescued my phone with a little (i.e. lot) of help from FunkyHuawei - and a bit of cash.
Now to decide whether I want/need to risk rooting again...
grockstar said:
So it looks like the unbrick tool actualy installed the full ROM correctly - I can't have been giving it enough time to boot.
However the first time it booted the DPI was screwy just as it was after I mistakenly flashed the P10+ Oreo ROM (maybe the data partition hadn't been wiped). But a quick factory reset and all's well, and I'm over the moon to have rescued my phone with a little (i.e. lot) of help from FunkyHuawei - and a bit of cash.
Now to decide whether I want/need to risk rooting again...
Click to expand...
Click to collapse
Rooting is where it all went to **** for me. I am staying the hell away from it until a lot of people confirm it works fine!
Are you having only limited functionality as well? It seems like we have to reinstall the update data file as well as the update hw file?
martindoublem said:
Are you having only limited functionality as well? It seems like we have to reinstall the update data file as well as the update hw file?
Click to expand...
Click to collapse
Limited in what respect? Mine seems fine so far - the radios work (cellular, WiFi, Bluetooth) and the system and the few apps I've tried so far are working as expected.
The notification toolbar is gone? Is that normal? Did i miss out on android removing them?
martindoublem said:
The notification toolbar is gone? Is that normal? Did i miss out on android removing them?
Click to expand...
Click to collapse
Nope, my notification toolbar is working.
A factory reset fixed some weirdness for me, but you said you'd wiped userdata in eRecovery which I guess has the same effect?
used the dc-phoenix tool with the one part Update and now my phone is back (= it is worth it 20 bucks because i have now 3 days for testig and rebuilding (=
martindoublem said:
Today, I had successfully updated my L09-C432 (rebranded to L29) to Oreo. I decide to keep going and try to root using the magisk method present in the guide section.
During that process, I had several error, so I decided to flash the ramdisk. I all went downhill from there, impossible to restore any of the images I had on TWRP. Eventually I tried following HWOTA but for some reason. TWRP for oreo is not recognize by ADB on my system, I then decided to launch the upgradeoreo.zip according to this method as I had the files on my SD-card prior. Which led me to be unable to get into fastboot.
I am now left with the following error>
ERROR MODE:
Attention!
Please update system again
green android of death
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
All I have left at this point is a functional fastboot,
I have tried:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash kernel kernel.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash ramdisk ramdisk.img
All of which complete successfully but none of them help me get forward. I am left with the same error.
All of which were extracted from the UPDATE.APP of the OREO update I had successfully completed on my phone.
Concerning TWRP:
fastboot flash recovery twrp.img (nougat version) fails.
fastboot flash recovery twrp.img (oreo version) succeeds but I am left with the same error.
fastboot flash recovery twrp.img (HWOTA8 version) succeds but left with the same error.
I have wandered the forums and tried a diversity of suggestion none of them seemed to work in my case.
What are your suggestion to fix this problem?
Any help you can provide is much appreciated.
I can probably find a way to pop my SD_Card into my laptop if necessary.
Click to expand...
Click to collapse
Go to rescue mod, you plug in your device in computer, and hold vol down and pow button, than you go in rescue mod, and use fastboot to repair your device.
Can confirm DC-Phoenix and only for 20eur.
ure3808 said:
Go to rescue mod, you plug in your device in computer, and hold vol down and pow button, than you go in rescue mod, and use fastboot to repair your device.
Click to expand...
Click to collapse
Ha! you are funny! Several of us mentioned here that fastboot didn't work in our case to repair the device.
I was rooted through Magisk on firmware .255, but I saw an approved update for firmware .280 which I wanted, and I also wanted to go back to stock for a while. I downloaded the update.zip, extracted the .img needed and flashed accordingly; cust, erecovery, system, cache, kernel, recovery, userdata, etc, all I could.
I now can't get it to boot no matter what I try. I always end up on the screen "Your device has been unlocked and can't be trusted" and then stuck on "Your device is booting now". I can get into eRecovery and/or flash TWRP.
I've tried the below;
Flashing dload folder on a USB OTG
Flashing update zip in TWRP
Flashing update zip with Huruupdater in TWRP
Flashing through fastboot update (update.app extracted)
Flashing through fastboot update_full_base (update.app extracted)
Going through HiSuite - it sees the recovery but then says "No recovery packages found for your phone"
Wipe data etc.
I did forget to remove fingerprint security before I did this, my bootloader is unlocked and FRP.
Genuinely never bricked a phone before! Any help would be appreciated.
I think it's because I need to flash boot.img but I can't see that when I extract from update.app
Does anyone have one please?
Don't make me buy a pixel tomorrow!
belloni said:
I think it's because I need to flash boot.img but I can't see that when I extract from update.app
Does anyone have one please?
Click to expand...
Click to collapse
it because there's no boot.img for EMUI 9, it's recovery_ramdis.img and kernel.img did you flash that ?
try to pull recovery_ramdis.img from the Update.app and patch it using latest magisk 19.4 and flash it then try to boot again
otonieru said:
it because there's no boot.img for EMUI 9, it's recovery_ramdis.img and kernel.img did you flash that ?
try to pull recovery_ramdis.img from the Update.app and patch it using latest magisk 19.4 and flash it then try to boot again
Click to expand...
Click to collapse
Yeah I've flashed those two.
How can I patch it if I can only get into TWRP?
belloni said:
Yeah I've flashed those two.
How can I patch it if I can only get into TWRP?
Click to expand...
Click to collapse
EDIT: I've found the old magisk_patched.img but when I flash it says "FAILED (remote: partition length get error)
belloni said:
Yeah I've flashed those two.
How can I patch it if I can only get into TWRP?
Click to expand...
Click to collapse
from other phone with magisk installed.
other thing you might want to try is enter stock recovery (not TWRP) and wipe /data and cache from there
just a heads up though,
your way of updating the OS is totally dangerous, you could.messed up partition,
you should use EMUI Flasher instead
I have a guide to fix this in the guides section. Follow it and you'll be fine.
Find somebody that had a p20 pro rooted to send you a backup of their software (with the data partition wiped).
https://forum.xda-developers.com/showpost.php?p=79107368&postcount=82
Hi everyone,
I have some months before accidentally reset after ota update on magisk and lost root. Unfortunately I cant find this FW anywhere since it was almost immediatly been replaced by 10.0.16, and the only thread having such old firmware was using filehosting from which the links expired.
I tried doing a system ota, but it won't work. I don't expect anyone to extract the boot.img for me just share the 10.0.14. if available, i would prefer not to wipe system data, since now without root i can't backup, and Helium is no longer supported.
Thank You.
Ikarus01 said:
Hi everyone,
I have some months before accidentally reset after ota update on magisk and lost root. Unfortunately I cant find this FW anywhere since it was almost immediatly been replaced by 10.0.16, and the only thread having such old firmware was using filehosting from which the links expired.
I tried doing a system ota, but it won't work. I don't expect anyone to extract the boot.img for me just share the 10.0.14. if available, i would prefer not to wipe system data, since now without root i can't backup, and Helium is no longer supported.
Thank You.
Click to expand...
Click to collapse
OTA updates usually don't touch the boot image so you could use the fastboot or recovery ROM V10.0.13.0 from here https://flashxiaomi.com/download-install-miui-rom-for-xiaomi-mi-a2-all-miui-firmwares/ also you can flash a recovery and backup your boot image to patch it through Magisk or flash directly the zip (a lower version)
SubwayChamp said:
OTA updates usually don't touch the boot image so you could use the fastboot or recovery ROM V10.0.13.0 from here https://flashxiaomi.com/download-install-miui-rom-for-xiaomi-mi-a2-all-miui-firmwares/ also you can flash a recovery and backup your boot image to patch it through Magisk or flash directly the zip (a lower version)
Click to expand...
Click to collapse
Thank you for replying,
i thought about it but if it proves not the case, and they changed the hex i wouldnt like bootloops or problems down the road. If it works i will try to backup and go to latest android 9, since many are complaining about version 10 with emmc apparently forgotten.
Also unfortunately i lost twrp, and don't have a sd cardfor flashing,and wouldn't like to wipe data to install twrp.
I thought about it and my only course of action is getting the boot.img, dd is out of option since I am not rot, is there a non root way to unpack if it turns out 10.0.13 causes a bootloop?
Sorry if some things don't make sense I am getting back to this after a long hiatus, can I still extract the img. from zip, or do I have to upack it with python?
Thank you.
Ikarus01 said:
Thank you for replying,
i thought about it but if it proves not the case, and they changed the hex i wouldnt like bootloops or problems down the road. If it works i will try to backup and go to latest android 9, since many are complaining about version 10 with emmc apparently forgotten.
Also unfortunately i lost twrp, and don't have a sd cardfor flashing,and wouldn't like to wipe data to install twrp.
I thought about it and my only course of action is getting the boot.img, dd is out of option since I am not rot, is there a non root way to unpack if it turns out 10.0.13 causes a bootloop?
Sorry if some things don't make sense I am getting back to this after a long hiatus, can I still extract the img. from zip, or do I have to upack it with python?
Thank you.
Click to expand...
Click to collapse
It was a minor/small update, I doubt it causes a bootloop.
You can flash Orange Fox through fastboot, no need to wipe data and from there either just flash Magisk or backup your boot and patch it if you prefer this method.
Not sure to which image you refer, no need to unpack the image by any method.
SubwayChamp said:
It was a minor/small update, I doubt it causes a bootloop.
You can flash Orange Fox through fastboot, no need to wipe data and from there either just flash Magisk or backup your boot and patch it if you prefer this method.
Not sure to which image you refer, no need to unpack the image by any method.
Click to expand...
Click to collapse
Thank you again, for orange fox especially,
I thought I needed Payload dumper, or is that only after android 10?
Thanks for the help, i only liked your replies, i dont know if they removed thanks globally or only on QA forums
Ikarus01 said:
Thank you again, for orange fox especially,
I thought I needed Payload dumper, or is that only after android 10?
Click to expand...
Click to collapse
No, if you refer to a method to unpack the ROM it comes either in zip format (recovery) or in tar.gz format (fastboot), you just need to unpack it with something like Winrar other 7zip and inside you will find the boot image.
It's a global change, in this new platform they removed the thanks option, I disagree but this is how it is.
SubwayChamp said:
No, if you refer to a method to unpack the ROM it comes either in zip format (recovery) or in tar.gz format (fastboot), you just need to unpack it with something like Winrar other 7zip and inside you will find the boot image.
Click to expand...
Click to collapse
Oh that is good to hear!
Thank You again you really helped me here.
Sadly I can only like your post, I guess that is the new rep system?
Have a good day!
Cheers