I followed the very helpful post from bschrib to root my newly acquired Kindle Fire for setting up the full Android Market. After the following the first few steps and trying to do "adb devices" it doesn't show any devices though my Kindle is currently connected to my laptop. I did the "adb kill-server" as suggested but still unable to see any devices when I issue the "adb devices" command. Being a newbie I'm not allowed to post on the dev forum so hoping someone here can help me with this?
Thanks
Krish
Update - a good one at that
got it figured out. Let me know if anyone out there needs the detailed solution, i'll gladly give the details
Krish
i would love the work around for this! i'm having the same problem. i went through all the instructions to the letter and even tried a few things of my own to see if i could get it to show up, but it's still blank when i do the "adb devices" command.
krishmo said:
I followed the very helpful post from bschrib to root my newly acquired Kindle Fire for setting up the full Android Market. After the following the first few steps and trying to do "adb devices" it doesn't show any devices though my Kindle is currently connected to my laptop. I did the "adb kill-server" as suggested but still unable to see any devices when I issue the "adb devices" command. Being a newbie I'm not allowed to post on the dev forum so hoping someone here can help me with this?
Thanks
Krish
Update - a good one at that
got it figured out. Let me know if anyone out there needs the detailed solution, i'll gladly give the details
Krish
Click to expand...
Click to collapse
where do u buy from it n how much , i brought a resistive 10 inch screen since kindle fire was launched exactly one day after i ordered my tab in India
I know that this is about a month old, but i would LOVE to know how you got it working. i'm stuck at that exact spot >->
krishmo said:
I followed the very helpful post from bschrib to root my newly acquired Kindle Fire for setting up the full Android Market. After the following the first few steps and trying to do "adb devices" it doesn't show any devices though my Kindle is currently connected to my laptop. I did the "adb kill-server" as suggested but still unable to see any devices when I issue the "adb devices" command. Being a newbie I'm not allowed to post on the dev forum so hoping someone here can help me with this?
Thanks
Krish
Update - a good one at that
got it figured out. Let me know if anyone out there needs the detailed solution, i'll gladly give the details
Krish
Click to expand...
Click to collapse
Hi Krish, I've just got my kindle fire last too weeks. I have upgraded to 6.2.2. Today I decide to root it and ran into the exact same problem you had. Please help me giving me a detail instruction how to do this. Thanks a lot bro.
Related
Hey XDA'rs,
Ive been messing around with building roms and I finally got one to finish(Kindle Fire V1 btw). So I flashed it to the device and tried to boot.
What I get is the backlight to come on and never see the bootlogo. So its hanging. (Not why Im posting)
My question lies in ADB. I want to get a logcat of the device as it boots to see what the problem is.
The rom is 4.2.2 so I know theres the new security prompt to enable access for adb on the device, but does this prevent me from using adb until the device will complete its boot or is there a way to make it work?
All I can get now is for it to show "0123456789ABCDEF offline".
Ill appreciate any help!
Bump
Sn0w17 said:
Hey XDA'rs,
Ive been messing around with building roms and I finally got one to finish(Kindle Fire V1 btw). So I flashed it to the device and tried to boot.
What I get is the backlight to come on and never see the bootlogo. So its hanging. (Not why Im posting)
My question lies in ADB. I want to get a logcat of the device as it boots to see what the problem is.
The rom is 4.2.2 so I know theres the new security prompt to enable access for adb on the device, but does this prevent me from using adb until the device will complete its boot or is there a way to make it work?
All I can get now is for it to show "0123456789ABCDEF offline".
Ill appreciate any help!
Click to expand...
Click to collapse
just went through this this morning too.
short version... make sure you have the newer version of adb installed and running from that directory... replace you older versions.
4.2.2 needs adb.exe 1.0.31 and can be downloaded here for windows pc.
if you have/need Linux or mac versions they are in the index of the folder too here
.
.
Hi everyone my kindle hdx7 is bricked several day ago.
First my kindle is shown stuck on grey kindle fire logo connect normal data cable
So i decide connect factory cable however, my kindle is shown black screen.
Nothing any logo but my laptop recognized Qhsusb_bulk.
I read gssole and follow his step but my kindle still brick anyone solve this problem?
Hehelp.me plz
Hello
cjdfyd2 said:
Hi everyone my kindle hdx7 is bricked several day ago.
First my kindle is shown stuck on grey kindle fire logo connect normal data cable
So i decide connect factory cable however, my kindle is shown black screen.
Nothing any logo but my laptop recognized Qhsusb_bulk.
I read gssole and follow his step but my kindle still brick anyone solve this problem?
Hehelp.me plz
Click to expand...
Click to collapse
Hi
I have the same problem, and I am in exactly the same situation as you, having got the factory cable from Amazon just today. unlike the other kindles, it doesn't appear with the yellow triangle, but its a big step since your PC recognises the kindle. Now all you really need is a unbrick utlity, but I haven't found one yet, I'll write to you as soon as i sort something out with my kindle so you can do exact same thing on yours.
---------- Post added at 12:11 PM ---------- Previous post was at 12:01 PM ----------
http://forum.xda-developers.com/showthread.php?t=2553474
ferrouskid said:
Hi
I have the same problem, and I am in exactly the same situation as you, having got the factory cable from Amazon just today. unlike the other kindles, it doesn't appear with the yellow triangle, but its a big step since your PC recognises the kindle. Now all you really need is a unbrick utlity, but I haven't found one yet, I'll write to you as soon as i sort something out with my kindle so you can do exact same thing on yours.
---------- Post added at 12:11 PM ---------- Previous post was at 12:01 PM ----------
http://forum.xda-developers.com/showthread.php?t=2553474
Click to expand...
Click to collapse
Hello
Can you get fastboot ultility to recognise your kindle? If it can,you can do a factory reset, by putting in the following command.
"fastboot -w -i 0x1949".
This is thanks to r3pawn.
Lets hope we goet somewhere.
cjdfyd2 said:
Hi everyone my kindle hdx7 is bricked several day ago.
First my kindle is shown stuck on grey kindle fire logo connect normal data cable
So i decide connect factory cable however, my kindle is shown black screen.
Nothing any logo but my laptop recognized Qhsusb_bulk.
I read gssole and follow his step but my kindle still brick anyone solve this problem?
Hehelp.me plz
Click to expand...
Click to collapse
Hard to say anything since there is no magic fix. Fixes are based on what you broke & your post gives no indication of what you did when you "bricked" it. Until I know what you did, I can not tell you what may, or may not, work.
Similar situation
Although I had Safe Strap, SU and etc. installed on my rooted HDX 7", I panicked when my firewall failed to block the 13.3.2.1 update and cut the power off in mid update. Unfortunate reflex that led to a soft brick. Although I now can get into Fastboot no problem (I can't access the ADB commands though), I have tried to flash recoveries, boot images and so on. I can erase data (I'd call myself an expert at this part of the rooting process) and arrange file system layouts but then can't get past this error:
FAIL: flashing not allowed for locked hw.
Anyone know how to, maybe change permissions on the hardware or whatnot to get the device to let me write to the system partition? I'm flashing from a iMac btw.
I mean the Christmas colors of the text as far as what worked and what didn't are fun to look at, but the actual loading of the Kindle OS might provide more long term visual excitement. Thanks and love all y'all's insights into navigating the treacherous waters of root access and tweaking the twerkinator in these here twandroids.
----
EDIT: I can use the ./adb commands but I was having trouble before with the period-less version. Was still getting no device to show up when I query adb but got this through fastboot:
fastboot -i 0x1949 devices -l
(serial number) fast boot usb:FA130000
Redaction is mine ...
qhsusb_bulk
So...
My Kindle Fire HDX is in the same boat... Honestly, not sure what happened. I had rolled back to 3.2.8, installed Saftstrap, SU, thought that I had disabled the OTA update but only by renaming the file. I was rooted and flashed ggow's Nexus mod on the ROM SLOT 1 and left the stock alone. It was working fine, never tried to update anything that night. Was plugged in and connected and booted to the Nexus side. The next morning I was showing someone how I could switch to the Amazon side through Safestrap and still had no issues. I set the Kindle on my desk at work and looked over to see it at the Kindle Fire logo and below it a progress bar saying Installing System Update! What I don't understand is I had not connected to the WiFi at work. The Kindle was wiped out and did not have the WiFi passwords nor did I accept the WiFi policy when connecting.
I had a couple of file on the SD card that I had transferred via the USB cable on the SD portion of the Kindle. The nexus mod .zip file and a copy of the renamed OTA update file that I had changed the name and extension on. Did it somehow recognize the .zip nexus file as an update and try to load it?? I am lost...
I am able to plug it into the computer and was getting the qhsusb_bulk as the device type. I have tried to access that through adb but it doesn't find it.
Amazon was kind enough to offer me a refurbished kindle for $149. I said I can buy a new HD7 for $99!? So... I have just over a year old 64gb HDX staring at me... asking me why I messed with it. Good question...
If anyone has any advice or possible solution, that would be great!
Thanks
I think I know what was happening. The I am not sure the rename to block ota does work on 3.2.8. I know it is not supposed to be able to update at all, but obviously it seems like it can. Odd.
Sent from my KFTHWI using Tapatalk
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
I recently purchased an RCA Voyager III model RCT6973W43 and I've noticed no one has said anything about how to root this one yet. I've heard of users who have had success with rooting the original Voyager and Voyager IIs, but there's nothing on the Voyager III. I think it's possible that the same procedure for rooting those devices might work for the Voyager III, but I don't want to take any chances in case it bricks mine. So is there a whole different procedure with my particular device? Or is the Voyager III simply too new?
Bump
RobinHood16 said:
I recently purchased an RCA Voyager III model RCT6973W43 and I've noticed no one has said anything about how to root this one yet. I've heard of users who have had success with rooting the original Voyager and Voyager IIs, but there's nothing on the Voyager III. I think it's possible that the same procedure for rooting those devices might work for the Voyager III, but I don't want to take any chances in case it bricks mine. So is there a whole different procedure with my particular device? Or is the Voyager III simply too new?
Click to expand...
Click to collapse
Bump!
Yes please!
I tried RCA to see if they would at least update the tablet and turn on the FM receiver. They claim it doesn't have it. I'm pretty sure it has both the FM and a GPS receiver built in. I think I also found a "clone", the DigiLand DL721-RB appears to be the same hardware.
What I'm trying to do is simply enable all the features the hardware has. The Atom x3 is supposed to have pretty much all the standard stuff, my RCA RCT6973w43 (on sale at Walmart right now for $37) does OTG nicely, but if I had the FM also it would be perfect for a tablet based car stereo. If anyone figures it out and can get the FM and or GPS going, I'd be tickled.
I just bought a couple of these for 25 bucks. I would very much like to get them rooted. Any news on if the method for the other Rca's works?
No good. I attempted to root the Voyager III with One Click Root, and it told me it was unrootable for the time being.
Any clues yet?? everyone owns this tablet figured there'd be a root already for this one.
i read where someone tried to root the 43 using 42, and it bricked the tablet, so i'm reluctant to try it. don't know if the 42 and the 43 had the same processor, or what makes them so different it would cause that to happen. maybe we can get a bump.
keep finding tons of people looking for root, but not dice so far. i've only got one cuz they were sold out. actually bought the display model. wish i had more than one so i could experiment. 8(
I'd been able to install twrm halfway then it fails signature verification.
Just got one of these! Bump
yes bump!!!! I can't believe this hasn't been rooted yet. is it because it's an intel x86 architecture?? I'm guessing it would require someone to compile the code for sudo/su/root to run on it??
anything yet?? 8(
---------- Post added at 02:04 AM ---------- Previous post was at 01:39 AM ----------
just as a quick notei found this guys.
http://specdevice.com/showspec.php?id=7920-d3ef-0033-c5870033c587
it's an alco tablet with the same model # as the voyager 3 RCT6973W43.
weird thing is it appears to have a quadcore arm processor, and not an intel atom.
i heard there was a root for the alco from twitter profile @srsrOOT, but they haven't responded yet.
no clue if this will help at all. I would imagine if the alco has an arm proc, and the rca has an intel then we'd need a different su/sudo binary for the RCA because the RCA runs on a CISC processor, and the ARM is a RISC. hope there's some clues here. hit us back with any info you find. 8(
look here
bump
Thought Id try bumping this. Sorry itll prolly be gone soon.
This tablet is begging for a root. I did a bunch of adb uninstalling and got rid of google play stuff. Battery is MUCH better. I suppose a custom rom would immensely improve battery.
TimmyP said:
Thought Id try bumping this. Sorry itll prolly be gone soon.
This tablet is begging for a root. I did a bunch of adb uninstalling and got rid of google play stuff. Battery is MUCH better. I suppose a custom rom would immensely improve battery.
Click to expand...
Click to collapse
Did you guys unlock the boot loader yet?
Code:
adb reboot fastboot
fastboot flashing unlock
If so, you can try and boot the cwm recovery I use on mine(RTC6873W42) to get a root shell. (if the kernel drivers were the same it would actually be full recovery enviroment) And with that root shell you could pull your boot.img . The expected result of the fastboot boot command is an attempted boot to cwm recovery except the screen will be blank, and adb will give root shell access.
Code:
fastboot boot v31-test-rca-recovery-cwm-ramdisk-20170709-2052.img
https://www.androidfilehost.com/?fid=961840155545581102
And with the pulled boot.img you can make the recovery fully boot by swapping the kernel, then manually change some rc files in the ramdisk folder of the boot.img the allow it to be rooted.
When you get that far, and if you need help, just ask.
This doesn't work with an RCT6973W43, I'm afraid. I get the blank screen from "adb reboot fastboot", as is apparently expected, but while the RCT6973W43 is in this mode, Windows doesn't recognize the device at all, as there are no drivers available. Also, it keeps disconnecting and reconnecting, so that "fastboot flashing unlock" can't get a fix on the device -- it's stuck on "< waiting for any device >" forever, and can only be stopped with Ctrl-C. Otherwise, the only way to restore the device to working order is a hard restart.
RobinHood16 said:
This doesn't work with an RCT6973W43, I'm afraid. I get the blank screen from "adb reboot fastboot", as is apparently expected, but while the RCT6973W43 is in this mode, Windows doesn't recognize the device at all, as there are no drivers available. Also, it keeps disconnecting and reconnecting, so that "fastboot flashing unlock" can't get a fix on the device -- it's stuck on "< waiting for any device >" forever, and can only be stopped with Ctrl-C. Otherwise, the only way to restore the device to working order is a hard restart.
Click to expand...
Click to collapse
That connect disconnect is expected when Intel drivers for fastboot not installed. I will link you to my write up on how to install
https://raw.githubusercontent.com/m...ster/unlock_tool/manual root instructions.txt
Read the document and follow directions in the driver install section. If trouble let me know
Neither of these builds works for me. My build number is RCT6973W43-ANDROID6.0-V16-V1.18.0-M01. Also, even if I could find the correct files, the Intel drivers don't work with my device.
RobinHood16 said:
Neither of these builds works for me. My build number is RCT6973W43-ANDROID6.0-V16-V1.18.0-M01. Also, even if I could find the correct files, the Intel drivers don't work with my device.
Click to expand...
Click to collapse
Sorry this is giving you such trouble,
but if you cant get the drivers to work, then you hae no way to know if these files will not work on your device.
If you are refering to the "tools" then, yes they will not work, as I coded them to not work if build numbers are not matched. But I never suggested tring the "tools". just the unlock and "fastboot boot" steps
again , If you cant get windows drivers to install then , thats as far as you can go.
I had a pictoral 'guide' for doing it, but cant find it right now.
In that case, my only recourse is to give up. It seems to me that they have made this tablet absolutely unrootable.
i managed to unlock bootloader
i used the method here https://raw.githubusercontent.com/m...ster/unlock_tool/manual root instructions.txt to unlock boot loader only difference is the fastboot screen flashes just input unlock command and keep taping up it works dont really know where to go from here
seasonednovice said:
i used the method here https://raw.githubusercontent.com/m...ster/unlock_tool/manual root instructions.txt to unlock boot loader only difference is the fastboot screen flashes just input unlock command and keep taping up it works dont really know where to go from here
Click to expand...
Click to collapse
Did you attempt my directions at the end . To boot the modified cwm , to get adb root shell?
I'd like to start off by apologizing for having to waste somebody's time for something I can't find the answer to. I should preface this post by saying that I know nothing about ADB, but in the last couple of days I've done plenty of reading and to be quite honest the more research sometimes adds to the confusion with contrary and outdated information.
I'm basically trying to get TWRP onto my Mi Pad 4 LTE using ADB on my Windows 10 PC coming from the MIUI EU ROM Bootloader unlocked from the supplier. USB debugging enabled drivers installed etc
I had a lot of trouble until I came across this thread http://www.testedtechnology.co.uk/debloating-the-huawei-p30-pro/ because of an error I was getting in the Powershell window.
https://forum.xda-developers.com/attachment.php?attachmentid=4781060&stc=1&d=1561218064
So basically in short, thanks to the above thread I was able to get into fastboot mode having recognized the device using the precursor .\ as shown above, but one of my problems is I'm not sure if I should be use the .\ with all commands? My problem from here now that my device was in fastboot mode I didn't know how to direct it to the file. I just have no idea what commands to you use to find a particular directory to get to recovery-TWRP-3.3.0-0429-XIAOMI_PAD4(PLUS)-CN-wzsx150.
I'm really concerned about putting the device into bootloop as some of the problems I've seen seem almost insurmountable!
Anyway sorry again and TIA for anybody taking the time to help.
All sorted now thanks for all the help.