Related
Hi guys massive android noobie here!
I really hope you guys can help me cause I am desperate!
This is what happened: I tried to manually update my phone B200 to B313. I had no luck with the update.zip so I tried the update.app (superstupid). As you guys might know, this resulted in a bootloop.
I downloaded Huawei firmware extractor and adb. I have two problems on top of a not working phone:
1: when i try to extract my firmware i just get a system.img, no boot.img or the other one you need
2: i managed to unlock my bootloader, but whenever i use adb devices it stays empty, fastboot reboot works though... weird
How do I get my lovely device working again?
Kind regards,
Jurgen
Flash B200 again with 3 button method, should work
Extract zip files and copy update.app on SD card, in dload folder
lejur said:
Hi guys massive android noobie here!
I really hope you guys can help me cause I am desperate!
This is what happened: I tried to manually update my phone B200 to B313. I had no luck with the update.zip so I tried the update.app (superstupid). As you guys might know, this resulted in a bootloop.
I downloaded Huawei firmware extractor and adb. I have two problems on top of a not working phone:
1: when i try to extract my firmware i just get a system.img, no boot.img or the other one you need
2: i managed to unlock my bootloader, but whenever i use adb devices it stays empty, fastboot reboot works though... weird
How do I get my lovely device working again?
Kind regards,
Jurgen
Click to expand...
Click to collapse
I tried to do something similar, although I screwed it up even further. Prior to attempting this entire process, I was using GRA-L09 build B171. After attempting to install B317 from B171, I got stuck in a bootloop between the Huawei logo and TWRP. I realized that my mistake was probably because I had TWRP instead of the stock ROM. Therefore, I downloaded the B170 full firmware and extracted the B170 files. I tried to use fastboot to flash boot.img system.img and recovery.img according to bihsik's guide, but fastboot could never recognize my device. So I decided to be "smart" and transfer Boot.img and recovery.img from the B170 firmware to my dload folder on my external sd card on the phone and install them directly from TWRP.
This screwed everything up, and now I'm stuck in Rescue Mode with "Error! Func NO : 11 (recovery image) Error NO : 2 (load failed!)"
I've searched google and XDA forums and have tried the methods here and here but without any luck.
Is there a way to fix my phone?
You can Easily Fix your Device , Just follow the Steps Carefully
Follow this link to fix your Mobile:
This Tutorial is easy to follow. Fix your device and Return to your OFFICIAL STOCK ROM
https://youtu.be/4AkSuE20_08
Links are included in video Description .
Cheers...!
I bricked my mobile few months ago and I fixed my mobile using this video , hope it will help you guys too.
---------- Post added at 12:28 PM ---------- Previous post was at 12:25 PM ----------
vudawatta said:
I tried to do something similar, although I screwed it up even further. Prior to attempting this entire process, I was using GRA-L09 build B171. After attempting to install B317 from B171, I got stuck in a bootloop between the Huawei logo and TWRP. I realized that my mistake was probably because I had TWRP instead of the stock ROM. Therefore, I downloaded the B170 full firmware and extracted the B170 files. I tried to use fastboot to flash boot.img system.img and recovery.img according to bihsik's guide, but fastboot could never recognize my device. So I decided to be "smart" and transfer Boot.img and recovery.img from the B170 firmware to my dload folder on my external sd card on the phone and install them directly from TWRP.
This screwed everything up, and now I'm stuck in Rescue Mode with "Error! Func NO : 11 (recovery image) Error NO : 2 (load failed!)"
I've searched google and XDA forums and have tried the methods here and here but without any luck.
Is there a way to fix my phone?
Click to expand...
Click to collapse
Just be Care full in choosing the Firmware , if your firmware doesn't match , then the 3 Button method will stop at 5%.
Changing thread to become updates on trying to 7.0 to work on L29
IGNORE:Has anyone tested the leaked Android N on an L29. It was confirmed that dload is not working. Has anyone tried fastboot
UPDATE:Tried flashing Boot Cust System and Recovery images from the new update.app. It flashed successfully with no errors. However, the device is currently stuck on "Device is booting"
Any Suggestions?
UPDATE 2:Went ahead and flashed the boot recovery and cust images from the update.app from L29C636B320 and i went through the device is booting screen. Currently on a black screen without a boot animation, waiting for something to happen. Tried a factory reset through the recovery and it failed. I'll let you know if it boots up
UPDATE 3: Noticed HiSuite being recognized, not sure how long its been there. Its been 15 minutes on black screen losing hope
UPDATE 4: Flashed back to B320 for now, @nakul has instructions to getting Nougat. Please refer to those. As of now I did not try it, I will when I have the time. Basically it's using dload after rebranding L29 as AL 10
UnchartedRd said:
Has anyone tested the leaked Android N on an L29. It was confirmed that dload is not working. Has anyone tried fastboot
Click to expand...
Click to collapse
Dload not working on my NXT-L29 bootloader Locked
Not tested by Bootloader
streetbike55 said:
Dload not working on my NXT-L29 bootloader Locked
Not tested by Bootloader
Click to expand...
Click to collapse
OK I'll try it with fastboot, as mine is unlocked. I guess I'll take the risk, however I believe that it should work.
UnchartedRd said:
OK I'll try it with fastboot, as mine is unlocked. I guess I'll take the risk, however I believe that it should work.
Click to expand...
Click to collapse
Ok, but if I understand it will pass the phone in AL-10. Because this leak is for AL-10
streetbike55 said:
Ok, but if I understand it will pass the phone in AL-10. Because this leak is for AL-10
Click to expand...
Click to collapse
Yeah, but the hardware is identical to the AL10.
UnchartedRd said:
Yeah, but the hardware is identical to the AL10.
Click to expand...
Click to collapse
Be carreful with related "Google play services" bug. Like contact synchronisation for example .
streetbike55 said:
Be carreful with related "Google play services" bug. Like contact synchronisation for example .
Click to expand...
Click to collapse
OK I'll keep that in mind. Thanks
UnchartedRd said:
OK I'll keep that in mind. Thanks
Click to expand...
Click to collapse
Good Luck !
we want the news ! :good:
streetbike55 said:
Good Luck !
we want the news ! :good:
Click to expand...
Click to collapse
I will let you know in a few hours or in the morning. It's late where I live
So how did it work out?
Skickat från min HUAWEI NXT-L29 via Tapatalk
Tried flashing Boot Cust System and Recovery images from the new update.app. It flashed successfully with no errors. However, the device is currently stuck on "Device is booting"
Any Suggestions?
Went ahead and flashed the boot recovery and cust images from the update.app from L29C636B320 and i went through the device is booting screen. Currently on a black screen without a boot animation, waiting for something to happen. Tried a factory reset through the recovery and it failed. I'll let you know if it boots up
UnchartedRd said:
Changing thread to become updates on trying to 7.0 to work on L29
IGNORE:Has anyone tested the leaked Android N on an L29. It was confirmed that dload is not working. Has anyone tried fastboot
UPDATE:Tried flashing Boot Cust System and Recovery images from the new update.app. It flashed successfully with no errors. However, the device is currently stuck on "Device is booting"
Any Suggestions?
UPDATE 2:Went ahead and flashed the boot recovery and cust images from the update.app from L29C636B320 and i went through the device is booting screen. Currently on a black screen without a boot animation, waiting for something to happen. Tried a factory reset through the recovery and it failed. I'll let you know if it boots up
Click to expand...
Click to collapse
UPDATE 3: Noticed HiSuite being recognized, not sure how long its been there. Its been 15 minutes on black screen losing hope
Bad news :crying:
Originally Posted by UnchartedRd
Changing thread to become updates on trying to 7.0 to work on L29
IGNORE:Has anyone tested the leaked Android N on an L29. It was confirmed that dload is not working. Has anyone tried fastboot
UPDATE:Tried flashing Boot Cust System and Recovery images from the new update.app. It flashed successfully with no errors. However, the device is currently stuck on "Device is booting"
Any Suggestions?
UPDATE 2:Went ahead and flashed the boot recovery and cust images from the update.app from L29C636B320 and i went through the device is booting screen. Currently on a black screen without a boot animation, waiting for something to happen. Tried a factory reset through the recovery and it failed. I'll let you know if it boots up
UPDATE 3: Noticed HiSuite being recognized, not sure how long its been there. Its been 15 minutes on black screen losing hope
Click to expand...
Click to collapse
do you try with dload via sd card L29C636320
UnchartedRd said:
UPDATE 3: Noticed HiSuite being recognized, not sure how long its been there. Its been 15 minutes on black screen losing hope
Click to expand...
Click to collapse
You doesn't flash Cache.img and userdata.img ?
streetbike55 said:
You doesn't flash Cache.img and userdata.img ?
Click to expand...
Click to collapse
I had the same issue on Saturday. Flash the recovery from the Android N zip file. Then downgraded to B172 using the dload method. Upgraded again to B320 and stopped there. Try it... Good Luck
This Tips only for L29C636xxx for upgrade to nouget 7 beta for L10 cn chinese only
uses Srk tool
1 root and unlock bootloader
2 use srktool Menu 7 utility /9:Changing oeminfo and custom.bin after that phone will reboot and reset factory
i have problem with phone show unlock in ADB but can not flash stock recovery via srk tool unlock once again
3 phone must open usb debug use srk tool flash stock recovery choose you have rom 4.0or 4.1
4 now phone on deban with L10 with usb debug make dload folder only sd card which copy file nouget update.app
5 at phone call *#*#2446578#*#* at 4: software upgrade phone will reboot to update with dload wait
6 until restart again ****f volum up with power go to menu reformat factory
end
now phone must on nouget 7
good thing this rom fast smooth and save bat can login huawei id install app
bad thing sim slot 1 lock only for cn chinese mobile only sim slot 2 only 2g internet
phone show lock ADB error can not flash anything
i can rool back by dload again with rom 4.1 AL 10 only
after unlock bootloader and root deban Changing oeminfo and custom.bin to L29C636320
laster dload with rom L29C636320
now phone with lock rom L29
someone wants to testing this rom nouget 7 ?
@nakul Are you sure turned on OEM unlock in developer options
nakul said:
do you try with dload via sd card L29C636320
Click to expand...
Click to collapse
Dload is not working with L29 but as @nakul said rebranding your phone seems to work. He also mentioned that International Sims are only receiving 2g internet
Okay, so :- :crying::crying::crying::crying:
I was on nougat and went to downgrade and followed ALL instruction apart from one - which was something I missed with translate until i visited the htc page for the tenth time trying to fix this.
:silly: :crying: ----- I didnt change default location whilst running nougat -----:silly: :crying:
I flashed the c432 oem file, and I have tried to update to b151, b150 and b161 all through the update.app method. to no avail.
I have tried flashing everything manually through adb pushing AND fastboot after using the extractor and everything works EXCEPT the system.img. I am faced with an error telling me it has failed, 'unable to mount /system' - - - This message comes through regardless of what I do and im panicking
PLEASE HELP I AM SO STUCK
thank you in advance for any suppport
What P9 lite you have?
Johnny TDN said:
What P9 lite you have?
Click to expand...
Click to collapse
I have the vns-L31 however ive just opened dc unlocker and its showing my model as 21
i can access fastboot and rescue mode as well as twrp although when flashing im faced with the /system error
It is written, on htcmania, using c432oeminfo and b130.
so,
Code bootloader
Twrp meticulus.
Install c432oeminfo.zip, power off
Restart dload c432b130.
Chisetdel31260 said:
It is written, on htcmania, using c432oeminfo and b130.
so,
Code bootloader
Twrp meticulus.
Install c432oeminfo.zip, power off
Restart dload c432b130.
Click to expand...
Click to collapse
i will try that, although ill get errors when flashing the zip - not only that but I cant get to meticulus once its flashed - possibly the system error?
Restart, bootloader code,
Twrp Meticulous, went a wipe, xxxx everything except external storage, installs c432oeminfo.zip, dload c432b130.
http://www.htcmania.com/showthread.php?t=1265458
Chisetdel31260 said:
Restart, bootloader code,
Twrp Meticulous, went a wipe, xxxx everything except external storage, installs c432oeminfo.zip, dload c432b130.
http://www.htcmania.com/showthread.php?t=1265458
Click to expand...
Click to collapse
what do you mean when you say code bootloader? what should i do there? anything im missing?
raihanbam said:
what do you mean when you say code bootloader? what should i do there? anything im missing?
Click to expand...
Click to collapse
Yes, I noticed that from time to time, in bootloader mode, it is written unlocked, but as the device bootloop (bug) I believe it too. so
I retype systematically the bootloader code to open.
raihanbam said:
what do you mean when you say code bootloader? what should i do there? anything im missing?
Click to expand...
Click to collapse
If you have your bootloader unlocked (if you don,t have it, unlock it) and flash TWRP. After that, flash B130 for your VNS-L31. Done.
Unlock yor Bootloader again. And try flashing again.
Have hade the same problem. My bootloader showed unlocked, but he was not.
Ron
raihanbam said:
what do you mean when you say code bootloader? what should i do there? anything im missing?
Click to expand...
Click to collapse
i have followed all of these and notw its stuck on your device is booting.....
i flashed the rom with recovery so now ill try the dload method again, i assume ill have to flash the second zip with recovery?
Chisetdel31260 said:
Restart, bootloader code,
Twrp Meticulous, went a wipe, xxxx everything except external storage, installs c432oeminfo.zip, dload c432b130.
http://www.htcmania.com/showthread.php?t=1265458
Click to expand...
Click to collapse
i am now stuck with your device is booting - cant access fastboot or recovery at all - doesnt show up in adb or fastboot either
raihanbam said:
i am now stuck with your device is booting - cant access fastboot or recovery at all - doesnt show up in adb or fastboot either
Click to expand...
Click to collapse
Shut down your device. Press the switch off for 10 secounds.
When the phone is off, swith on and same time with vol + without usb-kabel, and otherwise try it with usb-kabel.
When you stock recovery starts. You can try a factoryreset.
When you Revolution recovery starts flash oem.info again and perform the dload methode with your right MM UPDATE.APP.
Ron
RonPo said:
Shut down your device. Press the switch off for 10 secounds.
When the phone is off, swith on and same time with vol + without usb-kabel, and otherwise try it with usb-kabel.
When you stock recovery starts. You can try a factoryreset.
When you Revolution recovery starts flash oem.info again and perform the dload methode with your right MM UPDATE.APP.
Ron
Click to expand...
Click to collapse
no matter what I do I'm stuck with the device is booting screen I even let the battery drain to try that way-I'm so screwed
RonPo said:
Shut down your device. Press the switch off for 10 secounds.
When the phone is off, swith on and same time with vol + without usb-kabel, and otherwise try it with usb-kabel.
When you stock recovery starts. You can try a factoryreset.
When you Revolution recovery starts flash oem.info again and perform the dload methode with your right MM UPDATE.APP.
Ron
Click to expand...
Click to collapse
no matter what I do I'm stuck with the device is booting screen I even let the battery drain to try that way-I'm so screwed
RonPo said:
Shut down your device. Press the switch off for 10 secounds.
When the phone is off, swith on and same time with vol + without usb-kabel, and otherwise try it with usb-kabel.
When you stock recovery starts. You can try a factoryreset.
When you Revolution recovery starts flash oem.info again and perform the dload methode with your right MM UPDATE.APP.
Ron
Click to expand...
Click to collapse
okay so I got to the erecovery screen, it only gives the option to dl the latest version and fails along with reboot and shutdown - no wipe
raihanbam said:
okay so I got to the erecovery screen, it only gives the option to dl the latest version and fails along with reboot and shutdown - no wipe
Click to expand...
Click to collapse
OK. Go to bootloader and flash:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
extract this files with: Huawei Update Extractor from your Original UPDATE.APP
system.img is loading in steps and need much time.
Ron
Hi guys, i have the same problem after doing some ****, flashed stock rom from lineageos 14 and a lot of things that i'm trying now to unbrick my phone... i cant enter to the erecovery with the 3 buttons method, wathever i do, and i dont have any idea on how to unbrick my phone... I hope someone could help me
Anderusk said:
There is an assumption that I have a slightly different display. TWRP by Grarak does not work correctly with stock drivers. On LOS driver through a certain time, too, dies. I have A JDI screen, the device works correctly with stock ROM. I hate EMUI, and like LOS, but cant use it.
I already thought to install LOS and never reboot the device. 7 times i had died screen drivers on LOS and AOSP, and always it was happen in the first minutes after reboot.
@Axan,https://cloud.mail.ru/public/78UN/jSQ7mjhWT
I have stock ROM L11C432B394 flashed by 3 buttons, but device was AL-10 changed to Can-L11 with HUC, Vendor - hw, Country - eu.
Click to expand...
Click to collapse
I've flashed this oeminfo to my Can-L01 phone, phone does not boot (stuck at red huawei logo on boot) 3 button recovery wont start just a boot loop on 3 button... VolUP+Power does not open recovery... VolDown+Power opens fastboot mode but immediately reboots (there's a strange thing on screen that it started to say Phone Locked FRP Unlocked instead of Phone Unlocked or Relocked) my phone is totaly bricked now...
giraygokirmak said:
I've flashed this oeminfo to my Can-L01 phone, phone does not boot (stuck at red huawei logo on boot) 3 button recovery wont start just a boot loop on 3 button... VolUP+Power does not open recovery... VolDown+Power opens fastboot mode but immediately reboots (there's a strange thing on screen that it started to say Phone Locked FRP Unlocked instead of Phone Unlocked or Relocked) my phone is totaly bricked now...
Click to expand...
Click to collapse
I have finally get into a stable Fastboot mode, but unfortunately my phones serial number has changed to the oeminfo shared by our friend so my unlock code does not work anymore. Since the phone can not boot i cannot set Manufacture mode so i cannot unlock using paid apps. I am at the hands of our friend who shared oeminfo twrp backup to share his Unlock code inorder to recover my phone back to my oeminfo backup file. Or my phone is total brick
giraygokirmak said:
my phone is totaly bricked now...
Click to expand...
Click to collapse
You need to know what you're doing. in my country, changing IMEI is a criminal offense.
It is possible to raise locked phone using the firmware with three buttons, in this case I think you need to try a can-l11, because oeminfo is from can-l11 model
giraygokirmak said:
I've flashed this oeminfo to my Can-L01 phone, phone does not boot (stuck at red huawei logo on boot) 3 button recovery wont start just a boot loop on 3 button... VolUP+Power does not open recovery... VolDown+Power opens fastboot mode but immediately reboots (there's a strange thing on screen that it started to say Phone Locked FRP Unlocked instead of Phone Unlocked or Relocked) my phone is totaly bricked now...
Click to expand...
Click to collapse
Anderusk said:
You need to know what you're doing. in my country, changing IMEI is a criminal offense.
It is possible to raise locked phone using the firmware with three buttons, in this case I think you need to try a can-l11, because oeminfo is from can-l11 model
Click to expand...
Click to collapse
In my country it is illegal too besides i lost my own serial and imei because of this i think because my serial was different before flashing this oeminfo image backup of yours. I was only expecting to change country and vendor info to flash european firmware not trying to change my imei. And also phone does not boot just shows red huawei logo and thats all no recovery no erecovery and no button combination works like 3 button reboot...
I previously wrote in the subject that changed the location of the device through Huawei Unlock Client. Why u decided change it by flashing oeminfo i dont know. For firmware through three buttons need stock recovery, not erecovery.
Once i tryed flash by three buttons with stock erecovery and twrp in recovery, it was failed. But i many times flash stock firmware with stock recovery and twrp in erecovery and locked bootloader.
Anderusk said:
I previously wrote in the subject that changed the location of the device through Huawei Unlock Client. Why u decided change it by flashing oeminfo i dont know. For firmware through three buttons need stock recovery, not erecovery.
Once i tryed flash by three buttons with stock erecovery and twrp in recovery, it was failed. But i many times flash stock firmware with stock recovery and twrp in erecovery and locked bootloader.
Click to expand...
Click to collapse
I didnt have credit and thus i couldnt use HCU Client, How did you managed to flash many times stock recovery and twrp while having locked bootloader? I read that this is impossible... When i try flashing stock firmware or recovery fastboot only says
FAILED (remote: Command not allowed)
finished. total time: 0.018s
With a locked bootloader, you can flash through three buttons. You cannot flash TWRP or other partitions.
Anderusk said:
With a locked bootloader, you can flash through three buttons. You cannot flash TWRP or other partitions.
Click to expand...
Click to collapse
You dont understand... 3 button does not work! It just reboots endlessly while pressing 3 buttons at the same time. I've been using 3 button eRecovery menu before, i know how to enter to it. But after flashing your TWRP Backup phone stuck at boot logo red huawei logo and these combinations do not work, i repeat do not work!
VolUp + Power On --> This should bring recovery menu but it doesnt.
VolUp+VolDown+Power On --> This should bring force flash application but it just reboots to huawei logo endlessly...
VolDown+USB Plug --> This should bring Fastboot but it just shows fastboot then reboots immediately.
VolDown+PowerOn + USB Plug --> This brings Fastboot but i cant flash anything because PHONE Locked status and unlock you've provided does not help.
In the end, i have a total brick. I will try to forcefully flash through DC-Phoenix software but i lost hope with the phone completely plus i'll have to pay 15euro just to try... It was perfect before your oeminfo twrp backup file. I just wanted to change vendor/country info thats all and didn't want to use HCU Client to change it
All CAN-L11 or L01 owners DO NOT, DO NOT use any other person's oeminfo partition backup in any way!!!!!!!
giraygokirmak said:
VolUp+VolDown+Power On --> This should bring force flash application but it just reboots to huawei logo endlessly...
Click to expand...
Click to collapse
3 buttons work, but u dont know how use it.
I say again, u can flash with VolUp+VolDown+Power On if u have stock recovery and locked/unlocked bootloader and locked/unlocked FRP. I know because i did it.
Do you know how to use Google search? Look for information on how to flash with three buttons. And go to relevant topic.
Anderusk said:
3 buttons work, but u dont know how use it.
I say again, u can flash with VolUp+VolDown+Power On if u have stock recovery and locked/unlocked bootloader and locked/unlocked FRP. I know because i did it.
Do you know how to use Google search? Look for information on how to flash with three buttons. And go to relevant topic.
Click to expand...
Click to collapse
Dude, in order to restore your oeminfo twrp backup one has to be on TWRP recovery not Stock recovery. So in TWRP recovery if you restore the file oeminfo twrp backup of yours and reboot phone gets into my situation. I know how to use 3 button force flash (its been written trillion places on web including this forum) i wrote here as a warning because you have shared your OEMINFO twrp backup on this thread not any other and i wanted to warn people not to get into a situation like mine.
I' am in a very bad situation here
giraygokirmak said:
Dude, in order to restore your oeminfo twrp backup one has to be on TWRP recovery not Stock recovery.
Click to expand...
Click to collapse
This is why I recommend stock recovery and TWRP in erecovery. Now you have one way - DC Phoenix
Anderusk said:
This is why I recommend stock recovery and TWRP in erecovery. Now you have one way - DC Phoenix
Click to expand...
Click to collapse
Please remove your oeminfo twrp backup before anybody else gets hurt. right now you have 2 dead bodies... @Axan just wrote that his phone become bricked just like the same way as mine. Yea i know we had the responsibility but there's something wrong with the file you provided...
giraygokirmak said:
Please remove your oeminfo twrp backup before anybody else gets hurt. right now you have 2 dead bodies... @Axan just wrote that his phone become bricked just like the same way as mine. Yea i know we had the responsibility but there's something wrong with the file you provided...
Click to expand...
Click to collapse
Victims reached 3 unfortunately, a guy with the nickname @lazy_prodigy also bricked his phone with the file you shared that oeminfo backup. His serial number became just like mine
Test attached oeminfo from eu version, you can replace file in twrp by path /dev/block/platform/soc/7824900.sdhci/by-name, it's not twrp flash archive.
Thanks, is this OEMINFO C432 dual sim or single sim?
Great that finally someone shared it!
trol_sg said:
Thanks, is this OEMINFO C432 dual sim or single sim?
Great that finally someone shared it!
Click to expand...
Click to collapse
Dual SIM can-l11
Temanyan said:
Test attached oeminfo from eu version, you can replace file in twrp by path /dev/block/platform/soc/7824900.sdhci/by-name, it's not twrp flash archive.
Click to expand...
Click to collapse
Thanks For Sharing Sir
Sir Need Help To Read oeminfo Partition
Adb Commands Or Any Tool ?
I Have Rooted CAN-L12
Want To Read/Backup oeminfo
But Not From TWRP
Will Be Grateful To You
Thanks Anticipation
Hello everyone.
I managed to brick my p9 lite (VNS-L31C432 dual sim) by flashing the rollback package over B161 (I know B160 is for DS, I just missed the correct update.app twice). The current status of my phone right now is:
- Phone won't boot, is stuck at "Phone is booting now"
- VolUP + VolDOWN + Power combination doesn't access to dload. If I have it connected via usb to my computer it kinda enter to dload but an usb plug symbol appears and does nothing
- Can unblock/rebock bootloader
- Can access to TWRP 3.0.2-0
- Can access to Fastboot and flash partitions, however when I do it TWRP lose the ability to mount them and they appear as 0MB partitions (I have to change fs to EXT2 then to EXT4 to make them work again).
So, from where should I start to try to recover my phone?
Mairtrus said:
Hello everyone.
I managed to brick my p9 lite (VNS-L31C432 dual sim) by flashing the rollback package over B161 (I know B160 is for DS, I just missed the correct update.app twice). The current status of my phone right now is:
- Phone won't boot, is stuck at "Phone is booting now"
- VolUP + VolDOWN + Power combination doesn't access to dload. If I have it connected via usb to my computer it kinda enter to dload but an usb plug symbol appears and does nothing
- Can unblock/rebock bootloader
- Can access to TWRP 3.0.2-0
- Can access to Fastboot and flash partitions, however when I do it TWRP lose the ability to mount them and they appear as 0MB partitions (I have to change fs to EXT2 then to EXT4 to make them work again).
So, from where should I start to try to recover my phone?
Click to expand...
Click to collapse
Hello,
unlock again the bootloader then use correct rollback package (or flash L31C432OEMinfo_bin dual sim file with TWRP) and DLOAD correct firmware this time...
If you are unsure just ask...
Cheers
Dadditz said:
Hello,
unlock again the bootloader then use correct rollback package (or flash L31C432OEMinfo_bin dual sim file with TWRP) and DLOAD correct firmware this time...
If you are unsure just ask...
Cheers
Click to expand...
Click to collapse
Thanks, pal, but I already fixed it, doing a lot of trial-errors
If someone who had the same problems I had is reading this, what you really need to do is:
As Dadditz said, flash first your correct oem info, then unlock the bootloader
If you can't access dload, find the full-ota package for the exact same version of MM you previously had (before the brick, of course). Unzip the UPDATE.APP and then use UpdateExtractor to get BOOT, SYSTEM, RECOVERY, RECOVERY2 and CUST. Flash all of them via Fastboot.
If you try to boot and it gets into eRecovery, then it's a good sign. Put the UPDATE.APP from the previous step in the dload folder of your SD, use the dload method and let the install run. It will probably fail at the end, this seems to be normal.
You phone will boot and it will probably feel like it's working ok again, but I bet there are chances that a some stuff doesn't work or even appear at all (first time the fingerprint config didn't appeared to me, second time was the google account login). Turn off the phone, install the correct version of TWRP, wipe cache/dalvik, then do a factory reset (dunno if both are needed, I just did it this way and it worked ok).
Reboot you phone. Now it should really be working ok again.
If you little P9-Lite refuses to update to a newer version, use Firmware Finder to upgrade whatever version FullOTA-MF-PV you want to (in my case, I did to B370).
Enjoy
I'm still wondering why installing the wrong rollback package messes up with the recovery2 partition...
Mairtrus said:
Thanks, pal, but I already fixed it, doing a lot of trial-errors
If someone who had the same problems I had is reading this, what you really need to do is:
As Dadditz said, flash first your correct oem info, then unlock the bootloader
If you can't access dload, find the full-ota package for the exact same version of MM you previously had (before the brick, of course). Unzip the UPDATE.APP and then use UpdateExtractor to get BOOT, SYSTEM, RECOVERY, RECOVERY2 and CUST. Flash all of them via Fastboot.
If you try to boot and it gets into eRecovery, then it's a good sign. Put the UPDATE.APP from the previous step in the dload folder of your SD, use the dload method and let the install run. It will probably fail at the end, this seems to be normal.
You phone will boot and it will probably feel like it's working ok again, but I bet there are chances that a some stuff doesn't work or even appear at all (first time the fingerprint config didn't appeared to me, second time was the google account login). Turn off the phone, install the correct version of TWRP, wipe cache/dalvik, then do a factory reset (dunno if both are needed, I just did it this way and it worked ok).
Reboot you phone. Now it should really be working ok again.
If you little P9-Lite refuses to update to a newer version, use Firmware Finder to upgrade whatever version FullOTA-MF-PV you want to (in my case, I did to B370).
Enjoy
I'm still wondering why installing the wrong rollback package messes up with the recovery2 partition...
Click to expand...
Click to collapse
Yep, factory reset + wipe cache did the work..
Cheers