Database Users

who know's what i can do next to bring my 7 back to life?

Ok I just need a little help and advice so if you one of you out there in XDAland can help I’ll be truly grateful…
I’ve got the 32gb Nexus 7 which I rooted via the Wugfresh method and added I CWM for my recovery and did the OTA update to Jelly Bean 4.2.1. The last 6 months life have been peachy. Even the misses and her iDevices are jealous of my little corner of Android heaven.
So last night pick up the 7 and notice it’s running a tad sluggish and I also notice the battery is low and flashing red, so I plug in the power cable and attempted to shut it down and it just hangs… I give it 5 minutes and still not shut down so I hold power & volume down and get in to the Bootloader from here I select start and the tablet just hangs on the Google cross (red, blue, yellow, green). This now happens every time I power down even though there has been a good charge (6 hours) done. If I now go back in the Bootloader and try selecting the Recovery Mode I get the Android robot with the red warning triangle and the words “No Command” and that’s it. If I try the factory reset of power button & volume up from recovery mode I get nothing.
From the bootloader I see
Fastboot Mode
Product Name - grouper
Variant - grouper
HW version - ER3
Bootloader Version - 4.13
Baseband Version - n/a
Serial Number xxxxxxxxxxxxxxxxxxxx
Signing - not defined yet
LOCK STATE - UNLOCKED
Can someone advise what the best thing I can do to revive the 7? I don’t mind losing the data but I’m just unsure what to do next. I’ve read a few threads but none pointed me in the direction I think I need to be in…
Thanks in advance for any help given.

That's funny as I put my 16gig nexus 7 on charge a couple of hours ago and just went to pick it up and it was on the bootloader screen, but I managed to reboot and everything is fine, its funny cos I've had similar experience with galaxy s3 but that was dead after a night on charge. I've sent the s3 of for repair under warranty thinking it was the sudden death syndrome on the s3, but now I'm worried the charger might be at fault.
Has anyone heard of a charger frying an android phone or putting nexus 7 in bootloader mode? Or is it just a coincidence?
Sent from my Nexus 7 using xda premium

@OP
The recovery you describe is the stock recovery. If you used an OTA process after rooting, probably that is what overwrote the CWM install you did previously - so that explains why you see what you do when you boot to recovery via the bootloader menu.
When you use the "reset by holding the power button down for 30 seconds" you are crashed the running OS and potentially corrupted any filesystems which are mounted "rw" (read-write). So, that might explain the bootloops that occurred thereafter.
You have a couple options, but before you try any of them, I would suggest that you observe the "power state animation" that occurs for about 10 seconds when you plug the tablet in to the charger with the tablet turned off: it shows you graphically how much charged the battery has. If the animation starts with a nearly all black battery, and then "fills up", the battery is still deeply discharged; if it is all white, or mostly all white, and the animation only "tops off" the battery, it has a good charge.
If that animation shows a battery which is still discharged, I would try to solve that problem before doing anything further. It was a low battery condition that got you into trouble in the first place; no point in making things even worse.
OK. Well, if you weren't a toolkit user, I would suggest a couple things that could be done manually using a custom recovery to attempt a repair of the /data filesystem, or rescuing your raw data for a later data recovery effort. But they involve command-line stuff, so me mentioning it is a waste of time. Suffice it to say that if you still have an unlocked bootloader and functioning drivers on your PC, you can re-install whatever custom recovery you want (using either fastboot or Wugfresh) and then use the capabilities of that custom recovery. Given that you didn't even realize that your custom recovery went missing until now, that's probably also a waste of time too - I probably can safely assume you don't know what its' full capabilities are.
So, flash a custom recovery and perform a reformat of the userdata partition ("Wipe Data" in TWRP, don't know what it is in CWM). You could even try taking a Nandroid backup before doing this, but the problem with doing this is that by default it will try writing to /data - so under the presumption that your userdata partition is hosed up, writing a whole lot of stuff to it (the backup) may not create a reliable backup image(s). With TWRP you could write backups to an external device, though.
That leaves a factory reset. If you do it with the stock recovery (simultaneously press power and vol-up for about 1 second after the recovery splash screen shows up to get the menu), it will erase EVERYTHING in the /data partition - including your everything in the psuedo-SD card.
Without any further learning on your part (abandonment of toolkits), it seems like the stock recovery factory reset is the least-effort solution for you. As I said, this will destroy ALL of your data on the device, but your device should return to a bootable condition. If you made any Nandroid backups and got them off the tablet, you could restore them after installing the custom recovery which made those same backups.
good luck

As last user said, if you have any nandroids you could restore them. And honestly it'd be so much easier to just boot an img. Not that hard.
Sent from my Motorola XPRT

Defibrillator...
Sent from my Nexus 7 using xda app-developers app

@bftb0
Thanks for the response and I’m going to follow your advice… I have done the command line root method twice with this my phones the HTC Desire and the then Sensation so I have experience in the dark art… it was just I couldn’t see a way of enabling the ADB drivers so my PC and 7 could look at/see each other but I have found the following http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
and this goes over what I need to do so I’ll give this a try and see how it goes. Like I say I don’t really need the data, I only used the 7 as a media hub and social media tool so I don’t mind putting the music and films back on it and the few apps and games is no big deal.
@FitAmp if this don’t work I may be taking your advice hahahahahaha!!!

bricked

slybunda said:
bricked
Click to expand...
Click to collapse
@slybunda May I ask why you say bricked?

Another case where the N7 seems to overly discharge the battery and not be able to recharge it. I've heard of this several times, it just won't charge the battery once it gets too low.
I bet if you can get the battery to charge it'll be fine. Or failing all else, this place has the battery for $30.
http://www.portatronics.com/product...oogle-Asus-Nexus-7-Original-Battery-Part.html
It is NOT bricked.

Dr Asqueroso said:
@slybunda May I ask why you say bricked?
Click to expand...
Click to collapse
Hi, Dr Asqueroso...
'Bricked' is a certainly a bit pre-emptive... if the BOOTLOADER is still good (and from your description, it sounds like it still is), then you have a very good chance of resurrecting your tablet.
The thing is, from your description, you're only 'bootlooping'... which is trivial to get out of... if you have a recent NANDROID backup (or for that matter, a flashable ROM .zip), on your internel storage and you know how to FASTBOOT FLASH a CUSTOM RECOVERY.
Your options are threefold...
----------------------
1) Use the STOCK FACTORY recovery to perform a factory reset. (As detailed by bftb0, earlier).
2) FASTBOOT FLASH a custom recovery (CWM or TWRP).
-- http://www.teamw.in/project/twrp2/103
-- http://www.clockworkmod.com/rommanager
I note you used CWM previously, so fastboot flash this recovery, and restore your last NANDROID backup. If you didn't make any NANDROIDs, then flash some other CUSTOM ROM. Or better still, use the 'wipe data' option in your Custom Recovery. I've had 'bootloops' and other weird egregious behavior myself, and this usually fixes it. (Sometimes, even wiping 'CACHE' and 'DALVIK' can make mysterious problems vanish!.)
3) Restore back to FACTORY stock.
-- http://developers.google.com/android/nexus/images
(You need the 'nakasi' version for your 'grouper' tablet).
This last option carries some risk, because it reflashes the BOOTLOADER, which is always a risky procedure (a corrupt flash will hardbrick the tablet). So, ABSOLUTELY make sure your tablet is fully charged AND you have a good USB connection to your PC.
I note you're still on bootloader v4.13, so you could edit the 'flash-all.*' script from Factory Stock JellyBean 4.1.2 (JZO54K) to remove the command to flash the bootloader. Flash as normal (by running the script), and then take the OTA update to 4.2.2 (JDQ39) over WiFi... this will still update the bootloader (to v4.18), but because of the way OTAs work, the risk is significantly reduced.
----------------------
But before you contemplate doing any of this... you need to ascertain if your battery is in good shape.
Here's what I would recommend if the battery is failing to charge correctly...
1. Plug the Nexus 7 into a wall charger.
2. Immediately press Volume Down and Power at the same time to reach the Bootloader
3. From the Bootloader menu, press Volume Down until you see “Power Off Device.”
4. Press the Power button to select the "Power Off Device" option.
5. Once your device is off, unplug the charger and then plug it back into the device.
If you see a large white battery shaped logo, that is flashing nearly all white, then you have a good level of charge... if it's flashing nearly all black (with only a bit of white), then the charge level is low... and fastboot flashing anything is not recommended.
Good luck... and hope this helps.
Rgrds,
Ged.

