I unlocked my P8 Lite's bootloader today with the intention of moving from its current Asiapac ROM to the European ROM (both devices have no hardware differences, anyhow it shouldn't affect the issue I'm having).
I downloaded a complete C432B170 ROM, and used the Huawei Update Extractor Tool to extract the various system images from the update:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I then proceeded to flash the system.img and boot.img, and both appeared to flash properly, but however upon rebooting the device I have the exact same ROM!
Having flashed other devices previously in the same fashion with positive results, I downloaded a few other complete (aka, complete ROM) packages, with every one experiencing the same issue (one of them however did manage to downgrade the device from 5.0.1 to 5.0, so it must be doing something to it [this was after wiping the userdata and cache partitions]).
Further tries to flash the ROM have had the same result.
What am I doing wrong here?
How is the P8 Lite different to other Android devices (in respect of firmware flashing)?
Do I need to flash something else?
I thought that it could be that it's not actually letting me modify the partitions, but I am able to wipe /system in TWRP (yes, it did let me install a custom recovery, so that's working).
you need to flash cust.img and recovery.img too
PS:you will get balong error so you need to flash the B052 rom in the first place then flash the custom folder ( dload2 or step2 ) that comes with it to fix it, you may loose your IMEI but updating to B170 VIA OTA will fix it
AmINoS007 said:
you need to flash cust.img and recovery.img too
PS:you will get balong error so you need to flash the B052 rom in the first place then flash the custom folder ( dload2 or step2 ) that comes with it to fix it, you may loose your IMEI but updating to B170 VIA OTA will fix it
Click to expand...
Click to collapse
Did it, and upgraded to Marshmallow, cheers .
Yeah, I got the Balong build-number error, but the updater allowed me to upgrade to B188 and then to Marshmallow (it's only a build number so I'm not that bothered). Only bug I've found so far is with the settings panel, otherwise its great.
Only thing is, I now only have 2.5GB of storage on /system rather than ~10GB I had before; how can I fix this? This issue occurred after I flashed B170.
Looks like to me that the /system partition is only 2.56GB (perhaps the B170 ROM was from an 8GB variant of the device?).
Another issue that I've found is that I can't seem to root the device (flashing the SuperSu zip always causes a boot-loop, regardless of the version of SuperSu I use).
Will probably re-flash this weekend fixing the Balong build-number error and (hopefully) the /system partition's size).
Related
Hello everybody !
If you have downgraded from Lolipop to a KitKat ROM and you have issued black screen during call, I have find the solution:
You don't need to flash the Stock ROM. Just flash a Modem from a Stock ROM, Lolipop Modem doesn't work fine on KitKat, proximity sensor is busy and the screen don't wake up during call.
You can find here the latest Stock Modem (XNPH05Q) : MEGA | MediaFire
MD5 : 2fff2a1d9719294db84b714f4389ce6f
You don't need to wipe anything and it doesn't wipe anything. Just flash it and enjoy
Reserved
Can't get it to install with TWRP. When I try to do it, TWRP restarts. On reboot still get black screen on phone call. Is it indeed flashable from recovery?
Yay, of course, it's a flashable .zip, do you use the latest release of TWRP (2.8.6.X) ?
https://dl.twrp.me/bacon/
Mmh, I try to flash and it's works fine, here a screenshot :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ataft said:
Can't get it to install with TWRP. When I try to do it, TWRP restarts. On reboot still get black screen on phone call. Is it indeed flashable from recovery?
Click to expand...
Click to collapse
Then there's something wrong with the recovery or file. Try Calkulin's modem? If it fails again I think there is something wrong with your TWRP. Btw, you need to manually fastboot erase modem in order to flash the KK modem. Last time I tried it won't let me overwrite Lollipop modem with KK modem.
http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph05q-t3027033
I can overwrite LP modem with KK modem.
The flashable zip seems work fine on two OnePlus. I think it's his recovery who doesn't work
TWRP 2.8.6.0, haven't had any issues with it aside with this. Just tried flashing it, didn't know I needed to fastboot erase the LP modem.
Probably better it didn't work when I tried; made me go in search of a different rom I haven't tried yet [emoji51]
hello, i just tried to flash cloudyg2 3.3 and i have bricked my d802 16gb. i had stock lp and had rooted and installed twrp did the wipes (no internal), got the right lp bootstack and used the right settings, so i really dont know what went wrong.
the symptom is that lg logo show for a fraction of a second and then a washed out gray on top of screen that fades away slowly. also while connected in pc it reads like many many drives.
on the bright side i can enter recovery/download modes. in my original attempt i used the bumbed sign, on my tries to fix it i also used the loki one, same deal.
seems like i have no recovery file, i thought i did it with one of the programs i installed, but since i am newbie seems like i misunderstood. so no recovery file
any help?
solution found:
1.Download the latest TWRP from blastagator here.
2.Flash it with your current recovery, reboot into that new recovery.
3.Download SRKG2 rom (by somboons) here.
4.This rom is a full stock rom with some debloat and custom camera. Wipe /system/ /cache/ /dalvik-cache/ /data/ and flash it (choose any options, it's not important since you'll be only installing this rom because it also upgrades other partitions to a lollipop supported version.
5.Boot into the rom and reboot into recovery again. (If you are unable to boot or the boot is taking too long like 10 minutes, shut down, go to recovery again and perform a factory reset, the one that makes you type 'yes' in the keyboard and you should be fine).
6.Download CloudyG2 3.1 and wipe /system/ /cache/ /dalvik-cache/ /data/ again.
7.Flash the rom choosing the correct version of your phone (among other preferences) in the aroma installer.
8.Boot and enjoy!
i cant post link of the solution cause i am new, but many thanks to him. i still dont understand what went wrong, but my hypothesis is that i shouldnt install the lp bootloader since i was in lp anyway.
i hope it helps anyone with similar problem.
cheers
you are in qhsusb bulk 9006 souse srktool to unbrick
---------- Post added at 07:22 AM ---------- Previous post was at 07:20 AM ----------
that becuase wrong bootleader u must use bump kk bootleader then reboot recovery and flash rom
Can not change lte to 3g can someone please...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-D800 using Tapatalk
Saw many post from new users and senior members as well and most of the time there are lot of confusion on the OTA part, especially for the rooted phone. Few says it gets (I am one of them) and few says it doesn’t as rooting capabilities modifies the system boot.img and also we have unlocked bootloader so device wont get the OTAs. I have been using the Huawei/Honor phones for 2 years now and have been getting all the OTAs on rooted phone and confirmed the same many time but still there are lot of confusion and users thinks they wont get OTA on rooted phone.
Just confirming here that you will receive OTAs on rooted phone without any issues. This is 2nd update on my phone since rooted in past 2 months.
To show root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To show the update received
Note- I am not using any firmware finder or other things for this as I dont trust on FF as it messed my Honor 5C in February and I given up on it.
Instructions-
If you are rooted but then rolled back to stock recovery, just download the OTA and update.
If you are rooted with TWRP recovery, flash the stock recovery first and then download the OTA to update. (TWRP wont be able to update OTA)
That’s a good claim and for others/your satisfaction, I have checked it out. My honor 6x was already on B371 but it was having problem of themes and FM Radio, so I decided to root it and flash twrp, after which I flashed the B360 recovery and than again twrp and installed Flashfire. I also flashed the second zip file of B360 and it gave me the solution of FM radio and themes problem.
When I checked for updates there was the same B371 but after successful download it didn’t install due to the TWRP recovery.
Now the problem is what to do with the OTA update if you can’t flash it, I have also tried the Flashfire way of flashing because Flashfire automatically detects the OTA but it gives a warning that modified partitions may cause failed installation. Therefore I haven’t tried to flash the OTA.
So the question again here is what’s good in a OTA if you can’t flash it, yah that’s an other thing that you would know you have an OTA and you can’t flash until you go back to stock recovery.
Sent from my iPhone using Tapatalk
Hi All,
I'm a Huawei P8Lite 2017 PRA-LX1 user and I've had Android 9.0 AOSPExtended ROM installed for months. Now I'd Like to downgrade to stock firmware (either Nougat or Marshmallow). I've followed a couple of guides and now i've rendered my phone unusable (bootloop). I have Askuccio's 3.2.2.-0 TWRP installed. The huawei firmware extractor method and flashing system, boot and recovery through fastboot seemed the best option. I can't seem to find the .zip firmware that has just the UPDATE file though.... anytime I try to extract UPDATE.APP it just gives me rubbish instead of the system, boot etc... sorry for posting here but I'm trying to do something about this now for couple of hours and im just frustrated. Is there anyone that could lead me through the process of downgrading that Custom Android 9.0 AOSPExtended to the stock Oreo or Nougat? I'm just really frustrated at this point so sorry. I've obviously searched through the forum to no avail... all the guides for un-bricking are for people that are on stock and not on 9.0 Pie. I can't even seem to get my phone connected to HiSuite (even after enabling ADB debugging). It just tries to install the software on my phone forever in a bootloop. Probably can't install cause I'm on that Android Pie. I could possibly just get away with a firmware that when I extract in Huawei Firmware Extractor that it will actually give me the system, boot etc. in it. I could try stock recovery too, but the guides talk about a "dload" folder and when I extract any firmware (update.zip, update_data.zip or HW_ru.zip) that "dload" folder is never there... The picture below is from a update.zip file. Let me know if I need the whole 3 files (update.zip, update_data_full_public.zip and update_full_PRA-L31HN_hw_ru.zip). Do I even need anything from the below image? As you can see there is no boot.img or recovery.img either..... Please advise.
Thanks for any suggestions in advance, I can provide more info if someone needs.
Thanks in Advance...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nevermind, I've finally figured it out. Found a site with firmwares that actually have the "dload" folder in them. Recovered my phone to Stock Oreo. Thread can be closed.
Hi All,
I'm a Huawei P8Lite 2017 PRA-LX1 user and I've had Android 9.0 AOSPExtended ROM installed for months. Now I'd Like to downgrade to stock firmware (either Nougat or Marshmallow). I've followed a couple of guides and now i've rendered my phone unusable (bootloop). I have Askuccio's 3.2.2.-0 TWRP installed. The huawei firmware extractor method and flashing system, boot and recovery through fastboot seemed the best option. I can't seem to find the .zip firmware that has just the UPDATE file though.... anytime I try to extract UPDATE.APP it just gives me rubbish instead of the system, boot etc... sorry for posting here but I'm trying to do something about this now for couple of hours and im just frustrated. Is there anyone that could lead me through the process of downgrading that Custom Android 9.0 AOSPExtended to the stock Oreo or Nougat? I'm just really frustrated at this point so sorry. I've obviously searched through the forum to no avail... all the guides for un-bricking are for people that are on stock and not on 9.0 Pie. I can't even seem to get my phone connected to HiSuite (even after enabling ADB debugging). It just tries to install the software on my phone forever in a bootloop. Probably can't install cause I'm on that Android Pie. I could possibly just get away with a firmware that when I extract in Huawei Firmware Extractor that it will actually give me the system, boot etc. in it. I could try stock recovery too, but the guides talk about a "dload" folder and when I extract any firmware (update.zip, update_data.zip or HW_ru.zip) that "dload" folder is never there... The picture below is from a update.zip file. Let me know if I need the whole 3 files (update.zip, update_data_full_public.zip and update_full_PRA-L31HN_hw_ru.zip). Do I even need anything from the below image? As you can see there is no boot.img or recovery.img either..... Please advise.
Thanks for any suggestions in advance, I can provide more info if someone needs.
Thanks in Advance...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nevermind, I've finally figured it out. Found a site with firmwares that actually have the "dload" folder in them. Recovered my phone to Stock Oreo. Thread can be closed.