Related
Hi A7 users,
Let's start this off be saying, bare with me English is not my primary language.....
OK now, the reason for this Thread is to find a definite solution for current users and future users who have run into boot issues cuz they were trying to :
A- Go back to Un-rooted and lock bootloader state.
B- Started Playing with root tools and make a huge mistake
C- Started playing with twrp not knowing what they were doing
D- All the above + started flashing images files and got worts.
E- Any other type of situation.
I Know we make mistakes and we learn from them and well here today we are going to try or rather say Find a permanent /define solution to all this issues with your help, so PLEASE ONLY POST IF YOU HAVE RUN INTO ANY OF THIS ISSUES AND HOW YOU GOT INTO THE ENCHILADA ( MESS ) .
If you have the solution to your previous boot problems send me a PM and I'll keep this Thread updated for everyone to see with your solution and of course credit to the user/s.
NOTE : Please mention which Axon 7 you are using e.g. :
- A2017 (Chinese Variant)
- A2017U (USA Variant)
-A2017G (UK/Europe/International Variant)
reserve 1
reserve 2
reserve 3
reserve solution 4
reserve solution 5
Anyone this issues please post you issue, how to got into the problem, device model and if you got it fix let us know.
https://www.youtube.com/shared?ci=05LD4Ja-h3k
You'd think with all the other posts about problems there'd be something here by now.
Always thank those who are helpful...and just ignore those who aren't.
Mine happened when I wiped Internal storage from twrp. This caused the phone to only see 4gb of internal storage. Came to xda and it was suggested to flash back original boot.img. once that was done 4gb issue was fixed and the radio was gone.
I did indeed try every solution offered (thanks again for all the effort, DrakenFX and others). But, I've come to the conclusion that this is not going to get fixed until XTE releases US images. For other people's sake I hope I am wrong, but I myself decided to proceed with the exchange where I bought it, as I was right at the end of my 14 days (newegg doesn't seem to give the 30 days that xte does). I may be out of an Axon 7 for a while, so for now I am on my amazon ads, Blu R1 HD (with ads defeated
Is there a guide to go back to stock for the A2017G?
i'm on B02 with root and the bootloader still locked.
Like to go back to stock now that ZTE is working on an update to give the A2017G an unlocked bootloader.
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
aPexalpha said:
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
Click to expand...
Click to collapse
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
I am was rooting my axon a2017 on b10 chinnese version without any backup after rooting got password screen after boot then i was do factory reset and format data and all looking good but after that i saw that i dont have google play app so i installed macro gapps 6.0 after flashing phone stuck on axon screen (after zte logo) for long time i been wait up to 30 minutes and nothing was done..also i have the message on twrp about the modification(dont understand why i have this message all the time) i saw in xda forum that need to install supersu so i search on internet and was flash super su 2.65 and then when i am was boot device go to zte logo screen and then turning off when i connect the device as mtp device named as a2017u (whats worng with it??? I was flashed b10 root boot.img)
I regret about this root and want to back all to stock without any problems need help from someone
I need stock b10 boot.img if someone can upload
Many thanks!
---------- Post added at 04:23 AM ---------- Previous post was at 04:11 AM ----------
DrakenFX said:
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
Click to expand...
Click to collapse
Its will help me too i think
Dear All,
ZTE Axon 7 A2017 (Chinese version) Stuck on Bootloader mode.
Device after power on will Stuck on ZTE logo even power button press longer also will Off and came back to square one and the only way to power off is via selection on bootloader page via volume button which consists of Recovery mode, Power Off, Bootloader and some other mode which I can't recall.
History of this issue. Please bear with long story.
Manage to install MM ROM with B13 via sd card installation via update software in phone setting. follow by Unlocked bootloader and Install TWRP 3.1.1.0 then try few different ROM until one day when I use Xiaomi flashtool my PC crash half way through during flashing resulting in device with Pure Chinese ROM and TWRP also got corrupted, when I said corrupted because I install TWRP 3.1.1.0 but when I go to Recovery mode it shows TWRP 3.0 something. with this corrupted TWRP when I try to install ROM it will show loading but end result is NIL meaning same ROM nothing change.
Until this stage I never did a TWRP backup because all this while the ROM is Not my type of ROM from this junction when I boot back to TWRP and I did Advance Wipe most of it except external sd card thinking that I may be able to install fresh TWRP but my Recovery TWRP is residing in phone storage resulting in No more TWRP recovery software. next thing I did was I connect phone to PC and ran adb fastboot tool to detect device and managed to detect device in recovery mode and I make decision to Locked back the bootloader and did just that and Locked bootloader is Succes and it also Erased everything during the process.
To cut short the story after Locked back bootloader only Bootloader mode is accessible and when I connect to PC and enable Recovery mode (Black screen) and EDL mode (Black screen) from Windows PC Device Manager COM port able to see Qualcomm 9008 for this 2 mode.
I must admit after few days of trying to resolve this Stuck Bootloader issue I almost give up.
Then I remember this Woodo magic by jcadduno which recommends XM flashtool version 2016.08.30.0 but unable to flash after trying few version Xiaomi flashtool and the very latest and I mean from Xiaomi Flashtool webpage http://xiaomiflashtool.com/
version 20170425 that break the ice and finally able to load A2017U ROM because this US ROM my phone No Network detected.
From here onwards I unlocked bootloader and install back TWRP (Installation of TWRP via Axon7toolkit) because of Network issue since I got TWRP I install back A2017 ROM but still Not satisfied because Chinese ROM certain Apps having issue because of Google services and I chance upon this Conversion A2017 to A2017U ROM (Hybrid ROM caused ROM is US and Modem from Chinese Modem)
that I'm stay put right now and my phone now is A2017U model.
I hope this experience can help others with similar Stuck bootloader and those who wish to convert A2017 to A2017U ROM.
below is the link that I described Woodo magic.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Straight forward Axon7toolkit, please don't use Chrome browser cause Chrome will Automatically Delete it after complete download for my case I used Microsoft Edge.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
below is the link to Hybrid ROM for A2017U
https://androidfilehost.com/?fid=457095661767154458 by Michael Warner After flash install No verity patch for the bootloader.
Cheers.
I am stuck in a position where I can restore my nandroid backups but get Error 7
when trying to reinstall any Rom on a2017u I was able to fix the unlocked bootloop
by the EDL method. The Rom's are the same as the backups. I think I tried to role back to B29 Causing the bootloop) and have had problems ever since.
Should I try flashing A2017Uv1.1.0B32_Bootstack_by_DrakenFX since the Rooms are all B32?
The B15 and B19 Nandroid's still Restore fine.
Hello all,
i don't get onto forums very often but i thought this was a nice one to add to. i've rooted a few motorolas, a few ztes, a cat; i've also bricked those ztes, cat & a few samsungs. i'm dealing with two Axon7U's; one is factory MM-b29, the other is N-b35.
while screwing around with TWRP, i bricked the b35 (the b29 has been bricked for a month at this time) after i had it almost perfected. by perfected i mean a custom recovery & root user access fully acquired. with DrakenFX's {YOURS; thanks so much. i'm learning to get along with linux} extensive files created to save people from themselves i was able to unbrick the b35. albeit its CELLULAR DATA became unhinged; that's something i could've lived with except it was a loaner and had NO CAMERA! it's camera (along with the ability to push both volume buttons at once for say EDL mode...) was damaged having been beaten across a steering wheel several times. so with my newfound unbricking superpowers i decided to take another crack at the b29. managed to get it unbricked but couldn't get it setup with both TWRP & SuperSU without losing one, the other or, both. at times it didn't even boot up. i was doing pretty much everything cited above for reasons 'why'. best way to learn is by trial & error (if one can afford it).
the b29 is rooted right at this moment; i'm working on it as soon as i leave this posting. i used Axon7_EDL_Tool. i used Axon7root. i used MiFlash. i used Fastboot. I used ADB App Controller software too. back & forth i fought for three days mostly due to downloading glitches and i prevailed. i manipulated a stock OTA full system update.zip by happenstance and it Auto_Updated over itself. in other words it already had the same ROM installed. i don't know what it tested to realize it needed to update to what it already had. it didn't have CELLULAR DATA either. just like the b35, it broke somehow while flashing TWRP or SuperSU. funny thing is it still wanted to update that same ROM after it did. while perusing the system update setting(s) i noticed it had downloaded N-b15 and it wanted to update b29 AGAIN! i opted for the Nougat update. it did alright and appears to have fixed it's CELLULAR DATA too. i haven't looked at it since but i'm confident i can gain root user access with a minimal amount of effort.
The main problem i've had with dealing with bricked devices is the age of the file downloads. most of them are simply GONE!, expired links and whatnot. if i'd had a clear path say from a custom recovery and rooted boot image of my factory version or the path that leads to it, i'd have been fixed up long ago. i've found partial 'paths' if you will that almost get me there but no quite all the way. flashing images & zips through fastboot are different from their counterparts entered through TWRP or Emergency Download Mode which of course are both different too. three different ways to get into one's phone makes it almost impossible to keep them perfected.
i'm not sure i did what i'm supposed to regarding this thread. Thank you DrakenFX for your time & knowledge; you've saved my old Axon7!
Hello all update;
b35 Nougat phone is retired. b29 managed to update itself to b35 7.1.1. however, its CELLULAR DATA is still broken. i haven't managed to figure out how or where it's broken so i cannot fix it.
what i'm trying to do now is flash Magisk instead of SuperSU and using a TWRP version 3.0.3-1. heck i've used all of TWRP's versions in my efforts to reacquire CELLULAR DATA.
crazy part is the phone knows its CELLULAR DATA carrier and freely displays all of its hookup info. this is very frustrating.
So I followed a tutorial online to install Android Nougat 7.0 on my Huawei P9 lite. Once I was in TWRP I realised I was supposed to install two update files from two different .zip files. Trouble is I only had the one update on my phone at the time. I didn't want to exit TWRP at that stage because I already installed one of the update files.
When I booted my phone after the update, it all seemed to be working with 7.0 installed. Then I noticed my internet data wasn't working outside of wifi, and my bluetooth isn't turning on. The rest seems to be running fine other than those two things.
I rely a lot on bluetooth and internet on the go. I need it back, does anyone know what I could do, outside of factory reset?
Thanks
factory reset wouldn't help, you need to reflash update.zip and data_full.zip AT SAME TIME without rebooting
Coolyou said:
factory reset wouldn't help, you need to reflash update.zip and data_full.zip AT SAME TIME without rebooting
Click to expand...
Click to collapse
Okay, I realised that just now. Trouble is I am having trouble booting into TWRP now. I just get "your device has been unlocked and can't be trusted." with an orange web link.
For some reason my phone says in the settings that I'm still on android 4.3 although the ui and functionality is 7.0. Also, the EMUI is 2.0. I don't know how I got TWRP working before but I think there's a conflict due to it half being 7.0 so recover won't boot. I have tried loads of tutorials online but none of the rocovery.img or twrp.img files are working.
have the exact same problem, on android 4.3 and stuck.
from what i understand to dload a working stock rom, you need to have the correct oem info that matches the recovery stock rom. i cant flash any OEMinfo as i cant get root from revolution recovery.
no access to Data partition either.
no other recovery's to install as its the only one for nougat.
So i need help for this issue too.
jackvdbuk said:
have the exact same problem, on android 4.3 and stuck.
from what i understand to dload a working stock rom, you need to have the correct oem info that matches the recovery stock rom. i cant flash any OEMinfo as i cant get root from revolution recovery.
no access to Data partition either.
no other recovery's to install as its the only one for nougat.
So i need help for this issue too.
Click to expand...
Click to collapse
I fixed it! It was more simple than I realised. I used the dload folder method; Placing the update.app into a folder called 'dload' on an sdcard. Then holding power, both volume buttons to initiate the update.
Thanks for your help guys!!
Hey people,
I've updated to the unofficial Nougat leak here and ever since I can't get into the recovery. The ROM is OK but no matter what I do I can't get into the recovery. After "adb reboot recovery" I just get stuck in a boot loop and I must get into the upgrade utility and restart phone into the system from there. I've tried to flash few other recovery but nothing works. So far I'm fine with the system and I'd like to also try LineageOS but I have no way to flash the ROM. I have tried "Fastboot flash zip xx.zip" from the bootloader to flash LineageOS but it told me I don't have permissions so it was no good.
So do you folks here have any idea what I did wrong and how to make the recovery work again? I'm kind of learn from the tutorial guy so I'll post the sources I've been using to do the flash.
Unlocking bootloader and flashing new recovery
I've only used the unlock bootloader and flash twrp sections with their provided recovery. I've also tried to flash THIS recovery by Meticulus after the nougat update.
Flashing the ROM + used ROM
Used the old process because upgrade with system utility kept giving me errors.
Model number - VNS-L21
Also if this issue can't be (yet) fixed do you know any way to safely flash ROMs without recovery?
Thanks for any kind of help
You cannot flash any ROM in the nougat recovery, because it does not support /data mounting. Downgrade to MM and install the ROM you want from there.
@SALVO9
Ok, thank you for the reply. I'll probably try to downgrade and flash it afterwards to know which ROM suits me better. All I need to do is find the stock ROM copy it to the phone and restart with all buttons pushed right? Also, do you have any info about when there will be a nougat recovery that can mount /data?
TheAstaros said:
@SALVO9
All I need to do is find the stock ROM copy it to the phone and restart with all buttons pushed right?
Click to expand...
Click to collapse
No.
Flash proper OEMinfo first!
@Schlengge
Thanks for the advice. I did my research because I didn't know a thing about oeminfo and I have hit a wall since my phone is not rooted(Should have mentioned that earlier I know) and I'm supposed to replace custom.bin and then flash the img. So afterwards I searched how to root this nougat ROM and found nothing no app was working and everything I found was just using the phone's recovery which I can't access. Does anything come to mind? I will continue getting through the pages of google but I don't think I'll find anything useful.
EDIT> After some searching I found the official rollback package. I have yet to test it (downloading on slow connection atm) and I hope it will work.
Ok it's finally done and I'm back at old stock ROM(EMUI 4.1.1 VNS-L21C432B160) after hours of searching I gave up on the oeminfo or rooting the phone. I searched for the stock firmware and found some rollback packages on the Huawei site. I will post the links in there you even have instructions packed with the zip.
LINK1
LINK2
Download both start with the smaller one because it's flashing first and follow the instructions in the pdf. Worked for me so hope it also helps you.
Also as I found out just now this rollback also locks back your bootloader so be sure to unlock it back again with the code.
Plzzz help im stuck I want to rollback my huawei p9 lite VNS-L31 where its build number is NRD90M(test keys) to marshmallow 6.0 help don't know what to do . Plz if you can explain step by step what can i do because i'm not good in these things , My bluetooth not workng , there no calculator , no software updater , i am not able to check if got update or not and so on......, im stuck plz help
Well hey.. first download this rollback package from this link:
http://download-c1.huawei.com/download/downloadCenter?downloadId=93645&version=371484&siteCode=np
Extract and move all the files to dload folder on your external SD Card then install it with the 3 button method. If there's no dload folder then create one.
So the phone will reboot and now you can downgrade to any mm rom
Now just download this mm rom from this link:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v66015/f1/full/update.zip
And again extract and move the files to dload folder on your sd card.. Install with 3 button method.
Done! Everything should work now!
In case If you don't know what the 3 button method is..lol
•Power the phone off ?
•Just press and hold on POWER + VOLUME UP + VOLUME DOWN buttons
The phone will start installing the rom and that's the 3 button method ?❤
this is not working for me. it says incompatibility with current version and to download the correct version.
lennie27 said:
this is not working for me. it says incompatibility with current version and to download the correct version.
Click to expand...
Click to collapse
Man, you have to do entire procedure: unlock bootloader, install twrp for Nougat and flash oeminfo for your phone. Before that you have to put in dload folder MM firmware (B130/B131),
because after flashing oeminfo phone try to repair firmware from dload folder. If repair do not start, power off phone and power on with 3 keys combination.
Hi All,
I'm having a similar issue as lennie27 however I think I might have strayed down an incorrect path during the process of upgrading to Nougat. My device shipped with VNS-L31C16B120 with no updates available through the stock updater. I tried the Firmware Finder guides which listed options for VNS-L31C169B13x and VNS-L31C432B13x however none of these updates would work, updater would say it's incompatible with current version. I also tried manually downloading the VNS-L31C432B160 firmware and installing that with the 3 button method as well as the EngineerMenu option with the same result (found guides that stated needing to be on B160 or B161 before making the jump to Nougat). Eventually I decided to unlock the bootloader and install Nougat through TWRP and followed the obeygeekupdate-huawei-p9-lite-to-android-7-0-nougat-manually guide (can't post links ) on manually installing Nougat (stupidly never paying attention to the fact that it's a beta build guide). I've installed TWRP to the device again using the P9 Lite Toolkit v0.0.0.11 found here on XDA (used this when on MM however the upgrade seemed to restore the stock recovery) with the idea of downloading the build from the ministryofsolutions huawei-p9-lite-vns-l31-nougat-b371-update-stable-europe page and pushing that to the device instead (however now the device doesn't want to boot into recovery)
Now my only concern is, will this work? I've noticed a bit of commenting going back and forth on the ministryofsolutions site which essentially boiled down to the need for debranding the phone (apparently C19 is MTN South Africa specific and I need to debrand it and get it onto C432 Europe before mucking about with Nougat, but alas to late) which seemed to be something I should have done while on MM still. If I can find a full firmware link for VNS-L31C16B120 can I flash that through TWRP without needing to follow any prerequisite steps? So far nothing that I've tried to flash using the three button method has worked, I'd just like to get back onto an official stable firmware again.
Any advice will be appreciated
saintnite said:
Hi All,
I'm having a similar issue as lennie27 however I think I might have strayed down an incorrect path during the process of upgrading to Nougat. My device shipped with VNS-L31C16B120 with no updates available through the stock updater. I tried the Firmware Finder guides which listed options for VNS-L31C169B13x and VNS-L31C432B13x however none of these updates would work, updater would say it's incompatible with current version. I also tried manually downloading the VNS-L31C432B160 firmware and installing that with the 3 button method as well as the EngineerMenu option with the same result (found guides that stated needing to be on B160 or B161 before making the jump to Nougat). Eventually I decided to unlock the bootloader and install Nougat through TWRP and followed the obeygeekupdate-huawei-p9-lite-to-android-7-0-nougat-manually guide (can't post links ) on manually installing Nougat (stupidly never paying attention to the fact that it's a beta build guide). I've installed TWRP to the device again using the P9 Lite Toolkit v0.0.0.11 found here on XDA (used this when on MM however the upgrade seemed to restore the stock recovery) with the idea of downloading the build from the ministryofsolutions huawei-p9-lite-vns-l31-nougat-b371-update-stable-europe page and pushing that to the device instead (however now the device doesn't want to boot into recovery)
Now my only concern is, will this work? I've noticed a bit of commenting going back and forth on the ministryofsolutions site which essentially boiled down to the need for debranding the phone (apparently C19 is MTN South Africa specific and I need to debrand it and get it onto C432 Europe before mucking about with Nougat, but alas to late) which seemed to be something I should have done while on MM still. If I can find a full firmware link for VNS-L31C16B120 can I flash that through TWRP without needing to follow any prerequisite steps? So far nothing that I've tried to flash using the three button method has worked, I'd just like to get back onto an official stable firmware again.
Any advice will be appreciated
Click to expand...
Click to collapse
you need to install nougat recovery, not the one from the toolkit. then twrp will work and the device will boot.
to go back to 120 you need to install oeminfo, and then the update.app
mjz2cool said:
you need to install nougat recovery, not the one from the toolkit. then twrp will work and the device will boot.
to go back to 120 you need to install oeminfo, and then the update.app
Click to expand...
Click to collapse
Thank you for the reply, managed to come right a few hours after posting. Turned out the copy of TWRP that I had on hand was more outdated than I thought, downloaded the newest copy and that worked on the device. Additionally I managed to find a website listing just about every firmware for the phone (Including my original MTN ZA specific variant) so I downloaded that and managed to restore the phone using the three button method. Phone is back to stock now and even the unlocked bootloader nag screen is gone so I'm guessing the bootloader is locked again as well One day when I'm brave enough to attempt this again I'll look at debranding the phone and getting it onto a C432 based ROM before getting it onto Nougat again.
phone bricked
hello guys! im currently on lineage os 14.1 by meticulus, i wanna revert back to stock mm but i cant. i flashed the custom rom from mm using twrp recovery by meticulus, but now i cant even boot into erecovery! can you pls help me!:crying: DLOAD method doesnt work!
Hello fellows. I am in a deep sh&*. Maybe someone can help.
I have a p10+ L09 converted to L29, rooted, bootloader unlocked. It was on rooted stock rom. Yesterday, tried to make the update, and something went wrong. Now, I can't install any rom exept future rom or something found here. I've tried rayglobe knife, Huawei multi tool, eRecovery, dload, and no way to install an official rom. I am barely able to install twrp, format data, and install future rom before rebooting.
Tried to extract boot, cust, system from the original rom, but it says finished and bootloop just after the unlocked message. On latest versions, I cant even find them in the update.app..
Any help, any downloadable file or link is really appreciated. Please help...
dj_varizes said:
Hello fellows. I am in a deep sh&*. Maybe someone can help.
I have a p10+ L09 converted to L29, rooted, bootloader unlocked. It was on rooted stock rom. Yesterday, tried to make the update, and something went wrong. Now, I can't install any rom exept future rom or something found here. I've tried rayglobe knife, Huawei multi tool, eRecovery, dload, and no way to install an official rom. I am barely able to install twrp, format data, and install future rom before rebooting.
Tried to extract boot, cust, system from the original rom, but it says finished and bootloop just after the unlocked message. On latest versions, I cant even find them in the update.app..
Any help, any downloadable file or link is really appreciated. Please help...
Click to expand...
Click to collapse
What error/behaviour are you getting from erecovery?
Plop
Hello mate. Thanks for your time.
ERecovery crash everytime at 5%. If I try to download via erecovery, it doesn't download.
I've tried to extract the files from update. App, and inject them via fastboot. It goes to the end of the operation, but once rebooted, it bootloop before the Huawei logo..
I don't understand what happens.. It's like if the phone don't want the original firmware anymore..
If you have any files to propose me, I really want to try tonight...
Can you somehow recover your original oeminfo with TWRP and retry erecovery? That's how I got out of a similar situation, although I can't say for sure whether I really had the same root cause.
Hmm not sure that the oem info is ok or corrupted...
That's what I am affraid of..
I will try in a moment to see..
If it's corrupted, that means the phone is dead?
In that case you could try funkyhuawei, they provide their own oeminfo and erecovery connection. They do cost money though.
May I ask what makes you want to go away from the fromfuture ROM?
This... Android 5.1, emui 3.1
I don't know if iam becoming stupid with age, but can't find any more recent... And with the kids yelling on my back.... Lol
Well, I found a recent rom from future. Had some troubles with Android locking magisk, but now it's working ( update magisk before putting your Gmail account and restore). For now it's working fine. Just had a few freezes here and there but since this morning it's going fine. I think I'll stay with it for now.
Thanks for the people who tried to help me.
XDa rules!