Database Develop

A Goldcard Can Be Made for The HTC Vivid

C:\Users\Mini7\Desktop\New folder>fastboot oem writesecureflag 0
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) holiday_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
(bootloader) writesecureflag: Permission denied, value 1
OKAY [ 1.108s]
finished. total time: 1.108s
Goldcards....

i have made a goldcard for my vivid. it isnt allowing me to flash anything on it but the stock RUU .zip

Pirateghost said:
i have made a goldcard for my vivid. it isnt allowing me to flash anything on it but the stock RUU .zip
Click to expand...
Click to collapse
Have you tried looking for a way to expose the smart_IO.crd file?
referring to this quote on pastebin
http://pastebin.com/KmKe6keE
RUU sends the file to the phone and not external or internal storage at least i would think. keeping the file in memory like a tsr.
Ive noticed in a few tests during fastboot command executions the phone will delete specific offsets in memory automatically as if it was playing hide and seek.
Do you know any way of capturing data in the phones memory during a fastboot-usb session?
Im using the fastboot oem rebootRUU function, you will get the regular black screen with the HTC logo, but adb commands still work....
Im thinking if there was a way we could log the process of the install we could get a glimpse as to where this file may be pushed to. It could be generated uniquely on a per phone basis from RUU itself....at least thats what im led to

He's offer suggestions, are u?
Sent from my Inspire 4G using xda premium

maddiedad2009 said:
He's offer suggestions, are u?
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
He's spamming useless/old information across four threads.

There is already a thread devoted to ideas. Please post your ideas there.
Sent from my PG86100 using xda premium

[Q] Fastboot detect USB but adb doesn't [SOLVED]

Hello,
I have a HTC One S-On with bootloader unlocked.
I have installed Android Revolution HD, it worked fine for 2-3 months and suddenly the phone was not detected by any computer, and it was only charging when OFF.
I tried to restore with a stock rom and it was the same.
Then I have tried to format everything with CWM and to reflash with a new stock rom.
Now the problem is that when I plug the phone in fastboot mode it shows "fastboot USB", and it's well detected by computers, but when I start CWM or TWRP and when I try to mount USB storage, computers detect it for 1 or 2 seconds only and the USB storage never appear in the computer.
:crying:
So Im stuck can someone please help !!!

fenix71230 said:
Hello,
I have a HTC One S-On with bootloader unlocked.
I have installed Android Revolution HD, it worked fine for 2-3 months and suddenly the phone was not detected by any computer, and it was only charging when OFF.
I tried to restore with a stock rom and it was the same.
Then I have tried to format everything with CWM and to reflash with a new stock rom.
Now the problem is that when I plug the phone in fastboot mode it shows "fastboot USB", and it's well detected by computers, but when I start CWM or TWRP and when I try to mount USB storage, computers detect it for 1 or 2 seconds only and the USB storage never appear in the computer.
:crying:
So Im stuck can someone please help !!!
Click to expand...
Click to collapse
Your drivers are probably not up to date. Install HTC Sync Manager, connect phone to the manager, uninstall HTC SM. Otherwise check that USB Debugging is enabled.
If that doesn't work, get S-OFF, flash an RUU and see if it fixes it.

attanasi0 said:
Your drivers are probably not up to date. Install HTC Sync Manager, connect phone to the manager, uninstall HTC SM. Otherwise check that USB Debugging is enabled.
If that doesn't work, get S-OFF, flash an RUU and see if it fixes it.
Click to expand...
Click to collapse
I have just installed new HTC Sync Manager, I connect my phone via USB (fastboot USB), it install fine the driver (My HTC) then HTC SYnc Manager tells me that : Phone is not available, please reconnect it.
If I go back to bootloader and then fastboot USB HTC Sync tells me that again.
I can't get S-OFF because I have no OS installed
Please help !

fenix71230 said:
I have just installed new HTC Sync Manager, I connect my phone via USB (fastboot USB), it install fine the driver (My HTC) then HTC SYnc Manager tells me that : Phone is not available, please reconnect it.
If I go back to bootloader and then fastboot USB HTC Sync tells me that again.
I can't get S-OFF because I have no OS installed
Please help !
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (remove IMEI and s/n), and which ROM you are/were using. (you say no OS installed, how did you wipe it?) post more details so we can figure out where you are at.

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1020.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__247
(bootloader) battery-status: good
(bootloader) battery-voltage: 3625mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.051s
I was with Anroid Revolution HD 30.0
I wiped all with CWM with format system, cache, data