GedBlake said:
Hi, Dr Asqueroso...
'Bricked' is a certainly a bit pre-emptive... if the BOOTLOADER is still good (and from your description, it sounds like it still is), then you have a very good chance of resurrecting your tablet.
The thing is, from your description, you're only 'bootlooping'... which is trivial to get out of... if you have a recent NANDROID backup (or for that matter, a flashable ROM .zip), on your internel storage and you know how to FASTBOOT FLASH a CUSTOM RECOVERY.
Your options are threefold...
----------------------
1) Use the STOCK FACTORY recovery to perform a factory reset. (As detailed by bftb0, earlier).
2) FASTBOOT FLASH a custom recovery (CWM or TWRP).
-- http://www.teamw.in/project/twrp2/103
-- http://www.clockworkmod.com/rommanager
I note you used CWM previously, so fastboot flash this recovery, and restore your last NANDROID backup. If you didn't make any NANDROIDs, then flash some other CUSTOM ROM. Or better still, use the 'wipe data' option in your Custom Recovery. I've had 'bootloops' and other weird egregious behavior myself, and this usually fixes it. (Sometimes, even wiping 'CACHE' and 'DALVIK' can make mysterious problems vanish!.)
3) Restore back to FACTORY stock.
-- http://developers.google.com/android/nexus/images
(You need the 'nakasi' version for your 'grouper' tablet).
This last option carries some risk, because it reflashes the BOOTLOADER, which is always a risky procedure (a corrupt flash will hardbrick the tablet). So, ABSOLUTELY make sure your tablet is fully charged AND you have a good USB connection to your PC.
I note you're still on bootloader v4.13, so you could edit the 'flash-all.*' script from Factory Stock JellyBean 4.1.2 (JZO54K) to remove the command to flash the bootloader. Flash as normal (by running the script), and then take the OTA update to 4.2.2 (JDQ39) over WiFi... this will still update the bootloader (to v4.18), but because of the way OTAs work, the risk is significantly reduced.
----------------------
But before you contemplate doing any of this... you need to ascertain if your battery is in good shape.
Here's what I would recommend if the battery is failing to charge correctly...
1. Plug the Nexus 7 into a wall charger.
2. Immediately press Volume Down and Power at the same time to reach the Bootloader
3. From the Bootloader menu, press Volume Down until you see “Power Off Device.”
4. Press the Power button to select the "Power Off Device" option.
5. Once your device is off, unplug the charger and then plug it back into the device.
If you see a large white battery shaped logo, that is flashing nearly all white, then you have a good level of charge... if it's flashing nearly all black (with only a bit of white), then the charge level is low... and fastboot flashing anything is not recommended.
Good luck... and hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
First of all a massive Thank You all so much for the advice...
I think I've got it in the respects of each step but I'm just stuck with getting the drivers to work. I've installed the Java Dev Kit, the latest SDK from the Android site and successfully installed both the Tools and the Google USB Drivers. I also got the Asus drivers for the 7 and I have unziped the stock recovery JZO54K which ready to go. However can't get my 7 to show up in CMD Prompt via ADB devices string but if add my sensation it pops up everytime...
I've tried this process on a Windows 8 machine and a XP install too and the 7 is never picked up.
Does this mean the 7 is dead and stuck in the factory boot menu? What am I doing wrong?
This is killing me... :crying:

