Database Users

Need Help: Updating CM, Stuck

[Edit] I got the CM 1.4 recovery to flash and updated CM from sd card... Then hit reboot. It's been sitting on G1 screen for like 10 minutes. Do I need to wait longer or is this a bad sign? What should I do?
Please help!
THank you!
------
Hi guys...
My phone = stats in my sig. (Sorry, its the only way I can keep up with all the details.)
Okay... rephrasing this.
I'm trying to upgrade from the stats below to the current Cyanogenmod. http://wiki.cyanogenmod.com/index.php/Main_Page tells me to do one of three things, none of which tell me how to get rid of Dark Hero theme and I'm not sure about how to get it up to the latest radio/spl etc.
I flashed the recovery (terminal didn't make any feedback messages so I'm not sure if it worked?) and when I did a power-on while holding X, it didn't go into recovery so I"m kinda lost.
I just want to get the latest Cyanogen mod up and running. (Latest stable, not 5.x)
If anyone can give me a hand I'd really really appreciate it.

arsieiuni said:
Hi guys...
My phone = stats in my sig. (Sorry, its the only way I can keep up with all the details.)
Okay... rephrasing this.
I'm trying to upgrade from the stats below to the current Cyanogenmod. http://wiki.cyanogenmod.com/index.php/Main_Page tells me to do one of three things, none of which tell me how to get rid of Dark Hero theme and I'm not sure about how to get it up to the latest radio/spl etc.
I flashed the recovery (terminal didn't make any feedback messages so I'm not sure if it worked?) and when I did a power-on while holding X, it didn't go into recovery so I"m kinda lost.
I just want to get the latest Cyanogen mod up and running. (Latest stable, not 5.x)
If anyone can give me a hand I'd really really appreciate it.
Click to expand...
Click to collapse
A couple of things:
5.0.7 IS the latest stable build. If you want 4.2.15.1, you're going to have to search the forum for it because Cyanogen is no longer working on Donut (1.6) builds.
However, if you want the latest CM, its very simple.
First, download either the latest clockwork recovery or amon_ra recovery. follow the instructions to flash recovery. to check if it installed correctly, you dont power on while holding X, you power on while holding the home button. (alternately, grab the "quick boot" app from the market and you can one-touch boot to recovery or bootloader from your home screen)
Next, download the latest radio and appropriate SPL. In order to install these, follow the instructions here:
http://wiki.cyanogenmod.com/index.php/DangerSPL_and_CM_5_for_Dream#Prerequisites
Note: MAKE SURE YOU FLASH THE RADIO FIRST OR YOU WILL BRICK YOUR PHONE.
Once you follow those steps, you'll have CM 5.0.7 installed.
EDIT: I noticed you grabbed CM recovery 1.4. That recovery is old and outdated, also no longer supported. You need to grab one of the recovery files I mentioned.

Crap...
So trying to follow the instructions at Cyan WIki...
And like I said above, it's now sitting on G1 screen indefinitely...
Have I lost my phone?
Is there any way to fix this?

power off the phone by pulling the battery. boot into recovery by holding home+power. plug your phone into your computer. once there, use ADB from your computer to flash the new recovery, then power the phone off again. power it back on into recovery again (home+power) and then follow the steps in the wiki page i linked you to.

OMG that's wonderful I thought I had ruined it!
But I have no idea how to use ADB. I have never used it before. I found the site but I'm totally lost at that point o_o
If I plug phone into my computer it doesn't recognize to let me access the folder so I can't add files there since I can't Mount it.
How do I add the recovery from ADB?

