Build.prop - Desire 820 General

I rooted my phone recently about 2 months back before the update. Now when i put it back to stock ROM n ota could not finish update a red triangle with exclamatory mark appears. I pressed the volume up and power button together to show error it said build prop has changed. I dont know what to do i accessed my build.prop file using text editor everything seems different from the original form i found for my phone on the net. i dont know how to reset it please can someone help. My phone works fine and awesome but i cant ota please help

I have a similar problem as well kind of xD.
I accidently deleted my os xD in the twrp recovery soooo i cant reinstall the stock ROM.
And ik how to but i have to S-Off my htc desire 820 and pretty much unroot it and reconfigure it so yea idk
Can any1 tell me how to s-off an htc desire 820 with your computer or recovery and how to install clockwork recovery on thc desire 820?

Vikas_D_S said:
I rooted my phone recently about 2 months back before the update. Now when i put it back to stock ROM n ota could not finish update a red triangle with exclamatory mark appears. I pressed the volume up and power button together to show error it said build prop has changed. I dont know what to do i accessed my build.prop file using text editor everything seems different from the original form i found for my phone on the net. i dont know how to reset it please can someone help. My phone works fine and awesome but i cant ota please help
Click to expand...
Click to collapse
If you are rooted with Custom [ twrp,Cwm , what ever ] recoveries then you will not be able to do an OTA update . You will either get stuck in boot loop or recovery loop .

help
h1dd3n_sn1p3r said:
If you are rooted with Custom [ twrp,Cwm , what ever ] recoveries then you will not be able to do an OTA update . You will either get stuck in boot loop or recovery loop .
Click to expand...
Click to collapse
i have reinstalled stock recovery image and the update process begins but gets stuck due to absense of original build.prop file

Vikas_D_S said:
i have reinstalled stock recovery image and the update process begins but gets stuck due to absense of original build.prop file
Click to expand...
Click to collapse
man just install twrp recovery and flash stock rom. then re-install your stock recovery, should get you fixed. don't forget to remove root also before making the OTA update.

Related

I can't Boot into ICS recovery after the OTA UPDATE

