Database Info

2.31.651.7 fix.... No computers... No flash backs... Just root, recover and flash!!!

After receiving my second Hero I had noticed something weird about its software version... From what I remembered, it started with 2.27 on the last one I had and raised my curiosity/concern. I had heard about a root patch that was being sent out OTA by Sprint and after a little digging found the extremes that everyone was going through to achieve a successful root. The most common was to flash back .6 then to .5 which doesn't have the patch. I spent over an hour trying to find ANY copy of the 2.31.651.6 update and could not find anything. Then there where methods using the SDK which I'm sure could work, however the bootloader was a b!tch to access. I thought it would be entertaining to see If Sprint's new .7 root patched could be broken simply by the android market and third party developers; no use of Odin, unrevoked, HTC sync, no messing with debugging, not custom 2.31.651.7 (careful) and absolutely no flash backs! So here it is... enjoy.
All you will need ready is:
1).zip file of whichever OS you plan to flash. (I prefer the cm build's).
2)Rom Manager from the market (work's well with clockwork and cm).
3)Heroroot101.apk (Don't remember if it's on the market or third party).
4)NANDROID!!!!!!
All you do is run heroroot010 and push the root me button.
Reboot your phone and let it fully boot back up (give it a minute or two).
Turn it off and boot into recovery by holding down volume button and power.
I'll be damned there is a recovery image now by darchstar.
At this time there is no need to wipe just choose and flash rootme.zip
When you reboot you will see that sprint know's you're rooted already and wants to update you... This is fine.
Open Rom Manager, flash Clockwork (replacing darchstar) reboot into recovery mode and flash your new OS (DON'T FORGET TO WIPE).

I like your detailed method, but SuperOneClick was really easy too.
Install HTC Sync (v2 for Hero)
Enable USB debugging
Open SOC
Click Root
Plug in phone when prompted
Wait a bit.... then done.

There really is alot of outdated information on these forums. All versions of the stock ROMs can be rooted one way or another.
Above is two possible solutions

I agree with porkrinds but y would you replace Darchstar Recovery its the best IMO Thanks Darchstar
Root-Hack-Mod-Always™

Porkrinds said:
There really is alot of outdated information on these forums. All versions of the stock ROMs can be rooted one way or another.
Above is two possible solutions
Click to expand...
Click to collapse
Forum update, prune, re-sticky time?

I used one click method & there's no recovery image.

Great Way to Root Hero with 2.31
Used this without a hitch, has recovery & all took about 2 minutes...
http://forum.xda-developers.com/forumdisplay.php?f=643

cybertimber2007 said:
I like your detailed method, but SuperOneClick was really easy too.
Install HTC Sync (v2 for Hero)
Enable USB debugging
Open SOC
Click Root
Plug in phone when prompted
Wait a bit.... then done.
Click to expand...
Click to collapse
Hey man I just used your little posts instructions to root my Wife's hero (my evo is already rooted)
I can't believe how easy that was thanks so much everything appears to be working I have superuser authority and am going to try flashing a new rom momentarily

Incredible-S-Inc Alpha Rom Issue running on Dinc

I downloaded and installed the Incredible S Beta rom that is listed somewhere on this site for the Incredible. My issue is I want to revert to another ROM, HOWEVER, now my Superuser keeps force closing and will not allow ROM Manger to flash. I try to reboot in HBoot and ONLY get the start-up screen when doing Vol- and Power. Any suggestions on how to get into Hboot or another way to flash a different ROM when SuperUser will NOT allow permissions or Rom Manger wont reboot into Recovery (because superuser forecloses and wont let me flash Rom Manager
BTW-The Incredible S Rom works great...just NO pic/video (As it states in the description.)
Editing to take away some of the clutter (my clutter)
I am not sure what happened. As stated above once the ROM (which is great!) was installed, Rom Manager was no longer granted superuser access (was trying to reboot into recovery via Rom Manager). It wiped the Recovery Version from the phone and would not let me flash a new recovery. Everything else seemed to work fine (superuser permissions, ie. SetPC, etc.)
I tried plugging the phone in and reflashing Unrevoked directly to the phone. Unrevoked stated the root access was denied and asked if I had a "newer firmware".
I also tried uninstalling superuser (to only reinstall and see if it fixed the issue), however, Superuser was included in the ROM and would not let me uninstall.
The only way I was able to get back into Recovery was to re-run Unrevoked Flash and UNPLUG the phone when Unrevoked managed (somehow) to get the phone into bootloader. From there Clockwork ran fine.
Installed a different ROM and all is good.
The only thing I can think of is: In some post regarding the Incredible S being not branded to a certain carrier. When the ROM was installed, it showed "EVDO" in the notification bar (which leads me to believe it is for Sprint), I am not sure how THAT would affect anything being on a Verizon phone...again..only thing I can think of.

Just reboot the phone directly into recovery.

evilkorn said:
Just reboot the phone directly into recovery.
Click to expand...
Click to collapse
It wont let me. I dont think...I tried the Vol-+power...nothing..just reboots. Tried booting into recovery via Rom Manager, but since superuser no longer is granting persmission it wont even do that...is there another way to flash a different ROM?
I just tried reflashing Unrevoked directly to it...it failed to access boot, something about the firmware being too new...???

I dont know anything about your device but maybe your root is broken? Re root and re install superuser goodluck.
Sent from my X10a using XDA App

shahkam said:
I dont know anything about your device but maybe your root is broken? Re root and re install superuser goodluck.
Sent from my X10a using XDA App
Click to expand...
Click to collapse
Oh, HTC Incredible.
I went into Rom Manager (and against ALL I have read) am trying to instal and reboot using Rom Manager...instead of going into recovery mode...phone is just sitting here "thinking" right now...nothing YET about being denied root access...fingers crossed...
OK, not sure this was SMART...Hooked phone back up to PC, ran Unrevoked flash kit again...unplugged phone once it came up in recovery...have access NOW to CLockwork...wiped data..installing different ROM as I type...hopefully this will work..
YAY...close call...sorry to waste everyones time..lol. So..If your installing the INcredible S Rom onto your incrediable..I have learned two things...1.) Unrevoked failed to push recovery due to the firmware...2.) you may lose superuser ability....

