[Q] HELP me with my bricked HDX and adb seem l like dont regconize it - Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot

First, sory for my bad English
I'd tried to root my kindle but I make mistake with build.prop and now it's bricked
I'd tried almost methods in this forum but adb still dont regconize my kindle,so i cant do anything like " adb shell, adb root...." to fix it
Pls help me to fix my kindle

?
tuilakhang said:
First, sory for my bad English
I'd tried to root my kindle but I make mistake with build.prop and now it's bricked
I'd tried almost methods in this forum but adb still dont regconize my kindle,so i cant do anything like " adb shell, adb root...." to fix it
Pls help me to fix my kindle
Click to expand...
Click to collapse
Whatever you do do not do a factory reset and less you are about to drop it in the mailbox
http://forum.xda-developers.com/showthread.php?t=2781665. Post 66. And Have you read and tried last three pages here ? http://forum.xda-developers.com/showthread.php?t=2588608 and check read last three pages of http://forum.xda-developers.com/showthread.php?t=2782159 and include read OP on both thoroughly... If you have follow directions to T ..Too no avail .. Then there is probably no help to be had for you I apologize... That is without fastboot capabilities and an unlocked boot loader.

I'd read this and can't get it so well
My problem is adb don't regonize my device, and I can't do anything with adb command

jimyv said:
Whatever you do do not do a factory reset and less you are about to drop it in the mailbox
http://forum.xda-developers.com/showthread.php?t=2781665. Post 66. And Have you read and tried last three pages here ? http://forum.xda-developers.com/showthread.php?t=2588608 and check read last three pages of http://forum.xda-developers.com/showthread.php?t=2782159 and include read OP on both thoroughly... If you have follow directions to T ..Too no avail .. Then there is probably no help to be had for you I apologize... That is without fastboot capabilities and an unlocked boot loader.
Click to expand...
Click to collapse
I'd read this and can't get it so well
My problem is adb don't regonize my device, and I can't do anything with adb command

?
tuilakhang said:
I'd read this and can't get it so well
My problem is adb don't regonize my device, and I can't do anything with adb command
Click to expand...
Click to collapse
you followed all the directions on how to install sdk and uninstall old drivers ect http://forum.xda-developers.com/showthread.php?t=2588608 again the last 3 pages here are about installing the sdk to get it to see ....like I said before if you have done this and follow through and not just looked at it and thought it might not work then there's probably no help for you. Sorry folks if you don't understand and know how to use this info..there is hardly no help for you because currently there is not a 1 click solution...besides a call to amazon.....

You have the JDK & Android SDK installed? Occasionally I had issues connecting to adb when recreating previous bootloops & soft bricks. It seems that it gets hung up in a stat that Windows doesn't like. The only way I could get adb to function at these times was to run a Linux distro or on a Linux machine. You can download the wubi installer for dual booting Unbuntu, which is what 99% of people that have had issues have done to regain adb access. Linux just seems to play better with Android & the Android SDK tools, which really isn't surprising.

GSLEON3 said:
You have the JDK & Android SDK installed? Occasionally I had issues connecting to adb when recreating previous bootloops & soft bricks. It seems that it gets hung up in a stat that Windows doesn't like. The only way I could get adb to function at these times was to run a Linux distro or on a Linux machine. You can download the wubi installer for dual booting Unbuntu, which is what 99% of people that have had issues have done to regain adb access. Linux just seems to play better with Android & the Android SDK tools, which really isn't surprising.
Click to expand...
Click to collapse
I installed Ubuntu but when I open it, adb is not found, pls help me 2 use Ubuntu
Second, I just asked some friends have the old kindle verson, they say I should use Factory cable, will it work ????

tuilakhang said:
I installed Ubuntu but when I open it, adb is not found, pls help me 2 use Ubuntu
Second, I just asked some friends have the old kindle verson, they say I should use Factory cable, will it work ????
Click to expand...
Click to collapse
NO. This is not an OMAP device & it does NOT use uBoot, so factory cable is useless. Try a different USB port. Also, if you installed Linux, you still have to install the Java JDK & the Android SDK. There are some guides for setting up a build environment, which is pretty much what you need to do to really be able to use the tools in Windows or Linux. Taske a look here: Setting up a build environment in Unbuntu
You don't need Python or Gnu, nor the modules, but you must sdet up the JDK & the SDK & then set the paths.

tuilakhang said:
I installed Ubuntu but when I open it, adb is not found, pls help me 2 use Ubuntu
Second, I just asked some friends have the old kindle verson, they say I should use Factory cable, will it work ????
Click to expand...
Click to collapse
as I said maybe something will come through QPST
at least QPST detects Kindle HDX 8.9 (gray logo and then a black screen) with factory cable
I also lock the device after editing build.prop
but I lack the knowledge and skills to continue this way (in order not to kill the device)
thread(chinese) http://blog.csdn.net/syhost/article/details/20435957

amazonhdx said:
as I said maybe something will come through QPST
at least QPST detects Kindle HDX 8.9 (gray logo and then a black screen) with factory cable
I also lock the device after editing build.prop
but I lack the knowledge and skills to continue this way (in order not to kill the device)
thread(chinese) http://blog.csdn.net/syhost/article/details/20435957
Click to expand...
Click to collapse
Yeah, I don't read chinese & google doesn't do a very good job translating it, so, not gonna even try.
HOWEVER, I do know that you will need the Lab126 HSUSB driver. I don't remember if this was the one I used, but it was similarly named, I think this is for the BC radio stack diagnostic bulk mode originally & worked for the HDX. http://www.driverscape.com/download/lab126-hs-usb-diagnostics-0800-(com39)
Actually, I remember playing with this & thinking it could be useful for some of the early HDX issue I ran across too: http://forum.xda-developers.com/showthread.php?t=2582142