ok, first things first, make sure you have your drivers installed and adb working (for this, youre going to need the adnroid SDK installed, which can be found here: http://developer.android.com/sdk/download.html?v=android-sdk_r06-windows.zip). to check and see if adb works, open a command prompt on your computer(start>run>cmd), navigate to the sdk tools directory (for example, mine is C:\android\tools\ yours might be different depending on where you install the sdk) and then type "adb devices" without the quotes. if it shows your device connected, proceed to the next step:
Copy the recovery image you're going to install to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your G1 via usb to your computer and type the following commands into the command prompt
adb shell
#mount -a (this can give back an error if you don't have an ext partition, don't worry about it and just proceed)
#flash_image recovery /sdcard/custom-recovery-name-here.img
once that's done, you will have your new recovery going, then proceed with the steps to upgrade the radio and SPL from the wiki page i linked earlier. after you have the radio and SPL done, flash CM and you're all set!

Okay... I tried to use the SDK to install the drivers (it says in INstalled packages: Drivers r3) but It's not showing up under ADB devices when I check it in CMD.
It just says List of Devices: then there's nothing.
I think maybe because my phone won't go past recovery right now, I can't get the drivers working?
Is there a place I can manually download the drivers so I can manually install them?
I went in and followed the instructions here; http://developer.android.com/sdk/win-usb.html to install or upgrade and either way my computer is telling me I have the best driver installed for the HTC android phone. I don't SEE a place exactly like they say that says ADB Interface device.. that doesn't even appear on my list.
I really, really wish I could find my sd card adapter. That would make this considerably easier.

Please could someone help with the last question above?
I'm trapped at this point and can't figure out how to go onward.

For starters, don't flash your radio or SPL. FASTBOOT them.
Setting up adb is very useful. Download the sdk and extract it to where ever you want it and add the "tools" folder to your windows Path. There and HUNDREDS of tutorials on how to do this. Google it. Fastboot is just as easy as using adb, and safer than flashing.

Read BEFORE flashing!!

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.

Unable to install Recovery on streak..will not boot. completely lost.

Hi guys
Let me start off by saying..I should have never attempted this myself.
I'm hoping somebody could please help me with my somewhat-bricked device..bricked in the sense that I don't know what to do with it. (i'm a noob to this). I've tried installing a custom rom and completely screwed up my dell streak 5.
So the phone doesn't boot anymore and just takes me to the option to install update.pkg off the sd card. I added the file along with recovery.img to the sd card.
360 17397 00 May 31, 2011 PKG Recovery Hash Latest Retail rom
My problem is that I cannot for whatever reason get Flashboot to work in order to flash the recovery.img first. under device manager you see android phone/android adb interface but still can't manage the connection to use cmd prompt/fastboot.
Is there any other way of getting the recovery.img to work without fastboot..maybe thru the sd card. I have no idea what i'm doing anymore. I've tried installing the update.pkg but after installation it just stays on the dell logo loading screen forever.
PLEASE help if you can.

Well lets start off to get you back on a stock rom, as it sounds like that would be the easiest at this point. We can move on to a custom rom from there.
The pkg file you downloaded....did you rename it update.pkg ?
If not, rename it update.pkg and make sure it is on the root of your sd card. Get to the recovery menu where you have the option of upgrading from update.pkg and choose it. In about 5 minutes, you'll have a clean stock rom.

I tried installing the 360 rom listed on http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
I did name it update.pkg
It went through the installation phase but on reboot it doesn't get past the Dell Logo loading screen. Any suggestions?

On the screen where you choose upgrade from update.pkg, choose factory reset and see if that helps

Tried both..unfortunately, same end.
Is flashing recovery a required step prior to doing this..because I was unable to do that.
Also, Thank you for taking an interest. I really appreciate it.

yes, you need to have the recovery for the rom you are flashing (at least when it comes to stock roms). My understanding is that the pkg file is encrypted and the recovery decrypts it.
I'm going to try to start from scratch here. I am also assuming you are using a Windows PC.
Download the drivers from Dell. Here's the link:
http://support.euro.dell.com/suppor...dateid=-1&formatid=-1&source=-1&fileid=433681
Install them and reboot your pc.
Download MultiRecoveryFlasher from here:
http://forum.xda-developers.com/showthread.php?t=1000455
Extract it to somewhere on you pc where you can find it.
Now this hasn't been updated to include 360's recovery, but that's ok. We don't have to run the utility. It's the support files that are included that we are going to use.
Download the recovery.img for 360 (which I think you have already done)
Put the recovery.img in the root folder of MultiRecoveryFlasher. There should be other files in there such as fastboot.exe, adb.exe, etc.
Power down your phone and restart it in fastboot mode (hold down camera and power button together until you get a white screen. When fastboot appears in upper right, select it and plug your phone into your pc)
Verify the phone displays fastboot ready
Open a command prompt on your PC
Type in the following command: fastboot.exe -i 0x413c flash recovery recovery.img
Once that is done type in the following command: fastboot.exe reboot
Get ready to hold down the Volume + and - as soon as the screen goes black.
Now choose Upgrade from update.pkg
It should work now. If not, someone else may have to help you with another method such as QDL tool. I've never had to use that.

This is a screenshot of the problem i keep running into. i installed the drivers just as you said and am at the step with fastboot.
imgur [dot] com/gw2A0
Any advice? Thanks again

im an idiot.
i got fastboot to run and send over the recovery.img
currently installing the update.pkg but its still stuck at the Dell Logo screen upon reboot. No idea what is going on.

FIXED. You're a miracle worker. Thank you so much.
Only problem I have now is an irritating sequence of flashing buttons every now and then. Have you had a similar issue in the past?
THANK YOU so much again!

Are you on a stock rom still? Or have you moved on to a custom rom? Typically the flashing led's happen when you are running a rom with an "incompatible" baseband, but that should be pretty near impossible if you are running a rom installed from an update.pkg rather than an update.zip.

running the update pkg off the wiki site.
Only other problem I've noticed is that I can't get it to root. I've tried gingerbreak and superoneclick..both of which worked flawlessly in the past.
Baseband GAUSB1A134700-US
KERNEL 2.6.32.9-PERF
BUILD 17397
I really want another crack at getting streakdroid, but the phone just isn't budging. Tempted to flash/install another rom but worried as heck that this same incident is going to come up. (the flashing lights started after i updated the AMSS and DSP last night--my first attempt at installing streakdroid 2.3).

Installing the stock rom via the update.pkg file will overwrite the amss and dsp1. That's the biggest difference to the end user on update.pkg vs update.zip. It's the actual recommended way to install a baseband. There are several firmwares, besides amss and dsp1, that get installed with a pkg.
Now that you have MultiRecoveryFlasher on your pc, installed StreakMod (custom recovery) should be a breeze for you. The only thing to watch out for is since you have a stock rom now, the first time it boots it will rewrite the recovery back to stock. Here is how to get around this:
Download the custom rom of your choice.
Place the zip file on the root of your sd card.
Get your phone back in fastboot mode
Using MultiRecoveryFlasher, flash StreakMod
As soon as the screen goes black for the reboot, hold the volume +/- keys.
Choose option 2 again, this time it should take you into StreakMod
Choose flash from update.zip
On the next screen, choose search for zip file (similar wording)
Choose the custom rom from earlier
Let it do it's thing.
Choose reboot system now
Again, as soon as the screen goes dark, hold Volume +/-
Now choose option 1 - Factory Rest
Let it do it's thing.
It should boot up now and your custom recovery will stay intact.
Let me give you some friendly advice: Streakdroid 2.3 is too much of a work in progress. Install one of the other Streakdroids, Longhorn, Simple Streak, or even my Streakin' 354. Play with it for a while and learn a little more before jumping into one that may not be as stable.
As far as rooting a stock rom, the preferred method is via superuser.zip. I'm not at home, so I don't have the file to upload for you, but its on these Dell Streak forums somewhere. You have to have a custom recovery to use it though. The custom roms are all rooted already.

Thank you for everything

No problem. Did you get it working?
Sent from my Dell Streak using xda premium

Absolutely and I couldn't have done it without you. If you had written out just one of the x number of tutorials out there, I don't think anyone would have run into the problems I did at first.
Streakdroid 191 runs like a charm---snappy and more responsive than stock ever was.

Glad to hear it...I was lost when I first started too. Someone helped me out and I just like to pay it forward. It's what makes this forum my favorite.

lordmorphous said:
Glad to hear it...I was lost when I first started too. Someone helped me out and I just like to pay it forward. It's what makes this forum my favorite.
Click to expand...
Click to collapse
Hi guys.. Hi Mr Lordmorphous.. im a super noobie in dell streak 5.. i got my dell streak a month ago.. today my phone doesnt work.. im stuck on Dell logo when i am going to switch it to on.. i really dont know where to start and how to type the codes like you are talking about like .pkg ing. etc. .. when im pressing the factory reset nothing happens.. i also tried to click software upgrade via update.pkg on SD card and nothing happens .. i clicked also the screen calibration it says *successful calibration done*.. im totally lost.. can u help me how to start from beginning (like for super noobie like me)? also the codes that im going to type in pc.. thanks in advance!

dwadetiu said:
Hi guys.. Hi Mr Lordmorphous.. im a super noobie in dell streak 5.. i got my dell streak a month ago.. today my phone doesnt work.. im stuck on Dell logo when i am going to switch it to on.. i really dont know where to start and how to type the codes like you are talking about like .pkg ing. etc. .. when im pressing the factory reset nothing happens.. i also tried to click software upgrade via update.pkg on SD card and nothing happens .. i clicked also the screen calibration it says *successful calibration done*.. im totally lost.. can u help me how to start from beginning (like for super noobie like me)? also the codes that im going to type in pc.. thanks in advance!
Click to expand...
Click to collapse
RTFM
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak

Hi again guys.. and mr lordmorphous!
im following what you told him (aaivazi)..
I'm going to try to start from scratch here. I am also assuming you are using a Windows PC.
Download the drivers from Dell. Here's the link:
http://support.euro.dell.com/support...&fileid=433681
Install them and reboot your pc.
Download MultiRecoveryFlasher from here:
http://forum.xda-developers.com/show....php?t=1000455
Extract it to somewhere on you pc where you can find it.
Now this hasn't been updated to include 360's recovery, but that's ok. We don't have to run the utility. It's the support files that are included that we are going to use.
Download the recovery.img for 360 (which I think you have already done)
Put the recovery.img in the root folder of MultiRecoveryFlasher. There should be other files in there such as fastboot.exe, adb.exe, etc.
Power down your phone and restart it in fastboot mode (hold down camera and power button together until you get a white screen. When fastboot appears in upper right, select it and plug your phone into your pc)
Verify the phone displays fastboot ready
Open a command prompt on your PC
Type in the following command: fastboot.exe -i 0x413c flash recovery recovery.img
(im already here but this is what the command prompt says:
'fastboot.exe' is not recognized as an internal or external command, operable program or batch file.)
what should i do ?

Streak4ever said:
RTFM
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
Click to expand...
Click to collapse
hi streak4ever thanks for reply.. what does RTFM means? thanks

[Q] [HELP] How to root LG optimus L5 E617G WITH Jellybean 4.1.2

I lost my root after the official firmaware upgrade now i cannot root it . Please help I have tried everything in XDA please help..... frustrated as hell

bennatpjose said:
I lost my root after the official firmaware upgrade now i cannot root it . Please help I have tried everything in XDA please help..... frustrated as hell
Click to expand...
Click to collapse
have you tried to flash a pre-rooted JB?

Sabyn said:
have you tried to flash a pre-rooted JB?
Click to expand...
Click to collapse
is there a guide somewhere

bennatpjose said:
is there a guide somewhere
Click to expand...
Click to collapse
to flash a version of JB? come on my page , i can give you a link to my dropbox , there is anything you need

bennatpjose said:
is there a guide somewhere
Click to expand...
Click to collapse
i also have an e617g on 4.1.2 bell network id like to root and unlock the bootloader so i can install cwm and finally swap roms, this is a nice phone but it barely exists on the web any help would be greatly appreciated, thanks in advance

Never mind figured it out myself. I may post a guide here soon. Seeing as any help I ask for is ignored. I'd rather help than hold back

Turn your lG-e617g into an LG-e610 then root it and install cyanogenmod.
bennatpjose said:
is there a guide somewhere
Click to expand...
Click to collapse
this is my first tutorial so message me if something on here isnt clear.
step 1: download things, this is crucial, you need to download this stuff, it took me a while to find everything that ACTUALLY WORKED so i have it all in a nice little package to download.
step 2: make sure your phone is NOT plugged in the computer, install drivers if you do not have them. i have the drivers that worked for me in the package via direct download links. if they dont work for you somethings screwy with your computer and youll have to scour the internet to find drivers that'll work, google is your friend.
step 3: make sure your phone is recognised with your lappytop or computer. thats right i said lappytop, so sue me.
step 4nce all the drivers are installed and your phone is connected to the computer youll want to open up the folder labled: "LG FlashTool and Accessories" inside youll find "KDZ_FW_UPD.exe" open that right up.
step 5: next youll see a modded lg tool made by some guy on the internet, im not sure who but he/she did a good job thanks man/wo-man!!
ok youll want to leave all settings to default dont touch any thing, its good to go as is.
step 6: make sure phone is plugged in and usb debugging is enabled, use the kdz updater to browse for this file (download it via links in the package) "V10D_downgrade.kdz" then click on "Launch software update" this takes a while go make a coffee.
step 7: when its done its magic, your phone will boot up and youll see the LG logo for about 10 minutes any longer and your in a boot loop remove battery put it back in and hold both volume buttons down and power at the same time. time it carefully the lights on the soft keys will come on and a split second later the phone will slightly vibrate, the second you feel that press the home and hold it for about 10 seconds and the phone will do a hard reset, the phone will turn on now and initiate the first time use wizard, its in russian at first so just change your language to whatever, assuming english here. the phones software is now rooted just no su/superuser installed download from play store and update binary in settings of su app.
step 8: Unlocking bootloader time! after you flashed the software using kdz updater your phones ID is now technically an e610 now instead of an e617g, so unlocking the bootloader is now possible, connect your phone to computer, turn usb debugging on and drag and drop "emmc_appsboot.bin" into the root of your INTERNAL SD, also kill 2 birds with one stone here by also copying the recovery-clockwork-6.0.2.8-e610.img you downloaded via links in the txt document to the same place just rename it "recovery.img to make it easier also make sure you place the cm rom in the external sd. we need the bootloader unlocked to allow for cwm installation and good ol' rom swapping, open the folder "ADB" hold shift right click any where in the folder and select open "command window here",
type in the cmd window obviously without quotations: "adb shell" hit enter, then type "su" enter again then type "dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5" your bootloader is now unlocked, now type in "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17" this just installed clockwork mod. to boot into recovery and install cyanogen (the one im using. btw its a powerhouse compared to stock!!!) type in "reboot recovery"
step 9: factory reset, clear partition, wipe dalvik cache, install cyanogen, reboot, ENJOY.
seems i cant upload the programs needed so all i can do is this:
http://199.91.154.133/15ihz730pw2g/qwyqbfcp9fe7uhu/cm-10.1-20130725-UNOFFICIAL-e610.zip
this is the cyanogenmod rom.
http://199.91.154.102/r595o5bou5eg/bb2s0ohuj3jnflo/V10D_downgrade.kdz
this is the pre-rooted rom that allows su access to unlock bootloader this also
changes the phones id from e617g to e610, startup wizard is in russian at first simply change to english.
http://csmgdl.lgmobile.com/swdata/c...981MAN38AP22_ML_WHQL_Ver_3.8.1(0)_4.9.8.1.zip
this contains the correct drivers for phone.
http://dl.xda-developers.com/attach...65/51fc133a/1/7/5/6/7/5/9/CWM6_24-03-2013.rar
this is recovery image for cwm
and youll have to google search everything i quoted thats missing sorry about this but you need: 1) LG FlashTool and Accessories.
2) some form of adb for an adb shell.
3)emmc_appsboot.bin specifically for e610
4)lg drivers for e610/e617g
5)recovery.img for clockwork for e610
6)lastly the V10D_downgrade.kdz

