Hi all,
Quick backstory: I bought a Google Pixel 5a (from the USA) for my cousin who lives in India. The phone was working fine for him until about a few weeks ago when the phone was stuck in a boot loop. Unfortunately, my cousin did not have USB Debugging on and the OEM is locked.
I was able to help my cousin adb sideload the latest Full OTA update. The install completed successfully but when we try to restart the device, the phone bootloops once again. If we leave the phone to continue bootlooping, it gets very hot (which seems obvious but wanted to share this as well).
I cannot think of any other steps to take and it feels like this is a hardware driven issue. Worse yet, since my cousin is in India, we cannot service the phone. Posting here to see if anyone else has had a similar issue and was able to figure out what it was. Any advice helps, thanks!
did you try to extract the payload.bin to get the boot.img file and flash it to slots a & b .i think you can do that with twrp. with the bootloader you might not be able to do that.
Related
Hi,
So I wanted to prepare my unlocked Nexus 6 on T-mobile for my brother by completely un-rooting and then relocking to setup stock firmware. With the help of “Nexus Root Toolkit” it was a quick update. I simply picked up the latest firmware for t-mobile, then relocked - and off you go.
The Phone was ok for couple of days, but then google pushed new update – which would render my phone useless. After update Initially the phone went through the boot almost to the end, and then exception happened. Something about system UI crashing and then screen was unavailable. So I could not do anything on the phone.
I tried fixing with “Nexus Root Toolkit” (unlocking, rooting etc.), but at this point the phone is stock on booting (few colored dots signifying loading), but the phone never actually boots. Going to Factory reset or Recovery does nothing.
Is there anything else I can try please?
Thanks,
-Mariusz
keinam.ty said:
Hi,
So I wanted to prepare my unlocked Nexus 6 on T-mobile for my brother by completely un-rooting and then relocking to setup stock firmware. With the help of “Nexus Root Toolkit” it was a quick update. I simply picked up the latest firmware for t-mobile, then relocked - and off you go.
The Phone was ok for couple of days, but then google pushed new update – which would render my phone useless. After update Initially the phone went through the boot almost to the end, and then exception happened. Something about system UI crashing and then screen was unavailable. So I could not do anything on the phone.
I tried fixing with “Nexus Root Toolkit” (unlocking, rooting etc.), but at this point the phone is stock on booting (few colored dots signifying loading), but the phone never actually boots. Going to Factory reset or Recovery does nothing.
Is there anything else I can try please?
Thanks,
-Mariusz
Click to expand...
Click to collapse
There's not much you can do here. If you don't have TWRP or unlocked bootloader, you should just RMA the device direct through Motorola.
You could try to sideload the update you had received that caused this.
Other than that, RMA.
I was hoping not to hear RMA - but thanks for the reply.
Can someone please help. I'm getting desperate now. I flashed a Nougat build a little while ago but had some issues with Bluetooth and NFC so I flashed back to the original firmware using the dload folder and 3 button method. The installation seemed to go through fine but get's stuck booting at the vodafone logo. It then takes me into eRecovery where it attempts to download latest version over wifi but fails. I don't really know where to go from here because I can't access the internal sd card because the phone won't boot. I can access fastboot but don't really know what to do from there.
stevemacer10 said:
Can someone please help. I'm getting desperate now. I flashed a Nougat build a little while ago but had some issues with Bluetooth and NFC so I flashed back to the original firmware using the dload folder and 3 button method. The installation seemed to go through fine but get's stuck booting at the vodafone logo. It then takes me into eRecovery where it attempts to download latest version over wifi but fails. I don't really know where to go from here because I can't access the internal sd card because the phone won't boot. I can access fastboot but don't really know what to do from there.
Click to expand...
Click to collapse
Stevemacer10 Hello, I hope to be keen to help, because it happened to me the same thing, with two days of stomach ache for it. In wanting to load Android on my Nougat Huawei P9 Plus VIE-C02, with VIE-L09C605B354 and VIE-L29C185B320 I went into semi-brick or brick, or was only in bootloader, the screen with the green man to speak. No avail various ways, including via microSD-Fastboot or ADB to do restart your phone. Then, to my previous experience with a Huawei tablet, I logged on to the 'https://www.dc-unlocker.com/' site, and essend already registered, I bought 15 credits (15 Euros), for the 'option' DC Phoenix Firmware write ', valid for 72 hours, in addition to the program and downloaded the' DC program Phonix v29 '(https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial) following the related tutorial. Obviously procured the original firmware 'VIE-L09C02B133' or even lower versions, you'll have to unpack in a folder of your preference. Unfortunately, despite having used with DC Phoenix the original firmware was always also blocked me. At that point I wanted groped with a firmware that you can find on the same site of the DC-Unlocker (https://files.dc-unlocker.com/user.html?v=files/57694006a60d7) by downloading the firmware 'VIE_AL10B_M00A063_Factory_firmware_China_Nonspecific_Android_6.0_EMUI_4.1 .dgtks', which I loaded with DC-Phoenix on the phone. Rebooting of a minimal mode of andorid, I did not see well either. I went back into bootloader, as well as devone be made the previous steps that I have already described to you, and this time with DC-Phoenix I loaded on the phone firmware L09C02B128 and everything went well. Attention and keep in mind that just as I happened to me, the serial number of your phone is changed, to me has happened in '0123456789ABCDEF' and there was no way to change it, so as, while having the unlocked bootloader can not longer charge the TWRP recovery in order to then have root permissions. Until reading the paragraph '(Optional) Phone numbers REPAIR', I went to that point on the site 'http://hcu-client.com/'. Also here are sadly bought 8 credits (8,00 Euro) in order to work with the program 'HCU-Client v1.0.0.0115', you need to download and unpack, then follow the various instructions, which are not difficult when you have to be walked through the modding, otherwise you do even more damage. Let me know what you did and how it went to the method. I hope also good for you. In summary we want Euro 15 for Phoenix whose duration of operations applies to 72 hours and 8 Euro per HCU-Client, it can only use this for 24 hours.
P.S .: Obviously if you follow my instructions and all these signs you do so at your own risk, esonerandomi from every possible and accidental deterioration of the situation and the damage to your phone. Sorry for my English, whose translation has made Google translator.
---------- Post added at 12:59 AM ---------- Previous post was at 12:33 AM ----------
I wanted to say that the change of the serial number does not work well. The serial number has been changed from what I've shown you above, but was not put one I added that I had from the sales box. I write support and maybe let you know what they tell me. See you soon.
Hi Grlshia,
Thanks for getting back to me. It's such a minefield playing with all these different regional variants. I have though, managed to get it completely fixed. I just gave in and took it into the local Vodafone store and fortunately there happened to be one of the tech experts in there that owned a P9. He took it off me and within about 5 minutes he had completely restored it. He told me he just did a factory reset by holding down vol+ and power. I'm sure I had tried this myself to no avail previously but that's what he said he did.
stevemacer10 said:
Hi Grlshia,
Thanks for getting back to me. It's such a minefield playing with all these different regional variants. I have though, managed to get it completely fixed. I just gave in and took it into the local Vodafone store and fortunately there happened to be one of the tech experts in there that owned a P9. He took it off me and within about 5 minutes he had completely restored it. He told me he just did a factory reset by holding down vol+ and power. I'm sure I had tried this myself to no avail previously but that's what he said he did.
Click to expand...
Click to collapse
Stevemacer10 hello, I'm glad you've solved the problem. Unfortunately I'm still fighting because, for now I can only and even to load its firmware, but if you want to try to load the TWRP recovery for later obtain root permissions, it always fails. From what seems to understand me and certainly due to the fact that the bootloader unlock code now is different from what I have, because as I told you the serial number has changed and if I request a new unlock code, it stops notiziandomi the procedure that there is inconsistency between this number and the IMEI. For now I do not know what to do and how to proceed. I hope that over time can still solve my problem. A good evening to you :good:
i'v been throw it
after updating my p9 plus with a firmware that is not sutable to my area
my phone restarted and ask for an account wich ok but the problem was that the software not working properly and missing a keyboard.
and will not go to recovery mode to try another software.
this sloved by downloading a sutable correct software and unzip it into an SD card folder (i create) called dload, then swich off the device and turn it back on while holding three bottons (power+v up+v down) 10 to 15 sec. and the phone directly read from the SD card and start updating a new firmwarw.
try it.
it success with me , hope it work wth u
Hi guys,
I've bought an P9 and wanted to get rid of the booting screen with the resellers logo.
So I thought I'd be smart, unlocked the device, flashed TWRP 3.1.1-1-eva.img onto it. Got an SuperSu-file and tried to install it...
I never got to experience the rooted version. Got stuck in a bootloop, somehow got out of it. Logged in, saw an green SuperSu-app, opend it and it saidthe device has to be rooted to use the device, ergo i failed to root it. [Forgot some steps here] and I found myself in another bootloop. A friendly guy suggested to flash these 2 files
[Link-Removed]update.zip
[Link-Removed]update_data_full_hw_eu.zip
which I did with dload. After that, I was still in a bootloop, but with WipeCache I was able to get myself back into my phone [hooraay].
The happyness-phase was a short, because i soon found out, that it doesn't have an keyboard (only googleVoice, should be fun to type in a wifi-password). Huawei-ID tab is also missing (usually located below Accounts), Update Phone, which was between Advanced Settings and About Phone is also missing, and bluetooth doesn't seem to work. That's when I noticed that I'm on NRD90M test-keys build.
After reading some threads here i downloaded rollback from huawei (for west-europe). Now I'm on C900B300 but all settings still missing.
Now I'm here crying for help.
Any suggestions? Please?
Ryan
You got to rebrand your phone.
movizdb said:
You got to rebrand your phone.
Click to expand...
Click to collapse
do you mean, that i have to put the bootlogo back into it?
could be a meanie to do, because it's a swiss brand and I don't think that there's a version here for me to use.
//or do an OEM-Flash, which worked
Hi. So I decided it was time to move to EMUI 9 and after looking at various posts on here I believe the easiest way was to you EMUI Flasher to flash the ROM (coming from 8.1 rooted).
The phone restarted and went to EMUI installer but after 10% or so I got an error. It asked if I wanted to go to erecovery or reboot the device (I think). As far as I was concerned it was only checked that the ROM was OK and hadn't installed anything so I selected reboot. Now the phone won't come on. I've tried holding the power button for an inordinate period of time but it's not happening.
Is there anything I can do?
EDIT - I've tried a different USB port on my PC and can see something in the device manager now ---- Kedacom USB Device > Android Bootloader Interface ---- which gives me a sliver of hope this can be fixed.
EDIT2 - I could send img files through fastboot all day (phone was recognised even though it wouldn't turn on) but couldn't fix this. Gave DC Phoenix a try but no luck there either. Think I've killed it.
EDIT3 - Just in case anyone ever comes across this. I tried below but nothing would work so I contacted someone on Telegram who said the only option was to open the phone up and short it out. No way I was attempting that so I eventually contacted Huawei UK and told them it had died during an update, never let on that it was MY fault! Anyway, they sent out a prepaid envelope to send to a their repair partner. I won't name them here but they have terrible reviews on Yelp so I was a bit apprehensive. I know the phone arrived with them last Friday as I checked the post tracking but I never heard anything from them. Today out of the blue my phone has come back to me in full working order, repaired under warranty! Considering there was only one thing I was really using root for and it was only a slight convenience, I think I'll just leave it as is.
Are you able to flash anything in fastboot?
Are you able to boot to recovery via fastboot? Disconnect the cable after you give the reboot recovery command in fastboot.
You may be able to flash each component of emui, system, vendor, oeminfo, kernel etc. Seems that it's missing most or all of it.
Bootloader sounds like it's intact.
Btw. The easiest way to update to emui would be to wait for an OTA from Huawei.
Personally I don't see a point, pie is not as efficient as Oreo nor does it have any features to merit an upgrade, in fact you would lose features (4k zooming, functional TWRP)
Most of the time I am the guy helping people out. This time I think I did something pretty dumb.
I have an old "beater" P9 plus that I was using as a casual gaming device. Most of the apps I was using were beginning to no longer be supported because for some reason the device NEVER updated. Any time I check for a possible update the phone stated it was up to date. After much searching I discovered that this device SHOULD have updated quite a few times.
I used firmware finder to find a supported update and the first one went somewhat unexpected. The firmware was downloaded and put in the correct folders but kept failing after 5%. I decided that the next thing to do was to find a cool rom and go through the process of unlocking and installing TWRP. I usually try to install the latest TWRP. This turned out not working at all so I went for an older version and it booted into TWRP, however it found the update and installed it!
I kind of wanted to keep it stock, but updated stock so I went for a bigger upgrade to Android 7 firmware. This only worked partially and (stupid and I know better) forgot to do a backup. I did not know that TWRP was gone and root was gone. The battery died and I rebooted like normal and there was a much improved interface. However, a good bit of stuff stopped working like bluetooth and the boot screen was in red stating the device can't be verified and ended up in something like a NOR905 test keys build. I did a backup, selected a downgrade package that was checked and "updated" to the downgraded firmware through Project Menu. It successfully stated it was 100% complete.
Now it is stuck on the boot screen for an unlocked device.
What works (or is possibly a good thing):
The hardware keys can get me to the bootloader (fastboot)
ADB recognizes the device is in fastboot
Phone is Unlocked
FRP is unlock
What doesn't work:
Everything else. All I have is fastboot and an unlocked bootloader. I can try to flash recovery but that never boots, it just stays suck on the recovery boot screen. The system will not boot at all.
UPDATE:
I broke down and spent the money to use the DC-Phoenix software to unbrick the phone. Several of the options for firmware did NOT work. The one file set that did work was to use this firmware:
VIE-L29_C900B101_Firmware_countryValue_Nonspecific_Android_6.0_EMUI4.1
Then use this as the customization:
update_data_C900B101_hw_default
The phone originally started out as VIE-L29C636B130. This changed it to VIE-L29C900B101 and is on EMUI 4.1 android version 6.
Now the fun part is going to see if I can find a version of TWRP that will work and see if I can root it. Maybe even try a custom ROM. We'll see though. The device is just an old beater for fun. But at least, she's not broken anymore. Guess I'll grab a beer and celebrate my "unbricked" device.