GSLEON3 said:
Yeah, I don't read chinese & google doesn't do a very good job translating it, so, not gonna even try.
HOWEVER, I do know that you will need the Lab126 HSUSB driver. I don't remember if this was the one I used, but it was similarly named, I think this is for the BC radio stack diagnostic bulk mode originally & worked for the HDX. http://www.driverscape.com/download/lab126-hs-usb-diagnostics-0800-(com39)
Actually, I remember playing with this & thinking it could be useful for some of the early HDX issue I ran across too: http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Ths 4 your guide and I will try with it and feed back tonight

stuck in same problem
my device still can't be recognized, still the same when it first bricked

GSLEON3 said:
Yeah, I don't read chinese & google doesn't do a very good job translating it, so, not gonna even try.
HOWEVER, I do know that you will need the Lab126 HSUSB driver. I don't remember if this was the one I used, but it was similarly named, I think this is for the BC radio stack diagnostic bulk mode originally & worked for the HDX. http://www.driverscape.com/download/lab126-hs-usb-diagnostics-0800-(com39)
Actually, I remember playing with this & thinking it could be useful for some of the early HDX issue I ran across too: http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
how can I download Lab126 HSUSB, I enter your link and download driver toolkit, but I can't see Lab126... and it's a paid license

tuilakhang said:
how can I download Lab126 HSUSB, I enter your link and download driver toolkit, but I can't see Lab126... and it's a paid license
Click to expand...
Click to collapse
You'll have to search around for it. Lab126 is the company that makes the HDX. That page only shows you the various driver names, the correct com port & identifies what device you want to see in device manager once you get QPST set up properly.

GSLEON3 said:
You'll have to search around for it. Lab126 is the company that makes the HDX. That page only shows you the various driver names, the correct com port & identifies what device you want to see in device manager once you get QPST set up properly.
Click to expand...
Click to collapse
I had google it and I can't find any lnk for this driver, can you give me this driver or link I can down

tuilakhang said:
I had google it and I can't find any lnk for this driver, can you give me this driver or link I can down
Click to expand...
Click to collapse
try it http://www.mediafire.com/download/xnjxkd49dn9d75j/QualcommDrv.zip
or it http://kindle-sdk.s3.amazonaws.com/2ba63011a73a0a0d0f35e001696677ec92a825cb.zip

amazonhdx said:
try it http://www.mediafire.com/download/xnjxkd49dn9d75j/QualcommDrv.zip
or it http://kindle-sdk.s3.amazonaws.com/2ba63011a73a0a0d0f35e001696677ec92a825cb.zip
Click to expand...
Click to collapse
ths 4 your sharing, but it's not work with me too, I has tried with 2 laptop and 3 or 4 cables, but it's not work too, don't have any signal when I connect it. I can't understand why I can't be

tuilakhang said:
ths 4 your sharing, but it's not work with me too, I has tried with 2 laptop and 3 or 4 cables, but it's not work too, don't have any signal when I connect it. I can't understand why I can't be
Click to expand...
Click to collapse
if kindle bricked (for example after a failure edit build.prop - gray logo and black screen), pc not detect device with standart microusb cable, driver can not be installed, adb not working.
but if use factory cable (buy or make), then the device connect as a usb bulk. you may install the first driver to it.
further steps to recovery does not exist yet

amazonhdx said:
if kindle bricked (for example after a failure edit build.prop - gray logo and black screen), pc not detect device with standart microusb cable, driver can not be installed, adb not working.
but if use factory cable (buy or make), then the device connect as a usb bulk. you may install the first driver to it.
further steps to recovery does not exist yet
Click to expand...
Click to collapse
So, What shoud I do to connect my kindle?

tuilakhang said:
So, What shoud I do to connect my kindle?
Click to expand...
Click to collapse
if kindle bricked (gray logo, thor not installed), just wait until a way to recover

Related

Pantech Burst Love Thread Consolidated