Dr Asqueroso said:
First of all a massive Thank You all so much for the advice...
I think I've got it in the respects of each step but I'm just stuck with getting the drivers to work. I've installed the Java Dev Kit, the latest SDK from the Android site and successfully installed both the Tools and the Google USB Drivers. I also got the Asus drivers for the 7 and I have unziped the stock recovery JZO54K which ready to go. However can't get my 7 to show up in CMD Prompt via ADB devices string but if add my sensation it pops up everytime...
I've tried this process on a Windows 8 machine and a XP install too and the 7 is never picked up.
Does this mean the 7 is dead and stuck in the factory boot menu? What am I doing wrong?
This is killing me... :crying:
Click to expand...
Click to collapse
No... it just means you're stuck in what is ubiquitously called 'driver hell'. Windows has always been a pain in the arse when it comes to drivers.
If you have a Windows XP box, you could try the following...
Download my copy of the FASTBOOT/ADB files for XP...
http://dl.dropboxusercontent.com/u/...orXP-MD5_8e02ab9b4b8463b9ee5c2063477b01ec.zip
Unzip to a folder on the Windows Desktop.
Unzip and copy the files from nakasi-jzo54k into the same folder.
You should now have a folder with the following files in it...
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-grouper-3.41.img
image-nakasi-jzo54k.zip
flash-all.bat
flash-all.sh
flash-base.sh
Delete 'bootloader-grouper-3.41.img' and edit 'flash-all.bat' to reflect this... that is to say, remove the line...
Code:
fastboot flash bootloader bootloader-grouper-3.41.img.
This is to avoid unnecessarily flashing the BOOTLOADER partition, and which in any event will only downgrade your current BOOTLOADER.
-----
Boot your Nexus 7 into BOOTLOADER mode, by pressing Vol. Down (& hold) and the Power Button.
Connect your Nexus 7 to your Windows XP PC, via a USB cable (preferably the one that shipped with the N7 originally).
Open a command prompt window on the folder into which you have copied all of the aforementioned files, and type...
Code:
fastboot devices
It should return a SERIAL NUMBER... if it does, you have a working FASTBOOT connection, and you're free to run flash-all.bat
This should restore JellyBean 4.1.2... and upon a successful reboot and a WiFi connection, an OTA upgrade will be proffered.
Allow this, and your Nexus will be upgraded to JellyBean 4.2.2 (JDQ39).
Good luck.
Rgrds,
Ged.

Okay so I have a folder with the following
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-grouper-3.41.img
image-nakasi-jzo54k.zip
flash-all.bat
flash-all.sh
flash-base.sh
But I'm stuck on the edit line?? sorry for being a pain can you explain this bit.. how do you edit the flash-all.bat??
Delete 'bootloader-grouper-3.41.img' and edit 'flash-all.bat' to reflect this... that is to say, remove the line...
Code:
fastboot flash bootloader bootloader-grouper-3.41.img.
This is to avoid unnecessarily flashing the BOOTLOADER partition, and which in any event will only downgrade your current BOOTLOADER.

Open the bat file in notepad.
Sent from my Galaxy Nexus

Done the edit and ran the flash-all.bat... The serial number has appeared after the fastboot command but now I seem stuck on the sending system command of 446268 been like this for 20+ minutes and somehow my bootloader is showing 3.41 on the tablet.
What next?

Dr Asqueroso said:
Okay so I have a folder with the following
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-grouper-3.41.img
image-nakasi-jzo54k.zip
flash-all.bat
flash-all.sh
flash-base.sh
But I'm stuck on the edit line?? sorry for being a pain can you explain this bit.. how do you edit the flash-all.bat??
Click to expand...
Click to collapse
Sometimes it's easier to 'just do' than explain 'how to do'...
Here is the modified 'flash-all.bat' script, with the line removed.
http://dl.dropboxusercontent.com/u/37483979/flash-all-MD5_ a687082ef3179feb40ba108436dc5768.zip
------
Maybe I'm just being overcautious when it comes to BOOTLOADER stuff...
It's entirely possible you could just run the original 'flash-all.bat' as is... without problems... as many people do, and as Google intended.
So, it's not critical you delete bootloader-grouper-3.41.img or run the modified .bat file... just ensure you have a damn good USB connection and power to both devices before you do.
Rgrds,
Ged.
---------- Post added at 12:55 AM ---------- Previous post was at 12:41 AM ----------
Dr Asqueroso said:
Done the edit and ran the flash-all.bat... The serial number has appeared after the fastboot command but now I seem stuck on the sending system command of 446268 been like this for 20+ minutes and somehow my bootloader is showing 3.41 on the tablet.
What next?
Click to expand...
Click to collapse
Sending /system has always been problematic for me as well... you need to change to a different USB port on your PC.
Using the Vol. Keys navigate to RESTART BOOTLOADER... disconnect and reconnect to a different USB port, and try again.
If you're BOOTLOADER is showing 3.41, don't worry about it. The issue was never about the version, but about flashing it.
This will be taken care of later, with the OTA upgrade.
Rgrds.
Ged.