I had already tried that but i keep getting the bloody error in KDZ
03:58:19 : Launching SW update
03:58:19 : Unpacking KDZ
03:58:21 : KDZ file extraced
03:58:21 : Extract file error
03:58:23 : ===FINISHED===
r4nd0m14m said:
this is my first tutorial so message me if something on here isnt clear.
step 1: download things, this is crucial, you need to download this stuff, it took me a while to find everything that ACTUALLY WORKED so i have it all in a nice little package to download.
step 2: make sure your phone is NOT plugged in the computer, install drivers if you do not have them. i have the drivers that worked for me in the package via direct download links. if they dont work for you somethings screwy with your computer and youll have to scour the internet to find drivers that'll work, google is your friend.
step 3: make sure your phone is recognised with your lappytop or computer. thats right i said lappytop, so sue me.
step 4nce all the drivers are installed and your phone is connected to the computer youll want to open up the folder labled: "LG FlashTool and Accessories" inside youll find "KDZ_FW_UPD.exe" open that right up.
step 5: next youll see a modded lg tool made by some guy on the internet, im not sure who but he/she did a good job thanks man/wo-man!!
ok youll want to leave all settings to default dont touch any thing, its good to go as is.
step 6: make sure phone is plugged in and usb debugging is enabled, use the kdz updater to browse for this file (download it via links in the package) "V10D_downgrade.kdz" then click on "Launch software update" this takes a while go make a coffee.
step 7: when its done its magic, your phone will boot up and youll see the LG logo for about 10 minutes any longer and your in a boot loop remove battery put it back in and hold both volume buttons down and power at the same time. time it carefully the lights on the soft keys will come on and a split second later the phone will slightly vibrate, the second you feel that press the home and hold it for about 10 seconds and the phone will do a hard reset, the phone will turn on now and initiate the first time use wizard, its in russian at first so just change your language to whatever, assuming english here. the phones software is now rooted just no su/superuser installed download from play store and update binary in settings of su app.
step 8: Unlocking bootloader time! after you flashed the software using kdz updater your phones ID is now technically an e610 now instead of an e617g, so unlocking the bootloader is now possible, connect your phone to computer, turn usb debugging on and drag and drop "emmc_appsboot.bin" into the root of your INTERNAL SD, also kill 2 birds with one stone here by also copying the recovery-clockwork-6.0.2.8-e610.img you downloaded via links in the txt document to the same place just rename it "recovery.img to make it easier also make sure you place the cm rom in the external sd. we need the bootloader unlocked to allow for cwm installation and good ol' rom swapping, open the folder "ADB" hold shift right click any where in the folder and select open "command window here",
type in the cmd window obviously without quotations: "adb shell" hit enter, then type "su" enter again then type "dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5" your bootloader is now unlocked, now type in "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17" this just installed clockwork mod. to boot into recovery and install cyanogen (the one im using. btw its a powerhouse compared to stock!!!) type in "reboot recovery"
step 9: factory reset, clear partition, wipe dalvik cache, install cyanogen, reboot, ENJOY.
seems i cant upload the programs needed so all i can do is this:
http://199.91.154.133/15ihz730pw2g/qwyqbfcp9fe7uhu/cm-10.1-20130725-UNOFFICIAL-e610.zip
this is the cyanogenmod rom.
http://199.91.154.102/r595o5bou5eg/bb2s0ohuj3jnflo/V10D_downgrade.kdz
this is the pre-rooted rom that allows su access to unlock bootloader this also
changes the phones id from e617g to e610, startup wizard is in russian at first simply change to english.
http://csmgdl.lgmobile.com/swdata/c...981MAN38AP22_ML_WHQL_Ver_3.8.1(0)_4.9.8.1.zip
this contains the correct drivers for phone.
http://dl.xda-developers.com/attach...65/51fc133a/1/7/5/6/7/5/9/CWM6_24-03-2013.rar
this is recovery image for cwm
and youll have to google search everything i quoted thats missing sorry about this but you need: 1) LG FlashTool and Accessories.
2) some form of adb for an adb shell.
3)emmc_appsboot.bin specifically for e610
4)lg drivers for e610/e617g
5)recovery.img for clockwork for e610
6)lastly the V10D_downgrade.kdz
Click to expand...
Click to collapse