You would get more help if your thread title would actually be helpful.
Include your phone model, the rom you tried, and what happened (SuperUses FCs[forcecloses]).
Caps, lots of exclamation marks and a title like ZOMFG I NEED HELP, usually deters skilled people from threads like this.

Dark3n said:
You would get more help if your thread title would actually be helpful.
Include your phone model, the rom you tried, and what happened (SuperUses FCs[forcecloses]).
Caps, lots of exclamation marks and a title like ZOMFG I NEED HELP, usually deters skilled people from threads like this.
Click to expand...
Click to collapse
Good point...just paniked. Someone can close this or change title.

You can do it yourself through the edit button. Make it accurate so people who have the same problem and search for it will find your thread and your solution.

Please help me with ADB

I don't know why ADB is not working while normally booted! It works when in recovery, please help me. I am using Senseless version 3.7.1

cwest31 said:
I don't know why ADB is not working while normally booted! It works when in recovery, please help me. I am using Senseless version 3.7.1
Click to expand...
Click to collapse
Read this entire guide.

blackknightavalon said:
Read this entire guide.
Click to expand...
Click to collapse
koooooooooooool

reinstalled sdk following instructions carefully! its not an sdk problem

cwest31 said:
reinstalled sdk following instructions carefully! its not an sdk problem
Click to expand...
Click to collapse
ADB is part of the SDK.
Sent from a message in a bottle.