All Further updates will be handled in this other thread
Pre Req:
1) Make sure to install Pantech PC Suite as it will install the correct drivers you WILL need
2) Install ADB and Fastboot
How to gain Root
jcase said:
and here is root, you need fastboot and adb
androidpolice.com/2012/04/09/pantech-burst-rooted-and-the-process-is-stupid-easy/
IOMonster saved the day here, without him you would have to wipe your phone and install modified leaked firmware to get root.
Very glad we decided to not release the initial root, sorry
If IOMonster wants to explain he can, I would prefer not to however.
Details
goo.im/devs/jcase/prestoroot.img
adb reboot bootloader
fastboot boot prestoroot.img
once phone boots, reboot it again, install superuser from the market
Click to expand...
Click to collapse
How to Install Clockwork Recovery
Originally Posted by attn1
tau.shadowchild.nl/files/cwm-5.0.2.7-presto.img.zip
unzip
adb reboot bootloader
fastboot flash recovery cwm-5.0.2.7-presto.img
fastboot reboot
Click to expand...
Click to collapse
Press Volume Down and Power when booting to get into recovery
I have no come up with any of this information. I just gathered from the previous post to make it easier to search. I will try and keep this updated that way we can have a quick reference post at the beginning of the thread
Saved for future use
***Will have a Links section once this gets established***
Using adb with Ubuntu Linux - forum.xda-developers.com/showpost.php?p=28041279&postcount=641
Step by Step Root Guide - androidpolice.com/2012/04/09/pantech-burst-rooted-and-the-process-is-stupid-easy/
***Special Thank you goes to:***
jcase
Attn1
IOMonster
bulletproof1013
903tex
jackattack79
sandix
mr72
and everyone I didn't get *will update as we go*
from marcusmarcus
marcusmarcus said:
Here is what I did to get root on mine, maybe it will clear up things for others.
*Note, I am on 64bit Windows so folders will be different on 32bit windows.
On phone:
go to settings > Applications > Development > turn on USB Debugging
On Computer:
1-Download and install Pantech PC Suite from c724062.r62.cf2.rackcdn.com/PantechPCSuite_1.0.10.3314.exe
2-Launch Pantech PC Suite and update if it asks. When PC Suite is fully updated, plug phone into computer until device is recognized.
3-Download and install Android SDK from developer.android.com/sdk/index.html
4-Start SDK Manager and check the box next to “Android SDK Platform-tools” and install package.
5-Download prestoroot.img from dl.dropbox.com/u/9772722/XDA%20Forums/prestoroot.img and save it to “C:\Program Files (x86)\Android\android-sdk\platform-tools”
6-Download cwm-5.0.2.7-presto.img from tau.shadowchild.nl/files/cwm-5.0.2.7-presto.img.zip and save it to “C:\Program Files (x86)\Android\android-sdk\platform-tools” as well
7-Now open your command line and navigate it to “C:\Program Files (x86)\Android\android-sdk\platform-tools” folder
Run the following command
Code:
adb reboot bootloader
When the bootloader screen shows up on your phone then wait a few seconds to make sure your phone is recognized by the computer then run the following command
Code:
fastboot boot prestoroot.img
After phone reboots itself, shut the phone down and turn it back on again.
Then run the following command
Code:
adb reboot bootloader
When the bootloader screen shows up again then type the following commands
Code:
fastboot flash recovery cwm-5.0.2.7-presto.img
fastboot reboot
8-When the phone boots up this time, download the play.google.com/store/apps/details?id=com.noshufou.android.su superuser app[/URL] from Google Play
---------- Post added at 09:10 PM ---------- Previous post was at 09:06 PM ----------
FYI,
I've tried uot.dakra.lt UOT Kitchen couple times so far and have been ale to change the font of the device and the color of the glow for overscrolling but my time and other icons up in the status bar disappeared (the "AT&T" still shows up there though). The Backup and Restore in CWM does work nicely though to get me back to before I installed the zip from UOT Kitchen. I'll try 1 mod at a time using UOT kitchen and see which is making the icons and time disappear from my status bar.
EDIT: I did notice one issue with CWM backups. The backup I did today saved the folder name as "1970-02-22.03.14.56". Some reason the date is wrong in the file naming, should have started with "2012-04-13", right?
Click to expand...
Click to collapse
I hope this helps
For those having trouble with a missing driver I followed the below instructions and installed PDAnet (I did so while in fastboot mode so I could see the drivers install) as soon as it installed and the drivers showed installed. I went back and uninstalled pdanet (leaving the needed drivers behind)
hawkwind212 said:
I solved my problem by referencing to part II of the following page:
theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/Describe
Be sure to download two programs PDANet and USBView (which you may not really need but it's a nice little program).
It's suppose to be "stupid easy" to root PANETCH Burst, but who ever said that left out that it's not so easy if you don't have all the proper driver on your computer. Anyway, so soon after the fastboot mode is brought up, you should notice the computer is telling you a new hardware is found. This is when the burst switches from PANTECH's ADB driver to something else, and only way for the command "fastboot boot prestoroot.img" to work is to find the proper driver for the new hardware call "Android" in the device manager. Now you want to install PDANet, and as soon as the installation process begin, it'll find the driver for the device "Android." and install the driver for you. Once the driver is installed, the installation process will tried to install whole bunch other things into your phone, but I really don't think it can install them in fastboot mode, so you'll probably want to terminate the process. Now type command "fastboot devices" and you should see some kind of output telling you that it's recognize the "Android" device. Now, and only now you can follow the rest of "stupid easy" rooting instruction.
Click to expand...
Click to collapse
Spoiler Alert: Noob question.
Does this method unlocks the phone SIM also?? If not, there is a method to do it??
Thank you
tremeree said:
Spoiler Alert: Noob question.
Does this method unlocks the phone SIM also?? If not, there is a method to do it??
Thank you
Click to expand...
Click to collapse
This method doesnt but sim unlock is currently also being worked on.
Is there a Mac version of any of this software?
Is there a Mac version of any of this software. I understand all of this started on a PC but does that mean Mac users are forever out in the cold ? I own a Pantech Burst and a MacBook Air. I don't have access to a PC nor will I in the future, in so far as being able to use any of the software referenced here.
Any suggestions?
tfranzman said:
Is there a Mac version of any of this software. I understand all of this started on a PC but does that mean Mac users are forever out in the cold ? I own a Pantech Burst and a MacBook Air. I don't have access to a PC nor will I in the future, in so far as being able to use any of the software referenced here.
Any suggestions?
Click to expand...
Click to collapse
What software? Root..?
Cwm?...drivers? Carrier unlock for another provider? Pdl? I'm confused on what your asking...
Sent from my PantechP9070 using xda premium
bulletproof1013 said:
What software? Root..?
Cwm?...drivers? Carrier unlock for another provider? Pdl? I'm confused on what your asking...
Click to expand...
Click to collapse
I think tfranzman is referring to Pantech PC Suite and Android SDK. The Android SDK I believe has a Mac version but I do not think the Pantech PC Suite has a Mac version.
<QUOTE>Download software installed on PC : Click Here
Download MyPhoneExplorer Client App which software installed on Pantech Burst/ Breakout. You must find this from android market or you can read my previous post to get this : Click here
Connect your Pantech Burst/ Breakout device using your USB Cable Data
Please restart your phone and your Computer
After restarting finished, Now launch the installed MyPhoneExplorer Client app on your Pantech Burst/ Breakout and click on OK or Enable and it will connect to the PC Automatically,
Note :
If connection doesnt start or error you can choose another Sync software like Android Sync Manager WiFi.
If you are want Pantech Burst/ Breakout to connect on Mac OS X please follow my previous post : iSync for Mac OS X . I hope you are enjoy with this software.If any problem for downloading ,please contact me anytime</QUOTE>
I don't have a mac so I haven't tested this but this is what I found with google
Any news on CM7/9?? Im already rooted and im just playing around with UOT Kitchen
Let me know, thanks
No news as of yet. there have been people stating they are working on this but we haven't recieved any updates in awhile that I know of atleast. Anyone else reading this please feel free to correct me
All Further updates will be handled in this other thread
tfranzman said:
Is there a Mac version of any of this software. I understand all of this started on a PC but does that mean Mac users are forever out in the cold ? I own a Pantech Burst and a MacBook Air. I don't have access to a PC nor will I in the future, in so far as being able to use any of the software referenced here.
Any suggestions?
Click to expand...
Click to collapse
There is only Windows version of Pantech PC suite. proof
Finn81 said:
There is only Windows version of Pantech PC suite. proof
Click to expand...
Click to collapse
they were asking if any of the software we are using would work on a mac. the answer is yes depending on what software you are refering too. the pantech suite (which has been useless to me with the exception it installed the drivers for me) is windows only. I had actually gotten the drivers originally at work by using pda net. The information I gave above is what I came up with after a quick google search. I'm not sure if that or pdanet for mac would have those drivers.
and again this thread has ended. please follow the links in my Signature (Burst love for discussion or burst essentials for rooting information
I keep tring to root this phone but phone gets stuck in the fastboot mode and does nothing what can i do for this?
sounds like you don't have the fastboot driver installed. all futher questions should be pointed to http://forum.xda-developers.com/showthread.php?p=32885146
kagedws6 said:
sounds like you don't have the fastboot driver installed. all futher questions should be pointed to http://forum.xda-developers.com/showthread.php?p=32885146
Click to expand...
Click to collapse
Can you point me to the right place to get the fastboot driver's please
mobgod said:
Can you point me to the right place to get the fastboot driver's please
Click to expand...
Click to collapse
kagedws6 said:
all futher questions should be pointed to http://forum.xda-developers.com/showthread.php?p=32885146
Click to expand...
Click to collapse
install PDAnet on your computer. it will install the drivers

[Q] Impossible Rooting Polaroid PSPR355

Hello XDA community, this is my first thread, i had never needed to post anything cause i always find everything im searching for in this awesome community... until now :crying:
Last week I got a new android device which is made by Polaroid, model: PSPR355, its a pretty low class device but I thought it would be enough for me.... then i realize I needed root permissions, for obvious reasons... easy I thought... i had rooted many devices...how hard can it be...right?... WRONG! :crying: . The first problem I encountered were the drivers..couldnt find em anywhere... fortunatelly i found a tutorial were i could install the drivers in a different way...although I took 2 days to do this...Ive been about 5 days trying to root my phone.... Ive tryied about 10 different programs with their different versions... and any of those rooted my phone, nor Oneclikroot, nor Unlockroot, etc, etc..... I really gave up trying to find something on the web cause i didnt even find the phone on its official site, so I came her defeated asking for any solution, idea, or if you want to help me with commands, a programm or anything else to root my phone, Im not even afraid of trying programming (Im trying to learn how to make roms, kernels, etc for this phone cause theres nothing on the web abou it but this is a theme for another time) if you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
MecaMarck said:
If you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
Click to expand...
Click to collapse
I would recommend trying the towelroot application. It can be downloaded from here, just click on the orange lambda to download the tr.apk file. Then open towelroot follow the instructions in the application. After the device reboots I would recommend downloading, Root Checker Basic form the Play Store and running that to make sure your device is rooted. Finally install SuperSU, and you should be good to go.
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
MecaMarck said:
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
Click to expand...
Click to collapse
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
shimp208 said:
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
Click to expand...
Click to collapse
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
MecaMarck said:
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
Click to expand...
Click to collapse
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
shimp208 said:
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
Click to expand...
Click to collapse
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
MecaMarck said:
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
Click to expand...
Click to collapse
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Interesting for me.,.
Sent from my LT26w using xda premium
Same Boat
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
klonic0 said:
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
Click to expand...
Click to collapse
Unfortunately if fastboot doesn't show your device without any other flashing utility, even with the system dump there is no way to flash a rooted system image if it was created.
Got to see if this guys do the trick!
http://forum.xda-developers.com/showthread.php?t=2066041
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
MecaMarck said:
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
Click to expand...
Click to collapse
Since your computer recognizes the device and installed the driver and shows the device when in fastboot mode that's a good sign. The Android with the exclamation point is part of normal stock Android system recovery, it just means that the recovery menu has been hidden (You should be able to get the menu to appear by pressing the power and both the volume buttons in recovery mode). To dump /system run the following command:
Code:
adb pull /system
Then please send me a link to the /system dump, from there I will make a rooted system image.
Factory Rooted??
Hey guys I'm new to this so I may be wrong but has anybody thought to check if the Polaroid PSPR355 comes Factory Rooted??? I had a Polaroid Tablet, PID something(I forget the name), which I tried for hours to root resulting in: bootloop, hard reset, root, bootloop, hard reset, root, bootloop, hard reset, about to give up. So I Googled how to root Polaroid PID something (again, I forget the name), and I come to a post somewhere(forgot that too) that tells me my Tablet and similar Polaroid electronic devices(as well as most electronic devices coming from China) are factory rooted due to some Chinese law. So after the last hard reset, I downloaded HowToRoot App to check if my Polaroid Tablet is, in fact, rooted. I press the little lock button(root checker) and I find that, to my surprise, my Polaroid Table is in fact rooted. So all I had to do was download SuperSU from Google Play Store and Update Binary when prompted and I was Super User. Don't know if this helps but it worked for me.

How do I use a chromebook so I can flash a rom onto a samsung phone

Recently, actually the day after getting a phone, it broke, somehow, while using king root, and I need to fix it quick as possible. Is it possible to flash a new rom onto a phone using the chromebook I have. I need to know quick before I get in trouble.:crying:
H4ck3rz said:
Recently, actually the day after getting a phone, it broke, somehow, while using king root, and I need to fix it quick as possible. Is it possible to flash a new rom onto a phone using the chromebook I have. I need to know quick before I get in trouble.:crying:
Click to expand...
Click to collapse
Hello H4ck3rz,
I have recently purchased a Samsung Chromebook Plus and I also recently got a Nexus 6. I have been looking into how to use fastboot in order to root and rom my Nexus. I have found some promising info on the subject:
I first found this XDA Article that gives more of an overview on enabling ADB and Fastboot on Chrome OS
https://www.xda-developers.com/guide-to-enable-adb-and-fastboot-on-chromeos/
That article refers to an actual XDA guide (tutorial thread) at the very end:
https://forum.xda-developers.com/showthread.php?p=38232908#post38232908
I've read through them both and they seem pretty straight forward. It helps to have a bit of command line knowledge, but the commands used are clear in the instructions.
There is a section in the tutorial that links back to the Chromium Project site where you'll have to find your specific device to learn how to get into developer mode (assuming you don't already know).
NOTE: I have not tried this yet, but I am 100% sure I am going to at some point soon. Probably some time this weekend. After I go through it, I will post again to let you know how it went, if you want to wait to hear about results before you try it.
Hope this helps.
Rk.
Update: I decided I to work on this last night and from the beginning I had problems. TL;DR - adb and fastboot are already part of the developer mode system on my Chromebook Plus. So the need to follow those guides isn't necessary for me.
I was not, however, able to do anything to my Nexus 6 from my Chromebook. Since the Plus only has USB Type-C ports, I bought a USB Type-C to Micro USB cord, but the Nexus wasn't being recognized properly. adb devices returned "????????????" devices, and I didn't get anything with fastboot. I can only surmise that it is the cord, because on my windows laptop, adb and fastboot work flawlessly while my Nexus 6 was connected with the included sync cable.
I'll post again if have more info to share. Sorry I couldn't be of more help.
Rk
rkwarner2 said:
Hello H4ck3rz,
I have recently purchased a Samsung Chromebook Plus and I also recently got a Nexus 6. I have been looking into how to use fastboot in order to root and rom my Nexus. I have found some promising info on the subject:
I first found this XDA Article that gives more of an overview on enabling ADB and Fastboot on Chrome OS
https://www.xda-developers.com/guide-to-enable-adb-and-fastboot-on-chromeos/
That article refers to an actual XDA guide (tutorial thread) at the very end:
https://forum.xda-developers.com/showthread.php?p=38232908#post38232908
I've read through them both and they seem pretty straight forward. It helps to have a bit of command line knowledge, but the commands used are clear in the instructions.
There is a section in the tutorial that links back to the Chromium Project site where you'll have to find your specific device to learn how to get into developer mode (assuming you don't already know).
NOTE: I have not tried this yet, but I am 100% sure I am going to at some point soon. Probably some time this weekend. After I go through it, I will post again to let you know how it went, if you want to wait to hear about results before you try it.
Hope this helps.
Rk.
Click to expand...
Click to collapse
Thanks for this! I can't find my windows laptop and all I have to use now is a Chromebook that does not have adb or fastboot installed. I followed the links and tutorials you shared and was able to install chroot (linux), install adb and fastboot on that linux, and then finally use it to load my phone into fastboot and flash TWRP on my nexus 5. You saved me so much trouble!
i3uu said:
Thanks for this! I can't find my windows laptop and all I have to use now is a Chromebook that does not have adb or fastboot installed. I followed the links and tutorials you shared and was able to install chroot (linux), install adb and fastboot on that linux, and then finally use it to load my phone into fastboot and flash TWRP on my nexus 5. You saved me so much trouble!
Click to expand...
Click to collapse
can you please help me. when I enter 'sudo adb devices' the device is seen. but it says unauthorized. Can you help me with a a step by step write up. I want to flash Android P on to my Pixel 2 XL.
Thanks