That happens when the kdz file is corrupted. Redownload the firmware and try again

its more than likely a bad connection causing a bad download also are you starting off with an e617g or e610?

Will all app data, contacts, etc. be lost using this method? Thanks in advance!
r4nd0m14m said:
this is my first tutorial so message me if something on here isnt clear.
step 1: download things, this is crucial, you need to download this stuff, it took me a while to find everything that ACTUALLY WORKED so i have it all in a nice little package to download.
step 2: make sure your phone is NOT plugged in the computer, install drivers if you do not have them. i have the drivers that worked for me in the package via direct download links. if they dont work for you somethings screwy with your computer and youll have to scour the internet to find drivers that'll work, google is your friend.
step 3: make sure your phone is recognised with your lappytop or computer. thats right i said lappytop, so sue me.
step 4nce all the drivers are installed and your phone is connected to the computer youll want to open up the folder labled: "LG FlashTool and Accessories" inside youll find "KDZ_FW_UPD.exe" open that right up.
step 5: next youll see a modded lg tool made by some guy on the internet, im not sure who but he/she did a good job thanks man/wo-man!!
ok youll want to leave all settings to default dont touch any thing, its good to go as is.
step 6: make sure phone is plugged in and usb debugging is enabled, use the kdz updater to browse for this file (download it via links in the package) "V10D_downgrade.kdz" then click on "Launch software update" this takes a while go make a coffee.
step 7: when its done its magic, your phone will boot up and youll see the LG logo for about 10 minutes any longer and your in a boot loop remove battery put it back in and hold both volume buttons down and power at the same time. time it carefully the lights on the soft keys will come on and a split second later the phone will slightly vibrate, the second you feel that press the home and hold it for about 10 seconds and the phone will do a hard reset, the phone will turn on now and initiate the first time use wizard, its in russian at first so just change your language to whatever, assuming english here. the phones software is now rooted just no su/superuser installed download from play store and update binary in settings of su app.
step 8: Unlocking bootloader time! after you flashed the software using kdz updater your phones ID is now technically an e610 now instead of an e617g, so unlocking the bootloader is now possible, connect your phone to computer, turn usb debugging on and drag and drop "emmc_appsboot.bin" into the root of your INTERNAL SD, also kill 2 birds with one stone here by also copying the recovery-clockwork-6.0.2.8-e610.img you downloaded via links in the txt document to the same place just rename it "recovery.img to make it easier also make sure you place the cm rom in the external sd. we need the bootloader unlocked to allow for cwm installation and good ol' rom swapping, open the folder "ADB" hold shift right click any where in the folder and select open "command window here",
type in the cmd window obviously without quotations: "adb shell" hit enter, then type "su" enter again then type "dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5" your bootloader is now unlocked, now type in "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17" this just installed clockwork mod. to boot into recovery and install cyanogen (the one im using. btw its a powerhouse compared to stock!!!) type in "reboot recovery"
step 9: factory reset, clear partition, wipe dalvik cache, install cyanogen, reboot, ENJOY.
seems i cant upload the programs needed so all i can do is this:
http://199.91.154.133/15ihz730pw2g/qwyqbfcp9fe7uhu/cm-10.1-20130725-UNOFFICIAL-e610.zip
this is the cyanogenmod rom.
http://199.91.154.102/r595o5bou5eg/bb2s0ohuj3jnflo/V10D_downgrade.kdz
this is the pre-rooted rom that allows su access to unlock bootloader this also
changes the phones id from e617g to e610, startup wizard is in russian at first simply change to english.
http://csmgdl.lgmobile.com/swdata/c...981MAN38AP22_ML_WHQL_Ver_3.8.1(0)_4.9.8.1.zip
this contains the correct drivers for phone.
http://dl.xda-developers.com/attach...65/51fc133a/1/7/5/6/7/5/9/CWM6_24-03-2013.rar
this is recovery image for cwm
and youll have to google search everything i quoted thats missing sorry about this but you need: 1) LG FlashTool and Accessories.
2) some form of adb for an adb shell.
3)emmc_appsboot.bin specifically for e610
4)lg drivers for e610/e617g
5)recovery.img for clockwork for e610
6)lastly the V10D_downgrade.kdz
Click to expand...
Click to collapse

yes definitely back up

r4nd0m14m said:
yes definitely back up
Click to expand...
Click to collapse
Does this method actually unlock the network too? Can I use fido sim card? would it work?

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?