HI, Due tooo...excitement ...
lAST night I cant wait for the new ICS on ACER so I flash The COM_GEN1 coming from COM_GEN2 in CMW after that it updated to ICS... I also installed the ACER recovery but now when I used it and boot into recovery it says my tablet is not rooted?! and I tried the power+ volume down...It doesn't go recovery mode...instead its erasing some cache and a dead android with exclamation point appeared . ....... Can some 1 help me? I humbly ask for you help. Thank you.
hatyrei said:
HI, Due tooo...excitement ...
lAST night I cant wait for the new ICS on ACER so I flash The COM_GEN1 coming from COM_GEN2 in CMW after that it updated to ICS... I also installed the ACER recovery but now when I used it and boot into recovery it says my tablet is not rooted?! and I tried the power+ volume down...It doesn't go recovery mode...instead its erasing some cache and a dead android with exclamation point appeared . ....... Can some 1 help me? I humbly ask for you help. Thank you.
Click to expand...
Click to collapse
no patience whatsoever..
acer a500 , when I tried to press & hold power + up volume key it says
recovery verified failed ...
hatyrei said:
acer a500 , when I tried to press & hold power + up volume key it says
recovery verified failed ...
Click to expand...
Click to collapse
flash the unlocked ICS bootloader and install custom recovery with it , guide here
civato said:
flash the unlocked ICS bootloader and install custom recovery with it , guide here
Click to expand...
Click to collapse
Hi Civato,
Thanks., I'm thinkinring with my tab earlier using your guide but i have no luck.
Problems:
I used the uid log on my cmw that was store on my sd card before i update into ICS. i DID go to vache site nad get my sbk
0xB1927C00 0xA404C006 0xCB6B2404 0x30772103 but when i press enter ....the txt was fast and I just had a glimps of it before it was gone....it says something like this NV ERROR : Connection failed
also When I tried to go to APX it only work once.... Tablet was powered off hold the rest botton and the power key....then APX was installed to my computer.... after i remove the usb and put it back to my computer it was gone... I cant find it in the usb controller
pls. help...I think Im learning but...pls be patient hehehe thanks
hatyrei said:
Hi Civato,
Thanks., I'm thinkinring with my tab earlier using your guide but i have no luck.
Problems:
I used the uid log on my cmw that was store on my sd card before i update into ICS. i DID go to vache site nad get my sbk
0xB1927C00 0xA404C006 0xCB6B2404 0x30772103 but when i press enter ....the txt was fast and I just had a glimps of it before it was gone....it says something like this NV ERROR : Connection failed
also When I tried to go to APX it only work once.... Tablet was powered off hold the rest botton and the power key....then APX was installed to my computer.... after i remove the usb and put it back to my computer it was gone... I cant find it in the usb controller
pls. help...I think Im learning but...pls be patient hehehe thanks
Click to expand...
Click to collapse
Go back and try it again, you didn't follow the directions fully. It works if you do it right.
cruise350 said:
Go back and try it again, you didn't follow the directions fully. It works if you do it right.
Click to expand...
Click to collapse
Im really having trouble with the APX mode..... I already powered down the device and start poking and holding the reset button + the power button , then release it after 3 seconds... then the reset button... I only see the ACER logo then it vibrates then turned off .... At first Iam able to start the apx...vuz its installing the driveon my computer but after i removed it it was gone....
cruise350 said:
Go back and try it again, you didn't follow the directions fully. It works if you do it right.
Click to expand...
Click to collapse
I finally Made it ., it says PASS on my screen then i boot in to recovery do i need to install the A500-1.031.00-LIGHT-WITH_ICS_BOOTLOADER? or ist possible to go back restore to my back up? running HC 3.2.1 COM_GEN2? and recived official ICS UPDATE..... The thing is I cheated at first I installed COM_GEN1 ( 1.031 ww com_gen1) over my COM_GEN2...after that it upgrade automatically to ICS without connecting to my Wifi! And I thought it was not legit...
hatyrei said:
I finally Made it ., it says PASS on my screen then i boot in to recovery do i need to install the A500-1.031.00-LIGHT-WITH_ICS_BOOTLOADER? or ist possible to go back restore to my back up? running HC 3.2.1 COM_GEN2? and recived official ICS UPDATE..... The thing is I cheated at first I installed COM_GEN1 ( 1.031 ww com_gen1) over my COM_GEN2...after that it upgrade automatically to ICS without connecting to my Wifi! And I thought it was not legit...
Click to expand...
Click to collapse
Not possible to go back to HC that easy , see in the guide I posted , there is a link to a thread on how to.
And you don't need to flash the light version A500 rom from the guide thread as you are already on the ICS bootloader because you flashed the ICS leak.
Just so you know that 1.031.00 leak is what Acer is pushing out as OTA so you are not missing any thing.
See this line of my guide:
You can also flash the full leaked version of 1.031.00 but then you need to get root so you can delete "recovery-from-boot.p" from /system before you flash the unlocked booloader and custom recovery.
If you feel insecure better to flash full leak that way you get the stock recovery.
civato as we are talking recovery's is it safe to just flash the ICS update as a update.zip with CWM still on the tab or should i replace it with the acer recovery first?
civato said:
Not possible to go back to HC that easy , see in the guide I posted , there is a link to a thread on how to.
And you don't need to flash the light version A500 rom from the guide thread as you are already on the ICS bootloader because you flashed the ICS leak.
Just so you know that 1.031.00 leak is what Acer is pushing out as OTA so you are not missing any thing.
See this line of my guide:
You can also flash the full leaked version of 1.031.00 but then you need to get root so you can delete "recovery-from-boot.p" from /system before you flash the unlocked booloader and custom recovery.
If you feel insecure better to flash full leak that way you get the stock recovery.
Click to expand...
Click to collapse
Thanks Civato,
I manage to go back to HC which I got a back-up file in my CMW in my SDCARD ....after I installed the boot thingy V3 I regain the CMW recovery...then I just fully restored to my HC 3.2.1 com_gen2. After that I still manage to retain the V3 thingy boot & CMW recovery... Also, i got the official OTA & I'm running ICS now . Thank you so much. xoxoxooxx
civato said:
Not possible to go back to HC that easy , see in the guide I posted , there is a link to a thread on how to.
And you don't need to flash the light version A500 rom from the guide thread as you are already on the ICS bootloader because you flashed the ICS leak.
Just so you know that 1.031.00 leak is what Acer is pushing out as OTA so you are not missing any thing.
See this line of my guide:
You can also flash the full leaked version of 1.031.00 but then you need to get root so you can delete "recovery-from-boot.p" from /system before you flash the unlocked booloader and custom recovery.
If you feel insecure better to flash full leak that way you get the stock recovery.
Click to expand...
Click to collapse
The gen2's are being updated to 1.033.00_PA_CUS1
cruise350 said:
Go back and try it again, you didn't follow the directions fully. It works if you do it right.
Click to expand...
Click to collapse
It doesn't work. Any other ideas?

[Q] LG G2 bricked and can't flash stock firmware!

