[SOLVED] My Nexus 7, helpless or still hope? - Nexus 7 Q&A, Help & Troubleshooting

Hi guys, first at all, I'm noob with android, and I'm trying to root+up room for my first android device : the Nexus 7.
I used Nexus root tool kit 1.6.3 to unlock and root successfully my device; however, when I tried to up rom for the device, I screwed up everything. I tried Smooth room first and stuck with the "boot loop" screen :
"The green robot with the green circle around"_I can't upload pics because I have less than 10 post.
Luckily I could use Nexus root tool kit to restore my device to factory setting. But I decided to give it a try one more time with the other rom, the ATOM flash rom. This time after I swipe out all factory data, catch data.... the installer say "fail to install" and give me the option to: "try again", "swipe data again", "reboot". I choice "reboot" and this time the screen stuck at this :
"The white word GOOGLE in the middle and the CLOCK in the middle end"
I tried to reset to factory setting like before but I wasn't that lucky this time, the Nexus root tool kit keep saying "ADB device was not found". (noticed that I already have the right driver for the device because ADB was found before).
Right now I can return to bootloader by holding power button and volume down button, but I can't do anything else.
Please, people, can anyone help me with this? I really need some help here.
Thanks.

quocviet114 said:
Hi guys, first at all, I'm noob with android, and I'm trying to root+up room for my first android device : the Nexus 7.
I used Nexus root tool kit 1.6.3 to unlock and root successfully my device; however, when I tried to up rom for the device, I screwed up everything. I tried Smooth room first and stuck with the "boot loop" screen :
"The green robot with the green circle around"_I can't upload pics because I have less than 10 post.
Luckily I could use Nexus root tool kit to restore my device to factory setting. But I decided to give it a try one more time with the other rom, the ATOM flash rom. This time after I swipe out all factory data, catch data.... the installer say "fail to install" and give me the option to: "try again", "swipe data again", "reboot". I choice "reboot" and this time the screen stuck at this :
"The white word GOOGLE in the middle and the CLOCK in the middle end"
I tried to reset to factory setting like before but I wasn't that lucky this time, the Nexus root tool kit keep saying "ADB device was not found". (noticed that I already have the right driver for the device because ADB was found before).
Right now I can return to bootloader by holding power button and volume down button, but I can't do anything else.
Please, people, can anyone help me with this? I really need some help here.
Thanks.
Click to expand...
Click to collapse
Get the FACTORY IMAGE for your device from here...
https://developers.google.com/android/nexus/images
Unzip to the folder wherever your FASTBOOT.EXE and ADB.EXE files are located and run the FLASHALL script... and with the device in BOOTLOADER mode.
This should reflash back to stock.
Rgrds,
Ged.

GedBlake said:
Get the FACTORY IMAGE for your device from here...
Unzip to the folder wherever your FASTBOOT.EXE and ADB.EXE files are located and run the FLASHALL script... and with the device in BOOTLOADER mode.
This should reflash back to stock.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you for the reply but where are the files FASTBOOT.EXE and ADB.EXE located? I can't access to the internal storage of the device, and how to run the Flashall script?

There have been many similar cases like yours on this forum and I see it usually after the use of toolkits. Not that toolkits are badly written, but people who usually use them don't know what to do when things go wrong. As long as you can get into bootloader mode (=fastboot mode), you can restore your device with fastboot. Take this time to learn a bit about your device and the two only programs you'll ever need for it: ADB and FASTBOOT. You use fastboot when in bootloader mode and adb outside the bootloader.
Use this sticky to return to stock: http://forum.xda-developers.com/showthread.php?t=1907796 . You can skip a few steps in it though. For example, if your drivers are already set up and you have adb en fastboot somewhere (you can find them somewhere in the installation folder of the toolkit) then you don't need to download java and the android SDK. You also don't need to reflash the bootloader if you already use the latest version. Just read and think while you follow one of the best guides you can find on this forum.
To learn more about adb and fastboot, just type the name of the program in a terminal window and you will see a list with all commands associated with it. My recommendation is to flash a custom recovery (for example TWRP): you can type fastboot flash recovery name of recovery. You can use TWRP to root your device afterworths (TWRP will present you with a warning when you reboot your device through it). You can also make nandroid backups with it. In the future, make nandroid backups, because they will help you when you soft brick your device again.
Good luck!

