Database Info

[Q] Am i bricked ?

Hi All,
i rooted my phone using what i thought was the right img file, but i can only assume it was the wrong file as i can now do nothing, i can boot into the Moto symbol, i can get to the droid with the warning triangle and into the fastboot section but i can no longer detect it when connected to the usb...
can anyone suggest a fix or am i screwed ??
thanks for any help

Try reflashing it with my tool, using unbrick feature, maybe you need fastboot drivers, just download it from sdk
Sent from my awesome ICS Xoom with xda Premium HD

cheers xxlordxx
ill give that a go, which drivers do i need to install for the fastboot ?
i downloaded the google usb driver package via the SDK last time, but it seems they are not firing up when i connect the tab.

TheWhiteDragon said:
cheers xxlordxx
ill give that a go, which drivers do i need to install for the fastboot ?
i downloaded the google usb driver package via the SDK last time, but it seems they are not firing up when i connect the tab.
Click to expand...
Click to collapse
If you can boot, you are not bricked - just start over with the root process using the correct image.

hey guys,
i have downloaded LAIOT but im not sure its detecting the pad, currently im getting
Searching For Device
List Of Devices
(Nothing listed)
on the pad
Starting Fastboot Protocol Support

tried doing the same using the different modes.
on Pad
Starting RSD Protocol Support
Same result on LAIOT

Recovery -
Same result.
this has all been done on a windows 7 laptop,
i have a linux laptop, will i get any more success using that with the google driver ?

just had a brain wave, checked device manager - i have an unknown device detected.. thats where the sodding thing has been hiding...
any ideas what drivers i need to get the dam thing detected correectly ?
just going to try using the default google ones from the SDK.

TheWhiteDragon said:
just had a brain wave, checked device manager - i have an unknown device detected.. thats where the sodding thing has been hiding...
any ideas what drivers i need to get the dam thing detected correectly ?
just going to try using the default google ones from the SDK.
Click to expand...
Click to collapse
Try a diff USB cable - download drivers from MOTOROLA website get this file - MotoHelper_2.1.32_Driver_5.4.0.exe
Okay here we go....
first thing let your xoom stuck on M logo.
Then hold power+volume up.
while power up press volume down to get firstboot.(make sure your PC and xoom know each other.)
You will see some text firstboot bla bla bla on left, top of screen.
Second thing open window cmd.exe
then type ...
cd /AndroidSDK/tools (where ever your adb.exe is located)
fastboot flash boot boot.img (the right boot image)
fastboot flash system system.img
fastboot erase cache
fastboot reboot
wait for reboot. You should see splash screen and you smile on your face.

TheWhiteDragon said:
hey guys,
i have downloaded LAIOT but im not sure its detecting the pad, currently im getting
Searching For Device
List Of Devices
(Nothing listed)
on the pad
Starting Fastboot Protocol Support
Click to expand...
Click to collapse
I need to fix it then...
Sent from my awesome ICS Xoom with xda Premium HD

thanks Mjamocha
ill give it ago tomorrow, sorry been flat out at work.
ill also try xxlords again on another machine just incase its the drivers on the laptop which are the problem.

XxLordxX said:
I need to fix it then...
Sent from my awesome ICS Xoom with xda Premium HD
Click to expand...
Click to collapse
sorry guys i have been flat out at work, SCCM deployment is taking a while to learn & play with.
but im back now and hopefully unbuggering my phone
i am going to redo all the bits you guys suggested on my PC rather than Craptop.
hopefully ill have more joy, ill let ya know how i get on 8)

What about using RDS?

woot im back
Thanks guys, just needed a fresh machine to do it on, think the craptop was a bit confused with the drivers.

TheWhiteDragon said:
woot im back
Thanks guys, just needed a fresh machine to do it on, think the craptop was a bit confused with the drivers.
Click to expand...
Click to collapse
Glad you got it going!