So I'm really into Android developing, I'm always flashing and installing etc, but I got a problem now.
Phone information​
LG G2 D802
Rooted
TWRP Recovery 2.7.0.0
Was running 4.4.2, found a kdz file on the internet and flashed it (no regular update from my phone)
What happened​I actually did something stupid, I received an application update from the LG Download Center (or whatever it's called) on my phone and clicked on it. I was planning on flashing Android 4.4.2 again because my firmware was not stable, and I thought this update could help me.
But no, after it finished downloading, I automatically booted into recovery.
What I did​So I tried to reboot and enter my OS, but unfortunately, I was stuck in recovery.
I did everything I could, wiping (Dalvik) cache, factory reset, flashed a new rom, restored Nandroid backup, but no, every time I booted, I got back into recovery again.
I only saw 1 option left, booting into download mode and flashing a new firmware.
I found the Netherlands 16GB kdz file for Android 4.4.2 (because I had a French one first), the one I was looking for.
Looked all over the internet, and all guides pointed me to this guide.
Tried it, but I got multiple errors, one of them was that my phone was not connected while I was at 15% of the flash process.
What happened​After that first flashing process, I booted up, but got a Security Error. After the Security Error was showing for 5 seconds, my phone shut down. This is happening every time I try to boot up.
I couldn't access my recovery anymore, nothing. Edit: I can access my recovery right now, and I tried this, but when I boot up I get the Security Error again.
The big problem right now is the Security Error! How do I bypass that?
So can someone please help me out!
Several phones/tablets of mine bricked and I always found a way to get out of it, but not this time, unfortunately...
Have you tried this
Sent from LG-G2 D800 on AEONFLEX 4.4.2
XxZombiePikachu said:
Have you tried this
Sent from LG-G2 D800 on AEONFLEX 4.4.2
Click to expand...
Click to collapse
Yes, I actually have. Didn't mention it, but after I did that I booted and got an LG logo and below it was a text that said 'Security Error' After like 5 seconds the security error goes away and my phone shuts down. I can only enter download mode right now.
I'll edit my first post with this info.
Thanks for the help though!
Edit: I find a way to access my recovery again because at first I couldn't but I figured out that the code in the thread you linked was a bit different than the code I entered at first.
So I used the code you gave me, but now I get the Security Error again!
Hi mate, just like you i downloaded that damn OTA today and messed up my phone, but in my case was because i had totally forgotten it was rooted and had custom recovery installed :silly::silly::silly::silly:
I followed this tutorial to fix the boot secure error http://forum.xda-developers.com/showthread.php?t=2582142 and it worked like a charm except for download mode wasn't working at all.
After doing some research i found this post http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html and got download mode (apparently) working again but Windows didn't recognize it at all so i couldn't use it to flash the .kdz stock firmware.
In the end i just flashed a custom aosp rom and got my phone back to life but the download mode issue it's still there and it's bothering me quite a lot.
Any suggestion is welcome.
EDIT: Don't download the recovery from the post, instead look for the latest version (2.7.0.0) because the one posted there (2.6.3.2) might corrupt your partitions
evilruck said:
Hi mate, just like you i downloaded that damn OTA today and messed up my phone, but in my case was because i had totally forgotten it was rooted and had custom recovery installed :silly::silly::silly::silly:
I followed this tutorial to fix the boot secure error http://forum.xda-developers.com/showthread.php?t=2582142 and it worked like a charm except for download mode wasn't working at all.
After doing some research i found this post http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html and got download mode (apparently) working again but Windows didn't recognize it at all so i couldn't use it to flash the .kdz stock firmware.
In the end i just flashed a custom aosp rom and got my phone back to life but the download mode issue it's still there and it's bothering me quite a lot.
Any suggestion is welcome.
EDIT: Don't download the recovery from the post, instead look for the latest version (2.7.0.0) because the one posted there (2.6.3.2) might corrupt your partitions
Click to expand...
Click to collapse
Thanks! But does my internal storage get whiped? Will all my pictures etc. be gone?
And the first thred removes the security error right? And after that I can just boot into recovery mode (I can boot in recovery btw) and flash a new rom? Just wanted to know this so I don't go through all that trouble for nothing
Edit: You know I can enter both download and recovery mode right?
Ibrahim9999 said:
Thanks! But does my internal storage get whiped? Will all my pictures etc. be gone?
And the first thred removes the security error right? And after that I can just boot into recovery mode (I can boot in recovery btw) and flash a new rom? Just wanted to know this so I don't go through all that trouble for nothing
Edit: You know I can enter both download and recovery mode right?
Click to expand...
Click to collapse
Nope internal SD remains intact, basically what you'll be doing is pushing the right files into the system partitions and yes, in theory you should be able to flash a new rom.
Even if you can boot into recovery you should do it if you're getting that error, and after that you can just push a ROM file to flash (i'll assume you know how to do it) and btw let me know if you decide to flash a stock based rom instead of an aosp like i did.
Good luck with that :good:
evilruck said:
Nope internal SD remains intact, basically what you'll be doing is pushing the right files into the system partitions and yes, in theory you should be able to flash a new rom.
Even if you can boot into recovery you should do it if you're getting that error, and after that you can just push a ROM file to flash (i'll assume you know how to do it) and btw let me know if you decide to flash a stock based rom instead of an aosp like i did.
Good luck with that :good:
Click to expand...
Click to collapse
Thanks man! I'm probably going to save money because of you, awesome!
Ibrahim9999 said:
Thanks man! I'm probably going to save money because of you, awesome!
Click to expand...
Click to collapse
I hope so!
Let me know if you fix the thing :laugh:
evilruck said:
I hope so!
Let me know if you fix the thing :laugh:
Click to expand...
Click to collapse
I just managed to fix it! Thank you so much man!
Can someone help me plz I got flashily got CWM instead of the TWRP and got and lg update it updated and now it's stuck in recovery mode it won't go into download mode it only goes to recovery mode and my computer won't recognize my phone so if any one knows how to fix it can you plz help me out
my pc don't recognize the lg g2 in download mode!
i installed the drivers and the USB is connected but the pc don;t even say that the device is connected . and nothing in device manager at all
Perhaps you might consider sending it in to lg if you still have warranty. But I'd you don't, there are services on eBay/ Craigslist that can help you.
Sent from my LG-D800 using XDA Free mobile app