quocviet114 said:
Thank you for the reply but where are the files FASTBOOT.EXE and ADB.EXE located? I can't access to the internal storage of the device, and how to run the Flashall script?
Click to expand...
Click to collapse
FASTBOOT.EXE and ADB.EXE are part of the Android SDK and as such should be on your PC... so you don't need to access internal storage on your Nexus 7.
(In fact you can't, if the N7 is in BOOTLOADER MODE, which of course it needs to be to flash back to STOCK).
The Flash-all script is part of the Factory image, and is run in a COMMAND PROMPT window... to completely reflash back to STOCK.
-----
The toolkit you're using must use FASTBOOT to accomplish flashing... so you must have FASTBOOT somewhere on your PC.
Rgrds,
Ged.

Are you using twrp to flash your custom rom? Some of the custim rom must be flash it with cwm.
Try to install cwm thru fastboot or adb. Then flash again.
Good luck mate.
Sent from my GT-N7100 using xda premium

I'll try your instruction as soon as I go back from work. Thank a lot you guys. I appreciated!

I did it! Thank you so much everyone! I think just root and use the stock rom is ok with me, I don't want to risk again!

quocviet114 said:
I did it! Thank you so much everyone! I think just root and use the stock rom is ok with me, I don't want to risk again!
Click to expand...
Click to collapse
Awesome! Hopefully it was an informative (an maybe even fun) experience.
Also, as long as pushing all three buttons on the side of your nexus simultaniously (for up to 15 or more or less) seconds enters bootloader/fastboot mode, nothing is ever bricked and your nexus can (almost allways) be safed. The only ways to really hard brick and ruin your nexus is to flash wrong or corrupt bootloaders (so always be extra carefull if that ever needs to happen).

quocviet114 said:
I did it! Thank you so much everyone! I think just root and use the stock rom is ok with me, I don't want to risk again!
Click to expand...
Click to collapse
Well, that's very good news indeed, quocviet114... glad you got it sorted.
I remember when I was a beginner and had similar issues to yours,... upon resolution, the relief was palpable.
-----
ps. you should edit your thread title to include the word SOLVED...
Rgrds,
Ged.

Related

[Q] Nexus 7 Booting Failed & No ADB Connection

Hi Guys
Another rooting/flashing noob here that's messed up his N7 sorry
I know there's other threads with similair issues but they all advise fixes involving using adb connection and usb debugging which I cannot do (explained below)
My device will turn on, it goes to the google logo with the green start icon, I can select and go into bootloader and recovery, if I press start it says booting failed in the upper left corner and will go no further.
My device is plugged in via usb, i have the latest rookit 1.5.5, and sdk installed etc, i also have the naked drivers and the factory images from google on my pc.
The machine came with 4.1.2 installed (nakasi-jzo54k).
To mess it up, somewhere in between updating to 4.2, rooting and unrooting it, and flashing it i must have done something wrong but being a happy button bashing noob I don't know what exactly...
And yes I also didn't make a backup of any kind because well I'm just a moron and lesson well learnt.
So yeah, I have no adb connection, can't go into debuging mode and it won't boot.
Does anybody know if there is anyway I can restore my tablet please? Any help would be hugely appreciated!
Many thanks
greyphox said:
Hi Guys
Another rooting/flashing noob here that's messed up his N7 sorry
I know there's other threads with similair issues but they all advise fixes involving using adb connection and usb debugging which I cannot do (explained below)
My device will turn on, it goes to the google logo with the green start icon, I can select and go into bootloader and recovery, if I press start it says booting failed in the upper left corner and will go no further.
My device is plugged in via usb, i have the latest rookit 1.5.5, and sdk installed etc, i also have the naked drivers and the factory images from google on my pc.
The machine came with 4.1.2 installed (nakasi-jzo54k).
To mess it up, somewhere in between updating to 4.2, rooting and unrooting it, and flashing it i must have done something wrong but being a happy button bashing noob I don't know what exactly...
And yes I also didn't make a backup of any kind because well I'm just a moron and lesson well learnt.
So yeah, I have no adb connection, can't go into debuging mode and it won't boot.
Does anybody know if there is anyway I can restore my tablet please? Any help would be hugely appreciated!
Many thanks
Click to expand...
Click to collapse
If you got half way through rooting, what has happened to your ADB?
Try the option "Return to stock and Flash stock image" try that.
What message does ADB give you etc?
Wilks3y said:
If you got half way through rooting, what has happened to your ADB?
Try the option "Return to stock and Flash stock image" try that.
What message does ADB give you etc?
Click to expand...
Click to collapse
Hi thanks
Well when I run 'adb devices' in dos the device does not come up, blank etc
but if in the advanced utilities section of the rookit it will reboot it and say connected etc when i try to boot/flash image for bootloader, system, recovery etc but always goes back to google logo and won't boo up, can still get into bootloader and recovery though
i fully rooted it and unrooted it, i tried to flash 4.1.1 to see if i could thats when this all started
if i try flash stock + unroot option (device is on/normal) sub option the rootkit tries to check adb status and says not connected etc which makes sense as dos won't detect it, if this helps in device manager its coming up as...
samsung android phone
android bootloader interface
so i that driver in rootkit to manually install the naked drivers in device manager and it will say they are up to date etc
so the advanced utilities section for boot/flash image will communicate but no other.....
flash stock root used to detect it but even then in dos it would give me the 'too many links error'
I just hope there is a solution.... and i hope all that makes sense sorry
Cheers
greyphox said:
Hi thanks
Well when I run 'adb devices' in dos the device does not come up, blank etc
but if in the advanced utilities section of the rookit it will reboot it and say connected etc when i try to boot/flash image for bootloader, system, recovery etc but always goes back to google logo and won't boo up, can still get into bootloader and recovery though
i fully rooted it and unrooted it, i tried to flash 4.1.1 to see if i could thats when this all started
if i try flash stock + unroot option (device is on/normal) sub option the rootkit tries to check adb status and says not connected etc which makes sense as dos won't detect it, if this helps in device manager its coming up as...
samsung android phone
android bootloader interface
so i that driver in rootkit to manually install the naked drivers in device manager and it will say they are up to date etc
so the advanced utilities section for boot/flash image will communicate but no other.....
flash stock root used to detect it but even then in dos it would give me the 'too many links error'
I just hope there is a solution.... and i hope all that makes sense sorry
Cheers
Click to expand...
Click to collapse
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
nexus toolkit from dev section
ngoralph said:
nexus toolkit from dev section
Click to expand...
Click to collapse
Have you even read what hes said?
He's already tried the toolkit...
Wilks3y said:
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
Click to expand...
Click to collapse
The first step in the full driver guide in wugs kit is to enable usb debugging which i cannot do though as it won't power on.......
I have added the environmental variabes before yes sorry, qbkings utube vids showed me how to do that
Just tried these steps
toolkit home screen, flash stock + unroot (softbricked bootloop)
then naksaki 4.2 jzo54k, auto download and extract.
it got to dos stage and i get 'Failed bootloader is locked'
??? thanks again
Wilks3y said:
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
Click to expand...
Click to collapse
OK unlocked it via the main unlock option on rootkit and it unlocked ok, so im now re-trying te softbricked option to flash etc and its currently.. writing system...
greyphox said:
OK unlocked it via the main unlock option on rootkit and it unlocked ok, so im now re-trying te softbricked option to flash etc and its currently.. writing system...
Click to expand...
Click to collapse
Sounds good mate !
Need any extra help drop us a PM I'd be happy to lend a hand.
Wilks3y said:
Sounds good mate !
Need any extra help drop us a PM I'd be happy to lend a hand.
Click to expand...
Click to collapse
MOOOOOO!
It wrote to the system ok and now its hanging on erasing user data, googled and its happend to others.......
OK, more help please, been hanging for5 mins lol
Issue Fixed I think, he PM'd me.
Unlocked but... what do I do now?
Newbie but old or old but newbie - With the need and not just a curious want, to be able to "rename" my Nexus 7 v1 so I can see a friendly name in my old DD-WRTed Linksys GL, I finally had enough gumption to try rooting this tablet.
So, I was excited that when I used Nexus Root Toolkit v1.6.8 on my Nexus 7 v1, following the "easy and visual" steps, I actually managed to unlock this device. But when it came to the "root" part, the ADB repeatedly failed to recognize this tablet. I tried all the suggested steps and remedies, but so far, nada.
The tablet now boots past the white "Google" with an unlocked icon at the bottom, but nothing beyond thea big white "right-arrow" on the screen. I can choose a Wi-Fi signal to connect to, but that's it.
This is my first tablet and I have been playing with it for the past 3 months. I know people here are more than willing to help, so thank you in advance.
BTW, I am not that young to spend hours way past sleeping time to scour for answers and piece it together.
Wilks3y said:
Issue Fixed I think, he PM'd me.
Click to expand...
Click to collapse
Could you let me know his solution as I have exactly the same problem and have used all of his previous (unsuccessful) fixes myself?
Kindred Mole said:
Could you let me know his solution as I have exactly the same problem and have used all of his previous (unsuccessful) fixes myself?
Click to expand...
Click to collapse
+1
This worked for me...
Download the image file for your device which you can find at the Google Developer's site
Copy the uncompressed files from the image archive to the platform-tools folder of the Android SDK
Use the up and down volume on the device to get into bootloader mode. Connect the device to a usb port.
Open a command prompt in the platform tools folder and run the flash-all batch file to load the image to your device. After a few minutes I got the happy X logo to get me back to a blank slate.

Unlocked but can't root/install CWM

I used the toolkit for mac and it unlocked me, but when it came to the next steps it said device not found and then told me to highlight recovery and press start, when I do I get the android with the red ! symbol.
Can someone help me?
That symbol is a security feature within the stock recovery, volume up and power to access the stock recovery.
Sent from my Nexus 4 using Tapatalk 4
I tried that it's not working I press up then power the phone reboots and the red ! symbol shows up...
I searched and saw hold power and press up when I see the red ! but it just reboots the phone...
help please?
Sent from my GT-N5110 using Tapatalk 4
ADB wont work in stock recovery
roguedroid said:
I tried that it's not working I press up then power the phone reboots and the red ! symbol shows up...do you know the adb instructions on how to push supersymmetric and cwm?
edit my adb now won't recognize my phone even though it did a few mins ago...
I'm frustrated, been trying to access the stock recovery for the past several mins and simply can't.
help please?
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
For me also Stock recovery never worked. Just try to flash CWM or TWRP.
Btw, What toolkit did you use and how did you install the drivers. Please answer these, so that someone can help you better.(Or is it just the 'mac toolkit' ?)
My suggestion: PLZ DO NOT USE TOOLKIT. If you are stuck at some point while using the toolkit, then you'll not know what went wrong and how you can correct it. Do it manually. It is the most hassle-free method. Trust me.
I think that ADB will not work in stock recovery(may be you can boot normally into your phone and then try adb). The thing which you are looking for is 'fastboot'.
1) Restart ur phone (Power Button + Volume Down, i guess) and land in the bootloader and connect your phone to PC.
2) In CMD prompt(or Terminal), type 'fastboot devices'. If your device gets listed here, then fastboot is working and drivers are properly installed. If not, then drivers are not properly installed in your PC. You need both ADB and FASTBOOT drivers. Install them properly.
PS: For MAC, i think the command is slightly different. Something like './fastboot devices' . Please look for the same in this forum or just google it and find out.
3) Follow this guide for flashing CWM and Rooting.
http://forum.xda-developers.com/showthread.php?t=2266654
4) For properly installing the Drivers, read " A. Install the drivers " in the below thread (actually you can read the entire thread )
http://forum.xda-developers.com/showthread.php?t=2010312&highlight=cwm+6+0+3+5
My knowledge is limited to Windows PC, sorry if I am not of much help. Thanks !
badhri said:
For me also Stock recovery never worked. Just try to flash CWM or TWRP.
Btw, What toolkit did you use and how did you install the drivers. Please answer these, so that someone can help you better.(Or is it just the 'mac toolkit' ?)
My suggestion: PLZ DO NOT USE TOOLKIT. If you are stuck at some point while using the toolkit, then you'll not know what went wrong and how you can correct it. Do it manually. It is the most hassle-free method. Trust me.
I think that ADB will not work in stock recovery(may be you can boot normally into your phone and then try adb). The thing which you are looking for is 'fastboot'.
1) Restart ur phone (Power Button + Volume Down, i guess) and land in the bootloader and connect your phone to PC.
2) In CMD prompt(or Terminal), type 'fastboot devices'. If your device gets listed here, then fastboot is working and drivers are properly installed. If not, then drivers are not properly installed in your PC. You need both ADB and FASTBOOT drivers. Install them properly.
PS: For MAC, i think the command is slightly different. Something like './fastboot devices' . Please look for the same in this forum or just google it and find out.
3) Follow this guide for flashing CWM and Rooting.
http://forum.xda-developers.com/showthread.php?t=2266654
4) For properly installing the Drivers, read " A. Install the drivers " in the below thread (actually you can read the entire thread )
http://forum.xda-developers.com/showthread.php?t=2010312&highlight=cwm+6+0+3+5
My knowledge is limited to Windows PC, sorry if I am not of much help. Thanks !
Click to expand...
Click to collapse
I used the nexus 4 Mac rootkit I found in here.
It unlocked my phone fine. But when it came to installing a recovery and root it didn't.
Neither my adb or fastboot are working now before I unlocked and I messed around and they worked now nada ...
I went to YouTube saw my problem tried pressing volume up and power like in the video and it just gives me a black screen and either turns the phone off or reboots it normally...not sure if in supposed to hold power and let go of volume or vice versa.
I placed all the files on the storage I just need to access stock recovery which I strangely cannot now...
Tried framearoot and got nowhere.
Very frustrating
Sent from my GT-N5110 using Tapatalk 4
Sort out the drivers and adb,fastboot
roguedroid said:
I used the nexus 4 Mac rootkit I found in here.
It unlocked my phone fine. But when it came to installing a recovery and root it didn't.
Neither my adb or fastboot are working now before I unlocked and I messed around and they worked now nada ...
I went to YouTube saw my problem tried pressing volume up and power like in the video and it just gives me a black screen and either turns the phone off or reboots it normally...not sure if in supposed to hold power and let go of volume or vice versa.
I placed all the files on the storage I just need to access stock recovery which I strangely cannot now...
Tried framearoot and got nowhere.
Very frustrating
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
Just as I mentioned, i also had the same problem with stock recovery. So I simply flashed a Custom one(CWM, in my case)
Get the ADB and FASTBOOT working and that'll solve your recovery problem. Try fiddling with your drivers again. Not sure how to do that in MAC. If FASTBOOT is working, the you can boot into a Custom Recovery(you need not even flash it) and perform whatever you need to.
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Again, look at the efrant's guide i referred above; i took this from there only.Remember to replace 'customrecovery.img', with the actual downloaded custom recovery image name.
Or you can try posting your problem with the toolkit, in mac toolkit's thread.
I have been youtubing everything and finally got to
Reboot system
apply update from adb
wipe data/factory reset
wipe cache partition.
I now can get adb working so I tried ./adb sideload cwm from my desktop and it is giving me signature verification failed. installation aborted.
What can I do to resolve this?
I searched xda and no one can solve this issue from the threads I've read.
I fixed it! Whooohoooo! Installed cwm and root ....now to install pa rom.
Thanks for the help!
Sent from my GT-N5110 using Tapatalk 4