Stuck on [ fastboot ].

Please help, Kindle HDX 8.9 (3rd Generation).
Kindle is stuck on fastboot
@draxie it seemed like you know a lot about the kindle fire hdx model,
from a completely noobish point of knowing absolutely nothing about adb, sideloading, twrp any of that
I had attempted to use flashify to uh, boot a ubuntu.img
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
https://dl.xda-developers.com/thumbs/3/7/9/9/0/7/2/3799072.jpg
above image copied from another thread, showing the image that is displayed on my kindle when I try to turn it on now.
I called into Amazon tech support.
But, that didn't work. they suggested leaving the tablet on the charger for a good 1 hour then called me back, still on the same screen.
Before I was going to attempt restore to factory defaults, I wanted check back here to see if I could get some help before I decide to wipe it.
If I could get some step by step instructions on how to fix it I would greatly appreciate it!
Please help, thanks in advance.
Really desperate here.. :/
Whats happens when you connect the tablet on a PC? First of all , you need check if you can get ADB Conectivity, using Minimal ADB and Fastboot, before that, install Kindle Fire Drivers
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
After driver installation, download ADB and read how it works (super easy if you pay atention) to check if possible recover your tablet using some comands , read about that and wait for Draxie reponse or Davey126 to get correct instructions.
Here's a case similar to you (stuck in Fastboot) but dont take it as solution, becasue every single brick isnt the same, and you could need other method
https://forum.xda-developers.com/ki...stuck-fastboot-kidnle-hdx-8-9-apollo-t3667492
Yousucks2 said:
Whats happens when you connect the tablet on a PC? First of all , you need check if you can get ADB Conectivity, using Minimal ADB and Fastboot, before that, install Kindle Fire Drivers
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
After driver installation, download ADB and read how it works (super easy if you pay atention) to check if possible recover your tablet using some comands , read about that and wait for Draxie reponse or Davey126 to get correct instructions.
Here's a case similar to you (stuck in Fastboot) but dont take it as solution, becasue every single brick isnt the same, and you could need other method
https://forum.xda-developers.com/ki...stuck-fastboot-kidnle-hdx-8-9-apollo-t3667492
Click to expand...
Click to collapse
You are in a world of hurt. It's possible (likely) the device can be recovered but not without considerable effort and (probably) many failed attempts. Such assistance is beyond what can reasonably be provided via the forums. You can browse through HDX threads to get the gist of what needs to happen. If you are a technology/Android noob it will probably be easier to pick up a refurb at an auction site. Good luck.
PM for support is normally ignored
joltpodcast03 said:
Please help, Kindle HDX 8.9 (3rd Generation).
Kindle is stuck on fastboot
@draxie it seemed like you know a lot about the kindle fire hdx model,
from a completely noobish point of knowing absolutely nothing about adb, sideloading, twrp any of that
I had attempted to use flashify to uh, boot a ubuntu.img
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
https://dl.xda-developers.com/thumbs/3/7/9/9/0/7/2/3799072.jpg
above image copied from another thread, showing the image that is displayed on my kindle when I try to turn it on now.
I called into Amazon tech support.
But, that didn't work. they suggested leaving the tablet on the charger for a good 1 hour then called me back, still on the same screen.
Before I was going to attempt restore to factory defaults, I wanted check back here to see if I could get some help before I decide to wipe it.
If I could get some step by step instructions on how to fix it I would greatly appreciate it!
Please help, thanks in advance.
Click to expand...
Click to collapse
If you have fastboot working, your device should be recoverable.
The steps to take depend largely on your definition of "fix it"...
What host platform (i.e. Windows, MacOS, Linux) and variant
are you using BTW? Can you communicate with the device
using the fastboot command?
draxie said:
If you have fastboot working, your device should be recoverable.
The steps to take depend largely on your definition of "fix it"...
What host platform (i.e. Windows, MacOS, Linux) and variant
are you using BTW? Can you communicate with the device
using the fastboot command?
Click to expand...
Click to collapse
If it's fixable, it's worth fixing for me.
 @draxie I have a Mac OS for a computer, I'm able to hook up a virtual machine if I need Linux. (Thanks again for the timely response to).