Huawei u8800 pro stuck on image signature verification fail!

I am in need of help....
I have a Huawei u8800 pro. I upgraded it to ICS the official upgrade. I had rooted my device when it was on 2.3.5 itself.I had changed the recovery to twrp and had flashed many ROMs onto it which were listed in thus forum. Every ROM were good but always had a problem with the network. I used to go back to the gingerbread everytime because i had a nandroid backup. I then upgraded the phone to the official ICS by the method they had suggested.But I still had the problem with network so I went back to recovery and twrp was not there so i tried to put new one and now I am stuck on image signature verify fail!The pink wont show the image drive also wat should I do.....i am so desparate about wat to do...pls help me..pls reply..thanking u in advance..
Nishadhnash said:
I am in need of help....
I have a Huawei u8800 pro. I upgraded it to ICS the official upgrade. I had rooted my device when it was on 2.3.5 itself.I had changed the recovery to twrp and had flashed many ROMs onto it which were listed in thus forum. Every ROM were good but always had a problem with the network. I used to go back to the gingerbread everytime because i had a nandroid backup. I then upgraded the phone to the official ICS by the method they had suggested.But I still had the problem with network so I went back to recovery and twrp was not there so i tried to put new one and now I am stuck on image signature verify fail!The pink wont show the image drive also wat should I do.....i am so desparate about wat to do...pls help me..pls reply..thanking u in advance..
Click to expand...
Click to collapse
the new one as in TWRP 2.8.6.0?
which version of ICS did you install B928?
if so did you:
check if baseband 404029 instead of 404020?
IMEI wasn't messed up during process?
follow pink screen unlock method?
where does it say image signature verify fail during which process?
I am not able boot the phone its....neither to recover or normal mode...the baseband was 404029..I think
Nishadhnash said:
I am not able boot the phone its....neither to recover or normal mode...the baseband was 404029..I think
Click to expand...
Click to collapse
If you were on B928 version, you can run pink screen unlock to install a custom recovery such as TWRP.
However if you're not able to boot, this possibly means you flashed a wrong firmware. double check if you have a u8800pro not the u8800 or u8800+ (i'm not sure about the + one) they have different firmware.
Overall if you have a u8800pro, i recommend installing the stock B928 following the official procedure, this is almost a foolproof method to fix any possible software issue you may have.
the link below should have all you need.
http://forum.xda-developers.com/showthread.php?t=1736650
Solved the problem
The answer was so simple....If u want all the data present in your mobile download the boot loader unlocker from the website given above by sarsiroslayer..thx man
Paste the Update.App in folder called dload and the folder should be in the root of the sdcard...yes you need a sdcard...and then remove the battery of the phone so it switches off...then connect the phone to the USB wire without battery...and immediatly press the volume. Down,volume up and power button...so it goes to a pink screen..and remember the sdcard should already be placed in the phone...and yes if the phone does not go into pink screen and instead starts to update the software Olla ur phone is fixed......restart and all will be fine...
Ifthis did not work or u don't want any data download the official 2.3.5 android from the huawei site and place the update.app in dload folder and do the same thing as above....My phone is working..:highfive:
Remember remove the battery...before updating ....
Thx all for ur support..xda rocks...
I have typed the solution so even a begginer can utjnderstand...

551ml Bricked after updating to new offical MM build. (help pls)