Had a similar problem where I had a boot loop and adb didn't recognise my device, but I could still put it into fastboot or recovery with power + vol down.
What I did was boot the Xoom so that it was stuck at the Moto logo, connected to the PC and queued up the fastboot command (fastboot flash boot boot.img) so the command window said "Waiting for device...", then reset the Xoom and manually put it into fastboot again at which point it picked up the queued command and started flashing.

Bricked My Kindle Fire

I attempted to root a Kindle Fire Running 6.2.2 but was using a version on the Kindle Fire Utility to root 6.3. TWRP installed but now I'm stuck at the yellow triangle logo.
The biggest problem is my Window 7 laptop won't recognize the Fire when I plug it in with my USB cable. Therefore, none of the unbricking, KFU, or ABD utilities/commands are getting through to the device.
Has any one encountered this before?
(I've gotten stuck in a bootloop with TWRP before on another rooted Kindle Fire and that was easy to fix.) I don't know what to do when you laptop won't recoginize the Fire as a connected device.
I've rooted another Fire (though it was running 6.3) on this same laptop so the Kindle Fire drivers were installed.
I'd appreciate any help with this!!!
Sent from my Kindle Fire using xda premium

1) Unplug your kindle
2)
Microsoft said:
Click Start, point to All Programs, point to Accessories, and then click Command Prompt.
At a command prompt, type the following command , and then press ENTER:
set devmgr_show_nonpresent_devices=1
Type the following command a command prompt, and then press ENTER:
start devmgmt.msc
Click to expand...
Click to collapse
3) After you follow those steps, look for any android/adb devices and DELETE them from device manager
4) Re-plug your kindle fire usb into computer
5) Windows should now auto detect drivers (if you have windows 7) and you can use fastboot to reboot your device or flash files.

Thank you so much for your reply! I tried what you said.
I set my Device Manager to show hidden devices. "Android Phone" appears as a device. When I expand it, I see "Android ABD Interface". The Android Phone device displays for a few seconds and then disappears. I hear the Windows OS make a tone as it appears and disappears. If I shutdown the Kindle Fire and power it on again, the device manager does the same thing.
I should probably explain more how I bricked my Fire.
I tried to root it as I explained in my first post. It was unsuccessful. When I realized the Fire was runnning 6.2.2, I tried to upgrade the firmware to 6.3.1 from the Amazon site, thinking I'd do that and then run the rooting bat file again. I didn't think to uninstall any of the rooting software before trying the update because the root was unsuccessful.
The Fire started the update but stopped almost immediately and got stuck at the TWRP logo.
Is there any thing else I can try?
Sent from my Kindle Fire using xda premium

I bet you are stuck in fast boot. Can u see it when running fast boot devices? Search as this is common... happened to me. Just need to run a com,and to change default boot mode
Sent from my Kindle Fire using XDA

Paulnsx,
Thanks for the reply.
Can you explain a little more about this >> "Can you see it when running fast boot devices"?
Where and how would I check for that? And, what is the command to change the default boot mode?
Sent from my Kindle Fire using xda premium

warranty
will Amazon replace it or is it obvious you attempted to unlock the tablet? I mean is there and indication on the boot screen?

Yes, it's obvious I was rooting it. To return it to Amazon (or the retailer in my case), I need to get it to boot normally, then reset it to the factory default.
Sent from my Kindle Fire using xda premium

Are you able to boot into the recovery? Also, you may be able to re install the drivers yourself. I know that I downloaded the KFU and it came with drivers and an unbrick app as well.

try the kindle fire section lots of good ppl to help and loads of info

I wish I could but as a junior member of xda, I'm not allowed to post there.
Sent from my Kindle Fire using xda premium

you should be able to post if its not in the dev section

You are right. I just tried (like you suggested) and my post went right up. Yeah!! Thanks for explaining this!!

I just want it back to the original status and I get nothing.... I've been at this for 3 hours and it still won't read my kindle
Update: Finally got the usb to read and everything is recovered.

