Related
I rooted as soon as I got my N7 because I wanted to be able to use USB OTG to watch movies during my long flights a few weeks ago. Now I'm using mskip's tool kit to get back to stock (sending it to Asus because of the screen flicker and touchscreen issues).
I tried to download, extract and flash the stock rom and then re-lock the bootloader. After doing this, it wouldn't load. I can get to the bootloader, and managed to unlock it again, but I can't get it to flash the stock rom and thus it won't boot. When I select "Start", it says "booting failed". It also won't let me flash any of the recovery images included in the utility. I'm not exactly well versed in rooting and now I'm stuck.
Please help if you can. Thank you.
If You Have SuperUser Or SuperSU I believe, you could easily unroot it from the settings. As to locking the bootloader, there is a toolkit program and the link is: http://forum.xda-developers.com/showthread.php?t=1766475 With this you could go back to stock if you wish. You could also use a SDK Command prompt thing to lock the bootloader.
EDIT: I forgot you can't boot up. But you could still use the Toolkit program.
Ryan35310 said:
If You Have SuperUser Or SuperSU I believe, you could easily unroot it from the settings. As to locking the bootloader, there is a toolkit program and the link is: http://forum.xda-developers.com/showthread.php?t=1766475 With this you could go back to stock if you wish. You could also use a SDK Command prompt thing to lock the bootloader.
EDIT: I forgot you can't boot up. But you could still use the Toolkit program.
Click to expand...
Click to collapse
I tried that toolkit several times, but it doesn't work. Everytime I try to flash stock+ unroot I get this message:
"md5sum.exe- System Error
The program can't start because libintl3.dll is missing from your computer. Try reinstalling the program to fix this problem."
No idea what that means.
Use wugfreshs toolkit much better. IMO and i don't use toolkits normally but it was a snap. Also for locking the boot loader its fastboot OEM lock.
Sent From My Toro+ via White Tapatalk
ÜBER™ said:
Use wugfreshs toolkit much better. IMO and i don't use toolkits normally but it was a snap. Also for locking the boot loader its fastboot OEM lock.
Sent From My Toro+ via White Tapatalk
Click to expand...
Click to collapse
I was able to get Wugfresh's toolkit working after re-downloading it for the 3rd time and it is able to flash the bootloader but the next lines of text say:
EOCD not found, not zip error..... and then a bunch of nonsensical symbols.
Tried again this morning... still stuck at the same point. Any ideas guys?
Did you install the drivers for it? Did you try using the PDAnet drivers? Can you post a screenshot or picture of the error? Also are you making sure the device is on with USB Debugging enabled? I never got any errors try following this Video.
He can't go to USB Debugging because he can't boot up I think.
Ryan35310 said:
He can't go to USB Debugging because he can't boot up I think.
Click to expand...
Click to collapse
That is correct. I've attached a screenshot of what I was describing earlier. It looks like what I would imagine Transformer language in written form to look like.
Great googly moogly I got it to work! I had to download the stock image directly from Google... again and select the file manually along with inputting the MD5 checksum. So if you're having issues like I was, try this!
Thank you to everyone that tried to troubleshoot my problems and a big Thank You to WugFresh for his toolkit :good:
So I had the latest version of Paranoid Android on my rooted nexus 10. The keyboard was messing up so i wanted to run a factory reset and go all the way back to stock 4.2.1. In the process I accidentally wiped both the Rom and stock from my nexus 10 leaving it with no OS and nothing but the boot-loader. If i try and go to recovery mode all i get is the android laying down with an exclamation mark in a red triangle in it's stomach or the word Google with and unlocked padlock underneath it.
Any advice/help would be amazing! Thanks!
Download the factory image from Google: https://dl.google.com/dl/android/aosp/mantaray-jop40c-factory-0d641789.tgz
If you don't have fastboot already you need that too: http://downloadandroidrom.com/file/tools/fastboot.zip
Unzip the factory image tgz I linked to with 7zip/winrar etc
Unzip the fastboot.zip contents into the folder you just extracted
open a command prompt in the folder you just unzipped (mantaray-jop40c)
Boot your device into the bootloader by holding down BOTH volume keys and the power button
Connect your Nexus 10 to your PC
At the command prompt type
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader [wait for the device to reboot back to the bootloader]
fastboot -w update image-mantaray-jop40c.zip
This will wipe, repartition and install 4.2 straight from Google back to your device.. You will be prompted to update by Google to install the 4.2.1 update shortly after you boot up.
If you didn't have Fastboot already and had to download the zip I linked to, it's highly suggested to download and install the Android SDK so you have it and more native tools at your disposal. You can do that after the fact though and optional but highly suggested if you plan on learning your device more.
Will this work even if my device WAS Android 4.2.1 JOP40D?
Jamocobi said:
Will this work even if my device WAS Android 4.2.1 JOP40D?
Click to expand...
Click to collapse
Yep.
styckx said:
Yep.
Click to expand...
Click to collapse
Awesome thanks, I'll give it a shot once the files downloaded!
You're welcome. You should be fine.. This will start you right back at square one w/ an unlocked bootloader. You won't have a custom recovery or anything like that but you'll be back at a good starting point if you ever want to go that route again.
If you want to lock your bootloader again. After the device boots into Android reboot back to the bootloader one more time and type
fastboot oem lock
styckx said:
You're welcome. You should be fine.. This will start you right back at square one w/ an unlocked bootloader. You won't have a custom recovery or anything like that but you'll be back at a good starting point if you ever want to go that route again.
If you want to lock your bootloader again. After the device boots into Android reboot back to the bootloader one more time and type
fastboot oem lock
Click to expand...
Click to collapse
Awesome. Thanks so much! Unfortunately the command prompt is just stuck on "sending 'bootloader' <1280KB>..."
It's been over 4 minutes now which doesn't seem right, any ideas?
Jamocobi said:
Awesome. Thanks so much! Unfortunately the command prompt is just stuck on "sending 'bootloader' <1280KB>..."
It's been over 4 minutes now which doesn't seem right, any ideas?
Click to expand...
Click to collapse
How did you unlock and root this device in the first place?
styckx said:
How did you unlock and root this device in the first place?
Click to expand...
Click to collapse
With the WugFresh Nexus Root Toolkit (Sorry, Can't post a link yet)
styckx said:
How did you unlock and root this device in the first place?
Click to expand...
Click to collapse
Okay so after messing around with restarting bootloader i redid the script in command prompt and it is now back to factory settings, thank you so much!
Jamocobi said:
Okay so after messing around with restarting bootloader i redid the script in command prompt and it is now back to factory settings, thank you so much!
Click to expand...
Click to collapse
Figures. I had a long post written up to help you out. ha ha.. Good on ya for figuring it out..
I'm aware of the toolkit and situations like this is why I hate them. Users press a few buttons and `magic happens'.. When that user gets in trouble they now have no idea how to reverse what they did because there is no "Undo the magic" button and they learned nothing from the initial unlocking process because some toolkit did it for them.. Nexus devices can be unlocked and flashed with Google provided tools. Now that you manually did it you probably have a better overall idea of the actual process that is taking place. The more you do it manually, the more it becomes second nature. It's not even all that complicated. It's just a different way of copying files and erasing data.
One thing.. You NEVER.. EVER.. EVER... EVER... want to do is type this
fastboot erase bootloader
^ That is the quickest and easiest way to permanently brick your device.. If anyone ever suggests you do that.. Don't...
styckx said:
Figures. I had a long post written up to help you out. ha ha.. Good on ya for figuring it out..
I'm aware of the toolkit and situations like this is why I hate them. Users press a few buttons and `magic happens'.. When that user gets in trouble they now have no idea how to reverse what they did because there is no "Undo the magic" button and they learned nothing from the initial unlocking process because some toolkit did it for them.. Nexus devices can be unlocked and flashed with Google provided tools. Now that you manually did it you probably have a better overall idea of the actual process that is taking place. The more you do it manually, the more it becomes second nature. It's not even all that complicated. It's just a different way of copying files and erasing data.
One thing.. You NEVER.. EVER.. EVER... EVER... want to do is type this
fastboot erase bootloader
^ That is the quickest and easiest way to permanently brick your device.. If anyone ever suggests you do that.. Don't...
Click to expand...
Click to collapse
Sorry about that, i was hoping you'd see it in time! You're definitely right about that, i was just worried i would totally mess it up if i did it myself but i can do that anyway with a toolkit so next time ill give it a shot without one.
Okay thanks, I'll take note of that one for sure! Really appreciate the help, thought i was doomed! haha!
You're welcome man.. It's no fault of your own for using the toolkit. To new users they're attractive and promise quick results.
Side note. It's extremely, insanely, stupidly hard to permanently screw up a Nexus device by flashing. There is always a way back from `the grave'.
Take care
Hello ladies and gents,
So I'm a total noob and I think I bricked my phone.
I got root by using the motochopper tool
then I went for custom recovery, but I think I flashed the verizon version instead of the ATT version (I was trying to install the Google Wallet fix with a custom rom)
Rebooted the phone, I get an unlock symbol and samsung custom
I can boot into recovery mode and I still have root access / command line.
The phone either boots to black screen with a oscillating blue light or if I go into the other mode it says 'downloading'
Anything I can do to get my phone back working? Did I totally brick it?
Yes, if you see anything on the screen, that would be a soft brick, you are getting the unauthorized screen, then you need another kernel for sure, lets start there...
You really should either put your device in your information screen or tell us what type of device you have, that is very important.
I can not tell you what kernel, not knowing what device has the problem.
I see you mentioned att, is it US or Canadian version?
These are a must when you are seeking help.
I have the AT&T US Version of the S4, 1337
And now it seems I've made it worse, I reinstalled a new Rom, now I can't boot into recovery at all. It goes blank after the Samsung custom screen. Still can ADB into it though.
TheAxman said:
Yes, if you see anything on the screen, that would be a soft brick, you are getting the unauthorized screen, then you need another kernel for sure, lets start there...
You really should either put your device in your information screen or tell us what type of device you have, that is very important.
I can not tell you what kernel, not knowing what device has the problem.
I see you mentioned att, is it US or Canadian version?
These are a must when you are seeking help.
Click to expand...
Click to collapse
Do you have any type backup? Have you tried, power off phone. hold down power button and volume up at same time, when it vibrates, let go of the power button, it should go into recovery, and lets try restoring your backup.
Your problem is you have the wrong kernel loading, flash a ATT kernel once in the recovery, it will boot.
willenglishiv said:
I have the AT&T US Version of the S4, 1337
And now it seems I've made it worse, I reinstalled a new Rom, now I can't boot into recovery at all. It goes blank after the Samsung custom screen. Still can ADB into it though.
Click to expand...
Click to collapse
Just ODIN flash the stock firmware for ATT I337 and re-root? That's what I would try.
blyndfyre said:
Just ODIN flash the stock firmware for ATT I337 and re-root? That's what I would try.
Click to expand...
Click to collapse
Actually Ax has the best solution if he can get to recovery... your way will work but by far to many steps for something that simple...
just saying!!
sloanster said:
Actually Ax has the best solution if he can get to recovery... your way will work but by far to many steps for something that simple...
just saying!!
Click to expand...
Click to collapse
I agree Ax's solution is simpler, but OP said that he cannot boot to recovery.
And now it seems I've made it worse, I reinstalled a new Rom, now I can't boot into recovery at all. It goes blank after the Samsung custom screen. Still can ADB into it though.
Click to expand...
Click to collapse
blyndfyre said:
I agree Ax's solution is simpler, but OP said that he cannot boot to recovery.
Click to expand...
Click to collapse
But he can adb so he can push the kernel onto his phone and flash in recovery
Edit: my bad, he did say he can't boot into recovery. Odin is his best bet.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
he hasn't answered the get into recovery yet, nor has he said he has a backup. I was trying a simple solution. Then we can move on to the odin back.
TheAxman said:
he hasn't answered the get into recovery yet, nor has he said he has a backup. I was trying a simple solution. Then we can move on to the odin back.
Click to expand...
Click to collapse
Hope it gets it worked out!!!
The main thing is he's got options...:angel:
Hey Guys,
Hoping someone can help here, I have followed various tutorials I have found on the internet to try and restore my Nexus 7 back to its factory state after it one day decided to never get past the white Google logo.
Inevitably I ended up on this tutorial as the only one where I seemed to get any kind of a link and response with the tablet: blog.laptopmagDOTCOM/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
basically it got as far as trying to Unlock the Bootloader, but it fails to do so. I do get the popup on the tablet asking if I want to unlock it but nothing happens, it remains locked after I click Yes. My command line saying that it Failed.
All other tutorials seem to assume you can access the OS and enable debug mode but of course I cannot. I cannot even do a Factory Reset, every options eventually leading me to a white Google logo.
I also cannot get into recovery mode, im just stuck on the screen with the green android and the option to Start, Recovery mode etc all just lead to the Google logo.
The impression I have gotten from not being able to unlock the bootloader is that there must be a hardware failure? could anyone suggest some black magic I might be able to do to fix it? I realise at some point I should cut my losses. I had also wondered if it was worth buying a new motherboard/logic board?
Would appreciate any help.
Cheers,
Matt.
Have you tried this tools:
http://forum.xda-developers.com/showthread.php?t=1766475
or
http://forum.xda-developers.com/showthread.php?t=1809195
Both are magic tools for nexus 7, please read any explanation carefully!
It may help you :good:
ju1da said:
Have you tried this tools:
http://forum.xda-developers.com/showthread.php?t=1766475
or
http://forum.xda-developers.com/showthread.php?t=1809195
Both are magic tools for nexus 7, please read any explanation carefully!
It may help you :good:
Click to expand...
Click to collapse
Wow.....
Please stop spamming the toolkits.
The op has indicated that there is a hardware issue because the bootloader unlock isn't working.. A stupid toolkit isn't going to fix that. You should are promoting people to use their damn brains and doing it the right way, but laziness prevails, eh?
To the op, sorry but it sounds like you have a corrupt emmc. If the unlock process fails to commit, that's a bad sign.
Sent from my Nexus 5
Also to the op, USB debugging has nothing to do with the bootloader or recovery, only a booted os. Can you boot to recovery from the bootloader?
Sent from my Nexus 5
Hello all,
Anybody can help me, my problem is that my nexus 6p stuck on google screen (boot-loop), noting that unfortunately the boot-loader is locked . I've tried different solutions but non of the worked.
What to do please???
GlorySy said:
Hello all,
Anybody can help me, my problem is that my nexus 6p stuck on google screen (boot-loop), noting that unfortunately the boot-loader is locked . I've tried different solutions but non of the worked.
What to do please???
Click to expand...
Click to collapse
Install Wugfresh or any other toolkit of your choice to your PC, install drivers, install stock rom, follow onscreen instructions, done.
superviked said:
Install Wugfresh or any other toolkit of your choice to your PC, install drivers, install stock rom, follow onscreen instructions, done.
Click to expand...
Click to collapse
This won't work. The bootloader is locked and he has no way to unlock it.
GlorySy said:
Hello all,
Anybody can help me, my problem is that my nexus 6p stuck on google screen (boot-loop), noting that unfortunately the boot-loader is locked . I've tried different solutions but non of the worked.
What to do please???
Click to expand...
Click to collapse
Can you get into the stock recovery?
@GlorySy, you seem on the same issue as this. Please have a look and confirm it is what we got to worry. http://forum.xda-developers.com/nexus-6p/help/main-board-failure-story-t3409400
Not applicable
superviked said:
Install Wugfresh or any other toolkit of your choice to your PC, install drivers, install stock rom, follow onscreen instructions, done.
Click to expand...
Click to collapse
I cannot install any thing with locked boot loader :crying:
Yes
Heisenberg said:
Can you get into the stock recovery?
Click to expand...
Click to collapse
Yes I can, but can do nothing except for turn off the device. :crying:
GlorySy said:
Yes I can, but can do nothing except for turn off the device. :crying:
Click to expand...
Click to collapse
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 13 to adb sideload one of the full OTA zips.
Heisenberg said:
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 13 to adb sideload one of the full OTA zips.
Click to expand...
Click to collapse
I just started having this same issue.
I can't get into recovery from the bootloader in order to perform section 13. Once hit recovery, it's back to looping boot screen with white Google text.
Just got finished with Google phone support. They're sending me a new device. It must be a hardware failure.
Background: I got OTA notification on Friday night. I downloaded and hit install. Then after a while it said there was an upgrade error, and to please try again. But it was going to have to download the 1+ GB OTA file again, so I just said screw it, i'll do it later. Here am I 2 days later with a broken phone. Thinking this has to be related.
Stock phone, locked bootloader. Running 6.0.1
GlorySy said:
Hello all,
Anybody can help me, my problem is that my nexus 6p stuck on google screen (boot-loop), noting that unfortunately the boot-loader is locked . I've tried different solutions but non of the worked.
What to do please???
Click to expand...
Click to collapse
busbeepbeep said:
I just started having this same issue.
I can't get into recovery from the bootloader in order to perform section 13. Once hit recovery, it's back to looping boot screen with white Google text.
Click to expand...
Click to collapse
Please join this thread to help troubleshoot.
I am hoping to collect enough data to figure out a solution for all effected.
is your BL locked and device encrypted?
When you try to load recovery, does it ask for password?
try entering your last google account email password if so.
Help!! Stuck in Google screen
Heisenberg said:
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 13 to adb sideload one of the full OTA zips.
Click to expand...
Click to collapse
Hi Heisenberg,
I ran into this problem today with my phone stuck on Google screen. I tried to use your guide and put my phone in recovery but it just goes back to rebooting and just shows the "Google" logo so if I can't get the phone into recovery then I won't be able to use your guide right? Is these any other way to solve this problem or am I screwed?
Also how can this problem be prevented in the future if I got new phone under warranty? Do I root and flash pure Nexus ROM and backup images?
Thanks,
Azeem00 said:
Hi Heisenberg,
I ran into this problem today with my phone stuck on Google screen. I tried to use your guide and put my phone in recovery but it just goes back to rebooting and just shows the "Google" logo so if I can't get the phone into recovery then I won't be able to use your guide right? Is these any other way to solve this problem or am I screwed?
Also how can this problem be prevented in the future if I got new phone under warranty? Do I root and flash pure Nexus ROM and backup images?
Thanks,
Click to expand...
Click to collapse
Hello... Try to look here:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
For your second question, it's hard to tell... Making regular backups may help protecting your datas, but can't help your new phone to start acting crazy...
I have been doing weekly backups to my pc. I backup my TWRP, TBU, Super Backup, DCIM and download directories.
Sent from my Nexus 6P using XDA-Developers Legacy app
Heisenberg said:
Go to my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 13 to adb sideload one of the full OTA zips.
Click to expand...
Click to collapse
Any ideas are any solution when I have custom rom?
EDIT: Not needed, seems that wife phone has motherboard problem because now it will stuck in TWRP screen.
I am pretty sure I had this problem before. Actually within hours of purchasing and rooting. Lol go into fastboot and install factory images. If you were able to get into recovery you could use adb to oem unlock.. but that doesn't sound like an option.
My phone died last night in a bootloop death. Thankfully here in the UK we have a 2 year warranty so Huawei are taking it back. I mentioned "bootloop issue" and the tech guy stopped asking the standard stuff and just sent me a returns bag.
Try this:
https://forum.xda-developers.com/nexus-6p/general/confirmed-hardware-defects-nexus-6p-t3610405
Quickly enable bootloader unlocking, then follow the tutorials already known for 4-core recovery
Well I've now got a different phone back from Huawei as they told me they no longer have replacement motherboards available.
Sent from my MHA-L29 using Tapatalk