fenix71230 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1020.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__247
(bootloader) battery-status: good
(bootloader) battery-voltage: 3625mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.051s
I was with Anroid Revolution HD 30.0
I wiped all with CWM with format system, cache, data
Click to expand...
Click to collapse
OK, no problem. A couple of notes:
1- ARHD 30/31 is based on Android 4.3; and Android 4.3 is known to have (sometimes) connectivity issues (MTP and adb), these are usually solved by a combination of updated HTC drivers and/or updated firmware.
2- You are still on firmware 1.29.1020.2 and S-On, so you cannot flash unsigned firmware.... Are you interested/willing/able to getting S-Off (what's the date of you hboot)?
3- to get a ROM to your phone, you should enter CWM recovery, "adb" would work from there, you can either
------ "adb push <name of rom>.zip /sdcard/"
------ adb sideload
------ OR if you have an OTG cable, you can use that

nkk71 said:
OK, no problem. A couple of notes:
1- ARHD 30/31 is based on Android 4.3; and Android 4.3 is known to have (sometimes) connectivity issues (MTP and adb), these are usually solved by a combination of updated HTC drivers and/or updated firmware.
2- You are still on firmware 1.29.1020.2 and S-On, so you cannot flash unsigned firmware.... Are you interested/willing/able to getting S-Off (what's the date of you hboot)?
3- to get a ROM to your phone, you should enter CWM recovery, "adb" would work from there, you can either
------ "adb push <name of rom>.zip /sdcard/"
------ adb sideload
------ OR if you have an OTG cable, you can use that
Click to expand...
Click to collapse
Yes I am interested by installing S-Off but how can I do without OS and in CWM adb doesn't detect my phone.
My hboot date is 11 March 2013.
I don't have an OTG cable yet but I have order one.

fenix71230 said:
Yes I am interested by installing S-Off but how can I do without OS and in CWM adb doesn't detect my phone.
My hboot date is 11 March 2013.
I don't have an OTG cable yet but I have order one.
Click to expand...
Click to collapse
adb should work in CWM (I had one version that didnt, but the rest should), so just because it works for me, can you download the following one:
recovery-clockwork-touch-6.0.3.2-m7--v2.img (7.2 MB)
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD5: 1c6afb14db3f305b0ad7d85d5af80bef
Once you've downloaded and verified MD5:
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
and confirm "adb devices" now shows you are connected. we'll proceed from there.
BTW: hboot 11 March 2013 is good for revone, I'll PM you a link for a ROM that works for that when you confirm adb is working.
EDIT: can you copy/paste you command prompt as you do the above mentioned fastboot commands.

All done but when I launch CWM it shows :
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
Pc has well installed USB composite device, Mass storage USB device, won't install Android Phone : device disconnected, well installed HTC Android Phone USb Device
When I type adb devices it detect nothing I fear a hardware failure?
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot erase cache
erasing 'cache'...
OKAY [ 0.063s]
finished. total time: 0.064s
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot flash recovery recov
ery.img
sending 'recovery' (7422 KB)...
OKAY [ 1.143s]
writing 'recovery'...
OKAY [ 0.649s]
finished. total time: 1.794s
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot erase cache
erasing 'cache'...
OKAY [ 0.053s]
finished. total time: 0.053s
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.048s
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>

I had pretty much the same problem as you for a long time and did the following:
Uninstalled everything to do with HTC - drivers, sync etc
Downloaded a program called USBDEVIEW (google it) and then install it. Make sure you run it as administrator. It will load all the drivers installed. At this point make sure the phone is not connected. Select all the HTC drivers and delete - anything that says android usb, htc, mtp device etc
Once thats done I went to C:\windows\system32\driverstore and theres a file there I think called info cache. Right clich and change the security so that you can edit the file and then delete. Restart the computer
Try then inserting the phone to a USB 2.0 port and allow the drivers to install. Make sure you are using the HTC cable!
This is how I fixed it anyways, hope it works for you!

fenix71230 said:
All done but when I launch CWM it shows :
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
Click to expand...
Click to collapse
This is normal.
fenix71230 said:
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.048s
Click to expand...
Click to collapse
Did you enter Recovery after that? Can you see CWM recovery screen? adb will not work in bootloader.

nkk71 said:
This is normal.
Did you enter Recovery after that? Can you see CWM recovery screen? adb will not work in bootloader.
Click to expand...
Click to collapse
Yes i can enter and see CWM, that's when my PC have detected it but won't install Android phone

stovie_steve said:
I had pretty much the same problem as you for a long time and did the following:
Uninstalled everything to do with HTC - drivers, sync etc
Downloaded a program called USBDEVIEW (google it) and then install it. Make sure you run it as administrator. It will load all the drivers installed. At this point make sure the phone is not connected. Select all the HTC drivers and delete - anything that says android usb, htc, mtp device etc
Once thats done I went to C:\windows\system32\driverstore and theres a file there I think called info cache. Right clich and change the security so that you can edit the file and then delete. Restart the computer
Try then inserting the phone to a USB 2.0 port and allow the drivers to install. Make sure you are using the HTC cable!
This is how I fixed it anyways, hope it works for you!
Click to expand...
Click to collapse
I've done all that and after my PC won't install : USB MTP device, Android Phone

fenix71230 said:
Yes i can enter and see CWM, that's when my PC have detected it but won't install Android phone
Click to expand...
Click to collapse
Ok, that's either a driver version and/or adb version problem. get the latest HTC drivers and adb sdk. Are you on Win 8 or 8.1 by any chance? Maybe try a different PC.
Search the threads (or google), there are plenty of answers for that. Here's one, but I can't confirm it as I havent tried it:
http://forum.xda-developers.com/showthread.php?p=45415030#post45415030
http://forum.xda-developers.com/showthread.php?t=2256359
PS: don't forget to hit the thanks button if someone helped!

nkk71 said:
Ok, that's either a driver version and/or adb version problem. get the latest HTC drivers and adb sdk. Are you on Win 8 or 8.1 by any chance? Maybe try a different PC.
Search the threads (or google), there are plenty of answers for that. Here's one, but I can't confirm it as I havent tried it:
http://forum.xda-developers.com/showthread.php?p=45415030#post45415030
http://forum.xda-developers.com/showthread.php?t=2256359
PS: don't forget to hit the thanks button if someone helped!
Click to expand...
Click to collapse
I have tried with 3-4 different PC, using WIndows 7 64, WIndows 8, 8.1, always the same end (adb won't detect it)
Here on my PC I am on Windows 7 x64.
Maybe it's a phone hardware problem, I don't know what to do please help :crying:

fenix71230 said:
I have tried with 3-4 different PC, using WIndows 7 64, WIndows 8, 8.1, always the same end (adb won't detect it)
Here on my PC I am on Windows 7 x64.
Maybe it's a phone hardware problem, I don't know what to do please help :crying:
Click to expand...
Click to collapse
That worked ouff thanhs for all :
I have uninstall all HTC driver and HTCF Sync Manager, downloaded the latest HTC Sync Manger, installed it then uninstalled it, just remain new HTC drivers.
Then I took adb from HTC all_in_one kit 1.2, redo the commands and I pushed my rom on my sdcard.
Thanks a lot !!! :good:

fenix71230 said:
That worked ouff thanhs for all :
I have uninstall all HTC driver and HTCF Sync Manager, downloaded the latest HTC Sync Manger, installed it then uninstalled it, just remain new HTC drivers.
Then I took adb from HTC all_in_one kit 1.2, redo the commands and I pushed my rom on my sdcard.
Thanks a lot !!! :good:
Click to expand...
Click to collapse
:good::good:, glad everything worked out. Could I ask you to update the main thread title to include [SOLVED] so that others know is solved when they refer to it.

nkk71 said:
:good::good:, glad everything worked out. Could I ask you to update the main thread title to include [SOLVED] so that others know is solved when they refer to it.
Click to expand...
Click to collapse
How can I update the title ?

fenix71230 said:
How can I update the title ?
Click to expand...
Click to collapse
go to your first post and EDIT it, at the bottom of the edit window there's GO ADVANCED, once you click that you can see the main thread title and change it to include [SOLVED]

stovie_steve said:
I had pretty much the same problem as you for a long time and did the following:
Uninstalled everything to do with HTC - drivers, sync etc
Downloaded a program called USBDEVIEW (google it) and then install it. Make sure you run it as administrator. It will load all the drivers installed. At this point make sure the phone is not connected. Select all the HTC drivers and delete - anything that says android usb, htc, mtp device etc
Once thats done I went to C:\windows\system32\driverstore and theres a file there I think called info cache. Right clich and change the security so that you can edit the file and then delete. Restart the computer
Try then inserting the phone to a USB 2.0 port and allow the drivers to install. Make sure you are using the HTC cable!
This is how I fixed it anyways, hope it works for you!
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU!
Fixed finally!

[Q] My HTC ONE problem!

Hello, I have a big problem on my htc one.
My phone reconnecting with vibration. I tried to install RUU, firmware... ADB is not working, I can only use Fastboot.
I tried to install clockworkmod recovery, but ADB is not working....
Please help me..

NedasAndrius said:
Hello, I have a big problem on my htc one.
My phone reconnecting with vibration. I tried to install RUU, firmware... ADB is not working, I can only use Fastboot.
I tried to install clockworkmod recovery, but ADB is not working....
Please help me..
Click to expand...
Click to collapse
What does "reconnecting with vibration mean"? The phone stopped vibrating?

aooga said:
What does "reconnecting with vibration mean"? The phone stopped vibrating?
Click to expand...
Click to collapse
No, phone show HTC one logo and restart...

NedasAndrius said:
No, phone show HTC one logo and restart...
Click to expand...
Click to collapse
Oh okay. If ADB isn't working, are you sure you installed the right drivers? You should be able to go into RUU mode and flash the RUU once the drivers are installed. Just search for the drivers here on XDA.

aooga said:
Oh okay. If ADB isn't working, are you sure you installed the right drivers? You should be able to go into RUU mode and flash the RUU once the drivers are installed. Just search for the drivers here on XDA.
Click to expand...
Click to collapse
I am installed HTC sync drivers.
Code:
adb devices
ADB error:device not found

NedasAndrius said:
I am installed HTC sync drivers.
Code:
adb devices
ADB error:device not found
Click to expand...
Click to collapse
can you check FAQ #2 in my guide if that's the problem.
fastboot devices only works in bootloader
adb devices only work in custom recovery or a booted ROM with USB debugging enabled

nkk71 said:
can you check FAQ #2 in my guide if that's the problem.
fastboot devices only works in bootloader
adb devices only work in custom recovery or a booted ROM with USB debugging enabled
Click to expand...
Click to collapse
But I have s-on...

NedasAndrius said:
But I have s-on...
Click to expand...
Click to collapse
i was only referring to FAQ #2 about how to fix drivers, so i don't need to post all if it again, but here you go (this applies to not only Win7, it's a general thingy when the drivers don't get installed properly in Windows):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways​
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------

nkk71 said:
i was only referring to FAQ #2 about how to fix drivers, so i don't need to post all if it again, but here you go (this applies to not only Win7, it's a general thingy when the drivers don't get installed properly in Windows):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways​
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
ADB don't working... Help me.

NedasAndrius said:
ADB don't working... Help me.
Click to expand...
Click to collapse
you need to clarify, ^^ that statement doesn't explain much.
when you are in custom recovery (TWRP or CWM), check Windows Device Manager -> does it show up correctly?
-> if yes, adb devices doesn't give you any output?

nkk71 said:
you need to clarify, ^^ that statement doesn't explain much.
when you are in custom recovery (TWRP or CWM), check Windows Device Manager -> does it show up correctly?
-> if yes, adb devices doesn't give you any output?
Click to expand...
Click to collapse
Enable the USB into your computer and turn off the phone. Only in this way come into recovery mode, and see my device maneger:
Enable fastboot mode, connect a USB and see:
What's problem?

NedasAndrius said:
Enable the USB into your computer and turn off the phone. Only in this way come into recovery mode, and see my device maneger:
Enable fastboot mode, connect a USB and see:
What's problem?
Click to expand...
Click to collapse
Well the screenshot of fastboot mode is good, but the other doesn't even show any connected device (was that taken while the phone was in recovery?)
Which recovery (name and version please) are you using?

nkk71 said:
Well the screenshot of fastboot mode is good, but the other doesn't even show any connected device (was that taken while the phone was in recovery?)
Which recovery (name and version please) are you using?
Click to expand...
Click to collapse
*** TAMPERED ***
*** UNLOCKED ***
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35AW923426
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4148mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Turning off the phone, I plug in a USB - phone is charging and automatically switches to recovery mode...
Going to bootloader >> recovery - DON'T WORKING! I have ping letters "Entering to recovery", but phone restarting...
I'm flashing ClockworkMod Recovery v6.0.3.3 (touch don't working), but recovery working.
I flashing openrecovery-twrp-2.6.3.3-m7 but don't working I see battery charging, but recovery does not turn - but I have:
Also newest clockworkmod recovery versions..
Also philz_touch_6.08.9-m7ul, but recovery working and i have unknown devices, but ADB don't working...
I click this image and see:
Unknown device in here:

NedasAndrius said:
*** TAMPERED ***
*** UNLOCKED ***
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35AW923426
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4148mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Turning off the phone, I plug in a USB - phone is charging and automatically switches to recovery mode...
Going to bootloader >> recovery - DON'T WORKING! I have ping letters "Entering to recovery", but phone restarting...
I'm flashing ClockworkMod Recovery v6.0.3.3 (touch don't working), but recovery working.
I flashing openrecovery-twrp-2.6.3.3-m7 but don't working I see battery charging, but recovery does not turn - but I have:
Also newest clockworkmod recovery versions..
Also philz_touch_6.08.9-m7ul, but recovery working and i have unknown devices, but ADB don't working...
I click this image and see:
Unknown device in here:
Click to expand...
Click to collapse
only reason I asked is cause TWRP 2.7.0.0 seems to have problems with adb, the other ones should work
now update that "Unknown USB device" as I mentioned before (by manually selecting My HTC)
BTW, USB 2 ports are preferred!

nkk71 said:
only reason I asked is cause TWRP 2.7.0.0 seems to have problems with adb, the other ones should work
now update that "Unknown USB device" as I mentioned before (by manually selecting My HTC)
BTW, USB 2 ports are preferred!
Click to expand...
Click to collapse
I can't update drivers:

NedasAndrius said:
I can't update drivers:
Click to expand...
Click to collapse
Don't use "have disk", just unselect "Show compatible hardware", then Android USB Devices -> My HTC

nkk71 said:
Don't use "have disk", just unselect "Show compatible hardware", then Android USB Devices -> My HTC
Click to expand...
Click to collapse
I can not find "Android USB Devices":

NedasAndrius said:
I can not find "Android USB Devices":
Click to expand...
Click to collapse
in that window, go to HTC ..... -> My HTC

nkk71 said:
in that window, go to HTC ..... -> My HTC
Click to expand...
Click to collapse
I know, but there is nothing related to HTC or ANDROID.

NedasAndrius said:
I know, but there is nothing related to HTC or ANDROID.
Click to expand...
Click to collapse
Question 1: so nothing like this:
and question 2: the instructions in post #8 don't work?
.

Amazon Fire 7 (2015) 5.1.1 Stuck in Bootloop with No Recovery. Help ):

Hi all,
This is my first post here as I've been using XDA for years without issue, following other threads and seeing the community thrive. But i've gone and got myself stuck.
I recently got the 2015 Amazon Fire 7 and upon tuning it on, it updated to 5.1.1 after this I quickly saw how awful Fire OS is. I rooted (Thanks to RootJunky's Supertool) Installed GAPPS and Nova launcher, before I realised it's potential was wasted with the Fire OS.
After this I used another RootJunky tutorial to use Flashfire and install SlimLP with GAPPS.
This was successful. After this, I moved onto to wanting to install CM12.1. I found an Unofficial build with GAPPS on XDA and many people confirmed it to be working. I installed with FlashFire as I had with Slim, but after 90 minutes it was still trying to install. Then, before I knew it the battery died.
Now, I have the CM boot animation, but nothing loads. I have no recovery because 5.1.1 doesn't allow for it, so i'm stuck with the CM boot animation and no recovery. I've tried to sideload via command prompt, but my computer doesn't register it as an Android device, just an MTP USB Device, and even if it did register it properly, I don't have a recovery to allow me to install via ADB.
My question is; Does anyone know how to install anything without Recovery, ADB or a functioning device? This has been the hardest device I've ever tried to root, and now I'm stuck.
Thanks in advance guys

5.1.1 does allow recovery, it just doesn't have the ==>Booting Recovery... printed on the screen anymore. Hold vol up and power, release power when logo is seen, and sideload.

glitch3yf0x said:
5.1.1 does allow recovery, it just doesn't have the ==>Booting Recovery... printed on the screen anymore. Hold vol up and power, release power when logo is seen, and sideload.
Click to expand...
Click to collapse
Thank you very much for your quick reply. I've tried that and it shows ==> FACTORY apk Mode, then goes straight back to the Cyanogen boot animation. Even after the Factory APK Mode comes up, the device still shows as an MTP USB Device. I'm looking for the drivers for the MTP Device at the moment, but I still have the sideloading issues.
Command prompt shows; 'adb' is not recognized as internal or external command, operable program or batch file, when trying to sideload.
It's clear there's something very obvious I'm missing and I'm sorry for my ignorance.

DizzyJK said:
Thank you very much for your quick reply. I've tried that and it shows ==> FACTORY apk Mode, then goes straight back to the Cyanogen boot animation. Even after the Factory APK Mode comes up, the device still shows as an MTP USB Device. I'm looking for the drivers for the MTP Device at the moment, but I still have the sideloading issues.
Command prompt shows; 'adb' is not recognized as internal or external command, operable program or batch file, when trying to sideload.
It's clear there's something very obvious I'm missing and I'm sorry for my ignorance.
Click to expand...
Click to collapse
You need to change into the directory of the platform-tools folder of android SDK to run adb. Do this with the cd command. As for booting into recovery, use the other volume button... (Down)

i cannot get to recovery using the volumeup and power it gets stuck with amazon logo , rootjunky says there is some issue in 5.1.1 after using flashfire to get in to recovery

glitch3yf0x said:
You need to change into the directory of the platform-tools folder of android SDK to run adb. Do this with the cd command. As for booting into recovery, use the other volume button... (Down)
Click to expand...
Click to collapse
Sorry to sound stupid, but could you explain how I would do it? I've tried to sort the SDK before and just either got it completely wrong (most likely) or just not understood what it is I'm meant to be doing.
Volume Down leaves me hanging at the 'Amazon' start up screen. I'm assuming this is the recovery mode without the options? So from here, sideloading should be completely possible with a fixed ADB command?

can someone please help i am in the same boat, if i hold the vol-up and power get stuck at amazon logo instead of recovery and vol-down and power takes me to fast boot mode. can some one let us know how to fix this issue?
thanks in advance

See this video and make sure to push the correct button.
https://www.youtube.com/watch?v=RQLoH-ahjy4

fastcar22 said:
can someone please help i am in the same boat, if i hold the vol-up and power get stuck at amazon logo instead of recovery and vol-down and power takes me to fast boot mode. can some one let us know how to fix this issue?
thanks in advance
Click to expand...
Click to collapse
I believe the confusion is that it should be "Vol-Down(Left button) + Power". This will put the fire device into restore mode.
Make sure your using the correct 5.11 stock rom restore file.
Once you select, "apply update from adb". It will start to communicate with your machine and ask you to side load the restore rom. Do the deed "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin".
Also if you want to run adb from any directory in windows. There's 2 methods.
#1 Temporary session method. In the command prompt. Enter the path to your adb directory, "path=c:\adb", hit enter and your good to go.
#2 Permanent method. Add the path to your environment variables.
Windows 10:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Edit environment variable > (Select New) > (Enter the path to your adb directory "c:\adb").
Un-updated Win10 or Windows 7:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Goto the end of the long line of paths and Enter the path to your adb directory ";c:\adb".

thekrakah said:
I believe the confusion is that it should be "Vol-Down(Left button) + Power". This will put the fire device into restore mode.
Make sure your using the correct 5.11 stock rom restore file.
Once you select, "apply update from adb". It will start to communicate with your machine and ask you to side load the restore rom. Do the deed "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin".
Also if you want to run adb from any directory in windows. There's 2 methods.
#1 Temporary session method. In the command prompt. Enter the path to your adb directory, "path=c:\adb", hit enter and your good to go.
#2 Permanent method. Add the path to your environment variables.
Windows 10:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Edit environment variable > (Select New) > (Enter the path to your adb directory "c:\adb").
Un-updated Win10 or Windows 7:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Goto the end of the long line of paths and Enter the path to your adb directory ";c:\adb".
Click to expand...
Click to collapse
That has been the problem I am facing; when pushing Vol Down +Power it hangs on the Amazon logo. From what others have said, I believe this is the recovery mode but as it doesn't have the options I need, I don't know how I would go about applying the ADB update.
I will try all the steps you have mentioned when I get back home today and report back. I have the stock ROM file and the drivers installed from the previous processes, but as everything I believe will have to be done via command prompt I just hope i'll be able to apply the ADB update that way.
Thank you very much for your help. I really do appreciate the time you've taken to help.

thekrakah said:
I believe the confusion is that it should be "Vol-Down(Left button) + Power". This will put the fire device into restore mode.
Make sure your using the correct 5.11 stock rom restore file.
Once you select, "apply update from adb". It will start to communicate with your machine and ask you to side load the restore rom. Do the deed "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin".
Also if you want to run adb from any directory in windows. There's 2 methods.
#1 Temporary session method. In the command prompt. Enter the path to your adb directory, "path=c:\adb", hit enter and your good to go.
#2 Permanent method. Add the path to your environment variables.
Windows 10:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Edit environment variable > (Select New) > (Enter the path to your adb directory "c:\adb").
Un-updated Win10 or Windows 7:
- System Properties > Advanced > Environment Variables > System variables > Path > (Select edit).
- Goto the end of the long line of paths and Enter the path to your adb directory ";c:\adb".
Click to expand...
Click to collapse
Hi again,
Currently trying to install the ADB update. I'm in the command prompt, with drivers installed (comes up as HTC Dream) but as there is no visual recovery mode, I cannot select 'apply ADB update'. I use 'adb devices' and it looks for but gives me nothing.
Applying the update via 'adb sideload update-kindle-global-37.5.4.1_user_541112720.bin' just leaves me with the process in command prompt, but nothing on the device. I've tried reinstalling the google drivers, but that hasn't helped. All I need is a way to enable me to apply an update via command prompt but not being able to boot into recovery has made it impossible.
I hope there is some kind of fix :/ but thank you for your help so far.

I have the same problem, Amazon recovery was working at one point as i have used it before, but try as i may it will not boot now, all i have is fastboot and a flashing CM12 logo.

DizzyJK said:
Hi again,
Currently trying to install the ADB update. I'm in the command prompt, with drivers installed (comes up as HTC Dream) but as there is no visual recovery mode, I cannot select 'apply ADB update'. I use 'adb devices' and it looks for but gives me nothing.
Applying the update via 'adb sideload update-kindle-global-37.5.4.1_user_541112720.bin' just leaves me with the process in command prompt, but nothing on the device. I've tried reinstalling the google drivers, but that hasn't helped. All I need is a way to enable me to apply an update via command prompt but not being able to boot into recovery has made it impossible.
I hope there is some kind of fix :/ but thank you for your help so far.
Click to expand...
Click to collapse
If your unable to get your Fire device into "Amazon system recovery <3>", you won't be able to apply the restore rom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It also looks like dirty loading a Rom is a currently unresolved issue.

thekrakah said:
If your unable to get your Fire device into "Amazon system recovery <3>", you won't be able to apply the restore rom.
It also looks like dirty loading a Rom is a currently unresolved issue.
Click to expand...
Click to collapse
I can't believe that That's so annoying. so there is no was to force the ADB update without enabling it on the device through recovery first?
I doubt they will, but I hope amazon release something that can fix this issue. I know it's really my own fault, but I did really like working with the Fire 7 before this.

DizzyJK said:
I can't believe that That's so annoying. so there is no was to force the ADB update without enabling it on the device through recovery first?
I doubt they will, but I hope amazon release something that can fix this issue. I know it's really my own fault, but I did really like working with the Fire 7 before this.
Click to expand...
Click to collapse
All 2015 Fires are still under warranty (assuming it hasn't already been replaced). Contact Amazon to request a 1-time exchange.

DizzyJK said:
This was successful. After this, I moved onto to wanting to install CM12.1. I found an Unofficial build with GAPPS on XDA and many people confirmed it to be working. I installed with FlashFire as I had with Slim, but after 90 minutes it was still trying to install. Then, before I knew it the battery died.
Now, I have the CM boot animation, but nothing loads. I have no recovery because 5.1.1 doesn't allow for it, so i'm stuck with the CM boot animation and no recovery. I've tried to sideload via command prompt, but my computer doesn't register it as an Android device, just an MTP USB Device, and even if it did register it properly, I don't have a recovery to allow me to install via ADB.
Click to expand...
Click to collapse
Exact same boat here, long time lurker 1st time poster too. If anyone finds a solution please post here.

Davey126 said:
All 2015 Fires are still under warranty (assuming it hasn't already been replaced). Contact Amazon to request a 1-time exchange.
Click to expand...
Click to collapse
You are an absolute genius! I got in touch with Amazon, told them exactly what I did and they sent me another out for free. It isn't the technical solution I was hoping for, but this more than makes up for it. Thank you so much for showing me this. I will still look for a solution to the problem, but I did get a free tablet out of the whole thing

If anyone else is in this boat. You can try booting recovery from fastboot. You'll have to make sure that adb/fastboot is installed on your computer. See this thread ( http://www.xda-developers.com/15-se...ing-fast-adb-fastboot-and-driver-installation ) for help installing it. After it is installed power on the fire holding the right vol + power. It will boot to fastboot mode. If you installed everything right open a command prompt and type the following without the quotes. "fastboot reboot-recovery" if everything works properly your fire will reboot to recovery. Then you can restore the fire with amazons firmware linked a few posts back. You'll have to use adb sideload.

northmendo said:
If anyone else is in this boat. You can try booting recovery from fastboot. You'll have to make sure that adb/fastboot is installed on your computer. See this thread ( http://www.xda-developers.com/15-se...ing-fast-adb-fastboot-and-driver-installation ) for help installing it. After it is installed power on the fire holding the right vol + power. It will boot to fastboot mode. If you installed everything right open a command prompt and type the following without the quotes. "fastboot reboot-recovery" if everything works properly your fire will reboot to recovery. Then you can restore the fire with amazons firmware linked a few posts back. You'll have to use adb sideload.
Click to expand...
Click to collapse
Hmm - I don't think this will work. "reboot-recovery" is not a valid fastboot parameter. "fastboot reboot recovery" (no hyphen) won't work either as the 3rd parameter needs to be a .img file that resides on the computer. To my knowledge no one has created/extracted a generic Amazon recovery for FireOS v5. There's also the problem of getting to fastboot with a bootloader >5.0.1 but that's a separate issue.
What am I missing?

Davey126 said:
Hmm - I don't think this will work. "reboot-recovery" is not a valid fastboot parameter. "fastboot reboot recovery" (no hyphen) won't work either as the 3rd parameter needs to be a .img file that resides on the computer. To my knowledge no one has created/extracted a generic Amazon recovery for FireOS v5. There's also the problem of getting to fastboot with a bootloader >5.0.1 but that's a separate issue.
What am I missing?
Click to expand...
Click to collapse
Confirmed, both commands just return you to fastboot (one flashed up an error). Absolutely no way to reboot into recovery or sideload that I've found.
If you allow it to boot normally, at the CM logo it connects as an unauthorized device so it is at least getting pasrt way into the boot. But without fully booting you cannot authorize the usb connection.
I think its unlikely a fix will be found for this, unless there's some unknown adb commands in fastboot that might work to somehow sideload a recovery or allow CM to at least boot.
---------- Post added at 11:03 PM ---------- Previous post was at 10:14 PM ----------
Maybe this helps somone:
I wonder if the fact it shows locked is causing the problems. >fastboot unlock or unlock-critical return an error, as does any of the flash commands.
The unlock code is interesting, but I have no idea what it means.
Code:
>fastboot getvar all
(bootloader) max-download-size: 134217728
(bootloader) partition-size:userdata: 17329be00
(bootloader) partition-type:userdata: unknown
(bootloader) partition-size:cache: fa00000
(bootloader) partition-type:cache: unknown
(bootloader) partition-size:system: 4b000000
(bootloader) partition-type:system: unknown
(bootloader) partition-size:TEE2: 500000
(bootloader) partition-type:TEE2: unknown
(bootloader) partition-size:TEE1: 500000
(bootloader) partition-type:TEE1: unknown
(bootloader) partition-size:LOGO: 380000
(bootloader) partition-type:LOGO: unknown
(bootloader) partition-size:MISC: 80000
(bootloader) partition-type:MISC: unknown
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: unknown
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: unknown
(bootloader) partition-size:UBOOT: 100000
(bootloader) partition-type:UBOOT: unknown
(bootloader) partition-size:EXPDB: 1160000
(bootloader) partition-type:EXPDB: unknown
(bootloader) partition-size:DKB: 100000
(bootloader) partition-type:DKB: unknown
(bootloader) partition-size:KB: 100000
(bootloader) partition-type:KB: unknown
(bootloader) off-mode-charge: 1
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: FORD
(bootloader) version: 0.5
(bootloader) unlock_status: false
(bootloader) unlock_version: 1
(bootloader) unlock_code: 0x8eaXXXXXXX
(bootloader) prod: 1
all: Done!!
finished. total time: 0.817s

Help in unlocking Locked device state

Dear All,
This question may have been asked zillion times but may be I am not intelligent enough to understand those answers. Today morning, suddenly my OP3T switched off. On restarting it shows Chinese or Japanese characters with WLAN in between.
I don't want to lose data at any cost because it contains my entire 2 years work. I am sorry but I hadn't taken backup of phone. Since morning have been trying various things. It doesn't go into recovery. It goes into Fastboot menu. From there only came to know about Locked status. Tried Minimal ADB and Fastboot.
Ran commands
Fastboot oem unlock: Failed (OEM unlock is not allowed)
Fastboot oem device-info
Device tempered: false
Device unlocked: false
Device critical unlocked: false
Charger screen enabled: false
Display Panel:
Have console: false
Selinux type: <none>
Boot_mode: Normal
Kmemleak_detect: false
force_training: false
Fastboot oem boot_mode normal: Failed
Fastboot oem boot_mode wlan: Failed
Please help me

what version of OS do you have?? what was the last update ....4.X.X or 5.X.X

If you can see you phone's internal storage from you PC, then you can copy it across.
If not, then use ADB to backup your data. You'll have to search how to do this.
Sent from my OnePlus3T using XDA Labs

If you have ADB you could try "adb pull /sdcard0/" or similar typical storage locations for internal storage.
I've read somewhere that file creation time and things like that can be reset when you pull files, but I cannot confirm.
You should look into adb commands, if that's the only thing you have access to!

shahabkhan99 said:
what version of OS do you have?? what was the last update ....4.X.X or 5.X.X
Click to expand...
Click to collapse
I am not sure of that. It was 3 weeks back

Virral said:
I am not sure of that. It was 3 weeks back
Click to expand...
Click to collapse
as @Csöndi say you have to do the backup.... if you have 4.1.2 and below you can run some commands to change the boot
if not ... you canot fix by commands
aw ... go to fastboot > conect your mobile via usb (make sure driver is there)
open cmd from adb folder & run this : fastboot oem disable_dm_verity
then see wat you get... fail or okay??

shahabkhan99 said:
as @Csöndi say you have to do the backup.... if you have 4.1.2 and below you can run some commands to change the boot
if not ... you canot fix by commands
aw ... go to fastboot > conect your mobile via usb (make sure driver is there)
open cmd from adb folder & run this : fastboot oem disable_dm_verity
then see wat you get... fail or okay??
Click to expand...
Click to collapse
It shows failed.
Tried various things. Attached are the photos of the issue.
The phone shows in device manager but internal memory still not detected.

i think you have to go for Mega brick guide.... but keep in mind there is different method to fix.... so go with without wiping data