[Q] Installing Custom ROM on Wrong OS Version, Looking for Solutions

I apologize if this question has been answered already, but I just spent 15 minutes using the search button and could not find a response.
I just installed Matr1x v10.5 (http://forum.xda-developers.com/showthread.php?t=2007231) onto my Nexus 4 but it had JB 4.2. Based on the version notes of the thread, I assumed that it was backwards compatible with my phone and therefore installed the new version on my Nexus 4. Now every time I turn on my Nexus 4 the screen is blank. What can I do to fix this issue? Will it require a reset so that all my data is lost? Thanks.
What do you mean with '... The screen is blank'?
Can you get past the google bootanimation?
Sent from my Nexus 4 using xda app-developers app
failly said:
What do you mean with '... The screen is blank'?
Can you get past the google bootanimation?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nope, basically once I turn it on I see the "Google" text, and then the screen goes blank as in it's black. Basically the back light is on and you can see that it's on but the background is still black.
pooq said:
Nope, basically once I turn it on I see the "Google" text, and then the screen goes blank as in it's black. Basically the back light is on and you can see that it's on but the background is still black.
Click to expand...
Click to collapse
Go into recovery and flash the stock kernel. If that doesnt work you need to do a full wipe and reflash the rom.
failly said:
What do you mean with '... The screen is blank'?
Can you get past the google bootanimation?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Chromium_ said:
Go into recovery and flash the stock kernel. If that doesnt work you need to do a full wipe and reflash the rom.
Click to expand...
Click to collapse
Theoretically, if I flash v10.0 (which accommodates JB 4.2) it should fix the issue right?
I'm at a dilemma because I do not know if there are any other ways to insert the kernel into my phone as there is no microSD option on the Nexus 4. Does anyone know how I could potentially get the file into my phone?
pooq said:
Theoretically, if I flash v10.0 (which accommodates JB 4.2) it should fix the issue right?
I'm at a dilemma because I do not know if there are any other ways to insert the kernel into my phone as there is no microSD option on the Nexus 4. Does anyone know how I could potentially get the file into my phone?
Click to expand...
Click to collapse
Can you access recovery? If yes mount your storage and you can transfer the files.
Sent from my Nexus 4 using xda app-developers app
failly said:
Can you access recovery? If yes mount your storage and you can transfer the files.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I had already tried that, but once I connected my usb into my laptop I still couldn't transfer any files over.
In the end I reset my phone to factory settings, so the display still shows "Google". Just to confirm, the reason why this logo has been displayed on my phone for a while is because it is working to restore the factory setting (e.g. OS) correct?
pooq said:
I had already tried that, but once I connected my usb into my laptop I still couldn't transfer any files over.
In the end I reset my phone to factory settings, so the display still shows "Google". Just to confirm, the reason why this logo has been displayed on my phone for a while is because it is working to restore the factory setting (e.g. OS) correct?
Click to expand...
Click to collapse
I can't tell for sure since it never happend to me but I don't think if you choose to reset your phone to factory settings it will stay at the google logo.
If you choose to reset to facory settings I think you just will boot into recovery with that an android standing with something in his belly with a loading bar.
You can try this.
1.Boot into bootloader.
2A.Flash TWRP with the fastboot command and go to step 3.
2B.Flash stock N4 image with the fastboot command and profit!
3a.Try to mount storage and transfer another rom.
3b.Restore a backup.
Hopefully this works.
Sent from my Nexus 4 using xda app-developers app
failly said:
I can't tell for sure since it never happend to me but I don't think if you choose to reset your phone to factory settings it will stay at the google logo.
If you choose to reset to facory settings I think you just will boot into recovery with that an android standing with something in his belly with a loading bar.
You can try this.
1.Boot into bootloader.
2A.Flash TWRP with the fastboot command and go to step 3.
2B.Flash stock N4 image with the fastboot command and profit!
3a.Try to mount storage and transfer another rom.
3b.Restore a backup.
Hopefully this works.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have tried the above instructions up to step 3 because it did not work for me.
It shows the only files in my internal storage(/sdcard) are a file that says (Up A Level) and TWRP. Also, whenever I want to reboot it prompts "No OS Installed! Are you sure you wish to reboot?" At this point I am only interested in a factory reset now so that I can reinstall the initial JB 4.0 that came with the Nexus 4 and then upgrade to JB 4.3. However, whenever I do factory reset via recovery mode, I am stuck with an empty phone with the files I mentioned above.
What can I do to fix the situation? Thanks.
pooq said:
I have tried the above instructions up to step 3 because it did not work for me.
It shows the only files in my internal storage(/sdcard) are a file that says (Up A Level) and TWRP. Also, whenever I want to reboot it prompts "No OS Installed! Are you sure you wish to reboot?" At this point I am only interested in a factory reset now so that I can reinstall the initial JB 4.0 that came with the Nexus 4 and then upgrade to JB 4.3. However, whenever I do factory reset via recovery mode, I am stuck with an empty phone with the files I mentioned above.
What can I do to fix the situation? Thanks.
Click to expand...
Click to collapse
I think the reason that a factory reset won't help since there is no OS on the phone so it cannot reset something that isn't there.
And with the steps I mentioned, can you get into bootloader or does it directly boot into recovery.
Another thing you can try(I don't think it will work but I never tried it so you never know)
Download this toolkit:
http://forum.xda-developers.com/showthread.php?t=2015469
There is an option to flash to stock completly, that will maybe do the trick.
Good luck!
Sent from my Nexus 4 using xda app-developers app
failly said:
I think the reason that a factory reset won't help since there is no OS on the phone so it cannot reset something that isn't there.
And with the steps I mentioned, can you get into bootloader or does it directly boot into recovery.
Another thing you can try(I don't think it will work but I never tried it so you never know)
Download this toolkit:
http://forum.xda-developers.com/showthread.php?t=2015469
There is an option to flash to stock completly, that will maybe do the trick.
Good luck!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I can get into bootloader fine, it does not boot directly into recovery.
My Nexus 4 is already flashed with TWRP. I have installed the program from the link you provided, however, I have not used it to flash my phone again as one of the prerequisites to using the program is selecting which OS version I am using (at this point I am not using any) and want to prevent any further issues from occurring.
It seems like I can't really do anything with my phone unless I get a JB OS reinstalled, which is what I am currently struggling with. I am presently trying to find a way to copy the downloaded Nexus image files provided online into my internal storage so I can install them.
pooq said:
I can get into bootloader fine, it does not boot directly into recovery.
My Nexus 4 is already flashed with TWRP. I have installed the program from the link you provided, however, I have not used it to flash my phone again as one of the prerequisites to using the program is selecting which OS version I am using (at this point I am not using any) and want to prevent any further issues from occurring.
It seems like I can't really do anything with my phone unless I get a JB OS reinstalled, which is what I am currently struggling with.
Click to expand...
Click to collapse
Okay since you can get into bootloader thats great news!
Have you tried to manually download the nexus 4 image from google?
NOTE this are direct download links:
4.3:
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
4.2.2:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
Here is an excellent guide:
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
Scenario #2 on that guide suits you!
I think this will do the trick!
Sent from my Nexus 4 using xda app-developers app
You just have to do the following :
A) flash a recovery via fastboot (fastboot flash recovery recovery.zip)
B) now go ahead and boot from your recovery, and push the rom of your choice, in case you don't have one already inside your sdcard (adb push ROM.zip /sdcard/ROM.zip)
C) flash your recently copied rom of choice to your phone. (if necessary, wipe data, cache and dalvik cache)
failly said:
Okay since you can get into bootloader thats great news!
Have you tried to manually download the nexus 4 image from google?
NOTE this are direct download links:
4.3:
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
4.2.2:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
Here is an excellent guide:
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
Scenario #2 on that guide suits you!
I think this will do the trick!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I just spent a couple of hours reading through the guides (and trying them out) which led me to several other guides. To be incredibly honest, I am completely confused as there is a plethora of new information thrown at me. I have to pose several questions before I continue:
1) When you say bootloader, are you referring to the fastboot bootloader screen that pops up after holding the volume down button and the power button? I just wanted to confirm this as I am starting to feel you are referring to something different after reading several guides.
2) Is the scenario 2 guide you posted basically a method to "sideload" the JB 4.3 into the storage of my Nexus 4 so I can install it via Recovery Mode?
I tried installing the drivers but I cannot seem to do it successfully as I do not even have a starting OS for my phone in the first place. I can not access a theoretical "Developer Mode" either from when I first rooted my phone.
So basically, I do not understand how I can get the direct downloads from Google (the JB 4.3 files) and get them into the internal storage of my Nexus 4 to install the OS.
Is there a simpler way to do this? If not, here is my current progress. At the moment I am stuck at this guide (http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1) from the previous link you linked and am between C-D. I cannot get my laptop to recognize my device via fastboot devices in command prompt (D). To be honest, this is the second time I've seen this guide but could not get it working properly which is why I used the file provided at (http://forum.xda-developers.com/showthread.php?t=2015469) to root my Nexus 4.the OS[/B]. Is there a simpler way to do this? At the moment I am stuck at this guide (http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1) from the previous link you linked and am between C-D. I cannot get my laptop to recognize my device via fastboot devices in command prompt (D). To be honest, this is the second time I've seen this guide but could not get it working properly which is why I used the file provided at (http://forum.xda-developers.com/showthread.php?t=2015469) to root my Nexus 4.
Yes, the bootloader is the one where you press vol down and the power button together, that's the place where you select to go to the recovery, use fastboot.
First thing you got to do is turn on your phone on the bootloader as mentioned above. Then, assuming you downloaded this: [NEXUS 4 TOOLKIT V2.0.0] from here http://forum.xda-developers.com/showthread.php?t=1995688, open up command prompt and go to this address with "cd C:\Google_Nexus_4_ToolKit" or where you decided to install your toolkit. On windows explorer, go there and rename fastboot-toolkit or whatever it is called to fastboot to make things simpler.
Type in cmd: fastboot devices to check if it recognizes your phone.
If it doesn't; then install these drivers (you should have your device already connected via USB to your computer): https://www.dropbox.com/s/a808emeelvxkwyc/usb_driver.rar
Go to Control Panel\Hardware and Sound > Device Manager. Your phone should appear with an exclamation mark somewhere, right click it and click on update driver:
-Click on browse my computer software
-Let me pick from a list of device drivers on my computer
-Have disk
-Browse for where you downloaded the drivers I linked you to then click ok.
-You should find within the next page something that says Android Bootloader Interface, double click it and finish the installation.
After that's done, then type in fastboot devices on cmd again, it should show up now.
Then, go to here and download TWRP 2.6.0.0 http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img , that will be your recovery. After you've downloaded move it to C:\Google_Nexus_4_ToolKit to make matters easier.
NOTE: IF YOUR BOOTLOADER IS LOCKED YOU WILL HAVE TO UNLOCK IT , this can be done by typing fastboot oem unlock on command prompt
Now, simply type in this command: fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img you will now have a recovery on your device.
With the volume keys, choose to boot from the recovery. TWRP will load, while its loading, rename adb-toolkit to adb to make things easier. When its done loading, type in adb devices to see if it recognizes your phone, if it doesn't use your drivers again but this time instead of choosing Android Bootloader Interface, pick the one that says ADB.
When that's done, and it recognizes your device with the adb devices command you can now proceed to "push" or "copy/move a ROM you've downloaded in your computer towards your phone".
Of course you have to download a ROM, like Paranoid Android for example: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-3.69-20130722.zip , along with its GApps: http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130719-signed.zip
You might have to even update your radio and bootloader in the future too, but let's leave it at that for now.
After you are done downloading the ROM of your choice, then type in these commands (assuming ADB works)
adb push pa_mako-3.69-20130722.zip /sdcard/
adb push pa_gapps-full-4.2-20130719-signed.zip /sdcard/
Having moved these two files inside your phone, now its time to flash them.
1) Go to Wipe on TWRP and simply swipe to factory reset
2) Go back and click on Install, look for pa_mako-3.69-20130722.zip and then add pa_gapps-full-4.2-20130719-signed.zip to the queue, swipe to install.
After that's done, simply reboot your phone and it should start booting up Paranoid Android and you're done. Might give you a few issues if you have an old radio and bootloader, but that can be fixed by flashing the new versions of these two in TWRP. Can be found here: https://www.copy.com/s/JniBu/4.3 files (mako) (these can be pushed via ADB like before, or you can simply download them on your phone when its working)
Hope this helps, don't think I can be more detailed.
wammie said:
Yes, the bootloader is the one where you press vol down and the power button together, that's the place where you select to go to the recovery, use fastboot.
First thing you got to do is turn on your phone on the bootloader as mentioned above. Then, assuming you downloaded this: [NEXUS 4 TOOLKIT V2.0.0] from here http://forum.xda-developers.com/showthread.php?t=1995688, open up command prompt and go to this address with "cd C:\Google_Nexus_4_ToolKit" or where you decided to install your toolkit. On windows explorer, go there and rename fastboot-toolkit or whatever it is called to fastboot to make things simpler.
Type in cmd: fastboot devices to check if it recognizes your phone.
If it doesn't; then install these drivers (you should have your device already connected via USB to your computer): https://www.dropbox.com/s/a808emeelvxkwyc/usb_driver.rar
Go to Control Panel\Hardware and Sound > Device Manager. Your phone should appear with an exclamation mark somewhere, right click it and click on update driver:
-Click on browse my computer software
-Let me pick from a list of device drivers on my computer
-Have disk
-Browse for where you downloaded the drivers I linked you to then click ok.
-You should find within the next page something that says Android Bootloader Interface, double click it and finish the installation.
After that's done, then type in fastboot devices on cmd again, it should show up now.
Then, go to here and download TWRP 2.6.0.0 http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.0.0-mako.img , that will be your recovery. After you've downloaded move it to C:\Google_Nexus_4_ToolKit to make matters easier.
NOTE: IF YOUR BOOTLOADER IS LOCKED YOU WILL HAVE TO UNLOCK IT , this can be done by typing fastboot oem unlock on command prompt
Now, simply type in this command: fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img you will now have a recovery on your device.
With the volume keys, choose to boot from the recovery. TWRP will load, while its loading, rename adb-toolkit to adb to make things easier. When its done loading, type in adb devices to see if it recognizes your phone, if it doesn't use your drivers again but this time instead of choosing Android Bootloader Interface, pick the one that says ADB.
When that's done, and it recognizes your device with the adb devices command you can now proceed to "push" or "copy/move a ROM you've downloaded in your computer towards your phone".
Of course you have to download a ROM, like Paranoid Android for example: http://goo.im/devs/paranoidandroid/roms/mako/pa_mako-3.69-20130722.zip , along with its GApps: http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130719-signed.zip
You might have to even update your radio and bootloader in the future too, but let's leave it at that for now.
After you are done downloading the ROM of your choice, then type in these commands (assuming ADB works)
adb push pa_mako-3.69-20130722.zip /sdcard/
adb push pa_gapps-full-4.2-20130719-signed.zip /sdcard/
Having moved these two files inside your phone, now its time to flash them.
1) Go to Wipe on TWRP and simply swipe to factory reset
2) Go back and click on Install, look for pa_mako-3.69-20130722.zip and then add pa_gapps-full-4.2-20130719-signed.zip to the queue, swipe to install.
After that's done, simply reboot your phone and it should start booting up Paranoid Android and you're done. Might give you a few issues if you have an old radio and bootloader, but that can be fixed by flashing the new versions of these two in TWRP. Can be found here: https://www.copy.com/s/JniBu/4.3 files (mako) (these can be pushed via ADB like before, or you can simply download them on your phone when its working)
Hope this helps, don't think I can be more detailed.
Click to expand...
Click to collapse
The first thing I'd like to do before reporting my progress report is to thank you and failly for taking the time to help me out. You both have contributed tremendously in trying to help me out with this, so I would like to thank you both for that.
1) I had installed the sdk program and changed the adb path (following this guide http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/)
Following wammie's guide:
2) Booted into bootloader
3) Downloaded and installed NEXUS 4 TOOLKIT V2.0.0 (had used it before but it didn't work for me so I relied on a different program to root my phone). Renamed fastboot-toolkit to fastboot
4) Typed fastboot devices in in cmd, does not recognize phone
5) Uninstalled current usb drivers and installed usb drivers provided. The driver I chose to install for was titled "Android". The other ! mark was "Base System Device" which was something I had never seen before until today when I had reinstalled usb drivers
6) Typed fastboot devices in cmd again and still nothing has changed
I am unable to continue any further as fastboot does not recognize my phone when I have it under bootloader. I had downloaded all the files that were recommended in your post. I think the reason why I cannot access fastboot devices is because there is literally no OS running in my phone. I could be wrong though.
I guess I'll take a break and call it a night since I've been trying to fix this problem the past 13 hours or so. Any additional feedback and support is appreciated!
Additional Notes: I have tried this both on my laptops (Windows 8) and on my desktop PC (Windows 7)
Luckly, if windows doesn't recognize your device while in fastboot it isn't because you don't have a OS installes but because not correctly set up drivers.
I posted a link some posta ago about a toolkit:
http://forum.xda-developers.com/showthread.php?t=2015469
When opening the program at the top there is a button called full driver installation, press it and follow the instructions.
Sent from my Nexus 4 using xda app-developers app
http://i.imgur.com/sOT7FGh.png
http://i.imgur.com/WNEKb0z.png
http://i.imgur.com/vUmTDcZ.png
http://imgur.com/da7NGwB
http://i.imgur.com/bjmhXZv.png
This is what you should do when you are updating the drivers, its imperative you get those drivers working. Otherwise, you won't get access to fastboot.
Oh I would recommend using a Windows 7 PC.
Windows 8 can also do the trick but you maybe need to disable driver signature enforcement, so you better go with windows 7 for now.
Sent from my Nexus 4 using xda app-developers app
Status Update:
I had spent a whole day reformatting my Windows 7 machine and am back at it. I have made a bit more progress than before.
1) After typing in fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img in command prompt, under the "List of devices attached" it is blank (i.e. there is no device attached). http://i.imgur.com/TnyBCKS.png
2) I have successfully installed the usb driver on my PC the first time when the only explanation mark was titled "Android", however the only Android option at the moment now is labelled "Android Bootloader Interface". No such thing as ADB (or any variations including Android ADB Interface) exists.
3) In TWRP Recovery mode, I see an exclamation mark titled mako but I believe that is irrelevant. I have tried installing the drivers to this just in case but failed. I then tried it again in Bootloader mode and mako is gone and Android Device pops up again with "Android Bootloader Interface"
4) I have tried restarting my PC and repeating the above steps.
Edit:
5) The only time I see an Android Composite ADB Interfaces is when I boot normally to the "Google" screen. However, I cannot move any of my ROMS over into my phone. When I typed "adb devices" it shows a bunch of characters with offline beside it. I do not have any options to reinstall any drivers for this.
From my understanding,I should be able to access the Android Composite ADB Interface while in recovery mode, which should let me transfer my ROMs over... but the issue is I cannot access Android Composite ADB Interface while in recovery mode.
Also, is there any reason why I shouldn't use the official JB 4.3 img as the ROM I want to install on my phone?