cwest31 said:
I don't know why ADB is not working while normally booted! It works when in recovery, please help me. I am using Senseless version 3.7.1
Click to expand...
Click to collapse
There is literally no information in this posting that someone can use to help you.
Blackknightavalon's direction to the SDK webpage is about as helpful of a reply as you can expect to solicit with the information you have provided.
This is like going to a car forum, and saying " I have a blue camaro. It won't start. I tried turning the key. Help please"
What commands are you trying to run through adb?
What errors are you getting, if any?
What do you see when you type "adb devices"
What operating system are you running on the computer you are trying to connect from?
Have you turned on "usb debugging" in the options menu on the phone?
There are a whole lot of things that can be your problem, and we'd love to help, but we can't help you if you don't tell us what's wrong.
Doubtless someone else will get back to you before I get a chance to, since my time is very limited these days online, but posting some more information about your problem will elicit a response that may actually help you.
Best of luck!

Blue6IX said:
There is literally no information in this posting that someone can use to help you.
Blackknightavalon's direction to the SDK webpage is about as helpful of a reply as you can expect to solicit with the information you have provided.
This is like going to a car forum, and saying " I have a blue camaro. It won't start. I tried turning the key. Help please"
What commands are you trying to run through adb?
What errors are you getting, if any?
What do you see when you type "adb devices"
What operating system are you running on the computer you are trying to connect from?
Have you turned on "usb debugging" in the options menu on the phone?
There are a whole lot of things that can be your problem, and we'd love to help, but we can't help you if you don't tell us what's wrong.
Doubtless someone else will get back to you before I get a chance to, since my time is very limited these days online, but posting some more information about your problem will elicit a response that may actually help you.
Best of luck!
Click to expand...
Click to collapse
Make sure you have current adb drivers for your phone. It will show android composite in device manager. Fastboot will show fastboot device. Seeing a yellow question mark is bad.
Make sure your pathing is set up right.
Typing "adb devices" and if you see your device. If so you're ready to roll.
I usually get fastboot errors like this when I don't have drivers installed right.
sent from my Agent Orange MT4G Slide using xda premium

Droidmoder said:
Make sure you have current adb drivers for your phone. It will show android composite in device manager. Fastboot will show fastboot device. Seeing a yellow question mark is bad.
Make sure your pathing is set up right.
Typing "adb devices" and if you see your device. If so you're ready to roll.
I usually get fastboot errors like this when I don't have drivers installed right.
Adb is part of the adk. It's to help debug and install things via a directlink to the computer. Its found in platform tools and is considered a dev tool.
sent from my Agent Orange MT4G Slide using xda premium
Click to expand...
Click to collapse
sent from my Agent Orange MT4G Slide using xda premium

I get Error Message with ADB
Hey guys, so I perm rooted with S-OFF my mytouch 4g slide, with theunlockr.com youtube video and guide using revolutionary. then I attempted to install a ROM with ROM MANAGER, and it got stuck on the splash/loading screen. After some searching I found out that this meant that I could have potentially BRICKED the phone, so I followed theunlockr.com's guide to UNROOTING the phone, and it worked, I flashed the original stock tmobile rom, and it loaded fine, I tried to start the whole process again, but now I get stuck in the very beginning, trying to get TEMP root, I start the fr3vo exploit like the guide stated, but then i keep getting error messages on the command line prompt saying that there is an error with ADB, then when I power the phone with volume down and power, the revolutionary is no longer on the top of the screen, but it still says SHIP S-OFF. Does that have to do anything with my problem? is there a way to GET S back to ON, so I can start the process over? or am I better off having S off??? I installed ROM MANAGER and tried to flash a recover image thinking that having S off would allow me to do this, but I get error messages saying there are problems with the permissions. the web site for the guide I used to root is this one incase anyone wants more details into what I did, any help would be greatly appreciated. theunlockr.com/2011/09/09/how-to-permanently-root-and-gain-s-off-on-the-t-mobile-mytouch-4g-slide-revolutionary-method

