Related
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
AndiS21 said:
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
Click to expand...
Click to collapse
do it the right way, dont use toolkits.
to unlock the bootloader, go into the bootloader(fastboot), connect the divice via usb, type..
fastboot devices(to make sure your device is visable)
fastboot oem unlock(to unlock the bootloader)
if you get an error, reboot the bootloader and try again. i had an error the first time on my replacement seven, second time it unlocked.
simms22 said:
do it the right way, dont use toolkits.
to unlock the bootloader, go into the bootloader(fastboot), connect the divice via usb, type..
fastboot devices(to make sure your device is visable)
fastboot oem unlock(to unlock the bootloader)
if you get an error, reboot the bootloader and try again. i had an error the first time on my replacement seven, second time it unlocked.
Click to expand...
Click to collapse
Thanks for the reply, i tried this several times, each time rebooting bootloader, but the command still posts an error in unlocking the bootloader. Recovery and Restart bootloader are marked in red font, Start is in Green, Power off White. I also tried flashing the recovery, since its inaccessible but because of bootloader being locked in won't allow me. :S Anything else you know that can be done ?
Reflash the bootloader?
edit: making VERY sure that you DON'T erase the existing bootloader first.
Try a manual update
AndiS21 said:
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
Click to expand...
Click to collapse
You can try a manual update. Download the update and run adb sideload. That was not working for me, cause my Nexus it's allready updated, but hopefully it will work for you.
dave_uk said:
Reflash the bootloader?
edit: making VERY sure that you DON'T erase the existing bootloader first.
Click to expand...
Click to collapse
fortunatley though bootloader doesn't allow any command even the erase, it wouldn't allow me, nor formatting it as well. So i think the bootloader is intact. This is the screen i get from pressing Power and Vol Down.
pettymro said:
You can try a manual update. Download the update and run adb sideload. That was not working for me, cause my Nexus it's allready updated, but hopefully it will work for you.
Click to expand...
Click to collapse
As i have come to learn, adb can only function when debugging is enabled, in my device it wasn't unabled. Also the recovery program cannot be opened so sideloading through commands cannot be done. At least according to how some forums described the How To sideload through adb
try do it on another pc
AndiS21 said:
Thanks for the reply, i tried this several times, each time rebooting bootloader, but the command still posts an error in unlocking the bootloader. Recovery and Restart bootloader are marked in red font, Start is in Green, Power off White. I also tried flashing the recovery, since its inaccessible but because of bootloader being locked in won't allow me. :S Anything else you know that can be done ?
Click to expand...
Click to collapse
Can you post here the error message?
Israafiyl said:
Can you post here the error message?
Click to expand...
Click to collapse
Sure here it is. When i type in fastboot oem unlock, the message to unlock on my nexus comes up and when i click yes to unlock does the procedure start and end with failure.
AndiS21 said:
Sure here it is. When i type in fastboot oem unlock, the message to unlock on my nexus comes up and when i click yes to unlock does the procedure start and end with failure.
Click to expand...
Click to collapse
I don't know if fastboot let you flash the stock bootloader/recovery without unlocking but you may try:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot flash recovery recovery-stock-jro03d-nakasi.img
Israafiyl said:
I don't know if fastboot let you flash the stock bootloader/recovery without unlocking but you may try:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot flash recovery recovery-stock-jro03d-nakasi.img
Click to expand...
Click to collapse
thanks for the files, but bootloader won't allow me to change a single thing on it. Trying to flash recovery or the bootloader results in Failure result:bootloader locked!. :S
AndiS21 said:
thanks for the files, but bootloader won't allow me to change a single thing on it. Trying to flash recovery or the bootloader results in Failure result:bootloader locked!. :S
Click to expand...
Click to collapse
try one more time with a different port/pc if it daesn't work it may be a hardware fault, i think a corrupted sd.
(you will have to send it to warranty but don't worry, asus have a really good assistence, you may have a new nexus in a less than 2 days)
Manual update
AndiS21 said:
As i have come to learn, adb can only function when debugging is enabled, in my device it wasn't unabled. Also the recovery program cannot be opened so sideloading through commands cannot be done. At least according to how some forums described the How To sideload through adb
Click to expand...
Click to collapse
Use the volume up/down keys to navigate to "Recovery mode", then press the power button.
When the Android with the red exclamation point appears, hold down power first, followed quickly by volume down and volume up. (So that to start, you're holding down power, then you're holding down all three). After 2-3 seconds, release all three keys.
Use the volume up/down keys to select "apply update from ADB," then press power to select it.
On your computer, open up a command prompt or terminal window.
Using the command line, navigate to the folder containing the ADB executables and the update file.
type:
adb.exe sideload <update filename>
On my Nexus with Jelly 4.2 usb debugging is not enabled too, but I still get the option in recovery mode menu. Operation not succesful cause I cannot upgrade from 4.2 to 4.2. I will wait for another update and then try it again. Good luck!
Israafiyl said:
try one more time with a different port/pc if it daesn't work it may be a hardware fault, i think a corrupted sd.
(you will have to send it to warranty but don't worry, asus have a really good assistence, you may have a new nexus in a less than 2 days)
Click to expand...
Click to collapse
I tried it on the laptop too, even changed the drivers to universal naked drivers, but nothing! Restart bootloader is with red, clicking it wont reboot the tablet, also recovery mode red, the only working button is the Start (green) but that leads to boot failure and power off.
pettymro said:
Use the volume up/down keys to navigate to "Recovery mode", then press the power button.
When the Android with the red exclamation point appears, hold down power first, followed quickly by volume down and volume up. (So that to start, you're holding down power, then you're holding down all three). After 2-3 seconds, release all three keys.
Use the volume up/down keys to select "apply update from ADB," then press power to select it.
On your computer, open up a command prompt or terminal window.
Using the command line, navigate to the folder containing the ADB executables and the update file.
type:
adb.exe sideload <update filename>
On my Nexus with Jelly 4.2 usb debugging is not enabled too, but I still get the option in recovery mode menu. Operation not succesful cause I cannot upgrade from 4.2 to 4.2. I will wait for another update and then try it again. Good luck!
Click to expand...
Click to collapse
recovery mode cannot be opened, the text font is red on the tablet and clicking it does nothing. :S
Also tried to completley flash the device but unable to. Going back and doing an fastboot oem unlock yields the same feedback.
Unlock Bootloader on 4.2
Hello, I was wondering if the bootloader in 4.2 can be unlocked the same way as it was on 4.1.2? I recently got a new nexus 7 and updated to 4.2.
Thanks and Cheers!
After some research into my issue, i have discovered that other users have posted "unbricking" solutions through a program called nvflash, when the device is put in APX mode. But unfortunatley i've yet to find a nvflash solution for nexus 7. I will experiment with the commands and what the others have reported as a solution.
ErnestoV31 said:
Hello, I was wondering if the bootloader in 4.2 can be unlocked the same way as it was on 4.1.2? I recently got a new nexus 7 and updated to 4.2.
Thanks and Cheers!
Click to expand...
Click to collapse
Yes it can.
Sent from my GT-I9300 using Tapatalk 2
Hello all! I'm having a problem with a Nexus 7.
This is my brother's tablet that he hasn't used in a few months. It hasn't been unlocked or rooted.
I can get to the boot screen with the android lying on it's back and the options with the volume buttons. The other info on that screen which might be pertinent:
Fastboot mode
Product name: grouper
variant - grouper
hw version - er3
bootloader version - n/a
serial number -
signing - not defined yet
lock stated - locked
When I go to recovery mode and push the power button, it says "booting failed" in the upper left. It still says Google in the middle, and has the options with the volume in the upper right, but the android is gone as is the text in the lower left.
I have adb and fastboot installed, but I can't seem to do much since the tablet is locked. I tried unlocking a few times, and it's always failed. Usually it doesn't give a reason, but one time I got this: "Failed (status read failed (Too many links))"
I've tried googling this and can't find someone with the same problem.
Anything I can try?
Thanks!
Nexus Tool Kit
rbeavers said:
Nexus Tool Kit
Click to expand...
Click to collapse
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?
swirv81 said:
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?
Click to expand...
Click to collapse
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.
swirv81 said:
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.
Click to expand...
Click to collapse
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.
ariesgodofwar said:
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.
Click to expand...
Click to collapse
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.
swirv81 said:
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.
Click to expand...
Click to collapse
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?
ariesgodofwar said:
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?
Click to expand...
Click to collapse
I was trying this with the command prompt. I could get fastboot to list the device when using that command. And the tablet and command prompt both say "unlocking" when doing that. I would assume that means the computer is seeing the tablet and everything is set up correctly?
I think I tried to unlock with the Toolkit, but I believe it told me that device needs to be in debugging mode.
Hey there, I'm having a similar problem.
My info is the same except my bootloader version is 4.18 and my lock state says it's unlocked. I tried to use the root kit but I'm having trouble with the fastboot device being detected. Driver solutions attempted were the google ones, and the pdanet ones. I can't really do the manual thing since that involves the device being recognized when plugged in, and since I can't enable usb debugging... anyways the automated drivers windows says were installed successfully so I don't really know what else to do.
Note: I do know the usb port on the tablet and computer work since when plugged in, it will show that its charging with the white battery icon.
Same issue here
I was in the process of upgrading manually from android 5.0 to 5.0.2 owing to the serious lag that came with lollipop. The OTA was taking longer and testing my patience as most apps were crashing due to lag.
Therefore decided to go for manual flashing of the image. I have never done this before. I was able to make the computer see my device by disabling mtp via storage under setting in the device. This is one thin I noticed to make the device visible to the computer.
After installing the device drivers my nexus was visible within the device manager but it couldn't be seen as an external storage until I played with the MTP. I had even unlocked the boot loader before all this.
So everything was going well and while I started to think all is well, I ran into this issue. From adb I tried to run 'flash-all.bat' from the new device image. Something went wrong somewhere - don't know what it is, but from then on, I am stuck in the fastboot screen or into recovery mode but when i try to boot the device bu hitting the power button - I get this message 'Booting failed'.
I am also trying to use NRToolkit but no use. When I connect my device it is seen in the device manager in my pc but cannot see it as a storage. Therefore when I now try to run the 'adb devices' command it cannot see my device. From what I saw initially, until I enable/disable mtp mode adb was not able to see my device to communicate.
Now when I tried NRT and installed the drivers once again, it is being detected in the device manager but when I run the driver test within NRT - I get a ADB device not found error. Within NRT all that it says is go into device setting>storage to enable it which I know but at the current status of my device in boot screen/recovery mode how can I go in to enable this. This is not helpful.
Somebody please suggest a workaround for this issue. I know I am close to the solution but not sure how to enable the MTP or at least made the NRToolkit to say 'ADB device found'.
My fastboot screen shows these details:
Fastboot mode
Product name grouper
Variant = grouper
HW Version – ER3
Bootloader version – 4.23
Baseband version – N/A
Serial number – 015d21d910141c0a
Signing – not defined yet
Lock State - unlocked
Please help.
Hi guys,
I recently dropped my Nexus 4 on the floor today and the screen cracked. As a result, the screen is completely unresponsive now but I am able to see its display when I press the power button. Could you guys help me/point me in the right direction regarding how to get the data I have on the phone (music, photos etc.) please.
My Nexus is unrooted/stock version. I tried connected it to my laptop via USB, but all it does it charge. I think I might have the USB debugging option enabled (as I remember enabling it before sometime ago). I'm running the latest firmware (5.0.1 I believe). Also the bootloader is locked.
Any help would be much appreciated.
Thanks
EDIT: I should note that I have a Password (PIN) for the lock screen.
I installed android sdk and tried to enter commands, but it didn't work. When I typed in 'adb devices', no serial came up (I checked sdk manager for the google usb driver, and it says it's installed). Also, when I tried typing in anything i.e. 'adb shell' it said error no devices found. I was attempting to follow a guide to set up adb for any other steps required to get my data from the internal storage. Bear in mind, I don't have much knowledge on these tools, all I'm doing is following any guides. Please can you help me how to get my photos or the contents of the sdcard.
The pin is not letting you boot into the os and that's why adb isn't working. Can you get into the bootloader? If so boot into twrp then try adb
fastboot boot twrp.img. Where twrp.img is the full file name.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
The pin is not letting you boot into the os and that's why adb isn't working. Can you get into the bootloader? If so boot into twrp then try adb
fastboot boot twrp.img. Where twrp.img is the full file name.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for responding. I can enter the bootloader (if that's the Volume Down + power button menu). Quick google search shows that twrp is for customer recovery. Bear in mind that I haven't unlocked the bootloader or installed anything like recoveries before (it is basically a stock N4). Would I need to install it? If so, please could you direct me to a tutorial or guide me step-by-step on what to do as I don't have too many ideas on what to do to get the data from the phone.
Just to clarify: My N4 is completely stock, Bootloader is locked (says 'LOCK STATE - locked' in bootloader menu) and it is unrooted. I remember having the USB debugging option enabled the last time I was in the dev menu on the phone.
oracle93 said:
Thanks for responding. I can enter the bootloader (if that's the Volume Down + power button menu). Quick google search shows that twrp is for customer recovery. Bear in mind that I haven't unlocked the bootloader or installed anything like recoveries before (it is basically a stock N4). Would I need to install it? If so, please could you direct me to a tutorial or guide me step-by-step on what to do as I don't have too many ideas on what to do to get the data from the phone.
Just to clarify: My N4 is completely stock, Bootloader is locked (says 'LOCK STATE - locked' in bootloader menu) and it is unrooted. I remember having the USB debugging option enabled the last time I was in the dev menu on the phone.
Click to expand...
Click to collapse
We'll you've got a problem. You'll have to unlock the bootloader to run fastboot commands and that'll completely wipe your device. And with the pin and an unresponsive screen you can't get into the os. There really isn't anything you're going to be able to do to save your files. Sorry about that.
Edit, just one more thought, are you still on 4.4.4? If so there may be a hope. Shoot, you'll need to boot into the os though. So my idea isn't going to work.
jd1639 said:
We'll you've got a problem. You'll have to unlock the bootloader to run fastboot commands and that'll completely wipe your device. And with the pin and an unresponsive screen you can't get into the os. There really isn't anything you're going to be able to do to save your files. Sorry about that.
Edit, just one more thought, are you still on 4.4.4? If so there may be a hope. Shoot, you'll need to boot into the os though. So my idea isn't going to work.
Click to expand...
Click to collapse
Ah that was what I feared ... I'm running the latest firmware (5.0.1). I wouldn't really care about the phone if it weren't for a few images (should have had it backed up!).
Now I need to decide whether or not to change the screen etc. for £35 or just look in the market for a new phone. If I did buy a new screen/digitiser/frame thing, would these be suitable (where I won't need to use heat guns or glue and stuff)?
ebay (dot) co.uk/itm/LCD-Screen-Display-Touch-Digitizer-for-LG-E960-Google-Nexus-4-Frame-Replacement-/331224787829?pt=UK_Replacement_Parts_Tools&hash=item4d1e892b75
OR
ebay (dot) co.uk/itm/For-LG-E960-Google-Nexus-4-LCD-Display-Digitizer-Touch-Screen-Frame-in-Black-/331227949021?pt=UK_Replacement_Parts_Tools&hash=item4d1eb967dd
Also, if I did change it using the above, would dissembling the phone and reassembling it cause my data to be lost?
Thank you for your help
Edit: I managed to save about 80 photos which were probably in the default images folder in the SD card using AndroidLost. I'm guessing the other images which were in other folders i.e. WhatsApp Images etc. aren't recoverable using the site
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken
There are few different versions of P9 Lite, look at the back of the phone to the bottom to see the numbers beside VSN and let us know.
1) Also when the phone is turned off plug in the usb to a computer or charging adapter
2) Hold down volume up & power
3) Let go of the power button when you feel the buzz while still holding the volume up button
4) Download latest version & recovery.
5) Go to Settings>Developer Options>USB Debugging On
5B) If you don't see Developer Options in settings, then go to Settings>About Phone>Build Number & ( tap the Build Number untill it unlocks)
6) Update us on the status, hope it works out.
GloryNation said:
There are few different versions of P9 Lite, look at the back of the phone to the bottom to see the numbers beside VSN and let us know.
1) Also when the phone is turned off plug in the usb to a computer or charging adapter
2) Hold down volume up & power
3) Let go of the power button when you feel the buzz while still holding the volume up button
4) Download latest version & recovery.
5) Go to Settings>Developer Options>USB Debugging On
5B) If you don't see Developer Options in settings, then go to Settings>About Phone>Build Number & ( tap the Build Number untill it unlocks)
6) Update us on the status, hope it works out.
Click to expand...
Click to collapse
tried to enter recovery, still not work. can't go to developer options because phone is stuck on logo, can't power off. couldn't find any solution that works anywhere, been searching for more than 6 hours, still no use. phone model is VNS-L21 forgot to mention earlier
What exactly were you doing before this happened and does your computer recognize your phone when plugged in at all.
Try holding volume up & down together & plug phone in when it reboots on you, & report back with what you see. If anything at all.
GloryNation said:
What exactly were you doing before this happened and does your computer recognize your phone when plugged in at all.
Try holding volume up & down together & plug phone in when it reboots on you, & report back with what you see. If anything at all.
Click to expand...
Click to collapse
I tried to install nougat update, computer recognizes it only in fastboot. holding volume buttons haven't changed anything still no progress. the thing is i had installed nougat a moth or so ago and it worked fine, then rolled back to marshmallow and now this. i'm pretty sure i tried to install correct package, because it was the same i had installed earlier
Did you download a adb tool on your computer that have the 'fastboot.exe' file? If so open that folder,
Have the mouse curser hover in that folder, hold down shift & right click the mouse
Open command prompt
Connect phone as is in fastboot mode
Type adb devices & press enter
Type adb continue & press enter
Hi,
I have the same issue as ellanyx.
my phone can only be stucked while booting or if I connect my phone to a computer, I'm able to boot it in fastboot.
as ellanyx, I didn't enable usb-debug nor OEM unlock option...
so when I'm in fastboot, I type the command "fastboot oem unlock xxxxxx" (hopefully the different data needed are the correct ones mentioned on the box of the phone) I get this error message:
C:\Users\Dieu\Downloads\SRKToolHuawei-STABLE-V1.3-20160619>fastboot oem unlock xxxxx
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
and off course the other options like "fastboot flash recovery recovery.img "... doesn't work.
I can't use the adb commands neither.
when I type the commande, as mentioned above, "adb devices" or "adb continue", nothing works.
So I'm a bit desesperate
do you have any solution for this kind of issue?
thanks
Dude, so the last firmware on your phone was MM or N? If it was MM you should put stock firmware appropriate for your model in dload folder on SD card and put volume+volume-power, and thats it. If you stack on N,....then I dont know because dload method doesnt work with N, or maybe works if you can find stock firmware with recovery for N.
Regards
Unfortunately I can't update with the 3 button update otherwise it would indeed solvemy problem.
pyromana said:
Unfortunately I can't update with the 3 button update otherwise it would indeed solvemy problem.
Click to expand...
Click to collapse
Probably you didnt have correct Oeminfo for MM if dload method didnt work....Try to conect phone with Toolkit and follow procedure for flashing oeminfo and custombin, after that flash stock recovrry and b161 via dload metod. You will find it on forum here.
Regards
the procedure from SRK toolkit?
would it be possible to provide it? because I can't unlock the OEM and I didn't tick the USB debug think.
Maybe problem with the ps not phone so u can not connect with adb
Try with different pc you must have flash oem with fast boot without enable adb from phone if u in fastboot
I can only boot my phone in fastboot (vol- + power) and not in recovery (vol+ + power).
also when using the SRK toolkit, the first screen tells me to be sure that the usb debugging is enable, which I haven't done...
if I'm not mistaken, fastboot is to use the fastboot command and recovery the adb commands
the connection with fastboot works on my computer, the link is made. however when I type the command to unlock the OEM, I get an error stating that the command is not allowed.
when I use the SRK toolkit, with the different questions, he tries to connect the phone with adb and waiting.... waiting...
is there a command to reboot in recovery but from fastboot? in the otherway around it exists but it doesn't seem that from fastboot to recovery it exists.
thanks.
Alexxxx1 said:
Dude, so the last firmware on your phone was MM or N? If it was MM you should put stock firmware appropriate for your model in dload folder on SD card and put volume+volume-power, and thats it. If you stack on N,....then I dont know because dload method doesnt work with N, or maybe works if you can find stock firmware with recovery for N.
Regards
Click to expand...
Click to collapse
dload method works on N. I downgraded my phone from unofficial N update back to official MM update using this method yesterday. You just have to enable OEM at developer options on settings.
It looks like people can't be bothered to read the 1st post properly before they reply.
HE CAN NOT BOOT TO ANDROID SO HE CAN NOT ENABLE OEM OR ACTIVATE USB DEBUGGING!!!!
What he CAN do, is go into eRecovery and Fastboot.
With that in mind, I would suggest using the dload method through fastboot.
Also, make sure it is Huawei SRK Tools 2.0 that is used, as it actually asks if you are in debug mode or fastboot.
Note that there is a few bugs in SRK 2.0:
The TWRP recovery file has the wrong filename in the package, so it WILL fail unless you name it correctly.
Also, when trying to root, do NOT use the "P9 Lite" method as that WILL fail too. Use the "P9/P9 Plus" method.
I am trying to set up a complete guide that can restore the phone when it is stuck in fastboot, however I apparently went a step too far...
ellanyx said:
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken[/QUOTE
Do you have TWRP recovery ?
---------- Post added at 09:55 AM ---------- Previous post was at 09:50 AM ----------
ellanyx said:
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken
Click to expand...
Click to collapse
Boot into fastboot mode and flash a custom recovery by meticulus. Link : meticulus.co.vu
Then whenyou get stuck hold power and vol down button for 2 minutes the phone will reboot and then when it says that your device has been unlocked and cant be trusted then only press vol up key ( dont press power button then). The u get into huawei recovery. From that u should power off the phone. Now get a custom rom by meticulus into your device sd card ( Cyanogenmod 13 is recommended ). Then insert sd card in a powered off phone. Now press vol up and power key and flash gapps and custom rom and you are good to go.
Click to expand...
Click to collapse
So, MY question:
I have tried 4 times to get Nougat installed, but every time I got the SMALL package (1.25gb) which means it is not complete.
I decided to try ONE more time, but think I have made a serious mistake.
I was on B161 and tried to downgrade to B160 without upgrading to Nougat first.
This has caused my phone to be stuck at boot with the message "Your device is booting now..."
I can NOT get into eRecovery or fastboot no matter what I do.
If I just leave the phone, then it discharge very fast, but as soon as I plug it in, it starts up and gets stuck at the same screen again.
Does anyone have ANY idea about how I can get out of this problem?
UPDATE:
I have managed to boot to fastboot while connected to my pc.
The phone is unlocked but FRP is LOCKED, which means I can't flash anything.
I read about using Miracle Loader to remove the FRP lock, but it can't "see" my phone. Maybe I am doing it wrong?
SnowmanDK said:
So, MY question:
I have tried 4 times to get Nougat installed, but every time I got the SMALL package (1.25gb) which means it is not complete.
I decided to try ONE more time, but think I have made a serious mistake.
I was on B161 and tried to downgrade to B160 without upgrading to Nougat first.
This has caused my phone to be stuck at boot with the message "Your device is booting now..."
I can NOT get into eRecovery or fastboot no matter what I do.
If I just leave the phone, then it discharge very fast, but as soon as I plug it in, it starts up and gets stuck at the same screen again.
Does anyone have ANY idea about how I can get out of this problem?
UPDATE:
I have managed to boot to fastboot while connected to my pc.
The phone is unlocked but FRP is LOCKED, which means I can't flash anything.
I read about using Miracle Loader to remove the FRP lock, but it can't "see" my phone. Maybe I am doing it wrong?
Click to expand...
Click to collapse
Try to relock and then unlock the bootloader again. And make sure oem unlocking is enabled in dev options
Arsaam said:
Try to relock and then unlock the bootloader again. And make sure oem unlocking is enabled in dev options
Click to expand...
Click to collapse
Please read my previous post again
I can NOT boot normally. And as FRP is locked, then I can't relock or unlock the bootloader.
SnowmanDK said:
Please read my previous post again
I can NOT boot normally. And as FRP is locked, then I can't relock or unlock the bootloader.
Click to expand...
Click to collapse
Go to fast boot mode and from their try to flash meticulus recovery.
You can also try the adb method as well.
Visit meticulus.co.vu
Hello...
I am looking for a working way to root my SM-T555
The device is running android 7.1.1;
base ver. "T555XXU1CQHA";
build ver. "NMF26X.T555XXU1CRG1";
Samsung experience 8.5;
Android security patch August 2017.
So far, the several attempts I made using every T55X related software I found in this website have been unsuccessful.
It would seem that the rooting software available is for "Marshmallow only", thus not Nougat specific,
though I read some comments stating that the TWRP made for MM worked on Nougat too and, after that, Magisk would/could do the job...
So I gave it a try but, after installing the recovery, my tablet got stuck every time: refused to boot normally
and if I turned it off, long pressing the power key, I couldn't turn it on again as if it was bricked.
Every time I had to re-start it in download mode and re-flash the original stock rom with Odin in order to have it working again.
On top of that, the "OEM unlock" key is not present in the developer mode list: none of the "date changing tricks" I found around the web seems to fit this model.
I am inclined to believe this "might" be the mother of my problems in rooting the device though, supposedly, the patches were not for Nougat, anyway...
The developer options page, once activated, can only be "turned off" ("greyed out") but cannot be deactivated;
while, on other devices, if you turn it off the page usually disappears after rebooting then you have to tap 7 times the build version, again, in order to make it appear.
I never had problems in rooting any of the phones and tablets I have /had, including an SM-T819 running Nougat 7.1.1,
thanks to the great job done by the coders in this community to whom I would like to express my appreciation for what they do for the benefit of us all.
But this thing seems to reject everything I throw at it and it's been the most stubborn "phone like object" I ever fought with.
So far I am the one loosing the fight... I wish some of you guys could give me the means to defeat it.
Thanks in advance to whoever may be available to help me out.
Flash TWRP, then install Magisk in TWRP.
V0latyle said:
Flash TWRP, then install Magisk in TWRP.
Click to expand...
Click to collapse
thanks for your reply.
maybe my post was too long and boring so you didn't read it all
Of course I already tried the solutions posted in the page you suggested but they did not work.
not the autoroot files, not the recovery, etc...
I quote: "after installing the recovery, my tablet got stuck every time: refused to boot normally
and if I turned it off, long pressing the power key, I couldn't turn it on again as if it was bricked.
Every time I had to re-start it in download mode and re-flash the original stock rom with Odin in order to have it working again."
If there is a TWRP file specific for my Nougat version available I'd be happy to give it a shot
endlessquest said:
thanks for your reply.
maybe my post was too long and boring so you didn't read it all
Of course I already tried the solutions posted in the page you suggested but they did not work.
not the autoroot files, not the recovery, etc...
I quote: "after installing the recovery, my tablet got stuck every time: refused to boot normally
and if I turned it off, long pressing the power key, I couldn't turn it on again as if it was bricked.
Every time I had to re-start it in download mode and re-flash the original stock rom with Odin in order to have it working again."
If there is a TWRP file specific for my Nougat version available I'd be happy to give it a shot
Click to expand...
Click to collapse
Did you follow a guide when flashing TWRP? Did you unlock your bootloader?
You need to be clear and concise in your posts as yo what you did and how.
V0latyle said:
Did you follow a guide when flashing TWRP? Did you unlock your bootloader?
You need to be clear and concise in your posts as yo what you did and how.
Click to expand...
Click to collapse
of course I did follow the guide by the book. also, the recovery appears to be installed properly, Odin showing a nice green PASS sign, but it doesn't work anyway
now about unlocking the bootloader, as I mentioned in my first post:
"the "OEM unlock" key is not present in the developer mode list: none of the "date changing tricks" I found around the web seems to fit this model.
I am inclined to believe this "might" be the mother of my problems in rooting the device"
every time I had to re install the system, so there clock want back to zero. Maybe I should be waiting for the allotted number of days to pass on order for the OEM unlock key to appear...
but before my first attempt to root the device, almost one month was past and the OEM unlock key wasn't there, notwithstanding...
I hope there was a chance that the bootloader was already unlocked...
to be concise (schematic):
tablet in download mode
untick auto reboot in Odin
AP loaded with "smt550_cf-autoroot.tar"
flash with Odin, OK, green sign PASS
reboot manually home+volume down+power,
then switch to volume up when screen becomes black
the Samsung logo appears and stays there indefinitely
So I turn the device off, long pressing the power key
then I try and turn on the tablet but does not turn on anymore,
not even pressing the power button for 30 second
then I press home+volume down+power again
to enter download mode and reinstall stock rom
(the same happens with
sm-t550_p550_p555_cf-autoroot.tar
or twrp_3.0.2-1_sm-t550_mm_7816.tar,
I also tried
twrp_3.1.1-1_sm-t355_251117
remark: none of them mentions T555 nougat)
Put your tablet in Download Mode and take a picture of the text at the upper left of the screen.
V0latyle said:
Put your tablet in Download Mode and take a picture of the text at the upper left of the screen.
Click to expand...
Click to collapse
What process did you follow to unlock your bootloader?
Stop trying to use Autoroot. Let's figure out what we need to do to get TWRP on your device. Once we do that, you can flash Magisk in TWRP for root.
Please read this guide, sections 1 through 4 (don't worry about the GSI stuff) and tell me what you have or have not done.
ok, I wasn't able to do this:
Unlock Bootloader
Enable Developer Options and turn on OEM Unlocking
OEM Unlocking is missing in the list, as I mentioned in my previous posts
I tried the date change trick but it didn't work
endlessquest said:
ok, I wasn't able to do this:
Unlock Bootloader
Enable Developer Options and turn on OEM Unlocking
OEM Unlocking is missing in the list, as I mentioned in my previous posts
I tried the date change trick but it didn't work
Click to expand...
Click to collapse
This is the first step. You cannot flash custom or modified images if the bootloader is locked.
Connect to the Internet and check for updates in system options, then check Developer Options again.
I did that step too, several times:
the system found an update available
the first times I cancelled the download
then I downloaded the update without installing it
then I tried and installed it
no result at all the attempts: the OEM Unlock key does not appear in developer options
endlessquest said:
I did that step too, several times:
the system found an update available
the first times I cancelled the download
then I downloaded the update without installing it
then I tried and installed it
no result at all the attempts: the OEM Unlock key does not appear in developer options
Click to expand...
Click to collapse
Has it ever appeared before?
V0latyle said:
Has it ever appeared before?
Click to expand...
Click to collapse
it is the first time I work on this specific device, so I couldn't tell: so far I couldn't find the OEM unlock option in the list
it never happened before on any of the several devices I have rooted in my life,
included another Samsung tablet SM-T819 running Nougat 7.1.1: the option was right there and all I had to do is tick it.
I used fastboot for other brands
I wish there was a way to use fastboot to unlock the bootloader on Samsung
if there is any I don't know it
adb is working, but when I give the "adb reboot fastboot" command, the tablet enters the download mode and fastboot does not see the tablet anymore from the computer
endlessquest said:
it is the first time I work on this specific device, so I couldn't tell: so far I couldn't find the OEM unlock option in the list
it never happened before on any of the several devices I have rooted in my life,
included another Samsung tablet SM-T819 running Nougat 7.1.1: the option was right there and all I had to do is tick it.
I used fastboot for other brands
I wish there was a way to use fastboot to unlock the bootloader on Samsung
if there is any I don't know it
adb is working, but when I give the "adb reboot fastboot" command, the tablet enters the download mode and fastboot does not see the tablet anymore from the computer
Click to expand...
Click to collapse
Samsung devices do not have a fastboot mode.
Since this is a Snapdragon device, it probably cannot be unlocked, especially if it was marketed in the US.
Only Exynos and international Snapdragon devices can be unlocked, unfortunately.
V0latyle said:
Samsung devices do not have a fastboot mode.
Since this is a Snapdragon device, it probably cannot be unlocked, especially if it was marketed in the US.
Only Exynos and international Snapdragon devices can be unlocked, unfortunately.
Click to expand...
Click to collapse
actually I am in Rome, Italy so I am quite positive it was marketed here...
is there a way to know for sure whether or not it is international?
the Samsung SM-T819 I am writing from has a snapdragon chip
but I had no problem unlocking/rooting it,
I bought both the devices here in Rome
now that's a mystery...
endlessquest said:
actually I am in Rome, Italy so I am quite positive it was marketed here...
is there a way to know for sure whether or not it is international?
Click to expand...
Click to collapse
Usually the model number is a good indication with phones - the G908U vs G908N for example, but I don't see that being the case here
Have you tried signing into a Samsung or Google account on the device before checking for updates and looking for OEM Unlocking?
V0latyle said:
Usually the model number is a good indication with phones - the G908U vs G908N for example, but I don't see that being the case here
Have you tried signing into a Samsung or Google account on the device before checking for updates and looking for OEM Unlocking?
Click to expand...
Click to collapse
I did that too...
on a freshly installed rom:
I connected the internet thru wireless
signed into my Google account
completed the tablet configuration, etc
then I went and enable the developer options
no OEM Unlocking yet again...
endlessquest said:
I did that too...
on a freshly installed rom:
I connected the internet thru wireless
signed into my Google account
completed the tablet configuration, etc
then I went and enable the developer options
no OEM Unlocking yet again...
Click to expand...
Click to collapse
You manually checked for an update too?
Did you try disconnecting from the Internet, disabling network time, and manually setting the time ahead 1 week?