[SOLVED. READ BELOW FOR DETAILS]
HI all.
I've managed to brick my Hero (T-Mobile G2) by flashing the wrong SPL file.
To make things more difficult I've lost the USB cable.
I can still:
Power+Menu (three vibrations + blinking green)
Power+Back (Fastboot)
Power+Search (Storageclean)
Power+VolumeDown (HBOOT, SD checking ...)
Is there a way to reflash the right SPL with one of these menus?
I've not found any similar case here and in MoDaCo.
Thanks in advance.
[SOLUTION]
This case is particular as there is no system available to use the "adb shell" commands. Nonetheless it's recoverable.
At least in one case
Almost everything comes from MoDaCo.
Despite I would say I'm not a real newbie, this time was a little bit harder than with other embedded devices for some reasons I'll explain later.
What do you need?
1. A miniUSB cable. Now I know that any miniUSB can work.
2. A Windows XP PC. A Linux or Mac OS X should also work. Read below.
3. The right USB software driver (I used this one) otherwise it won't work.
4. A modified recovery image (I used this one) that has flashing capabilities from the SD.
5. A working SPL (Second Program Loader) image (I used this one, thanks to the enlightner.
6. A system ROM image (again, I used this one).
What was the problem?
I used to play also with a Magic and still had an SPL zip of its on my SD.
I already had rooted and modded my Hero with MoDaCo's mod.
By mistake I flashed that SPL zipped image into my Hero and since then nothing was working any more.
The boot process was simply stopping at the "G2 Touch T-Mobile" screen up to the complete battery drain.
The directions found here were ineffective due to the fact that there was no running system to execute the "adb shell" commands.
I am using 99.99% of the time a Linux laptop but decided to get a Windows XP PC in order to simplify the troubleshooting while asking people for help and hints.
Maybe in the future I'll dare to reproduce the problem and solution with Linux. Maybe,
But let's see a stepwise procedure.
How I solved it (impossible to me without MoDaCo's and englightner's help, kudos to them)!
0. Unpack the USB driver and the recovery image ZIP files somewhere into your PC. Put the SPL and the system ROM image zip files into the SD card. Use the root directory of the FAT partition in case you have already partitioned it.
1. Switch off the Hero (by pulling the battery out).
2. Turn it on again without the USB cable in by pressing the back and the power keys. I've noticed some different behaviour if you keep the cable plugged in.
3. A white screen (the Initial Program Loader aka IPL aka Fastboot) will pop up.
4. Plug the USB cable in both the Hero and the PC. The screen will now show in red "FASTBOOT USB".
5. Windows should warn you about some unknown hardware having been plugged (Android 1.0). Ask for a manual installation by browsing to the directory where you unpacked the USD driver. Install it. No reboot is required (unbelievable!).
6. Open a command line session on your PC (Start-->Execute-->CMD on Windows), change the current directory (cd) to where modified recovery image has been unpacked and where both the fastboot.exe and cm-hero-recovery.img files are located.
7. From the command line run this command (without the quotes): "fastboot boot cm-hero-recovery.img". You'll see a green progression bar rising on the right side of the Hero screen and after 1 second you'll see the modified recovery image running.
8. At this point I tried to recover a previously saved nandroid backup. But for some reason this time the recovery was complaining about a chown/chmod not being able to change the permissions on a system file! So it's useless to try it.
9. Instead I asked to flash the SPL zip file. It worked fine and I asked for a reboot.
10. the final step was to pop the recovery tool again (Home+power, keep the home pressed until you'll see the friendly black and green screen) and to slash the system ROM zip file.
I also reset all user data before doing it. I'm not sure whether this reset is required.
11. At the reboot the flashed system ROM was happily waiting for me to customise the settings.
12. As a last check, I rebooted once again the Hero to see whether the solution was permanent. And it was.
Few suggestions for seniors.
Please, please be patient with newbies. This could be the first time they hit the wall and panic and frustration can play an important and irritating role.
Please, please be as precise as possible. What a senior thinks is an implicit piece of information, can lead to hours of frustration for the newbie. For example, the SUB driver installation is not mentioned very often in any thread. It looks trivial. It's not.
Please, please be positive to newbies. By encouraging them they'll become less newbies than they are now.
And a few suggestions for juniors (like me).
Please, please don't panic! If there's a solution, you don't need to panic. If there's none, you don't need to panic as well.
Please, please be precise in describing the problem (I've not been myself). Small unseen details can matter a lot.
Please, please don't blame people for late answers. Very probably they are busy with their own job, life or hobbies.
Please, please remember that if you are in trouble is very probably due to your own mistakes. Not someone else's. You are playing with low level stuff, not just application settings.
If you decide to follow someone's directions, please do it carefully. If you take some decisions on your own, please document them in the thread.
If you can get to fastboot with power and back, then all is not lost. And most importantly it's not a 'brick'. A 'brick' is a device that won't turn on.
You can flash the recovery via fastboot (using this guide) then a new ROM (I suggest my custom ROM) but, er, you're obviously gonna need a USB cable!
P
I was already using your marvelous mod, though.
I only took the SPL file from the wrong directory (I have been playing also with Magic, aka G1).
The cable is a huge problem, now.
At the moment I'm using a mini-USB cable which is good for charging the battery, but has no effect on the communication side.
Can I put some file in the SD card from my PC in order to have it booted into?
I still have a couple of nandroid backups in the SD but have no idea whether this makes any difference.
Anyway, thanks not just for the hints. Your 1.5 (1.5.1 when I'll fix my problem) rocks!
A real miniUSB cable should work fine. Yours must be only wired for charging. Go and buy one.
There's no other way to do it unless power+home gets you into recovery (which it sounds like it should?)
P
The mini-USB comes from my USB 2.5" HD.
It works with cameras and other mini-USB devices for full dvice access.
But it does not work with the Hero.
The original cable looked different from this one because of the asymmetric shape (and possibly an extra pin or two).
The Hero cable looks like it's proprietary design and buying one seems quite difficult. Would any HTC USB cable work?
Now I'm not in the Netherlands anymore and here the HTC stuff looks quite uncommon to have a cable lent.
I never use my HTC cable, I use a standard mini USB cable.
P
OK.
I've bought a brand new mini-USB cable. It works with my Nokia phone, my digital camera dnd also my USB disk.
1. I've donwloaded the file from the guide MoDaCo referred previously.
2. I've unpacked the ZIP file, opened the CMD session, CDed to the directory containing the adb.exe file
3. I've booted the phone to the FASTBOOT (VOLUMEDOWN+POWER)
4. I've connected the phone to the cable.
5. The HERO screen says now "FASTBOOT USB"
6. I've run the command "adb shell reboot bootloader"
7. I get "error: device not found".
What's next?
P.S.
Steps 3 and 4 are not mentioned in the guide, though.
You can't use adb shell from the fastboot screen, you need to boot a recovery image using the "fastboot boot <filename>" command.
Just of curiousity. What is the HBOOT version displayed on your fastboot screen?
Could you type all the text it displays?
I might be able to help you out.
Try following the guide linked above.
You can't do ADB until you've done the 'fastboot boot cm-hero-recovery.img'.
Seriously... how hard can it be to read thru a handful of steps!
P
You are right! It's hard unless you already know how to.
I quote:
- download this file and extract it to your PC or mac
- open a command prompt to the directory containing the extracted files
- type the following commands (prefix each command with ./ if you're on a mac)
So far it's trivial ...
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
That could also be trivial if:
1. I knew about the driver installation (quite later in the thread)
2. I knew in which initial status the phone is to be
Of course, a bit at a time I find everything.
Maybe re-editing the original post to include all the bits in one single place would both boost the success rate of n00bs like me (really) and lower the amount of stupid questions (really) like mine.
Anyway, I need to thank you very much!!!
Hmm, bad news, ust spoken to an extremely knowledgeable friend of mine, and he says your device is knackered.
P
I'm impressed the SPL actually booted on a Hero.
It's is a "real" Hero you have right? aka T-Mobile G2 Touch?
Fastboot can be used when you are in HBOOT, with FASTBOOT USB being displayed.
So, if this doesn't work, you're screwed.
- download this and extract the rom.zip
- copy the .zip to your SD card and name it HEROIMG.zip
- turn on your device with volume down+ power
If it doesn't start flashing, buy a new Hero.
P
packetlss said:
You can't use adb shell from the fastboot screen, you need to boot a recovery image using the "fastboot boot <filename>" command.
Click to expand...
Click to collapse
Good to know. I have no idea about this specific device!
And the help is quite fragmented among a large number of threads.
packetlss said:
Just of curiousity. What is the HBOOT version displayed on your fastboot screen?
Could you type all the text it displays?
Click to expand...
Click to collapse
HERO CVT
HBOOT-1.33.2005 (HERO10000)
MICROP-010e
RADIO-6.35.05.15
Apr 20 2009,15:30:43
packetlss said:
I might be able to help you out.
Click to expand...
Click to collapse
I hope so.
Try doing what modaco suggested and see where that ends up.
modaco said:
So, if this doesn't work, you're screwed.
- download this and extract the rom.zip
- copy the .zip to your SD card and name it HEROIMG.zip
- turn on your device with volume down+ power
If it doesn't start flashing, buy a new Hero.
P
Click to expand...
Click to collapse
I hope to fix mine.
Anyway, is there any comprehensive guide about the booting (not rooting) process with the software stack and the "cheat codes"?
I don't think I'm really a n00b, but the fragmentation of information is quite large for these marveloous Android phones.
The HEROIMG.zip has been flashed, I presume, as a vertical blue bar appeared on top right screen.
After fre minuted the process ended ... with no news.
At the reboot everything is again as before.
Home+Power won't make the CyanogenMode+JF menu pop up.
The simple boot itself won't make my Hero botting in any system.
Only a big "G2 Touch T-Mobile" on the black background.
Now what?
That HEROIMG.zip contained a hboot. When you boot to bootloader is still the same?
You say 'fastboot boot recovery.img' (as per my instructions) didn't work?
P
'fastboot boot recovery.img' works.
It's the subsequent step that doesn't. I cannot mount /sdcard (error: device not found)!
And even recovering a previous nandroid backup won't help.
What I understand there's something in between the fastboot and the actual image (the SPL?) that is missing doe to my original error.
Does the bootloader still show the old version?
P
Related
I can't get fastboot to work. I never have really tried it before, so maybe I'm just doing it wrong, but when I turn the phone on using the camera + power method, I get the Androids with skateboards, press back to enter fastboot mode. When I connect the usb cable, it shows "fastboot usb" for one second on the phone, then goes back to "fastboot". I try to connect using the comand prompt all I get is "waiting for device"
Here is what I'm running
Dream PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
ROM: Dudes 1.2
Aero Theme
I do have the USB drivers for both bootloader and ADB with the fastboot.exe file with the SDK/tools folder.
I am running Windows XP professional.
I thought it might be the new SPL from haykuro, so I flashed back to the old Hard SPL with no luck. I have uninstalled the fastbood & ADB drivers, then re-installed them and it still doesn't work.
I searched the forum also & found some people with similar issues, but none of their fixes worked for me.
If somebody could give me a check list of things to check, I would appreciate it.
Thanks in advance.
did you try re-installing the drivers after you plugged in the USB it fastboot? i had a problem similar to this a long time ago, and the drivers were only loading in normal mode when android was booted up for adb and all that good sh*t. i booted into fastboot, plugged in the usb cable, and installed the drivers while at the fastboot screen. hope this helps any
I think I have. I kind of remember uninstalling the drivers, restarting my computer, plugging it in (while in fastboot) and installing the drivers when the "found new hardware" screen popped up. Guess I will try it again and report back.
Thanks.
I fixed it...
Okay, I figured out what I was doing wrong.
I checked the usb driver, found that while installed, it was not enabled. I went ahead and re-installed it from the android sdk just to be sure. Afterwards I found that when I was in fastboot mode, it would say "fastboot usb" instead of just "fastboot".
I still couldn't get use fastboot on my computer and see the device attached.
Turns out I am also an idiot. What I was trying to do is flash a new boot screen. I was reading this post:
aron4588 said:
This is updated with the lastest tool. (Windows)
I included a zip with all files you may need at the bottom of the post.
1. Turn off your phone
2. Turn on the phone into bootloader (camera+power).
Make sure it say fastboot in the middle if not hit back and it should appear-
3. Make sure your device is found in device manger
If you don't see adb device up top in device manger find the yellow mark devices
Right Click, update driver, and point to the location of the USB Driver
(http://dl.google.com/android/android_usb_windows.zip)
4. Open and extract the below zip to your desktop
You should now have a custom and fastboot folder on your desktop
5. Open up a dos window (start>run>CMD)
6. Type cd desktop then cd fastboot
7. If you would not like to flash the sample images skip to step 9
8. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565
fastboot reboot
Part 2 Making your own images
9. Open up the "create" folder
10. Run CreateG1Splash.exe
11. Open up your image in the program and click convert
12. Goto the folder of your images and their you will find mysplash.rgb565
13. Place the mysplash.rgb565 into the fastboot folder
14. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565
fastboot reboot
Files updated 1/4/08
Credit to JF for all app to make this possible
Original G1 Bootloader/Splash Image
Click to expand...
Click to collapse
trying to do it. I was following the post trying to run fastboot from the desktop directory (which the folder was there). However when I tried running it from the SDK/tools folder on the root of my C: drive everything worked great. I have a new boot screen and everything was easy after I figured out to do it all from the /tools folder.
Even though I didn't get a lot of support with this problem I posted, I would still like to thank everybody here at XDA. I try to keep my questions down to a minimum and search the forum, among other places, before I ask the help of everybody here.
Thanks again.
NICE!!! I tried a whole bunch of solutions as well. Finally, I stumbled on yours, and it worked! Hell yeah! I think maybe adding fastboot folder to the path of system variables may have done the trick, too.
Thanks!!!
ccunningham83 said:
I can't get fastboot to work. I never have really tried it before, so maybe I'm just doing it wrong, but when I turn the phone on using the camera + power method, I get the Androids with skateboards, press back to enter fastboot mode. When I connect the usb cable, it shows "fastboot usb" for one second on the phone, then goes back to "fastboot". I try to connect using the comand prompt all I get is "waiting for device"
Here is what I'm running
Dream PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
ROM: Dudes 1.2
Aero Theme
I do have the USB drivers for both bootloader and ADB with the fastboot.exe file with the SDK/tools folder.
I am running Windows XP professional.
I thought it might be the new SPL from haykuro, so I flashed back to the old Hard SPL with no luck. I have uninstalled the fastbood & ADB drivers, then re-installed them and it still doesn't work.
I searched the forum also & found some people with similar issues, but none of their fixes worked for me.
If somebody could give me a check list of things to check, I would appreciate it.
Thanks in advance.
Click to expand...
Click to collapse
best advice i got was load up your phone is fastboot connected to pc...run the same commands in cmd but go through SDK/Tools and run fastboot from there once your in tools...skip putting it to your desktop...that didn't work for me
Hey guys, I have a problem, the driver is installed, but I can't see the device when I go to the cmd. I need help please!
Also, since my recovery is dead, and my cyanogen rom is dead, I have no way to revive my phone... can anybody help me please?
99.9% of the problems with getting fastboot to work are actually problems with windoze and incorrect_drivers/driver_conflicts/windoze_is_retarded.
Best thing to do is use Linux. No special drivers needed.
And this is not to start a linux is better than windoze fight (even if it *is* better )... it is simply a matter of this; android *is* linux, it was developed with linux, that's what all the platform developers use, and simply put, it is absolutely and fully compatible, so when all else fails, that is what you should use as well.
Option a) grab latest fedora livecd and boot off that,
Option b) grab latest fedora installdvd and install it to something and boot it up,
Then:
copy the fastboot executable into any directory (download from developer.htc.com),
connect USB,
put phone in fastboot mode,
./fastboot flash {partition} {image}
And it'll "just work".
Note: http://www.fedoraproject.org/en/get-fedora
omg. countless hours spent on trying to do this. and all i had to do was to use the fastboot in the sdk? thanks youuuuuuuuuuuuuuuuuuuu!
ccunningham83 said:
Okay, I figured out what I was doing wrong.
I checked the usb driver, found that while installed, it was not enabled. I went ahead and re-installed it from the android sdk just to be sure. Afterwards I found that when I was in fastboot mode, it would say "fastboot usb" instead of just "fastboot".
I still couldn't get use fastboot on my computer and see the device attached.
Turns out I am also an idiot. What I was trying to do is flash a new boot screen. I was reading this post:
trying to do it. I was following the post trying to run fastboot from the desktop directory (which the folder was there). However when I tried running it from the SDK/tools folder on the root of my C: drive everything worked great. I have a new boot screen and everything was easy after I figured out to do it all from the /tools folder.
Even though I didn't get a lot of support with this problem I posted, I would still like to thank everybody here at XDA. I try to keep my questions down to a minimum and search the forum, among other places, before I ask the help of everybody here.
Thanks again.
Click to expand...
Click to collapse
Hi all,
I am completely at my wits end here and just don't know what to do
I have successfully unlocked my stock Nexus One boatloader, and have installed superboot to root it.
- I am using Windows 7 64 bit with all USB drivers for the nexus one correctly installed
- I have remembered to reset debuggingt mode in the Nexus USB settings
- Rooted apps seem to be working fine - I've just been playing with the LED torch app and I have a 'Superuser Permission' icon in my programs list
I am attempting to install the Amon_Ra recovery file - I've tried two different versions of it with no joy so far.... 1.7.0 and 1.6.2
I am able to boot into fastboot (with the skateboarding droids) with no probs. I can see the device using fastboot devices. However, when I try to send any recovery image using fastboot, it just hangs there with an empty progress bar on the right hand side of the screen in green that doesn't fill up.... Here is the terminal output:
---
C:\AndroidSDK\android-sdk-windows\tools>fastboot devices
HT9C(-REMOVED-) fastboot
C:\AndroidSDK\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3948 KB)...
---
Anybody have any idea why it hangs here and if there is anything else I can do to maybe figure out why? I'm pretty certain I've almost cracked it - installing this recovery image is a problem
Thanks in advance!
Gil
don't rename the recovery.img file.
Then if that still doesn't work...maybe try using a terminal on your phone. Not sure myself which terminal app works.
SiNJiN76 said:
don't rename the recovery.img file.
Then if that still doesn't work...maybe try using a terminal on your phone. Not sure myself which terminal app works.
Click to expand...
Click to collapse
Thanks for the quick response!
It still fails even when I don't rename the recovery image.
Re 'using a terminal on my phone' - is there a guide to this anywhere? Do I download a shell or something?
TIA!
Gil
Go to market and search Android Terminal Emulator.
Then follow these instructions:
via terminal app
Code:
Copy recovery-RA-nexus-v1.7.0.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.img(press enter)
reboot recovery(press enter)
Got those instructions from the Recovery thread.
It looks like fastboot is not properly detecting your device? Also, did you install "superroot" before attempting to flash recovery image?
Thanks everyone for the help so far.
SiNJiN76 said:
Go to market and search Android Terminal Emulator.
Then follow these instructions:
via terminal app
Code:
Copy recovery-RA-nexus-v1.7.0.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.img(press enter)
reboot recovery(press enter)
Got those instructions from the Recovery thread.
Click to expand...
Click to collapse
I have tried these steps - when I issue the su command, I get root and a dialog box prompting me to allow it. However, when I type the flash_image command, I get the following message:
flash_image: not found
How is it that I don't have the flash_image command on my Nexus?!
aoch88 said:
It looks like fastboot is not properly detecting your device? Also, did you install "superroot" before attempting to flash recovery image?
Click to expand...
Click to collapse
I think fastboot is detecting my device, because I managed to display the serial number (I obsficated most of the output above for security reasons) and I also successfully unlocked the bootloader. After I unlocked the bootloader, I tried to copy over the recovery image, and it just hung, so I then went and installed Modaco's superboot version ERD27 with himem enabled. This allowed me root access but still will not allow me to flash with the recovery image.
In addition, I have noticed that since I installed superboot himem, I am having a couple of network issues. Firstly - my 3G signal has now dropped from virtually full strength all the time to now never more than 50% strength, and frequently gives network errors when accessing the android store. It has also said "emergency calls only" a couple of times and probably worst of all (!) no longer checks my gmail automatically (I have plenty of emails but don't get notified - texts work fine though and my contacts are all still there and my account seems to be linked) - could the superboot have affected this in any way?
Thanks all for your help - I'm getting a little worried I may have totally borked my phone now
Gil
A little extra info if it helps anyone - I just tried to erase the recovery image in fastboot to see if I could then write a new recovery image. Here is the output:
---
C:\AndroidSDK\android-sdk-windows\tools>fastboot devices
HT9CXP8##### fastboot
C:\AndroidSDK\android-sdk-windows\tools>fastboot erase recovery
erasing 'recovery'... FAILED (remote: not allowed)
---
Anybody have any clue what this means?
Try to redownload the recovery image, maybe you got a bad download.
thisisgil said:
when I try to send any recovery image using fastboot, it just hangs there with an empty progress bar on the right hand side of the screen in green that doesn't fill up....
Click to expand...
Click to collapse
Can you try a different USB port? I found when flashing mine that it didn't like USB1.1 only worked on USB2.0
thisisgil said:
A little extra info if it helps anyone - I just tried to erase the recovery image in fastboot to see if I could then write a new recovery image. Here is the output:
---
C:\AndroidSDK\android-sdk-windows\tools>fastboot devices
HT9CXP8##### fastboot
C:\AndroidSDK\android-sdk-windows\tools>fastboot erase recovery
erasing 'recovery'... FAILED (remote: not allowed)
---
Anybody have any clue what this means?
Click to expand...
Click to collapse
Another thing I discovered recently: Never use a port on a USB hub. Always use a USB port on the PC directly. I was having trouble flashing ROMs on my Acer Liquid and they went away when I stopped using a port on the hub.
without a doubt i bet its a naming issue, this is one of those things that go unmentioned and overlooked. either u do or dont have file extensions showing or not and or the .img does or does not need to be changed to .zip, i messed with this for days last year when flashing my g1. just go and change whatever you hide/show known file extensions is set to and see if ur problem is solved.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
AndyBurns said:
Can you try a different USB port? I found when flashing mine that it didn't like USB1.1 only worked on USB2.0
Click to expand...
Click to collapse
Thank you AndyBurns. I registered just to say that. You saved me a lot of time.
I had the same problem. Had the USB cable plugged into my front 1.1 ports instead of the back 2.0 ports. Switch ports and now I'm good to go.
Thank you.
Hi all -
Just wanted to post a follow up to this message, in the hope that it may help someone in the future!
Basically, I was not using the original USB cable that came with the nexus one (lost it), and instead was using a cable that I bought from a mobile phone retailer - it was basically one of those 6-in-1 multi USB cables where I had to put an adaptor on the end to switch it from mini to micro USB to fit the Nexus one.
Anyhow, for some reason, despite the fact that I could charge the phone using this new cable, and access it through device manager, explore the contents of the phone, root it etc etc, it would not do the flash as described above. I went out and bought a dedicated 1 metre gold plated micro USB cable, and it worked great
Dodgy cables - should have thought of this before I spent days frigging around and maybe even almost bricking the phone with a bad flash
Ok, so I know this will eventually get buried in the forums but I thought I would attempt to give a little basic info here. Right now the QA section is flooded with people that have flashed and are now soft bricked (have problems but can recover) or hard bricked (have problems and cannot recover). I'm hoping that I can help some people prevent these issues to an extent.
Terminology, the differences in my opinion.
Soft brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your hardware buttons work or ADB works and you are able to boot into DOWNLOAD mode.
Hard brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your unlucky and hardware buttons do not allow access to DOWNLOAD mode or ADB is not downloading.
Also, after a new flash or flash to stock, it's a good idea to immediately enable USB debugging. Menu, Settings, Applications, Developement, check the box for USB debugging. It will make things easier later on.
1. First. BEFORE you flash, can you access download mode with your buttons??? Test it.
3 Methods.
Method 1: (ADB - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold Volume Up + Volume Down + Power
Method 3: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons (from i9000 just down, don't touch the power button)
Plug in the USB cable and continue holding both Volume buttons
If not, use designgears fix. http://forum.xda-developers.com/showthread.php?t=812434
2. Second. Download the SDK, drivers for your PC, and learn some basic ADB commands, ie, adb reboot download, adb reboot recovery, adb shell. Here's my quick guide. ADB can be used when the OS is running, when in recovery, and when stuck on ATT boot screen.
Here's what I do. After you download the sdk and unzip. There is a folder called tools. I copy that to c:
Then open a command prompt and type,
C:
CD tools
Then issue adb commands.
adb reboot, adb reboot download or whatever command you need.
Of course make sure your phone is connected via USB and debugging is enabled.
Here's another method for using adb.
1) start-> run-> sysdm.cpl
this will start the system properties. you can reach this from right clicking "My Computer" and hitting properties. Windows 7 though is different. The above method is most universal.
2) Move to Advanced Tab that pops up. From there click the "Environment Variables" button.
http://wtfokc.com/sef****/sysdm-1.gif
3) In the window that pops up, find the "PATH" area in the "System Variables" listbox at the bottom:
http://wtfokc.com/sef****/sysdm-2.gif
4) Click edit again, put in path to the AndroidSDK tools folder. Do it like shown otherwise you can biff something up. DO NOT REMOVE ANYTHING. Just add a SEMICOLON ( ; ) to the last of the line that's already there, then the path to the folder.
http://wtfokc.com/sef****/sysdm-3.gif
5) If on Win7 you shouldnt have to reboot. XP however will. Then you are set. You can now just load a CMD prompt and do ADB without having to CD TOOLS.
3. Third. Install Clockwork Recovery! Root your phone and download ROM Manager from market. Install Clockwork recovery from ROM Manager. BOOT into recovery to make sure it works. You will have to choose reinstall packages from stock recovery. What ROM Manager does, it put an update.zip on the root of your SDcard, then when you choose reinstall packages from stock recovery it install update.zip. I personally leave the update.zip file on my sdcard at all times, just in case.
Once you have clockwork installed, make a Nandroid backup of a good running rom. In case something happens, if you can boot into recovery, then you can possibly restore your nandroid to at least get you up and running quickly, and without the need of a pc.
NEW Info!!! You can recover from a hard brick, maybe. Here's how to create a USB Jig to reproduce the button download mode for you folks who don't have it.
http://forum.xda-developers.com/showthread.php?t=841512
Here's another thread about the USB Jig method.
http://forum.xda-developers.com/showthread.php?t=819551&highlight=USB+jig
If my captivate was one that had the missing button recovery/download out of the box, I would probably know how to make a USB jig or have one already before flashing. Even with the 3 button fixes that are out, it looks like some people are still bricking.
****Disclaimer****
This is just from personal exprience. I have flashed most roms available, and I have experienced every variation of soft brick mentioned above and have recovered.
I find that being able to get your phone into download mode and knowing how to use Odin will be your 2 biggest life savers after something bad happens.
This will not keep you from getting a bad flash or something else, but having this knowledge ahead of time may help you recover from issues more quickly and without asking a question on the forums that have been asked dozens of times.
Also, personally, if I cannot perform step 1, access download mode with buttons, I personally would be VERY cautious about flashing! ADB reboot download is nice, but if you are stuck at ATT logo or phone--!--PC mode then ADB doesn't work, YOU HAVE TO USE BUTTONS.
Just my 2 cents, take it or leave it.
Edit. Added some new info to post. Thanks for extra info guys. I'll mirror the links to the images later when not at work.
+sticky
excellent write up. a must-read for anyone even thinking about flashing
Original Post updated to add my information
bobbylx said:
ADB reboot download is nice, but if you are stuck at ATT logo
Click to expand...
Click to collapse
Ok first off something that should be added to this is always may sure you have usb debug mode Settings>Applications>Development>USB Debugging enabled on your phone. Don't take it out of debug mode. This will allow you to issue adb commands if you have.
If you are getting to the att logo screen and not beyond that and you have debug mode enabled then you can use adb to reboot into either recovery or download mode.
Steps
1: Get the command prompt up and que up the adb command you want to issue either reboot download or reboot recovery. Don't press enter yet.
2: When the att screen comes on your pc should make a notification sound that the device is connected.
3: On the second notification sound issue your adb command and the phone will reboot into the mode you selected.
Mileage may vary but should work.
This has saved me a few times.
STICKY
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks for the extra info. Malfuncion, awesome write up with pics, I'll add to first post later. I always forget about adding a system variable.
Sparker366, thanks, I always thought that at the ATT screen adb didn't, but you know what, I never tried.
I figured since I'm not a dev and don't have that knowledge I would try to help start this up to contribute a bit. And honestly, if you hop over to the QA sections there are so many threads that could be solved by knowing this info ahead of time. I doubt everyone will read it, but I hope it helps the ones that do.
bulletproof1013 said:
STICKY
Click to expand...
Click to collapse
+1
This is my first smart phone and first experience with Android. I also don't have any experience with linux. Fortunately, I was able to avoid problems when I first started by reading, reading, reading. This type of information would have been invaluable. In fact, the tip on keeping debug mode on all the time is great to know, and I never saw that before.
Sent from my SAMSUNG-SGH-I897 using XDA App
This thing is getting buried in the BS posts....BACK TO THE TOP!
definitely sticky
Bump Bump Bump
Great Info
Updated original post with extra info.
Shameless bump here. New version of Cog uploaded, so that means there will be questions soon.
Thanks, great info.
FWIW........
I feel like I am of average intelligence, and would think I could nail download mode everytime by the 3 button method, but damn if it is hit and miss for me every other time.
One way I found (I didnt discover it, but read it somewhere) to nail it EVERYTIME is to remove sd and sim. Plug the usb to the phone AND THE PC, while odin is sitting and waiting. Then while holding both up and down volume buttons, insert the battery. It works every time with no fuss.
Thanks for the post, my vote for sticky as well.
+1 sticky
Sent from my SAMSUNG-SGH-I897 using XDA App
Moving this to the top. More questions in QA that can be helped by reading these tips first.
I would also suggest that anyone who wants to flash actually test their phone's USB transfer ability before flashing.
The best way is to find a large file, perhaps one just under 2G in size and transfer it to the internal SD storage.
Test md5 checksums on the source and this file and make sure these match.
(you can use the 'md5sum <filename>' command from the terminal app, from Windows you can use a md5sum port for the source file win32 md5sum).
This will ensure your USB connection is stable enough for long, error free transfers to the phone.
Also important: it's useful to disable any powersave actions on your PC while using an app like ODIN.
Sorry all, moving this to the top. There are about 6 or 7 bricked phone Questions in Q & A now.
Awesome, clear and concise. Been trying to figure out how to make nandroid backups and this explained it very simply Thank you!
thanks for the reminder
there's so many steps to install a rom...
specially with download mode keycomb, i tend to not to remove sim and memory card cuz i dont want to lose or damaged my mcard. now i will remove each time!
another good reason flashing stock with odin before flashing new rom
I would also say its a good idea to back up your efs folder. Mine got all borked up when that jpc rom came out a while ago and it is a ton of work to fix. Sgs tools copies your nvdata.bin and. /nvdata.bak files to your sd card if you do a product code check. Or you can use root explorer.
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.
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?