If I plug my machine into my computer and attempt to access its storage with the android tool that it mentions when you plug it in. I was able to access its storage before this happened, (factory provided cable), (just talking about accessing downloads).
It's bricked!?
How do I use fast boot commands?
And don't I need to make a special cord for it?
I have tons of micro USB to USB cords laying around to.
Do your homework...
joltpodcast03 said:
If it's fixable, it's worth fixing for me.
@draxie I have a Mac OS for a computer, I'm able to hook up a virtual machine if I need Linux. (Thanks again for the timely response to).
If I plug my machine into my computer and attempt to access its storage with the android tool that it mentions when you plug it in. I was able to access its storage before this happened, (factory provided cable), (just talking about accessing downloads).
It's bricked!?
How do I use fast boot commands?
And don't I need to make a special cord for it?
I have tons of micro USB to USB cords laying around to.
Click to expand...
Click to collapse
As I said, if fastboot works, it's fixable (in other words, it's not a brick).
BUT, you'll have to find one of the million guides on how to setup and
use fastboot all by yourself. That's not something I'm willing to spend
time on. Sorry...
As for cables, unless the device is a soft-brick, you don't need a special
cable, but it's preferable to use your factory cable not random junk.
BUT, seeing that you have MacOS, my 1-Click tool _should_ work for you.
Then, all you need to do is click through a web-UI. If you want to do that
instead, you'll have to wait though, because I need to iron out a wrink or
two, and haven't had the time the last week or so...
Do you have the drivers installed ? Its the first step, you need it because ADB program needs recognize a device to work , without that, its useless
Before continue, i reccomend you use windows , the tools provided to get ADB and Unlock bootloader, are simplier for beginners, with linux you need some commands input skills
Second = Install ADB from the link i posted or search it on google "ADB And Minimal Fastboot" dont take more than a seconds
And read please, without your cooperation, i think no one have the time and patience to guide you on a step by step instructions (assuming youre on a tech forum and you need a minimun knowledge before ask/do something)
If you get ADB Connection :aka conect your tablet to your PC using USB Cable ,run ADB (prefer as admin) and this show some device connected (you dont need put some command to get connection)
From my ignorance (Fortunately i do two succesfull bootloader unlocks without brick my devices) i think you screwed the original boot, thats why your tablet starts directly to fastboot mode, if you can get ADB connection, its possible unlock it or reapair, but again, you need know how to input the codes, come back when you post the results about ADB State and read abouthow works ADB before proceed to help you
Yousucks2 said:
Do you have the drivers installed ? Its the first step, you need it because ADB program needs recognize a device to work , without that, its useless
Before continue, i reccomend you use windows , the tools provided to get ADB and Unlock bootloader, are simplier for beginners, with linux you need some commands input skills
Second = Install ADB from the link i posted or search it on google "ADB And Minimal Fastboot" dont take more than a seconds
And read please, without your cooperation, i think no one have the time and patience to guide you on a step by step instructions (assuming youre on a tech forum and you need a minimun knowledge before ask/do something)
If you get ADB Connection :aka conect your tablet to your PC using USB Cable ,run ADB (prefer as admin) and this show some device connected (you dont need put some command to get connection)
From my ignorance (Fortunately i do two succesfull bootloader unlocks without brick my devices) i think you screwed the original boot, thats why your tablet starts directly to fastboot mode, if you can get ADB connection, its possible unlock it or reapair, but again, you need know how to input the codes, come back when you post the results about ADB State and read abouthow works ADB before proceed to help you
Click to expand...
Click to collapse
Technically not ADB if working in fastboot but guidance is still 100% relevant.
fastboot commands?