AT&t Huawei Ascend XT H1611 Rooting Help.

I have unlocked the bootloader but I can not figure out how to root this thing at all. Has anyone had any success? I would like TWRP and SuperU.
this device is new yet. give it time
Tmobilefan906 said:
this device is new yet. give it time
Click to expand...
Click to collapse
Yeah I didn't realize how new this was whenever I posted it.
TWRP and root instructions available now in post 1 of
https://forum.xda-developers.com/android/general/huawei-ascend-xt-h1611-t3507933/
dabadguycr said:
I have unlocked the bootloader but I can not figure out how to root this thing at all. Has anyone had any success? I would like TWRP and SuperU.
Click to expand...
Click to collapse
divineBliss said:
TWRP and root instructions available now in post 1 of
https://forum.xda-developers.com/android/general/huawei-ascend-xt-h1611-t3507933/
Click to expand...
Click to collapse
You've already been helping me before you posted this.
People reading this thread might not realize we have root now. It's for their benefit .
dabadguycr said:
You've already been helping me before you posted this.
Click to expand...
Click to collapse
divineBliss said:
People reading this thread might not realize we have root now. It's for their benefit .
Click to expand...
Click to collapse
Good Point, I know my thread shows up first on Bing whenever I search for my phone and rooting help.
I have another XT and followed all instructions fine but no SuperSU when checking the phone. I tried flashing it twice (the one from the OP in main thread) and nothing. Am I missing a step?
I had installed fine on the first phone. this new one is 100% stock, unlocked bootloader, installed TWRP successfully but no supersu and root checker confirms no root.
Is it B140 or what? If you are missing a step, only you can check that.
powerserge1 said:
I have another XT and followed all instructions fine but no SuperSU when checking the phone. I tried flashing it twice (the one from the OP in main thread) and nothing. Am I missing a step?
I had installed fine on the first phone. this new one is 100% stock, unlocked bootloader, installed TWRP successfully but no supersu and root checker confirms no root.
Click to expand...
Click to collapse
divineBliss said:
Is it B140 or what? If you are missing a step, only you can check that.
Click to expand...
Click to collapse
Fixed
Can someone check the EMUI Huawei website for the unlock bootloader? Is it still working for requesting code? It keeps loop me back to the EMUI 5.0 page
sweetboy02125 said:
Can someone check the EMUI Huawei website for the unlock bootloader? Is it still working for requesting code? It keeps loop me back to the EMUI 5.0 page
Click to expand...
Click to collapse
Ya same. I got angry since I spent hours trying to find it so I just paid $4 and had DC-Unlocker unlock my bootloader.
sweetboy02125 said:
Can someone check the EMUI Huawei website for the unlock bootloader? Is it still working for requesting code? It keeps loop me back to the EMUI 5.0 page
Click to expand...
Click to collapse
webosFTW said:
Ya same. I got angry since I spent hours trying to find it so I just paid $4 and had DC-Unlocker unlock my bootloader.
Click to expand...
Click to collapse
If you follow this guide there should be no issue. The rootmygalaxy link should be pretty straightforward at unlocking the bootloader. The guide should be stickied in the OP.
https://forum.xda-developers.com/showpost.php?p=70515102&postcount=649
powerserge1 said:
If you follow this guide there should be no issue. The rootmygalaxy link should be pretty straightforward at unlocking the bootloader. The guide should be stickied in the OP.
https://forum.xda-developers.com/showpost.php?p=70515102&postcount=649
Click to expand...
Click to collapse
The issue is that https://emui.huawei.com/en/plugin.php?id=unlock that page hasnt worked for days. Keep redirecting me to the main page.
webosFTW said:
The issue is that https://emui.huawei.com/en/plugin.php?id=unlock that page hasnt worked for days. Keep redirecting me to the main page.
Click to expand...
Click to collapse
Yes use a different browser. Not working with chrome but working with edge. Go to the same link, it will bring you to EMUI 5.0 page, towards the top click on "download" then on the following page under the search bar click on "unlock bootloader" and it will bring you to the unlocking page. Just confirmed working. Updating the guide and will make a new post for root and twrp
Updated guide: https://forum.xda-developers.com/android/development/huawei-ascend-xt-h1611-feb27-2017-t3564389
Unlocked the boot loader, now adb/fastboot-15 Second won't work
Hello guys!
I used the 15 Second minimal adb/fastboot package from this site to unlock the boot loader. All seemed to go well, a screen message said success or something like that. It's been over 2 weeks since I had to put the phone down and take care of some other business. Now, after turning the phone off and then back on again when I am ready when I type in "fastboot devices" in the elevated cmd window in the adb directory the only message that comes back is "waiting on the device." Or the equivalent. I have tried what I could find from searching with Google to no avail. I am pretty sure that I am using the same cord, laptop, and everything that worked when I unlocked the boot loader. So, I am at a loss.
My goal originally was to use madvane20's slim downed version of b180 just to get it working again as my almost 2 years old P10 was stolen. I have no money in my budget for a new phone until Feb. 2020. I last talked with him in a series of PM's ending around May of last year, when a reply stated he had to get back to work on the last part of it. I have since seen a post referencing that it was ready in a package that after I had successfully unlocked the boot loader, it would root and install everything. This would have made me a happy guy... but I also noticed a custom ROM is now to be had based on Android 7. In order to get my Bank App's updated version of it's Mobile App to work, I have to install Android v 7 or higher. That's the main app that needs v 7 or better that I use daily. Several times...
But, now when I power up the phone, the first message is, "Your device has been unlocked and cannot be trusted... Press the Power Key now to reboot. Or the device will automatically reboot in 5 seconds." Which it does, the first time walking me through the Set-Up process, now it just boots into Huawei's EMUI 4.1. But, I cannot get adb to find the phone to follow the remainder of the instructions in the guide, "AT&T Huawei Ascend XT H1611 Feb27, 2017 update all things Root and TWRP (guide)"
Nor, can I get into the Recovery mode using the Vol Down/Power Keys.
So, where have I gone wrong or what is my next step? Since the phone can not be found and I can not get into Recovery using the proper keys what do I need to do and how do I do it?
I want to:
Root the phone.
Install the custom ROM I mentioned.
Or, Install an upgrade, if possible, to Android v 7... But,
can not get the phone recognized to get into a Recovery mode (is that right?) to push TWRP to it as well as the other files
it needs and to do whatever the Guides tell me to do.
Specs on the phone:
Model: H1611
Build: H1611C07B180
EMUI v: 4.1
Android v: 6.0.1
Security Patch level: September 1, 2017
Baseband v: 20234
Kernal v: 3.10.49-g03b627c
Sorry for the long post, but I thought it might answer some questions that came to mind before replying back.
Thanks in advance. I'm not here often, but when I am I am always relieved to get out of some jam I have gotten myself into!
mike0921
mike0921,
What happens if the phone is in normal mode and you type "adb devices" from the PC adb directory command prompt?
divineBliss said:
mike0921,
What happens if the phone is in normal mode and you type "adb devices" from the PC adb directory command prompt?
Click to expand...
Click to collapse
I just now found a new(er) USB cable for the phone. I also uninstalled the H1611 under Portable Devices in the Device Manager and rebooted the laptop. Where before, under Events the message was ".... needs further installation..." it now showed a successful install.
At the "adb devices" command, nothing happened, no response. I went and found the directions and explanations for the use of the top 30 commands. It told me to reboot the bootloader. A screen on the phone had me confirm the RSA command. Afterwhich the Fastoot&Recovery Mode screen with the little green Android guy with the message Phone Unlocked, FRP Unlock messages.
I went back to the elevated cmd window and at the adb directory command prompt entered "fastboot devices" and Voila! There were some letters and numbers, five or six spaces and the word "fastboot."
So, am I good to go with the rest of the steps in the guide from here? A question, about him saying to flash the Superuser zip file using TWRP. Is that suppose to already be on my SD card to flash it or can I flash it from my laptop without having to touch the phone or current USB cable? It seems stable but I am a bit gunshy and don't have much faith left in the old equipment I am having to use. A very old, refurbished HP Elitebook 8460P which is running really wonky, a not too new USB cable, the last of five I dug up and have used and finally works but is a bit loose, and Windows 10 1903 etc., which has disappeared all kinds of things I am having to run down) Can I use the "push" command to move the zip file to the SD card? And is that a fastboot function or an adb function? I seem to have read somewhere along the way to this point here that "push" is what I want to do, but powerserge1's Step 7 states to flash it using TWRP. I just want to check. And should questions from here on out be placed in his 184-page thread? I still haven't managed to read the whole thing, it seems to go off in so many other directions that I don't think I need to travel down. But, I will follow your advice.
I want to say a hearty thanks for your help. I was stuck, confused and frustrated at getting no results from Googling and reading for hours and getting nowhere it seemed. And I think I am good to go now.
Thoughts? Suggestions?
Just to be clear, The SuperSU zip file is currently on my laptop in the adb directory. Not on the phone.
mike0921 said:
I just now found a new(er) USB cable for the phone. I also uninstalled the H1611 under Portable Devices in the Device Manager and rebooted the laptop. Where before, under Events the message was ".... needs further installation..." it now showed a successful install.
At the "adb devices" command, nothing happened, no response. I went and found the directions and explanations for the use of the top 30 commands. It told me to reboot the bootloader. A screen on the phone had me confirm the RSA command. Afterwhich the Fastoot&Recovery Mode screen with the little green Android guy with the message Phone Unlocked, FRP Unlock messages.
I went back to the elevated cmd window and at the adb directory command prompt entered "fastboot devices" and Voila! There were some letters and numbers, five or six spaces and the word "fastboot."
So, am I good to go with the rest of the steps in the guide from here? A question, about him saying to flash the Superuser zip file using TWRP. Is that suppose to already be on my SD card to flash it or can I flash it from my laptop without having to touch the phone or current USB cable? It seems stable but I am a bit gunshy and don't have much faith left in the old equipment I am having to use. A very old, refurbished HP Elitebook 8460P which is running really wonky, a not too new USB cable, the last of five I dug up and have used and finally works but is a bit loose, and Windows 10 1903 etc., which has disappeared all kinds of things I am having to run down) Can I use the "push" command to move the zip file to the SD card? And is that a fastboot function or an adb function? I seem to have read somewhere along the way to this point here that "push" is what I want to do, but powerserge1's Step 7 states to flash it using TWRP. I just want to check. And should questions from here on out be placed in his 184-page thread? I still haven't managed to read the whole thing, it seems to go off in so many other directions that I don't think I need to travel down. But, I will follow your advice.
I want to say a hearty thanks for your help. I was stuck, confused and frustrated at getting no results from Googling and reading for hours and getting nowhere it seemed. And I think I am good to go now.
Thoughts? Suggestions?
Just to be clear, The SuperSU zip file is currently on my laptop in the adb directory. Not on the phone.
Click to expand...
Click to collapse
And after backing up in TRWP, I just checked the SD card's contents for the backup and saw the SuperSU zip file neatly placed on it as well. Just to be clear!??!
Okay, I somehow screwed this up I think. I was a little distracted by a friend dropping by. After telling her to give me a minute, I looked back at the phone after following Step 6:
Step 6: Confirm phone goes to FASTBOOT & RESCUE mode.
a) fastboot devices (to make sure your device is recognized)
b) fastboot boot TWRP.img (boots TWRP.img from Step 3)
c) The phone will boot into TWRP. Always select Keep Read Only from the first screen every time you go into TWRP.
Peek around a bit if you want to, then use TWRP to backup your stock recovery to external micro SD.
d) Reboot bootloader from inside TWRP to flash this custom recovery image (no adb command this time, you are rebooting to the bootloader from TWRP, you will see this option under "reboot" in TWRP).
e) fastboot flash recovery TWRP.img (now flashes TWRP recovery to the phone)
I then went to Step 7:
Step 7: After phone reboots, get into TWRP recovery repeating Step 6, a and b or hold the power button and volume up button from power-off state, then release when you see Huawei logo.
But now, the phone isn't being recognized again. And when I shut it off, hold Volume Up and Power buttons, I get a screen that asks if I want to: Reboot system now; Wipe data/factory reset; Wipe cache partition. Not the Recovery Screen with the options I got used to seeing in little green characters.
I tried the Reboot system now option and I'm back into the Huawei EMUI with everything appearing unchanged. Powered off, did the Vol Up + Power buttons and am back with the screen offering the three options I mentioned above. And the phone not being recognized after the "Devices" command.
Can you clarify my confusion? What am I doing wrong? Or not doing?
Thanks.
mike
---------- Post added at 06:47 PM ---------- Previous post was at 05:53 PM ----------
mike0921 said:
I just now found a new(er) USB cable for the phone. I also uninstalled the H1611 under Portable Devices in the Device Manager and rebooted the laptop. Where before, under Events the message was ".... needs further installation..." it now showed a successful install.
At the "adb devices" command, nothing happened, no response. I went and found the directions and explanations for the use of the top 30 commands. It told me to reboot the bootloader. A screen on the phone had me confirm the RSA command. Afterwhich the Fastoot&Recovery Mode screen with the little green Android guy with the message Phone Unlocked, FRP Unlock messages.
I went back to the elevated cmd window and at the adb directory command prompt entered "fastboot devices" and Voila! There were some letters and numbers, five or six spaces and the word "fastboot."
So, am I good to go with the rest of the steps in the guide from here? A question, about him saying to flash the Superuser zip file using TWRP. Is that suppose to already be on my SD card to flash it or can I flash it from my laptop without having to touch the phone or current USB cable? It seems stable but I am a bit gunshy and don't have much faith left in the old equipment I am having to use. A very old, refurbished HP Elitebook 8460P which is running really wonky, a not too new USB cable, the last of five I dug up and have used and finally works but is a bit loose, and Windows 10 1903 etc., which has disappeared all kinds of things I am having to run down) Can I use the "push" command to move the zip file to the SD card? And is that a fastboot function or an adb function? I seem to have read somewhere along the way to this point here that "push" is what I want to do, but powerserge1's Step 7 states to flash it using TWRP. I just want to check. And should questions from here on out be placed in his 184-page thread? I still haven't managed to read the whole thing, it seems to go off in so many other directions that I don't think I need to travel down. But, I will follow your advice.
I want to say a hearty thanks for your help. I was stuck, confused and frustrated at getting no results from Googling and reading for hours and getting nowhere it seemed. And I think I am good to go now.
Thoughts? Suggestions?
Just to be clear, The SuperSU zip file is currently on my laptop in the adb directory. Not on the phone.
Click to expand...
Click to collapse
And after backing up in TRWP, I just checked the SD card's contents for the backup and saw the SuperSU zip file neatly placed on it as well. Just to be clear!??!
Okay, I somehow screwed this up I think. I was a little distracted by a friend dropping by. After telling her to give me a minute, I looked back at the phone after following Step 6:
Step 6: Confirm phone goes to FASTBOOT & RESCUE mode.
a) fastboot devices (to make sure your device is recognized)
b) fastboot boot TWRP.img (boots TWRP.img from Step 3)
c) The phone will boot into TWRP. Always select Keep Read Only from the first screen every time you go into TWRP.
Peek around a bit if you want to, then use TWRP to backup your stock recovery to external micro SD.
d) Reboot bootloader from inside TWRP to flash this custom recovery image (no adb command this time, you are rebooting to the bootloader from TWRP, you will see this option under "reboot" in TWRP).
e) fastboot flash recovery TWRP.img (now flashes TWRP recovery to the phone)
I then went to Step 7:
Step 7: After phone reboots, get into TWRP recovery repeating Step 6, a and b or hold the power button and volume up button from power-off state, then release when you see Huawei logo.
But now, the phone isn't being recognized again. And when I shut it off, hold Volume Up and Power buttons, I get a screen that asks if I want to: Reboot system now; Wipe data/factory reset; Wipe cache partition. Not the Recovery Screen with the options I got used to seeing in little green characters.
I tried the Reboot system now option and I'm back into the Huawei EMUI with everything appearing unchanged. Powered off, did the Vol Up + Power buttons and am back with the screen offering the three options I mentioned above. And the phone not being recognized after the "Devices" command.
Can you clarify my confusion? What am I doing wrong? Or not doing?
Thanks.
mike
Sorry for the delay. What's the latest status with attempts to root the phone?