HELP! Won't boot fastboot.

I was flashing back to the stock Asus US 4.1 Rom from asus.com and that worked fine, but in the process I lost root. Now the operating system runs just fine, but when I power on into bootloader that works, but if I try recovery I get the android with the red ! (eclimation point), and if it try fastboot it says its starting fastboot, but just sits there.... Can someone please help me. Anything will help, and I mean anything. if there is a way to get root back or recovery through apx or anything. Any help will be much appreciated! thanks

If you are referring to what it says on the tablet saying fastboot is enable or something like that doesn't say any thing mire than that has long has you type fastboot devices in terminal under sdk/platform-tools and comes up with a serial number your good to go? If that helps?
Sent from my Galaxy Nexus using xda premium

larryv1979 said:
If you are referring to what it says on the tablet saying fastboot is enable or something like that doesn't say any thing mire than that has long has you type fastboot devices in terminal under sdk/platform-tools and comes up with a serial number your good to go? If that helps?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sorry I should have been specific but I was at work. After I press vol and power and then go to the usb symbol; on the tablet it says "starting fastboot USB download protocol". On the computer it loads the driver for the "ASUS Android Bootloader Interface". I can't get the computer to comunicate with the tablet at all like this..."Fastboot devices" in cmd prompt does nothing. any advice?

my droid ultra shows offline in adb

I can't get my droid ultra to be recognized other than offline and can't flash it back to try the root method it says i need the fastboot o bake driver .RSD lite doesn't recoginze it in fastboot can anyone suggest a fix i have installed moto device manager 5 times each differet downloads

If I boot it up in bp mode red lite see the phone until it reboots to fastboot the it says it didn't switch modes but it seems to
Sent from my XT1080 using XDA Premium 4 mobile app

Make sure USB debug is enabled. Make sure the phone is not on the lock screen while plugged in. Unplug and replug the device. Restart the adb service (adb kill-server, then adb start-server).
These are the easiest things to try that come to mind.

Debugging is on ,lockscreen is not on . unplugged my phone and killed and restarted the server and still showing offline. Just used the same computer to unlock a HTC droid incredible 2 today and restore a lg optimus elite from a bootloop cycle. So I am pretty sure its not a issue with the computer I am using ,but I guess its time to try another computer and see if it changes anything. Any ideas or help is much appreciated and thanks nimdae for the input
Sent from my XT1080 using XDA Premium 4 mobile app

Make sure you have updated adb to the latest
Sent from my XT1080 using XDA Free mobile app

akellar said:
Make sure you have updated adb to the latest
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Glad you mentioned that has been quite some time since I updated it. Will get it done when this lg p930 is finished and be back .with good news I hope
Sent from my XT1080 using XDA Premium 4 mobile app

Yes, if it reports offline, then you don't have ADB 1.0.31. Type "adb version" and make sure it's 1.0.31.

kcipopnevets said:
Yes, if it reports offline, then you don't have ADB 1.0.31. Type "adb version" and make sure it's 1.0.31.
Click to expand...
Click to collapse
OK your right . how do I get the new one download it from the android SDK website? Well that's what I'm going to do tonight thanks all for the great help
Sent from my XT1080 using XDA Premium 4 mobile app

dogie425 said:
OK your right . how do I get the new one download it from the android SDK website? Well that's what I'm going to do tonight thanks all for the great help
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You should be able to update the tools through the manager, though I've been having trouble using the latest manager myself (it doesn't load). Otherwise, you can go to dev.android.com and download the latest package which includes the tools.

Got the new version install . and I plan to flash back to 4.4 version 19.5.3 for my phone. RSD lite is still not detecting the phone when it switches to fastboot so that brought up the question in my mind do I need to update fastboot or was this done when I updated the adb and is there anything else I might be forgetting to do b4 I start this since I will be using the manual method to flash this in fastboot? Any and all feedback is greatly appreciated. This is my everyday driver and I'm still paying for it thru the edge plan.
Sent from my XT1080 using XDA Premium 4 mobile app