Hello guys, I noticed this morning that MM was officially released today. I followed the steps on to update my phone. I downloaded the rom for 551ml put it on my root of my internal storage, after that a pop up showed that there was a system update. I did the update and now my phone wont turn on now. It vibes twice and nothing comes on the screen. I have no idea how to fix it. I was on the latest firmware that system update would give me (184). If someone isn't busy could they possibly help me out. thx..
Same issue here, have you found a solution yet?
arturocr said:
Same issue here, have you found a solution yet?
Click to expand...
Click to collapse
tyring a guide atm but links seem to be outdated. I managed to get in fastboot or whatever its called when you can boot in to recovery. but from there I cant do anything.
You cant get into recovery after fastboot?
Sent from my ASUS_Z00AD using XDA Premium HD app
same problem ,
so im from cm 13 lastest build , and then i wipe data from twrp , after that i directly flash MM offical rom and its done without any problem. the problem start after i reboot system. my phone just vibrating twice with no lights led on , no screen on , no asus logo , can't go to recovery nor fastboot just keep restarting i guess because after a couple minute it vibrate again.
when i charge it wont show charging battrey , only stuck at battrey logo with zap with no charging animation.
don't have any clue. can anyone help ?
try to connect to pc but only show "moorefield" with (?).
sorry for my bad english.
Same for me...
baonxxx said:
same problem ,
so im from cm 13 lastest build , and then i wipe data from twrp , after that i directly flash MM offical rom and its done without any problem. the problem start after i reboot system. my phone just vibrating twice with no lights led on , no screen on , no asus logo , can't go to recovery nor fastboot just keep restarting i guess because after a couple minute it vibrate again.
when i charge it wont show charging battrey , only stuck at battrey logo with zap with no charging animation.
don't have any clue. can anyone help ?
try to connect to pc but only show "moorefield" with (?).
sorry for my bad english.
Click to expand...
Click to collapse
I think mm system.img boot.img splashcreen.img need mm bootloder to run and at the moment twrp doesnt work with it, if you install mm via twrp you only updating these img and bootloader still lp that causes your phone cant boot. (Correct me if im wrong)
So now you need xfstk downloader to recover your fastboot and then flash .194 raw firmware using asus flash tool then adb sideload mm firmware from stock .194 recovery, theres guide how to do that in here but im forget where
Sorry my english are bad too..
miku1024 said:
I think mm system.img boot.img splashcreen.img need mm bootloder to run and at the moment twrp doesnt work with it, if you install mm via twrp you only updating these img and bootloader still lp that causes your phone cant boot. (Correct me if im wrong)
So now you need xfstk downloader to recover your fastboot and then flash .194 raw firmware using asus flash tool then adb sideload mm firmware from stock .194 recovery, theres guide how to to that in here but im forget where
Sorry my english are bad too..
Click to expand...
Click to collapse
how does make xfstk work ? don't have idea how. it just show nothing after i open xfstk , have a reference link ?
baonxxx said:
same problem ,
so im from cm 13 lastest build , and then i wipe data from twrp , after that i directly flash MM offical rom and its done without any problem. the problem start after i reboot system. my phone just vibrating twice with no lights led on , no screen on , no asus logo , can't go to recovery nor fastboot just keep restarting i guess because after a couple minute it vibrate again.
when i charge it wont show charging battrey , only stuck at battrey logo with zap with no charging animation.
don't have any clue. can anyone help ?
try to connect to pc but only show "moorefield" with (?).
sorry for my bad english.
Click to expand...
Click to collapse
baonxxx said:
how does make xfstk work ? don't have idea how. it just show nothing after i open xfstk , have a reference link ?
Click to expand...
Click to collapse
I found the link!
You need You need asus usb and intel soc drivers
Heres
http://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
Try this: http://forum.xda-developers.com/zenfone2/general/guide-how-to-update-to-official-mm-t3452082
miku1024 said:
I think mm system.img boot.img splashcreen.img need mm bootloder to run and at the moment twrp doesnt work with it, if you install mm via twrp you only updating these img and bootloader still lp that causes your phone cant boot. (Correct me if im wrong)
So now you need xfstk downloader to recover your fastboot and then flash .194 raw firmware using asus flash tool then adb sideload mm firmware from stock .194 recovery, theres guide how to do that in here but im forget where
Sorry my english are bad too..
Click to expand...
Click to collapse
I used XFSTK to upload firmware etc... but after upload firmware, the phone will vibrate twice and download of OS will not start... the soft will try 20 attemps to connect with the phone and the OS part can't be download on the phone... I'm stick at this point.
Hello guys, i'm trying to unbrick my phone, i'm following this guide http://forum.xda-developers.com/zenf...l-usb-t3405840 but when i get to the end of te install of intelSoC my device is detected as Moorefield for like 4-5 seconds and then it disappears. I've been trying to solve this for like 4 hours now, a little help would be much appreciated.
quarterbreed said:
tyring a guide atm but links seem to be outdated. I managed to get in fastboot or whatever its called when you can boot in to recovery. but from there I cant do anything.
Click to expand...
Click to collapse
try this if you unable to flash
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
try this if you unable to flash
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
I did this morning and it worked. Im on 6.0.1 now, I guess the cause of my brick was that I had TWRP installed. Now I know next time to remove it before updating lol.
quarterbreed said:
I did this morning and it worked. Im on 6.0.1 now, I guess the cause of my brick was that I had TWRP installed. Now I know next time to remove it before updating lol.
Click to expand...
Click to collapse
glad to know that it worked. but sad to know that despite that you didn't hit thanks
quarterbreed said:
I did this morning and it worked. Im on 6.0.1 now, I guess the cause of my brick was that I had TWRP installed. Now I know next time to remove it before updating lol.
Click to expand...
Click to collapse
If you don't need to use twrp everyday (maybe just a backup from time to time) you'd better keep stock recovery and whenever you need something from twrp, you just boot into it without flashing with the usual "fastboot boot twrp.img" command. That way if you ever upgrade again you don't have to remember whether you removed twrp before. But that's just an opinion, since if done that way, you'd need to have yor phione hooked to a computer to get into twrp, an that's not always possible.
thanks
quarterbreed said:
I did this morning and it worked. Im on 6.0.1 now, I guess the cause of my brick was that I had TWRP installed. Now I know next time to remove it before updating lol.
Click to expand...
Click to collapse
sukhwant717 said:
try this if you unable to flash
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
that link saved my phone, thanks man
sukhwant717 said:
glad to know that it worked. but sad to know that despite that you didn't hit thanks
Click to expand...
Click to collapse
I just hit thanks now, I was at my limit of 8 at the time.