There must be something else going wrong as every step I've taken thus far has worked but the final sending bit... currently on my machine see the following... it's been like this for 2 hours...

Dr Asqueroso said:
There must be something else going wrong as every step I've taken thus far has worked but the final sending bit... currently on my machine see the following... it's been like this for 2 hours...
Click to expand...
Click to collapse
2 hours is way too long... it should take less than 5 minutes to flash back to stock.
I suspect a USB connectivity issue... open another command prompt window, and type
Code:
fastboot devices
If you don't see a SERIAL NUMBER, then your FASTBOOT connection has died...
Try again, from a different USB port... and maybe a different USB cable.
----
You are actually getting somewhere though... your screenshot indicates that 'boot' went over successfully.
Don't give up hope - persevere!
Rgrds,
Ged.

Ok I'll try it again when I get home from work...

Okay followed all the steps but I think the tablet is not going to play nice... I just can't get past the sending system bit.
The 7 is now showing
Fastboot Mode (in red)
Product Name - grouper
Variant - grouper
HW version - ER3
Bootloader Version - 4.18
Baseband Version - n/a
Serial Number xxxxxxxxxxxxxxxxxxxx (now showing my number)
Signing - not defined yet
LOCK STATE - UNLOCKED
My CMD prompt window is yet again just showing sending system and nothing. Been like this for the past 30 mins or so... I've swapped my USB ports over tried and the process a few times and still no joy. I think I've been defeated.
It looks like the 7 will have to go back... but can I make a warranty claim from Asus in it's current state or will I have to lock it somehow??
Failing that I'll "lose" it and claim off the house insurance.
Oooops the CMD window is doing something different...
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4944 KB)...
OKAY [ 0.656s]
writing 'boot'...
OKAY [ 0.203s]
sending 'recovery' (5446 KB)...
OKAY [ 0.719s]
writing 'recovery'...
OKAY [ 0.219s]
erasing 'system'...
OKAY [ 0.094s]
sending 'system' (471804 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 5264.891s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
< waiting for device >
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.656s
C:\android-sdk\platform-tools>
Anyone with any suggestions as to my next move?

[Q] Nexus 7 (2012) unlocked, but unrooted: waiting for device

I had an unlocked and rooted Nexus 7 (2012) with Android 4.2. After on OTA-Update I have an unlocked but _rooted_ Nexus 7. I read a lot about "waiting for device", but can't get it work anymore to connect. The device is reset and contains a fresh install without any added data.
I tried to follow http://forum.xda-developers.com/showpost.php?p=44179882
Step 2: Reboot the Nexus 7 into fastboot mode using the combination of volume up, volume down and power buttons
Click to expand...
Click to collapse
I can't get into fastboot with 3 buttons, but with Power and Vol- I see:
Product-Name - tilapia
Variant - tilapia
HU Version - PR
Bootloader Version - 4.23
Baseband Version - 1231_0.18.0_0409
Serial Number - ....
Signing - not signed yet
Lock state - unlocked
Maybe I am doing something wrong then, when I try to flash.
I see start, when I press the power button the N7 starts
When I change to recovery mode, I see "waiting for device" (USB debugging is on, the cable worked to unlock it)
Since I have an unlocked device, I tried only from Ubuntu 12.04 as root:
Code:
~# fastboot-linux flash recovery CF-Auto-Root-tilapia-nakasig-nexus7.img
Before I followed http://forum.xda-developers.com/showpost.php?p=44179882 I flashed recovery-clockwork-6.0.0.6-grouper.img
I could also install SuperSU 1.51, but root doesn't work and I found no way to install an updated SuperSU 1.51
BTW, I didn't know, that the grouper.img is the wrong one for my 3G device, UMTS worked fine with 4.2

try using nexus root toolkit. I had rooted prior to 4.3. when I updated, i just had to press one button to reroot(if you didn't use nexus root toolkit to begin with then you may need to go thru the driver setup)

Xanthius Balaraw said:
try using nexus root toolkit. I had rooted prior to 4.3. when I updated, i just had to press one button to reroot(if you didn't use nexus root toolkit to begin with then you may need to go thru the driver setup)
Click to expand...
Click to collapse
I will try it, also I hoped to use Linux.
http://www.wugfresh.com/nrt/
Configure your drivers if you haven’t already using the driver guide (If you aren’t sure use Step 3 of the driver guide to test your drivers).
Click to expand...
Click to collapse
Where do I get the drivers? Couldn't find a link there.
Edit: Since I have to go to a Windows PC, I downloaded the windows-programm only on my linux pc, it looks like the drivers are included in Nexus Root Toolkit: http://www.youtube.com/watch?v=iQhyerPfGes

I tried a lot with Windows XP 32bit and Windows 7 bit, but always I got "adb device was not found", but I saw a popup on the windows desktop with the Nexus after I attached the USB-cable. With Win7 I tried drivers 1-3, with XP driver 1.
With Linux something works:
Code:
adb devices
List of devices attached
<serial no> device
Code:
fastboot devices
<serial no> fastboot
Code:
~# fastboot flash recovery cf-auto-root-tilapia-nakasig-nexus7_92bf3da522bbb6e86725fe3290f391cc.zip
sending 'recovery' (6900 KB)...
OKAY [ 0.802s]
writing 'recovery'...
OKAY [ 0.332s]
finished. total time: 1.134s
But how can I install supersu? I don't know how to get the menu, where I can install zip-files.

lg-optimus said:
Where do I get the drivers? Couldn't find a link there.
Click to expand...
Click to collapse
There is a button in nrt to download and install drivers also to test to make sure they are working.

This forum is for the new 2013 Nexus 7 named Flo. You stated you have the 2012 verson...might want to go to the 2012 Nexus 7 forum here for advice.
On the 2013 Nexus 7 I use the volume button in bootloader/fastboot mode to switch to recovery, then select it with the power button to boot into the recovery you just flashed to the device. From there you can install Supersu (if you have downloaded the Supersu zip file to your device before hand).

geckocavemen said:
This forum is for the new 2013 Nexus 7 named Flo. You stated you have the 2012 verson...might want to go to the 2012 Nexus 7 forum here for advice.
Click to expand...
Click to collapse
This Guy ^

Oh, I am sorry to be in the wrong forum. What I found out in the menatime, that the stock-recovery is flashed everytime after a reboot, so there is no menu to flash zip-files after a new start.

lg-optimus said:
Oh, I am sorry to be in the wrong forum. What I found out in the menatime, that the stock-recovery is flashed everytime after a reboot, so there is no menu to flash zip-files after a new start.
Click to expand...
Click to collapse
I know it was in the wrong forum and all, but found something odd. I had a lot of trouble due to the same thing, waiting for device when trying fastboot. Just in case anyone arrives here: When you see the screen with the Start on top and FASTBOOT MODE in small red letters with the product specs, you're exactly where you should, no need to choose any option.
In my case, the fastbood mode doesn't work from linux (Kubuntu 13.10). It's just not detected, it makes no usb plugged sound, no icon on the tray...nothing. After some headaches just decided to boot to windows and try again. Fastboot mode, exactly as described, plug it to USB, and there you go, the "bop-beep" sound of usb plugged. I knew then it was gonna work on Windows.

Wrong forum *and* necro posting. Fantastic.
Sent from my Nexus 7 (2013) running 4.4

limbonik said:
Wrong forum *and* necro posting. Fantastic.
Sent from my Nexus 7 (2013) running 4.4
Click to expand...
Click to collapse
Thanks for your contibutive post. However I got there through google searches, that kept directing me to this thread. I imagined more people would get there searching for answers not finding them. By the way, the thread is from august, not so old.

install PDAnet on your device .. follow procedure of installation carefully ( should be installed on both pc and phone ) and when it was installed .when u enter your bootloader your phone will be recognize by your pc and wait for device will gone .
the method tested by me and took me one month two years ago to find .. on my g nexus first try to unlock .
PDAnet isntall drivers and everything you need to use adB commands ... if it helped give me thanks and let me know by pm .
PDA links
http://junefabrics.com/android/downloadold.php

No Command Error

I went to update to KitKat and it was nearly done and then the "No Command" error came up. My tablet has an unlocked boot loader but isn't rooted. However it was before but I updated it from an OTA and that got rid of it. I've tried booting into recovery etc but the same thing happens.
Anyone have any advice please?

Same exact issue and set up here. Also, maybe I'm just dumb, but I can't get my tablet to turn off either. It just keeps cycling back to the "no command" screen until I do something.

tgearhar said:
Same exact issue and set up here. Also, maybe I'm just dumb, but I can't get my tablet to turn off either. It just keeps cycling back to the "no command" screen until I do something.
Click to expand...
Click to collapse
I think that both of you what you see (the "no command") is your stock recovery, if indeed you see an android with a yellow !.
If it is the case to access the menu of the stock recovery press power and tap volume up. The menu will give you the choice of rebooting your Nexus 7.

gunner1937 said:
I think that both of you what you see (the "no command") is your stock recovery, if indeed you see an android with a yellow !.
If it is the case to access the menu of the stock recovery press power and tap volume up. The menu will give you the choice of rebooting your Nexus 7.
Click to expand...
Click to collapse
I can get to the menu but when trying the reboot option, it just cycles the same way again. Back to the android with a red ! and says "No command." I also tried clearing cache and data to no avail. I was going to try using ADB to manually push the update but my computer was recently updated and now I can't get the driver installed for some reason.
I spent too much time messing around with and learning how to do things with my SIII and not enough time with this

Same deal here! Not sure what to do short of wiping and losing my info.

Same here...any advice? Not sure what happened. OTA update too.

Significa said:
Same here...any advice? Not sure what happened. OTA update too.
Click to expand...
Click to collapse
Wow, this seems to be widespread, at least somewhat. I'm in same situation. Toolkits, adb, nothing works. I thought this was a soft brick, but now I'm thinking it's toast. Probably doesn't help that I didn't have Dev options enabled along with USB Debugging. I can't even turn it off. Just bootloops after Google logo shows up twice, then to No Command error, then starts over again. I wonder what the hell is causing this. (Device was locked and unrooted)

Same boat here, even sideloaded the factory image via ADB.

[QUOTE [/QUOTE]
I was going to try using ADB to manually push the update but my computer was recently updated and now I can't get the driver installed for some reason.
If you have android-sdk-windows installed on your computer do not forget to update it through "SDK Manager.exe".

Pushing via ADB didn't work for me. That also failed.
I caved and called Google. Tech support is stumped as well.
Sent from my Nexus 5 using Tapatalk

Could this be a widespread issue? Like I don't even understand why it happened at all!
Sent from my Nexus 5 using XDA Premium 4 mobile app

I finally got mine working again!
I tried a million different things so I'm going to try and explain my process as simple as I can, I apologize in advance because I am far from an expert...
First, I tried using the method, well some of it, from this thread: http://forum.xda-developers.com/showthread.php?t=1907796
- I would suggest using this thread to get everything set up (drivers, ADB, the factory image downloaded and in the correct file location) I wasn't able to get the drivers working correctly with that route so I ended up using the toolkit to get them working but that thread helped me get all of the system files in the correct location and helped get all of the ADB stuff set up.
Once you have everything set up and your computer recognizes the tablet, (I checked that by opening a cmd prompt and using the command from the original thread above "adb devices"). As long as you see your device, I think you should be good.
From the "No Command" screen I held down Power and Volume + to get the menu to come up. I then chose the Restart option and immediately held Power and Volume -. This got me into the Fastboot Mode.
Once in Fastboot mode I went to the cmd prompt on my computer and used the following commands in this order from this post:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot flash system system.img
fastboot reboot
*Make sure that all of the image files are in the proper location on your computer otherwise this step is worthless
The tablet then rebooted normally and I was able to set everything up again. Again, I am by no means an expert at all, this is just what worked for me. Try at your own risk.
I hope I covered all of the steps, I tried a million different things last night so they all kind of run together.

I ended up doing and it worked for me as well. Wiped everything though. How can I restore / reinstall my apps w/o needing to download them all again?

Two things: That guide says you must have USB Debugging enabled. Since my wife had this tablet, I did not have dev options enabled at all, including USB debug.
The other thing is that when I run the SDK Manager, nothing happens on my computer. I double click it or try Run as Admin, and a small CMD box flashes on my screen for a millesecond and disappears. That's all.

My wife's 2012 N7 is having this same problem. Unlocked bootloader, but I reflashed factory image and unrooted before giving it to her. She got the OTA last night, and now stuck at No Command.
I've subscribed to this thread, hoping that you guys will have it solved before I get home from work tonight! Would love to not have her lose all her data.
(I was kinda mad that she got the OTA last night and I haven't got it yet on my 2013 N7, but that's another gripe for another thread)

killswitch11 said:
Two things: That guide says you must have USB Debugging enabled. Since my wife had this tablet, I did not have dev options enabled at all, including USB debug.
The other thing is that when I run the SDK Manager, nothing happens on my computer. I double click it or try Run as Admin, and a small CMD box flashes on my screen for a millesecond and disappears. That's all.
Click to expand...
Click to collapse
Unfortunately I'm not sure on the SDK manager part. As far as the USB Debugging, I'm 98% sure that I did not have it enabled either. I think I did at one point but after doing several OTA upgrades, I'm sure it got unchecked.
---------- Post added at 01:34 PM ---------- Previous post was at 01:01 PM ----------
kr33mo said:
I ended up doing and it worked for me as well. Wiped everything though. How can I restore / reinstall my apps w/o needing to download them all again?
Click to expand...
Click to collapse
I don't believe there is a way. Maybe someone smarter than myself can chime in but I had to let the play store do it's thing and re-download all of mine.

tgearhar said:
I finally got mine working again!
I tried a million different things so I'm going to try and explain my process as simple as I can, I apologize in advance because I am far from an expert...
First, I tried using the method, well some of it, from this thread: http://forum.xda-developers.com/showthread.php?t=1907796
- I would suggest using this thread to get everything set up (drivers, ADB, the factory image downloaded and in the correct file location) I wasn't able to get the drivers working correctly with that route so I ended up using the toolkit to get them working but that thread helped me get all of the system files in the correct location and helped get all of the ADB stuff set up.
Once you have everything set up and your computer recognizes the tablet, (I checked that by opening a cmd prompt and using the command from the original thread above "adb devices"). As long as you see your device, I think you should be good.
From the "No Command" screen I held down Power and Volume + to get the menu to come up. I then chose the Restart option and immediately held Power and Volume -. This got me into the Fastboot Mode.
Once in Fastboot mode I went to the cmd prompt on my computer and used the following commands in this order from this post:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot flash system system.img
fastboot reboot
*Make sure that all of the image files are in the proper location on your computer otherwise this step is worthless
The tablet then rebooted normally and I was able to set everything up again. Again, I am by no means an expert at all, this is just what worked for me. Try at your own risk.
I hope I covered all of the steps, I tried a million different things last night so they all kind of run together.
Click to expand...
Click to collapse
Worked for me! Thanks, I don't believe I had USB Debugging enabled either. Shame it wiped all my data though.

OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
I first used Wug's Toolkit to download and install the RAW drivers. (Option #4, I believe) They were the only ones that worked for me. I followed the instructions to install them and then when it looped to the No Command screen, I held volume up and power. This got me to the menu, where I chose reboot. I then immediately held down the volume button and power to get into the bootloader screen, where it (thankfully) stopped looping. Then I unlocked the bootloader using the one-click option. Next step was to download and flash factory 4.4 image using the Soft Brick mode. Fastboot recognized my device and pushed the image. Now all is well. Close call... I've already enabled USB Debugging for my wife on this tablet so that crap doesn't happen again. She did lose all her data but she is happy to have a working tablet again instead of a $200 beer coaster.

killswitch11 said:
OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
Click to expand...
Click to collapse
Worked for me as well. Really appreciate that.
Sent from my Nexus 5 using Tapatalk

killswitch11 said:
OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
I first used Wug's Toolkit to download and install the RAW drivers. (Option #4, I believe) They were the only ones that worked for me. I followed the instructions to install them and then when it looped to the No Command screen, I held volume up and power. This got me to the menu, where I chose reboot. I then immediately held down the volume button and power to get into the bootloader screen, where it (thankfully) stopped looping. Then I unlocked the bootloader using the one-click option. Next step was to download and flash factory 4.4 image using the Soft Brick mode. Fastboot recognized my device and pushed the image. Now all is well. Close call... I've already enabled USB Debugging for my wife on this tablet so that crap doesn't happen again. She did lose all her data but she is happy to have a working tablet again instead of a $200 beer coaster.
Click to expand...
Click to collapse
I'll give that a go tomorrow. Missed my tablet! Hope it works!

[Q] Hard bricked tablet - what happened and what to do now?

I believe I've hard-bricked my Nexus 7. I'm not stranger to flashing, etc., but something must have messed up this time. I was previously running stock Android 4.3 with TWRP recovery and my tablet took the OTA update. The update of course failed because of the root and recovery, but instead of going back to Android 4.3, it wouldn't boot past the fastboot screen (bootloader screen? with the green android).
So, planning to return to all stock, I downloaded the official Android 4.4 .tgz file and extracted it to my platform-tools folder for the Android SDK. I ran "flash-all.bat" as explained in this tutorial: http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/
Something must have went wrong because the screen went black and will not turn back on. When plugged into the PC, it is recognized as only an "APK" device. Sources online indicate that this is hard-bricked, as there is no "nvflash" openly available for the Nexus 7 to restore the bootloader.
1. What happened and how can others prevent this?
I think I should have flashed each partition individually (i.e. boot, recovery, system, etc) instead of "flash-all." Any idea what happened to the bootloader? Any other ideas on how to restore the bootloader?
2. What to do now?
EDIT: Apparently my device is out of warranty. Crap.
EDIT 2: Apparently I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi)... Opps!
There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?
Thanks for your assistance in advance! This forum is great.

What about pressing and holding power button for more than 30 seconds?
Once it could boot and you could enter into fastboot mode, then I think you would get a chance to save it.
BTW, I did mess up when I was flashing KRT16O factory images, which was the earlier release for Kitkat.
At that time, I just used the flash-all.bat like you did. And in the second round, I still failed when following and typing the listed commands in flash-all.sh.
So I chose to use nexus toolkit after that.

Thanks for your reply.
I keep trying that, along with the various other combinations of power button and volume down and volume up. Nothing. The most that happens is when it's plugged into the PC, the PC makes the sound of something being connected and disconnected. I just tried unplugging the battery too. I'll let it charge over night and try again tomorrow.
When yours failed the first 2 times, you were still able to get into fastboot? You're right, if I can just get there then I'll be alright.
Thanks again.

I was just backtracking my steps and realized the mistake I made. I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi). Major opps!!
1. Any way to recover from this brick? My gf also has a Nexus 7 (2012). Anything I can copy from that to restore mine? (if she even lets me touch it after she hears about this!)
2. There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?

No problem,bro. I think you can always get responses here at XDA though I didn't help you out.
And yes, I could still enter into Fastboot at that time.
However, I was not able to reboot my N7 using the aforementioned methods since it got stuck in Google logo.
Hence I removed the batterysilly, booted it and used the key combination to get into Fastboot. And you know the rest, used the toolkit....

My friend if u can enter fastboot then u can definately revive ur device, it is soft brick not hard brick (soft brick = software is dead) (hard brick = hardware is dead)
I do this all the time just for fun
Let me give u step by step instructions.
1. Download this tool kit
http://forum.xda-developers.com/showthread.php?t=1766475
2. Download the proper stock image for ur device (make sure u pay attention when u download the file, u definately dont want to download wrong file and then redownload the file again)
https://developers.google.com/android/nexus/images
3. Install toolkit, Select your device and don't worry about android version because u have non rit now and install the proper drivers for fastboot to work.
4. From toolkit main screen, select (softbrick/bootloop) and accept the warning.
5. Now select (Other/Browuse option) and then select (I Downlaoded a factory image myself) option then it will ask for the image that u downloaded from google website (Step 2).
6. If u have done exactly as i said then ur phone should be detected in Fastboot mode and the flashing would start and after some time phone should show loading screen (os is booting) wait for it to boot and enjoy ur stock android.
7. Enjoy.
FYI u should have enough battery (around 50%) and to enter fastboot mode u just have to boot to bootloader (restart/ power on the device while pressing volume down button) u should see the screen with bunch of numbers e.g bootloader version etc.

zamboniman87 said:
I was just backtracking my steps and realized the mistake I made. I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi). Major opps!!
1. Any way to recover from this brick? My gf also has a Nexus 7 (2012). Anything I can copy from that to restore mine? (if she even lets me touch it after she hears about this!)
2. There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?
Click to expand...
Click to collapse
Hmm... there is a thread on making it unbrickable, but you have to do that ahead of time. If you were to buy a broken tablet, you'd probably need to replace the motherboard.
Sent from my Nexus 4 using XDA Premium 4 mobile app

xateeq said:
My friend if u can enter fastboot then u can definately revive ur device, it is soft brick not hard brick (soft brick = software is dead) (hard brick = hardware is dead)
Click to expand...
Click to collapse
Thanks for your help, but unfortunately I can't even enter fastboot. I can only enter APX mode, which apparently is pre-fastboot.

korockinout13 said:
Hmm... there is a thread on making it unbrickable, but you have to do that ahead of time. If you were to buy a broken tablet, you'd probably need to replace the motherboard.
Click to expand...
Click to collapse
Thanks. I saw that thread, but of course it was too late at that point. Perhaps I'll look into buying one with a cracked screen, or sell mine for parts on ebay.

Plz dont tell me u flashed wrong bootloader, plz plz plz.

zamboniman87 said:
I was just backtracking my steps and realized the mistake I made. I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi). Major opps!!
Click to expand...
Click to collapse
Dammit, I just made this exact same mistake. Came here to XDA looking for help, and it seems that this may be one of those things that you simply can't recover from... sad day!
---------- Post added at 11:40 AM ---------- Previous post was at 11:09 AM ----------
SteveRiley said:
Dammit, I just made this exact same mistake. Came here to XDA looking for help, and it seems that this may be one of those things that you simply can't recover from... sad day!
Click to expand...
Click to collapse
Well, now isn't this weird... I unplugged the USB cable from my PC and then plugged it into the wall charger. After waiting a while, I was able to boot the Nexus into the "wrong" bootloader. I immediately flashed the correct one, and now am running the latest factory image.
@zamboniman87 -- I did find a thread on Android Central describing a situation in which someone erased their bootloader. The thread contains a tool that a couple folks claimed to help fix the problem. You might give that a try.

