Title says it all... I tried using kingroot pc, I couldn't swap super su so I had to reboot. Some of the adb commands were not working so I tried buying super su me pro but that only said I don't have kingroot. I opened kingroots superuser app and it said I am not rooted. It had a fix now button I pressed which installed the kingo app. This worked to 90% where it froze.
Now I am stuck in the fire splash screen. I can get into recovery mode and tried factory resetting without success.
Is there a stock fire hd 10 rom out there? Any other ways out of this than requesting an Amazon return?
Sent from my SM-G930T using Tapatalk
stinkbud said:
Title says it all... I tried using kingroot pc, I couldn't swap super su so I had to reboot. Some of the adb commands were not working so I tried buying super su me pro but that only said I don't have kingroot. I opened kingroots superuser app and it said I am not rooted. It had a fix now button I pressed which installed the kingo app. This worked to 90% where it froze.
Now I am stuck in the fire splash screen. I can get into recovery mode and tried factory resetting without success.
Is there a stock fire hd 10 rom out there? Any other ways out of this than requesting an Amazon return?
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
I rooted my HD 10, removed apps and got stuck on the fire splash screen too. To restore it I downloaded the 5.6 update from Amazon's site then:
-Put the 5.6 file in the adb folder
-Put the HD 10 in recovery mode and select apply update with adb
-Connect HD 10 to PC
-In command prompt go to the adb folder then type adb sideload <filename>
Good luck
If you have a 2017 HD 10, download the update .bin from here and follow the steps posted by SeventhGen.
One thing to note is that there are two rooting applications with similar names: Kingoroot and Kingroot; the original post seems to treat them as the same thing. They are not the same. As far as I am aware (I stand to be corrected), GatesJunior's SuperSUMe Pro was developed to clean up after rooting with Kingroot and install SuperSU, it does not work for Kingoroot.
From what I can gather, it seems that after rooting the Fire HD 10 with Kingoroot and rebooting, you end up with a rooted tablet with Kingoroot's own superuser app installed. The rest of the process removes this superuser app and the Kingoroot-installed junk, and switches to SuperSU. Once you have root, open an ADB shell and grant it superuser privileges (type su and OK this, if asked, by the Kingoroot superuser app). Leave the ADB shell open, and use the Kingoroot PC app to unroot (this will remove the Kingo superuser app). You can use the ADB shell to clean up and install SuperSU as described in the thread quoted in the first post in this thread.
Writing this post (on an Amazon Fire 7) indicates that autocorrect is not helping distinguish between Kingroot and Kingoroot. It seems to not 'like' 'Kingoroot' - it keeps changing it to 'KingoRoot'. If I change back it then autocorrects to 'Kingroot'. I am having to fight it to make corrections!
The previous poster but one (SeventhGen) is correct. If the tablet is stuck at the 'fire' splash screen, it is not bricked. It should be possible to reinstall the software (ADB sideload) from recovery mode.
SeventhGen said:
I rooted my HD 10, removed apps and got stuck on the fire splash screen too. To restore it I downloaded the 5.6 update from Amazon's site then:
-Put the 5.6 file in the adb folder
-Put the HD 10 in recovery mode and select apply update with adb
-Connect HD 10 to PC
-In command prompt go to the adb folder then type adb sideload <filename>
Good luck
Click to expand...
Click to collapse
This worked. THanks so much!
stinkbud said:
This worked. THanks so much!
Click to expand...
Click to collapse
Cool, I'm glad it worked
Be careful when doing this.
Tablets update to 5.6.1.2, whereas the latest image on the Amazon site is 5.6.1.0, adb sideload this and you will perma-brick your tablet!
edikat said:
Be careful when doing this.
Tablets update to 5.6.1.2, whereas the latest image on the Amazon site is 5.6.1.0, adb sideload this and you will perma-brick your tablet!
Click to expand...
Click to collapse
Are you sure about this? Have Amazon included anti-rollback in this new version (5.6.1.2)?
I have also seen a report on an Amazon forum of someone's HD10 receiving an OTA update to 5.6.2.0. It will be interesting to see if these versions have anti-rollback, and are still rootable.
MontysEvilTwin said:
Are you sure about this? Have Amazon included anti-rollback in this new version (5.6.1.2)?
I have also seen a report on an Amazon forum of someone's HD10 receiving an OTA update to 5.6.2.0. It will be interesting to see if these versions have anti-rollback, and are still rootable.
Click to expand...
Click to collapse
On the HD 10, you could not downgrade if you are on 5.6.1.0. I would assume the same for the latest version.
I tried to downgrade from 5.6.2.0 to 5.6.1.0 because I was stuck with the show mode thing and could not use Nova launcher properly and, well, mine seems to be permanently bricked. After applying adb sideload, I selected rebooting menu and nothing. It does not turn on or show anything. I cannot even get into the recovery mode. I tried vol up + power, just power, vol dn + power, vol up + vol dn + power. Can anybody advise what I can do? other than selling it for repair?
livefree78 said:
I tried to downgrade from 5.6.2.0 to 5.6.1.0 because I was stuck with the show mode thing and could not use Nova launcher properly and, well, mine seems to be permanently bricked. After applying adb sideload, I selected rebooting menu and nothing. It does not turn on or show anything. I cannot even get into the recovery mode. I tried vol up + power, just power, vol dn + power, vol up + vol dn + power. Can anybody advise what I can do? other than selling it for repair?
Click to expand...
Click to collapse
same here... after trying to downgrade from latest version to prior version via adb comment, the device does not turn on or show anything..
It will be greatly appreciate if anyone can advise on how to repair this.. Thanks
yhuang168 said:
same here... after trying to downgrade from latest version to prior version via adb comment, the device does not turn on or show anything..
It will be greatly appreciate if anyone can advise on how to repair this.. Thanks
Click to expand...
Click to collapse
There is no known method of repair at this time.
yhuang168 said:
same here... after trying to downgrade from latest version to prior version via adb comment, the device does not turn on or show anything..
It will be greatly appreciate if anyone can advise on how to repair this.. Thanks
Click to expand...
Click to collapse
late post but i am suffering the same thing, tried to downgrade from 5.6.8.0 to 5.6.4.0, wish i knew sooner before i tried something like this
RjGunner111 said:
late post but i am suffering the same thing, tried to downgrade from 5.6.8.0 to 5.6.4.0, wish i knew sooner before i tried something like this
Click to expand...
Click to collapse
You're probably already in boot ROM mode in which case without the proper drivers installed and the device hooked up to a PC you probably won't know if it's turned on. The screen in fact might be on if the battery is charged but too dim for you to be able to tell even at a dark room. My suggestion would be to go over to this thread and try and recover using this method if possible: https://forum.xda-developers.com/t/...hd-10-2017-suez.3913639/page-68#post-84552275
Related
I rooted my Asus Transformer TF101-B1, but I can't get into Recovery. I know rooting was successful because I get the # prompt in ADB shell and can run root-only apps like Titanium Backup. I've tried every method for getting into CWM/Recovery that I've been able to turn up on XDA and Google, including:
* Running "adb reboot recovery"
* Holding Power + Vol down during boot, then pressing Vol up within 5 seconds of the device powering on.
* Selecting "reboot into recovery" from the ROM Manager app.
Nothing works, it just does a normal boot every time. I even did a factory reset to try and get into the stock recovery (a suggestion I found on another thread here), but that didn't work, either (and my device still appears to be rooted).
I'm hoping someone out there can provide more insight/advice, as I'm pretty well out of options.
Device info:
Android version: 3.0.1
Kernel: 2.6.36.3-00003-g8038d35, android 'at' Mercury #1
Build: HRI66.US_epad-8.2.3.9-20110423
(all stock)
ok, I managed to get into CWM and now my question is, "where can I get the latest version of CWM?" I've seen several posts that just say, "head over to the CWM thread and download the newest version", but they don't give links and I didn't find much searching the forums.
Sorry for being such a n00b...
Im also having a similar problem though my transformer wont do anything after i choose to boot into recovery.
kfarstrider said:
ok, I managed to get into CWM and now my question is, "where can I get the latest version of CWM?" I've seen several posts that just say, "head over to the CWM thread and download the newest version", but they don't give links and I didn't find much searching the forums.
Sorry for being such a n00b...
Click to expand...
Click to collapse
How did you get into recovery? No matter what I do it just boots normally. adb doesn't see the tablet anymore either..and I already rooted it so adb *was* working.
ferparedes said:
How did you get into recovery? No matter what I do it just boots normally. adb doesn't see the tablet anymore either..and I already rooted it so adb *was* working.
Click to expand...
Click to collapse
For real. I rooted succesfully. Currently trying to flash a rom, but I don't know how to get into CWM.
Same issue here. Can someone write how they got into CWM?
I used RazorClaw to root my Transformer, yet when I try to reboot into recovery, it gives me the Android with the Caution symbol in the middle. It looks like I cannot get into ClockWorkMod, either.
On www (dot) clockworkmod (dot) com, it does not list the Asus Transformer as being supported with a version of CWM. Rom Manager shows the same thing, so I am forced to select the Xoom or Nook Color.
What are the steps to get from Root to CWM Recovery?
Thanks!
Ok so I'm at the same part of the problem everyone else is in this thread.
I've done the following steps:
Installed Java SDK
Installed Andriod SDK
Rooted via Razorclaw
device is recognized when i do "adb devices" in command shell
install ROM Manager by Clockwork Mod from App store
tried to boot into recovery while connected to PC using Vol Down + Power Button and I get Android Man with Caution with nothing going further. if I unplug the cable from the PC I can't seem to get into Boot Recovery. I've asked for help in asus-transformer on Freenode.net with no help what so ever. From what I can tell my model is a B50
Any help would be appreciated from what I can peice together on the forums the install order would be
Root
CWM on App Market
CWM Recovery by roach
Nandriod
install ROM
Correct me if I'm wrong.
---------- Post added at 08:18 AM ---------- Previous post was at 07:49 AM ----------
Edit: Problem solved, I read somewhere that you needed to enable USB Debugging on the tablet which is correct. But you should not do it until the correct time I enabled it from the start which is wrong
jlscarpa said:
I used RazorClaw to root my Transformer, yet when I try to reboot into recovery, it gives me the Android with the Caution symbol in the middle. It looks like I cannot get into ClockWorkMod, either.
On www (dot) clockworkmod (dot) com, it does not list the Asus Transformer as being supported with a version of CWM. Rom Manager shows the same thing, so I am forced to select the Xoom or Nook Color.
What are the steps to get from Root to CWM Recovery?
Thanks!
Click to expand...
Click to collapse
Exactly what I get!
No Such Luck
[/COLOR]Edit: Problem solved, I read somewhere that you needed to enable USB Debugging on the tablet which is correct. But you should not do it until the correct time I enabled it from the start which is wrong[/QUOTE]
I don't get it. I've been having the same problem as you. So I turned off usb debugging and still had no success getting into recovery in spite of a successful root. Advice anyone?
TommyGunn
If anyone ever received a solution, I'd love to hear it, I'm having the same problem...
Have the same Problem need help.
Hey guys, first time on here.
I've been trying to root my unlocked Asus tf700 running JB 4.2.1 for days and have been following all the xda guides with no luck.
I've tried to flash CMW on it through fastboot to no avail. Everything I see says, once you get into the bootloader or whatever, to press Vol Down until you get to the USB icon and then press volume up but there isn't any USB icon. Right when I get into the bootloader, after I hold Vol Down and Pwr, the first thing it reads on the top left corner of the screen is "Key driver missing." But I have downloaded the drivers from the asus website. Any suggestions about why this is happening? I also tried just using Motochopper (http://forum.xda-developers.com/showthread.php?t=2230763) but when it ran it said failure. I booted it up and I had SuperSU but I tried to open it and it said "no SU binary found! This is a problem!". Any suggestions on how to root this and flash a recovery on it would be greatly appreciated, because none of the other forums guides seem to work? help out a noob!
npf24 said:
Hey guys, first time on here.
I've been trying to root my unlocked Asus tf700 running JB 4.2.1 for days and have been following all the xda guides with no luck.
I've tried to flash CMW on it through fastboot to no avail. Everything I see says, once you get into the bootloader or whatever, to press Vol Down until you get to the USB icon and then press volume up but there isn't any USB icon. Right when I get into the bootloader, after I hold Vol Down and Pwr, the first thing it reads on the top left corner of the screen is "Key driver missing." But I have downloaded the drivers from the asus website. Any suggestions about why this is happening? I also tried just using Motochopper (http://forum.xda-developers.com/showthread.php?t=2230763) but when it ran it said failure. I booted it up and I had SuperSU but I tried to open it and it said "no SU binary found! This is a problem!". Any suggestions on how to root this and flash a recovery on it would be greatly appreciated, because none of the other forums guides seem to work? help out a noob!
Click to expand...
Click to collapse
If your device is unlocked you don’t need MotoChopper for rooting, just flash TWRP Recovery and it will ask you if you want to root your device (in case it detect that root is missing).
For the "Key driver missing" error, just ignore it, Fastboot will work just fine as long as you are sure that the drivers are installed just fine.
Pretoriano80 said:
If your device is unlocked you don’t need MotoChopper for rooting, just flash TWRP Recovery and it will ask you if you want to root your device (in case it detect that root is missing).
For the "Key driver missing" error, just ignore it, Fastboot will work just fine as long as you are sure that the drivers are installed just fine.
Click to expand...
Click to collapse
Thanks, but I'm still confused. I thought you needed GooManager to install TWRP, and GooManager won't work unless you have a rooted device.
npf24 said:
Thanks, but I'm still confused. I thought you needed GooManager to install TWRP, and GooManager won't work unless you have a rooted device.
Click to expand...
Click to collapse
Goo Manager is not mandatory, you can still flash the TWRP via fastboot.You can find more info on the TWRP website.
Sounds like a driver issue to me. If you can't fastboot cwm or use motochopper something is up.
Could also be your usb connection. Try another cable or port or another pc.
lafester said:
Sounds like a driver issue to me. If you can't fastboot cwm or use motochopper something is up.
Could also be your usb connection. Try another cable or port or another pc.
Click to expand...
Click to collapse
yeah ive tried two differ pcs already so I dont think its that. It definitely could be the drivers. Ive tried to install them from the asus site a bunch of times though so idk whats up.
npf24 said:
yeah ive tried two differ pcs already so I dont think its that. It definitely could be the drivers. Ive tried to install them from the asus site a bunch of times though so idk whats up.
Click to expand...
Click to collapse
If you have recently updated your firmware to xxxx.10, you will "not" be able to run motochopper (there is nothing wrong with your PC or cables), Ausus closed the Moto root opening with the latest firmware. However, you can still root following the TWRP instructions.....as indicated above.
just some more info
So i tried re installing the drivers one more time to my PC, and everything went okay, so I'm sure it can't be the drivers, although the error still comes up. And just to tell you guys, when moto chopper runs it says, "waiting for device, daemon not running, starting it now on port 5057, daemon started successfully." Don't know if that helps at all to what the problem is, but just some more info. Now I'll try flashing twrp and rooting that way.
Nothing works at all
dishinit said:
If you have recently updated your firmware to xxxx.10, you will "not" be able to run motochopper (there is nothing wrong with your PC or cables), Ausus closed the Moto root opening with the latest firmware. However, you can still root following the TWRP instructions.....as indicated above.
Click to expand...
Click to collapse
So I went to the TWRP website to try and install twrp 2.6.0. The three options on how to do this were:
1. Via GooManager - which I can't do because my device isn't rooted.
2. Through fastboot (it says to click on the usb icon) - there isn't any usb icon.
3. The terminal method.
I just tried the terminal method, and that didn't work either because when I typed in what it said I was supposed to type in, it said "permission denied."
So yeah.
npf24 said:
So I went to the TWRP website to try and install twrp 2.6.0. The three options on how to do this were:
1. Via GooManager - which I can't do because my device isn't rooted.
2. Through fastboot (it says to click on the usb icon) - there isn't any usb icon.
3. The terminal method.
I just tried the terminal method, and that didn't work either because when I typed in what it said I was supposed to type in, it said "permission denied."
So yeah.
Click to expand...
Click to collapse
I vaguely remember running Motochopper & getting the same message.....it you are on .8 or earlier firmware (in 4.2.1), Motochopper should run.
I think I turned off my tablet, left it connected to PC & then ran motochopper & tablet self booted.....lots of ABD's out of date messages, but Moto worked it's way through them and rooted my device.
I have read of problems with Win 7 (my OS) & Motochopper, but none if used with XP.
Good luck, & Let us know how t goes
npf24 said:
2. Through fastboot (it says to click on the usb icon) - there isn't any usb icon.
Click to expand...
Click to collapse
Recent bootloaders do not have a USB icon because they activate fastboot already while the boot menu is visible (read the tiny text in the top left corner).
dishinit said:
I vaguely remember running Motochopper & getting the same message.....it you are on .8 or earlier firmware (in 4.2.1), Motochopper should run.
I think I turned off my tablet, left it connected to PC & then ran motochopper & tablet self booted.....lots of ABD's out of date messages, but Moto worked it's way through them and rooted my device.
I have read of problems with Win 7 (my OS) & Motochopper, but none if used with XP.
Good luck, & Let us know how t goes
Click to expand...
Click to collapse
I tried what you said. The tablet didn't self-boot when I ran Motochopper again. It just stayed powered off. I turned it on, and the exact same thing happened. except there was another error in motochopper this time. it said "FAILURE ALREADY EXISTS." any other suggestions?
_that said:
Recent bootloaders do not have a USB icon because they activate fastboot already while the boot menu is visible (read the tiny text in the top left corner).
Click to expand...
Click to collapse
Okay that's what I thought. So if I do that second method on twrp, I guess I should just skip when it says to press the USB icon because fast boot is already running??
npf24 said:
Okay that's what I thought. So if I do that second method on twrp, I guess I should just skip when it says to press the USB icon because fast boot is already running??
Click to expand...
Click to collapse
Correct.
_that beat me to it - again. )
Anybody have one? It's Best Buy's brand tablet.
insigniaproducts.com/products/computer-speakers-accessories/NS-14T002.html
(can't post a link...)
Just picked up a Flex 8 on Black Friday. Not bad for $80. Not sure if I'd pay full price for it though.
It seems good for the price so far, except I'm having a rough time trying to root it.
Anyone have one and root it?
Employee here and I had to pouch one up as well for the price of $80. Now to figure out root.
Sent from my SPH-L710 using xda app-developers app
Let us know if you get it.
I've tried Bin4ry, doomlord, tpsparky, played around with it myself a bit. Still not luck. Closest I got is normal on Bin4ry. Just when it reboots, it has no root privaledges. su is in /data/local/tmp but it fails to do anything...
I haven't messed around with it until this very moment. I will admit that the price is killer but initial impression with the device could be better. I was impressed and I mean really impressed with its quadrant score. I'll root this device later today. Black Friday sales and I am tired.
---------- Post added at 01:20 AM ---------- Previous post was at 01:18 AM ----------
I found a link to root this device on both ICS and jellybean. I will personally look into it tomorrow but I will post it if you would like to go ahead. The guide itself was written for ICS but later down the thread you will find another link to a working root for jellybean.
http://androidforums.com/insignia-flex-all-things-root/661247-how-root-insignia-flex.html
Please root at your own discresion and I sure hope you purchased a protection plan (GSP) for your tablet.
also picked this up at my BB, was surprised when i walked in at 3pm and they still had about 10. i want to root too
We had a large quantity to sell as well and they all went. It is honestly not half bad. And I would really recommend getting the GSP for the tablet in case of anything. Will report back after rooting.
Let us know if you have any luck. I found the link you posted before which led me to try Bin4ry. The script seems to be updated for JB in general but still had no luck. I'm on a Mac and haven't tried any of the windows rooting apps, like posted at the bottom of that thread. I do have a windows partition and would be willing to try that method if needed. That chinese one at the bottom seems shady regardless though.. I hope there is an alternative to that
Is there a way to flash clockworkmod onto this tablet?
rekagear20 said:
Is there a way to flash clockworkmod onto this tablet?
Click to expand...
Click to collapse
I managed to get the CX-803 version of CWM for Rockchip 3066 from AndroTab.info to work by replacing its kernel with ours by unpacking and repacking with RK3xxx-Firmware-Tools by Sergio.
Note: This is for the Insignia NS-14T002 (aka iRiver NS-14T002) tablet that shipped with Android 4.2.2
Be EXTREMELY careful! Highly recommend you dump your current kernel and recovery partitions and save them somewhere before flashing anything.
If for some reason the recovery doesn't work, you can flash your stock recovery back as long as you can get back into root shell. But, if it fails to boot normally, I have no idea how to fix it. I have not been able to get any of the Rockchip flashing utilities to recognize the tablet so far, in bootloader mode (these devices have no fastboot) or otherwise. So don't blame me if you somehow brick your tablet.
You have been warned!!
CWM & Stock* Recovery image for NS-14T002
* if for some reason you can't back up your own, but again highly recommend backing up your existing recovery in case it's different from mine
You need root, and you need to do the install from root shell (don't forget to su) as described here.
I used /data/local instead of /dev - anywhere writable should be okay.
To boot into recovery:
adb reboot recovery
power off tablet, disconnect USB, press and hold Vol+ and Power until recovery comes up.
USB disconnect is not a strict requirement, but the battery status thing tends to get in the way.
In stock recovery, push Vol+ and Vol- simultaneously to bring up the menu. CWM menu should be visible at launch.
install petrus's Reboot App and use it to Reboot into recovery
Note: In CWM recovery you can swipe up for Vol+ (move up), swipe down for Vol- (move down), swipe left for Power (select), and swipe right for Back.
Re:Insignia Flex Tablet
I actually just purchased one of these last night. It was on sale at Best Buy for $99! I have successfully rooted it and it actually works great! I used Kingo Root to root but first I installed pda net first to install the necessary drivers. I have used this program to root several Android devices and haven't had a problem thus far!
http://www.kingoapp.com/
cramamarshall said:
I actually just purchased one of these last night. It was on sale at Best Buy for $99! I have successfully rooted it and it actually works great! I used Kingo Root to root but first I installed pda net first to install the necessary drivers.
Click to expand...
Click to collapse
Great news! I didn't have luck with that one but it might have been the machine I was using at the time.
Just to confirm, your model came with Jellybean 4.2, Model NS-14T002?
The previous version with Ice Cream Sandwich 4.0 was easier to root.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
bhiga said:
Great news! I didn't have luck with that one but it might have been the machine I was using at the time.
Just to confirm, your model came with Jellybean 4.2, Model NS-14T002?
The previous version with Ice Cream Sandwich 4.0 was easier to root.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
Click to expand...
Click to collapse
Yes my device came with 4.2.2 Jelly Bean! My first attempt using Kingo Root it did not see my device. Windows would not install the drivers needed. So I installed PDA net for windows and choose other in the program and once it was done installing it had configured the necessary drivers for Kingo Root to find my tablet and it rooted fine within a couple minutes after that! :good:
help!
klowdhaus said:
Anybody have one? It's Best Buy's brand tablet.
insigniaproducts.com/products/computer-speakers-accessories/NS-14T002.html
(can't post a link...)
Just picked up a Flex 8 on Black Friday. Not bad for $80. Not sure if I'd pay full price for it though.
It seems good for the price so far, except I'm having a rough time trying to root it.
Anyone have one and root it?
Click to expand...
Click to collapse
I was wondering, because I rooted my insignia flex 8 tablet and downloaded an app to try and customize the navigation bar and the developer provided a way on how to do it but said it was risky and took the risk anyway. Unfortunately, after turning on my tablet, it gets stuck on the insignia logo which I'm assuming it is stuck in the boot screen. I emailed the developer on how to fix this and said to flash a ROM to it. But I am just wondering if I am able to still do this even if my tablet gets stuck on the boot screen and freezes. I used ultimate dynamic navbar lite to try and customize my navbar.
arahmahndy said:
I was wondering, because I rooted my insignia flex 8 tablet and downloaded an app to try and customize the navigation bar and the developer provided a way on how to do it but said it was risky and took the risk anyway. Unfortunately, after turning on my tablet, it gets stuck on the insignia logo which I'm assuming it is stuck in the boot screen. I emailed the developer on how to fix this and said to flash a ROM to it. But I am just wondering if I am able to still do this even if my tablet gets stuck on the boot screen and freezes. I used ultimate dynamic navbar lite to try and customize my navbar.
Click to expand...
Click to collapse
I don't have the tablet anymore as it was a gift for a family member that lives elsewhere (I just wanted root so I could remote control it with TeamViewer QuickSupport), but will try to help from my notes and memory.
Flashing ROM may be difficult.
There is no fastboot on these Rockchip devices...
I couldn't find a way to flash without it being bootable and accessible via ADB
None of the Rockchip flashing tools would recognize it, even when I thought I got it booted into flash mode - it loaded drivers, but the flash tools still didn't see it.
The only way I know how to flash is to use a flash tool via ADB root shell.
Have you tried plugging it into USB on computer and booting it? Even if it doesn't reach the launcher, maybe it is accessible from ADB?
If you can access ADB, you may be able to reverse whatever the app changed from ADB shell and uninstall the app. (Politely ask the author for help)
You might be able to flash the system image I took too, but that has potential to brick it even worse.
If you have custom recovery loaded, you should just be able to restore from a backup.
If you don't have custom recovery loaded, things get a little more hairy...
You can try booting into Safe mode, maybe it'll bypass the offending app.
Power off tablet
Unplug USB*
Press and hold Vol- and Power until (hopefully) it completely boots
Try booting into standard recovery and see what your options are there - Factory Reset might help (depends what was changed and where)
Power off tablet
Unplug USB*
Press and hold Vol+ and Power until recovery comes up (Android with open chest)
Press Vol+ and Vol- simultaneously to bring up the menu.
* while unplugging USB isn't really required, because a battery app launches shortly afterward, it can make getting into recovery and safe mode more difficult
The folks over at Freaktab and Vondroid are really the experts at this Rockchip stuff.
For reference, the platform is RK3066, but there are many variations of the platform (different WiFi, memory configuration, etc) so you can't just grab any ROM.
Thank you!
bhiga said:
I don't have the tablet anymore as it was a gift for a family member that lives elsewhere (I just wanted root so I could remote control it with TeamViewer QuickSupport), but will try to help from my notes and memory.
Flashing ROM may be difficult.
There is no fastboot on these Rockchip devices...
I couldn't find a way to flash without it being bootable and accessible via ADB
None of the Rockchip flashing tools would recognize it, even when I thought I got it booted into flash mode - it loaded drivers, but the flash tools still didn't see it.
The only way I know how to flash is to use a flash tool via ADB root shell.
Have you tried plugging it into USB on computer and booting it? Even if it doesn't reach the launcher, maybe it is accessible from ADB?
If you can access ADB, you may be able to reverse whatever the app changed from ADB shell and uninstall the app. (Politely ask the author for help)
You might be able to flash the system image I took too, but that has potential to brick it even worse.
If you have custom recovery loaded, you should just be able to restore from a backup.
If you don't have custom recovery loaded, things get a little more hairy...
You can try booting into Safe mode, maybe it'll bypass the offending app.
Power off tablet
Unplug USB*
Press and hold Vol- and Power until (hopefully) it completely boots
Try booting into standard recovery and see what your options are there - Factory Reset might help (depends what was changed and where)
Power off tablet
Unplug USB*
Press and hold Vol+ and Power until recovery comes up (Android with open chest)
Press Vol+ and Vol- simultaneously to bring up the menu.
* while unplugging USB isn't really required, because a battery app launches shortly afterward, it can make getting into recovery and safe mode more difficult
The folks over at Freaktab and Vondroid are really the experts at this Rockchip stuff.
For reference, the platform is RK3066, but there are many variations of the platform (different WiFi, memory configuration, etc) so you can't just grab any ROM.
Click to expand...
Click to collapse
Thanks for the information! I know I have ADB from rooting my tablet so I'm gonna check how that is when I get home and I have found some rockship information on vondroid so I will check that out also. Thanks for the reply again!
arahmahndy said:
Thanks for the information! I know I have ADB from rooting my tablet so I'm gonna check how that is when I get home and I have found some rockship information on vondroid so I will check that out also. Thanks for the reply again!
Click to expand...
Click to collapse
If you can access ADB then try loading the CWM recovery I posted above. If you can at least get CWM up, at worst case I can give you a copy of my stock backup to restore.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
arahmahndy said:
Thanks for the information! I know I have ADB from rooting my tablet so I'm gonna check how that is when I get home and I have found some rockship information on vondroid so I will check that out also. Thanks for the reply again!
Click to expand...
Click to collapse
Did you get things sorted out?
If anyone is interested or needs it, Insignia sent me the GPL source.
You can also request it directly from them like it says on the website but it took a week or two (they might not have had a procedure in place yet, the agent had to forward my request to a different department) and I had completely forgotten until an unexpected package arrived.
Performance NS-15at10, ta120, ITQ701
Just thought someone might want to know, kingo root works, updated to 4.4.2, Booster plus battery saver pro is worth the money, better than 3c so far, still looking for more sources, any advice or help is appreciated especially for a recovery, dual bootloaders, ugh
cramamarshall said:
I actually just purchased one of these last night. It was on sale at Best Buy for $99! I have successfully rooted it and it actually works great! I used Kingo Root to root but first I installed pda net first to install the necessary drivers. I have used this program to root several Android devices and haven't had a proble
Can I install drivers without PC?
Click to expand...
Click to collapse
So I want to install the latest 4.4.4 Kit Kat on my Transformer Infinity because the latest Jelly Bean on it is extremely slow. Through research and google I found that the only way to root it was go back to an earlier version of Jelly Bean. Otherwise the motochopper program was denied access so I was unable to root it. So I found the right Jelly Bean update and stuck it on my SD card and it showed up in the notifications as an update to fall back to. Installed it and the motochopper app worked and rooted the tablet. I tried to use the Asus unlocker tool but it always says to try back later as it is trying to unlock it. Some info on the internet says that app doesn't work with jelly bean some says it does. So I thought i would roll back to Ice Cream Sandwich. In order to do that the info. on the internet says to hold the down volume button along with the power button and you can go to some menu that will allow you to install earlier version of android. Which I have an ICS for the infinity on the SD card. Problem is the volume down button plus power button does nothing. It has no effect. I'm at my wits end here. Everything I have found on the internet doesn't work. I'm fairly new to rooting, unlocking, and installing a custom android. I have done this once for a Kindle Fire tablet and it was MUCH easier then this Infinity tablet.
You do not need to downgrade to ICS (and you can't - at least not with stock firmware) The unlock tool version 8 works fine on JB roms - if it works at all. You really have to keep trying. For some people it literally took 50 tries or more and all the sudden it worked... And for some it never worked. There's no rhyme or reason for this except that Asus is not trying very hard to make this work for us. They enable it, but do not support it.
Google "unable to unlock TF700" and you will get a dozen threads discussing this and a few more strategies you can try.
Sent from my DROID4 using Tapatalk
That was kind of how the root tool worked I had to try it over and over I think about the 5th or 6th time it worked.
Well that was relatively painless then - happy flashing
I'm not quite to 50 times yet but I still get "an unknown error has occured. The network may be down please try again later" error.
So i'm all rooted and unlocked now. I have a snapshot version of 4.4.4 for transformer infinity. The cyanogen mod program says the TF700T isn't supported and aborts. I've tried the Clockwork Rom recovery program and it says the TF700T isn't supported either only the TF200 is it says. What is the best way to install this ROM?
So I tried Rom Toolbox. When the tablet reboots to boot into the recovery where you can install the rom it just sits at the asus logo screen forever. I don't think I have a recovery boot anymore. When I hold the power button and volume down button which is supposed to allow you to boot into recover nothing ever happens.
It's probably a little late, but to install a custom rom you have to install a recovery compatible with your bootloader and the rom you intend to flash.
You flash this recovery (TWRP or CWM) in fastboot, then you can boot into it to install a rom.
If you can't boot into the bootloader with Power and Volume Down and you did not generate nvflash blobs prior to all this, I'm afraid it's a brick.
Try every combination you can think of: Holding the buttons a very long time, use the reset pin hole on the side in conjunction with Volume Down, let it sit for hours and hope it sorts something out.
You need some magic to give you access to the bootloader menu and fastboot - that's your last hope.... Sorry
I can still boot into the version of jelly bean I have on the tablet fine. I did manage to get it to finally boot into a recovery console. it might have been a fluke I tried like 20 times and it finally just booted into it from the Rom Manager program. I tried installing my rom image but it would fail every time. I just rebooted and it went back into jelly bean. No idea what to do from here. The power button and volume down still don't do anything. And I haven't been able to reproduce getting it to boot back into the recovery again. At least it isn't bricked but I hate this tablet so much I might just take a hammer to it and give up.
If you have the time can you walk me through putting a decent version of 4.4.4 on here if it will work? Apparently I either don't know what i'm doing, the guides I have tried online are missing important steps, or my tablet is just "special". I do know that it is rooted and unlocked and that is where its at right now.
This guide seems like a good place to start but I don't see how to get through it when the volume down and power button doesn't do anything
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
kahless1979 said:
If you have the time can you walk me through putting a decent version of 4.4.4 on here if it will work? Apparently I either don't know what i'm doing, the guides I have tried online are missing important steps, or my tablet is just "special". I do know that it is rooted and unlocked and that is where its at right now.
This guide seems like a good place to start but I don't see how to get through it when the volume down and power button doesn't do anything
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Click to expand...
Click to collapse
I know when I'm upset with this thing I start doing things wrong....make sure you are actually using the vol down button and not the Up button. It's an easy thing to do when you're in PO'ed mode.
You're lucky to be unlocked! I bet I have run that unlock tool a million times to no avail.....
kahless1979 said:
If you have the time can you walk me through putting a decent version of 4.4.4 on here if it will work? Apparently I either don't know what i'm doing, the guides I have tried online are missing important steps, or my tablet is just "special". I do know that it is rooted and unlocked and that is where its at right now.
This guide seems like a good place to start but I don't see how to get through it when the volume down and power button doesn't do anything
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Click to expand...
Click to collapse
You cannot use ROM Manager on the TF700!!! That is the fastest way to a hard brick I know on this tablet. Forget ROM Toolbox, ROM manager and all the other tools! You have to get ADB and fastboot working on your computer and my guide you linked to is a good start.
I have no idea why you cannot boot into the bootloader if your rom boots fine????
You are pushing Power and Volume Down until you feel the tablet vibrate TWICE?
Get the ADB drivers installed on your PC and with the tablet booted into your rom type this in a command prompt:
Code:
adb devices
What do you get?
berndblb said:
You cannot use ROM Manager on the TF700!!! That is the fastest way to a hard brick I know on this tablet. Forget ROM Toolbox, ROM manager and all the other tools! You have to get ADB and fastboot working on your computer and my guide you linked to is a good start.
I have no idea why you cannot boot into the bootloader if your rom boots fine????
You are pushing Power and Volume Down until you feel the tablet vibrate TWICE?
Get the ADB drivers installed on your PC and with the tablet booted into your rom type this in a command prompt:
Code:
adb devices
What do you get?
Click to expand...
Click to collapse
Volume Down and Power yields one vibration and nothing happens after that. I have tried holding them down longer to no avail and released them after one vibration and nothing still.
I would use ADB to push the rom to the tablet and that is what I did with a Kindle Fire a couple years ago and worked great. But your guide still calls for being able to use the volume down and power button. I guess I got a real lemon of a tablet here.
I get List of devices attached
C7OKAS090001 device
kahless1979 said:
Volume Down and Power yields one vibration and nothing happens after that. I have tried holding them down longer to no avail and released them after one vibration and nothing still.
I would use ADB to push the rom to the tablet and that is what I did with a Kindle Fire a couple years ago and worked great. But your guide still calls for being able to use the volume down and power button. I guess I got a real lemon of a tablet here.
I get List of devices attached
C7OKAS090001 device
Click to expand...
Click to collapse
Well that's good. You seem to have ADB access. Try this command:
Code:
adb reboot - bootloader
That should reboot your tablet into fastboot mode. If it does, use this command:
Code:
fastboot devices
That should return a (different) alpha-numeric string and you would be in business to flash. But let's not get ahead of ourselves...
adb reboot - bootloader
That command restarted my tablet.
So just type "adb fastboot devices" at the command prompt?
kahless1979 said:
adb reboot - bootloader
That command restarted my tablet.
Click to expand...
Click to collapse
The correct command is:
Code:
adb reboot-bootloader
_that said:
The correct command is:
Code:
adb reboot-bootloader
Click to expand...
Click to collapse
I took out the spaces between the hyphen. Same thing, it rebooted the tablet right back to the android desktop.
kahless1979 said:
I took out the spaces between the hyphen. Same thing, it rebooted the tablet right back to the android desktop.
Click to expand...
Click to collapse
I'm stumped... @_that you have an idea why it doesn't boot into the bootloader? I thought maybe the Volume button is bust - but now...IDK
berndblb said:
I'm stumped... @_that you have an idea why it doesn't boot into the bootloader? I thought maybe the Volume button is bust - but now...IDK
Click to expand...
Click to collapse
Is it possible I messed something up when I downgraded from Jelly Bean 4.2.1 to 4.03? The reason I had did that was a guide somewhere for this tablet said the ADB motochopper program wouldn't root 4.2.1. Which I could never get it to work. But did fine once I went to 4.03. I did that by downloading that update from asus's website and putting it on my SD card and it found the update and asked me if I wanted to fallback to an older one.
kahless1979 said:
I can still boot into the version of jelly bean I have on the tablet fine.
Click to expand...
Click to collapse
kahless1979 said:
Is it possible I messed something up when I downgraded from Jelly Bean 4.2.1 to 4.03?
Click to expand...
Click to collapse
So what version of Android is now actually running on your device? 4.2.1 or 4.0.3 (which is ICS)?
You also speak repeatedly of some version 4.4.4 you are trying to install - the latest version of Android as of today is 4.4.2.
Note that there are multiple ways to hard brick your tablet if it is unlocked - don't do anything you don't understand.
Seems I'm an idiot.
Recently bought a Kobo Arc 10HD, my first Android device. I rooted it according to Dazza9075's guide on here. I didn't update the recovery image, because in my ignorance I thought it'd allow me to recover to factory settings.
Apparently not.
I've just reset it, and now I've lost everything. The base OS is still working, but there is no loader, no settings widget, nothing. The battery remaining indicator and time are showing in the top right, the three Android buttons are showing at the bottom. It's powering down the screen properly. That's it. If I press the recent apps button the old wallpaper comes up. Any swiping on the recent apps and the System UI stops responding.
Edit: Might also be worth mentioning it'll only restart after the first power on after a reset - any subsequent attempts and it stays on the Kobo loading screen.
Have I just completely buggered it, or do I have some options available?
Okay, I'm able to sideload using ADB in the recovery settings - is this of any use?
Hello
Yes you can sideload recovery using ADB as given in the guide you mentioned . Ensure that the device drivers and ADB drivers are properly installed on your PC before sideload.
Hope it works
4shreyas said:
Hello
Yes you can sideload recovery using ADB as given in the guide you mentioned . Ensure that the device drivers and ADB drivers are properly installed on your PC before sideload.
Hope it works
Click to expand...
Click to collapse
Don't think that's going to help. I'm unable to access dev mode as the settings app isn't there. There's no way to go into ADB shell, I can only use the sideloader mode in the recovery settings.
Glompish said:
Don't think that's going to help. I'm unable to access dev mode as the settings app isn't there. There's no way to go into ADB shell, I can only use the sideloader mode in the recovery settings.
Click to expand...
Click to collapse
Flash stock rom back
Sent from my GT-S7582 using XDA Premium 4 mobile app
Unfortunately don't have one. I didn't install a custom ROM on it because they're unavailable on Kobos. If I get a stock upgrade.zip I think it should work, but I haven't managed to find one.
Hello
Search on the internet if someone has uploaded your stock rom . You can use ADB Fast boot to flash recovery and without stock rom , recovery alone won't help you . If you find a custom rom try that
All the best
I'll try having a further look. Thus far no luck though.
Thanks for the help.
Glompish said:
If I get a stock upgrade.zip I think it should work, but I haven't managed to find one.
Click to expand...
Click to collapse
If you go this route you'll need to sniff out the url on an update from Kobo. I know this works on the original arc but they may have smartened up and started using ssl.