My phone is caught in a bootloop. - Huawei P9 Lite Questions & Answers

Please help me..
My phone is caught in a bootloop.
I flashed my device with wrong rom, then I tried a roll back, but I flashed the wrong rollback file(see the pattern? Yes, I am indeed an idiot of epic proportions..)
I don't have access to fastboot or bootloader (I used Firmware Finder for the update.)
I tried Huawei eRecovery; it doesn't work
I tried Hisuite; it doesn't work.
my device model is VNS-L31C16B120.
I have the stock rom for the device.
Can anyone help me?
maybe someone can find a roll back package that will work with my device?

Are you that this is your device? Because a wrong ROM means also that it thinks you have a different device.
We might still try.
What was your Android and Emui Version?
3Gb or 2Gb ram?

ImBadAtThis said:
Are you that this is your device? Because a wrong ROM means also that it thinks you have a different device.
We might still try.
What was your Android and Emui Version?
3Gb or 2Gb ram?
Click to expand...
Click to collapse
It's a single with 3GB of ram.
Originally it was android 6.0 MM. I think it was Emui 4.1

AADeaney said:
It's a single with 3GB of ram.
Originally it was android 6.0 MM. I think it was Emui 4.1
Click to expand...
Click to collapse
Forgot to ask, which region?

if you can access to "update mode" (three-buttons boot), you may be able to use "adb reboot bootloader" to switch into fastboot. im faced with similiar problem, i flashed oeminfo from p9 to p9lite. it brings phone to "coma" and only what helps was DC-phoenix (15 credits). but till i didnt delete oeminfo, phone was still recognized as P9. now im solving missing imei2 and maybe wrong model/custom info and somehow blocked bootloader... so who is "idiot of epic proportions"?

ImBadAtThis said:
Forgot to ask, which region?
Click to expand...
Click to collapse
South Africa.

Alright, the flashing is probably easy, but the hard part is finding the right firmware for you. I know that your right firmware should have a B131/B141/B151 or a B161 at the end, because you have a 3GB Ram device and you were on Android 6. I'm not sure about the C though, and this part can **** your device up, like you have. As much as I understand, C is your Kernel number (look it up using Terminal Emulator and "uname -r"). I don't know how to determine the right version for you using the kernel version. I also found out that you will have only minor problems if you have the wrong region (better than bootloop).
Try flashing version VNS-L31C432B161. This is the version I'm currently on. I have also Android 6, Emui 4.1 and 3GB of RAM. I'm experiencing some battery issues, but it's still better than a bootloop. I'm trying to upload the file to drive but it's buggy, I'm going to send you the link shortly. You will have to flash the rom using adb and fastboot, but the problem is, the link is gonna be an update.app, adb can only flash img. Follow this guide to extract all the parts of the update.app:
https://forum.xda-developers.com/showthread.php?t=2315547
You will now have 3 or 4 .img files.
Follow this guide to flash them correctly:
http://www.daviddosa.nhely.hu/en/2016/04/05/flashing-via-fastboot/
You might not have the cust.img files, that doesn't matter. You can also try the same with other update.App (run an Android emulator like Bluestacks and download Huawei Firmware Finder)
I'm sure you're gonna find the right version if you search good.
I'm going to upload the file now.

Here's the link, I hope it will help.
https://drive.google.com/open?id=0B5tgej_hUMkoblprVFZRMWRXS00

Related

So, the YotaPhone 2 is officially dead?