Use perm root method. Myself I flashed oneclick in recovery, but you can follow the guide the perm root part.
Btw rom manager supports flashing of the new cwm only. I checked the roms in rom manager they aren't supported. You have to go to the cm7 thread here and download and flash cm7 from recovery.
Just redo root process and install cwm from rom manager. Then go to the dev section and flash your favorite rom in recovery. My sig has directions on how to do everything.
Also if you're having permissions error use root explorer on the rom manager apk make sure it has execute checked. Also I think rom manager has a fix permissions button. Its never worked for me.
S off will allow flashing of cwm. However you need to be rooted to flash cwm threw rom manager. My sig has a guide on installing cwm without being rooted.
sent from my Agent Orange MT4G Slide using xda premium

Thanks for the QUICK reply, but I looked at the guide, and it stated I have to have recovery installed, BEFORE I do the perm root method, but I dont have recovery, when I do HBOOT, and I try to boot into recovery, I get a red exclamation mark on the screen and I have to end up taking out the battery. Thats why I was wondering if having S OFF from the beginning now is what is messing me up when I am trying to ROOT again, I mean, I am doing the same steps.... just now I get errors when I try to do the TEMP root step... so I cant continue... and I cant get ROM MANAGER to flash a recovery image... is there a guide or steps someplace that can guide me to root the MT4G slide already having S off?

I found the problem myself, I had to enable USB Debugging.

