Related
I was in rogue recovery and was partitioning an old sdcard i messed up a while back it finished partitioning then my figure hit the power button by mistake..wich shouldnt have hurt anything since it was fished doing what it was doing any way.
I think reboot recovery was hilighted when i hit the power button. It went black and never turned back on. Ive tried the volume+power and adb wont work unless its powered on so im screwed. When i plug into comp nothing happens but when i plug in the charger i get the white charging light.
Ive looked around at other brick threads but they were all stuck at moto logo and stuff but i cant even get that.
ericman77 said:
I was in rogue recovery and was partitioning an old sdcard i messed up a while back it finished partitioning then my figure hit the power button by mistake..wich shouldnt have hurt anything since it was fished doing what it was doing any way.
I think reboot recovery was hilighted when i hit the power button. It went black and never turned back on. Ive tried the volume+power and adb wont work unless its powered on so im screwed. When i plug into comp nothing happens but when i plug in the charger i get the white charging light.
Ive looked around at other brick threads but they were all stuck at moto logo and stuff but i cant even get that.
Click to expand...
Click to collapse
I'm not really familiar with the Rogue recovery for the Xoom (what it actually partitions when you choose "partition sdcard") but are you sure you were partitioning your external sdcard? in the Xoom, the internal storage is also called sdcard. IF you did the internal sdcard, you would be in trouble. I can't imagine that the recovery would let you do that though...
Yeah surly it wouldn't have an option to partition the internal sdcard. Ive used this option several times in clockwork recovery to fix cards. I never even seen any option to choose ether internal or external sdcard. It just said partition sdcard in the advanced. I'm looking at instructions to build a moto programing cord to force it to boot into fastboot.
I made the program cable. I plugged it in it started installing drivers then failed to install. Went to the next usb port then the same thing and the same on the third.
I went to moto.com got the usb drivers now when i plug it in the pc just makes the sound that it does when you plug something in and nothing happens. I checked adb devices in cmd and theres nothing. anybody have any ideas?
The same prob here
ericman77 said:
I made the program cable. I plugged it in it started installing drivers then failed to install. Went to the next usb port then the same thing and the same on the third.
I went to moto.com got the usb drivers now when i plug it in the pc just makes the sound that it does when you plug something in and nothing happens. I checked adb devices in cmd and theres nothing. anybody have any ideas?
Click to expand...
Click to collapse
Hi mates,
I have the same prob like ericman77. When I plug the usb to PC I can heard the sound when a USB is plugged in a PC, but when I am typping "adb devices", CMD says "List of devices attached" without any device. (RDS2 or RDS3 prob¿?¿?¿)
I found some interesting links that are talking about made a "service cable", solding en micro-usb's 5 pin a cable from red cable. I did it one, but nothing changed it.
Today, I will try to do another service cable, and crossing my fingers for found a solution.
I've installed SDK from Android (adb...) and downloaded moto drivers before. I am working on Win7 64 bits.
Any idea?
Thanks in advance.
Xavi.
Solved!
xfernandezs said:
Hi mates,
I have the same prob like ericman77. When I plug the usb to PC I can heard the sound when a USB is plugged in a PC, but when I am typping "adb devices", CMD says "List of devices attached" without any device. (RDS2 or RDS3 prob¿?¿?¿)
I found some interesting links that are talking about made a "service cable", solding en micro-usb's 5 pin a cable from red cable. I did it one, but nothing changed it.
Today, I will try to do another service cable, and crossing my fingers for found a solution.
I've installed SDK from Android (adb...) and downloaded moto drivers before. I am working on Win7 64 bits.
Any idea?
Thanks in advance.
Xavi.
Click to expand...
Click to collapse
Hi folks,
at least a ssolution come to my home.
I had RSD 3 error, so what does it means? My pc recognise Xoom. So, here there are the steps:
First of all, all drivers and SDK on your computer.
Plug USB and the to Xoom. The PC will recognise with the special sound.
Go to this site htt*://developer.motorola.com/products/software/ (register need) and download the files from your xoom model.
Type this:
adb reboot bootloader
fastboot flash boot <dir from boot.img>
fastboot flash system <dir from system.img>
fastboot flash recovery <dir from recovery.img>
fastboot flash userdata <dir from userdata.img>
fastboot erase cache
fastboot reboot
In "dir from" you have to paste all the files that you doanloaded before.
And at least, I have my Xoom alive again.
Thanks mates.
Good luck.
Xavi.
Good job!
Glad you bring xoom back to life!
...I think these threat will help others as well!
I'm thinking I'm just screwe. Adb reboot bootloader gives me error device not found.
Motorola Xoom screen Freezes
Hi,
I am very new and am a novice to software in general. I have a xoom, I followed the steps as described here
http://forum.xda-developers.com/showthread.php?t=1242241
and was able to
a) Set up ADB
b) Get the required drivers
c) Unlock the bootloader
d) Get CWM to work
e) was able to do In cwm, go into "install zip from sdcard" -> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.
f) I did not have this file in my micro sd card, so I accessed the computer as an USB through CWM and pasted the file into SD card
g) Then it showed in SD card
h) Then I chose it from SD card
i) The message I got is SU is installed
j) Then there was a reboot, however it freezes at the Motorola screen
I am able to get into CWM, but can not get the device to go beyond the Motorola screen.
My objective when I started this was to install a new ROM
Please help and thanks for all help.
Update - 1 and Help request
Since I could access the CWM through the device keys, I thought may be I can install another rom and it would work, so the steps I follwed
a) Connect device to Desktop
b) Device not detected, the adb devices returned nothing
c) other commands returned "waiting for device"
d) any way I connected the device to desktop using a blackberry USB cable
e) Entered Recovery mode
f) Mounted USB storage and accessed the SD card through desktop
g) Saved the file "Eos-umts_everest-2.0.0.zip" into the SD card by accessing this through the Desktop
h) used the CWM to install this zip
i) Installed the google aps as mentioned by team EOS
Result - No more Freezed Motorola screen, and there was a Team EOS screen after that there is an animation which is still going on. I am assuming this is ok and intend to let it run as long as possible. Now it's on charge and then I will take it off charge and let it run till the battery drains itself. Do let me know if I am doing anything wrong.
gaganpattanayak said:
Since I could access the CWM through the device keys, I thought may be I can install another rom and it would work, so the steps I follwed
a) Connect device to Desktop
b) Device not detected, the adb devices returned nothing
c) other commands returned "waiting for device"
d) any way I connected the device to desktop using a blackberry USB cable
e) Entered Recovery mode
f) Mounted USB storage and accessed the SD card through desktop
g) Saved the file "Eos-umts_everest-2.0.0.zip" into the SD card by accessing this through the Desktop
h) used the CWM to install this zip
i) Installed the google aps as mentioned by team EOS
Result - No more Freezed Motorola screen, and there was a Team EOS screen after that there is an animation which is still going on. I am assuming this is ok and intend to let it run as long as possible. Now it's on charge and then I will take it off charge and let it run till the battery drains itself. Do let me know if I am doing anything wrong.
Click to expand...
Click to collapse
The first boot-up can be quite long, but if it goes past, say 20 minutes, get the Xoom back into recovery and you should wipe cache partition, go to advanced and wipe dalvik cache, go back and re-flash the ROM and the Gapps files and then reboot. You might also want to re-download the ROM zip file, just in case the download was corrupt.
Good luck!
I'm thinking what ever I did when I formatted that sdcard must have completely whipped my hole xoom. Good thing I had a 3 year square trade warranty.
ericman77 said:
I'm thinking what ever I did when I formatted that sdcard must have completely whipped my hole xoom. Good thing I had a 3 year square trade warranty.
Click to expand...
Click to collapse
That's what I said in my first comment...it formatted the partitions of your internal "sdcard"...your "hard drive" in essence. That's why I stay away from that operation completely.
Update - 2 and Help request
Please see quote below,
I have mentioned that I was able to root and then upgrade to Teameos ROM. However I tried various options in Goo Manager and when I tried to flash other roms, I got a message that I need an open recovery enabled script. The goo manager offered to find and install one for me, I tried that however the same message that I need an open recovery enabled script when ever I tried to flash nightlies. Hence I decided to go back to the stock rom
a) Downloaded the relevant files from Motorola websites
b) Followed the instructions and was able to downgrade and followed the instructions for OTA updates after flashing the stock rom
c) Now this has replaced the Clockwork mod recovery.
d) Now I want to reinstall Clockwork mod
e) Hence, unlocked the bootloader, got confirmation on Xoom that it is unlocked and the device rebooted automatically, I did not have to type the reboot command in ADB
f) I flashed the clockworkmod recovery image as I have done it earlier
g) The device says flashing is successful
h) However when I reboot there is no CWM
I started surfing and realized that this is has something do with the OTA updates.
So I again flashed the Motorola stock and did the CWM without the OTA, even then I am not able to get the CWM
Please just link me to proper post so I can learn, thanks for all the help
gaganpattanayak said:
Since I could access the CWM through the device keys, I thought may be I can install another rom and it would work, so the steps I follwed
a) Connect device to Desktop
b) Device not detected, the adb devices returned nothing
c) other commands returned "waiting for device"
d) any way I connected the device to desktop using a blackberry USB cable
e) Entered Recovery mode
f) Mounted USB storage and accessed the SD card through desktop
g) Saved the file "Eos-umts_everest-2.0.0.zip" into the SD card by accessing this through the Desktop
h) used the CWM to install this zip
i) Installed the google aps as mentioned by team EOS
Result - No more Freezed Motorola screen, and there was a Team EOS screen after that there is an animation which is still going on. I am assuming this is ok and intend to let it run as long as possible. Now it's on charge and then I will take it off charge and let it run till the battery drains itself. Do let me know if I am doing anything wrong.
Click to expand...
Click to collapse
I was able to sort it out. Had to install the Gapps package.
However I was mot able to install this through goo manager. Had to download it to the SD card and install it via CWM
Regards and Thank you for all help
gaganpattanayak said:
I was able to sort it out. Had to install the Gapps package.
However I was mot able to install this through goo manager. Had to download it to the SD card and install it via CWM
Regards and Thank you for all help
Click to expand...
Click to collapse
Goomanager is great and it is also still a work in process. I'm glad you figured it out.
anyone have solutions for not powering on after flashing?
05/30/2012 14:26:08 [WARNING] Machine: stingray
05/30/2012 14:26:08 [INFORMATION] stingray_panel_init: setting pll_c to 598000000 Hz plck to 66400000 Hz
05/30/2012 14:26:09 [INFORMATION] print_constraints: stingray_panel_reg: 5000 mV
05/30/2012 14:26:12 [INFORMATION] GPIO Input Driver: Start gpio inputs for stingray-keypad in interrupt mode
05/30/2012 14:26:12 [INFORMATION] input: stingray-keypad as /devices/virtual/input/input7
05/30/2012 14:26:12 [INFORMATION] using input dev stingray-keypad for key reset
05/30/2012 14:26:13 [INFORMATION] keychord: using input dev stingray-keypad for fevent
05/30/2012 14:26:14 [INFORMATION] stingray_gps_reset_gpio: setting GPS Reset GPIO to 0
05/30/2012 14:26:14 [INFORMATION] stingray_gps_standby_gpio: setting GPS standby GPIO to 0
05/30/2012 14:26:14 [INFORMATION] stingray_gps_reset_gpio: setting GPS Reset GPIO to 1
05/30/2012 14:26:14 [INFORMATION] stingray_gps_standby_gpio: setting GPS standby GPIO to 1
05/30/2012 14:26:32 [INFORMATION] stingray_gps_standby_gpio: setting GPS standby GPIO to 0
I used android-os-monitor to get this, my xoom is mz601, i am curious why the machine identifies it as stingray.
does it mean i can flash roms for stingray
Sent from my MZ601 using xda premium
gaganpattanayak said:
05/30/2012 14:26:08 [WARNING] Machine: stingray
05/30/2012 14:26:08 [INFORMATION] stingray_panel_init: setting pll_c to 598000000 Hz plck to 66400000 Hz
05/30/2012 14:26:09 [INFORMATION] print_constraints: stingray_panel_reg: 5000 mV
05/30/2012 14:26:12 [INFORMATION] GPIO Input Driver: Start gpio inputs for stingray-keypad in interrupt mode
05/30/2012 14:26:12 [INFORMATION] input: stingray-keypad as /devices/virtual/input/input7
05/30/2012 14:26:12 [INFORMATION] using input dev stingray-keypad for key reset
05/30/2012 14:26:13 [INFORMATION] keychord: using input dev stingray-keypad for fevent
05/30/2012 14:26:14 [INFORMATION] stingray_gps_reset_gpio: setting GPS Reset GPIO to 0
05/30/2012 14:26:14 [INFORMATION] stingray_gps_standby_gpio: setting GPS standby GPIO to 0
05/30/2012 14:26:14 [INFORMATION] stingray_gps_reset_gpio: setting GPS Reset GPIO to 1
05/30/2012 14:26:14 [INFORMATION] stingray_gps_standby_gpio: setting GPS standby GPIO to 1
05/30/2012 14:26:32 [INFORMATION] stingray_gps_standby_gpio: setting GPS standby GPIO to 0
I used android-os-monitor to get this, my xoom is mz601, i am curious why the machine identifies it as stingray.
does it mean i can flash roms for stingray
Sent from my MZ601 using xda premium
Click to expand...
Click to collapse
Stingray is for CDMA/LTE (and GSM???), wingray is wifi, only.
Is your Xoom for CDMA/LTE (US version usually) or is it GSM?
My xoom is MZ601, this would me umts evesrest its a gsm/wifi handset, however this is presenting itself as stingray, so can i install nightlies for stingray or not
Sent from my MZ601 using xda premium
[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"
Hello
The situation:
I'm trying to relock the bootloader and flash RUU, so that I can get rid of the tampered flag and start over.
I'm trying to use Hasoon2000's Toolkit to do this, but I'll try any method that sounds reasonable.
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
EXTRA INFO:
I didn't use Hasoon's toolkit to unlock the bootloader, I actually used the platform-tools from the SKD bundle thru the terminal on a mac pc. Then I flashed CWM onto the One S using "./fastboot flash recovery recovery_thefilename.zip". Then I reloaded bootloader, selected Recovery, then my phone's screen went black, turned back on, and I saw the Red Triangle with the Exclamation mark. According to a "How to" blog, which I didn't read until after the fact, I was supposed to hold down the power button and volume button at that point in time, but I didn't. I had no idea what was going on. I pressed the power button and my phone restarted, and now every time I reboot to recovery mode, it just restarts the phone and says "This build is for development purposes only. Any redistribution will result in legal action." or something like that.
OK THAT'S ALL.
I appreciate any help!
jire
The text in red is normal if you have a custom recovery.
Just get the device in fastboot USB mode.
Check with command: fastboot devices
To see if it is connected. I should return you sn number.
(Since you manually unlocked, this should be easy for u.)
Then manually flash a correct recovery (or use the toolkit with the custom option). Reboot in recovery. Flash ROM.
Verstuurd van mijn One S met Tapatalk
Can you try to execute fastboot oem lock command on Windows OS which have hTC drivers installed? I guess that you using Linux OS now... Just install Windows in VM and hTC drivers, adb and fastboot you can download on htcdev.com or from android bundle package... I'm pretty sure that you have problem with your drivers...
Sent from quietly brilliant HTC One S
USB 3.0 might be the issue
Hey guys, thanks for trying to help me out here, I appreciate it a bunch!
Before I go any further. I think I've learned what the problem is. Well, first of all, if you didn't catch it, I've been working thru this on both win and apple computers.
Hasoon's toolkit is only available for windows. Therefore, if I said/say I did something with his toolkit, that means I was using my win computer, which is actually a Surface Pro, which has USB 3.0 === THE PROBLEM
According to this: http://forum.xda-developers.com/showthread.php?p=29286429
Unfortunately, I haven't been able to test this hypothesis, yet, because I first need to find a win pc with USB 2.0. [Fact: I couldn't get androidfiletransfer.app to recognize my htc one S on my mac. Coincidence?]
real187: When you say to install a "correct" recovery, are you implying I currently have an incorrect recovery on my phone?
mikronac: I have virtually no experience with command prompt. I just got my Surface Pro last week :laugh: and I'm geeking out...So, what I'm saying is I don't know how to do "fastboot oem lock command" ... The htc drivers are installed, up-to-date and operating without a hitch.
It can't be problematic your usb 3.0.
Please deinstall your phone drivers and install them again...
If you know how to navigate to platform tools folder in Windows Explorer, only what you need to do is to hold shift key on keyboard and right click on mouse and select option open command prompt here. Than you type :
Adb devices
Response should be serial number of phone
Adb reboot bootloader (uab debugging must be enabled)
When it reboot in fastboot, type in cmd:
Fastboot oem lock
Sent from quietly brilliant HTC One S
I can confirm: It is USB 3.0
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.
maatriks said:
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.
Click to expand...
Click to collapse
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
No USB 2.0
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance
dsuresh89 said:
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance
Click to expand...
Click to collapse
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...
dsuresh89 said:
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...
Click to expand...
Click to collapse
hey
there is no driver for 3.0 USB xtensible host controller for windows 8
and I already have a usb 2 but I have the same problem
I think that it came from windows 8
Thanks in advance
Unable to fastboot in Windows 8.1
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hey Bro,
I am facing the same issue. Unfortunately I don't have a USB 2.0 port in my computer. Im struggling to flash the boot file.
Please help
jire0006 said:
Hello
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
jire
Click to expand...
Click to collapse
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
To apply the workaround for a specific device, add a REG_DWORD value named SkipBOSDescriptorQuery that has a value of 1 to the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\usbflags\vvvvpppprrrr
(where vvvv is the device's Vendor ID, pppp is the device's Product ID, and rrrr is the device's Revision number. You can get the VID/PID/REV numbers from the device manager's details tab. This number is encoded in the HardwareIDs of the device)
1. Click Start, click Run, type regedit in the Open box, and then click OK .
2. Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags
3. On the Edit menu, point to New, and then click Key.
4.Type the name of the new key in the following form:
vvvvpppprrrr
where
vvvv is a 4-digit hexadecimal number that identifies the vendor (idDevice from the USB Deviceescriptor),
pppp is a 4-digit hexadecimal number that identifies the product (idVendor from the USB Device Descriptor)
rrrr is a 4-digit binary-coded decimal number that contains the revision number of the device
(bcdDevice from the USB Device Descriptor).
5. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
6. Type SkipBOSDescriptorQuery for the name of the DWORD Value, and then press ENTER.
7. Right-click SkipBOSDescriptorQuery, and then click Modify.
8. In the Value data box, type 1 , and then click OK.
9. Exit Registry Editor.
10. Unplug and re-plug the device for the workaround to take effect.
Click to expand...
Click to collapse
On mine that meant editing a registry key called 0BB40FF00100 that already existed.
windows 8 have a issue with ville fastboot... please make you sure you have a fix
zoodles said:
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
On mine that meant editing a registry key called 0BB40FF00100 that already existed.
Click to expand...
Click to collapse
THANK YOU SO MUCH. Fixed for me on HTC Magic
..
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows.
---------- Post added at 10:41 PM ---------- Previous post was at 10:17 PM ----------
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows. Btw, I tried all methods in forums and in YouTube too (updating USB Root Hub drivers). Nothing helps, just "Failed device enumeration". Windows 10.. I will go back to Win7, fortunately I don't have license for 10.. Pray about these who has...
Bruh, this worked like magic on my HTC One X+ !!!
Using Windows 10 Enterprise Build 17134 by the way
Thanks a lot!
Thank you very much bro. HTC One V good working.
First of all this is my first post and I am a complete NOOB.
Also I apologize in advance if I break any rules with this post and please excuse my terrible grammar and spelling.
Computer 1:Windows 7 Ultimate 32bit
Computer 2:Ubuntu 12.04 LTS
Device: Amazon Kindle Fire 2nd Gen
I will try to provide as much information as I can stating how I got here
Eastern Time:
11:00pm : Decided to root and flash a custom rom on my friends kindle fire hd 10.4.6 have rooted and flashed my first gen kindle and a galaxy s before successfully. So i looked around the forums and found this http://forum.xda-developers.com/showthread.php?t=2494232 The last comment lead me to this site staticchaos.freeoda.com/fire/ where I downloaded the following files
1)Kindle Fire USB driver
2) RootFire.zip
The RootFire.zip had http://imgur.com/uqFGWyu
and i rooted the device using the RunME shown http://imgur.com/OCYoM9p
11:49pm: Happy and dandy rooted and superuser was installed no problem now I had to install TWRP so I followed http://forum.xda-developers.com/showthread.php?t=2404120 and
I thought everything was fine until I realized that in the post the version he says to download is CM-10.1 and I had downloaded cm-11-20140106-NIGHTLY-otter2.zip from the link he provided. I realized that after I was in TWRP after wiping all the caches and the system I went to install it and it gave me an error which i don't remember what it said.
12:40am: So now im trying to figure how the hell to mount the kindle back so I can transfer the rom out and put the correct one in. I see there is a mount option in TWRP but it would always show up as a hidden removeable disk and when i looked at the command line it said
"E: unable to locate volume information for usb storage mode"
So i googled that and found this post http://forum.xda-developers.com/showthread.php?t=2274315
I figured okay I don't have a fastboot cable so let me try the sideboot loader. But now my computer running windows 7 ultimate 32 bit was not recognizing the kindle like before. It came up as kindle fire2 and the previous drivers werent working
so when i ran cmd an issued the adb devices command nothing showed and I was unable to sideload anything.
So then i got to thinking the error said it could not locate volume information, there was an option in TWRP that said format or partition I don't remember so the idea in my noob brain was ill partition a small part of the memory inside to hold the correct ROM and than flash it using TWRP and problem solved. until this point I could turn my kindle off and on and be able to get into TWRP no problem just hitting the power button.
After the third try of partitioning and each time failing because it could not mount "/data"
i got fustrated and went looking for answers but the kindle was dying at 3% so i shut it off and let it charge while i looked. MISTAKE
i powered it off via the power button and the light disappeared when I went to turn it on again I had no luck BLACK SCREEN and nothing
SO i turned on my xbox and decided Ill play while it charges.
1:40am: no luck nothing on the screen cant get it to come up on the computer F Me i bricked this thing. Finally wiggle the usb around plug out of the hub and directly into the computer and BAM OMAP4430 is being connected and disconnected continuously
YES WE HAVE LIFE. So i began looking at what it is and found several post
http://forum.xda-developers.com/showthread.php?t=1413951
http://forum.xda-developers.com/showthread.php?p=20565446
http://forum.xda-developers.com/showpost.php?p=19800610&postcount=74
First i found out that im in the "cpu's USB boot mode. You need to send the cpu something to boot over usb or it will loop forever trying to find something to boot off flash".
so I powered up my vmware and transfered all the files in I would need to run 2) Open a terminal and sudo or su to root. It's easier that way.
3) Unplug the USB or AC adapter if it's plugged into the KF. But have the USB cable's A end plugged into the PC. This is very important.
4) Turn the power completely off. Do a shutdown if actually running Android, or hold the power button until there's no LED or backlight.
5) Pry open the back cover. The iFixit teardown (Google it) gives some ideas on how to do it, but be really careful because it's easy to snap the tabs along the long sides. DID NOT DO THIS SINCE I HAD READ ELSEWHERE I WAS ALREADY IN THIS MODE
6) The power must still be off. If you accidentally powered it back on, turn it back off.
7) Run:
Code:
./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img
This will chain load aboot, FIREFIREFIRE, then TWRP.
This got me nothing expect waiting for
OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
unexpected 2ndstage response
< waiting for device >
and then the terminal just stood there so then on another thread I read
http://forum.xda-developers.com/showthread.php?t=1413358
" run the script usb_fix_parts_and_install_fff_twrp and plug your device in while off when it says <waiting for omap44xx device> in the terminal. The script should run when your device boots up because it`s in this state. I don`t believe you will even need the short trick"
yes a solution finally after looking for so long!
3:37am: download the files run the script run the
[email protected]:/home/orlando/Desktop/rekindle/rekindle# ./fk
5837+1 records in
5837+1 records out
5977554 bytes (6.0 MB) copied, 4.69615 s, 1.3 MB/s
Stopping any running adb servers...
Done. Tools are in /root/firekit. Files copied to USB are likely in /cdrom
Scripts:
install_fff_twrp_from_stock - install FFF and TWRP while in stock Android
install_fff_twrp - install FFF and TWRP while in fastboot
fix_parts - restore partition table to stock while in fastboot
normal_boot - set the bootmode to boot android and reboot while in fastboot
usb_boot_twrp - USB boot TWRP without installing
usb_install_fff_twrp - USB boot FFF, install FFF and TWRP
usb_fix_parts_and_install_fff_twrp - USB boot FFF, restore partition
table to stock, install FFF and TWRP
Good luck. -pokey9000
[email protected]:~/firekit#
[email protected]:~/firekit#
[email protected]:~/firekit#
[email protected]:~/firekit# usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
unexpected 2ndstage response
Fixing partitions...
< waiting for device >
"YES ITS GONNA FIX IT"
20 mins later
"NOPE"
It froze there and the kindle kept connecting and disconnecting it is now 4:30am
it will still only connect and disconnect as OMAP4430
If the developers or someone who knows more than me would be kind enough to lead me in the right direction I would appreciate it
I have tried hard to fix this thing and no luck.
+1
+1
Is this considered as terminal?
As a super hard core bricked?
*i'm here now all ill be doing now buying is broken Screen Kindle and assemble with my good screen
Try search on YouTube for Tekify lollipop or marshmallow on Kindle fire HD. He has a real easy to follow step by step. I used him on 2 kindles both with success in minutes.
Or: www.tekify.co.uk/kindle-fire-hd/roms/cyanogenmod-13-6-0-marshmallow
this computer malfunctioned.."
windows 10 64 bit opened fastboot and not working had worked in the past (forget what date) currently no rom on phone was wanting to install a new one.
tried on an other comp and no luck. I'm on twrp recovery menu and mounted device nothing showed only showed usb connected when at phone power up
Try with another usb cable. Does the phone charge correctly (if not, then usb port may be damaged). Try installing one of the ADB and fastboot installers available here e.g Minimal ADB and fastboot or 15 seconds ADB and fastboot installer.
You can copy the rom files to a sdcard if you have a sdcard reader.
Broadcasted from Zeta Reticuli
Link me if you can also i've put rom's and gapps on sd with sd reader and can't find the folder I named so I can get there.It does charge but the main power it's not saying usb connected.
Minimal ADB and fastboot installer. Do a system image before installing it, just to be safe.
And, try to place the rom and gapps into root of your sdcard, it'll save a lot of confusions. In TWRP, select Install>Select storage>External Storage. And you should see your files.
Sorry but I didn't understand you, 'the main power it's not saying usb connected' part. Is it the bootloader screen (the one comes up when you hold power+volume down?)
Broadcasted from Zeta Reticuli
same
hi i have the same problem! when i conect my xt1540 pc says "USB device not recognized" and i go to device manager and says on USB section (Device descriptor request failed) i install it minimal adb and motorola device manager on a pc with win 8.1 and win 10 pro and nothing happens, also i did the tuto about regedit on both pcs and nothing, i did and wipe data/factory reset too, my xt1540 have marshmallow 6.0 no root stock firmware.
any idea because y dont have nothing
thanks in advice and sorry bout my bad english
Problem:
When I tried to turn on my Samsung week back, it got stuck at "SAMSUNG" logo, eventualy it always turn off itself after some time. I wasn't doing anything crucial at that time when it broke (no system update, no new app installed). I can't turn on my phone to get my internal data.
What I need
I have some important photos/notes in internal storage and I can't reach for them. I only need the internal data. I know that SAMSUNG stuck logo boot issue can be fixed by wipe data/factory reset, but I would lost all my important data.
What I tried:
Removed SD card
Removed SIM card
Removed battery for few days
Let battery drop to 0% and charged back to 100%
Wiped cache partition in system recovery
Installed newest Samsung USB driver (from official Samsung site), restarted PC
Installed Kies - after connecting Samsung to PC, showing only "connecting" and after time it fails
Downloaded ADB - via CMD (/w admin priv.) tried command "adb devices" - returns empty list
Downloaded Dr.Fone (device unsupported)
FonePaw for Android (device unsupported)
I know I can get internal data via ADB, but ADB can't recognise my device for some reason. I tried 2 different cables, different USB ports (USB 2.0 / USB 3.0) / (front / back USB ports).
Also in my Device Manager, my Samsung Phone shows under "Modem" category.
What's interesting - in Odin3 (v3.13) I can see my Samsung as 0:[COM13] always without problem in any port with any cable.
I tried command "adb devices" when my Phone was in "Download Mode", "Android system recovery <3e>". In both situations - always returned empty list. In that time I was watching device manager and Odin3 to see, if my phone was really connected to my PC (it was).
Any ideas how to get those data? Btw I am newbie, just started dealing with all those things today and may not understand things clearly. Much thanks for any guidance, tips or info!
Specs:
Device: Samsung Galaxy Core Prime (SM-G360F)
Fastboot: Doesn't exist on this device
Rooted? No (tried KNOX, it remained in system but is not rooted)
USB Debugging: Was ON before logo boot stuck (Can't tell 100% sure)