Related
I am a noob at android--just putting that out there. But trying...
I just received my new nexus 7 2013. I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it, and then the plan was to root it. Something happened in the process--can't say for certain what, but at some point the tool brought up TWRP on the nexus and a file that the tool said was supposed to be there, wasn't. The end result now is that my nexus is stuck on the bootloader. None of the buttons seem to work, other than restart bootloader. Turn off DOES turn off the nexus, but then when pressed again, goes right back to the bootloader. The recovery one flashes the screen quickly, then goes back to the bootloader. The Start option makes it so the screen shows the "Google" icon indefinitely with the unlocked lock icon. I need to note that the option to get into the bootloader (power + vol up and vol down) did not work for me—the only way I was able to go into the bootloader was the power and vol down. Currently though, pressing the power button makes the nexus go directly into the bootloader.
When plugged into computer via the usb cord, windows xp currently doesn't recognize anything is plugged in, although I do have the latest USB drivers installed.
I downloaded and ran SDK and went through the various fastboot commands from within a cmd window. The fastboot devices command does bring up a device number, so it is recognized by fastboot.
Here's where others will start to shake their heads in bewilderment...in my haste to try and get this up and working and out of the endless bootloader menu, I *could* have flashed it with the nexus 7 2012 recovery image, because when using fastboot to do so, at end says something about grouper and my device says flo (although nothing changed with the nexus—as in there are no obvious changes as still in bootloader). I am aware that the official flo factory image is not yet available, although at this point, I don’t have much confidence in that doing anything.
If I open up Wugfresh’s Toolkit, I can’t do anything with it, as it says that ADB doesn’t work or something and to enable USB debugging, which I can’t do because I’m stuck on the bootloader.
I don't know where to go from here--I don't know if the device is salvageable or if it is completely toast and I should just return it and get another one...I see that in the day since I downloaded Wugfresh’s Toolkit, he has released two more versions—not sure if the new version can do anything—haven’t tried yet. Can anyone with more knowledge than myself give me a hand or some advice? Thanks in advance.
You first need to have the bootloader unlocked before flashing any custom recovery to make a nandroid backup.
Username invalid said:
You first need to have the bootloader unlocked before flashing any custom recovery to make a nandroid backup.
Click to expand...
Click to collapse
it is unlocked. I am able to use the fastboot commands to unlock and lock. it currently is unlocked.
Easiest thing to do is just flash back to stock and start over.
Grab the zip file from here. It has the stock rom, stock recovery, and stock boot that you need.
You can either run the .bat file, or issue the commands yourself:
fastboot oem unlock
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot -w
"I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it" which I assumed you meant you tried to make a nandroid backup before unlocking.
Username invalid said:
"I used Wugfresh's version 1.6.6 toolkit to backup the nexus prior to unlocking it" which I assumed you meant you tried to make a nandroid backup before unlocking.
Click to expand...
Click to collapse
I will try the one click factory restore method posted by Geodude when I get home from work--at this point I have nothing to lose.
And Username invalid, sorry, no nandroid backup--by backup I meant just the basic backup of settings that are shown on Wugfresh's Toolkit.
Hopefully the one click restore will work....thank you very much.
busdonic said:
I will try the one click factory restore method posted by Geodude when I get home from work--at this point I have nothing to lose.
And Username invalid, sorry, no nandroid backup--by backup I meant just the basic backup of settings that are shown on Wugfresh's Toolkit.
Hopefully the one click restore will work....thank you very much.
Click to expand...
Click to collapse
I assumed that as doing an app and setting backup on a brand new device does not seem to make much sense.
Username invalid said:
I assumed that as doing an app and setting backup on a brand new device does not seem to make much sense.
Click to expand...
Click to collapse
Yeah, I see that....not sure why I did it myself actually, cuz now that you mentioned it, does seem pretty stupid--I guess that explains why I'm here asking for advice
I'm assuming that the one click restore will work. If it doesn't, I think I found a non-official flo factory image. I think (?) if I flash that to the tablet in fastboot, that will restore it, or at least get it past either the bootloader menu or past the Google icon shown at startup.
Geodude074 said:
Easiest thing to do is just flash back to stock and start over.
Grab the zip file from here. It has the stock rom, stock recovery, and stock boot that you need.
You can either run the .bat file, or issue the commands yourself:
fastboot oem unlock
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot -w
Click to expand...
Click to collapse
this worked--thanks much. Am much relieved to be up and running again....
Hi...
This is the tutorial to root any Moto G
To root any Moto G, three basic steps need to be followed... you can either do them manually or use a tool do them for you. It is advised to follow them manually so that if there's some bug in the tool you don't get into any trouble.
CAUTION - You will lose all data and files so better back them up.
For Google Play edition devices, the process is same and only the recovery.img file is different. For GPe CWM Advanced Edition recovery go here https://goo.im/devs/philz_touch/CWM_Advanced_Edition/ and select falcon_gpe and download the latest one.
For AT&T and Verizon models don't do anything written above. Just download the Towelroot app. Its a one click root app and doesn't require a PC. Itis trustworthy but is not guaranteed to work but you must give it a try since it won't do any harm and claims of never bricking a phone. Please reply with the result and your android and kernel version.It will probably not work on phones build after June 3 but you can give it a try. You can download it from the website https://towelroot.com
The three steps are :-
1) UNLOCKING THE BOOTLOADER
2) FLASHING CUSTOM RECOVERY
3) INSTALLING SuperSu.zip FILE THROUGH RECOVERY. (SuperSu is acknowledge as the best app to give superuser and root rights)
UNLOCKING THE BOOT LOADER - The instructions to unlock the boot loader are given in the official Motorola website here https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a . Don't be scared by their warnings.
UPDATE - There currently seems to be an issue with unlocking the bootloader on devices running 4.4.4 though it works for 4.4.2. The issue is with Motorola and is that, the unlock code given by the company is showing an error. They are fixing it and it may take some time though you can give it a try as it won't do any harm. Or you can downgrade the boot loader to 4.4.2 and then unlock it.
As confirmed by the Motorola agent, the problem of unlocking bootloader on 4.4.4 has been fixed
FLASHING CUSTOM RECOVERY :-
To flash a custom recovery, you need these things
1) PC and a USB data cable
2) Android SDK ( developer.android.com/sdk/index.html ) For flashing recovery only SDK is needed but it's your wish if you want to download the ADT bundle. After downloading and unzipping the sdk , open the SDK manager and download only the platform tools for this.. rest is your wish..... and separately download ADB tools and fastboot and extract them minimal-adb-and-fastboot.software.informer.com/1.1/
3) Recovery.img file - You can either use CWM foum.xda-developers.com/showthread.php?t=2563599 or CWM advanced editionforum.xda-developers.com/showthread.php?t=2639583 or TWRP forum.xda-developers.com/showthread.php?t=2561757. EDIT - If your phone had come pre installed with 4.4.4 then use only CWM Advanced Edition. CWM Advanced Edition doesn't make backup on XT1033
4) Motorola drivers https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97326/p/30,6720,9050
5) Enable USB Debugging mode in your phone by going to Settings-About Phone and then tap the build number until you get the toast 'You are a developer'. Now go to Settings again and you will see a new Developer Options there. Go there and enable USB debugging.
6) Have at least 25% of charge on your phone.
After getting all these things:-
1) Download the recovery.img file to your PC and copy paste it to android SDK/platform tools folder.
2) Boot your phone to fastboot mode by first switching it off and holding the volume down and power button for 3 seconds.
3) When in fastboot mode, connect your phone to pc, go to the platform tools folder, there pres shifft and right mouse click simultaneously and select 'open command prompt window here'.
4) In the command window enter
Code:
fastboot devices
If it shows a number and fastboot then we are good..
5) Then enter
Code:
fastboot flash recovery recovery.img
( where in recovery.img the recovery is the name of your recovery file. Example if the name of recovery file is ABC then enter fastboot flash recovery ABC.img)
5) Press enter and if the command prompt window displays the message okay then the recovery is successfully flashed.
6) Now just boot your phone to recovery mode through fastboot mode by following the on screen instructions and in recovery mode select Reboot System Now to reboot your phone normally.
(see attached images below for screenshots)
INSTALLING SuperSu
To install SuperSu :-
1) Download SuperSu zip file download.chainfire.eu/452/SuperSU/ and transfer it to your phone
2) Reboot to recovery via fastboot.
3) Select install zip and select choose from SD card.
4) Locate the file and install it.
5) Now reboot your phone.
YUP.. YOU ROOTED YOUR PHONE!
Download any root checker app from the Play Store to check whether your phone is rooted or not.
If you get into any trouble, please contact and don't forget to hit thanks if it helped
Consider rating the thread by going to the option 'rate thread' which is located above the thread on the right side. You can also participate in the poll
I have a huawei p6 but I'm absolutely not satisfied with that and I bought a moto g for my girlfriend and that is awesome.
The only thing why I haven't bought the g for myself as well is the rooting. That time I didn't find an easy way to root it.
If it is a working method than I will buy the 4g verson with sd card support
Sent from my HUAWEI P6-U06 using XDA Free mobile app
sisqoboy said:
I have a huawei p6 but I'm absolutely not satisfied with that and I bought a moto g for my girlfriend and that is awesome.
The only thing why I haven't bought the g for myself as well is the rooting. That time I didn't find an easy way to root it.
If it is a working method than I will buy the 4g verson with sd card support
Sent from my HUAWEI P6-U06 using XDA Free mobile app
Click to expand...
Click to collapse
Yup dude...this works for sure..!
I also added screenshots.. check them out.
Meuuks13 said:
Yup dude...this works for sure..!
Click to expand...
Click to collapse
Does this work with the latest bootloader on 4.4.4? Im still stock but i wanna root it so much
Thanks
motocruiser said:
Does this work with the latest bootloader on 4.4.4? Im still stock but i wanna root it so much
Thanks
Click to expand...
Click to collapse
I looked into it just now... Currently there's an issue with Motorola with unlocking the bootloader when on 4.4.4...As people say, the unlock code given my Motorola is showing an error... You can still try it.. maybe it's even fixed by now.. Even if it fails there wouldn't be any harm.. Though the unlocking works fine with 4.4.2... You can revert back to 4.4.2, unlock the bootloader and then update to 4.4.4... The thing will be same as you will lose all data and files when unlocking the bootloader and so in reverting to 4.4.2.....(Remember, only unlocking doesn't mean you won't recieve updates, you won't receive updates only if you flash a custom recovery.)
EDIT - I added it to the OP. Thanks for bringing it to attention.
And does this work for Verizon model
Sent from my XT1028 using XDA Premium 4 mobile app
xrilex said:
And does this work for Verizon model
Sent from my XT1028 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have Verizon I see. The only you will probably face is unlocking the bootloader.. Oh, wait first let me laugh... lol...OK....At one point of time you couldn't unlock the bootloaders for AT&T and Verizon and then we were blessed by the 'one click root' app by the famous hacker geohot called TowelRoot. This app claims to root all the AT&T and Verizon devices with just a click. You don't even need a PC. Just download the app and in the app chick 'make it rain'. Though this is not guaranteed to work but must give a try as it won't do any harm but there's a chance of bricking the phone but you can easily recover from a soft brick by flashing the stock firmware.
Towelroot - https://towelroot.com/
P.S. - Please reply if you tried this and if it didn't work reply with your android version and kernel version. Well reply with your android version and kernel version anyway.
Edit- I added it to the OP
Meuuks13 said:
I looked into it just now... Currently there's an issue with Motorola with unlocking the bootloader when on 4.4.4...As people say, the unlock code given my Motorola is showing an error... You can still try it.. maybe it's even fixed by now.. Even if it fails there wouldn't be any harm.. Though the unlocking works fine with 4.4.2... You can revert back to 4.4.2, unlock the bootloader and then update to 4.4.4... The thing will be same as you will lose all data and files when unlocking the bootloader and so in reverting to 4.4.2.....(Remember, only unlocking doesn't mean you won't recieve updates, you won't receive updates only if you flash a custom recovery.)
EDIT - I added it to the OP. Thanks for bringing it to attention.
Click to expand...
Click to collapse
thanks for your help dude but i heared that if you flash back to 4.4.2 your bootloader is still the latest so its still unlockable...
i have found a fix on a motorola customer forum for this problem, but when i flash this testdrive motoboot image file it goes wrong and i cant fix it by my self
motocruiser said:
thanks for your help dude but i heared that if you flash back to 4.4.2 your bootloader is still the latest so its still unlockable...
i have found a fix on a motorola customer forum for this problem, but when i flash this testdrive motoboot image file it goes wrong and i cant fix it by my self
Click to expand...
Click to collapse
Sorry I didn't know that. Downgrading the bootloader is a very risky process.
What did you exactly do?
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
t.lou91 said:
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
Click to expand...
Click to collapse
Please tell which android version your phone came preinstalled with and what recovery you used.
Also when you reboot to recovery, after the blank screen do you see the android logo lying down with a red triangle?
t.lou91 said:
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
Click to expand...
Click to collapse
Please tell your phone's android version and the recovery you used and what did you enter at the command prompt?
Meuuks13 said:
Sorry I didn't know that. Downgrading the bootloader is a very risky process.
What did you exactly do?
Click to expand...
Click to collapse
Well it doesnt go wrong like you think so my phone is actually not bricked.
But the command window says that the operation failed so i think something is wrong with this testdrive image from the moto forum.
thanks
motocruiser said:
Well it doesnt go wrong like you think so my phone is actually not bricked.
But the command window says that the operation failed so i think something is wrong with this testdrive image from the moto forum.
thanks
Click to expand...
Click to collapse
Testdrive image?
Meuuks13 said:
Testdrive image?
Click to expand...
Click to collapse
Yeah they say, if you on 4.4.4 and want to unlock your bootloader you have to flash the motoboot_testdrive.img file wich downgrades the bootloader to i think it was called 40.15 or so after that you have to unlock your bootloader and then flash the motoboot 4.4.4 stock image so that you have the actual one but for me it failed while i try to flash this testdrive image
motocruiser said:
Yeah they say, if you on 4.4.4 and want to unlock your bootloader you have to flash the motoboot_testdrive.img file wich downgrades the bootloader to i think it was called 40.15 or so after that you have to unlock your bootloader and then flash the motoboot 4.4.4 stock image so that you have the actual one but for me it failed while i try to flash this testdrive image
Click to expand...
Click to collapse
So basically you want to downgrade the bootloader and then unlock it?
Well if you are on KitKat you can downgrade the bootloader by flashing 4.3 , then unlocking the bootloader and then updating to KitKat
Thanks for the guide. I've already recommended it to someone who was having problems.
jselene said:
Thanks for the guide. I've already recommended it to someone who was having problems.
Click to expand...
Click to collapse
Cool.
Thanks Meuuks13. This worked well.
Also, I've found that you can remove the "unlocked bootloader warning message" shown on boot-up by following the method in the Moto X forum:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
JDCGW said:
Thanks Meuuks13. This worked well.
Also, I've found that you can remove the "unlocked bootloader warning message" shown on boot-up by following the method in the Moto X forum:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
Click to expand...
Click to collapse
I got something wayyyy better than that!
I let you remove that sign and use the pics given here forum.xda-developers.com/moto-g/themes-apps/shareboot-logos-t2875147 or you can give me the pic you want and I will make it in such a way that you can use it.
Hi,
My Nexus 6p was running the latest OTP update of Android Nougat successfully, Suddenly while using google maps it, restarted and went into a boot loop. All i can see is the unlocked bootloader warning (i had unlocked the bootloader earlier) and then the google logo.
I am able to go into bootloader mode and my system identifies my device as a fastoboot device .
I was able to access my stock recovery but while trying to fix my phone, i tried installing twrp recovery and now whenever I choose the option of recovery mode using my volume keys. it again shows the google logo and nothing happens after that.
I have tried many things, but I am not able to resolve my boot loop. Somebody please help me. Please guide me what should be my approach to this problem
Regards
Ishmeet
ishmeet said:
Hi,
My Nexus 6p was running the latest OTP update of Android Nougat successfully, Suddenly while using google maps it, restarted and went into a boot loop. All i can see is the unlocked bootloader warning (i had unlocked the bootloader earlier) and then the google logo.
I am able to go into bootloader mode and my system identifies my device as a fastoboot device .
I was able to access my stock recovery but while trying to fix my phone, i tried installing twrp recovery and now whenever I choose the option of recovery mode using my volume keys. it again shows the google logo and nothing happens after that.
I have tried many things, but I am not able to resolve my boot loop. Somebody please help me. Please guide me what should be my approach to this problem
Regards
Ishmeet
Click to expand...
Click to collapse
FOLLOW THESE INSTRUCTIONS ONLY IF ANYTHING BETTER DOESNT COME UP BECAUSE I DON'T WANT TO FEEL GUILTY IF YOU "FUBAR" YOUR PHONE. I am not an expert in this stuff.. I can only follow instructions and the two videos helped me get out of crappy situation in the past couple weeks.
Follow the two videos below on how to re-install your drivers properly and flash and root Nougat 7.0
First go delete your driver from your PC via Device Manager. Anything that you can associate with N6P or Google.
Then watch this video on how to install new drivers.
This video on how to install Nougat
If you can access fastboot, I would just follow Heisenbergs guide (look In the stickies) and reflash the N stock images manually via fastboot. Also, make sure that you flash the recommended TWRP version that he has linked in his guide otherwise you will have problems with recovery. His guide has saved me multiple times when I messed up my phone.
Pain-N-Panic said:
If you can access fastboot, I would just follow Heisenbergs guide (look In the stickies) and reflash the N stock images manually via fastboot. Also, make sure that you flash the recommended TWRP version that he has linked in his guide otherwise you will have problems with recovery. His guide has saved me multiple times when I messed up my phone.
Click to expand...
Click to collapse
I am in something similar situation but the thing is computer does not detect any device and phone just shows google. I ended up in this situation after I was trying to flash zip drivers for google assistant. But now I am not able to access recovery mode even.
ranjha94 said:
I am in something similar situation but the thing is computer does not detect any device and phone just shows google. I ended up in this situation after I was trying to flash zip drivers for google assistant. But now I am not able to access recovery mode even.
Click to expand...
Click to collapse
I have a locked bootloader and I now have a similar issue, I can't flash anything manually because of the BL . following this topic
bkgovols said:
I have a locked bootloader and I now have a similar issue, I can't flash anything manually because of the BL . following this topic
Click to expand...
Click to collapse
I think I figured out mine problem. I am not sure what you mean by locked bootloader but in my case I was able to reboot to bootloader by pressing all three buttons (Volume up, Volume down and power button) at the same time.
Once you are there and if your bootloader is already unlocked you can flash your own android. Probably this process is called unbrick your phone. I am surprissed and sad as I am not allowed to post link which can help you. Ask admin.
Any related problem while following process. I can try as I am not very expert.
RIP my English.
Thanks
---------- Post added at 05:20 AM ---------- Previous post was at 05:16 AM ----------
bkgovols said:
I have a locked bootloader and I now have a similar issue, I can't flash anything manually because of the BL . following this topic
Click to expand...
Click to collapse
https://devs-lab.com/how-to-unbrick-hard-soft-bricked-google-huawei-nexus-6p.html
bkgovols said:
I have a locked bootloader and I now have a similar issue, I can't flash anything manually because of the BL . following this topic
Click to expand...
Click to collapse
And that's why it's a good idea if you do ANY tinkering to your phone that you have an unlocked bootloader. I have screwed my phone up a hundred times over but nothing that a fastboot flash of the stock Google images couldn't overcome.
I'm not sure what situation you're in but I would try to get that bootloader unlocked asap. Just know that when you unlock it, every partition on the phone will be completely wiped to include internal storage (sd card).
I wasn't tinkering that's the thing. I was on the Android beta but I have installed those OTA. I would love to be able to unlock the bootloader but none of the commands will work to unlock it because usb debugging was not enabled or the developer options and I can't boot it to change that.
My Nexus 6P is seemingly bootlooping.
I can boot into the bootloader menu but not into recovery. My bootloader is not unlocked so I cannot flash anything.
Issuing the command: "fastboot flashing unlock" does not work nor does "fastboot oem unlock". I cannot flash a custom recovery. Because my bootloader is locked.
Any help would be great.
avansledright said:
My Nexus 6P is seemingly bootlooping.
I can boot into the bootloader menu but not into recovery. My bootloader is not unlocked so I cannot flash anything.
Issuing the command: "fastboot flashing unlock" does not work nor does "fastboot oem unlock". I cannot flash a custom recovery. Because my bootloader is locked.
Any help would be great.
Click to expand...
Click to collapse
You say that your bootloader was not unlocked, so I'm assuming you didn't have developer options turned on and USB debugging checked before fastboot flashing unlock?
Fe Mike said:
You say that your bootloader was not unlocked, so I'm assuming you didn't have developer options turned on and USB debugging checked before fastboot flashing unlock?
Click to expand...
Click to collapse
I don't recall if i had them turned on or not. I know my device was enrolled in the Android beta program.
avansledright said:
I don't recall if i had them turned on or not. I know my device was enrolled in the Android beta program.
Click to expand...
Click to collapse
Do you remember if you modded anything prior to bootloop? The reason you can't unlock bootloader is because USB debugging isn't on. What version of Android were you on when it happened? I believe you can still use google factory Image to restore your phone.
Fe Mike said:
Do you remember if you modded anything prior to bootloop? The reason you can't unlock bootloader is because USB debugging isn't on. What version of Android were you on when it happened? I believe you can still use google factory Image to restore your phone.
Click to expand...
Click to collapse
The last thing i did was installed the new Google camera 4.2 but it worked fine after that.
avansledright said:
The last thing i did was installed the new Google camera 4.2 but it worked fine after that.
Click to expand...
Click to collapse
Since you don't have twrp you probably don't have a backup, which what I'm going to suggest will bring you back to stock and may lose everything. Though it's better than a bricked phone. Since I never did the flash-all.bat you may lose your stuff on internal SD. In this link, download the correct image your phone was on (under angler) and if using windows use the flash-all.bat in fastboot. If you're phone isn't 32 GB, extract all from zip and flash everything except user data. Forgive me for assuming you may be new. https://developers.google.com/android/nexus/images
Fe Mike said:
Since you don't have twrp you probably don't have a backup, which what I'm going to suggest will bring you back to stock and may lose everything. Though it's better than a bricked phone. Since I never did the flash-all.bat you may lose your stuff on internal SD. In this link, download the correct image your phone was on (under angler) and if using windows use the flash-all.bat in fastboot. If you're phone isn't 32 GB, extract all from zip and flash everything except user data. Forgive me for assuming you may be new. https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
,
avansledright said:
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
Click to expand...
Click to collapse
Do you get the error on all that you try to flash? Maybe just try the recovery img only to see if you can at least get that. If that works you should be able to sideload ota through recovery. With having a locked bootloader you might be at a loss. But on the flip side, having everything locked and not rooted you should be ok for warranty replacement.
avansledright said:
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
Click to expand...
Click to collapse
Fastboot is useless since your bootloader is locked. Try to ADB sideload the latest OTA image from Google and see if it will boot.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Fastboot is useless since your bootloader is locked. Try to ADB sideload the latest OTA image from Google and see if it will boot.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
avansledright said:
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
Click to expand...
Click to collapse
Ahh, missed that in your first post. I'm not sure how you can get recovery going if it's bootlooping when you access it.
Sent from my Nexus 5X using Tapatalk
avansledright said:
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
Click to expand...
Click to collapse
Check out this thread at post number 268 they mention using adb through mtp mode when not able to use recovery.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page6
Fe Mike said:
Check out this thread at post number 268 they mention using adb through mtp mode when not able to use recovery.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page6
Click to expand...
Click to collapse
Tried running through those steps. I can't even get a temporary boot of TWRP or stock recovery continues to bootloop even though WugFresh claims it was successful. Tried doing it manually via Fastboot and continue to get the error in flashing.
I just received my replacement phone. So I might just call it a day on this one. :crying:
avansledright said:
Tried running through those steps. I can't even get a temporary boot of TWRP or stock recovery continues to bootloop even though WugFresh claims it was successful. Tried doing it manually via Fastboot and continue to get the error in flashing.
I just received my replacement phone. So I might just call it a day on this one. :crying:
Click to expand...
Click to collapse
Good to hear about replacement! There are a few people in these forums that have a brick and can't get out of it. I thought you couldn't Hard brick these phones unless that was your goal. And most of these users who have bricks don't even know what causes it. Just a random reboot then loops. Kinda scary.
If your device has unlocked boot loader and for some reason you just tried to flash something and it went wrong then there is no problem guys. The simplest solution if you are stuck on boot is that press vol down and power key for 3 minutes. It will work and will reboot. No before rebooting into the phone just go to the recovery by pressing the vol up key on boot process. This will load you in eRecovery of huawei. From there you can power off the phone. Now take out the sd card and put the desired rom in it. If you want stock android then you need to put UPDATE.APP in the dload folder in sd card and then go to eRecovery again. If you have a twrp recovery then you can go to stock as well and switch to a custom rom as well. Just place custom rom zip file and gapps zip file and flash it through twrp recovery.
For custom roms and recover visit :
Meticulus.co.vu
Thank you if I ever need it. Maybe someone that has needed to use this fix will confirm that it works.
gerrykiddy said:
Thank you if I ever need it. Maybe someone that has needed to use this fix will confirm that it works.
Click to expand...
Click to collapse
Well, it doesn't work for me... I held those buttons for 5 minutes, and all my phone did was to reboot about every15 seconds to the "Your device is booting now..."
I also tried with other button combos without any luck.
SnowmanDK said:
Well, it doesn't work for me... I held those buttons for 5 minutes, and all my phone did was to reboot about every15 seconds to the "Your device is booting now..."
I also tried with other button combos without any luck.
Click to expand...
Click to collapse
What happened to your device. Please tell me in detail ?
Arsaam said:
What happened to your device. Please tell me in detail ?
Click to expand...
Click to collapse
I made a post just before you did over here: https://forum.xda-developers.com/hu...i-p9-lite-stuck-bootloop-enter-t3600868/pages
After that post I managed to get into fastboot mode, when connected to my computer using usb, however my frp is locked and fastboot unlocked, so I am stuck there at the moment.
SnowmanDK said:
I made a post just before you did over here: https://forum.xda-developers.com/hu...i-p9-lite-stuck-bootloop-enter-t3600868/pages
After that post I managed to get into fastboot mode, when connected to my computer using usb, however my frp is locked and fastboot unlocked, so I am stuck there at the moment.
Click to expand...
Click to collapse
Download the SRK Tool for huawei p9 lite and unlock bootloader ( if required ). Then flash twrp recovery and then root the device. You might have made a mistake between any one of the processes. Also check if the OEM is unlocked in device developer options
Arsaam said:
Download the SRK Tool for huawei p9 lite and unlock bootloader ( if required ). Then flash twrp recovery and then root the device. You might have made a mistake between any one of the processes. Also check if the OEM is unlocked in device developer options
Click to expand...
Click to collapse
As written in the other thread, the phone boot loops, and I only have access to fastboot. It refuses to go into recovery and can not boot normally.
I can't flash TWRP as frp is locked.
I tried messing around with Miracle Loader 2.27A, but it can't find my phone (maybe I am doing something wrong).