Soft Brick Kindle Fire HDX 7 - 4.5.5.3

Hello everyone,
I've been tinkering with my kindle attempting to flash TWRP so I could flash other ROMs on my Kindle Fire HDX 7 (3rd generation) but I have seemed to soft brick the device after using unlock.bat from https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982/post70881555#post70881555
The unlock.bat was supposed to unlock my bootloader, but now the device won't power on. If I plug it into the windows a bunch of partitions appear and windows prompts me if I want to format the various drives. If I plug my kindle into Linux, the 7 (i think) partitions show folders various different system functions.
Someone wrote in a separate forum that it's possible to restore kindle if I using something called eMMC Raw tool, but didn't really give any clear instructions.
If anyone could help me recover my device, that would be greatly appreciated. Thank you.
For some reason I can't upload a picture of the various files in the partition.
Side note: could I theoretically put CM 12 or anything else on one of the partitions instead of the stock ROM?
Praxxer1 said:
Hello everyone,
I've been tinkering with my kindle attempting to flash TWRP so I could flash other ROMs on my Kindle Fire HDX 7 (3rd generation) but I have seemed to soft brick the device after using unlock.bat from https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555
The unlock.bat was supposed to unlock my bootloader, but now the device won't power on. If I plug it into the windows a bunch of partitions appear and windows prompts me if I want to format the various drives. If I plug my kindle into Linux, the 7 (i think) partitions show folders various different system functions.
Someone wrote in a separate forum that it's possible to restore kindle if I using something called eMMC Raw tool, but didn't really give any clear instructions.
If anyone could help me recover my device, that would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
Unlock.bat did not "soft brick" your device as the actions it performs are totally benign. More likely you got sloppy and flashed an incompatible aboot (via dd) or erased aboot and don't know how to recover. Me thinks it is the latter. Keep reading; you'll eventually stumble on posts that describe corrective actions. I will edit this post with a link as time permits.
You do not need "eMMC Raw Tool" whatever that is.
edit: https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Davey126 said:
Unlock.bat did not "soft brick" your device as the actions it performs are totally benign. More likely you got sloppy and flashed an incompatible aboot (via dd) or erased aboot and don't know how to recover. Me thinks it is the latter. Keep reading; you'll eventually stumble on posts that describe corrective actions. I will edit this post with a link as time permits.
You do not need "eMMC Raw Tool" whatever that is.
edit: https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Click to expand...
Click to collapse
Ah. I wish I had seen that thread before I started the process! You may be right about the compatible boot. I couldn't find the original aboot_vuln.mbn file mentioned in the thread I was following, but managed to find aboot.img file and flashed that hoping it was the same. I could have sworn though, that the device stopped working the second after I clicked the unlock.bat file (executed outside the fastboot screen), but could be wrong.
Only problem about the thread you linked, device isn't responding to any ADB or fastboot commands, but still shows that my PC recognizes the device as a fire device.
Thank you for your time, I'll keep reading through the thread you linked.
Praxxer1 said:
Only problem about the thread you linked, device isn't responding to any ADB or fastboot commands, but still shows that my PC recognizes the device as a fire device.
Click to expand...
Click to collapse
Likely a Windows driver issue. Suggest installing Motorola Device Manager here which includes composite USB drivers that work reliably with HDX devices. Need need to run MDM; just install it. After connecting the device you will need update the driver via Windows Device Manager. Bit of hit and miss with a non-functioning device. Cables and USB ports also play a huge role, especially with fussy bootloader/fastboot communications. Avoid external hubs, USB3 ports and add-on expansion cards. Change cables, ports, etc. Good luck.
Davey126 said:
Likely a Windows driver issue. Suggest installing Motorola Device Manager here which includes composite USB drivers that work reliably with HDX devices. Need need to run MDM; just install it. After connecting the device you will need update the driver via Windows Device Manager. Bit of hit and miss with a non-functioning device. Cables and USB ports also play a huge role, especially with fussy bootloader/fastboot communications. Avoid external hubs, USB3 ports and add-on expansion cards. Change cables, ports, etc. Good luck.
Click to expand...
Click to collapse
Thanks Davey, I'll definitely give it a try. Just as a bit more information on my situation, the device manager on windows does read Fire Device "ADB composite driver". I also have it connected to the PC using a Fastboot Cable. I will give all of this a try when I get home from work today.
If I am able to communicate with the device after installing the MDM drivers, should I attempt to restore the device? Or try to unlock and flash the stock ROM?
Praxxer1 said:
Thanks Davey, I'll definitely give it a try. Just as a bit more information on my situation, the device manager on windows does read Fire Device "ADB composite driver". I also have it connected to the PC using a Fastboot Cable. I will give all of this a try when I get home from work today.
If I am able to communicate with the device after installing the MDM drivers, should I attempt to restore the device? Or try to unlock and flash the stock ROM?
Click to expand...
Click to collapse
- dump the fastboot cable (all but useless on a HDX); this isn't a generic Android device
- ADB composite drivers come in many flavors; HDX bootloader only likes a few of them
- if/when you reestablish communication first step is to restore aboot and install TWRP; unlocking and ROM installation come later
- do not attempt to reinstall stock; frustration and heartache consume those who do
- again, this is not a run-of-the-mill Android gizmo; many of the tricks you learned in kindergarden do not apply to Amazon tablets
Davey126 said:
- dump the fastboot cable (all but useless on a HDX); this isn't a generic Android device
- ADB composite drivers come in many flavors; HDX bootloader only likes a few of them
- if/when you reestablish communication first step is to restore aboot and install TWRP; unlocking and ROM installation come later
- do not attempt to reinstall stock; frustration and heartache consume those who do
- again, this is not a run-of-the-mill Android gizmo; many of the tricks you learned in kindergarden do not apply to Amazon tablets
Click to expand...
Click to collapse
Lol I feel like I'm in kindergarten tinkering with this HDX. How do I restore aboot? clearly the image I flashed with was not the correct bootloader. Should I attempt to extract aboot from the stock ROM? Or would you be able to share you tool set/point me to a working link for aboot, TWRP, and ROMs (I've looked at 4 threads so far without working links)?
UPDATE: I managed to install the ADB MOT Composite driver, but still no response to simple ADB and Fastboot commands
Thanks again
Praxxer1 said:
Lol I feel like I'm in kindergarten tinkering with this HDX. How do I restore aboot? clearly the image I flashed with was not the correct bootloader. Should I attempt to extract aboot from the stock ROM? Or would you be able to share you tool set/point me to a working link for aboot, TWRP, and ROMs (I've looked at 4 threads so far without working links)?
UPDATE: I managed to install the ADB MOT Composite driver, but still no response to simple ADB and Fastboot commands
Thanks again
Click to expand...
Click to collapse
Not uncommon. Unfortunately, there is no 'fix script' moving forward as each situation is unique. If aboot is too damaged to support basic communication it's pretty much game over for the average laymen. You will need to comb the threads for information nuggets that may apply to your situation. Or cut your losses and move on. I am not big on trying to unbrick these pups unless one well versed in low level trouble shooting. Lousy ROI; has to be a labor of love including copious time researching, trying and (likely) failing. Good luck.
@draxie - for awareness; read back a few posts for context.
1-Click is your friend
Davey126 said:
Not uncommon. Unfortunately, there is no 'fix script' moving forward as each situation is unique. If aboot is too damaged to support basic communication it's pretty much game over for the average laymen. You will need to comb the threads for information nuggets that may apply to your situation. Or cut your losses and move on. I am not big on trying to unbrick these pups unless one well versed in low level trouble shooting. Lousy ROI; has to be a labor of love including copious time researching, trying and (likely) failing. Good luck.
@draxie - for awareness; read back a few posts for context.
Click to expand...
Click to collapse
Right... the symptoms described are the normal state of affairs
after 'fastboot erase aboot' and 'unlock.bat' does no such thing.
The post linked above and/or my original "Bulk mode" post both
have the necessary instructions to recover. Alternatively, 1-Click
can handle this, assuming access to either MacOS or Linux (for
the time being).

Categories

Resources