Database Info

[Q] CMW (internal storage) no ROM (on SD) on TF101 b80

hi! my apologies but i searched and read alot of post already on how to solve this.
i flashed Roach latest CMW how ever being so stupid i forgot to put a ROM on internal memory. did full wipe already and i have no ROM to flash as it reads internal memory only.
ive read alot of post regarding the concern, i want to try to push a ROM on internal drive using ADB but when i run "adb devices" nothing is found.
any suggestions or any links to posts that i might get help or tutorial. im not an expert on using ADB so keep instructions simple, im a noob i admit it but i just need help. thanks!
read through posts "[Troubleshooting/Solved] ClockworkMod recovery 5.5.0.4 from Koush" "Used roach's new CWM recovery, now can't intall rom" "

im on recovery and when i run adb devices it just blank. any walk through is much appreciated!

Do yo have USB debugging on?

I dont know because i was about to flash a new rom so i did a full wipe already

Did you ever get ADB working before all this? USB debugging usually have to be turn on by the user. In Settings>Developer options.

i havent with my tablet but with my htc desire hd i used adb. and when ever i flash a ROM on my tf i usually turn on usb debugging always. right now in on recovery roach r2. my ROM is on my external memory. also tried to do a nvflash how ever whenever i run the download.bat cmd opens then closes 3 secs maybe

i also got a new sdk from this forum " [GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting!" as ave said above when i type "adb devices" its just blank and does not list any device.

I had exactly the same problem - I'm not sure about tablet version that I own, but I've flashed Wipe Lite and new Recovery. I also have HTC phone that I've been using on the same PC .
I've spent an hour trying to get my TF back on feet and I managed it.
I would recommend uninstalling all HTC and ASUS software and drivers, rebooting PC and installing just ASUS PC Suite. It worked in my case - suddenly Device ID showed up for a few seconds before ADB reported "no device" again.
So I've pushed Rogue XM Recovery to data/media:
adb push roguexm data/media
Of course use name of zip file instead "roguexm" in command above.
After that zip file showed up on sdcard and I could flash it - it doesn't support AROMA but it works quite fine otherwise.
Hope it'll work in your case. Good luck!

Hope it will help
I once were in your case, did full wipe and forgot to put a Rom in internal memory. But in my case I just rebooted the transformer and all of a supprise, my tablet reverted to the stock Rom! I dont know how this happend but may be Asus did something to keep stock Rom persistent whatever you have flashed roms or CWMs.
So i hope this also happened in your case, just give it a try. Good luck!

If he did "Full Wipe - factory reset" then he should be able to boot HC/ICS and from that copy files onto internal /sdcard.
But if he used Android Revolution Super Wipe script either Lite or Full then he has nothing to boot into, no system at all - I've done that Only thing that left was recovery without external sdcard support, so I had nothing to install...
ASUS and HTC drivers have some issues and make everything harder than it should be, that's why I recommend to uninstall all HTC and ASUS software, rebooting PC and installing ASUS PC Suite only, to have "clean" drivers on PC.
I've tried different drivers and none of them worked, until I've done that.
Ok, I'll try to write it simple, I'm not sure if I can post links so just in case I'll give thread names. If it will be too simple don't get mad - ok?
1. Uninstall ASUS and HTC software, reinstall ASUS software like mentioned above.
2. Create folder on your C: drive called CWM
3. Go to post "Eee Pad Transformer Android Development\[Recovery] Rogue XM Recovery v1.3.0 (CWM-based Recovery v5.0.2.7" thread - http://forum.xda-developers.com/showthread.php?t=1446019
and "save as..." cwm_recovery-5027_rogue_rburrow-tf101-r1.zip to C:\CWM
4. Highlight/select command below:
adb push cwm_recovery-5027_rogue_rburrow-tf101-r1.zip data/media
then right click on it and select "copy" - it will save you typing it later.
5. Boot Recovery on your Transformer and connect it to PC, let system install device drivers
6. Click START, "Run...", type: cmd
7. It should show you path to your profile folder - C:\Users\yourname>
8. Type: cd /CWM
it will change folder to C:\CWM>
9. type: adb devices
(it should give you your device ID, if it still will give "no device id" then there I can't help you - I'm sorry)
10. right click on black background and select "paste" (you'll see command that you've copied from number 4), then press enter
11. It should copy recovery onto your internal sdcard - you will be able to select it from tablet
12. type adb kill-server and disconnect tablet, install new recovery and from that one you will be able to select external or internal sdcard
Notes:
I don't know why but I was able to send only small file from CWM-adb connection, it kept disconnecting quite quickly that is why I recommend sending Rogue XM Recovery instead of whole new ROM.
Other thing - it may depend on what windows system you have - I'm on Win 7 x64 (don't remember how it worked on other versions) and I can paste onto cmd (black) window without problems from right click menu. If you won't be able to paste there or you'll get some rubbish, try to right click on top bar and select "Edit" and then "Paste".
Ok, that's all. Hope it will work.