Broken connection during flashing

Hello,
I wanted to install aosp_grouper on my Nexus /, but after wiping the connection becam elabile during dlahing. Now I cannot connect the Nexus anymore to my PC via the Nexus root toolkit. The device shows only the Google logo and an open lock. Hard reset does not result in anything different.
Is there a way to reconnect to my PC or do I have to throw away the device?
Many thanks for your help.
Phero100 said:
Hello,
I wanted to install aosp_grouper on my Nexus /, but after wiping the connection becam elabile during dlahing. Now I cannot connect the Nexus anymore to my PC via the Nexus root toolkit. The device shows only the Google logo and an open lock. Hard reset does not result in anything different.
Is there a way to reconnect to my PC or do I have to throw away the device?
Many thanks for your help.
Click to expand...
Click to collapse
Hi, Phero100...
Your device should be recoverable, because...
Phero100 said:
...The device shows only the Google logo and an open lock...
Click to expand...
Click to collapse
This indicates that the bootloader is still good, and the device is not hardbricked.
I've never used a toolkit myself, preferring to use fastboot commands instead, so I can't comment too much on the Nexus root toolkit you mention in your post. But it's possible you may get a response from the toolkit by booting your Nexus 7 into fastboot mode, as follows...
From a powered off state, press VOL-DOWN and then simultaneously press POWER-ON. Hold both buttons for 15 seconds or until the device boots into the bootloader.
If you don't get anywhere with the toolkit you're using, I suggest you just reflash the Nexus 7 back to Google factory stock using fastboot.
Take a look at my response to another XDA member, from a couple of days ago, where I elaborate on fastboot flashing in more detail...
https://forum.xda-developers.com/showpost.php?p=80387547&postcount=2
...and of course there are other detailed guides elsewhere on XDA.
Good luck
Rgrds,
Ged.
Dear Ged,
thanks, but it does work only partially. Although I got a new image on the Nexus, an opened android man with Start at the top (fastboot mode?), neither the toolkit nor Windows 10 makes any connection to my Nexus. Anyway, without connection I can't do anything.
How can I connect to the Nexus 7 now?
GedBlake said:
Hi, Phero100...
Your device should be recoverable, because...
This indicates that the bootloader is still good, and the device is not hardbricked.
I've never used a toolkit myself, preferring to use fastboot commands instead, so I can't comment too much on the Nexus root toolkit you mention in your post. But it's possible you may get a response from the toolkit by booting your Nexus 7 into fastboot mode, as follows...
From a powered off state, press VOL-DOWN and then simultaneously press POWER-ON. Hold both buttons for 15 seconds or until the device boots into the bootloader.
If you don't get anywhere with the toolkit you're using, I suggest you just reflash the Nexus 7 back to Google factory stock using fastboot.
Take a look at my response to another XDA member, from a couple of days ago, where I elaborate on fastboot flashing in more detail...
https://forum.xda-developers.com/showpost.php?p=80387547&postcount=2
...and of course there are other detailed guides elsewhere on XDA.
Good luck
Rgrds,
Ged.
Click to expand...
Click to collapse
Phero100 said:
Dear Ged,
thanks, but it does work only partially. Although I got a new image on the Nexus, an opened android man with Start at the top (fastboot mode?), neither the toolkit nor Windows 10 makes any connection to my Nexus. Anyway, without connection I can't do anything.
How can I connect to the Nexus 7 now?
Click to expand...
Click to collapse
Hi, Phero100...
It's possible your Nexus 7's USB port has failed/is failing, and I'm guessing you've already tried different USB cables/different USB ports on your PC.
But... I have some questions...
Phero100 said:
...but it does work only partially...
Click to expand...
Click to collapse
What do you mean 'partially'?
------------------------------------
Phero100 said:
...Although I got a new image on the Nexus...
Click to expand...
Click to collapse
Where did you get this image from, and why is it on your Nexus 7? It should be on your Windows 10 box - unzipped, with the contents in the same folder as the fastboot and ADB executables, and these are likely to be found in your toolkit folder.
------------------------------------
Phero100 said:
...an opened android man with Start at the top (fastboot mode?)...
Click to expand...
Click to collapse
Yes - that is fastboot mode.
------------------------------------
What happens when you run this command from your PC?
Code:
fastboot devices
Do you see your N7's unique serial number confirming you have a valid fastboot connection - eg., something like this...
019d2424b14050b fastboot
------------------------------------
Have you read this guide...
https://forum.xda-developers.com/showthread.php?t=1907796
It's a little out of date, perhaps - but the underlying principles are still good. There are also other guides available here on XDA, and if you take a look at my own posting history, you'll see I've written some fairly detailed responses to other XDA members regarding aspects of reflashing the Nexus 7, although you may have to go back to around 2012/2013/2014, since I no longer use my Nexus 7 and haven't done so for about five years.
------------------------------------
I could have written another detailed guide here, but it would feel like I'd be 'reinventing the wheel'. The Nexus 7 is now a little over seven years old, and everything that can be written about reflashing it, has been written about it...
...and writing yet another guide seems redundant and pointless, not to mention time consuming on my part.
I would advise you to read around the Nexus 7 forums/threads here on XDA and the 'stickies' - acquaint yourself with using fastboot and rely less on toolkits - I know that people use them, and I'm not wholly opposed to them, but they hide/mask the process of using things like fastboot and ADB, and the possible errors they occasionally throw. In short, using fastboot directly is a more transparent way of doing things, not to mention a more granular way of doing things - eg., such as flashing a specific partition - and you'll learn more about Android, and will likely have a better idea of what to do when things go wrong, as sooner or later, they inevitably will.
However, I digress...
Comimg back to your specific case. Your bootloader is still good, which is a good thing - it means your device is not hard-bricked. If you cannot, by any means whatsoever, achieve any kind of connection with your Windows 10 box, then, as I intimated at the beginning of this post, your Nexus 7's USB port may have failed/come-loose/become detached from the motherboard, or maybe there's a problem with the USB cable you're using.
Another possibility is, you may have a Windows driver problem, which is something I've never experienced myself, and is therefore something I wouldn't be able to immediately help you with, without me doing quite a bit of research first. But I've read that Windows driver problems are a notorious obstacle when it comes to things like fastboot and ADB, and by extension, with toolkits too - so called 'driver hell' (ie., possible Windows device driver conflicts), so I would suggest you Google around, and run some searches here on XDA pertaining to that particular problem.
I hope I've given you some useful pointers in the right direction, and I hope you get your Nexus 7 up and running again.
Good luck.
Rgrds,
Ged.
GedBlake said:
Another possibility is, you may have a Windows driver problem, which is something I've never experienced myself, and is therefore something I wouldn't be able to immediately help you with, without doing a bit of research myself. But I've read that Windows driver problems are a notorious obstacle when it comes to things like fastboot and ADB, and by extension, with toolkits too - so called 'driver hell' (ie., possible Windows device driver conflicts), so I would suggest you Google around, and run some searches here on XDA pertaining to that particular problem.
I hope I've given you some useful pointers in the right direction, and I hope you get your Nexus 7 up and running again.
Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
If it does turn out to be a Windows driver problem, in my experience the Universal Naked Drivers work the best.
Hi Ged,
GedBlake said:
Hi, Phero100...
But... I have some questions...
Click to expand...
Click to collapse
What do you mean 'partially'?
That I do not get a connection ot Windows.
Where did you get this image from, and why is it on your Nexus 7? It should be on your Windows 10 box - unzipped, with the contents in the same folder as the fastboot and ADB executables, and these are likely to be found in your toolkit folder.
aosp_grouper-7.1.2-ota-20190823.eng.ds.zip
from: https://androidfilehost.com
Yes - that is fastboot mode.
------------------------------------
What happens when you run this command from your PC?
Code:
fastboot devices
Do you see your N7's unique serial number confirming you have a valid fastboot connection - eg., something like this...
019d2424b14050b fastboot
Yes
Have you read this guide...
https://forum.xda-developers.com/showthread.php?t=1907796
Not yet, but i will do.
On the other hand, if I try the toolkit again, to unlock boatloader it tries several times, but says that it is a connectivity issue. It seems to me that it cannot be the USB port/cable, because otherwise it would not be detected by windows. Furthermor, USB connection worked before until the decribed error occurred. Therefore, I assume that it might be a driver problem.
Phero100 said:
Hi Ged,
What do you mean 'partially'?
That I do not get a connection ot Windows.
Where did you get this image from, and why is it on your Nexus 7? It should be on your Windows 10 box - unzipped, with the contents in the same folder as the fastboot and ADB executables, and these are likely to be found in your toolkit folder.
aosp_grouper-7.1.2-ota-20190823.eng.ds.zip
from: https://androidfilehost.com
Yes - that is fastboot mode.
------------------------------------
What happens when you run this command from your PC?
Do you see your N7's unique serial number confirming you have a valid fastboot connection - eg., something like this...
019d2424b14050b fastboot
Yes
Have you read this guide...
https://forum.xda-developers.com/showthread.php?t=1907796
Not yet, but i will do.
On the other hand, if I try the toolkit again, to unlock boatloader it tries several times, but says that it is a connectivity issue. It seems to me that it cannot be the USB port/cable, because otherwise it would not be detected by windows. Furthermor, USB connection worked before until the decribed error occurred. Therefore, I assume that it might be a driver problem.
Click to expand...
Click to collapse
Ahh, my apologies ~ I thought you where referring to a Google Factory Image, not...
aosp_grouper-7.1.2-ota-20190823.eng.ds.zip
I have no familiarity with that image file, having never used it myself. If, as you say, it's on your Nexus 7's internal storage, you may be able to flash it using TWRP custom recovery, assuming you have TWRP flashed to the recovery partition. If not, then this brings us back to your problem, because TWRP needs to be flashed with fastboot...
You can find the download links (and instructions) for the Nexus 7 TWRP .img files at this link...
https://twrp.me/asus/asusnexus72012wifi.html
There are two download mirror links at this website, one for Europe and the other for America. Select the one that works best for you.
To flash TWRP, your Nexus 7 should be booted into fastboot mode, and from your laptop/PC, type this command in...
Code:
fastboot flash recovery [name-of-twrp.img file]
I usually rename the rather lengthy TWRP .img file to something short, like twrp.img, so the fastboot command is much easier to type, and would look like this...
Code:
fastboot flash recovery twrp.img
-------------------------------------------------
What is particularly puzzling about all of this, is the following...
Phero100 said:
What happens when you run this command from your PC?
Do you see your N7's unique serial number confirming you have a valid fastboot connection - eg., something like this...
019d2424b14050b fastboot
Yes
Click to expand...
Click to collapse
You answered 'Yes' to this question, and you do see your Nexus 7's unique serial number ~ this means you have a valid and usable fastboot connection to your Windows 10 PC. Logically then, your toolkit should work, and fastboot flash commands certainly should.
With regard to unlocking the bootloader, you might want to try this...
Code:
fastboot oem unlock
You should see a confirmation request screen on your Nexus 7, like the screenshot below.
Rgrds,
Ged.
Dear Ged,
I know manage to get everything running until flashing. The error occurs again, but hti time I red it correctly. It says zip file is corrupt. That is surprising to me given the source I downloaded the file from. I will now try a different custom ram.
GedBlake said:
Ahh, my apologies ~ I thought you where referring to a Google Factory Image, not...
aosp_grouper-7.1.2-ota-20190823.eng.ds.zip
I have no familiarity with that image file, having never used it myself. If, as you say, it's on your Nexus 7's internal storage, you may be able to flash it using TWRP custom recovery, assuming you have TWRP flashed to the recovery partition. If not, then this brings us back to your problem, because TWRP needs to be flashed with fastboot...
You can find the download links (and instructions) for the Nexus 7 TWRP .img files at this link...
https://twrp.me/asus/asusnexus72012wifi.html
There are two download mirror links at this website, one for Europe and the other for America. Select the one that works best for you.
To flash TWRP, your Nexus 7 should be booted into fastboot mode, and from your laptop/PC, type this command in...
Code:
fastboot flash recovery [name-of-twrp.img file]
I usually rename the rather lengthy TWRP .img file to something short, like twrp.img, so the fastboot command is much easier to type, and would look like this...
Code:
fastboot flash recovery twrp.img
-------------------------------------------------
What is particularly puzzling about all of this, is the following...
You answered 'Yes' to this question, and you do see your Nexus 7's unique serial number ~ this means you have a valid and usable fastboot connection to your Windows 10 PC. Logically then, your toolkit should work, and fastboot flash commands certainly should.
With regard to unlocking the bootloader, you might want to try this...
Code:
fastboot oem unlock
You should see a confirmation request screen on your Nexus 7, like the screenshot below.
Rgrds,
Ged.
Click to expand...
Click to collapse

Categories

Resources