Lucky you! This gives me hope though. I'll check it out. Thanks!

xateeq said:
Plz dont tell me u flashed wrong bootloader, plz plz plz.
Click to expand...
Click to collapse
yep.... I feel dumb. haha.

xateeq said:
My friend if u can enter fastboot then u can definately revive ur device, it is soft brick not hard brick (soft brick = software is dead) (hard brick = hardware is dead)
I do this all the time just for fun
Let me give u step by step instructions.
1. Download this tool kit
http://forum.xda-developers.com/showthread.php?t=1766475
2. Download the proper stock image for ur device (make sure u pay attention when u download the file, u definately dont want to download wrong file and then redownload the file again)
https://developers.google.com/android/nexus/images
3. Install toolkit, Select your device and don't worry about android version because u have non rit now and install the proper drivers for fastboot to work.
4. From toolkit main screen, select (softbrick/bootloop) and accept the warning.
5. Now select (Other/Browuse option) and then select (I Downlaoded a factory image myself) option then it will ask for the image that u downloaded from google website (Step 2).
6. If u have done exactly as i said then ur phone should be detected in Fastboot mode and the flashing would start and after some time phone should show loading screen (os is booting) wait for it to boot and enjoy ur stock android.
7. Enjoy.
FYI u should have enough battery (around 50%) and to enter fastboot mode u just have to boot to bootloader (restart/ power on the device while pressing volume down button) u should see the screen with bunch of numbers e.g bootloader version etc.
Click to expand...
Click to collapse
I soft bricked my nexus 7 (2012), I was in Team Win Recovery and I selected Dalvik Cache, System, Cache, Data, Internal Storage and formated/deleted it , now I don't have system or recovery
img > https://www.dropbox.com/s/a7ojrr16lt8n27s/nexus bricked (3).JPG?dl=0
all I can load is fastboot mode
img> https://www.dropbox.com/s/jzmr7811w02r525/nexus bricked (2).JPG?dl=0
I will try to do all this steps that "xateeq" wroted and let you now how it went thanks!

psykg said:
I soft bricked my nexus 7 (2012), I was in Team Win Recovery and I selected Dalvik Cache, System, Cache, Data, Internal Storage and formated/deleted it , now I don't have system or recovery
img > https://www.dropbox.com/s/a7ojrr16lt8n27s/nexus bricked (3).JPG?dl=0
all I can load is fastboot mode
img> https://www.dropbox.com/s/jzmr7811w02r525/nexus bricked (2).JPG?dl=0
I will try to do all this steps that "xateeq" wroted and let you now how it went thanks!
Click to expand...
Click to collapse
hey it worked thanks!
at first there were problems with fastboot and drivers somehow usb 2.0 was a bit problematic but usb 1.0 was able to see device
after downloading many drivers (some from nexus tollkit some from web) , and after few restarts of device and bootloader, pc was able to recognize device and than I had to go 2 times with nexus tololkit >softbrick/bootloop
1st time failed
2nd time worked!
thank all!

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?