Hey guys,
I have the YotaPhone 2 and it's stuck on lollipop 5.0 for ages.
It feels like they ditched this phone completely.
What do you think guys?
Someone has some different info?
I hope not, some marshmallow would be nice and i am about do start an cyanogenmod port (if if find the time...)
fies76 said:
I hope not, some marshmallow would be nice and i am about do start an cyanogenmod port (if if find the time...)
Click to expand...
Click to collapse
good news!
TopTomy said:
Hey guys,
I have the YotaPhone 2 and it's stuck on lollipop 5.0 for ages.
It feels like they ditched this phone completely.
What do you think guys?
Someone has some different info?
Click to expand...
Click to collapse
I've spoken to them a couple of times, both their Facebook page and their customer service indicated their won't be a move up to Marshmallow, very doubtful over a move to 5.1 even. Any more updates will be focussed with optimising the existing software, adding slight features for the EPD etc.
Sad but they are a small company, seems they can only focus on 1 model and a time.
zute333 said:
I've spoken to them a couple of times, both their Facebook page and their customer service indicated their won't be a move up to Marshmallow, very doubtful over a move to 5.1 even. Any more updates will be focussed with optimising the existing software, adding slight features for the EPD etc.
Sad but they are a small company, seems they can only focus on 1 model and a time.
Click to expand...
Click to collapse
Thanks for sharing!
New Update .
Still Lollipop 5.0, but brings some useful improvements and enhancements. I'll take it.
I hope, with the release of the Yota 3 and 2c, that the price of the YD201 falls down. They can't update neither Yota 1 and 2. I still got the first one, but just because I live in Brazil and got from a nice guy that agreed to sell and send his Yotaphone 1 to me from India.
Anyone inclined to sell your Yota2 please talk to me.
zute333 said:
New Update .
Still Lollipop 5.0, but brings some useful improvements and enhancements. I'll take it.
Click to expand...
Click to collapse
Woot??
You got a new firmware OTA?
mine shows nothing!
TopTomy said:
Woot??
You got a new firmware OTA?
mine shows nothing!
Click to expand...
Click to collapse
It's for the RU (russian) firmware, if you check the other threads there are methods to flash the previous version. I have been using it for a few iterations now, the new one worked as an OTA, even with TWRP (they added something to reflash the stock recovery, Yota noticing the significant root community using this phone in Russia at least).
zute333 said:
It's for the RU (russian) firmware, if you check the other threads there are methods to flash the previous version. I have been using it for a few iterations now, the new one worked as an OTA, even with TWRP (they added something to reflash the stock recovery, Yota noticing the significant root community using this phone in Russia at least).
Click to expand...
Click to collapse
Thanks for the info!
I only believe it when it is real, but according to info from tech support, also the EU firmware will get an update this month...
BTW, lollipop isn't too bad, I switched back from marshmallow on my nexus 7 - too much battery drain. if Google could get it right the first time, you wouldn't need monthly bug fixes. not saying that an update for the yota isn't overdue...
Is just me that can't update? I have no OTA and flashing manually gives me "no MD5 file found" error
TKPL said:
Is just me that can't update? I have no OTA and flashing manually gives me "no MD5 file found" error
Click to expand...
Click to collapse
More info please .
firmware version? software version?
can you skip the md5 checksum?
you're rooted, so can you download the russian (RU) firmware and flash that?
zute333 said:
More info please .
firmware version? software version?
can you skip the md5 checksum?
you're rooted, so can you download the russian (RU) firmware and flash that?
Click to expand...
Click to collapse
Yes, thanks
Sorry what you mean with firmware and software version? Phone was running Kitkat 4.4.2 or 3 (now is bricked).
I cannot skip the checksum, no such option in my TWRP (2.8.5). There are others option about checksum on backup but no skipping during install.
I am rooted (and bootloader is unlocked) but I cannot install the RU version. Here I don't understand why you ask me if I am rooted: I can install from recovery or TWRP without root
I downloaded all RU versions and the last EU version from the ftp and I got the MD5 error with all, both Lollipop and KitKat.
Then I tried with Yota Flasher utility: I saw that for flash ROM it was seeking for "firmware" path, so I created "firmware" path and put there the ROM.
I started to flash and it took only some seconds... I understood immediately phone has gone bricked.. and so it is...
Then I tried to download the firmware through Yota Flasher: it arrived to 100% and got stuck in there...
I'm trying to redownload it and hope to flash the system, phone is here in downloading mode waiting...
Provide you my flash method, manually. Use the fastboot.exe in cmd, and type command line below
****************************************************************************
fastboot.exe flash aboot firmeare/emmc_appsboot.mbn
fastboot.exe flash boot firmware/boot.img
fastboot.exe flash -S 512M system firmware/system.img
fastboot.exe flash recovery firmware/recovery.img
fastboot.exe flash cache firmware/cache.img
fastboot.exe flash modem firmware/radio/NON-HLOS.bin (flash the radio)
fastboot.exe flash sbl1 firmeare/radio/sbl1.mbn
fastboot.exe flash rpm firmware/radio/rpm.mbn
fastboot.exe flash aboot firmware/emmc_appsboot.mbn (flash again, just do it.)
fastboot.exe flash userdata firmware/userdata.img (notice this is for the user data, including app data and SD)
fastboot.exe reboot (reboot and wait, about 20 min stuck on logo, it's ok.)
Thank you xingshi.
I'll try.
How long does the entire process take?
TKPL said:
Yes, thanks
Sorry what you mean with firmware and software version? Phone was running Kitkat 4.4.2 or 3 (now is bricked).
I cannot skip the checksum, no such option in my TWRP (2.8.5). There are others option about checksum on backup but no skipping during install.
I am rooted (and bootloader is unlocked) but I cannot install the RU version. Here I don't understand why you ask me if I am rooted: I can install from recovery or TWRP without root
I downloaded all RU versions and the last EU version from the ftp and I got the MD5 error with all, both Lollipop and KitKat.
Then I tried with Yota Flasher utility: I saw that for flash ROM it was seeking for "firmware" path, so I created "firmware" path and put there the ROM.
I started to flash and it took only some seconds... I understood immediately phone has gone bricked.. and so it is...
Then I tried to download the firmware through Yota Flasher: it arrived to 100% and got stuck in there...
I'm trying to redownload it and hope to flash the system, phone is here in downloading mode waiting...
Click to expand...
Click to collapse
UPDATE
Via Yota Flasher I download succesfully the 4.4.3 and flashed the phone. Now it's back
I tried to download again the 5.0 EU but no way: arrives at 100% and stops. If I check file's dimension I see it is a couple of kbytes below the size of the other package I downloaded from web browser and in fact it's impossibile to open the zip.
I'll try to download other version of Lollipop through the Yota Flasher.
TKPL said:
UPDATE
Via Yota Flasher I download succesfully the 4.4.3 and flashed the phone. Now it's back
I tried to download again the 5.0 EU but no way: arrives at 100% and stops. If I check file's dimension I see it is a couple of kbytes below the size of the other package I downloaded from web browser and in fact it's impossibile to open the zip.
I'll try to download other version of Lollipop through the Yota Flasher.
Click to expand...
Click to collapse
NEW UPDATE
I have 5.0!
After flashing and old version of 4.4.3 (my phone went with a 4.4.something branded Vodafone Italy, and they evidently don't give a fork about updates). With the 4.4.3 rev 1.0.51a I immediately received he update to 1.0.56a: I downloaded the 114MB, rebooted, and then got the update to 1.0.61a, around 63MB. I rebooted and then got finally the update to 5.0, 1GB
I have only one problem now: the device doesn't recognize when I'm looking at the ink screen, and power button powers on the amoled... Even unlocking through swiping from bottom to top doesn't work. Option is correctly set, I tried to uncheck, reboot, wipe cache and check the option again but it not working well yet. I open a thread for this...
TKPL said:
NEW UPDATE
I have 5.0!
After flashing and old version of 4.4.3 (my phone went with a 4.4.something branded Vodafone Italy, and they evidently don't give a fork about updates). With the 4.4.3 rev 1.0.51a I immediately received he update to 1.0.56a: I downloaded the 114MB, rebooted, and then got the update to 1.0.61a, around 63MB. I rebooted and then got finally the update to 5.0, 1GB
I have only one problem now: the device doesn't recognize when I'm looking at the ink screen, and power button powers on the amoled... Even unlocking through swiping from bottom to top doesn't work. Option is correctly set, I tried to uncheck, reboot, wipe cache and check the option again but it not working well yet. I open a thread for this...
Click to expand...
Click to collapse
Same here , have just bought the YOTA 2 too, Vod branded. I wanted to upgrade to to EU 1.60 (rom which seems to be pretty stable): Can I ask you if you have the 1.60 actually or the 1.9x (Russian one)?.
The bug you describe seems to be a real pain, do not want to risk.
Will appreciate any help.
Thx mate
lexman941 said:
Same here , have just bought the YOTA 2 too, Vod branded. I wanted to upgrade to to EU 1.60 (rom which seems to be pretty stable): Can I ask you if you have the 1.60 actually or the 1.9x (Russian one)?.
The bug you describe seems to be a real pain, do not want to risk.
Will appreciate any help.
Thx mate
Click to expand...
Click to collapse
I have the 1.60 EU.
You can make a NAND backup and then flash the newest firmware, trying maybe the 1.99 RU. Even if you flash the 1.60 EU, is not sure that you'll have my same problem, there's people who flashed without issues...

No keyboard.

I had problem with my wifi and bluetooth, i couldn't turn it on. It was after I dropped my phone into water, not whole phone just a bit. I teared it down and let it dry overnight. Didint help. I thought that i can downgrade back to stock android 6.0 and then go back to 7.0, something like reinstall(don't ask). I did it with official package from huawei and now i cant turn on phone because i have only Google text to speak, without keyboard. ADB is not working and i don't know my phone's serial number just only VNS-L21, I don't know how to call it correctly. OTG keyboard doesn't work too. I'm looking for stock ROM and instruction how to flash it.
You installed the wrong firmware.. the good one is FULL OTA MF PV
What's your model phone exactly ? VNS-L21C??? Single/Dual SIM ?
edit: I believe you used dload method then use Firmware Finder for updating to Android 7.0
FunnkyHD said:
You installed the wrong firmware.. the good one is FULL OTA MF PV
What's your model phone exactly ? VNS-L21C??? Single/Dual SIM ?
edit: I believe you used dload method then use Firmware Finder for updating to Android 7.0
Click to expand...
Click to collapse
That's the point. I dont know my model. I cant check it in options (have no keyboard) and i cant check it in fastboot becouse i have locked botlooader so i cant flash custom recovery/rom too. The only thing i know is that short model number. It is hybrid dual SIM. And I did just downgrade with package, it wasnt whole rom, and yes, by sdcard method.
Use rollback package to downgrade to Marshmallow
FunnkyHD said:
Use rollback package to downgrade to Marshmallow
Click to expand...
Click to collapse
Do you even listen to me. I just did that and I have no keboard and I can't find my rom to reinstall it to get keyboard.
hello im stuck in the same situation. how did you solve it?
Just install Gboard

No service axon 7 A2017U help me please

I changed my cell phone from A2017 to A2017U with no problem but ... now IMEI everything ok, unless the signal without no service appears whats wrong? Does anyone know something to solve this problem? Thank so much guys
What's ur phone model? If its the U model flash U modem if G or CN flash modem for their respective models
J0nhy said:
What's ur phone model? If its the U model flash U modem if G or CN flash modem for their respective models
Click to expand...
Click to collapse
I have an Axon 7 Chinese version I changed to the A2017U version android 7.1.1
Senik said:
I have an Axon 7 Chinese version I changed to the A2017U version android 7.1.1
Click to expand...
Click to collapse
You'll have to install ch modem im pretty sure you can find it around the forums
J0nhy said:
You'll have to install ch modem im pretty sure you can find it around the forums
Click to expand...
Click to collapse
where I find a modem that works, I searched the forum all the way down trying to see one that works. I did not install it because I do not know the right one to install, because mine was a Chinese version to get an area in the version with a U variant. Do you have a correct link?
Senik said:
where I find a modem that works, I searched the forum all the way down trying to see one that works. I did not install it because I do not know the right one to install, because mine was a Chinese version to get an area in the version with a U variant. Do you have a correct link?
Click to expand...
Click to collapse
https://androidfilehost.com/?w=files&flid=148464
Last one in the list...
joaste said:
https://androidfilehost.com/?w=files&flid=148464
Last one in the list...
Click to expand...
Click to collapse
Forgive me for asking so many questions, but this topic is good so that other people with this problem try to solve it too, I under which of the files?
Senik said:
Forgive me for asking so many questions, but this topic is good so that other people with this problem try to solve it too, I under which of the files?
Click to expand...
Click to collapse
Most people have searched and found the modem files. They are mentioned in many of the ROM threads.
As said, the last one in the list: A2017_N_Modem.zip.
Good luck.
joaste said:
https://androidfilehost.com/?w=files&flid=148464
Last one in the list...
Click to expand...
Click to collapse
joaste said:
Most people have searched and found the modem files. They are mentioned in many of the ROM threads.
As said, the last one in the list: A2017_N_Modem.zip.
Good luck.
Click to expand...
Click to collapse
I'm on android 7.1.1 I tried the last version b19 of mivafor, it did not work for twrp because when I start the system it hangs on the black screen of unlocking the bootloader
Senik said:
I'm on android 7.1.1 I tried the last version b19 of mivafor, it did not work for twrp because when I start the system it hangs on the black screen of unlocking the bootloader
Click to expand...
Click to collapse
Sorry, but you are not very clear on your issue. A modem file will not prevent you from booting.
If you flashed B19, which I believe is for the A2017U, did you also flash a universal bootloader? I believe this will be necessary. Also, how did you flash it?
You'll need to say what exactly your phone is (A2017, A2017U, A2017G), confirm your booltoader was unlocked already (I suppose it was), what state you phone is in now, and what you flashed already.
Then perhaps someone who understands your situation can help you.
joaste said:
Sorry, but you are not very clear on your issue. A modem file will not prevent you from booting.
If you flashed B19, which I believe is for the A2017U, did you also flash a universal bootloader? I believe this will be necessary. Also, how did you flash it?
You'll need to say what exactly your phone is (A2017, A2017U, A2017G), confirm your booltoader was unlocked already (I suppose it was), what state you phone is in now, and what you flashed already.
Then perhaps someone who understands your situation can help you.
Click to expand...
Click to collapse
I bought it in banggood it's a 2017 4gb 128gb Chinese version, so I unlocked the bootloader, until then everything ok, I used the B19 \ A2017U_B19-NOUGAT_FULL_EDL miflash, this was the version I used to change the system from A2017 to A2017U. because when I start the system everything works well unless the area goes up, even with the chip says in the service, however I saw that it can solve this being and the Chinese and American networks are different. I installed the one that you sent me the link by twrp modem A2017 but when I start the system it is in the black screen of the message of the unlocked bootloader. hence I come back in TWRP and it works less the system starts
Senik said:
I bought it in banggood it's a 2017 4gb 128gb Chinese version, so I unlocked the bootloader, until then everything ok, I used the B19 \ A2017U_B19-NOUGAT_FULL_EDL miflash, this was the version I used to change the system from A2017 to A2017U. because when I start the system everything works well unless the area goes up, even with the chip says in the service, however I saw that it can solve this being and the Chinese and American networks are different. I installed the one that you sent me the link by twrp modem A2017 but when I start the system it is in the black screen of the message of the unlocked bootloader. hence I come back in TWRP and it works less the system starts
Click to expand...
Click to collapse
Sorry, but it is still not clear to me. It is best to wait for someone like @Choose an username... to help, if he has the time.
Flash this ch modem through twrp https://androidfilehost.com/?fid=457095661767137840
I think this should solve ur problem
Senik said:
I bought it in banggood it's a 2017 4gb 128gb Chinese version, so I unlocked the bootloader, until then everything ok, I used the B19 \ A2017U_B19-NOUGAT_FULL_EDL miflash, this was the version I used to change the system from A2017 to A2017U. because when I start the system everything works well unless the area goes up, even with the chip says in the service, however I saw that it can solve this being and the Chinese and American networks are different. I installed the one that you sent me the link by twrp modem A2017 but when I start the system it is in the black screen of the message of the unlocked bootloader. hence I come back in TWRP and it works less the system starts
Click to expand...
Click to collapse
This is a mess. Do this:
Download an A2017 miflash package, just like the one you used to wreck your phone. Install it. If the signal works, you have two options:
-Update to official Oreo (it's out for Chinese phones). It should appear as an OTA. After updating DON'T change to other systems. Just stay with Oreo.
-If you still want to install the U system, don't update. take the A2017U package that you had downloaded, and delete the file called NHLOS.bin inside (might be called NON-HLOS.bin, I don't remember). Then flash it via MiFlash just as you did before
Choose an username... said:
This is a mess. Do this:
Download an A2017 miflash package, just like the one you used to wreck your phone. Install it. If the signal works, you have two options:
-Update to official Oreo if you don't want to install the u software (it's out for Chinese phones). It should appear as an OTA.
-If you still want to install the U system, take the A2017U package that you had downloaded, and delete the file called NHLOS.bin inside (might be called NON-HLOS.bin, I don't remember). Then flash it via MiFlash just as you did before
Click to expand...
Click to collapse
I decided the following way I made a backup of everything of the A2017U since the A2017 did not get wifi imei nothing .. so I did use the miflash and put the Chinese version B13, hence I installed the twrp since my bootloader was unlocked. I used the backup and started the system now everything works
Senik said:
I decided the following way I made a backup of everything of the A2017U since the A2017 did not get wifi imei nothing .. so I did use the miflash and put the Chinese version B13, hence I installed the twrp since my bootloader was unlocked. I used the backup and started the system now everything works
Click to expand...
Click to collapse
Good. If I were you I'd restore to B13 and update to Oreo, but if you're okay with the old U firmware then ok
Choose an username... said:
Good. If I were you I'd restore to B13 and update to Oreo, but if you're okay with the old U firmware then ok
Click to expand...
Click to collapse
when I go by twrp still appears the A2017U this can be a problem later? Even though you were the only one who understood me I speak Portuguese English for me is a bit complicated, but every day I struggle to improve. ah already there forgetting I appeared an update here of the b15 but being I updated more goes to the twrp screen I start the system and usually updates more when I go there in the mifavor to see if there is another update appears the old b15 to update again some solution?
Senik said:
when I go by twrp still appears the A2017U this can be a problem later? Even though you were the only one who understood me I speak Portuguese English for me is a bit complicated, but every day I struggle to improve. ah already there forgetting I appeared an update here of the b15 but being I updated more goes to the twrp screen I start the system and usually updates more when I go there in the mifavor to see if there is another update appears the old b15 to update again some solution?
Click to expand...
Click to collapse
I understood you, but I think it would be easier if you also wrote it in Portuguese. I talk Spanish, so I can also understand Portuguese.
So, you want to get Oreo? If you do, you have to use MiFlash to install the chinese B13 update. After that the update to Oreo should appear.
Choose an username... said:
I understood you, but I think it would be easier if you also wrote it in Portuguese. I talk Spanish, so I can also understand Portuguese.
So, you want to get Oreo? If you do, you have to use MiFlash to install the chinese B13 update. After that the update to Oreo should appear.
Click to expand...
Click to collapse
it does not update because of the twrp since the original recovery has no error in the update, how to remove twrp and return with original recovery mode?
Senik said:
it does not update because of the twrp since the original recovery has no error in the update, how to remove twrp and return with original recovery mode?
Click to expand...
Click to collapse
Didn't TWRP get replaced after you flashed the MiFlash images? If so, you can get the recovery.img from the B13 package and install it from TWRP (Install - install image

flashed a2017u b35 Nougat 7.1.1 (SIM Card Airplane Mode)

Flashed A2017U b35 Nougat 7.1.1 on a2017 Chinese , USB to PC Hangs (should Restart to work)
Most Important is 2 Sim Showing No Service and when trying to Make A call Saying (Turn Off Airplane Mode to Make A Call)
Despite it Closed , SIM CARD Working on Other Device !!!
Not 100% sure, but it could have something to do with having the wrong radios on the US firmware.
Sidenote, where did you get the B35 update, would you mind sharing it?
KH_Lionheart said:
Not 100% sure, but it could have something to do with having the wrong radios on the US firmware.
Sidenote, where did you get the B35 update, would you mind sharing it?
Click to expand...
Click to collapse
It's official Nougat, literally nothing special
I think someone will upload the U files in some time anyways
Right, but what is special is that OTA is the only way it was put out. ZTE never made it available for download from the support page from what I understand so no one seems to actually have the usable firmware available to download in the way others have copies of the official firmware from ZTE support page. Plus since he has the Chinese model it means he probably didn't get it OTA and has a flash able file that he could share.
KH_Lionheart said:
Not 100% sure, but it could have something to do with having the wrong radios on the US firmware.
Sidenote, where did you get the B35 update, would you mind sharing it?
Click to expand...
Click to collapse
I Missed it but this file name (A2017U_B32_NOUGAT_FULL_EDL) .zip , i extracted it and flashed by mi-flash
Mohamed.Rady2017 said:
I Missed it but this file name (A2017U_B32_NOUGAT_FULL_EDL) .zip , i extracted it and flashed by mi-flash
Click to expand...
Click to collapse
at all , thanks for rebly ,kindly ,need to install by mi-flash A2017U_OREO_FULL_EDL as i have problem to unlock with boot-loader (twrp) and unlike to root my device

Stuck on NRD90M test-keys

Team,
I've got a problem. My brother got the phone locked on NRD90M test-keys and can't roll back. I've tried getting into the SD card the UDPATE.APP for my model (VNS-L22) but when doing the three key method it shows an error message with something like "incompatibility with current software" and it just gives me the option to reboot the device. I have access to the device as it boots but things like camera stopped working (it's been a while since he did that and he just told me)
I've tried with the "Huawei Recovery Updater thread" here but I don't know if I am doing something wrong or what but it does not work.
Reading a bit more it seems I've to unlock bootloader and do a bunch of things, just wondering what do you think is the best approach or how can I get back to stock ROM, so we he can get OTA updates and have the device working without a problem.
He did this by using the Firmware Finder app from play store, so I guess he did an update and got the device on that state.
Device details:
EMUI Version: 5.0
Android Version: 7.0
Huawei P9 lite
Model: Huawei VNS-L22
I appreciate all the help you could provide,
Thanks!
danag07 said:
Team,
I've got a problem. My brother got the phone locked on NRD90M test-keys and can't roll back. I've tried getting into the SD card the UDPATE.APP for my model (VNS-L22) but when doing the three key method it shows an error message with something like "incompatibility with current software" and it just gives me the option to reboot the device. I have access to the device as it boots but things like camera stopped working (it's been a while since he did that and he just told me)
I've tried with the "Huawei Recovery Updater thread" here but I don't know if I am doing something wrong or what but it does not work.
Reading a bit more it seems I've to unlock bootloader and do a bunch of things, just wondering what do you think is the best approach or how can I get back to stock ROM, so we he can get OTA updates and have the device working without a problem.
He did this by using the Firmware Finder app from play store, so I guess he did an update and got the device on that state.
Device details:
EMUI Version: 5.0
Android Version: 7.0
Huawei P9 lite
Model: Huawei VNS-L22
I appreciate all the help you could provide,
Thanks!
Click to expand...
Click to collapse
Hello,
if you remember exactly the complete firmware your device were on
before been stucked on NRD90M test-keys, maybe using Firmware Finder ( FF )
you'll be able to force the update to a newer and working version..
( ex. mine was VNS-L31C432B381 and updated to B415 )
The other method is most complicated...
Unlock the bootloader, flash a custom recovery and use
Huawei Recovery Updater in order to reflash your stock rom.
Then you should use FF too to make an update and correctly
relock the bootloader.
Is you'll use those awesome apps don't forget to thank the developers.
Cheers
Dadditz said:
Hello,
if you remember exactly the complete firmware your device were on
before been stucked on NRD90M test-keys, maybe using Firmware Finder ( FF )
you'll be able to force the update to a newer and working version..
( ex. mine was VNS-L31C432B381 and updated to B415 )
The other method is most complicated...
Unlock the bootloader, flash a custom recovery and use
Huawei Recovery Updater in order to reflash your stock rom.
Then you should use FF too to make an update and correctly
relock the bootloader.
Is you'll use those awesome apps don't forget to thank the developers.
Cheers
Click to expand...
Click to collapse
Yes I do, actually I just realized the one I could find here wasn't the same I had before so maybe I will try that one. I tried firmware finder from the app but it wasn't working properly, when downloading the FULL OTA files it started crashing and then I was not able to proceed with the "downgrade" now i've used the FF for PC and downloaded the files from FULL OTA, however there are 3 files. I am not sure what to put into the dload folder.
These are the files:
update.zip
update_data_full_hw_normal.zip
update_data_full_ice_cr.zip
As per my understanding I should place only the files from "update.zip" right? I also saw a few comments on a video that said put all content from all three files into the dload folder.
If you happen to know the answer I will appreciate it!
Hello,
I'm also stuck in this rom... But in my case I went from a custom ROM to it. But it blocked my bootloader, etc...
And I forgot my bootloader code
Now I have to unlock it and I will use DC-Unlocked but when I dial this number: *#*#2846579#*#* in this ROM it doesn't show anything!!! So I can't open Project Menu...
What can I do?
Thanks
danag07 said:
Yes I do,
actually I just realized the one I could find here wasn't the same I had before so maybe I will try that one. I tried firmware finder from the app but it wasn't working properly, when downloading the FULL OTA files it started crashing and then I was not able to proceed with the "downgrade" now i've used the FF for PC and downloaded the files from FULL OTA, however there are 3 files. I am not sure what to put into the dload folder.
These are the files:
update.zip
update_data_full_hw_normal.zip
update_data_full_ice_cr.zip
As per my understanding I should place only the files from "update.zip" right? I also saw a few comments on a video that said put all content from all three files into the dload folder.
If you happen to know the answer I will appreciate it!
Click to expand...
Click to collapse
Dude,
you cannot use DLOAD aka three buttons method
on nougat ( android 7 ) 'cause it wont work.
As i wrote you should know exactly the firmware your device were before the softbrick.
Getting 'nrd90m - test keys' firmware probably mean you already tried to use a wrong firmware.
I don't know whic firmware you downloaded, but i can assure you without that correct no methods will work.
As you can see in the attachment exists many custs ( C185, C569. C576, C635, C636, etc... )
and firmware ( Bxxx ) that indicate the region/brand were you live or where the device was sold when you bought it and if single or dual sim.
Without those info become a lot complicated bring back your device in an working state.
The last chance should be a rebrand but you need some files like OEMinfo zip but ever first you should unlock the bootloader, flash a custom recovery and use HWOTA method, but the risk
to completely brick the device is really high.
Example of a firmware : VNS-L31C432B415
VNS ( venus is the name of the device )
L31 ( is the version of the device )
C432 ( is the cust that indicate the region where was sold )
B415 ( is the running firmware/security patch on the device )
You had VNS-L22 C??? B???
paniczzz said:
Hello,
I'm also stuck in this rom... But in my case I went from a custom ROM to it. But it blocked my bootloader, etc...
And I forgot my bootloader code
Now I have to unlock it and I will use DC-Unlocked but when I dial this number: *#*#2846579#*#* in this ROM it doesn't show anything!!! So I can't open Project Menu...
What can I do?
Thanks
Click to expand...
Click to collapse
Dude,
before attempting to unlock again the bootloader
you should try to force the update with Firmware Finder.
What was the firmware you were on before flashing your custom rom ?
Which custom firmware you were on ?
How you gone back to stock ?
Which stock firmware you used to go stock ?
Dadditz said:
Dude,
you cannot use DLOAD aka three buttons method
on nougat ( android 7 ) 'cause it wont work.
As i wrote you should know exactly the firmware your device were before the softbrick.
Getting 'nrd90m - test keys' firmware probably mean you already tried to use a wrong firmware.
I don't know whic firmware you downloaded, but i can assure you without that correct no methods will work.
As you can see in the attachment exists many custs ( C185, C569. C576, C635, C636, etc... )
and firmware ( Bxxx ) that indicate the region/brand were you live or where the device was sold when you bought it and if single or dual sim.
Without those info become a lot complicated bring back your device in an working state.
The last chance should be a rebrand but you need some files like OEMinfo zip but ever first you should unlock the bootloader, flash a custom recovery and use HWOTA method, but the risk
to completely brick the device is really high.
Example of a firmware : VNS-L31C432B415
VNS ( venus is the name of the device )
L31 ( is the version of the device )
C432 ( is the cust that indicate the region where was sold )
B415 ( is the running firmware/security patch on the device )
You had VNS-L22 C??? B???
Click to expand...
Click to collapse
So the firmware I had before doing that was VNS-L22C106B150.
What should I do with that if the android app is not working? I mean... I tried doing it with firmware finder and it didn't work, used proxy thing, dns thing, downloaded the files (multiple errors, files corrupted) and it is not my internet connection, it's the app. I did downloaded the files on the Windows app
danag07 said:
So the firmware I had before doing that was VNS-L22C106B150.
What should I do with that if the android app is not working? I mean... I tried doing it with firmware finder and it didn't work, used proxy thing, dns thing, downloaded the files (multiple errors, files corrupted) and it is not my internet connection, it's the app. I did downloaded the files on the Windows app
Click to expand...
Click to collapse
Ok, if you sure your firmware are L22C106, things aren't so good.
Cannot make an update, can make a downgrade but you need the correct rollback package
and i don't know were you can find it, but in any case you couldn't re-upgrade to android 7.
Checking in the FF PC 's app, as you can see, no nougat
versions of this firmware are present. Which version you downloaded before ?
If you are really sure about that firmware, you have only a possibility, which is
make a rebrand but it's a bit complicated and really dangerous.
Choise remain yours, you can find some guides how to do a rebrand, just search
in the p9 lite threads.
Cheers

Categories

Resources