thanks for all inputs. i did a full wipe but not as scripts. i wiped manually. i did try to reboot but stuck as eepad screen. will try to re-install asus drivers and uninstall htc ones. hopefully i get it done today. i will update later...

still no luck. device not found. im going to try to install new sdk... i hope it works. ive already removed htc sync and drivers. also re-installed asus sync and updated drivers. on device manager detects on other devices transformer but drivers are not installed.

yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz

monespeso said:
yahoo! got it working now. i had to enable adb usb Drivers for Nvidia Tegra based Android Tablets and re-install SDK download android usb and learn What Is ADB And How To Install It With Android SDK.
finally got my tablet working again and my first thing to do is have a copy of a ROM and CWM in both storages!
thanks alot for the input and for helping!
thanks Kraliz
Click to expand...
Click to collapse
Could you tell me how to do that? Because I have the exact same problem.

Trouble getting adb to work

Sorry about the uninspiring title, but after an afternoon of this I'm uninspired. All I wanted to do was root this Xoom so I could take some screenshots..
I can get the tablet to stage where it says
--> fastboot
starting fastboot protocol support.
at which time I assume I can start adb. I've tried the USB drivers from the PDAnet package, but when I plug in the Xoom I get a desktop notification saying 'HTC Exit -1' (sorry, that may not be the exact wording, but the same effect).
in that 'fastboot' state, adb devices tells me there aren't any devices connected
the Xoom show up OK when booted into Android, Windows (7, 64 bit) sees it as a drive, and Device Manager sees an MZ604. adb still doesn't see anything
I started off by using the minimum set of utilities (adb, fastboot and their dlls) and then installed the SDK and used its tools (yeah, I've pathed everything properly, I was writing DOS batch files in 1985... and now am a grumpy old man )
The Xoom is Australian WiFi only, runs Honeycomb 3.2.2, hasn't been rooted (I'm trying to do that)
speaking of old, though, the fiddly volume rockers get that way (and or so ironically are used for screenshots in ICS I believe)
I have a feeling that I don't have the proper USB driver installed, I've uninstalled PDAnet, and the Xoom still shows up in windows, but since I can't get a root prompt on the Xoom have no idea what it's using
Any ideas?
Rob

SD card not found
I may as well get all my woes into the open
When in Recovery Mode, the Xoom won't recognise the SD card, it seems to be trying to mount it on /sdcard
I have some zip files of a rooted Honeycomb image, and was going to triple cjeck whether flashing a zip file was a good idea or not first, but I don't get that far
I can see the card and contents from Windows while it's mounted in the Xoom
I should be able to use the card from recovery mode, right?
Rob

emueyes said:
Sorry about the uninspiring title, but after an afternoon of this I'm uninspired. All I wanted to do was root this Xoom so I could take some screenshots..
I can get the tablet to stage where it says
--> fastboot
starting fastboot protocol support.
at which time I assume I can start adb. I've tried the USB drivers from the PDAnet package, but when I plug in the Xoom I get a desktop notification saying 'HTC Exit -1' (sorry, that may not be the exact wording, but the same effect).
in that 'fastboot' state, adb devices tells me there aren't any devices connected
the Xoom show up OK when booted into Android, Windows (7, 64 bit) sees it as a drive, and Device Manager sees an MZ604. adb still doesn't see anything
I started off by using the minimum set of utilities (adb, fastboot and their dlls) and then installed the SDK and used its tools (yeah, I've pathed everything properly, I was writing DOS batch files in 1985... and now am a grumpy old man )
The Xoom is Australian WiFi only, runs Honeycomb 3.2.2, hasn't been rooted (I'm trying to do that)
speaking of old, though, the fiddly volume rockers get that way (and or so ironically are used for screenshots in ICS I believe)
I have a feeling that I don't have the proper USB driver installed, I've uninstalled PDAnet, and the Xoom still shows up in windows, but since I can't get a root prompt on the Xoom have no idea what it's using
Any ideas?
Rob
Click to expand...
Click to collapse
What USB cable are you using? Try to use your Xoom oem cable. Also, make sure that you try different USB ports, especially the ones tied more directly to the pc motherboard. It's finicky like that. Recheck your drivers. I'm not familiar with that PDAnet source. Motodev is the place to get them from. You may also need the java sdk from oracle.
There are some useful guides on setting up adb/fastboot/rooting in General...you may have to go back a few pages but it will be worth it to make your task easier.
Good luck!
---------- Post added at 10:51 AM ---------- Previous post was at 10:47 AM ----------
emueyes said:
I may as well get all my woes into the open
When in Recovery Mode, the Xoom won't recognise the SD card, it seems to be trying to mount it on /sdcard
I have some zip files of a rooted Honeycomb image, and was going to triple cjeck whether flashing a zip file was a good idea or not first, but I don't get that far
I can see the card and contents from Windows while it's mounted in the Xoom
I should be able to use the card from recovery mode, right?
Rob
Click to expand...
Click to collapse
Which recovery mode are you talking about? Have you unlocked and installed a custom recovery, as in a ClockworkMod-based recovery? If so, which one? They have some different behaviors. If it is stock recovery, I don't think it sees the external sdcard at all.

