Hey XDA!
Got my Nexus into some trouble today. I Was running stock rooted 5.0.2, received an OTA update for 5.1. Ran the update and it sent me to my TWRP 3.0 recovery. Restarted the device and found out the update did not work, leaving me at 5.0.2. Ran the update again like a tard, took my to the stock bootloader. TWRP is now no where to be found... In fact there is no recovery to be found. When I select the recovery option in the bootloader it goes to black screen then redirects back to the bootloader. When I select the "start" option, it's reboots the device taking me to the bootloader. I have attempted a hard restart with the power button but the device hangs on the Google logo forever. I have tried to use the Nexus Root Tool but it can't help me since the device won't connect via fastboot, or ADB.
Any help is appreciated.
Hallo,
got the same problem, how did you resolve it ??? Thanks a lot ...
Same here. I can't connect to the device by no means. How did you solve your problem?
Tallyphillips said:
Hey XDA!
Got my Nexus into some trouble today. I Was running stock rooted 5.0.2, received an OTA update for 5.1. Ran the update and it sent me to my TWRP 3.0 recovery. Restarted the device and found out the update did not work, leaving me at 5.0.2. Ran the update again like a tard, took my to the stock bootloader. TWRP is now no where to be found... In fact there is no recovery to be found. When I select the recovery option in the bootloader it goes to black screen then redirects back to the bootloader. When I select the "start" option, it's reboots the device taking me to the bootloader. I have attempted a hard restart with the power button but the device hangs on the Google logo forever. I have tried to use the Nexus Root Tool but it can't help me since the device won't connect via fastboot, or ADB.
Any help is appreciated.
Click to expand...
Click to collapse
you mention it wont connect via fastboot but you can still reboot with the pwr + vol- to get menus of some kind.. ? if the screen is backlite even just a blank screen but you can see it light up theres still hope. All i can say is try to reboot the device into fastboot an then try Nexus Root Toolkit an see if you can reset to Factory to restore the stock recovery partition along with reset the OS to which ever you select and start over .. Good Luck Flashing... the only way i can say your SOL is if when you plug it into your PC an it pops up with the error "Device Malfunctioned,....." then you SOL Good Luck Flashing :good:
EDIT: Sorry didnt notice it was resolved in the title..
Hello all,
I recently tried unlocking my bootloader for my P8 lite and was disappointed to find out that while my device says " Phone Unlocked, FRP Unlock" while at the fastboot&recovery screen, it fails to download supersu to my phone while going through the root process. I am unable to obtain root and furthermore canno't factory reset. I figured I would factory reset by getting my hands on the original stock lollipop firmware for my ALE-L04 which I did, uploading it to my sd card, turning the phone off, and holding both power buttons as well as the home button to prompt the installation of the stock firmware. While holding all three of these buttons nothing happens and when I let go the phone goes back into the fastboot&recovery mode screen with the green android character. Any help on this matter would be greatly appreciated. I would like to either go back to stock or root this bad boy seeing as how it is a little buggy since trying to unlock bootloader and root. - Regards Andrew
same issue my huawei p8 lite
Dear bro same issue whit me if you find any kindly inform and how u firmware update
saum36 said:
Hello all,
I recently tried unlocking my bootloader for my P8 lite and was disappointed to find out that while my device says " Phone Unlocked, FRP Unlock" while at the fastboot&recovery screen, it fails to download supersu to my phone while going through the root process. I am unable to obtain root and furthermore canno't factory reset. I figured I would factory reset by getting my hands on the original stock lollipop firmware for my ALE-L04 which I did, uploading it to my sd card, turning the phone off, and holding both power buttons as well as the home button to prompt the installation of the stock firmware. While holding all three of these buttons nothing happens and when I let go the phone goes back into the fastboot&recovery mode screen with the green android character. Any help on this matter would be greatly appreciated. I would like to either go back to stock or root this bad boy seeing as how it is a little buggy since trying to unlock bootloader and root. - Regards Andrew
Click to expand...
Click to collapse
Could you give me the link for your firmware?
Also how did you unlocked?
aijazahmadrahi said:
Dear bro same issue whit me if you find any kindly inform and how u firmware update
Click to expand...
Click to collapse
kingroot work.
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?
Hello all.
I have a really annoying problem with my Mi 9t - 100% Official rom.
It happened after an update that got stopped for some reason, 'update failure' the phone said.
After that i have been able to use may phone as usual, but the phone was always asking me to do the update.
So i click again on update and that happen... https://www.youtube.com/watch?v=LNQhNUj_d8k
So my phone is trying to do the update and fail and restart again and again after less than 1%.
I can't turn it off, all i can do is launch the Fastboot mode.
The other mode with vol+ and power manipulation is not working, i try with discharged phone to go in there to reset everything, but that's not working.
My phone is not unlocked so in fastboot i can't even try to reinstall a new rom.
I already more or less given up the idea to recover my phone data but if i could unlock the phone it could be great..
Does anyone have any idea what I could do? or do I really have an official bricked phone?
Thank you
Shaykz said:
Hello all.
I have a really annoying problem with my Mi 9t - 100% Official rom.
It happened after an update that got stopped for some reason, 'update failure' the phone said.
After that i have been able to use may phone as usual, but the phone was always asking me to do the update.
So i click again on update and that happen... https://www.youtube.com/watch?v=LNQhNUj_d8k
So my phone is trying to do the update and fail and restart again and again after less than 1%.
I can't turn it off, all i can do is launch the Fastboot mode.
The other mode with vol+ and power manipulation is not working, i try with discharged phone to go in there to reset everything, but that's not working.
My phone is not unlocked so in fastboot i can't even try to reinstall a new rom.
I already more or less given up the idea to recover my phone data but if i could unlock the phone it could be great..
Does anyone have any idea what I could do? or do I really have an official bricked phone?
Thank you
Click to expand...
Click to collapse
If under guarantee, you should go to official service center
Otherwise, have you tried Factory reset from Settings (maybe, it will wipe what is blocking OTA)
Finally, if I understand correctly, you could still unlock your Bootloader and then try to flash update (zip/recovery firmware) by TWRP or even (tgz/fastboot firmware) by Mi Flash. The second option works for some bricks, returning to stock from custom ROMs, etc - hence, should IMO also work for you
Thanks for response.
I can't do a factory reset, it won't start and the menu with reset option that you can get by using volume and power is not reachable.
i can't unlock it neither because you need a working phone to do that...
I live in begium and there is no official xiaomi service center...
i'm feeling so screwed by Xiaomi >_<
You said it works with fastboot, so just try miflash or push official rom with fastboot
Yes, i can acces to fastboot, but i already try miflash and official rom but that's not working, my phone is lock by xiaomi because i didn't think i will need to do that one day !
( https://en.miui.com/unlock/) to make the process, of unlock, you need a working phone with a xiaomi ID, an app installed on it...
double post
You said it works with fastboot, so just try miflash or push official rom with fastboot
So, i manage to get the phone boot. i share the solution here for someone who could have the same issue.
Using fastboot command line : " fastboot continue "
and so MIUI has boot !