Related
So i need to flash a cust.img through recovery because fastboot doenst work gives me "remote:command not allowed fastboot" but if i want to flash it through the recovery it says "Error: File larger then target device" i basicly only need to flash the cust.img to fix my phone.
What i tried:
Use fastboot, tried new version of android SDK
flashed diffrent recoverys, same results.
Please help i really need my phone ;/
Demian3112 said:
So i need to flash a cust.img through recovery because fastboot doenst work gives me "remote:command not allowed fastboot" but if i want to flash it through the recovery it says "Error: File larger then target device" i basicly only need to flash the cust.img to fix my phone.
What i tried:
Use fastboot, tried new version of android SDK
flashed diffrent recoverys, same results.
Please help i really need my phone ;/
Click to expand...
Click to collapse
Are you on stock rom? if so you have to enable oem for fastboot to work, it should be somewhere in the developer settings. otherwise i wouldn't know
jimandroidnerd said:
Are you on stock rom? if so you have to enable oem for fastboot to work, it should be somewhere in the developer settings. otherwise i wouldn't know
Click to expand...
Click to collapse
Im on b130 kiw l21 my phone shows wrong data under about phone and i cant apply a update to go back to stock from the dload file it simply instant says syatem update failed. I just want to revert back to stock then update to b140 and then to B330 emui 4.0 but i cant because the dload keeps failing
Demian3112 said:
Im on b130 kiw l21 my phone shows wrong data under about phone and i cant apply a update to go back to stock from the dload file it simply instant says syatem update failed. I just want to revert back to stock then update to b140 and then to B330 emui 4.0 but i cant because the dload keeps failing
Click to expand...
Click to collapse
you say you are on b130 but than you say you wanna go to stock rom? I dont really understand what you are telling me here
jimandroidnerd said:
you say you are on b130 but than you say you wanna go to stock rom? I dont really understand what you are telling me here
Click to expand...
Click to collapse
My device got bricked B330. So i had to reflash some stuff and ended up with false info under the section About Phone i had the same issue as him So i followed that instructions but i couldnt flash the Cust.img in the recovery (twrp) it gives me the error that i have as title. Without flashing the cust.img i cant use a revert package through dload since my Phone shows other information then the update package (denies to do the update instant) . My question how can i fix the error "File bigger then target device" so i can flash the Cust.img since fast boot doesnt work (error remote: command not allowed recovery) and twrp is my only option..
Instructions i followed to get back to stock.
Flash Boot.img, system.img, cust.img through twrp > flash stock recovery > Apply UK back to stock through dload
I cant flash cust.img so step 1 fails and i cant do the rest.
Anyone a idea why i cant flash this file through TWRP and fastboot? This is littery my last hope to get back to stock ;/
Demian3112 said:
Anyone a idea why i cant flash this file through TWRP and fastboot? This is littery my last hope to get back to stock ;/
Click to expand...
Click to collapse
I could give you my twrp backup? Maybe that will help
jimandroidnerd said:
I could give you my twrp backup? Maybe that will help
Click to expand...
Click to collapse
I mean i should be able to flash cust.img through fastboot right?
Demian3112 said:
I mean i should be able to flash cust.img through fastboot right?
Click to expand...
Click to collapse
No, i meant i can give u my twrp backup so you van restore it from twrp. Do you want it or not?
jimandroidnerd said:
No, i meant i can give u my twrp backup so you van restore it from twrp. Do you want it or not?
Click to expand...
Click to collapse
Nvm thanx! Fixed it im an idiot.
I was so bussy almost 2 days with this. I have no experience (14old) and i simply went bussy so much with it that i started looking over the simple things. I fixed it now it left me with a damm headache thnx anyways, i learned something again!
jimandroidnerd said:
No, i meant i can give u my twrp backup so you van restore it from twrp. Do you want it or not?
Click to expand...
Click to collapse
Oke i got a bit too excited. The fingerprint option is gone like it never has been there. Honor boot logo has a red H, i get the b140 update but cant apply it same issue with dload. Would you mind sharig your TWRP update? If it is possible for B330 and B130 Thx!
Demian3112 said:
Oke i got a bit too excited. The fingerprint option is gone like it never has been there. Honor boot logo has a red H, i get the b140 update but cant apply it same issue with dload. Would you mind sharig your TWRP update? If it is possible for B330 and B130 Thx!
Click to expand...
Click to collapse
You need to use kiwi_twrp_5-14_recovery.img
and the backup needs to contain all these partitions
boot.emmc.win
cust.ext4.win"
erecovery.emmc.win"
firmware.info"
firmware.vfat.win"
misc.emmc.win"
persist.ext4.win
system.ext4.win000
system.ext4.win001
restore those and you'll be back in business
This rom also contains the /cust partition for b130
http://forum.xda-developers.com/honor-5x/development/custom-rom-starter-template-honor-5x-t3328809
clsA said:
You need to use kiwi_twrp_5-14_recovery.img
and the backup needs to contain all these partitions
boot.emmc.win
cust.ext4.win"
erecovery.emmc.win"
firmware.info"
firmware.vfat.win"
misc.emmc.win"
persist.ext4.win
system.ext4.win000
system.ext4.win001
restore those and you'll be back in business
This rom also contains the /cust partition for b130
http://forum.xda-developers.com/honor-5x/development/custom-rom-starter-template-honor-5x-t3328809
Click to expand...
Click to collapse
This is what i got.. http://prntscr.com/brv0ay the Repository doesnt contain this files aswell any idea? Is it possible to flash for example a full Kiw L22 rom and then use a revert package for L21 through Dload?
Oke what i did:
Wipe
Apply Cust partition with terminal
Apply backup/restore
flash stock recovery
Boots same issue, I just need the dload to get to work so i can flash the recovery pack. But it stays at 0 percent even after 15 mins.
What i found out is that i dont have the stock firmware (Dont have fingerprint and stuff, device doenst show as KIW L21), so i doenst do a ota update and local update ofcourse. I need a TWRP backup with firmware included. What im trying now is installing L21 MIDDLE-EAST firmware and then try to use a revert package for L21 through OTA.
Arobase40 said:
Well, I'm not sure this is a good idea as it took me 11 days to upgrade from B140 (Lollipop) to B330 (Marshmallow) and only a few minutes to brick my Honor 5x L21 using a backup from kiwi_twrp_5-14_recovery.img when I wanted to revert back to B140... ^^
At boot time after the restore, I have an animated red H letter from the Honor Logo and impossible to get back to the welcome screen nor to any other screen so I don't have access to TWRP anymore...
We really need to have access to the official downgrade firmware from Honor !!!
Click to expand...
Click to collapse
Same issue.. I get red H honor logo.. cant apply a single update through ota/dload and finger print is gone.. I can do everything, installing apps and stuff but i cant revert back to full stock.
clsA said:
You need to use kiwi_twrp_5-14_recovery.img
and the backup needs to contain all these partitions
boot.emmc.win
cust.ext4.win"
erecovery.emmc.win"
firmware.info"
firmware.vfat.win"
misc.emmc.win"
persist.ext4.win
system.ext4.win000
system.ext4.win001
restore those and you'll be back in business
This rom also contains the /cust partition for b130
http://forum.xda-developers.com/honor-5x/development/custom-rom-starter-template-honor-5x-t3328809
Click to expand...
Click to collapse
Could you link me the firmware.vfat and misc.emmc and persist.ext. Is there a way to make the update.app a flashable zip? Anyways any idea what i still could do?
Anyways what would you recommend me to go back to stock right now? Is it cuz my system partition is messed up? How to fix? thx anyways!
Arobase40 said:
As I said it is NOT really a good idea to use a TWRP backup to revert back from Marshmallow to Lollipop as it will brick your device !
I also said : ask your local Honor technical support for an official revert back firmware as your whole system is obviously messed up.
I don't know how you upgraded your smartphone but better downgrade to Lollipop first and try to upgrade again to MM a "proper way"...
Click to expand...
Click to collapse
]
Thats the point.. I simply cant. Phone doenst accept dload updates instant says "System Failed", most near honor technical support is 98 km out.
Ok anyways does anyone have a B330 full stock backup?
Arobase40 said:
I didn't say you had to move yourself to a technical support but place a phone call or mail them. You should find their phone number or their email address from your the Honor Website.
I'll do it myself by tomorrow...
Click to expand...
Click to collapse
I fixed it. Go to hi honor and search for honor 5x firmware, download it unpack it put the update.app on dload on microsd make sure you flashed stock recovery through fastboot hold power + volume down + volume up until it vibrates and done. I couldnt install any dload file on XDA the error "system failed" means the update is not for your device. The one on hihonor was the only one that worked for me ive been bussy 3 days its worth trying. I can link/upload you the download and instructions if you want to but ill do it tomorrow.
jimandroidnerd said:
No, i meant i can give u my twrp backup so you van restore it from twrp. Do you want it or not?
Click to expand...
Click to collapse
Hello i have the same problem could you please give me your backup so i can try it?
Same issue
Hi guys,
I am using the link below to perform the restore to stock from CM13 but I think I am not interpreting the questions in this post correctly.
http://forum.xda-developers.com/honor-5x/how-to/guide-kiw-l24-to-stock-t3318268
I tried to follow them to get my Honor 5x back to stock rom (while still keeping TWRP) and it was a no go. I kept getting stuck in a boot loop. I was able to immediately reflash CM13 though and get it functionaly. Would someone be kind enough to verify for me as to what steps exactly I need to follow (including ROM names, etc.)? I would greatly appreciate it.
Thanks.
@DigiGoon here's a person needing your help
I have a couple questions for you:
1) Before flashing CM13, what stock firmware version were you on? (e.g. b130, b140, b151, b331)
2) Before flashing CM13, did you take a NANDROID backup of your stock setup? Most guides have this step.
Follow these steps, and you'll get your stock ROM back.
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
Hope this helps you.
@DigiGoon
You are a lifesaver. That seems to have done the trick. Thanks a lot man!
fistfullofbeer said:
Hi guys,
I am using the link below to perform the restore to stock from CM13 but I think I am not interpreting the questions in this post correctly.
http://forum.xda-developers.com/honor-5x/how-to/guide-kiw-l24-to-stock-t3318268
I tried to follow them to get my Honor 5x back to stock rom (while still keeping TWRP) and it was a no go. I kept getting stuck in a boot loop. I was able to immediately reflash CM13 though and get it functionaly. Would someone be kind enough to verify for me as to what steps exactly I need to follow (including ROM names, etc.)? I would greatly appreciate it.
Thanks.
Click to expand...
Click to collapse
There is also a full, latest twrp, recovery backup o.o for b331
You restore everything except data, erecovery, and recovery... 1.6 gig download o.o does the job in one fell swoop as long as you have latest twrp.
Just did this the other day...
fistfullofbeer said:
@DigiGoon
You are a lifesaver. That seems to have done the trick. Thanks a lot man!
Click to expand...
Click to collapse
Happy to help buddy.
DigiGoon said:
Follow these steps, and you'll get your stock ROM back.
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Flash all other extracted files similarly firing these commands.
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
Hope this helps you.
Click to expand...
Click to collapse
Just wondering, does this replace the TWRP recovery with stock? And is there a way to keep TWRP if so?
gabepaul said:
Just wondering, does this replace the TWRP recovery with stock? And is there a way to keep TWRP if so?
Click to expand...
Click to collapse
Yes it does replace, and you simply need to reflash TWRP again
gabepaul said:
Just wondering, does this replace the TWRP recovery with stock? And is there a way to keep TWRP if so?
Click to expand...
Click to collapse
It replaces the TWRP, and if you are flashing stock via 3 button method, then there is no way you can keep it, but if you are getting on stock by flashing individual files then just dont flash the recovery file and you will just have the TWRP alone.
gabepaul said:
Just wondering, does this replace the TWRP recovery with stock? And is there a way to keep TWRP if so?
Click to expand...
Click to collapse
Instead of flashing full update.app , i can help u just to stop doing a lot of work after flash
DigiGoon said:
It replaces the TWRP, and if you are flashing stock via 3 button method, then there is no way you can keep it, but if you are getting on stock by flashing individual files then just dont flash the recovery file and you will just have the TWRP alone.
Click to expand...
Click to collapse
So which is the three button method and which is the other?
gabepaul said:
So which is the three button method and which is the other?
Click to expand...
Click to collapse
Three button method is nothing but by placing update.app in /sdcard/dload/
And then put off the phone followed by pressing vol down+vol up+ power button . This will let it install full stock rom and phone looks brand new in terms of software
gabepaul said:
So which is the three button method and which is the other?
Click to expand...
Click to collapse
As @gopinaidu77 said about three button method, its just that. And about the other one, in that you have to extract all the important img files from UPDATE.APP and flash it via fastboot commands.
DigiGoon said:
As @gopinaidu77 said about three button method, its just that. And about the other one, in that you have to extract all the important img files from UPDATE.APP and flash it via fastboot commands.
Click to expand...
Click to collapse
so I've tried both, and I'm getting stuck on the "Honor for the brave, powered by Android" screen.
I should probably also add that im trying to downgrade from lineage 14.0 Nougat to the android 6.1 emui 3.1
gabepaul said:
so I've tried both, and I'm getting stuck on the "Honor for the brave, powered by Android" screen.
I should probably also add that im trying to downgrade from lineage 14.0 Nougat to the android 6.1 emui 3.1
Click to expand...
Click to collapse
Sorry. 6.0.1 is emui 4.0.1 . Well bro , u can still unbrick ur device . Can i know which build number u are on before u flashed lineageos ?
gopinaidu77 said:
Sorry. 6.0.1 is emui 4.0.1 . Well bro , u can still unbrick ur device . Can i know which build number u are on before u flashed lineageos ?
Click to expand...
Click to collapse
Oh yeah, I have restored it already. I made a nandroid backup, and so when it happened, I just rebooted into fastboot and reflashed TWRP, then restored my phone from the backup. Not sure which build. Wondering what went wrong? And how I can successfully convert to stock
gabepaul said:
Oh yeah, I have restored it already. I made a nandroid backup, and so when it happened, I just rebooted into fastboot and reflashed TWRP, then restored my phone from the backup. Not sure which build. Wondering what went wrong? And how I can successfully convert to stock
Click to expand...
Click to collapse
Extract UPDATE.APP via Huawei Update Extractor tool, pull out relevant img files (system.img, boot.img, recovery.img, recovery2.img(if not in your device), cust.img) flash this one by one via fastboot by booting your device in fastboot mode, fire the given below commands.
Code:
fastboot flash <img name w/o extension> <full path to the relevant img file>
After this try the three button method, if it doesn't work then boot into eRecovery then tap "Download Latest Firmware". It will connect to Wi-Fi and will start downloading the latest firmware of your device. After the process gets completed you'll be on stock ROM with your bootloader in "Locked" state.
You are guiding wrong bro . There is a need of extension too. Else it will give error saying file not found
CUST issue
Hi,
I tried to do the same, Boot.img, system.img and recovery.img are flashed successfully but I cannot flash CUST.img, following error occurs, please help.
it says: while writing 'cust'...,
error: FAILED (remote: command not allowed)
Please help, thanks in advance.
I just received the OTA update from 7.1.1 DP2 to MNF26F.
Here is the OTA url to download:
https://android.googleapis.com/pack.../2c6f100d0f9ef8ccee10d661b7454adb7161aa0e.zip
You can sideload it into your device and you will be on the official 7.1.1 release.
Just got it too. Only 27 megabytes.
Just download it... Where the downloaded OTA file located in our file system?
deani77 said:
Just download it... Where the downloaded OTA file located in our file system?
Click to expand...
Click to collapse
/data/data/com.google.android.gms/app_download/
If rooted on dp2 I can just download and install through TWRP, no?
I installed this and I got a boot loop, so careful. First time ever with an issue and I didn't bring my cable
thedead69 said:
I installed this and I got a boot loop, so careful. First time ever with an issue and I didn't bring my cable
Click to expand...
Click to collapse
Any more info? What version were you on before? Rooted? Used TWRP? What version of TWRP?
RaceFaceXC said:
If rooted on dp2 I can just download and install through TWRP, no?
Click to expand...
Click to collapse
No. ota only installs on stock images.
http://forum.xda-developers.com/showthread.php?p=62924118
Points 12/ and 13/
RaceFaceXC said:
Any more info? What version were you on before? Rooted? Used TWRP? What version of TWRP?
Click to expand...
Click to collapse
Rooted with SuperSU on DP2. Using flashfire
I got this OTA this afternoon. Stock DP2 on Verizon.
rchtk said:
No. ota only installs on stock images.
http://forum.xda-developers.com/showthread.php?p=62924118
Points 12/ and 13/
Click to expand...
Click to collapse
Thank.
I think I knew this at some point. Wasn't sure so that's why I asked.
thedead69 said:
Rooted with SuperSU on DP2. Using flashfire
Click to expand...
Click to collapse
Can you or someone help me??
Yesterday I received the notification. Download the file from here, as I am rooted, twrp and custome kernel.
I tried to flash this via flashfire, but after phone reboots, nothing happens... am I doing something wrong??
I open flashfire, choose Flash ZIP or OTA, choose the file, on the options I don't change anything (it only has Restore boot and recovery images ticked) and then on the main screen I press Flash. Then phone reboots and nothing happens, it enters again on android.
Someone??
onesolo said:
Can you or someone help me??
Yesterday I received the notification. Download the file from here, as I am rooted, twrp and custome kernel.
I tried to flash this via flashfire, but after phone reboots, nothing happens... am I doing something wrong??
I open flashfire, choose Flash ZIP or OTA, choose the file, on the options I don't change anything (it only has Restore boot and recovery images ticked) and then on the main screen I press Flash. Then phone reboots and nothing happens, it enters again on android.
Someone??
Click to expand...
Click to collapse
Can you enter bootloader or recovery with power/vol dn? If so, try sideloading a stock image? Or, if you can get into recovery restore with a nandroid backup?
Link ota for NEXUS 5X PLEASE
Link ota for NEXUS 5X PLEASE
hanibioud said:
Link ota for NEXUS 5X PLEASE
Click to expand...
Click to collapse
Wrong forum. This is for the Nexus 6P.
RaceFaceXC said:
Can you enter bootloader or recovery with power/vol dn? If so, try sideloading a stock image? Or, if you can get into recovery restore with a nandroid backup?
Click to expand...
Click to collapse
I didn't even try, cause I can enter on twrp fine. As I said, I have twrp and root. My sys is obviously modified. I'm not even trying to sideloaded over bootloader cause it wont work. The same thing on TWRP. I think that sideloading on TWRP only works with full OTAs and not with this one, that is an incremental OTA file, unless I'm completely wrong (I wish).
Anyone's got a changelog for those 26 MB of 'system stability and performance' ?
onesolo said:
Can you or someone help me?? Someone??
Click to expand...
Click to collapse
Download the full Google image- not OTA and flash that. If you can still boot the OS, use FF to flash boot, system, vendor. If you cannot boot OS, use ADB Fastboot to flash those partitions. Yes, I used the full image to go from DP2 to Public Release using FF. If more details are needed, check out the FF thread.
v12xke said:
Download the full Google image- not OTA and flash that. If you can still boot the OS, use FF to flash boot, system, vendor. If you cannot boot OS, use ADB Fastboot to flash those partitions. Yes, I used the full image to go from DP2 to Public Release using FF. If more details are needed, check out the FF thread.
Click to expand...
Click to collapse
yep, that is what I'm going to do... I guess not even FF can flash an mere incremental OTA (only full OTAs). bad luck
onesolo said:
yep, that is what I'm going to do... I guess not even FF can flash an mere incremental OTA (only full OTAs). bad luck
Click to expand...
Click to collapse
I didn't think flashing a ota over a rooted os, let alone a highly modified os/kernel/etc was a good idea with any utility.
Now supports among other things back up to pc. I've installed and tested and works.
https://dl.twrp.me/ailsa_ii/twrp-3.1.0-0-ailsa_ii.img
Edit: the original article https://www.xda-developers.com/twrp...-support-for-adb-backup-ab-ota-zips-and-more/
Edit: seems flashing via TWRP image flash is providing better success than via TWRP app. Recommend updating via TWRP flash.
thanks
Do not work.
Get a black screen if i try to Boot in to twrp.
Must go back to 3.0.4.1..
Eller1987 said:
Do not work.
Get a black screen if i try to Boot in to twrp.
Must go back to 3.0.4.1..
Click to expand...
Click to collapse
u sure ur bl is unlocked?
MaxRink said:
u sure ur bl is unlocked?
Click to expand...
Click to collapse
Yes.
I am in LOS 14.1 and twrp 3.0.4.1. works fine.
Flashed 3.1.0.0. whit Flashify.
Worked great for me! I always flash in TWRP, I guess that a I am old school. Thanks for pointing out the new version. I will have to try out the new ADB backup feature later. Although I am not sure if we are still having problems restoring backups like we used to on this phone. I haven't been able to keep up with the forum's lately.
Wrong thread, this needs to be in General
Mod please move.
I flashed the image file in recovery and I still ended up with a black screen.
borijess said:
I flashed the image file in recovery and I still ended up with a black screen.
Click to expand...
Click to collapse
Weird man i got it working flashing it feom twrp it self
borijess said:
I flashed the image file in recovery and I still ended up with a black screen.
Click to expand...
Click to collapse
Maybe you should also write from which TWRP version you come and which Axon 7 model(US/Chinese/European?) you own?
redandr said:
Maybe you should also write from which TWRP version you come and which Axon 7 model(US/Chinese/European?) you own?
Click to expand...
Click to collapse
i have a A2017G and come from twrp 3.0.4.1..
Which partion must i flash for the update to 3.1.0.0.?
I flashed this 3.1 on my chinese b13 with twrp 3.0.4-1 and everything is fine. Flashed it thru twrp btw.
---------- Post added at 11:26 AM ---------- Previous post was at 11:25 AM ----------
Eller1987 said:
i have a A2017G and come from twrp 3.0.4.1..
Which partion must i flash for the update to 3.1.0.0.?
Click to expand...
Click to collapse
Flash it in twrp install and choose img. Flash it for recovery partition.
redandr said:
maybe you should also write from which twrp version you come and which axon 7 model(us/chinese/european?) you own?
Click to expand...
Click to collapse
twrp 3.0.41 axon 7 us version.
Ok I flashed TWRP through fastboot and it worked. I think my first DL was bad. It was half the size of the second one I downloaded.
Success here too. Thank you.
Its all ok with Axon Zte A2017 Chinese.
The last TWRP I conscioulsy installed was 3.0.4.1 but it now shows 3.0.N1-1, what is that? Could it have been updated automatically from the TWRP app?
Also, before I noticed that my boot partition disappeared from TWRP, I can no longer make backups of it or restore the ones I had. Why could that happen? I get something like "unable to locate boot". Thanks
0Kajuna0 said:
The last TWRP I conscioulsy installed was 3.0.4.1 but it now shows 3.0.N1-1, what is that? Could it have been updated automatically from the TWRP app?
Also, before I noticed that my boot partition disappeared from TWRP, I can no longer make backups of it or restore the ones I had. Why could that happen? I get something like "unable to locate boot". Thanks
Click to expand...
Click to collapse
I am guessing you used EDL mode to install TWRP as that is the modified version, as I saw that too. I used TWRP to flash the 3.0.4-1 image and all is normal.
EDIT: TWRP 3.0.4-1 on A2017U Running modified Stock B15 (lots of APKs frozen). Flashing TWRP 3.1 both from TWRP and from "Official App" results with black screen for Recovery. TWRP 3.0.4-1 re-flashed OK from app.
N1-1 is from unjustified devs bootstack.
lafester said:
N1-1 is from unjustified devs bootstack.
Click to expand...
Click to collapse
N1-1 & 3.0.4-1 both work fine, but 3.1 boots to black screen. Why?
Twrp 3.1.0 worked fine on my Axon 7 US version A2017U
Flashed via fastboot over stock recovery.
Will edit this thread and report back if issue is discovered.
I unlocked bootloader (critical aswell) today and installed twrp on my A3. The device is NOT rooted
Weird thing is I can't use my wifi anymore, anytime I try to toggle it on it just jumps back.
Anyone knows what caused this and how I can fix it?
felloguard123 said:
I unlocked bootloader (critical aswell) today and installed twrp on my A3. The device is NOT rooted
Weird thing is I can't use my wifi anymore, anytime I try to toggle it on it just jumps back.
Anyone knows what caused this and how I can fix it?
Click to expand...
Click to collapse
Did you flash any boot.img when installing twrp? Or after you installed twrp?
If you did that is more than likely the problem. Flash original stock boot.img from the same security patch date as your firmware and flash it in twrp and then flash twrp installer afterwards
It seems your boot.img corrupted. If you format data and wipe dalvik cache data and flash stock rom you will succeed i think
---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------
https://c.mi.com/oc/miuidownload/detail?device=1900372
download official xiaomi mi a3 rom here. and flash it via pc and you will have brand new stock rom. Try it if you fail i will help you when i have free time
garylawwd said:
Did you flash any boot.img when installing twrp? Or after you installed twrp?
If you did that is more than likely the problem. Flash original stock boot.img from the same security patch date as your firmware and flash it in twrp and then flash twrp installer afterwards
Click to expand...
Click to collapse
I was stupid and thought I did it without a boot image untill I checked all of my commands again.
I used fastboot flash boot twrp-3.3.1-15-laurel_sprout-mauronofrio.img .
My phone was on V10.3.9.0 EUropean. But that image file is for twrp or is it also a boot.img? Not sure if this caused the problem? I'm very new to all of this so how can I find a stock boot.img of that version and how do I flash it again? I feel kinda lost right now.
Anyone can help me out with this?
felloguard123 said:
Anyone can help me out with this?
Click to expand...
Click to collapse
This phone has the recovery inside the boot partition, this is why you need to flash the boot partition, you do not need to flash it again normally, you just flash it to the other slot, boot twrp, go back on the original slot, flash twrp using the .zip file, idk where you should get the boot.img file, but lok online for it, maybe you will find it.
EDIT: https://github.com/AndroidDumps/xia...KQ1.190416.001-V10.3.9.0.PFQMIXM-release-keys
antoine62 said:
This phone has the recovery inside the boot partition, this is why you need to flash the boot partition, you do not need to flash it again normally, you just flash it to the other slot, boot twrp, go back on the original slot, flash twrp using the .zip file, idk where you should get the boot.img file, but lok online for it, maybe you will find it.
EDIT: https://github.com/AndroidDumps/xia...KQ1.190416.001-V10.3.9.0.PFQMIXM-release-keys
Click to expand...
Click to collapse
But what was the my fault here? What did I wrong? Was it the .img file of the twrp or did I install it wrongly? I am very new to this and don't understand why there are 2 slots etc. Sorry for the confusion.
felloguard123 said:
But what was the my fault here? What did I wrong? Was it the .img file of the twrp or did I install it wrongly? I am very new to this and don't understand why there are 2 slots etc. Sorry for the confusion.
Click to expand...
Click to collapse
You installed it uncorrectly, you need to switch slot (because this device have an A/B partition type), flash twrp, boot it, switch to the og slot, flash twrp using the .zip file (so it modify your current boot.img), and done.
This phone will be my first A/B phone, i cant wait to receive it.
But what you didnt is still correct, just not perfect.
antoine62 said:
You installed it uncorrectly, you need to switch slot (because this device have an A/B partition type), flash twrp, boot it, switch to the og slot, flash twrp using the .zip file (so it modify your current boot.img), and done.
This phone will be my first A/B phone, i cant wait to receive it.
But what you didnt is still correct, just not perfect.
Click to expand...
Click to collapse
So twrp has to be installed on both partitions?
I'm not sure if really twrp installed on only one partition could cause Wifi problems.
I would assume that my .img for twrp was faulty.
a
garylawwd said:
Did you flash any boot.img when installing twrp? Or after you installed twrp?
If you did that is more than likely the problem. Flash original stock boot.img from the same security patch date as your firmware and flash it in twrp and then flash twrp installer afterwards
Click to expand...
Click to collapse
and how to do that:{?
i have same problem as yours and searched too many videos on youtube but then i have decided to remove the twrp from the device and no one yet has told me that how to flash twrp in another partition rather i dont know what is the another partition