Related
This is it guys... HUGE props to bigrushdog (his kernel made this possible!), MADindustries and modplan!
Download the Motorola WiFi Xoom Root Zip file and unzip it. (MediaFire) - Contains Tiamat 1.3.1
You need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
You'll need fastboot - get it here http://developer.htc.com/adp.html
Make sure you have the latest SDK - adb and fastboot should be in /platform-tools - http://developer.android.com/sdk/index.html
Place the files in the SDK Tools folder.
If rebooting works... - This will wipe your phone by the way!!
adb reboot bootloader
fastboot oem unlock
adb reboot bootloader
If stuck at "Dual Core Technology"
Hold VolUp and power to restart Xoom
Hold VolDown will booting unit for fastboot mode
fastboot flash boot boot.img
fastboot reboot
adb shell
mkdir /data/media/sdcard2
exit
(physically put in microSD card if you are planning to use)
adb reboot
adb remount
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
adb push su /system/bin
adb shell ln -s /system/bin/su /system/xbin/su
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app
adb push vold.fstab /system/etc/vold.fstab
adb reboot
adb shell
WE HAZ ROOT!!
Check out this video for basic Windows walkthrough from Buddhahb - http://www.youtube.com/watch?v=ZsVpY0PDwtQ
Check out this video for basic Mac walkthrough from sleeplessninjas - http://www.youtube.com/watch?v=zC6J-hV6SM4
Update: 3/27/2011 12:04pm CST Added cifs.ko, tun.ko, and scsi_wait_scan.ko
Update: 3/27/2011 12:22pm CST Added vold.fstab file for USB mounting & MegaUpload
Update: 4/13/2011 10:07am CST Updated to Tiamat's 1.3.1 kernel for SD card support & Gallery support.
awesome work guys!
Woooooooooooooooooooooooooot
fantastic work!!
\o/
can you try the cifs.ko module as well? i have a 3g version and am curious
Thanks Xaositek and HUGE props to MADindustries and modplan for coming up with a quick solution.
Is there a rip of the stock "boot.img" in case it doesn't work so that people who soft brick their xoom can return it back to stock? If so can that be posted in the OP's post? I know I am not the only paranoid one that would like to have the stock boot.img before attempting any rooting.
Also just for curiousity, can someone explain the differences between the wifi and wifi+3g boot.img versions and what they had to do to workaround this. Thanks.
We end up replacing the stock boot - We'll probably need to wait for Motorola to toss us a bone there
I just downloaded the "xoomwifiroot.zip" file and realized the files in the "xoomwifiroot.zip" are just tiamat's 1.1.6 files (boot.img and kernel modules) that can be found in tiamat's thread.
I was expecting the files to be something different that was close to the original root method by Koush where there is a "rootboot.img".
Maybe a better question for my understanding is this. Sorry if I am a noob.
Is Koush's file rootboot.img for the original xoom root only good for rooting the system while tiamat's boot.img file not only roots the system but also has code to overclock the xoom?
ericdabbs said:
I just downloaded the "xoomwifiroot.zip" file and realized the files in the "xoomwifiroot.zip" are just tiamat's 1.1.6 files (boot.img and kernel modules) that can be found in tiamat's thread.
Click to expand...
Click to collapse
It also has the su and Superuser.apk but essentially yes...
ericdabbs said:
Is Koush's file rootboot.img for the original xoom root only good for rooting the system while tiamat's boot.img file not only roots the system but also has code to overclock the xoom?
Click to expand...
Click to collapse
Koush's rootboot got us into this mess, Tiamat's boot.img got us out of it. It also allows the critical adb remount to allow the next steps.
Xaositek said:
It also has the su and Superuser.apk but essentially yes...
Koush's rootboot got us into this mess, Tiamat's boot.img got us out of it. It also allows the critical adb remount to allow the next steps.
Click to expand...
Click to collapse
Gotcha. Thanks for all your help.
ericdabbs said:
Gotcha. Thanks for all your help.
Click to expand...
Click to collapse
Grab the latest file from MegaUpload and add the additional modules
glad I could help get this working and glad that it fixed my bricked xoom! One thing that I would suggest is someone pull the stock ko files and save them, after moto releases the stock boot.img files I am sure that there will be some people that want to go back to the stock kernel which will then be as easy as flashing the stock boot.Img and then pushing the stock ko files back on.
Guess I'll run out and grab one now at Best Buy then. Thanks!
modplan said:
glad I could help get this working and glad that it fixed my bricked xoom! One thing that I would suggest is someone pull the stock ko files and save them, after moto releases the stock boot.img files I am sure that there will be some people that want to go back to the stock kernel which will then be as easy as flashing the stock boot.Img and then pushing the stock ko files back on.
Click to expand...
Click to collapse
Is there a way to extract the stock boot.img and wifi ko files before flashing it with tiamat's files? If so, what are the instructions so that people who haven't rooted it yet can give it a try. That way we can give back to the community.
ericdabbs said:
Is there a way to extract the stock boot.img and wifi ko files before flashing it with tiamat's files? If so, what are the instructions so that people who haven't rooted it yet can give it a try. That way we can give back to the community.
Click to expand...
Click to collapse
Pulling the boot image looks like it is rather difficult but pulling the ko files should be as simple as using the adb pull command instead of adb push. For example
Adb pull /system/lib/modules/something.ko c:/something.ko (put the right paths obviously the second path is just where you want to save it on your computer)
As an FYI. coolbho's ocboot.img does not work on the wi-fi version of the xoom yet. To prevent your headaches I have already flashed and it stays at boot screen. Tiamat's seems the only kernel that is working for wi-fi only
modplan said:
Pulling the boot image looks like it is rather difficult but pulling the ko files should be as simple as using the adb pull command instead of adb push. For example
Adb pull /system/lib/modules/something.ko c:/something.ko (put the right paths obviously the second path is just where you want to save it on your computer)
Click to expand...
Click to collapse
Got it. When I get my wifi xoom, I'll give this a shot.
d3coy3d said:
As an FYI. coolbho's ocboot.img does not work on the wi-fi version of the xoom yet. To prevent your headaches I have already flashed and it stays at boot screen. Tiamat's seems the only kernel that is working for wi-fi only
Click to expand...
Click to collapse
Tiamat's kernel allows for the 1.5ghz OC
When i command to push the first file, I get all the info on android debug.
chaz03 said:
When i command to push the first file, I get all the info on android debug.
Click to expand...
Click to collapse
Revisit the instructions now - you can just copy and paste them all now
This is my personally compiled kernel for the Kindle Fire with a few optimizations.
Acknowledgments:
DooMLoRD - for helping greatly in my initial trials on how to create kernels for the Fire
g1011999 - for providing a working .config
paulobrien - insecure boot image
franciscofranco - for some of the ARM optimizations which I've missed since I stopped modding the N1
hashcode - the 3.0 kernel base
Features:
- compiled using Mjolnir
- CPU overclocking code from OMAPZOOM repositories
- ARM code optimizations
What doesn't work:
same bugs as Hashcode's
Download URL:
http://intersectraven.euroskank.com/kernels/
Latest Changes:
20120730_08XX:
- backported cleancache and zcache improvements from 3.4
20120709_1619:
- added further tweaks to interactive scheduler
- rebased experimental optimization to minimize chance of faulty merge
20120703_1041:
- rebased to hashcode's 3.0.31 kernel with support for the touchscreen filter
- added an experimental optimization which in theory should make the kernel a bit more responsive...at least in theory...
20120619_2251:
- numerous ARM optimizations (most from the 2.6 series)
- ported CM's changes to the interactive governor and low memory killer
- GPU driver is compiled into the kernel
20120601_1145:
- integrated latest BFQ release 4 for selection (not default) in SetCPU
20120513_1557:
- integrated shutdown fix from hashcode
20120512_2044:
- first 3.0 release with almost all my tweaks
20120216_1740:
- final fix for TUN without module (if it still doesn't work, going to module in next release)
- UTF8 support for file systems
- some optimizations
20120211_1219:
- minor update for fixing OpenVPN based VPNs
20120207_19XX:
- unification release (unified all my modifications with my Galaxy Nexus kernel and restarted from scratch)
- ARM optimizations
- OC without thermal control
- compiler optimizations
- CIFS and TUN enabled
- now based on 2.6.35.14
- now in zip version for easier flashing
***DEPRECATED***
Instructions (stock WiFi driver):
1.) Boot to fastboot
2.) Test first using fastboot boot command
Instructions (custom WiFi driver):
1.) Turn off WiFi.
2.) Use adb push command to push tiwlan_drv.ko to /sdcard/
3.) Using root explorer, rename tiwlan_drv.ko from /system/etc/wifi to tiwlan_drv.ko.bak.
4.) Usring root explorer, copy tiwlan_drv.ko from /sdcard/ to /system/etc/wifi. Make sure permissions are same with other files in directory together with owner and group being set to root.
5.) Reboot to fastboot and TEST FIRST using fastboot boot command
Detailed instructions are on the next post.
***DEPRECATED***
GitHub:
http://www.github.com/intersectRaven/kindle-kernel
Detailed Instructions:
Turn off your device's WiFi.
From your command prompt issue the ff. commands:
Code:
adb shell
su
idme bootmode 4002
reboot
This will cause your kindle to reboot to fastboot mode. Issue the ff. commands:
Code:
fastboot -i 0x1949 boot bootnew.img
This will cause the Kindle to boot TEMPORARILY to the new kernel which I assume you downloaded from me.
If it doesn't boot normally, you can turn off your Kindle by holding down the power button for at least 10 seconds then turn it on again.
This will boot your Kindle to fastboot mode again.
If the kernel didn't work:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
This will reboot your Kindle back to normal.
If the kernel worked, here's how to flash it permanently:
Code:
fastboot -i 0x1949 flash boot bootnew.img
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
This should boot up with the new kernel.
Once you've booted up properly, issue the ff. commands to replace your stock WiFi driver with the new one.
Code:
adb push tiwlan_drv.ko /system/etc/wifi/
adb shell
su
cd /system/etc/wifi
chmod 644 tiwlan_drv.ko
Ensure that the permissions, owner and group settings for the new WiFi driver are correct by issuing:
Code:
ls -l
Turn on your WiFi.
Partition Backup Instructions:
From your command prompt, issue the ff. commands:
Code:
adb shell
su
This should give you superuser command prompt on your Kindle Fire. To confirm,
you should see a # as your command prompt. Next, issue the ff. commands to backup the smaller partitions to your sdcard. Make sure that the sdcard isn't mounted on your computer so that it is accessible to the Kindle Fire.
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/xloader.bin
dd if=/dev/block/mmcblk0p2 of=/sdcard/bootloader.bin
dd if=/dev/block/mmcblk0p3 of=/sdcard/dkernel.bin
dd if=/dev/block/mmcblk0p4 of=/sdcard/dfs.bin
dd if=/dev/block/mmcblk0p5 of=/sdcard/recovery.bin
dd if=/dev/block/mmcblk0p6 of=/sdcard/backup.bin
dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.bin
After executing those commands, you can now mount the sdcard through USB and copy those files to your HD for backup purposes. The remaining partitions through 8 - 11 can be backed up as well but I'll leave that to your own discretions. These partitions were chosen because they're either critical or unreplicable.
You can also use adb to pull the images above directly to your PC. Here're the commands to do so:
Code:
adb pull /dev/block/mmcblk0p1 xloader.bin
adb pull /dev/block/mmcblk0p2 bootloader.bin
adb pull /dev/block/mmcblk0p3 dkernel.bin
adb pull /dev/block/mmcblk0p4 dfs.bin
adb pull /dev/block/mmcblk0p5 recovery.bin
adb pull /dev/block/mmcblk0p6 backup.bin
adb pull /dev/block/mmcblk0p7 boot.bin
for stock only?
JackpotClavin said:
for stock only?
Click to expand...
Click to collapse
Yeah. There's still a couple of glitches though. Seems connecting USB crashes everything.
And wifi doesn't work?
Sent from my Kindle Fire using xda premium
Veritass said:
And wifi doesn't work?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Yup. That's why it's marked INCOMPLETE in the title.
Stock Wifi works now!
*a bit flaky though...drops every now and then...still fixing...
great work mate!!!
have u uploaded sources to git?
also can u please send link of correct toolchain to use?
Have you tried to compile the bluetooth module? I still believe that the Kindle has Bluetooth support
DooMLoRD said:
great work mate!!!
have u uploaded sources to git?
also can u please send link of correct toolchain to use?
Click to expand...
Click to collapse
I'm still thinking of how to quickly upload to git.
As for the toolchain, anything should work. I've fixed my source to use Mjolnir though since I need it for some planned compiler fixes I want to use.
N23 said:
Have you tried to compile the bluetooth module? I still believe that the Kindle has Bluetooth support
Click to expand...
Click to collapse
Not yet. I was quite busy with fixing the WiFi module loading (since it's a pain to build) so I haven't looked at that. Also, even if I enable it, there's no support in the stock ROM so we need CM7 (or 9) to work as well.
intersectRaven said:
I'm still thinking of how to quickly upload to git.
As for the toolchain, anything should work. I've fixed my source to use Mjolnir though since I need it for some planned compiler fixes I want to use.
Not yet. I was quite busy with fixing the WiFi module loading (since it's a pain to build) so I haven't looked at that. Also, even if I enable it, there's no support in the stock ROM so we need CM7 (or 9) to work as well.
Click to expand...
Click to collapse
no problems mate
btw seems one of the kernels i posted yesterday boots, atleast for one user :
http://forum.xda-developers.com/showthread.php?p=20130507#post20130507
regarding wifi, do u have any idea which model of TI chipset is there?
i have the following repo for patched TI modules for Xperia 2011 devices... give it a shot if it works for Kindle Fire...
https://github.com/DooMLoRD/Xperia-2011-TI-WLAN
DooMLoRD said:
no problems mate
btw seems one of the kernels i posted yesterday boots, atleast for one user :
http://forum.xda-developers.com/showthread.php?p=20130507#post20130507
regarding wifi, do u have any idea which model of TI chipset is there?
i have the following repo for patched TI modules for Xperia 2011 devices... give it a shot if it works for Kindle Fire...
https://github.com/DooMLoRD/Xperia-2011-TI-WLAN
Click to expand...
Click to collapse
Thanks for the info! I'll try that later. Fyi, I tried the one in Amazon's release and it didn't work but maybe I did something wrong. I am quite unfamiliar with compiling modules outside of the kernel tree.
*Seems you modified it heavily to prevent reliance in outside export commands.
intersectRaven said:
Thanks for the info! I'll try that later. Fyi, I tried the one in Amazon's release and it didn't work but maybe I did something wrong. I am quite unfamiliar with compiling modules outside of the kernel tree.
*Seems you modified it heavily to prevent reliance in outside export commands.
Click to expand...
Click to collapse
me too
hahahha... yes i had to got bored with long commands
just the msm_env.bash is changed...
DooMLoRD said:
me too
hahahha... yes i had to got bored with long commands
just the msm_env.bash is changed...
Click to expand...
Click to collapse
Forgot to mention that the WiFi is wl1283.
intersectRaven said:
Forgot to mention that the WiFi is wl1283.
Click to expand...
Click to collapse
On the Wifi chip, a quick look at Chipworks indicates that not only does the WL1283 have bluetooth, but also GPS. Providing that its wired up right inside, should we also be able to get GPS working as well? Or is it missing the GPS antenna to make it work?
jcatt said:
On the Wifi chip, a quick look at Chipworks indicates that not only does the WL1283 have bluetooth, but also GPS. Providing that its wired up right inside, should we also be able to get GPS working as well? Or is it missing the GPS antenna to make it work?
Click to expand...
Click to collapse
Might have to add the GPS antenna if anything, but bluetooth could be possible. We just dont know if it has to be enabled in software or if it cant due to the hardware
jcatt said:
On the Wifi chip, a quick look at Chipworks indicates that not only does the WL1283 have bluetooth, but also GPS. Providing that its wired up right inside, should we also be able to get GPS working as well? Or is it missing the GPS antenna to make it work?
Click to expand...
Click to collapse
interesting... the TI driver i have (for Xperia 2011 devices) is WL1273... i have talked to a developer friend and he told me that WL12xx drivers are unified so we can try those drivers too...
Downloading the source here in a bit, but I had a few questions.
Can you check the gpu config? I believe its 1.7 pvr driver but the 3d memory has been cut down a bit. I'm not sure if it'd be possible to move some of that back w/o affecting other optimizations in the kernel. The reason I ask, is that I know ICS/tablet apps would run better with a bit more dedicated 3d mem.
I noted that CM7 was having some audio issues, is the kernel using a stock SoC/Alsa config? Or did they do something odd?
Lastly, I applaud you guys for grinding this out, it's always best to start from the ground up. Great work!
Sent from my DROID3 using XDA App
Kernel updated! See OP for changes.
I've compiled two additional ppp modules for franco's Galaxy Nexus kernel. These fix the I/O error with Sonicwall Netextender and maybe other apps. I would post these in his development thread but for now I'm under the 10 post count and can't. I take no responsibility if this blows up your phone, makes your toaster come to life or anything else you may come up with. Use at your own risk.
Short howto (assuming your on a computer):
Unzip the correct ppp-(version).zip from below (this gives you two files ppp_async.ko & ppp_synctty.ko)
Use adb to push both files to /sdcard/ (example: adb push ppp_async.ko /sdcard/)
Use adb shell or terminal emulator and navigate to /sdcard/
Insmod both modules (example: insmod ppp_async.ko & insmod ppp_synctty.ko) in your shell. This step will have to be done on each reboot.
*** I have only tested this on CDMA GNEX ***
For Franco's GNEX 18.4 kernel: http://dl.dropbox.com/u/19832908/ppp-franco/18.4/ppp-18.4.zip
Sonicwall released there new Mobile connect client today which appears to no longer require the extra ppp modules.
https://market.android.com/details?...yLDEsImNvbS5zb25pY3dhbGwubW9iaWxlY29ubmVjdCJd
Sent from my Galaxy Nexus using Tapatalk
How to enable ADB on ALLWINNER A13 9" - 4.2.2 - Windows 7 - error:device not found
Hi folks, my target is to do a full backup of my android tablet device without rooting nor installing app's on the device. It can be done just by the ADB tool and the simple command
Code:
adb backup -apk -shared -all
.
Basic information
PC: Windows 7, pro. USB 2.0 port. ADB Driver "Drivers-AllwinnerA10-32bits\32Bit_Win_7_Vista_XP" from 2011. ADB Platform-Tool, Android Debug Bridge version 1.0.31. Logged in as normal User, not Admin. The development kit is not installed, I just downloaded the Platform-Tool, unzipped it and started "adb" - I just want to make a f***ing backup :crying:
Tablet:
ALLWINNER A13 9". Android Version 4.2.2. USB Debugging enabled. Detail Info's:
Model number: JL902
Kernel Version: 3.4.0+ [email protected] #1 Mon 25.11.2013
Build-Number: full_gs702c-userdebug 4.2.2 JDQ39 eng.root.20131207
NOT ROOTED.
Problem:
I do not get a connection from the PC to the tablet. Also no RSA Key question comes up at the tablet. The adb tool just throws an error :"device not found". I tried several things, log in as Admin, "adb wait-for-device", plugging and unplugging ... nothing helped. The adb tool works fine, I tested it with a Samsung Galaxy S2. I'm not quite sure about the adb USB driver on windows, but there is no exclamation mark nor other problems reported. So this should be fine.
Anyone any hint, tip or solution? Would be great - gathering for hours with this problem - searching forum 'n stuff....
Thanks in advance
Juha
Try with uberizer or MTKDroid tools. Just connect and select adb terminal.
kramkumar said:
Try with uberizer or MTKDroid tools. Just connect and select adb terminal.
Click to expand...
Click to collapse
Thx 4 the hint, tried uberizer:
Code:
ERROR No useable device has been found
I think since in Android 4.2.2 the RSA Key authentication was introduced, something is wrong with the connection. Because I would expect the RSA Key question on the tablet, but the tablet does not show this dialog.
By the way, I recognized that the USB driver for the ADB interface is titled "Drivers-AllwinnerA10" but the tablet has a A13 core. But I do not find another driver at the moment and the vendor ID -VID_10D6&PID_0C02&REV_0202&MI_01- fits (otherwise, windows wouldn't install it anyway). Does it make sense to search for another driver?
hi from messing with various drivers and android devices i have found that installing PDA net for windows (theirs and android version too but not needed) once pdanet installs let the drivers for your phone be installed, if by any chance you have drivers already installed what you can do is go to device manager, click on your device uninstall the drivers, unplug your phone and then open pdaNET a window will come up waiting for you to connect your phone and the driver installation process will begin.
The program downloads the correct driver for mostly any model phone you have and works flawlessly with ADB, if by any chance this helped just give me a thanks !
abstractVoid said:
The program downloads the correct driver for mostly any model phone you have and works flawlessly with ADB, if by any chance this helped just give me a thanks !
Click to expand...
Click to collapse
Thanks for the tip. It really installed an USB driver as you said (I've deinstalled the other driver before). But sadly the result is the same. I can't access the ADB interface - same error "Device not found".
At this point I want to say thanks to all viewers of this thread, it seems really to be not an easy task. I'm still open minded in any direction and would be happy for any suggestion what I might try.
Even a hint, how I could reduce the possibilities for the root of my problem. I'm still not quite sure, if the driver is the problem or even if the tablet itself has some kind of software defect on this kernel version - By the way, does anyone have the same kernel version (posted at the beginning - 3.4.0+ [email protected] --- repeated for your convenience) of Jelly Bean (4.2.2)? Do you have experience with the ADB interface then?
How may I isolate the real problem? Any idea wellcome :cyclops:
I have nearly an identical tablet except mine has the PnP code of Vendor 10D6/Device 0C01 and it shows as P706 on the USB description.
I installed PDAnet, that actually was able to upload the Android version of PDAnet to the tablet, so I think that's a definite for the driver working. But I'm also having trouble getting ADB to list the device and I'm using the latest ADB from the SDK. Since ADB tries to setup a network server, I'm wondering if the ADB driver on windows has to be tethered as a NIC somehow?, just a theory.
I'm using a fresh install of XP and can do a complete rollback, so I'm certain it's not the OS.
There's also another quirk about this tablet. I wanted to do a backup of the firmware from this device. Techknow's utilities use ADB to issue several shell commands to copy "partitions" to the SD card, I thought I might as well try to do that manually only to find what would've been copied as /dev/block/nanda, nandb, etc. is named /dev/block/acta, actb, etc. instead. But lack of "root" means I can't read any of those partitions or even copy su into /sbin.
Uberizer isn't any good since as far as I can see that also uses ADB. Any known issues with versions of ADB? or even any other tools which do similar to ADB?, or even a way to "root" these devices just by Terminal and SD?
Regards
Ah, okey, soz I got the USB thing a bit mixed up. My tablet does have the same code, I assume the 0C01 is when it's in recovery mode (power on with volume + pressed)
I also realised the driver that was working wasn't one from PDAnet.
I've updated the working 32-bit driver with the version of ADB I'm using and included it in the attachment. Maybe you can try that and see if you have any progress.
I'll keep posted on this thread.
SOLVED!
Copy .android from the attachment into your %USERPROFILE% directory (i.e. C:\Document and Settings\<user> on XP or C:\Users\<user> on Windows 7)
You can check what the user directory is by DIR %USERPROFILE% in the "DOS" command line (%USERPROFILE% is case sensitive).
ADB should list your device when you do adb devices in the "DOS" command line.
Basically, adb_usb.ini with a custom identifier was missing.
Regards,
qUE
Right, I've made up a pack to automate putting SU on the device and setting up permissions on SU and BUSYBOX.
!!! This is only for the VID_10D6&PID_0C02 device, your mileage may very with other devices. !!!
DRIVER directory should contain the USB driver you need, otherwise try installing PDAnet and tell it to replace the driver.
Install USB driver, run SUME.BAT
to hopefully backup all the needed stock firmware to SD;
adb shell
su
cat /dev/block/acta > /mnt/sd-ext/acta.img
cat /dev/block/actb > /mnt/sd-ext/misc.img
cat /dev/block/actc > /mnt/sd-ext/system.img
exit
exit
adb kill-server
qUE
Confirmed solved
qUE-ARM said:
SOLVED!
Copy .android from the attachment into your %USERPROFILE% directory (i.e. C:\Document and Settings\<user> on XP or C:\Users\<user> on Windows 7)
<SNIP>
Basically, adb_usb.ini with a custom identifier was missing.
Click to expand...
Click to collapse
CONFIRMED SOLVED
Yes, that was it! I copied the adb_usb.ini file into the .android user directory (which only contains these ascii chars "0x10D6" - no CR no LF or anything else) and it worked out !!!
Thank you (Thanks meter will follow ) Some interesting things I discovered now:
There was no RSA-Key question at all on the tablet!!!
as I did the full backup with "adb backup -apk -shared -all" I was asked on the tablet to confirm this
So obviously something strange is going on here. Since it is claimed everywhere the with Android 4.2.2 the ADB interface should be generally RSA-Key protected. Okay, might be that I misunderstood something here :silly:
At least this problem is solved and I appreciated every comment in this thread. One question would be final to answer:
Who should have brought the adb_usb.ini to my PC. The ADB driver ? The ADB Platform-Tool package? So, whom to blame here - NO - just kidding :laugh:
I did briefly try the platform-tools (since I didn't mind the OS being trashed), they didn't add any adb_usb.ini and there isn't any real indication the file was needed/didn't exist, they could've simply put a note on the ADB utility when it didn't find any devices.
I'm not sure what ADB backup does. As far as I know the mounted partition images are differently named to various backup tutorials, so I get the feeling ADB backup just simply copies the user data and not much else. I recommend doing the backup I mentioned as well, it'll at least capture a copy of the boot partition, which if the device doesn't have that you'll probably need to revert to using live suite or some other firmware utility to restore it. Getting the firmware for that is another story, read a fair amount of posts here and other places on the net that don't sound fun.
I personally still can't get superuser to behave for using su on the terminal/term.apk (I want to remove useless "system" apps and make sure the device isn't talking back to anyone, i.e. google), but I'll keep tinkering.
My main aim for getting one of these tablets was to boot other firmware from the SD slot, but it looks as if the u-boot process is locked to internal NAND. So might have to modify it by adding "fatload mmc" to the script.
qUE
Quick Update;
Right the permissions thing turned out to be an issue with Superuser, dunno why. So replace the su binary from SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053) into my SUME pack and install the Superuser.apk by;
adb root
adb shell mount -o rw,remount /system
adb push Superuser.apk /system/app
as for stripping back the Applications, I've got it down to this as bare bones
adb pull /system/app backup\system\app
to backup system applications before you do anything
I found if you do delete any applications and then android gets stuck at the logo, just adb push them back and it'll boot without reboot when you've got the chain right.
minimum applications needed for boot are;
DefaultContainerService.apk
DefaultContainerService.odex
SystemUI.apk
SystemUI.odex
Launcher2.apk
Launcher2.odex
Settings.apk
Settings.odex
SettingsProvider.apk
SettingsProvider.odex
ActSensorCalib.apk
InputDevices.apk
InputDevices.odex
FusedLocation.apk
FusedLocation.odex
LatinIME.apk
LatinIME.odex
PackageInstaller.apk
PackageInstaller.odex
ApplicationsProvider.apk
ApplicationsProvider.odex
A few odds and sods missing will make settings close, but it's trivial stuff. Personally don't like the sound of Fused Location, but it won't boot without it and I haven't seen any dodgey traffic from it (yet).
I recommend installing Droidwall with adb push /system/app, before installing games.
And modifying /etc/hosts with 127.0.0.1 to certain you know whos and advertisers.
Some of my personal choice replacement applications (so far);
Total Commander over ES file explorer.
Opera Classic over the inbuilt browser (although I'm still trying to remove the default search engine).
qUE
More update;
Discovered some new things;
BACKUP FILES WITH "ADB PULL" BEFORE MODIFYING ANY FILES!!!
I think performancepolicy.apk needs to be added to the bare bones application list, afaics from looking inside the package it sets system performance stuff, so likely throttling to preserve battery power.
bin_cfg.xml in /misc which can be modified by
adb shell mount -o rw,remount /misc
then adb pull, edit and push the file back
the line in there for "backlight_brightness" 780;1020;780 can be changed to 240;1020;240 which dims the backlight substantially saving battery power. not sure if 240 is the absolute minimum, but 120 seems to be too low afaics. interestingly information on the settings is in the files named _userview.xml
build.prop in /system which can be modified by
adb shell mount -o rw,remount /system
then adb pull, edit and push the file back
and then chmod 644 /system/build.prop
the lines in there for ro.wifi.signal.level.# can all be set to 0, this theoretically cuts the wifi power usage to less than 1mW, again saving battery. if android doesn't boot fully on reboot it's because chmod hasn't been set, you should be able to adb back in and correct.
please be careful modifying either file as both seem to have safety limits imposed on certain device components (i.e. battery temprature), messing with those can make the tablet stop working.
qUE
Hi everyone. I am experiencing problems trying to flash RR Nougat to my Oneplus 3, currently on CM13 6.0.1. It just won't flash at all. I've wiped cache etc but it doesn't want to execute. I've also tried Lineage OS but failed, I have even tried pushing the file via Unified Android Toolkit and even that didn't work. Phone has an unlocked boot-loader (I'm pretty sure) USB debugging, root access etc. Unsure what the issue is so any help would be appreciated. This is what happened whilst using UAT.
Working out the best location to set for Internal Storage..
Waiting for Adb Mode
Device mode detected [device adb]
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /sdcard/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
File push did not work for sdcard
Setting push location to mnt/sdcard and trying again
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /mnt/sdcard/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
File push did not work for mnt/sdcard
Setting push location to storage/emulated/0 and trying again
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /storage/emulated/0/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
An Error Occured
The file did not push to the set location for some reason
Please report this in your device thread with details for more help
Press any key to return to the Main Menu..
Thank You.
I don't really have an answer for you but recently I tried to go back to stock, after I locked my bootloader I was unable to sideload anything with adb, have you tried flashing it with TWRP? Just a suggestion, are you able to use recovery at all, if uat can't find the directory, it could be a PC issue? I'm just throwing out ideas to try to help.
Update your adb drivers, now command prompt can push files larger then several mb's, don't know precisely how much.
Same problem I had couple of weeks back, don't know why but mine adb driver changed, set it back to the Google adb driver from sdk and the file was sideloaded.
Make sure you are on the latest firmware that is required.
I would just transfer through mtp or download on your op3, then just flash trough TWRP. That's what I do.
sv2203 said:
Update your adb drivers, now command prompt can push files larger then several mb's, don't know precisely how much.
Same problem I had couple of weeks back, don't know why but mine adb driver changed, set it back to the Google adb driver from sdk and the file was sideloaded.
Click to expand...
Click to collapse
Yup follow his method. This issue is somekind of adb sideload bug for huge files, name too long or not run as admin. Restarting PC, reinstall driver OP3 driver is another option if problem still persists.