P9 Lite wont turn on

Hello everyone, have been a long time
I have a VNS-L21 (P9 Lite 2016) from Colombia, it worked fine but I started to get more and more ads over the time so I decided to unlock the bootloader and root it, and I did it, after almost a year of working just fine, the phone start to restart by itself with no reason around 1 or 2 days per month, they were not scheduled or something.
Last night the phone started to restart by itself again, but this time after it turned on completely it went off some minutes later and started to restart several times without reason, I got frustrated so I decided to uninstall root (thought it was the problem) but the problem was still there, turn on and after some minutes it went off and restart.
Then I decided to check for updates and it had a pending update so I chose to install it but after restart, it won’t come on and kept in an endless boot loop.
Can anyone help me and tell me what to do? Thanks in advance...
fr4nk32 said:
Hello everyone, have been a long time
I have a VNS-L21 (P9 Lite 2016) from Colombia, it worked fine but I started to get more and more ads over the time so I decided to unlock the bootloader and root it, and I did it, after almost a year of working just fine, the phone start to restart by itself with no reason around 1 or 2 days per month, they were not scheduled or something.
Last night the phone started to restart by itself again, but this time after it turned on completely it went off some minutes later and started to restart several times without reason, I got frustrated so I decided to uninstall root (thought it was the problem) but the problem was still there, turn on and after some minutes it went off and restart.
Then I decided to check for updates and it had a pending update so I chose to install it but after restart, it won’t come on and kept in an endless boot loop.
Can anyone help me and tell me what to do? Thanks in advance...
Click to expand...
Click to collapse
Hello,
I bet that along with the root you also had a custom recovery.
So if before you install the update you have re-flashed the stock recovery, simply hold vol + and power button until it restarts in e-recovery mode. At this point make a factory reset and wipe cache.
Reboot system, done.
If instead you have not reinstalled the stock recovery, download one for the system you use (android 6 or 7) and install it via fastboot. ( you can download a rom the same version you use and extract recovery with extractor.
There are two recovery.img in the rom, just take recovery, NOT recovery2 ).
Try to reboot with vol + and power until you turn it on,
then factory reset in custom recovery.
Reboot in fastboot mode, install stock recovery, reboot system and launch again the update.
Happy holidays and good luck
Dadditz said:
Hello,
I bet that along with the root you also had a custom recovery.
So if before you install the update you have re-flashed the stock recovery, simply hold vol + and power button until it restarts in e-recovery mode. At this point make a factory reset and wipe cache.
Reboot system, done.
If instead you have not reinstalled the stock recovery, download one for the system you use (android 6 or 7) and install it via fastboot. ( you can download a rom the same version you use and extract recovery with extractor.
There are two recovery.img in the rom, just take recovery, NOT recovery2 ).
Try to reboot with vol + and power until you turn it on,
then factory reset in custom recovery.
Reboot in fastboot mode, install stock recovery, reboot system and launch again the update.
Happy holidays and good luck
Click to expand...
Click to collapse
Hello, thanks for answer
Yes, I still have the custom recovery and I was using nougat, where can I find an stock recovery for nougat? I wasn't able to use firmware finder (didn't understand how to use it).. does the recovery in rollback package works for this? just asking...
or can someone provide an stock rom compatible with my phone?
sorry for my bad engish and my little knowledge of all this, thanks in advance.
fr4nk32 said:
Hello, thanks for answer
Yes, I still have the custom recovery and I was using nougat, where can I find an stock recovery for nougat? I wasn't able to use firmware finder (didn't understand how to use it).. does the recovery in rollback package works for this? just asking...
or can someone provide an stock rom compatible with my phone?
sorry for my bad engish and my little knowledge of all this, thanks in advance.
Click to expand...
Click to collapse
No worries dude my english is very bad too......
So, you're in nougat L21, but what is your complete firmware ? (example L21C432B504)
Then download from official THREAD Firmware Finder for PC and unzip in a folder on your desktop.
Launch FF and go to COMMON BASE tab.
Type your complete firmware into search space and click on the search button...
Find FULL OTA MF firmware, tap on FILELIST tab, a pop up will appear...
Select the whole link of ONLY update.zip and copy/past into your browser for download...
Once downloaded, unzip to a folder on your desktop.
Download Huawei Update Extractor you find here on XDA...
Launch HUE and select UPDATE.APP you find into folder you just unzipped from upadate.zip...
Now you'll see two recovery, just select recovery.img and with mouse's* right key extract somewere on your desktop...
Done dude you have stock recovery....
Copy that .img recovery into your adb/fastboot folder (very important) and reboot in fastboot mode.
If you don't have adb/fastboot just download here from XDA..
From PC with terminal launch "fastboot flash recovery
(name.of.recovery).img" and recovery will be flashed.
Now you have stock recovery and can make stock ota update correctly.
Hope all will take right way, feel free to ask.
Good luck :fingers-crossed:
edit: * added
Dadditz said:
No worries dude my english is very bad too......
So, you're in nougat L21, but what is your complete firmware ? (example L21C432B504)
Then download from official THREAD Firmware Finder for PC and unzip in a folder on your desktop.
Launch FF and go to COMMON BASE tab.
Type your complete firmware into search space and click on the search button...
Find FULL OTA MF firmware, tap on FILELIST tab, a pop up will appear...
Select the whole link of ONLY update.zip and copy/past into your browser for download...
Once downloaded, unzip to a folder on your desktop.
Download Huawei Update Extractor you find here on XDA...
Launch HUE and select UPDATE.APP you find into folder you just unzipped from upadate.zip...
Now you'll see two recovery, just select recovery.img and with mouse's* right key extract somewere on your desktop...
Done dude you have stock recovery....
Copy that .img recovery into your adb/fastboot folder (very important) and reboot in fastboot mode.
If you don't have adb/fastboot just download here from XDA..
From PC with terminal launch "fastboot flash recovery.img" and recovery will be flashed.
Now you have stock recovery and can make stock ota update correctly.
Hope all will take right way, feel free to ask.
Good luck :fingers-crossed:
edit: * added
Click to expand...
Click to collapse
Hello again
thanks for your help, your guide is really useful
One more thing (excuse me for my little knowledge about this) I don't know what's the exact firmware for my phone, I mean I know it is VNS-L21 and should end B3xx but don't know which C... (I didn't check before the cellphone started to bootloop).
I search around the web and found some recommend the C432 one so I download the update.zip from it, would it have any problem if I flash the recovery from there?
And last thing, Can I flash recovery with P9 lite Toolkit? or just through adb? thanks in advance.
fr4nk32 said:
Hello again
thanks for your help, your guide is really useful
One more thing (excuse me for my little knowledge about this) I don't know what's the exact firmware for my phone, I mean I know it is VNS-L21 and should end B3xx but don't know which C... (I didn't check before the cellphone started to bootloop).
I search around the web and found some recommend the C432 one so I download the update.zip from it, would it have any problem if I flash the recovery from there?
And last thing, Can I flash recovery with P9 lite Toolkit? or just through adb? thanks in advance.
Click to expand...
Click to collapse
Dude at this step how can you tell you were on nougat ?
Is your device branded / unbranded one ?
I searched for Colombia firmware and L21 device don't exist, please check behind the cover,
it's wrote at the bottom. ( maybe L23 one ? )
Try to someway backup your stuff then
reboot with vol+ and power button to recovery, tap WIPE then SWIPE to factory reset.
If boot correctly see inside wich is your complete firmware.
C432 are for european area devices, teoratically should work, but will not risk...
Recovery.img can be easily be flashed with toolkit, i used it a lot of times...
Dadditz said:
Dude at this step how can you tell you were on nougat ?
Is your device branded / unbranded one ?
I searched for Colombia firmware and L21 device don't exist, please check behind the cover,
it's wrote at the bottom. ( maybe L23 one ? )
Try to someway backup your stuff then
reboot with vol+ and power button to recovery, tap WIPE then SWIPE to factory reset.
If boot correctly see inside wich is your complete firmware.
C432 are for european area devices, teoratically should work, but will not risk...
Recovery.img can be easily be flashed with toolkit, i used it a lot of times...
Click to expand...
Click to collapse
Hey dude
You really know about this, I'm sure because I updated the phone to Nougat before unlock and root it, time after an update came but I ignore it (I know it was a security updated not sure which one).
Yes, I just checked my phone in the backpart and it is L23, my bad, when you say branded it means if it is related to a phone/internet company? No, it is not tied to any company, I bought it free from internet.
I really don't care about backing up, if it starts from zero or is back to previous stage is fine for me since it can turn on and use it .
Cheers!
fr4nk32 said:
Hey dude
You really know about this, I'm sure because I updated the phone to Nougat before unlock and root it, time after an update came but I ignore it (I know it was a security updated not sure which one).
Yes, I just checked my phone in the backpart and it is L23, my bad, when you say branded it means if it is related to a phone/internet company? No, it is not tied to any company, I bought it free from internet.
I really don't care about backing up, if it starts from zero or is back to previous stage is fine for me since it can turn on and use it .
Cheers!
Click to expand...
Click to collapse
OK, since from first time i saw this post i thinked was a hardware problem, hope no....
You have to reboot to recovery holding vol+ and power button until a recovery will appear.
Then make a factory reset as already wrote in previous post.
Dadditz said:
OK, since from first time i saw this post i thinked was a hardware problem, hope no....
You have to reboot to recovery holding vol+ and power button until a recovery will appear.
Then make a factory reset as already wrote in previous post.
Click to expand...
Click to collapse
Hi there
Sorry for the late reply...
I managed to turn on the phone updating it through dload method (installing stock kernel and trying to update it with erecovery didn't work) without your help I wouldn't know how to to download the right firmware for my phone. Now, my phone is working "properly".
BUT my phone show a new update, when I tried to install it, it says "your device fail verification and may not work properly" and won't install the update, after that if I reboot the phone it will show your device... sign in red letters and won't turn on without choosing continue (when I was using custom kernel, it will show some letters in orange I think, but will turn on by itself without pressing continue) when I installed the firmware through dload I didn't see that message till I try to update the phone.
Thanks in advance and a very happy new year!.
fr4nk32 said:
Hi there
Sorry for the late reply...
I managed to turn on the phone updating it through dload method (installing stock kernel and trying to update it with erecovery didn't work) without your help I wouldn't know how to to download the right firmware for my phone. Now, my phone is working "properly".
BUT my phone show a new update, when I tried to install it, it says "your device fail verification and may not work properly" and won't install the update, after that if I reboot the phone it will show your device... sign in red letters and won't turn on without choosing continue (when I was using custom kernel, it will show some letters in orange I think, but will turn on by itself without pressing continue) when I installed the firmware through dload I didn't see that message till I try to update the phone.
Thanks in advance and a very happy new year!.
Click to expand...
Click to collapse
Dear forgive me, even for me English it's not my main language and maybe
i did not grab everything you posted. Did you use the dload method?
So you were on EMUI 4 / android 6, but now? If I understand correctly when you turn
on the device, see the red lines and press the power button to boot into the system?
If so, unlock again the bootloader.
If you want to post some screenshots so as to simplify ...
Best regards
Dadditz said:
Dear forgive me, even for me English it's not my main language and maybe
i did not grab everything you posted. Did you use the dload method?
So you were on EMUI 4 / android 6, but now? If I understand correctly when you turn
on the device, see the red lines and press the power button to boot into the system?
If so, unlock again the bootloader.
If you want to post some screenshots so as to simplify ...
Best regards
Click to expand...
Click to collapse
Hi there
I have been so busy these days, and I'm thinking in get another phone.
The red letters are still appearing, I cant install updates and it is driving me crazy.
Yes, i did use dloaad method and it turned on but after that it doesnt install the updates neither through dload method. I'm on EMUI 5, it says the bootloader is already unlocked
here are some pictures....
fr4nk32 said:
Hi there
I have been so busy these days, and I'm thinking in get another phone.
The red letters are still appearing, I cant install updates and it is driving me crazy.
Yes, i did use dloaad method and it turned on but after that it doesnt install the updates neither through dload method. I'm on EMUI 5, it says the bootloader is already unlocked
here are some pictures....
Click to expand...
Click to collapse
Hey dude,
Don't worry about replying soon or late,
we all have our personal stuff to do in our lifes...
You' ve been lucky you don't bricked your device using dload method
on your nougat/android 7 rom version.
This is allowed only to downgrade to a precedent android version (in your case android 6/Marshmallow...)
Even it says your bootloader is unlocked, it isn't, so backup your stuff and unlock it again.
Once unlocked, factory reset will start. When finished do wipe cache too...
Booting into the system will now show yellow (not red) lines and after a bit will automatically boot.
Will take some minutes... ( prepare a coffee )
Set up your phone and look forward for updates...
If all will take right direction, new update will completely lock the bootloader
and at the reboot no yellow or red lines will appears. :fingers-crossed:
Voilà, complete stock with latest firmware.
Take your coffee and enjoy :laugh:
Best regards
P.S.: Remove or obscure the screenshot with imei codes ( it's sensitive datas )
Dadditz said:
Hey dude,
Don't worry about replying soon or late,
we all have our personal stuff to do in our lifes...
You' ve been lucky you don't bricked your device using dload method
on your nougat/android 7 rom version.
This is allowed only to downgrade to a precedent android version (in your case android 6/Marshmallow...)
Even it says your bootloader is unlocked, it isn't, so backup your stuff and unlock it again.
Once unlocked, factory reset will start. When finished do wipe cache too...
Booting into the system will now show yellow (not red) lines and after a bit will automatically boot.
Will take some minutes... ( prepare a coffee )
Set up your phone and look forward for updates...
If all will take right direction, new update will completely lock the bootloader
and at the reboot no yellow or red lines will appears. :fingers-crossed:
Voilà, complete stock with latest firmware.
Take your coffee and enjoy :laugh:
Best regards
P.S.: Remove or obscure the screenshot with imei codes ( it's sensitive datas )
Click to expand...
Click to collapse
Hi there
Hey didn't know about the IMEI codes, already deleted the picture.
I did as you said and my phone is fully stock now (no red or yellow letters) and the ads are back ,anyway thank you so much for your patience and time for helping me out.
I really appreciated your help, take care and see you around. :victory:
fr4nk32 said:
Hi there
Hey didn't know about the IMEI codes, already deleted the picture.
I did as you said and my phone is fully stock now (no red or yellow letters) and the ads are back ,anyway thank you so much for your patience and time for helping me out.
I really appreciated your help, take care and see you around. :victory:
Click to expand...
Click to collapse
Ok i'm glad to see that worked..
I wish to thank in a special way Firmware Finder TEAM that with their
programs gave us the chance to solve many problems, THX guys. :good:
See you

Categories

Resources