Also make sure usb debugging option is enabled. And flash another recovery image.
You don't really need to root. Just unlock the bootloader. Push the recovery image. Reboot to recovery. And flash a pre rooted rom from team EOS.
Sent from my MZ601 using Tapatalk 2

[Q]Problem with MTP (and help with a workaround)

Hi
Some background. Like many, I bought a TF700T and like a fool installed the OTA update to JB. I then downgraded, rooted in .30, then upgraded again and flashed SU to keep root in JB. I am now, therefore, running the stock OTA JB ROM, rooted. My bootloader is also unlocked.
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
I want to get files on and off the *internal* storage (I don't have an external sdcard)
Things i have tried:
- Using a different USB port
- Using one of the USB ports on the back of the machine, instead of the front ones
- Uninstalling the MTP drivers
- Using the ASUS drivers from the website
- Cleaning out all my old unconnected USB devices (show devmgr_unconnected_devices=1 or whatever) and uninstalling all THOSE drivers
- Cleaning out with USBDeview
- Fresh install of the OTA ROM, after a data wipe/factory reset and wiping cache and dalvik
The only things I haven't tried are a new USB cable (damn you ASUS and your proprietary connector), and a clean install of Windows (major ballache).
Any ideas about what I could do to sort this would be greatly appreciated.
Since I only want to be able to move files on and off the device, I tried a workaround. I tried mounting the sdcard (internal) in windows manually through adb but the command I used to use on my old S2 through adb shell (echo dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) but it errors with No such path or similar. I'm unsure if the mount points are different (I guess they will be, can anyone help with telling me what the mount point for the internal emmc is on the tf700?)
Really hope someone will be able to help me!
Thanks in advance guys

I'm in a similar situation except I'm not rooted or unlocked. I've tried just about all the steps you've mentioned w/ no luck. I've even tried to three different PCs running XP, Vista, and 7 and get the same result. What makes the situation even worse is my brand new 32GB microSD card won't read on my desktop as well.

m000se said:
Hi
Some background. Like many, I bought a TF700T and like a fool installed the OTA update to JB. I then downgraded, rooted in .30, then upgraded again and flashed SU to keep root in JB. I am now, therefore, running the stock OTA JB ROM, rooted. My bootloader is also unlocked.
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
I want to get files on and off the *internal* storage (I don't have an external sdcard)
Things i have tried:
- Using a different USB port
- Using one of the USB ports on the back of the machine, instead of the front ones
- Uninstalling the MTP drivers
- Using the ASUS drivers from the website
- Cleaning out all my old unconnected USB devices (show devmgr_unconnected_devices=1 or whatever) and uninstalling all THOSE drivers
- Cleaning out with USBDeview
- Fresh install of the OTA ROM, after a data wipe/factory reset and wiping cache and dalvik
The only things I haven't tried are a new USB cable (damn you ASUS and your proprietary connector), and a clean install of Windows (major ballache).
Any ideas about what I could do to sort this would be greatly appreciated.
Since I only want to be able to move files on and off the device, I tried a workaround. I tried mounting the sdcard (internal) in windows manually through adb but the command I used to use on my old S2 through adb shell (echo dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) but it errors with No such path or similar. I'm unsure if the mount points are different (I guess they will be, can anyone help with telling me what the mount point for the internal emmc is on the tf700?)
Really hope someone will be able to help me!
Thanks in advance guys
Click to expand...
Click to collapse
First check make sure you have your "USB debug" and "Unknow software" checked in settings. Then go here and install the pda software for your windows. Once installed, it will installed all the driver for your tab automatically. You don't need to use the software, you can uninstall it later, but the driver will stay.
http://junefabrics.com/android/download.php

I haven't picked up a TF700 yet (out of stock locally), so these are just general suggestions...
From adb, shell into the OS (adb shell) and list the directories to try and determine their structure. If the device is booted, the internal SD should already be mounted.
I would start by looking for the following folders:
/sdcard
/mnt/sdcard
/data/media

m000se said:
Hi
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
Click to expand...
Click to collapse
I had the same problem getting MTP to work on old XP machine. The following worked for me...see post #12
http://www.transformerforums.com/fo...ormer-manual-usb-drivers-sync-software-2.html

Thanks for the replies, everyone. I installed PDANet and was initially hopeful once the drivers started installing. Sadly, Windows still doesn't see my device.
adb shell-ing into the device --> mounts
This lists /dev/fuse as the internal storage. I can't echo this to /sys/devices/usb_mass_storage/lun0/file because when I do it returns "No such file or directory"
The solution posted as working on XP machines doesn't work either.
This is seriously annoying. I'm tempted to just give in and get myself a 32GB SDHC and card reader and just use that instead - at least that way I can move the files across with Root Explorer or something...

[GUIDE] Kobo Arc, 7, 7HD and 10HD - ROOT and Development

Kobo
Arc, Arc 7, Arc 7HD and Arc 10HD​
With the release of not 1 but 3 new devices from Kobo and no specific device forum I thought it time we consolidated any and all root / development available information on them under one roof. All credit for others work will be acknowledged if known.
If anyone has any info they feel should be added please post it and ill add it
The following devices and development status are list below
Kobo Arc - Root + recovery (POSSIBLE PROBLEM WITH NEW SYSTEM UPDATE, Arctic may no longer work)
Kobo Arc 7 - Root
Kobo Arc 7HD - Root + recovery
Kobo Arc 10HD - Root + recovery
Please support development on these projects, sign up to XDA and join in, we need all the help that we can get!​

Kobo Arc
Root
Enable unknown sources In security options
Download arctic.apk to your tablet from http://zhuoweizhang.net/Arctic.apk and install, it will do the rest and install Chainfires SU
Enjoy your root access
Please note, the Arctic patch for the original arc may no longer work after a recent system update, possible solution would be to use fiddler to check what response the device receives to with the update, then hardreset device, connect to an access point directed to a proxy with fiddler running and change the response it gets, going to be a pure pain in the bum but it should work, ill maybe add that info later. Or work on a way to flash a ROM from stock recovery....
Credit to
zhuowei @ http://zhuoweizhang.net/ for Arctic.apk
Chainfire for SU
Recovery Mod
Root needed first!
And something like ROM Toolbox for all the various apps needed
Install the android SDK on your computer, you will need to add the google usb drivers, you will find them in the "extras"
Enable usb debug on the arc and install the generic google adb usb drivers
Plug in the device and let it install drivers, it WILL fail one device, manually install drivers for the failed "arc" device that's highlighted with an error, click on it and update the driver, browse, let me pick my own, show all devices, click next and have disc. Click browse and navigate to your android SDK>extras>google USB driver, for the correct drivers, select "ADB interface"
Delete or rename the file on the device located at /etc/install-recover.sh this will make the custom recovery persistent
Copy the recovery.img to the SDCard, either by using drag and drop in windows ( to root of "internal storage") or by adb push "adb push recovery.img /sdcard/
The next job is to open up a command window on your computer and navigate to adb folder, SDK>platform-tools. Type the following exactly, even better copy and paste them!
adb shell
su
cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit adb shell (ctrl+C) and type
adb reboot recovery
and bobs your uncle, one happy new recovery
Original ROM files
recovery Recovery
xloader Xloader
system System
misc Misc
logos Logos
crypto Crypto
cache Cache
bootlogo Bootlogo
bootloader Bootloader
boot Boot
efs Efs
Custom ROM files
Credit to
Me for recovery mod

Kobo Arc 7
Root
Fully setup device
Download impactor on PC from http://www.cydiaimpactor.com/
Download android SDK on PC, from http://developer.android.com/sdk/index.html
Run SDK manager and acquire the google USB drivers
Enable dev mode on device by going to settings, about kobo, and tap build number 7 times
Enable USB debug mode in developer options
Enable unknown sources in security options
Plug in device and let it install a USB composite device and a arc 7hd drive, it will fail on the third, go to device manager, and manually install drivers for the "arc" device that's highlighted with an error.
Click on it and update the driver, browse, let me pick my own, show all devices, click next, have disc. click browse and navigate to your android SDK>extras>google usb driver\android_winusb.inf, for the correct drivers, select ADB interface
Run the impactor program downloaded earlier, once loaded, click on start
Check your device screen, you should see an error message, click on decline then decline again and finally decline again, (not sure that makes any difference)
Go to the market place and download SU by Chainfire
EDIT: Impactor was updated which will now make the above work
Credit to
http://www.cydiaimpactor.com/ for the rooting tool
Chainfire for SU
howlinwolf430 for trying the unlock with the new impactor available above
Recovery Mod
howlinwolf430 has a working Recovery img up and running, tests continue but we look forward to seeing this soon!

Kobo Arc 7HD
Root
Fully setup device
Download impactor on PC from http://www.cydiaimpactor.com/
Download android SDK on PC, from http://developer.android.com/sdk/index.html
Run SDK manager and acquire the google USB drivers
Enable dev mode on device by going to settings, about kobo, and tap build number 7 times
Enable USB debug mode in developer options
Enable unknown sources in security options
Plug in device and let it install a USB composite device and a arc 7hd drive, it will fail on the third, go to device manager, and manually install drivers for the "arc" device that's highlighted with an error.
Click on it and update the driver, browse, let me pick my own, show all devices, click next, have disc. click browse and navigate to your android SDK>extras>google usb driver, for the correct drivers, select ADB interface
Run the impactor program downloaded earlier, once loaded, click on start
Check your device screen, you should see an error message, click on decline then decline again and finally decline again, (not sure that makes any difference)
Go to the market place and download SU by Chainfire
Credit to
http://www.cydiaimpactor.com/ for the rooting tool
Chainfire for SU
Recovery Mod
Ensure SU is working and you can get SU access with adb shell
download the recovery.img attached in to your adb folder
with the device connected to computer type the following
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
ctrl-c
adb reboot recovery
Make sure you allow recovery to make changes when prompted or it will automatically revert to stock recovery
Kobo 7HD notes
Fastboot and Bootloader modes are ONLY available via adb/fastboot commands, there are NO hardware button combos.
adb reboot bootloader / fastboot reboot-bootloader
adb reboot recovery / fastboot reboot recovery
Recovery can be accessed by turning off the device, holding down "VOL DOWN" and turning on, keep VOL DOWN pressed until booted
APX mode can be accessed by plugging in a USB cable connected to a computer, turning off the device, holding down "VOL UP" and turning on, keep VOL UP pressed until booted, note that the screen remains BLACK and as far as I have worked out it is completely useless without certain files we do not have access to.

Kobo Arc 10HD
Root
Fully setup device
Download impactor on PC from http://www.cydiaimpactor.com/
Download android SDK on PC, from http://developer.android.com/sdk/index.html
Run SDK manager and acquire the google USB drivers
Enable dev mode on device by going to settings, about kobo, and tap build number 7 times
Enable USB debug mode in developer options
Enable unknown sources in security options
Plug in device and let it install a USB composite device and a arc 7hd drive, it will fail on the third, go to device manager, and manually install drivers for the "arc" device that's highlighted with an error.
Click on it and update the driver, browse, let me pick my own, show all devices, click next, have disc. click browse and navigate to your android SDK>extras>google usb driver, for the correct drivers, select ADB interface
Run the impactor program downloaded earlier, once loaded, click on start
Check your device screen, you should see an error message, click on decline then decline again and finally decline again, (not sure that makes any difference)
Go to the market place and download SU by Chainfire
http://www.cydiaimpactor.com/ for the rooting tool
Chainfire for SU
Recovery Mod
Ensure SU is working and you can get SU access with adb shell
download the recovery.img attached in to your adb folder
with the device connected to computer type the following
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
ctrl-c
adb reboot recovery
Make sure you allow recovery to make changes when prompted or it will automatically revert to stock recovery
Kobo 10HD notes
Fastboot and Bootloader modes are ONLY available via adb/fastboot commands, there are NO hardware button combos.
adb reboot bootloader / fastboot reboot-bootloader
adb reboot recovery / fastboot reboot recovery
Recovery can be accessed by turning off the device, holding down "VOL DOWN" and turning on, keep VOL DOWN pressed until booted
APX mode can be accessed by plugging in a USB cable connected to a computer, turning off the device, holding down "VOL UP" and turning on, keep VOL UP pressed until booted, note that the screen remains BLACK and as far as I have worked out it is completely useless without certain files we do not have access to.
EDIT: 16th Feb 2014
Arc 10HD received an OTA update "update-ota832-ota932.zip" around the 10th of Feb. Initial look in to this suggests not only are there some system updates the but the bootloader is updated too, its only about 17MB

Edit 6
10HD received a OTA update
Edit 5
thanks to howlinwolf430 Arc 7 now has root, I need to confirm this and the method but I believe the new impactor has added another vulnerability that allows ROOT Thus the guide for the 7HD and the 7 is the same
Edit 4
Recovery img is now complete for the Arc 10HD and 7HD! There are some small configuration changes needed to fix some mounting issues but it backs up and restores just fine
Edit 3
Source code now available for all arcs, git for everything available https://github.com/dazza9075
Recovery Roms for Arc 7HD and 10HD almost complete, just testing to see if it restores correctly
Edit 2
Please note, the Arctic patch for the original arc may no longer work after a recent update
Bootloaders on the 7HD and 10HD appear to be unlocked.
Edit 1
Development on the Arc 7 has stagnated and I no longer have one to directly play with although I do have access if need be.
Sent from my arc 10HD using xda app-developers app

Support needed!
Hi everyone, if your reading this and have some experience in building custom ROMs for unsupported devices and wish to give us a guiding hand please jump on board and help where you can. We currently have working custom recovery's on all devices ( Arc 7 needing a little bit of testing ) but we are needing some support for the next steps!
Many thanks!

Arctic,apk
I have ordered a Kobo Arc online. Any idea if the Arctic.apk does or does not work on them with the system update. Just looking for confirmation

Nice work...I hope it won't remain an isolated effort
@dazza9075: I just ordered the Arc 10HD - can I safely update the software once I get it and root it AFTER? I didn't see any notes indicating otherwise, but I know from my other Android devices that usually the root/recovery methods are tied to a specific version.
Note I don't even know yet if it will require an update - I'm super-new to the Kobo ecosystem.
BTW: thanks for the work done - I never use an Android phone/tablet/media device that does not have root access and a recovery mechanism to save the day.

kayge said:
I have ordered a Kobo Arc online. Any idea if the Arctic.apk does or does not work on them with the system update. Just looking for confirmation
Click to expand...
Click to collapse
after the most recent and probably last system update it is disabled. I stopped my arc from updating so cant confirm without a full reset but the original author of the arctic apk has said it no longer works, I cant see any reason for him to lie.
Ipse_Tase said:
@dazza9075: I just ordered the Arc 10HD - can I safely update the software once I get it and root it AFTER? I didn't see any notes indicating otherwise, but I know from my other Android devices that usually the root/recovery methods are tied to a specific version.
Note I don't even know yet if it will require an update - I'm super-new to the Kobo ecosystem.
BTW: thanks for the work done - I never use an Android phone/tablet/media device that does not have root access and a recovery mechanism to save the day.
Click to expand...
Click to collapse
ok, Kobo will do a system update as soon as you turn the thing on, you cant even get around that (although some fiddling with fiddler might fool it if we can ID what is going on). however, to date there hasn't been an update that disables it. and if there was we can simply flash my stock ROMs which already have root and are flashable.
what we are lacking however is a custom ROM for any of the arcs. More importantly than that we are lacking people to help us!

Weird, I could not install the ADB drivers from the SDK (Win 7 64-bit Enterprise). Had to use my trusted Nexus Root Toolkit and worked fine with that.
I'm liking it so far....appreciate your work to document the rooting procedure.
Let's hope development will pick up at some point, it's a good device (I have the ARC 10HD - got it on sale + coupon in Canada).

Been meaning to ask: have any of you guys found a good screen protector for the Arc 10HD?
I realize this is off topic (sorry OP) but I feel there is ZERO chances I would get an answer elsewhere than in this thread - the only valuable one on XDA re Kobo.

Ipse_Tase said:
Been meaning to ask: have any of you guys found a good screen protector for the Arc 10HD?
I realize this is off topic (sorry OP) but I feel there is ZERO chances I would get an answer elsewhere than in this thread - the only valuable one on XDA re Kobo.
Click to expand...
Click to collapse
Actually I don't, I have a leather case for mine that acts as a stand and protector,i don't sell them either but I suspect that will change soon
Sent from my arc 10HD using xda app-developers app

Ipse_Tase said:
Weird, I could not install the ADB drivers from the SDK (Win 7 64-bit Enterprise). Had to use my trusted Nexus Root Toolkit and worked fine with that.
I'm liking it so far....appreciate your work to document the rooting procedure.
Let's hope development will pick up at some point, it's a good device (I have the ARC 10HD - got it on sale + coupon in Canada).
Click to expand...
Click to collapse
Bazaar, I thought they were the same drivers, well I'm glad it worked eventually, if you or anyone else wants to help with dev you could try searching if there are other devices with the same SoC , we are looking for same gpu/CPU combo that already has a working custom ROM.
Sent from my arc 10HD using xda app-developers app

Yep...I am looking in the Transformer TF-701t forums. I'm not on the software side of Hi Tech, so I'll have to do some reading as I am as frustrated as you with the lack of interest in this platform.
BTW: you may want to add to your tutorial that after booting in Recovery for the first time, the user should accept to make boot.img changes - as otherwise all the frequent updates will wipe the recovery you installed. I was too quick to reboot and now I have to push recovery again.
Or if you think this is not safe to make permanent (I did it on every other Android device I own) maybe that should be stated too. People might want to get OTA updates and it is my understanding that with a custom recovery you won't be getting them. Hell, I'm still hoping we will get a stock KitKat at some point.
Thanks...for being the only one that cares
PS. From what I read about Netflix (big user....I "cut the cord" a year ago) it seems we need 4.3 for Netflix to run in HD (DRM ****). All I can say is that I don't get HD now - so it seems true.
One good reason to hope for a Kobo upgrade. I am already plagued with Ouya being stuck at 4.1.2

Very surprised at the pack of interest in the Kobo tablets, given the impressive combination of awesome specs and very low price. Have an Arc 7 32gb and an Arc 7 16gb in the family and gathering my forces to root em both.
I've read the forum but am a bit thick. Bottomline, are the root guides here conformed working on the latest updates since November 2013?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

JoshReuben said:
I've read the forum but am a bit thick. Bottomline, are the root guides here conformed working on the latest updates since November 2013?
Click to expand...
Click to collapse
I just rooted my ARC 10HD 2 days ago, AFTER it got the last update (something one cannot prevent when setting it up for the first time).

JoshReuben said:
Very surprised at the pack of interest in the Kobo tablets, given the impressive combination of awesome specs and very low price. Have an Arc 7 32gb and an Arc 7 16gb in the family and gathering my forces to root em both.
I've read the forum but am a bit thick. Bottomline, are the root guides here conformed working on the latest updates since November 2013?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Should work fine, they updated the bootloader a couple of days ago on the 10HD but nothing appears to have changed, some system updates, some app updates, not a lot else from first impression
Ipse_Tase said:
I just rooted my ARC 10HD 2 days ago, AFTER it got the last update (something one cannot prevent when setting it up for the first time).
Click to expand...
Click to collapse
it updated the other day. ive been away for a bit so cant be sure when.

Kobo contact
I could not find a way to send an email to Kobo support or get in touch with someone in this company. As a legitimate user I have a legitimate question for them: what are the plans moving forward with software upgrades?
They don't seem to realize that part of the problem of not selling more devices is also the complete lack of communication (including advertising) from this company.
Mind blowing...
That being said, I love my Arc 10HD and seeing how much better my old Xoom is with KitKat, I can only imagine what it would mean for the Kobo family.
PS. I ended up buying this screen protector:
http://www.illumishieldstore.com/iL...e-Anti-Fingerprint-Replacements/dp/B00F6FJHNU

Ipse_Tase said:
I could not find a way to send an email to Kobo support or get in touch with someone in this company. As a legitimate user I have a legitimate question for them: what are the plans moving forward with software upgrades?
They don't seem to realize that part of the problem of not selling more devices is also the complete lack of communication (including advertising) from this company.
Mind blowing...
That being said, I love my Arc 10HD and seeing how much better my old Xoom is with KitKat, I can only imagine what it would mean for the Kobo family.
PS. I ended up buying this screen protector:
http://www.illumishieldstore.com/iL...e-Anti-Fingerprint-Replacements/dp/B00F6FJHNU
Click to expand...
Click to collapse
Ask your question at http://kobo.frontlinesvc.com/app/ask
They are usually pretty quick to get back to you, as for upgrades, I've not heard any news of anything so really don't know what the official line is, I've not heard any news on new devices either so we may get at least one supported is upgrade. Ideally though we need to nail our own ROM to be sure
Sent from my arc 10HD using xda app-developers app

[Q] Have TWRP No OS no SU can't install os

Hey everyone. Long time lurker, first time poster, and always grateful.
Okay, so I took a good look at some related threads. They all seem to have been resolved by using tools specific to their particular device. I have not had luck following their lines. So, here's what's up with me:
Asus Transformer Tf700 US edition
Had Cyanogen Mod. Wanted to sell my tablet, so I decided to wipe and go back to factory. Unfortunately, while fooling around in TWRP, I managed to putz it up and wipe the system and data. So no more OS, and apparently no more super user (whoops), although I may be wrong about that.
I can reboot the device into TWRP, but I can't mount the microsd card. When I plug my microsd card into my device, I just get an error that says cannot mount external sd card. So, since that isn't working, I've tried to sideload via adb.
I have the SDK but can't run ADB sideload because ADB on my computer does not recognize my device. I have tried to install updated drivers, though the drivers that I did find, when I point windows to the folder with them, it doesn't see a driver. SO maybe I'm doing that wrong.
I'm completely at my wit's end here. Can someone give me a little help?
Thanks everyone for your help in advance.

Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979

berndblb said:
Specifics please????
CM, TWRP, Windows, drivers: What version?
You may want to try this, it installs the drivers for you: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Hey there, thanks so much for replying!
I'm using TWRP v2.6.0.0.
Windows 7 x64 SP1
The CM version that I had, I actually don't recall now. I had flashed it back to stock though, before this, by using TWRP recovery. I noticed after that that I had not flashed my saved files properly. That's when I pooched it, hah.
I removed the existing USB drivers via device manager, restarted, used the installer that you linked to, restarted, and plugged in my device. It said installing drivers, and then failed to install drivers. ADB does not recognize a connected device. Merp.

I still haven't had any luck. Does anyone have any ideas?

You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.

http://forum.xda-developers.com/showthread.php?t=2646279

berndblb said:
You have to get the Windows drivers working to get ADB and fastboot access to your tablet and that can be tricky. Any chance you can get your hands on a Linux machine?
If the ADB tool I linked to didn't work (and I don't understand why - I used it on Win7 32 bit without a hitch) try to install the Google Universal Naked Drivers (google the term and should find them easily).
Actually - do you have the Asus device drivers installed? What happens if you connect the USB cable? Does Windows recognize the device at all? If not try to download Asus Sync, install it and try again. Once Windows recognizes the tablet as a MTP device, run the adb tool again and then try "adb devices" when you are booted into Android and "fastboot devices" when the tablet is in fastboot mode.
Click to expand...
Click to collapse
Hey, thanks for the reply. When I plug in the device, it tries to install drivers and almost immediately fails. It then shows in the device manager as shown in the attached file. When I right click, select update driver, and point it to the folder with the google naked drivers (or the asus drivers), it says that "Windows cannot find drivers for this device." This seems strange to me. It has no idea what the transformer is when it is plugged in. Is there a different manual method of installing drivers, or cuing windows to recognize that these are the correct drivers?
I had Asus Sync installed, and that didn't seem to do anything for me. Windows would not do anything differently than it had already done. Grrr. This hurts.
sbdags said:
http://forum.xda-developers.com/show....php?t=2646279
Click to expand...
Click to collapse
This method looks promising, but it requires one to go into Android and turn on USB debugging mode. Problem is: I have no OS to log in to in order to do so

Whoops, forgot screen shot

Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....

berndblb said:
Jeez - this is frustrating. I'm running out of ideas how to get Windows to work...
You are running Windows with administrator rights - yes?
Consider installing Linux as a dual boot on your Windows machine. I did that just to get rid of these ADB/fastboot driver problems....
Click to expand...
Click to collapse
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.

hardshank said:
I'm running shy on space on my OS SSD, but would it potentially work running off of a boot disk? I have Fedora lying around here somewhere. Would the process be especially different? I have so very little experience working in Linux.
Also, I wonder if this is important. When I tell TWRP to reboot the machine, it informs me that super user isn't installed, and offers to root my device for me, but when I select that option, the screen just goes blank and it appears to hang, and I have to reboot it with the volume and power keys.
Click to expand...
Click to collapse
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
I do not understand your driver problems at all. I helped someone today with a lot of the same problems: The tablet only booted into recovery, TWRP would not mount the microSD, didn't see any files on the internal... The ADB tool I linked to earlier allowed him to adb reboot to the bootloader - the rest was a breeze... Something in your Windows setup is just effed up... Sorry - wish I had that magic wand...

berndblb said:
I have no idea if you can run adb or fastboot if you boot Linux off a boot disc - but what the heck? Why not try it at this point?
Click to expand...
Click to collapse
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.

_that said:
Sure, if you have compatible adb and fastboot binaries it should work. Linux doesn't care where it was booted from.
Click to expand...
Click to collapse
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?

berndblb said:
I had to install the adb and fastboot binaries on my distro. You can't do that on Linux running off a disc - can you? You would have to find a distro that comes with them?
Click to expand...
Click to collapse
On some live distros you can install additional software to a ramdisk. For adb and fastboot, any live distro with 32 bit libraries should have the required libs so that you can just copy/download the binaries and run them.

So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....

hardshank said:
So here is an interesting development: I am now able to see my micro SD card when it is plugged into my device. Why? I haven't the foggiest. However, I still can't see any of its contents. Curious....
Click to expand...
Click to collapse
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!

hardshank said:
Okay. I can't believe this worked, but I'm back in action. Here's how it went down:
- I tried doing a Linux USB drive, but was having difficulties getting it to boot, and my knowledge of Linux is so limited, I basically gave up hope.
- Today, I picked up my tablet (which has remained plugged in for power all of this time), and rebooted it. At the opening screen, which allows me to choose to go into TWRP, boot into (I think) Linux, or wipe data, I had never selected Wipe Data. Why? Because accidentally wiping the wrong partition is what got me in this mess to begin with.
- SO then I think, what the hell. It seems to have actually done something (though I don't know what), so I grab my micro SD with stock Android loaded on it, and pop it in. Voilà! It is recognized (as above).
- For some reason, no contents of card are visible
- Restarted device: card contents visible!
- Selected "Install" in TWRP menu, and selected my stock ROM
So. This has been a weird month. Thank you to EVERYONE who helped out on this. I'll be sure to hit the Thanks buttons!
Click to expand...
Click to collapse
Glad you got it working!
Out of curiosity: Was your tablet booted or completely off until you picked it up today? Did you reboot into the bootloader or did it do that by itself?
Sent from my ASUS Transformer Pad TF700T using Tapatalk