Have you tried putting your phone in fastboot mode then connecting it to pc

TRIED Flashing thru fast boot
so i got the nerve to try downgrading my ultra with fastboot since rsd won't detect my phone when it switches to fastboot using this tutorial http://forum.xda-developers.com/showthread.php?t=2580060 all went well except on the mfastboot command i got this responce
C:\ANDROID PWNAGE\adt-bundle-windows-x86_64-20130917\adt-bundle-windows-x86_64-2
0140321\sdk\platform-tools>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (574208 KB)...
OKAY [ 36.243s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 59.547s
and it said on the screen mfastboot error invalid piv image size for system
now the phone won't boot just jumps right back to the bootloader screen
tried it 2 more times and still no joy same out come so what do i do now? download the file again and try once more . and do i need to repeat all the steps b4 this command or will just running this command alone be fine to fix me HELP pls

Lordomn said:
Have you tried putting your phone in fastboot mode then connecting it to pc
Click to expand...
Click to collapse
yes i tried that but found out my adb was an older version and need to be updated its seeing the phone fine now. just have to figure out my latest problem
GOOD NEWS i unzipped a second download i had in my downloads folder and used that system img file to try flashing and it when through. phone is rebooting now. time to clam down and try me some pie in a bit
(thanks jcase for the pie)

You need to update your adb and fastboot files if your devices is shown as offline...

joel_sinbad said:
You need to update your adb and fastboot files if your devices is shown as offline...
Click to expand...
Click to collapse
Pretty sure we established that roughly 3 weeks ago
Sent from my XT1080 using XDA Free mobile app

akellar said:
Pretty sure we established that roughly 3 weeks ago
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Lol

usb debugging is not necessary for fastboot commands, only ADB; however, it sounds to me like you do not have the proper drivers installed for the device if RSD is not detecting it. I would delete all Motorola drivers and Motorola Device manager, reboot computer with device unplugged, reinstall Device Manager, and then connect device. You can also download Minimal ADB and Fastboot (Google search) and it is a lot less hassle than trying to use the SDK.
You may also try using a different USB cable on a different USB port (not USB 3.0). Sometimes that causes problems.

In the end my problem was my SDK was not updated ,so the device was only seen as offline as for why rsd doesn't detect it in fastboot I do not know ,but I was able to manually flash it in the end. Now I'm loving w/p off and root with safe strap installed despite the locked bl
Sent from my XT1080 using XDA Premium 4 mobile app

LG P500 complete dead , no fastboot, no LG logo

Hi Guys, pls help me.
This is not the first time i tried to update firmware using KDZUpdater [KDZ_FW_UPD.exe] .
But this is the first time my device has been bricked.
During updating my firmware, i was in "Emergency Mode" and i received some error on KDZUpdater GUI Console.
As i was unable to move from "Emergeny Mode", i tried again to update firmware, but again i got some error.
I thought removing the battery will do some good, but i was wrong.
Now my mobile is as good as "BLACK BRICK".
It even doesn't detect in "Device Manager".
Note:
Before using "KDZUpdater", i had disabled "LG modems" from device manager.
Pls help me on this.

Can anyone please help me on this.
Sent from my TCL J636D+ using XDA Free mobile app

First one in!
Have you got a recovery? You could try holding down VolDown + Home + Power at the same time to boot to recovery. I think you have already tried that however. Try using a linux computer, plug it in and type into the terminal "lsusb". This can help because linux doesn't need drivers when win does. If you can find an entry saying something with "LG" "P500" "Android" she lives! Then you can try One Click Unbrick. I'm not an expert on unbricking, though, so don't quote me on these steps.
EDIT: found this tutorial: http://forum.xda-developers.com/showthread.php?t=1197111

I fear thatvm not seeing any p500 entry on Linux terminal with command "lsusb"
Sent from my TCL J636D+ using XDA Free mobile app