Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Liebaart said:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Click to expand...
Click to collapse
With fastboot method, unlock bootloader again. Flash recovery. Boot into recovery. Wipe system and boot. Flash stock boot IMG and recovery IMG. Power off. Use dload. Now you are in bootloop. When booting press vol up 3 seconds, on e-recovery press shutdown. Press and hold power and vol up. Go to stock recovery, do factory reset.
Sent from my NEM-L21 using Tapatalk
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Liebaart said:
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Click to expand...
Click to collapse
Power off, vol up+ power can you go to recovery?
Sent from my NEM-L21 using Tapatalk
Liebaart said:
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Click to expand...
Click to collapse
Post here IMEI+SN and i try to get you bootloader unlock code.
Thanks! I sent you a PM.
Anonda said:
Power off, vol up+ power can you go to recovery?
Click to expand...
Click to collapse
No, I can only get into fastboot when connected to a pc.
OK. gtdaniel was so kind to provide me with an unlock code. THANKS!
But, I don't seem te be able to use it...
I can put the phone in bootloader when connected to a pc. When I type "fastboot devices" I do get the correct serial number. But when I type "fastboot oem unlock 343...338" I get a FAILED (remote: command not allowed).
It seems this is because I never could allow OEM unlocking from the Android settings menu. But since my phone is bricked, I can not enter into that menu!
Does anybody know how to solve this??
Liebaart said:
OK. gtdaniel was so kind to provide me with an unlock code. THANKS!
But, I don't seem te be able to use it...
I can put the phone in bootloader when connected to a pc. When I type "fastboot devices" I do get the correct serial number. But when I type "fastboot oem unlock 343...338" I get a FAILED (remote: command not allowed).
It seems this is because I never could allow OEM unlocking from the Android settings menu. But since my phone is bricked, I can not enter into that menu!
Does anybody know how to solve this??
Click to expand...
Click to collapse
u can try with
VNS-L21-L22-L31 Toolkit or
SRKToolHuawei-Lod-Chong-V2.0-20161002
But i dont know is that good idea to listen to me anymore
Thanks, but the Toolkit says it can't find the device.
Liebaart said:
Thanks, but the Toolkit says it can't find the device.
Click to expand...
Click to collapse
at command line when u write adb devices u got your phone ?
Maybe is dump question but did you install adb android driver ?
I'm pretty sure that someone wrote in thread that you don't need to have this oem permission in android if you are in fastboot
dragon218 said:
at command line when u write adb devices u got your phone ?
Maybe is dump question but did you install adb android driver ?
I'm pretty sure that someone wrote in thread that you don't need to have this oem permission in android if you are in fastboot
Click to expand...
Click to collapse
OEM permission need for fastboot/unlock bootloader.
Sent from my NEM-L21 using Tapatalk
Anonda said:
OEM permission need for fastboot/unlock bootloader.
Click to expand...
Click to collapse
Yes, that's what I read too. Since I can't change that permission anymore while I can't start Android, I can't unlock. Dammit.
Is DC Unlocker my only option then? It seems their software can do it.
I'm afraid I've got some pretty bad news. Last week the same thing happened to me after I was THAT stupid to actually try and flash the rollback package for the second time. My phone got bricked just like yours, and NOTHING worked to fix it. I tried completely everything I could find on the net and XDA, and in the very end I was forced to bring it in for warranty repairs. Even they COULD NOT fix it and the phone ended up with the entire logicboard changed with a completely new one. I was lucky that it all was done under warranty. Will never do anything as stupid as that!
Really hope you find a fix somehow, but if not, the repair service is your only solution, because otherwise the phone is as good as dead.
markositoo said:
I'm afraid I've got some pretty bad news. Last week the same thing happened to me after I was THAT stupid to actually try and flash the rollback package for the second time. My phone got bricked just like yours, and NOTHING worked to fix it. I tried completely everything I could find on the net and XDA, and in the very end I was forced to bring it in for warranty repairs. Even they COULD NOT fix it and the phone ended up with the entire logicboard changed with a completely new one. I was lucky that it all was done under warranty. Will never do anything as stupid as that!
Really hope you find a fix somehow, but if not, the repair service is your only solution, because otherwise the phone is as good as dead.
Click to expand...
Click to collapse
my phone is also reedy to send to service. I have a lot of phone with android but no rom make so many damage to my phone, like this fc** rollback. finger cross, because huawei service in my country without warranty,takes for new motherboard 175 $ . I bought phone for 233 $ with 3 gb ram..... This will be harsh and pay(in)ful lesson for me.
dragon218 said:
my phone is also reedy to send to service. I have a lot of phone with android but no rom make so many damage to my phone, like this fc** rollback. finger cross, because huawei service in my country without warranty,takes for new motherboard 175 $ . I bought phone for 233 $ with 3 gb ram..... This will be harsh and pay(in)ful lesson for me.
Click to expand...
Click to collapse
Uhh, I am sorry to hear that. But yes, I had the same harsh lesson. They will be forced to changed the motherboard too, cause even they won't be able to re-flash the whole system. Though, what I did to have the warranty not declined, is I brought the phone to the service and said that - "The phone received and OTA update through the updater, I didn't look much into it and just went with it, pressed on update and everything seemed well. It worked until the moment where it installed and restarted, and now the phone is stuck on Huawei logo and you can't possibly do anything with it, not even turn it off." - and that's it. They will have to repair it under warranty because there is no proof left that you had rooted it or done any other installations not authorized by Huawei.
Best of luck!
Liebaart said:
Yes, that's what I read too. Since I can't change that permission anymore while I can't start Android, I can't unlock. Dammit.
Is DC Unlocker my only option then? It seems their software can do it.
Click to expand...
Click to collapse
I know that i read somewhere how to manage to this oem lock. I was 50 % right.
https://forum.dc-unlocker.com/forum...61751-huawei-mate-9-mha-l29-erase-frp-problem
Some user got the same problem that you have and flash boot.
But truly if u don't have "your device has been unlock" only bootloop on huawei logo, is more simple to send it back to warranty and play dump.
I have now "your device is unlock" and i pray for miracle.
Liebaart said:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Click to expand...
Click to collapse
I am exactly in the same situation with the difference that I don't have Fasboot! How do you get to Fastboot? Mine hangs on the screen that says the phone is unlocked and the device is booting... Vol+/Vol- and Power doesn't boot into Fastboot and my minimal ADB doesn't recognize the phone in the stages that it hangs...
---------- Post added 16th April 2017 at 12:04 AM ---------- Previous post was 15th April 2017 at 11:52 PM ----------
I have the same situation. I tried everything, Three button method, letting the battery run out completely, Vol+ and Power, Vol- and Power, connected to PC, not connected to PC. Every time I disconnect the charger, and reconnect it starts from 0. I read some other people here have the same problem. Send it to warranty and explain your rollback process unlocked the bootloader somehow (I mean the phone does do a lot of sh*ty sh*t, so this shouldn't seem very odd as well!!!) and hope that you get a repair/replacement and after that sell it on ebay hoping some stupid people like us in the first place will buy it and spend your money on a phone more reliable!
I managed to access the fastboot using the 3 button method in cold boot. Hold the Power key until the screen goes off and then release and hold down the Vol- key and immideately connect the usb cable to PC right before it vibrates or exactly when it vibrates (it's a matter of timing), and bingo you are in fastboot and you can flash system.img, recovery.img, cust.img, cache.img and boot.img from there, but this is not how I revived my phone. I used the 3 button method again when the phone was charged for like half an hour or so and the did the same cold boot trick and I could boot into the force upgrade environment (strangely this still didn't work whitout connecting the usb cable to PC), but it somehow didn't want to read the UPDATE.APP that I had in dload folder on my SD card and wanted to have it from my PC (I just felt it nad there was no indication of it ) so then I installed the DC Phoenix tool and payed 15 euros to be able to inject the complete UPDATE.APP to my bricked phone and the installation went well to 99% and failed, but I rebooted the phone and I could boot normally. Just to make sure I did a factory reset afterwards. Hope this helps.
Cannot get into Bootloader
Hey there!
Essentially as stupid as I am i flashed the Rollback Image at Android 6.0 too, because i wanted to get rid of C900. So now my phone is stuck in the Startup screen too. As mentioned here, I wanted to unlock bootloader again; The Button combination does not work, and if I want to start in bootloader via ADB, it just says "waiting for device"
i am really desperate and i don't know what i should do now
Thanks for the help
EDIT: Somehow managed to got it into Bootloader. At the moment i am unlocking it. Where do i get TWRP and the needed things? Please help, i'm just some noob who doesn't know how it's done
EDIT2: Solved, got Stock Recovery Re-installed, Flashed with the Force Update Method the Main Package of the Rollback (so not the temp rollback data), and worked. But Still C900 and no Google sign-in possible. Someone know how to solve?
I posted in the discussion forum as well but here is the post. Ok so to start i got my bootloader code, did the Oem line in adb all went well, used the greatslon us M3 Twrp, said it went through ok, tried to boot using the volume up an down as well as power just boots to blackscreen then does nothing. if i let it just boot into factory android it runs for a min and then forces a reboot, oh and my model is the CPN-W09 which i think is the issue upon reading, the Greatslon twrp is for a dif version of M3 then mine, so i tried the erecovery it says im not supported, i tried restore through hisuite says not supported, i try and do a factory reset but unit powers off before it can complete. Any ideas what i can do?
deeman1971 said:
I posted in the discussion forum as well but here is the post. Ok so to start i got my bootloader code, did the Oem line in adb all went well, used the greatslon us M3 Twrp, said it went through ok, tried to boot using the volume up an down as well as power just boots to blackscreen then does nothing. if i let it just boot into factory android it runs for a min and then forces a reboot, oh and my model is the CPN-W09 which i think is the issue upon reading, the Greatslon twrp is for a dif version of M3 then mine, so i tried the erecovery it says im not supported, i tried restore through hisuite says not supported, i try and do a factory reset but unit powers off before it can complete. Any ideas what i can do?
Click to expand...
Click to collapse
ok so a followup i can get into fastboot&rescue mode, but seems the usb debugging or dev options are now turned off so trying to flash anything with fastboot doesn't seem to work" FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Developer op)" so now im really stuck as i have no way to get into the phone settings to enable it, oh and it now wont boot past the huawei logo it comes up animates a little then unit restarts. I am hoping i dont need to send it to repair, cause i know you guys are smarter then they are so hoping i can pick your brains for an easy fix.
Hello everyone, just wanted to say a quick thanks, after successfully rooting and installing custom roms on two phones thanks to the information on these forums, third time turns out to be a charm and I managed to hard brick my new P10 lite.
The situation right now:
no charge light, no combination of buttons will do anything, phone is dead and will not boot or vibrate.
my computer will recognize that a phone is connected, for example Hisuite will pop up when i connect the phone, and in device manager, it shows Lemobile android device and the submenu says Android bootloader interface.
how i got here:
i was trying to install lineage 14.1 from this haky86
https://forum.xda-developers.com/p8...m-lineageos-14-1-huawei-p8-lite-2017-t3649292
but before i did that, i used this guide to install twrp and supersu:
https://forum.xda-developers.com/p10/how-to/twrp-how-to-root-p10-lite-t3617418
everything went fine, on the stock operating system i had root and system was running.
when i installed lineage, i lost root and couldnt figure out how to get it back. so i used this guide to restore the stock system and was going to try again from the beginning.
https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097
however, when i tried to reinstall lineage for the second, third and fourth time, i kept getting stuck in a bootloop with the lineage animation. it seemed to me that i needed to flash the vendor image, and i found a guide on xda how to do it, but it wouldnt let me flash to the vendor partition. (sorry, i dont recall the exact error and i cant get there anymore :/)
so in massive frustration and desperation, i tried to use this method:
https://forum.xda-developers.com/p8...uide-unbrick-huawei-p8-lite-2017-pra-t3713574
which i know is for a p8 and i never should have tried to install it, but it went through the whole download process and at about 50-60% on the recovery the phone went black and never turned on again.
i have read that perhaps disconnecting the battery for a few minutes might help? or is this something that dc unlocker can help with?
any advice would be greatly appreciated. if more information is needed, please let me know.
Hi,
Have you tried completely turning off your phone (pressing on/off button for roughly 20 seconds) and then booting into recovery (pressing Volume Up and Power key simultaneously for rouhgly 10 seconds)?
Best,
Kenny
Thanks for the reply, but as I said, no button combinations elicit any response. The only sign that the phone is not completely dead is that it will be recognized by my computer as an android phone, but adb (for example) says no device is connected.
lineage gives you bootloop due to wrong data partition format
bricked my p10 lite several times same ending
only way that always gets the phone back to life is flashing lineage, i took haazan's one
BUT BEFORE flashing the lineage 14.1 zip check partition format is ext4
when back on lineage and stock ROM is wanted boot into twrp and re change format to f2ts or how it is named and flash the stock zip
unbricked
edit:
saw your second post too late
if the phone does not response on any button(s) maybe adb sideload command for change partition format and then sideloading the lineage zip is a way?
I have a similar problem, I have a custom rom (Elemental) but I flash another custom rom, it was normal, in the reboot it not turn on, only is in fastboot mode, i flash original system, cust, boot, and another but it is the same, help me please
Hi all,
I've installed LineageOS on my mate 9, using their own tutorial, and with a stock recovery.
Everything ran smoothly for a couple of weeks. Today however my phone would not turn the screen on, just minutes after it worked fine. So, I rebooted manually by holding the power button.
Did not work, but instead: my phone is stuck on the 'your device has been unlocked and can't be trusted' + your device is booting now... screen. But it does not boot.
I can't go into the stock recovery mode, using power + volume up.
I can get into fastboot mode, but my pc (which I used to root my phone) does not recognise it using adb, while it did earlier. sometimes a fastboot command (fastboot devices) works and lists a code.
But if I try fastboot flash system and the filename for the lineageOS img, it sends the first package but does not seem to write, writing system 1/4 lasts for ever without anything happening. The phone also stays in the white fastboot screen during this event.
Can someone help me solve this? Is there a solution?
Mate 9
dekraan said:
Hi all,
I've installed LineageOS on my mate 9, using their own tutorial, and with a stock recovery.
Everything ran smoothly for a couple of weeks. Today however my phone would not turn the screen on, just minutes after it worked fine. So, I rebooted manually by holding the power button.
Did not work, but instead: my phone is stuck on the 'your device has been unlocked and can't be trusted' + your device is booting now... screen. But it does not boot.
I can't go into the stock recovery mode, using power + volume up.
I can get into fastboot mode, but my pc (which I used to root my phone) does not recognise it using adb, while it did earlier. sometimes a fastboot command (fastboot devices) works and lists a code.
But if I try fastboot flash system and the filename for the lineageOS img, it sends the first package but does not seem to write, writing system 1/4 lasts for ever without anything happening. The phone also stays in the white fastboot screen during this event.
Can someone help me solve this? Is there a solution?
Click to expand...
Click to collapse
In fastboot mode does it tell you the phone is still unlocked and frp is unlocked?
Newrooter22 said:
In fastboot mode does it tell you the phone is still unlocked and frp is unlocked?
Click to expand...
Click to collapse
Did not try that! It is at a repairshop at the moment, they feel it is a software problem, but I guess mainly because I dropped the word 'custom rom'.
I've got a couple clues that suggest it might be a fried chip: I get Command not allowed errors when trying several fastboot commands, and I also get a remote:flash write failure when I try to flash a ramdisk.img or system.img.
Hope to hear from the shop today or tomorrow, and will update afterwards!
I have this exact issue on my huawei y6 2018, i can access to the emui recovery mode, and have bootloader unlocked.
Hello,
short story i rebranded my l29c636 to l29c432 oreo 8.0 everything worked until i try to deleted some of the google bloatware. Phone rebooted and i got FPR locked in fastboot. Did couple of stupid things and right now situation is this:
1. FPR in fastboot locked
2. Bootloader relocked
3. Phone stuck in boot loop, only goes to huawei logo and continuously reboot.
4. I can only access fastboot (and phone is detected in cmd ), other buttons don't do anything.
Is there any solution to this?
Plantdump said:
Hello,
short story i rebranded my l29c636 to l29c432 oreo 8.0 everything worked until i try to deleted some of the google bloatware. Phone rebooted and i got FPR locked in fastboot. Did couple of stupid things and right now situation is this:
1. FPR in fastboot locked
2. Bootloader relocked
3. Phone stuck in boot loop, only goes to huawei logo and continuously reboot.
4. I can only access fastboot (and phone is detected in cmd ), other buttons don't do anything.
Is there any solution to this?
Click to expand...
Click to collapse
I got it fixed, this guy charged 10€ for what dc phoenix charge 50 dollars . Here are the links: ebay.com/usr/mulenkachi?_trksid=p2060353.m2749.l2754 and gsmzambia.com/ they are he same persone. Superb experience and cheep compare to the rest.