Database Develop

HTC one M7 stuck on Fastboot / Bootloader screen

Hi All,
I have an HTC one M7 unlocked. Two days ago I tried to restart my phone and it is stuck on the Fast boot /bootloader screen. I tried to use the recovery and Reset Factory options, but these are bringing me back to Fastboot screen. Took my phone to a gadget shop and they said OS has gone. Any idea how to proceed? I am a newbie to this forum and any help would be much appreciated
***LOCKED***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.000
OS-6.13.707.107
eMMC-BOOT 2048M
Jan 7 2015,14:50:53.0
FASTBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER>to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN

Unlock the bootloader first then install custom recovery

what's up everyone... got a little question and apologise if it's been asked many times before. my wife loves htc (sense UI) so recently i bought a brand new one for her (M7)... the reason im telling this is the fact that I have already drivers and adb installed on my pc (unlocked, rooted and flashed a rom for her on the second day after buying it) but few days ago I bought another M7 at a good price just to use with mhl-vga converter (as a stationary with Bluetooth keyboard and mouse connected so we wouldn't have to connect her m7 or my s5 all the time back and forth) but the thing is, that volume rocker (the one you actually need to enter a fastboot mode, the Volume Down) - dont work, so my question is, - is it possible to enter a fastboot mode through pc using cmd ? I've read that it is possible but yesterday I connected, opened command window, typed ADB devices just to see if pc recognizes the device and nothing, then typed other commands I found googling... commands for reboot, reboot to fastboot... whatever... so I'm asking is it possible? or the only way to get there is to use power and volume down buttons? thanx.
edit : drivers are all good (updated), adb us on my pc. the device was On (booted).

methoddon1 said:
what's up everyone... got a little question and apologise if it's been asked many times before. my wife loves htc (sense UI) so recently i bought a brand new one for her (M7)... the reason im telling this is the fact that I have already drivers and adb installed on my pc (unlocked, rooted and flashed a rom for her on the second day after buying it) but few days ago I bought another M7 at a good price just to use with mhl-vga converter (as a stationary with Bluetooth keyboard and mouse connected so we wouldn't have to connect her m7 or my s5 all the time back and forth) but the thing is, that volume rocker (the one you actually need to enter a fastboot mode, the Volume Down) - dont work, so my question is, - is it possible to enter a fastboot mode through pc using cmd ? I've read that it is possible but yesterday I connected, opened command window, typed ADB devices just to see if pc recognizes the device and nothing, then typed other commands I found googling... commands for reboot, reboot to fastboot... whatever... so I'm asking is it possible? or the only way to get there is to use power and volume down buttons? thanx.
edit : drivers are all good (updated), adb us on my pc. the device was On (booted).
Click to expand...
Click to collapse
You can reboot to the bootloader / fastboot usb mode by using the command "adb reboot bootloader". To use this command, you must have the latest HTC drivers installed on your computer and "USB debugging" option turned on in the developer option menu. If you can't access the developer menu from the settings menu (not in the list), you must active it by going to "settings --> about --> Software info --> more" then start tapping on the "build number" until you see a notification "You are now a developer" telling you that the developer option menu is enabled. Then go back to the settings menu --> Developer option -> USB debug --> ON.
Another important thing when using adb from a booted rom is to make sure that you have unlocked the screen using your PIN (or any other security method). ADB won't work if the screen is locked for obvious security reasons.
Once in the bootloader, if you can't use the volume down key to navigate the options, there is not much you can do except using fastboot commands. If you want to boot in recovery mode for example, since the volume key is broken, you'll need to reboot in the OS and use the "adb reboot recovery" command so you can access the recovery mode. If you want to exit the bootloader, use "fastboot reboot".

I I
alray said:
You can reboot to the bootloader / fastboot usb mode by using the command "adb reboot bootloader". To use this command, you must have the latest HTC drivers installed on your computer and "USB debugging" option turned on in the developer option menu. If you can't access the developer menu from the settings menu (not in the list), you must active it by going to "settings --> about --> Software info --> more" then start tapping on the "build number" until you see a notification "You are now a developer" telling you that the developer option menu is enabled. Then go back to the settings menu --> Developer option -> USB debug --> ON.
Another important thing when using adb from a booted rom is to make sure that you have unlocked the screen using your PIN (or any other security method). ADB won't work if the screen is locked for obvious security reasons.
p. s. with my wife's phone I was done in 15 minutes (including unlocking, rooting, flashing a rom and a boot up). so I'm confused a bit. but since wife's June us new and obviously the volume rocker is functioning, I had no problem getting to bootloader and take it from there.
Once in the bootloader, if you can't use the volume down key to navigate the options, there is not much you can do except using fastboot commands. If you want to boot in recovery mode for example, since the volume key is broken, you'll need to reboot in the OS and use the "adb reboot recovery" command so you can access the recovery mode. If you want to exit the bootloader, use "fastboot reboot".
Click to expand...
Click to collapse
thanx for such detailed info. I'm not" working " a lot with htc, I'm myself a Galaxy Series kinda guy but im familiar with the basics of htc. I'll try again tomorrow. but commands don't do what they were meant to do. after updating the drivers with htc sync and having USB debugging On, and adb installed (everything I used to unlock, root etc my wife's device, this device gives me problems). got to see in manager (on pc) if it's even sees the device. but the command Adb devices didn't show anything connected.

methoddon1 said:
I I
thanx for such detailed info. I'm not" working " a lot with htc, I'm myself a Galaxy Series kinda guy but im familiar with the basics of htc. I'll try again tomorrow. but commands don't do what they were meant to do. after updating the drivers with htc sync and having USB debugging On, and adb installed (everything I used to unlock, root etc my wife's device, this device gives me problems). got to see in manager (on pc) if it's even sees the device. but the command Adb devices didn't show anything connected.
Click to expand...
Click to collapse
Yep and post a screenshot of your devices manager when you'll have time.

alray said:
Yep and post a screenshot of your devices manager when you'll have time.
Click to expand...
Click to collapse
what do you mean? I meant go into pc, open a manager and see if the pc sees it.

methoddon1 said:
what do you mean? I meant go into pc, open a manager and see if the pc sees it.
Click to expand...
Click to collapse
Exactly and if the phone isn't detected or is incorrectly detected (yellow triangle with an exclamation mark) take a screenshot of your windows devices manager and post it here.

I will.

alray said:
Exactly and if the phone isn't detected or is incorrectly detected (yellow triangle with an exclamation mark) take a screenshot of your windows devices manager and post it here.
Click to expand...
Click to collapse
here is the thing, - I was gonna switch my interface to English so it'd be easier for you but don't have it installed and since we just had a major storm, my Internet is down for a minute so here is the thing... in the manager it showd all is good as you see, when you double tap on My HTC, in the little window in General it shows Connected but in time in the same General it'll show "At this moment the device isn't connected (code45). To solve this problem reconnect the device."
p. s. in Drivers tab (just for the hell of it I pressed Update but the drivers are up to date. so does HTC Sync... connected, synced.

oh sh**, I'm finally in after trying and trying... adb devices - Recognised, adb reboot bootloader - rebooted... never mind right now, I'll take it from here. out of time right now but I'll get back to it when my Internet connection fixed. thanx again, but I might be back with another question.
---------- Post added at 09:46 AM ---------- Previous post was at 09:27 AM ----------
maybe it's a coincidence but I deleted folders that I used to work with my wife's htc (in mini-sdk folder was unlock code that I got unlocking her device) and unzipped (still had the zip) again. now I have no problems using adb commands.?

alray said:
Exactly and if the phone isn't detected or is incorrectly detected (yellow triangle with an exclamation mark) take a screenshot of your windows devices manager and post it here.
Click to expand...
Click to collapse
well, I fckd it up... after successfully going through process of unlocking, flashing twrp, restoring apps from Titanium Backup, last thing I had to do was install xposed installer... i installed exactly the same that I did before 4beta but instead of flashing 68 arm 21 zip to install framework I flashed 74 arm 21 zip, wiped dalvik but no boot up. that's it! htc one logo... connected the device to pc, now it sees it but it says it's off line (in cmd). another thing, - as soon as I connect it the Manager shows everything is fine, then I open cmd, go to cd C:\ (everything is still ok in the Manager) but as soon as I type mini-sdk (the adb folder), the Android USB at the top of the Manager stays the same but Removable Devices gers a triangle. any clue??? Jesus, I was there, everything was fine, I've got a backup of stock rom after flashing twrp but now a brick.

here it is

I was using mini-sdk but just now installed 15 seconds ADB program and tried with it... same sh**. it sees it but the status is offline... tested on my Galaxy s5, works just fine. wtf? did I hardbricked my htc?! can it actually see the # but be Offline. still on htc logo.
p. s. on connecting the s5, in the line where htc (pic above) has yellow triangle, it's not there on s5.is there a solution? double pressing on HTC with yellow triangle and in the window popping up in General tab it says, - Impossible to start (code 10).
and another thing... i honestly don't remember if I enabled Debugging when I flashed ARHD Rom... is it On by default in custom roms in htc?
---------- Post added at 03:56 PM ---------- Previous post was at 03:21 PM ----------
alray said:
Exactly and if the phone isn't detected or is incorrectly detected (yellow triangle with an exclamation mark) take a screenshot of your windows devices manager and post it here.
Click to expand...
Click to collapse
look at this... the craziest sh**. look at the commands... on adb reboot - device not found, on adb devices - it shows up but as offline and at that exact moment HTC line on Manager changes to a yellow triangle but not before.

pic

methoddon1 said:
pic
Click to expand...
Click to collapse
You can't use adb if the phone isn't fully booted to the OS or booted in a custom recovery. What version of android or what firmware version is installed on the phone? The Xposed version you need to install depends the android version that is installed on the phone. Bootloop caused by xposed is something easy to fix normally, but you need to get in recovery mode which is a problem without a working volume down key

alray said:
You can't use adb if the phone isn't fully booted to the OS or booted in a custom recovery. What version of android or what firmware version is installed on the phone? The Xposed version you need to install depends the android version that is installed on the phone. Bootloop caused by xposed is something easy to fix normally, but you need to get in recovery mode which is a problem without a working volume down key
Click to expand...
Click to collapse
I know.... (about the volume)... it was on official 5.0... when I was done with it, it was with a latest twrp and ARHD 92.0 Rom installed. everything was fine... i didn't spend much time on it (had to set it all up), so restored everything with Titanium but instead of waiting for my wife to come back from work (I'm sure I didn't even delete the RIGHT xposed zip. it's still on her phone), I've decided to go and f*** it all up by just flashing the wrong one ....
---------- Post added at 04:24 PM ---------- Previous post was at 04:13 PM ----------
so you're saying it's either fixing a volume rocker or throwing it out?! but the thing is, because I was planning on changing the casing anyway, i took off the back cover to have access to the volume down button and I can feel a weak click but it's there (the click) and couldn't enter a fastboot anyway. f*******ck.

methoddon1 said:
I know.... (about the volume)... it was on official 5.0... when I was done with it, it was with a latest twrp and ARHD 92.0 Rom installed. everything was fine... i didn't spend much time on it (had to set it all up), so restored everything with Titanium but instead of waiting for my wife to come back from work (I'm sure I didn't even delete the RIGHT xposed zip. it's still on her phone), I've decided to go and f*** it all up by just flashing the wrong one ....
Click to expand...
Click to collapse
xposed-v74-sdk21-arm.zip should have worked fine on ARHD 92 (android 5.0.2) but flashing xposed can sometimes cause boot problems, even simply enabling a module can cause boot problems. That was a little risky to do it on a that phone since you need adb to reboot in recovery/bootloader because of the broken volume button.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
methoddon1 said:
so you're saying it's either fixing a volume rocker or throwing it out?! but the thing is, because I was planning on changing the casing anyway, i took off the back cover to have access to the volume down button and I can feel a weak click but it's there (the click) and couldn't enter a fastboot anyway. f*******ck.
Click to expand...
Click to collapse
Unfortunately yes.
Like I said this problem should be easy to fix, but without access to the bootloader or the recovery, there is not much you can do

ok thanx.
I wish youd reminded of that earlier... I've been using Samsung for too long...

deleted

Can someone PLEASE help me boot my phone into FASTBOOT mode? ( T mobile h811) on CM13

When I first purchased this phone I was able to boot to the default recovery that came with the phone ( which clearly had a *fastboot option*), it came with stock 5.1, and a bunch of bloatware.
I downloaded the one click root method for the h811 which was perhaps the easiest root i've ever done. great. i also had to flash my recovery to twrp 2.8 for some reason.
Rocked out to a newely rooted device on 5.1 until the t mobile bloatware and system update notification kept bugging me, so I said * eff it, i've been holding out for a while*
So I get to the cm 13 wiki for my device, I managed to install the cm recovery ( cant remember how i did this for some reason) and then i was able to flash cm13 to my phone. CM13 is sleek, and smooth but is presenting problems.
First of all, no google play store and the gapps zip wont install through cm recovery ( fails and tells me to use twrp instead which is a problem because i can't boot this phone into fastboot mode)
I am unrooted and can not figure out how to properly root a T mobile h811 running cm13, so the twrp manager doesn't work because it "requires root" then shuts down. ( enable root access in the cm13 developer options does nothing at all and yes, for adb and apps)
FAST BOOT MODE DOES NOT SEEM TO EXIST ANYMORE ON MY PHONE - Following the many tutorials, which goes long the lines of using adb/fastboot, adb devices can see my device, but fastboot devices can't ( figures) because its not in fastboot mode. Any fast boot reboot bootloader or any variant of that command only reboots the phone, to... swipe the screen.
I've installed the lg bridge crap ( which installed an updated usb driver) that doesn't even recognize my phone " no mobile device connected". tried uninstalling and reinstalling, but nothing. When putting the phone in download mode, to see if adb would rcognize it, windows sees this as a new device , installs drivers but says " device can not start, code 10 * in device manager. :silly:
is there anything that can be done?? google searches result in obvious solutions that SHOULD work but don't, or threads where a person coincidentally has the same exact problem as I do, but their response is usually the last response in the thread that goes unanswered
summary : I've install cm13 on my lg g4 h811, I do not have root access, I can not install twrp due to ( no fastboot mode) in effect, i cant install gapps, cant root phone etc..
any help?

did you ever unlock the phone....?

Yes, unlocking the phone is one of the first things you would need to do. In Developer Options > OEM Unlock. Then in bootloader, run the unlock command. This will delete /data and internal storage so back up your files so you can transfer them back via adb or fastboot.
Then you're probably going to need to temp boot TWRP, then flash the TWRP recovery image in TWRP. THEN you can flash properly.
Carefully read through this thread:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Good luck.
Edit: oh and this thread belongs in Q&A.

Alright. Am I only to read the first post or all 30+ pages? ( not that i have a problem, just curious)

Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.

aoaleman said:
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
Click to expand...
Click to collapse
"ARE YOU HAVING TROUBLE WITH LGUP NOT SEEING YOUR MOBILE?
Try this....... take the back off your mobile so you can get at the battery. Connect your mobile via USB. Start LGUP, if it does not see your phone DO NOT DISCONECT, DO NOT RESTART OR TURN OFF LGUP. Take out the battery and then put it back in.......let the phone restart on its own. LGUP should now see it."
didn't work, very frustrating. any clues? on windows 8.1 by the way. tried two computers. none can see this phone. I can connect the phone to the computer and see its storage, lg usb driver is installed

You probably need to reinstall the drivers. It might be the fastboot driver. That's what worked for me.

I've reinstalled the official drivers, uninstalled them... Jusst the mobile USB driver, a combo of both, plenty of times. Don't understand why this software doesn't see my phone
Lgup, lgair, lg bridge, lg USB driver (skinned down) .. Nothing works tested on my gaming rig., and work laptop both running win 8.1 64 bit

Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know

TacoTuco said:
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
Click to expand...
Click to collapse
This section does get more views though haha.
Anyway I feel that the 811 is one of the more finicky devices to get into fastboot at least in my experience. I had to enable and disable dev options while plugging and unplugging device and it finally worked. No idea if that'll work for everyone though.

I reasked the question in Q and A. Please help some one.

You start over. LG bridge.

Having the same issue. I'm on Windows 10. What developer settings did you mess with to get it working, tiskewlio?

The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?

Sunaj1 said:
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Click to expand...
Click to collapse
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing

thevirgonian said:
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
Click to expand...
Click to collapse
silly question maybe, but is there a specific tutorial in getting this to work with the files provided given my situation? (commands, etc..) will this somehow bypass the the lge mobile mtp device that wont install ? I had installed the system wide adb/fastboot drivers, and already had a folder with just the minimal install of the adb but didnt have a few files in the one you provided ( lg root, busy box, etc) so not quite sure what to do with them.
Again, if possible want to flash twrp recovery to my device but can't due to * waiting for any device* and the ( device cannot start ) error
Thanks

* waiting for device* when putting phone in download mode and pushing fastboot flash twrp-2.8.7.1-h811.img.
Any help would be appreciated as I need to get the driver to work first. see attached picture.
Cha h

the issue is largly resolved as i've been able to flash the recovery and install another rom. But i'd still like to know how to get the download mode driver properly working in the event i need a computer and can't do a self contained install.

Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.

travisd4est said:
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
Click to expand...
Click to collapse
i dont know man, i did all that a million times over, but recently i was able to just flash the stock MM rom to the device using LGup. Think i'll just stick with stock rom and root for a while as all this stuff is a little finicky at times. Thanks for your help.

Stuck on LG screen when boot.

I tried to reboot and it is stopped at the LG screen as shown in the attach photo. I dont know what to do now, as I think it cant even connect and to the dock (still charging but not recognised at all by the PC). It would be great and very appreciated if anyone knows what I need to do? Otherwise it is an expensive paperweight now.
Thanks in advance.
P/S: This is my 1st post in XDA, so if anything wrong with my post please let me know, I will change. Thanks again.
Update
I managed to make it work again. this is what you have to do is boot it to bootloader mode, then go to recovery mode and use the "apply update from adb" function (sideload in other words) to install the Android 6.0.1 again.
Link to download Android 6.0.1.
To put the watch in bootloader mode, follow the instruction in my youtube video here.
As soon as it is in bootloader mode, your computer should see the watch as an android device now.
In Bootloader mode, go to recovery mode (use the virtual buttons on screen), then go to the "apply update from adb" option.
Now, at this step, you need to open command line on your computer and type "adb sideload <android file>", where the <android file> is the one you download earlier. You can just type "adb sildeload" then leave a space and drag the file to the running Cmd window.
Now just wait for it to complete and restart itself.
Hope this helps.

This may not help, but try pressing the side button in for 20-30 seconds. Shortly after it stops vibrating, it will start rebooting again and then you can stop pressing the button.

JimSmith94 said:
This may not help, but try pressing the side button in for 20-30 seconds. Shortly after it stops vibrating, it will start rebooting again and then you can stop pressing the button.
Click to expand...
Click to collapse
Hi, I think I messed up with the wrong kernel is the reason of this issue, and I have been able to get to the fastboot menu, do you know how revert it back to the factory/out of box condition? Thanks.

I haven't tried this, but it may work for you: http://forum.xda-developers.com/wat...recovery-stock-recovery-image-v1-1-1-t3124452

JimSmith94 said:
I haven't tried this, but it may work for you: http://forum.xda-developers.com/wat...recovery-stock-recovery-image-v1-1-1-t3124452
Click to expand...
Click to collapse
Thanks for ur help. I have manage to make it works again.

johnnyle7 said:
Thanks for ur help. I have manage to make it works again.
Click to expand...
Click to collapse
Please let us know how you did it, in case or when I or others need to do the same.

JimSmith94 said:
Please let us know how you did it, in case or when I or others need to do the same.
Click to expand...
Click to collapse
should I update my post with the solution?

johnnyle7 said:
should I update my post with the solution?
Click to expand...
Click to collapse
Either that or post a new reply. I know we would appreciate it.

johnnyle7 said:
I tried to reboot and it is stopped at the LG screen as shown in the attach photo. I dont know what to do now, as I think it cant even connect and to the dock (still charging but not recognised at all by the PC). It would be great and very appreciated if anyone knows what I need to do? Otherwise it is an expensive paperweight now.
Thanks in advance.
P/S: This is my 1st post in XDA, so if anything wrong with my post please let me know, I will change. Thanks again.
Update
I managed to make it work again. this is what you have to do is boot it to bootloader mode, then go to recovery mode and use the "apply update from adb" function (sideload in other words) to install the Android 6.0.1 again.
to download Android 6.0.1.
To put the watch in bootloader mode, follow the instruction in my youtube video here.
As soon as it is in bootloader mode, your computer should see the watch as an android device now.
In Bootloader mode, go to recovery mode (use the virtual buttons on screen), then go to the "apply update from adb" option.
Now, at this step, you need to open command line on your computer and type "adb sideload <android file>", where the <android file> is the one you download earlier. You can just type "adb sildeload" then leave a space and drag the file to the running Cmd window.
Now just wait for it to complete and restart itself.
Hope this helps.
Click to expand...
Click to collapse
Hi There,
I have the same problem after the update.
I followed your steps but to enter into recovery mode I had to enable USB debugging mode which cannot be done as the watch keeps on rebooting.
Please let me know is there any other way to enable usb debugging mode to enter into recovery?
I get this error on my pc when I enter into recovery " error device '(null)' not found adb"

rayyansyed said:
Hi There,
I have the same problem after the update.
I followed your steps but to enter into recovery mode I had to enable USB debugging mode which cannot be done as the watch keeps on rebooting.
Please let me know is there any other way to enable usb debugging mode to enter into recovery?
I get this error on my pc when I enter into recovery " error device '(null)' not found adb"
Click to expand...
Click to collapse
Can anybody help me out in bringing my watch to life?

Great post. . . .

Driver Issue
I can get into the fastboot menu but my pc cannot recognize it. What is the appropriate method to connecting it. I have tried different cables, google driver, adb driver but the device doesnt even show up.

Teamwin boot loop after factory reset

An app in google play store wasn't installing correctly and I was told a factory reset would fix my issue but now when the Kindle HD reboots it stays on the blue screen teamwin logo and keeps looping. How do I solve this ?
p.s my fastbooy cable is coming tomorrow but not sure what to do with it

did you manage to sort this im in the exact same position. factory reset within a custom rom! in windows its recognised in adb but not authorised and cant get it to recognise whilst in fastboot

KindleFireHD7" said:
did you manage to sort this im in the exact same position. factory reset within a custom rom! in windows its recognised in adb but not authorised and cant get it to recognise whilst in fastboot
Click to expand...
Click to collapse
Yeah I got it up and running again NO help to this site ... anyways
First I bought this Fastboot cable
www.amazon.com
Second install these Drivers:
http://forum.xda-developers.com/attachment.php?attachmentid=1337103&d=1348009415
Third install 2nd set of drivers if you need them/Used this tool to restore the kindle
https://drive.google.com/file/d/0B14UeDuAgQxRSjdzNGFDMzVRcms/view?usp=sharing
option 2 if that one didn't work or if you want to restore with root access
http://androidcowboy.com/2013/07/how-to-recover-bricked-kindle-fire-hd/

meowmix2 said:
Yeah I got it up and running again NO help to this site ... anyways
First I bought this Fastboot cable
www.amazon.com
Second install these Drivers:
http://forum.xda-developers.com/attachment.php?attachmentid=1337103&d=1348009415
Third install 2nd set of drivers/Used this tool to restore the kindle
https://drive.google.com/file/d/0B14UeDuAgQxRSjdzNGFDMzVRcms/view?usp=sharing
option 2 if that one didn't work or if you want to restore with root access
http://androidcowboy.com/2013/07/how-to-recover-bricked-kindle-fire-hd/
Click to expand...
Click to collapse
Will give this a go later on , I have fastboot cable just having serious trouble trying to pc to recognize it whilst in fast boot mode. It recognizes it in adb but it's unauthorized so that's no help. Thanks for reply will let you know how I get on
---------- Post added at 10:50 PM ---------- Previous post was at 10:40 PM ----------
meowmix2 said:
Yeah I got it up and running again NO help to this site ... anyways
First I bought this Fastboot cable
www.amazon.com
Second install these Drivers:
http://forum.xda-developers.com/attachment.php?attachmentid=1337103&d=1348009415
Third install 2nd set of drivers if you need them/Used this tool to restore the kindle
https://drive.google.com/file/d/0B14UeDuAgQxRSjdzNGFDMzVRcms/view?usp=sharing
option 2 if that one didn't work or if you want to restore with root access
http://androidcowboy.com/2013/07/how-to-recover-bricked-kindle-fire-hd/
Click to expand...
Click to collapse
its failing to install the first set of drivers any suggestions?? thanks

KindleFireHD7" said:
Will give this a go later on , I have fastboot cable just having serious trouble trying to pc to recognize it whilst in fast boot mode. It recognizes it in adb but it's unauthorized so that's no help. Thanks for reply will let you know how I get on
---------- Post added at 10:50 PM ---------- Previous post was at 10:40 PM ----------
its failing to install the first set of drivers any suggestions?? thanks
Click to expand...
Click to collapse
continue to second set maybe the first set of drivers is what worked for me maybe you don't need them . I'll try to find the source where i found them maybe you need a different set that was provided
update* ok heres the source of the ADB drives that finally worked for me
http://forum.xda-developers.com/showthread.php?t=1893838
Your goal is for the unbrick tool to detect your device. so find right combination of drives that work for you. some people even go to thier driver manager and uninstall / refresh them from there. If it still not working try uninstalling all previous drives and do a clean install with the two i gave you

Fix...
meowmix2 said:
An app in google play store wasn't installing correctly and I was told a factory reset would fix my issue but now when the Kindle HD reboots it stays on the blue screen teamwin logo and keeps looping. How do I solve this ?
p.s my fastbooy cable is coming tomorrow but not sure what to do with it
Click to expand...
Click to collapse
Hello,
Fortunately, i was in the same position as you and that too, for a whole year and 3 months. But I was a noob at that time. With your fastboot cable to be usable(no drivers needed but just a simple program), you need to get (Minimal ADB and Fastboot. The link is provided for download. Now you need to do some research. For me I found out that the main problem was that it was a TWRP problem and nothing else. So I am guessing you ahve the exact same. You need to go to CyanogenMod Wiki(discountinued so you'll have to wait until Lineage OS gets their Wiki up and then figure it out) and from there find your device and then the installation instructions whihc include the downlaod link for TWRP. From there download the recovery(it will link you to android file host or something like that). Now you can install Minimal Adb and Fastboot(MAF) and install it wherever convenient to you. Now you can place the zip file of recovery in the folder where MAF is installed and rename it to recovery.zip for your convenience. In that folder, open the exe that says "MAFAF" or something to that extent(dont' have it memorized lol). Now connect your fastboot cable to your Kindle and it should turn on with a screen on the kindle that says Fastboot and then Kindle. Now on your MAF, you cna check it's working by typing
Code:
fastboot devices
or
Code:
adb devices
. In theory, you should get something like " recovery (device number[random letters and numbers])". From this you can now type in
Code:
fastboot flash recovery recovery.zip
as done to flash our TWRP recovery. When this finishes(shouldn't take to long), you can detach the fastboot form the computer and device. Next, hodl down power to turn it off. Wait like 5 seconds after shut down and then turn the Kindle back on. This should momentarily boot into TWRP and then it will take off into your ROM or whatever OS you have installed. Now you should have not jsut fixed your problem but got TWRP to work too and from there it is easy to do stuff without the need of a PC. Hope this helps and feel free to quote me with a post if something didn't work or messed up. Sorry for bad grammer and spelling. Thanks!

meowmix2 said:
continue to second set maybe the first set of drivers is what worked for me maybe you don't need them . I'll try to find the source where i found them maybe you need a different set that was provided
update* ok heres the source of the ADB drives that finally worked for me
http://forum.xda-developers.com/showthread.php?t=1893838
Your goal is for the unbrick tool to detect your device. so find right combination of drives that work for you. some people even go to thier driver manager and uninstall / refresh them from there. If it still not working try uninstalling all previous drives and do a clean install with the two i gave you
Click to expand...
Click to collapse
Sorted thank you!

Can I please get some help I think I might of bricked my phone

So using a root app disabler I disabled "telephony service" and when I restarted it shutdown immediately, on the newest WW rom it doesnt have a recovery so I cant go in there and wipe to factory reset. Right now I'm getting slot_b is unbootable. My computer recognizes the phone as "Android Bootloader Interface" but when I run "adb devices" it doesnt show up and I cant run fastboot commands even though I'm plugged into the side usb port. Please help me.

trustedenemy said:
So using a root app disabler I disabled "telephony service" and when I restarted it shutdown immediately, on the newest WW rom it doesnt have a recovery so I cant go in there and wipe to factory reset. Right now I'm getting slot_b is unbootable. My computer recognizes the phone as "Android Bootloader Interface" but when I run "adb devices" it doesnt show up and I cant run fastboot commands even though I'm plugged into the side usb port. Please help me.
Click to expand...
Click to collapse
Was the boot img rooted, is that why you have no recovery? If so, just boot to fastboot mode and flash stock boot instead of root, that should have recovery

trustedenemy said:
So using a root app disabler I disabled "telephony service" and when I restarted it shutdown immediately, on the newest WW rom it doesnt have a recovery so I cant go in there and wipe to factory reset. Right now I'm getting slot_b is unbootable. My computer recognizes the phone as "Android Bootloader Interface" but when I run "adb devices" it doesnt show up and I cant run fastboot commands even though I'm plugged into the side usb port. Please help me.
Click to expand...
Click to collapse
Can you go to bootloader screen ?
If you can
Just use the full stock Rom
Flash it
---------- Post added at 04:45 PM ---------- Previous post was at 04:42 PM ----------
https://drive.google.com/file/d/1M2V1Jh2CS5vt1xbQYlDvhxfu0yB6hmZi/view
Download the Full Rom
Extract it
Use the exe file to install with bootloader screen

Ok that was able to get me back to recovery, I tried to wipe and then boot into android, didn't work got the "your device is corrupt and cannot be trusted and will not boot". Still isn't recognized in adb devices so I don't know how I would proceed from here. My device is the Tencent Edition if that helps with raw firmware/rom.
P.S Thank you guys so much for your help I really appreciate it.

trustedenemy said:
Ok that was able to get me back to recovery, I tried to wipe and then boot into android, didn't work got the "your device is corrupt and cannot be trusted and will not boot". Still isn't recognized in adb devices so I don't know how I would proceed from here. My device is the Tencent Edition if that helps with raw firmware/rom.
P.S Thank you guys so much for your help I really appreciate it.
Click to expand...
Click to collapse
Did you fix it ?

rowihel2012 said:
Did you fix it ?
Click to expand...
Click to collapse
No, I still cannot boot into android and it still isnt recognized in adb devices, but I can get into recovery now.

trustedenemy said:
No, I still cannot boot into android and it still isnt recognized in adb devices, but I can get into recovery now.
Click to expand...
Click to collapse
But you get fastboot mode, just plug the USB in side port and flash latest raw WW Rom.
Here's the link to 1908.21
https://drive.google.com/file/d/13Mgz9GhopE-DUsGT3N_5qC283cKkUxYb/view?usp=drivesdk
Once in fastboot mode (the first menu you see, before selecting recovery, start, power off etc is fastboot mode) check your device is recognised with fastboot devices cmd and then run flashall_AFT.cmd that'll get back your working rom . But also, delete or move the original zip from that same extracted folder, the raw rom with the same name confuses the flashall_AFT.cmd

So I flash the most recent firmware you linked and double checked in recovery that it was pushed to the device and it was, but when I try to boot into android I get the asus logo for a second and then it restarts and it will give me a screen that says "Your device is corrupt. It cant be trusted and will not boot" and then has a link to google support .

trustedenemy said:
So I flash the most recent firmware you linked and double checked in recovery that it was pushed to the device and it was, but when I try to boot into android I get the asus logo for a second and then it restarts and it will give me a screen that says "Your device is corrupt. It cant be trusted and will not boot" and then has a link to google support .
Click to expand...
Click to collapse
Did you let the raw rom flash entirely? It should take a minimum of 10 minutes... The phone should reboot twice (I think) as it completes... Maybe try again, but I'm not familiar with that message...
If the phone doesn't reboot, I would let it run for a half hour or so before rebooting...

There we go, I got it to work man, I was just being impatient with the firmware flash but now I got it to work I appreciate your help and patience so much let me got through and thank your comments and then you can flag a mod to take down this thread. Thank you

trustedenemy said:
There we go, I got it to work man, I was just being impatient with the firmware flash but now I got it to work I appreciate your help and patience so much let me got through and thank your comments and then you can flag a mod to take down this thread. Thank you
Click to expand...
Click to collapse
Excellent, glad you got it working again

trustedenemy said:
There we go, I got it to work man, I was just being impatient with the firmware flash but now I got it to work I appreciate your help and patience so much let me got through and thank your comments and then you can flag a mod to take down this thread. Thank you
Click to expand...
Click to collapse
Yes this way always fix bootloap problem
Thanks asus for this easy flashing