I had USB debugging enabled.... hmmmm you made me doubt myself... I guess I will try it again, since I flashed stock rom again all settings were reverted... so I cannot VERIFY I had USB debugging on, but I was sure I did... I will try again and post... I am reflashing the stock rom like 5 times a days trying to root again =(
wait... cwest31, you had which same problem? because I was writing about 2 problems: about booting into recovery with S off, but no recovery image (hence I got red exclamation mark), and trying to get ROM MANAGER to flash a recovery image on my phone since I have S off already, but I get error messages (problem with permissions)

RT2023 said:
I had USB debugging enabled.... hmmmm you made me doubt myself... I guess I will try it again, since I flashed stock rom again all settings were reverted... so I cannot VERIFY I had USB debugging on, but I was sure I did... I will try again and post... I am reflashing the stock rom like 5 times a days trying to root again =(
wait... cwest31, you had which same problem? because I was writing about 2 problems: about booting into recovery with S off, but no recovery image (hence I got red exclamation mark), and trying to get ROM MANAGER to flash a recovery image on my phone since I have S off already, but I get error messages (problem with permissions)
Click to expand...
Click to collapse
Umm...did you read the full instructions very carefully? When you get to the part where you flash the Superuser .zip file, you need to try it several times before it'll hold.

blackknightavalon said:
Umm...did you read the full instructions very carefully? When you get to the part where you flash the Superuser .zip file, you need to try it several times before it'll hold.
Click to expand...
Click to collapse
What he said.
Also ROM MANAGER WILL NOT WORK UNLESS ROOTED. Get rooted then try flashing the image. The compendium also has step by step guides using terminal emulator once rooted
sent from my Agent Orange MT4G Slide using xda premium

Also I want you op and the other one to be clear on what s off is and root.
Getting S OFF allows unsigned zips to be flashed. This means you can now flash roms and root. Without s off you cannot root, rom, kernels. S OFF is not root.
Root is gaining admin rights over your phone. this allows programs that require access to the root files to have access to them. ROM Manager, titanium backup, drocap, setcpu will be granted access to the root files and programs which unrooted phones would not be granted access .
This can be a reason why you two are having trouble using rom manager unrooted. Rom manager cannot access the files it needs
sent from my Agent Orange MT4G Slide using xda premium

Please go follow this thread ---> http://forum.xda-developers.com/showthread.php?t=1178606. It tells you how to Permanently root a device that is already s-off.

AWESOME!!! turns out i just had to run revolutionary TWICE, and the second time it figured out it was already rooted and then asked if I wanted to install recovery, I dont know how to do it manually so I clicked yes, and THEN i was able to go into recovery and flash the PERM root ZIP, rebooted and i had SUPERUSER in my app drawer!!!! awesome, now to try to get the version of google talk installed that actually allows for video chat!!! I HATE QIK!!!!!!
DROIDMODER, CWEST31: Thanks so much for the lenghty explanation and help. I have loved android for the ability to customize, and I had the G1, MOTOCLIQ, G2, and now MT4GS, I rooted my G2, but didnt do anything to it because i was scared to F it up, but with the MT4GS I got the balls to do it just because I was SOOOO UPSET that the phone comes with a version of GTALK that does NOT ALLOW FOR VIDEO CHAT!!?!?! WTF!!! whats the front camera for then?! and QIK sucks, not all my friends are on tmobile... i was even more upset when the HTC AMAZE has a version of GTALK that does allow for video chat straight out of the box!!! this is my main push to wanting to root... thanks for letting me vent! lol and thanks for all your great info

RT2023 said:
AWESOME!!! turns out i just had to run revolutionary TWICE, and the second time it figured out it was already rooted and then asked if I wanted to install recovery, I dont know how to do it manually so I clicked yes, and THEN i was able to go into recovery and flash the PERM root ZIP, rebooted and i had SUPERUSER in my app drawer!!!! awesome, now to try to get the version of google talk installed that actually allows for video chat!!! I HATE QIK!!!!!!
Click to expand...
Click to collapse
Your welcome! now procead to install undead's senseless ROM (Best Rom available) and also get rom manager and flash the official CWM recovery! Also proceed to "thank."

mmmm... I tried to install a ROM before and thats what F-ed everything up =/ I am hesitant, I really want a Gtalk version that allows for video chat, does the senseless rom have video gchat capabilities??

[Q] Rooting at&t HOX with 4.2.0.001 drivers

Hey guys I have been searching all over the place for this answer and I just cant seem to find anything on the topic.
This is my first time tinkering with my HTC One X (old version 4.0.3) and downloaded the most updated drivers which is where I believe I went wrong.
I have the 4.2.0.001 drivers and when I open the root.zip file nothing happens I get no errors I just get the "your HTC One X is rooted..." yet my phone simply doesn't reboot.
So I attempted to install the downgraded drivers the 3.0.0.007 which looking back has been the recommended drivers, however; when I extract those files and head into my device manager it does not pull up the androidusb.inf file to upload the 3.0.0.007 drivers.
Am I missing a proper BMP USB Driver and where can I find it? Or is there a root file that will work with the 4.2.0.001 drivers?
If there is any link to this topic please post it, I am very new to rooting or if I have made any mistakes please let me know.

social_spider said:
Hey guys I have been searching all over the place for this answer and I just cant seem to find anything on the topic.
This is my first time tinkering with my HTC One X (old version 4.0.3) and downloaded the most updated drivers which is where I believe I went wrong.
I have the 4.2.0.001 drivers and when I open the root.zip file nothing happens I get no errors I just get the "your HTC One X is rooted..." yet my phone simply doesn't reboot.
So I attempted to install the downgraded drivers the 3.0.0.007 which looking back has been the recommended drivers, however; when I extract those files and head into my device manager it does not pull up the androidusb.inf file to upload the 3.0.0.007 drivers.
Am I missing a proper BMP USB Driver and where can I find it? Or is there a root file that will work with the 4.2.0.001 drivers?
If there is any link to this topic please post it, I am very new to rooting or if I have made any mistakes please let me know.
Click to expand...
Click to collapse
Drivers are drivers. You can root with either. Old new, doesn't matter. It just allows your phone to be recognized by fastboot and ADB, that's all.

exad said:
Drivers are drivers. You can root with either. Old new, doesn't matter. It just allows your phone to be recognized by fastboot and ADB, that's all.
Click to expand...
Click to collapse
Thank you :good: so this means its something wrong with the root.zip file or the process Im doing to root? I just attempted it a few seconds ago this time the phone rebooted 2 times but I am not seeing any Su app on my phone

social_spider said:
Thank you :good: so this means its something wrong with the root.zip file or the process Im doing to root? I just attempted it a few seconds ago this time the phone rebooted 2 times but I am not seeing any Su app on my phone
Click to expand...
Click to collapse
The root methods simply give you temp root and super cid so you can unlock the bootloader. *facepalm*
Then when your bootloader is unlocked you can flash recovery and then flash su through recovery or install a custom rom which will already be rooted.

exad said:
The root methods simply give you temp root and super cid so you can unlock the bootloader. *facepalm*
Then when your bootloader is unlocked you can flash recovery and then flash su through recovery or install a custom rom which will already be rooted.
Click to expand...
Click to collapse
damn im an idiot haha thank you for clearing this up

I guess I am not understanding the core concept here, so I now I theoretically have a temp root with Super CID. I was under the impression that I was supposed to download Titanium Backup before attempting to unlock the bootloader. So I went to download and it told me I did not have root access so I could not run Titanium. I am afraid to attempt a bootloader unlock with out my rom being backed up. Can you please shed some light on this or post a link that would explain the process after temp root in detail thank you

social_spider said:
I guess I am not understanding the core concept here, so I now I theoretically have a temp root with Super CID. I was under the impression that I was supposed to download Titanium Backup before attempting to unlock the bootloader. So I went to download and it told me I did not have root access so I could not run Titanium. I am afraid to attempt a bootloader unlock with out my rom being backed up. Can you please shed some light on this or post a link that would explain the process after temp root in detail thank you
Click to expand...
Click to collapse
You can backup after your bootloader is unlocked.. bootloader unlock is just a flag that allows you to flash certain partitions like recovery.
Backing up before or after will make no difference. If you end up really messing up your device, a backup won't save you anyway so I don't see why you'd be worried. If you S-OFF, you can RUU to get back to stock any time no problem, unless you full on brick. Then only jtagg will save you.
Typically before I root a phone, I read all the stickies in all the subsections to understand how things work since every phone has differences, some subtle some not so subtle.

exad said:
You can backup after your bootloader is unlocked.. bootloader unlock is just a flag that allows you to flash certain partitions like recovery.
Backing up before or after will make no difference. If you end up really messing up your device, a backup won't save you anyway so I don't see why you'd be worried. If you S-OFF, you can RUU to get back to stock any time no problem, unless you full on brick. Then only jtagg will save you.
Typically before I root a phone, I read all the stickies in all the subsections to understand how things work since every phone has differences, some subtle some not so subtle.
Click to expand...
Click to collapse
Thank you very much before I unlock Im gonna hit the stickies and make sure I completely understand everything :good:

Bootloop from root app permissions

Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?

val3nteen said:
Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?
Click to expand...
Click to collapse
Start here, http://forum.xda-developers.com/showthread.php?p=53439068. I'd return to stock and start all over, it will wipe your device, see the return to stock thread linked there. Then don't be lazy and read some more in the thread I linked you to. The n5 is one of the easiest devices to work with and you don't need kingroot, tool kits and junk like that
Sent from my Nexus 5 using XDA Free mobile app

You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image

deelan_chan said:
You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image
Click to expand...
Click to collapse
Thanks, but that is not possible, as I have not enabled USB debugging before bootloop. I need to unlock the bootloader (wipe) to install TWRP and backup data.

Can you get into fastboot mode? You can flash twrp from there no USB debugging needed
Sent from my Nexus 5 using Tapatalk

Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.

wangdaning said:
Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.
Click to expand...
Click to collapse
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.

val3nteen said:
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.
Click to expand...
Click to collapse
But it is so fun to use fastboot. I remember almost dunking my wife's G2 until I got it to fastboot. Pain in the butt, but the command prompt does not lie