Related
Hello,
Ive got a phone from a customer saying it wont boot up, also said he just OTAed, It only enter bootloader mod (stuck on black screen when trying yo enter recovery).
It also says Secure Boot - enable
and I cant flash anything of course , What can I do to boot it up ?
is his bootloader unlocked?
---------- Post added at 01:09 PM ---------- Previous post was at 01:08 PM ----------
try and use this https://developers.google.com/android/nexus/images
---------- Post added at 01:09 PM ---------- Previous post was at 01:09 PM ----------
try and use this https://developers.google.com/android/nexus/images
theyau said:
is his bootloader unlocked?
---------- Post added at 01:09 PM ---------- Previous post was at 01:08 PM ----------
try and use this https://developers.google.com/android/nexus/images
---------- Post added at 01:09 PM ---------- Previous post was at 01:09 PM ----------
try and use this https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Its always locked, if I unlock the bootloader its automatically re-locking after reboot
Bump
any one has any idea please ?
deadwolf666 said:
Hello,
Ive got a phone from a customer saying it wont boot up, also said he just OTAed, It only enter bootloader mod (stuck on black screen when trying yo enter recovery).
It also says Secure Boot - enable
and I cant flash anything of course , What can I do to boot it up ?
Click to expand...
Click to collapse
Secure boot is enabled on all Nexus 4's, and you cannot disable it. By the way, Secure boot has nothing to do with the lock state of the bootloader -- it has to do with the secure boot chain of the AQP8064 chipset.
Unlock the booloader using "fastboot oem unlock" and then flash the factory images. See here.
If simply flashing factory images, an unlock should not be necessary. Is customer wanting you to try and preserve data?
efrant said:
Secure boot is enabled on all Nexus 4's, and you cannot disable it. By the way, Secure boot has nothing to do with the lock state of the bootloader -- it has to do with the secure boot chain of the AQP8064 chipset.
Unlock the booloader using "fastboot oem unlock" and then flash the factory images. See here.
Click to expand...
Click to collapse
Thanks for the answer but the wierd problem is that after I unlock the bootloader and try to flash any thing I get":
sending 'bootloader' (2188 KB)... FAILED (command write failed (Unknown error))
Click to expand...
Click to collapse
and after I reboot it shows that the bootloader is locked
I managed to boot into twrp recovery but no screen by "fastboot boot recovery.img" and I get adb access.
ant thing I can do from here ?
deadwolf666 said:
I managed to boot into twrp recovery but no screen by "fastboot boot recovery.img"
Click to expand...
Click to collapse
You are seeing a black screen because you are not using the correct command. It should be: fastboot -c "lge.kcal=0|0|0|x" boot recovery.img
efrant said:
You are seeing a black screen because you are not using the correct command. It should be: fastboot -c "lge.kcal=0|0|0|x" boot recovery.img
Click to expand...
Click to collapse
Thank you it helped abit
now I tryed twrp and it asked me for decryd pass, and cant mount any partition.
cwm can sideload but wipe will give errors (cant mount) and after reboot the bootloader is locked againg and wont boot.
stock just reboots.
can it be HW ? or any other solution ?
btw where did you learend this switch and where can I read about it ? "lge.kcal=0|0|0|x"
Thanks again
deadwolf666 said:
Thank you it helped abit
now I tryed twrp and it asked me for decryd pass, and cant mount any partition.
cwm can sideload but wipe will give errors (cant mount) and after reboot the bootloader is locked againg and wont boot.
stock just reboots.
can it be HW ? or any other solution ?
btw where did you learend this switch and where can I read about it ? "lge.kcal=0|0|0|x"
Thanks again
Click to expand...
Click to collapse
Two options before we decide it's hardware.
Procedure #1:
1) Download the LATEST version of fastboot.exe from here and extract it to C:\android.
2) Download the latest factory image from Google's dev page and verify the checksum with what is posted on the website.
3) Extract all the images from all the .tgz, .tar, .zip files within and put the 6 image files in C:\android
4) Reboot your device into the bootloader and plug into your PC.
5) Open a command prompt in that same directory and type the following commands:
Code:
fastboot oem unlock
fastboot reboot-bootloader
fasltboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
Does that work? If so then continue with flashing the radio, boot, system and recovery images. If not, then go to procedure number 2:
Procedure #2
Follow the instructions in this thread.
deadwolf666 said:
btw where did you learend this switch and where can I read about it ? "lge.kcal=0|0|0|x"
Thanks again
Click to expand...
Click to collapse
Have a look here.
efrant said:
Two options before we decide it's hardware.
Procedure #1:
1) Download the LATEST version of fastboot.exe from here and extract it to C:\android.
2) Download the latest factory image from Google's dev page and verify the checksum with what is posted on the website.
3) Extract all the images from all the .tgz, .tar, .zip files within and put the 6 image files in C:\android
4) Reboot your device into the bootloader and plug into your PC.
5) Open a command prompt in that same directory and type the following commands:
Code:
fastboot oem unlock
fastboot reboot-bootloader
fasltboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
Does that work? If so then continue with flashing the radio, boot, system and recovery images. If not, then go to procedure number 2:
Procedure #2
Follow the instructions in this thread.
Have a look here.
Click to expand...
Click to collapse
Procedure #1 is not working I get FAILED command write failed unknown error
Procedure #2 I tryed a few times on different pc (also different OS) and never got the software to recognize the phone (any way Ill try again and update)
thanks for the link will read it soon ^^
Cant make the NPST recognize the phone ;\
while booting custom recovery I cant mount any partition and the bootloader remains locked after reboot.
Any thing else to try ?
I am looking for a clear explanation of how to flash Android 6.0.1 with root and encryption disabled without wiping data. With all the explanations through the forum, all the "if's" and "but's" get confusing and can be clear as mud. Thanks for your help.
i'm on 6.0 with a stock kernel with encryption disabled and an unlocked bootloader as well.
As far as i can tell you need 2 things.. Flash the System.IMG manually and then we need to wait for someone to post a modified stock 6.0.1 kernel that has encryption disabled too. you can get away with just flashing system.IMG and stay on your older 6.0 de encrypted kernel but I have seen online that wonky things happen when you dont stay up to date on your kernel sometimes.
I
nextelbuddy said:
i'm on 6.0 with a stock kernel with encryption disabled and an unlocked bootloader as well.
As far as i can tell you need 2 things.. Flash the System.IMG manually and then we need to wait for someone to post a modified stock 6.0.1 kernel that has encryption disabled too. you can get away with just flashing system.IMG and stay on your older 6.0 de encrypted kernel but I have seen online that wonky things happen when you dont stay up to date on your kernel sometimes.
I
Click to expand...
Click to collapse
I know there is a new boot.img file that has encryption disabled but I'm not sure how or where to install it properly.
how_to_flash_update_images_without_wiping_data
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
ShaunWinSC said:
I know there is a new boot.img file that has encryption disabled but I'm not sure how or where to install it properly.
Click to expand...
Click to collapse
Where did you find or see this new 6.0.1 modified boot.img that has encryption disabled?
all you need is wugfresh tool kit and go into the Advanced settings and choose to flash individual files. and flash the boot.img to your device.
so flash the 6.0.1 system.img first and then flash the 6.0.1 modified boot.img 2nd.
remember that when you flash anything from fastboot, after the item is finished, the device reboots so you need to watch the device and have your fingers prepared to hold down power and volume down so the device goes back into fastboot and doesnt start booting again on its own.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
Ovrclck said:
how_to_flash_update_images_without_wiping_data
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
Click to expand...
Click to collapse
that works too!
now just to find the modified 6.0.1 boot.img that has encryption disabled.
nextelbuddy said:
Where did you find or see this new 6.0.1 modified boot.img that has encryption disabled?
all you need is wugfresh tool kit and go into the Advanced settings and choose to flash individual files. and flash the boot.img to your device.
so flash the 6.0.1 system.img first and then flash the 6.0.1 modified boot.img 2nd.
remember that when you flash anything from fastboot, after the item is finished, the device reboots so you need to watch the device and have your fingers prepared to hold down power and volume down so the device goes back into fastboot and doesnt start booting again on its own.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
that works too!
now just to find the modified 6.0.1 boot.img that has encryption disabled.
Click to expand...
Click to collapse
Doughnut643 posted it in Android 6.0.1 thread, post #61.
https://www.dropbox.com/s/la4c6f8o5z...e-new.img?dl=0
It's been my understanding that Wug Fresh Tool Kit has been having some issues.
What about recovery, will it have to re-flashed? And what about root?
ShaunWinSC said:
Doughnut643 posted it in Android 6.0.1 thread, post #61.
https://www.dropbox.com/s/la4c6f8o5z...e-new.img?dl=0
It's been my understanding that Wug Fresh Tool Kit has been having some issues.
What about recovery, will it have to re-flashed? And what about root?
Click to expand...
Click to collapse
your recovery should remain as long as oy only flash the system.img and boot.img. you will need to reroot but I cant help you there unfortunately as I am not rooted myself since I need Androidpay to work.
i h avent had any issues with wugfrsh tool kit but if anything you dont have to use it. you can just go to the wugfresh tool kit folder and run the ADB and manually flash with the flash commands manually.
nextelbuddy said:
your recovery should remain as long as oy only flash the system.img and boot.img. you will need to reroot but I cant help you there unfortunately as I am not rooted myself since I need Androidpay to work.
i h avent had any issues with wugfrsh tool kit but if anything you dont have to use it. you can just go to the wugfresh tool kit folder and run the ADB and manually flash with the flash commands manually.
Click to expand...
Click to collapse
So you don't think I will need flash TWRP after flashing everthing.
I am hoping enough people chime in on how to do this so I can make a clear set of instructions.
I will let you know in a few min.
I just finished flashing 6.0.1 system.img, bootloader.img, cache.img, modified boot.img you posted and the device is at the android is upgrading screen.
if its successful, I will reboot into my recovery which had TWRP previously. if thats good i will let you know.
---------- Post added at 12:51 PM ---------- Previous post was at 12:18 PM ----------
ShaunWinSC said:
So you don't think I will need flash TWRP after flashing everthing.
I am hoping enough people chime in on how to do this so I can make a clear set of instructions.
Click to expand...
Click to collapse
so I have one problem now.
when My device fully boots up it now says :
"there's an internal problem with your device"
the only reference I can find to this is in regards to the Nexus 9 and flashing the Vendor.IMG file but nothing for phone devices.
any one know anything about this?
I h ave a feeling its because i flashed the stock 6.0.1 bootloader.IMG over my modified bootloader.IMG and I have TWRP installed AND a modified boot.img...
if i could find a new modified bootloader.img for 6.0.1 that would be awesome.
BTW my TWRP is still installed and launches fine.
nextelbuddy said:
I will let you know in a few min.
I just finished flashing 6.0.1 system.img, bootloader.img, cache.img, modified boot.img you posted and the device is at the android is upgrading screen.
if its successful, I will reboot into my recovery which had TWRP previously. if thats good i will let you know.
---------- Post added at 12:51 PM ---------- Previous post was at 12:18 PM ----------
so I have one problem now.
when My device fully boots up it now says :
"there's an internal problem with your device"
the only reference I can find to this is in regards to the Nexus 9 and flashing the Vendor.IMG file but nothing for phone devices.
any one know anything about this?
I h ave a feeling its because i flashed the stock 6.0.1 bootloader.IMG over my modified bootloader.IMG and I have TWRP installed AND a modified boot.img...
if i could find a new modified bootloader.img for 6.0.1 that would be awesome.
BTW my TWRP is still installed and launches fine.
Click to expand...
Click to collapse
Have u flashed vendor.img ???
That's probably the problem :silly:
kauemelhado said:
Have u flashed vendor.img ???
That's probably the problem :silly:
Click to expand...
Click to collapse
I did not. i thought that was only for the nexus 9 since the toolkit had that button disabled unless I set my device to Nexus 9. i flashed vendor.IMG and good to go now thanks lol
nextelbuddy said:
I did not. i thought that was only for the nexus 9 since the toolkit had that button disabled unless I set my device to Nexus 9. i flashed vendor.IMG and good to go now thanks lol
Click to expand...
Click to collapse
I saw a yt video today (https://www.youtube.com/watch?v=i6Gpi1ruLgM)
He showed that if you don't flash vendor.img, you'll get this error message
kauemelhado said:
I saw a yt video today (https://www.youtube.com/watch?v=i6Gpi1ruLgM)
He showed that if you don't flash vendor.img, you'll get this error message
Click to expand...
Click to collapse
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!
I have flashed these three Files via the readme commands(fastboot flashing) and did not have my data partition wiped. and now FC's on ubermallow custom rom.
nextelbuddy said:
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!
Click to expand...
Click to collapse
Some people are having this problem with EX kernel. But I guess the kernel is not the problem.
I'll flash the update later on today, then i'll tell you how that work for me hehe
nextelbuddy said:
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!
Click to expand...
Click to collapse
I flashed all the imgs last night (had some troubles with being dumb installing twrp :silly:
But other than that, everything works perfeclty. LTE is fine. (here in brazil at least)
I'm currently on Stock 6.0.1 + EX Kernel + SuperSu 2.61
kauemelhado said:
I flashed all the imgs last night (had some troubles with being dumb installing twrp :silly:
But other than that, everything works perfeclty. LTE is fine. (here in brazil at least)
I'm currently on Stock 6.0.1 + EX Kernel + SuperSu 2.61
Click to expand...
Click to collapse
Nice, how did you made it? Did you leave the recovery.img?
Martini3001 said:
Nice, how did you made it? Did you leave the recovery.img?
Click to expand...
Click to collapse
I flashed stock recovery and later on flashed twrp.
I was getting the android of death when booting into TWRP.
So, I did this:
-fasboot flash recovery *twrp*
-fastboot reboot-bootloader
*on your fone* using the volume buttons search for "RECOVERY"
-boot into recovery
-thank me!
lololol
I am facing the same problem. After flashing the files manually as below -
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
I rebooted the phone into bootloader and flashed TWRP. After flashing I could boot into TWRP, but if I reboot and try to boot into TWRP little android guy appears.
What am I doing wrong?
MPAI said:
I am facing the same problem. After flashing the files manually as below -
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
I rebooted the phone into bootloader and flashed TWRP. After flashing I could boot into TWRP, but if I reboot and try to boot into TWRP little android guy appears.
What am I doing wrong?
Click to expand...
Click to collapse
after you flash TWRP, if you reboot, the system will flash the stock recovery back if its not the original
after u flash TWRP, u need to boot into recovery, and then flash the expected SuperSU.zip
the supersu zip script will edit the system and disable the flashing of stock recovery
Hello all,
Does anyone know how to update the 6P to the latest April 2016 security patch with TWRP?
Can I flash with the nexus factory image from google server?
Thanks.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Section 9 - change names of files to the latest version.
manikandanguru said:
Hello all,
Does anyone know how to update the 6P to the latest April 2016 security patch with TWRP?
Can I flash with the nexus factory image from google server?
Thanks.
Click to expand...
Click to collapse
Flash the System.img and Vendor.img from the April Factory Image, through TWRP.
DJBhardwaj said:
Flash the System.img and Vendor.img from the April Factory Image, through TWRP.
Click to expand...
Click to collapse
brichardson1991 said:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Section 9 - change names of files to the latest version.
Click to expand...
Click to collapse
Thanks for the suggestions.
Can I flash all the images mentioned by Heisenberg through TWRP or I should only do it in CMD?
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
like this
I am gonna try it any way. I am downloading it and will report it later.
Thanks again.
manikandanguru said:
Thanks for the suggestions.
Can I flash all the images mentioned by Heisenberg through TWRP or I should only do it in CMD?
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
like this
I am gonna try it any way. I am downloading it and will report it later.
Thanks again.
Click to expand...
Click to collapse
You can flash boot.img, system.img, and vendor.img
Bootloader, Radio, and Cache.img needs to be flashed via fastboot, in bootloader mode.
DJBhardwaj said:
You can flash boot.img, system.img, and vendor.img
Bootloader, Radio, and Cache.img needs to be flashed via fastboot, in bootloader mode.
Click to expand...
Click to collapse
Yeah,
Done it by what you have said.
Thank you so much. Now my 6P is upgrading
I will follow this procedure in future update. :good::good:
manikandanguru said:
Yeah,
Done it by what you have said.
Thank you so much. Now my 6P is upgrading
I will follow this procedure in future update. :good::good:
Click to expand...
Click to collapse
Good to know. And all the best for future upgrades.
hello All upgraded how do i root again now safely?
sunandoghosh said:
hello All upgraded how do i root again now safely?
Click to expand...
Click to collapse
You just need to flash the latest SuperSU through TWRP: BETA-SuperSU-v2.71-20160331103524.zip
DJBhardwaj said:
You just need to flash the latest SuperSU through TWRP: BETA-SuperSU-v2.71-20160331103524.zip
Click to expand...
Click to collapse
thank you so after up gradation do i have still TWRP or i need to first install twrp?
---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------
DJBhardwaj said:
You just need to flash the latest SuperSU through TWRP: BETA-SuperSU-v2.71-20160331103524.zip
Click to expand...
Click to collapse
Need one more help...should i go for systemless root (not sure If i know if and how to do it) or normal root?
Also am i correct to understand that now that i flashed flash recovery recovery.inmg as part of upgrade the TWRP recovery is gone and I am on stock recovery?
sunandoghosh said:
thank you so after up gradation do i have still TWRP or i need to first install twrp?
Click to expand...
Click to collapse
How did you update? And did you had TWRP prior the upgrade?
Sent from my Nexus 6P using XDA-Developers mobile app
---------- Post added at 04:11 PM ---------- Previous post was at 03:59 PM ----------
sunandoghosh said:
thank you so after up gradation do i have still TWRP or i need to first install twrp?
---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------
Need one more help...should i go for systemless root (not sure If i know if and how to do it) or normal root?
Also am i correct to understand that now that i flashed flash recovery recovery.inmg as part of upgrade the TWRP recovery is gone and I am on stock recovery?
Click to expand...
Click to collapse
If you upgraded through the regular OTA method or by sideloading, you must be having stock recovery. Now, to install TWRP, you will need the latest image file from here:https://twrp.me/devices/huaweinexus6p.html
Boot your 6P into bootloader mode, and flash using the following command:
Code:
fastboot flash recovery twrp-3.0.2-0-angler.img
As about Systemless/System root, the installer itself goes for the systemless method, and if somehow the requirements fail, it will install to system.
sunandoghosh said:
thank you so after up gradation do i have still TWRP or i need to first install twrp?
---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------
Need one more help...should i go for systemless root (not sure If i know if and how to do it) or normal root?
Also am i correct to understand that now that i flashed flash recovery recovery.inmg as part of upgrade the TWRP recovery is gone and I am on stock recovery?
Click to expand...
Click to collapse
Yes, if you flashed the recovery.img as part of the update you'll need to flash TWRP again. Just use systemless SuperSU.
do i have to compulsorily flash twrp or can i boot temporarily?
sunandoghosh said:
do i have to compulsorily flash twrp or can i boot temporarily?
Click to expand...
Click to collapse
You can live-boot it instead of flashing it to the device. Where the filename of the recovery is twrp-3.0.2-0-angler.img, the command would be this:
Code:
fastboot boot twrp-3.0.2-0-angler.img
This is my first time posting on XDA, so sorry if the formatting is bad.
I've tried to root my P9 lite installing TWRP and Magisk, everything went fine, until the last reboot that caused a bootloop.
Trying to fix this I mistakenly wiped the System partition (instead of Data), reading online people adviced to flash the update.zip, when i tried it I had "unable to mount /vendor" and "unable to mount /product".
I tried the update.app method and the eRecovery tool, but still nothing.
I read that the problem was probably caused by en error in boot.img or recovery.img, so i extracted those files from the firmware and flashed them using TWRP. By doing so i deleted TWRP itself leaving me unable to flash system.img.
I tried to flash it using fastboot, but every time i try to write a command regarding flashing i get a FAILED (remote: command not allowed).
Now i have a bricked phone, i can access fastboot but it doesnt seem to be working. I cant access adb since i can't access the recovery (at least i dont know how to ).
Any advices?
Do you have bootloader unlock code?
Dino_S said:
Do you have bootloader unlock code?
Click to expand...
Click to collapse
Yes I do.
Unlock bootloader again and in fastboot flash system.img and boot from firmware,I used b370
---------- Post added at 12:46 AM ---------- Previous post was at 12:38 AM ----------
Extract from update.zip file update.app and use huawei update extractor and extract files from that system.img and boot.img and put in fastboot folder and flash it
Dino_S said:
Unlock bootloader again and in fastboot flash system.img and boot from firmware,I used b370
---------- Post added at 12:46 AM ---------- Previous post was at 12:38 AM ----------
Extract from update.zip file update.app and use huawei update extractor and extract files from that system.img and boot.img and put in fastboot folder and flash it
Click to expand...
Click to collapse
I can't, whenever I try using a fastboot command I get "FAILED (remote: command not allowed)
How much is internal data memory in twrp
Dino_S said:
How much is internal data memory in twrp
Click to expand...
Click to collapse
Around 10 gb, by the way I can't access twrp anymore, since I flashed recovery.img
TinkyWinkyJr said:
Around 10 gb, by the way I can't access twrp anymore, since I flashed recovery.img
Click to expand...
Click to collapse
It is showing in fastboot mode unlocked both
Dino_S said:
It is showing in fastboot mode unlocked both
Click to expand...
Click to collapse
Bootloader unlocked and FPR locked (or is it FRP?)
I have same prob yesterday,and showing me same thing,but i flashed twrp again and format data and system to ext4,and from fastboot flash system and boot img and it booted,it is confusing to undestand yours problem
---------- Post added at 01:15 AM ---------- Previous post was at 01:14 AM ----------
TinkyWinkyJr said:
Bootloader unlocked and FPR locked (or is it FRP?)
Click to expand...
Click to collapse
Mine showing FRP unlocked
hey guys
i have the same problem, had rr marshmallow on my p9 lite and tried to flash the new recovery for nougat by old droid. since then i cant enter nowhere without fastboot. phone unlocked and frp unlocked. does anybody have another idea. flashing stock recovery did not work, flashing twrp did also not work. need more ideas, erecovery and dload method do not work, i have acces to fastboot
Try to flash the correct oem.info.I've had the same problem with my P9(EVA-L09).
Hello I wanted to install Oreo on my PRA-LX1 following this guide
https://www.haky86.com/2018/05/12/install-emui-8-0-huawei-p8-lite-2017/
I was on official EMUI Nougat firware, I downloaded LX1C432B322 of 2018.04.13 what he said, installed nocheck recovery and then update_command. Reboot, title, nothing works except fastboot. I re-unlocked the phone with oem unlock and after reboot same.
I tried to flash twrp-3.2.1-v3.5-prague.img again to fix but length error with "fastboot flash recovery"
I tried to flash his OreoTWRP.img with "fastboot flash recovery_ramdisk" and it pass, reboot but I can't boot to recovery.
Pressing VolUp + Power does nothing, "phone can't be trusted" screen with the eRecovery option (VolUp for 3 seconds) but eRecovery is dead (error mode)
Maybe this OreoTWRP worked but how to bot to recovery now ?
please help I can't buy another phone it's urgent...
p181153 said:
Hello I wanted to install Oreo on my PRA-LX1 following this guide
https://www.haky86.com/2018/05/12/install-emui-8-0-huawei-p8-lite-2017/
I was on official EMUI Nougat firware, I downloaded LX1C432B322 of 2018.04.13 what he said, installed nocheck recovery and then update_command. Reboot, title, nothing works except fastboot. I re-unlocked the phone with oem unlock and after reboot same.
I tried to flash twrp-3.2.1-v3.5-prague.img again to fix but length error with "fastboot flash recovery"
I tried to flash his OreoTWRP.img with "fastboot flash recovery_ramdisk" and it pass, reboot but I can't boot to recovery.
Pressing VolUp + Power does nothing, "phone can't be trusted" screen with the eRecovery option (VolUp for 3 seconds) but eRecovery is dead (error mode)
Maybe this OreoTWRP worked but how to bot to recovery now ?
Click to expand...
Click to collapse
I'm not responsible of bricks caused by people since most of them not follow the steps I wrote.
@haky 86 (I'm assuming you were the one who wrote that guide) is the guide for updating from nougat to oreo or updating an Oreo firmware to the latest?
haky 86 said:
I'm not responsible of bricks caused by people since most of them not follow the steps I wrote.
Click to expand...
Click to collapse
Tell me where I said you are responsible of bricks ? I followed the steps you described, If you don't want to help just don't say anything
neondragon1909 said:
@haky 86 (I'm assuming you were the one who wrote that guide) is the guide for updating from nougat to oreo or updating an Oreo firmware to the latest?
Click to expand...
Click to collapse
This is I want to know. He don't said it but I tried to flash oreotwrp from nougat and it said partition error using recovery_ramdisk. And the nocheck didn't work, so I took another nocheck for this TWRP and put the update_package command and then this
I just update my guide, the sample I wrote it was emui 8.x because I'm already at oreo. but procedure is same the only thing change is recovery, on oreo called Recovery Ramdisk on nougat called just recovery, please check the updated article here the screenshot.
haky 86 said:
I just update my guide, the sample I wrote it was emui 8.x because I'm already at oreo. but procedure is same the only thing change is recovery, on oreo called Recovery Ramdisk on nougat called just recovery, please check the updated article here the screenshot.
Click to expand...
Click to collapse
Ok thanks but now I can't do anything on my phone I just have bootloader. How to restore a device which is bricked followed a bad update
p181153 said:
Ok thanks but now I can't do anything on my phone I just have bootloader. How to restore a device which is bricked followed a bad update
Click to expand...
Click to collapse
Download the nougat rom you were on before. Extract update.app to get the recovery. Flash it using fastboot. Then try dload method.
Or flash nougat twrp and try flashing the nougat rom via HuRUpdater
neondragon1909 said:
Download the nougat rom you were on before. Extract update.app to get the recovery. Flash it using fastboot. Then try dload method.
Or flash nougat twrp and try flashing the nougat rom via HuRUpdater
Click to expand...
Click to collapse
Thanks any detailled guides for that so I'll not make the things worst ?
neondragon1909 said:
Download the nougat rom you were on before. Extract update.app to get the recovery. Flash it using fastboot. Then try dload method.
Or flash nougat twrp and try flashing the nougat rom via HuRUpdater
Click to expand...
Click to collapse
I can't flash recovery from update.app of nougat rom. It say partition length error. recovery_ramdisk say partition error...
Can I flash the system.img ? There are fastboot.img in the update.APP. Can I flash recovery after flashing fastboot ?
I need to be sure because if I flash fastboot and lost it my phone will be really dead
p181153 said:
I can't flash recovery from update.app of nougat rom. It say partition length error. recovery_ramdisk say partition error...
Can I flash the system.img ? There are fastboot.img in the update.APP. Can I flash recovery after flashing fastboot ?
I need to be sure because if I flash fastboot and lost it my phone will be really dead
Click to expand...
Click to collapse
Use recovery not recovery_ramdisk
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
p181153 said:
I can't flash recovery from update.app of nougat rom. It say partition length error. recovery_ramdisk say partition error...
Can I flash the system.img ? There are fastboot.img in the update.APP. Can I flash recovery after flashing fastboot ?
I need to be sure because if I flash fastboot and lost it my phone will be really dead
Click to expand...
Click to collapse
Use fastboot flash recovery recovery.img not recovery_ramdisk
neondragon1909 said:
Use recovery not recovery_ramdisk
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
Use fastboot flash recovery recovery.img not recovery_ramdisk
Click to expand...
Click to collapse
I can't flash recovery how to restore my phone using fastboot please
It's urgent if you don't know how to solve that at least tell who can do that I can't let my phone like that I miss everything
p181153 said:
I can't flash recovery how to restore my phone using fastboot please
It's urgent if you don't know how to solve that at least tell who can do that I can't let my phone like that I miss everything
Click to expand...
Click to collapse
Try unlocking bootloader again
neondragon1909 said:
Try unlocking bootloader again
Click to expand...
Click to collapse
bootloader is unlocked... read first post "re-unlocked" the bootloader... I need serious answers. Actually I download a nougat firmware and try this guide
And this guide tell me to extract 4 img files using Huawei Firmware Extractor. I downloaded 2 full OTA firmware and can't find cust.img files...
I just want to restore my phone...
p181153 said:
bootloader is unlocked... read first post "re-unlocked" the bootloader... I need serious answers. Actually I download a nougat firmware and try this guide
And this guide tell me to extract 4 img files using Huawei Firmware Extractor. I downloaded 2 full OTA firmware and can't find cust.img files...
I just want to restore my phone...
Click to expand...
Click to collapse
please help me can't restore my phone when I want to flash boot of a nougat firmware it say partition length error.....
when I want to flash recovery same...
I can't do anything I need my phone it's 3 days already I miss important calls...
This forum is called xda-developers but there are no developers or someone who really know how android works. I can't found anyone who can help me even on other forums. I have access to something which can save my phone but NOBODY know how to use it. How disapointing.
why