Related
I think all of you PS3 owners here already know about the Jailbreak tool that allows you too execute unsigned code on the PS3. That opens the console for a lot of homebrew possibilities(mplayer port maybe?). The source code for the exploit leaked and a dev called KaKaRoTo managed to get it to be executed from a N900. Yesterday KaKaRoTo released his souce code and today someone already ported it to the Palm Pre. This quick port was possible because the N900 and Palm Pre both share the same USB controller(mUSB) which happens to be the controller used by the Droid/Milestone.
Here is some info from KaKaRoTo's blog:
Q: How hard is it to port it to a new device ?
A: Well, I’ve just separated my code from the N900 specific stuff, so it’s quite easy, there are mainly two functions to write, one to get and one to set the USB address.. two other functions that only return some static result depending on the configuration of the controller (the name of the endpoints, and whether the controller supports high speed or full speed mode).
Read the README file provided with PSFreedom, and check the psfreedom_machine.c file for specifics on what to implement.
Q: How can I port it to a new device.
A: Well, first, you need to figure out what controller your device uses, in the case of the N900, it’s ‘musb’..
Then go to the driver code for that controller (probably in drivers/usb/gadget) and look for ‘SET_ADDRESS’. In the case of musb, it was in drivers/usb/musb/musb_gadget_ep0.c. In there it was setting the address to the USB device, so just copy that code into the psfreedom_machine.c to allow setting the address, and add a similar function to be able to retreive the address.
Then add a function to return 0 or 1 depending on whether the controller supports HIGH, FULL or LOW speed mode (go to usb_gadget_register_driver for your controller, and in the first lines, it should validate the speed argument, it will tell you which ones are acceptable), set LOW speed mode to return TRUE only if FULL speed isn’t available .
Finally, add a function to return the endpoint names.. it will usually be something like ‘epXin’ and ‘epXout’ (where X is the endpoint number), or “epXin-bulk”, etc.. look at how the driver initializes its endpoints or grep for “->name” in the file to find where it sets it…
That should be enough!
Ok this is it for now with the FAQ. Next time, I’ll tell you all about my experience, what problems I encountered and how I fixed them, maybe it will help others!
Click to expand...
Click to collapse
http://kakaroto.homelinux.net/
Some people over the HTC Desire boards are already working on a port but Desire's controller is a different one(MSM72K) so they might take some time and it will be of no use for us
http://forum.xda-developers.com/showthread.php?t=772795
So, any dev here willing to give it a try?
according to zzg in the desire forum, this is what you need to do. no source changes.
Well you don't really need any changes to get it compiled against Droid's kernel, a quick and dirty way by looking at psfreedom's make file:
make -C /path/to/droid/kernel/source M=/path/to/psfreedom/source ARCH=arm CROSS_COMPILE=/path/to/android_ndk/tree/build/prebuilt/linux-x86/arm-eabi-4.4.0/bin/arm-eabi- EXTRA_CFLAGS=-DENABLE_MUSB_CONTROLLER modules
Click to expand...
Click to collapse
You can get the source from motorola.
Has anyone been successful with the exploit?
On the wiki it shows that it's in progress, but no info on who is working on it
hxxp://psfreedom.com/wiki/index.php?title=Device_compatibility_list
The guys over in the Milestone thread are beginning to get somewhere it seems, and someone in the desire thread said they've almost got the Milestone version working.
Not sure it means anything to the droid-ers though
Ahhhh I want a Droid version! I wish I could code!
Patiently waiting for the Motorola Droid Port....
Anybody know who is working on milestone/droid port?
desolateone1 said:
according to zzg in the desire forum, this is what you need to do. no source changes.
You can get the source from motorola.
Click to expand...
Click to collapse
Tried that. It didn't work, though I'm not familiar with configuring kernels. I have a compsci degree, but I just haven't ever played with them. Didn't figure it'd be as simple as this but thought I'd give it a go for the community... anyone want to give me a new clue?
Edit: I configured the kernel with 'make defconfig'
Where did you get the motorola source kernel?
https://opensource.motorola.com/sf/projects/droid
http://tinyurl.com/droid-ks-ese81
http://android.git.kernel.org/?p=ke...1;hb=34485287cb92a298eb6110926b729bf40bf3ba69
The third link is to the kernel space tree and I took the "snapshot" from there.
Got the NDK from here...
http://developer.android.com/sdk/ndk/index.html
Confirmed working!!!
place linked files on root of sdcard
First do nandroid backup!
Then reboot into recovery fire up adb and
"adb shell"
"#cd /sdcard"
"#flash_image boot boot.img"
reboot into ROM normally
open a terminal
"$su"
"#mount -o remount,rw /system"
"#mv psfreedom.ko /data/psfreedom.ko"
"#insmod /data/psfreedom.ko"
Then do the normal Jailbreak/PSgroove/PSFreedom power off on and quickly hit eject
It will take a little longer to boot (this is good)
Then under the "Game" tab it will show two new icons "/app_home/PS3/Game" and "Install Package Files"
Done using Cyanogenmod 6
Excellent job devs!
Links: hxxp://dl.dropbox.com/u/8949251/psfreedom.ko
hxxp://dl.dropbox.com/u/8949251/boot.img
freehood4all said:
Confirmed working!!!
place linked files on root of sdcard
First do nandroid backup!
Then reboot into recovery fire up adb and
"adb shell"
"#cd /sdcard"
"#flash_image boot boot.img"
reboot into ROM normally
open a terminal
"$su"
"#mount -o remount,rw /system"
"#mv psfreedom.ko /data/psfreedom.ko"
"#insmod /data/psfreedom.ko"
Then do the normal Jailbreak/PSgroove/PSFreedom power off on and quickly hit eject
It will take a little longer to boot (this is good)
Then under the "Game" tab it will show two new icons "/app_home/PS3/Game" and "Install Package Files"
Done using Cyanogenmod 6
Excellent job devs!
Links: hxxp://dl.dropbox.com/u/8949251/psfreedom.ko
hxxp://dl.dropbox.com/u/8949251/boot.img
Click to expand...
Click to collapse
So just to make sure I am understanding correctly you are saying that this method is confirmed working for the droid? If so where did the work come from? Was this recompiled from another platform and if so what is the source?
-Z
zerosignal0 said:
So just to make sure I am understanding correctly you are saying that this method is confirmed working for the droid? If so where did the work come from? Was this recompiled from another platform and if so what is the source?
-Z
Click to expand...
Click to collapse
Yes I have tested and it works, I have already backed up a game, and used the ftp server.
The work came from several people in #PSFreedom on irc.freenode.net
I think you are asking how was the module compiled, afaik it was from a 2.6.32 droid kernel.
Also you should note that when you flash the modded boot image Charging does NOT work you should have adequate battery BEFORE trying and you should flash back to your old boot image with an advanced nandroid restoring the boot image.
freehood4all said:
Yes I have tested and it works, I have already backed up a game, and used the ftp server.
The work came from several people in #PSFreedom on irc.freenode.net
I think you are asking how was the module compiled, afaik it was from a 2.6.32 droid kernel.
Also you should note that when you flash the modded boot image Charging does NOT work you should have adequate battery BEFORE trying and you should flash back to your old boot image with an advanced nandroid restoring the boot image.
Click to expand...
Click to collapse
Awesome! Thanks for the info, I was just wondering where the dev work was coming from. Also thanks a bunch for the boot_image heads up because I was just about to flash it over but wouldnt have been able to test it for a few hours.
-Z
So this may seem like a dumb question but I have the backup manager files and such but am not sure where on the sdcard to place it. Also what is the path you are supposed to use on the hdd (both internal and external) to place backups and write backups?
zerosignal0 said:
So this may seem like a dumb question but I have the backup manager files and such but am not sure where on the sdcard to place it. Also what is the path you are supposed to use on the hdd (both internal and external) to place backups and write backups?
Click to expand...
Click to collapse
Place any .pkg files on the root of a thumb drive thats formated to FAT32
As for backups you can put backups under /dev_hdd0/game/LAUN12345/GAMEZ "This is the path if you are using the original backupmanager.pkg and not some stealth backupmanger"
For games on an external I believe you put a folder named "GAMEZ" on the root of HDD. I haven't tried with external yet, so correct me if I'm wrong.
I will let you know when I get out of work. I have setup and saved my rom with the kernel changes so I can quick change when necessary. Thanks for the update on the file paths as well.
-Z
I'm totally lost right now can someone walk me through on how to do this? I have cm6 on my droid
You essentially are kinda following the same steps for flashing the boot image for getting manual root and some older roms. The instructions are pretty straightforward but make sure that you take a nandroid backup before making any changes.
I am running chevys SS 4.7 rom but I believe the kernel versions should be the same. As soon as I get out of here Ill update with the results.
-Z
Hi, everyone
I hope that I am in the right part for posting? I am new to this android thing.
I am trying to find a how to root idea usa 7" tablet from fry's for $77.00. Their is a lot of rooting programs but I have not been able to find anything on this model.
Also what would be a good rom to flash it with? I tried finding out if uberoid and cyanogenmod would work but I could not find any info on this model.
Not to sure what model I have that I would be able to flashing this rom with, either uberoid or CM7? Help
Model: MID, sv7206 v1.4, kernel 2.6.35.7-infotm
processor armv6 rev5,
hardware imapx200,
android 2.3.3,
brand infotmic,
display gri40,
release codename REL
bootloader unknown
I don't know if this is the right model IDea USA IUMID-0071 because the spec's are off. Http ://ideausa.us/produects.html but similar. I am looking for rom that is more update/modern. any potters?
Does anyone have the original rom for this or know how to make a backup this rom?
Well I am thinking that is might be this model but not to sure wm8650,SV7206 v1.4 or IDea USA IUMID-0071.
It's not flytouch
The screen is very slow on this model. Unless you use a pen then is works better.
Also hoping to be able to flash this to ics 4
Thanks
I just bought one, too. What a pos? it works but the screen is almost unusable, lots of mis-fires.
I did figure-out the real OEM web-page,
http://www.sinovideo.com.cn/Products/indexshow.asp?lang=EN&SortID=61&ID=85
This correctly identifies the installed 2.3 OS and reveals that it's some kind of 1 GHz processor. The real performance problem, however, is the 256 MB of memory, ouch!
I have not had any luck finding any updated ROMs. Actually, I suspect the installed ROM is tweaked to work around the defective screen (I think it's configured to ignore any 'touch' lasting less than 0.5 second?) so I'm not going to change it.
---------- Post added at 08:58 AM ---------- Previous post was at 08:49 AM ----------
FYI - I found another site that has lots of discussion about the "M7206" tablet
http://www.techknow.t0xic.nl/forum/index.php?board=51.0
Here's some more info. (Yes, I have continued to investigate even though I bad-mouthed it )
- This tablet is also sold as the "infotmic m7206"
- the screen works MUCH better if you use a stylus
Currently, my tablet seems to be getting about 24 hr standby battery-life, and the battery-usage report says "Cell standby" is using 75%, even though there's no cell radio? Some of the discussion on the techknow forum seems to be about this same issue but all the solutions seem to involve rolling your own ROM, which I'm not prepared to do. For now I just plan on leaving the tablet plugged-in overnight.
Rooting Idea USA Tablet
Oh my, what a mess...
This post is in regards to the Idea USA Tablet (Unable to Root)
My specs:
- Idea USA Tablet (Made in China)
- Model Number: MID (Unknown)
- Android Version: 2.3
- Kernel Version: 2.6.35.7
- Build Number: MID-userdebug 2.3 GRH55 (ENG)
Issues:
Whelp, I have tried the basics and I can't get this thing to root for anything. I was able to get it to hook into the PC through USB. There are 2 usb slots on the side of the tablet. I believe one is for HOST and the other usb is for OTG (Charging). Once I figured out the host port, then I had to download the drivers for this poorly made tablet...But, what drivers? You go to the Idea US website and you get no helpful information. So, there are no drivers made specifically for this $100 dollar generic tablet from FRY's. Ok... No big deal... So, I download the default "Android USB Drivers".
Peachy, it worked! Now, I can transfer files back and forth between the card(s). Wonderful, first step down, next step was to root. So, I read up on how to root with Super One Click.
Ok, so now, I set the tablet to "USB Storage" and "Host"...Then I download and run Super One Click.
Ok, I run the "Super One Click v.2.3.3"; by clicking the root button and then all I get is a frozen screen that reads:
Code:
Killing ADB Server.... Kill Server 0.11s
Starting ADB Server.... StartServer 4.09s * daemon not running. starting it now on port 5037* *daemon started successfully*
And then it just freezes the program. So, now I'm completely stuck. I mean I learned a great deal, that I can hook up a keyboard, mouse, etc to this thing, but, obviously Super One Click was not designed for these generic tablets. I have read other articles which have suggested that the .inf driver for the default "Android USB Drivers" needs to be edited for your specific tablet model and you must enter the specific CODE# for it to recognize for rooting with Super One Click... But, god forbid, I haven't found any useful information on where that might be. Also, someone suggested to install the Android SDK and edit those files along with the .inf files to make this work. But, that didn't work either. I did everything right. I turned off USB debugging and then I would wait for super one click to come up with waiting for device...but that never happened. I even tried it with USB debugging on... still nothing.
Has anyone created a generic batch program to root these types of devices? What am I doing wrong here?
Rooting Idea USA Tablet
Well, this took me all night to read and learn about how to root this basic tablet from Fry's.
First off, I tried many different things and it just didn't work. Using super one click is definitely out of the question for this particular tablet.
I read all night and thankfully found the forum article on how to solve this issue on xdadevelopers own forum.
As per quoted quotes below:
.....You can use gingerbreak to root this. Run it once and let it reboot, then use supermanager free from market to rename the su symlink from /bin/ to "old" or something, and reboot again.
You should now have root ........ It might take a couple of trys but it works.
You need to download supermanager from the market. Enable root in supermanager settings and click yes when superuser pops up.
Then use the file explorer within supermanager to navigate to the /bin/ directory and you will find a sysmlink called su
You need to rename this su symlink to old - completely take out the name su.
Just to be safe run gingerbreak again and then you can install busybox from market.
pablo11
Click to expand...
Click to collapse
Thank you so much Pablo11. The idea is to download the APK for GingerBreak from online onto your IDEA USA tablet directly. The trick here is that the brand name is IDEA "USA", but the real workings behind the "MID" is "ViMicro". You will notice that displayed as you turn on your tablet. So, in order to find real information about your MID device, you have to search articles for vimicro.
Once you run gingerbreak, your tablet will go completely nuts. Nothing will run right. Things will break and it will be a complete mess. It will however, install superuser apk. However, it will not work. You can download the Root Checker from the market and you will notice it is NOT rooted. So...thanks to pablo11, you will want to download supermanager from the google play market. Install it.
Next go into the supermanager settings and click on ROOT. Make sure root is enabled and checked marked in the settings. When you enable root in the settings, it will prompt you with "allow root?" Click on Yes. This will give you the access you need.
But, your not done, once again as per Pablo11, go to the super managers file manager section. Get to the root directory by clicking up, and then find the folder "bin". Look for the file "SU" and rename this to "old".
Now, you will be able install busybox and any thing else thats root.
By the way, restart your tablet again, and I "personally" recommend that you go into your settings> Privacy> Check mark both (Backup my data and Automatic Restore) and then click on Factory data reset. Start the tablet from like it was brand new. Don't worry it will keep the root that you did intact. You will just have to re-register the tablet with your existing gmail that you originally used with that tablet.
Lastly, use the root checker from the market and you will see that it is successfully rooted.
Okay... Now, my next step. To crack open this tablet and put in a bigger SD Card as the 2G SDCARD is way too small, especially if you want to use new roms and install a linux operating system onto it....
Hey guys!
First off, any help or info on this is GREATLY APPRECIATED!!
Just wondering if anyone has any info or knows where I can find, how to root this Vivitar XO, children's tablet?
My daughter just won this at preschool. It's ok, I guess, its similar to the other kids tablets with the "kid UI" and the normal Android UI, we see on our phones and tablets. it does have decent specs (below) for a kids tablet, better than most so far, especially in the $150 range..
Hopefully, some kids with hacker parents/siblings gets one soon, so we can really make this thing cool! :fingers-crossed:
If anyone knows anything now, please share the knowledge, a very generous beer/coffee donation's waiting! :highfive:
THANKS!!!!
Technical Specifications
Size: 7.6" x 4.65" x .39"
Screen Size: 7"
Screen Resolution: 1024 x 600
Storage: 8GB
Processor: 1.6GHz dual core
Operating System Android: 4.2 (Jelly Bean)
RAM: 1GB
Wi-Fi: 802.11 b/g/n
Camera: 1.2MP Front-Facing / 2.0MP Rear-Facing
Battery Life: up to 7.5 hours
I'm interested in this too - I hooked up with USB debugging turned on and tried adb, but it couldn't see the device. I'm guessing this is due to a generic adb driver not working, but I suppose there could be other secret sauce (e.g. adb.ini magic numbers) needed too.
I'm eager to try some scans for e.g. the Master Key vulnerability and point the Impactor to it - if I can just get adb to see the device! Please, anyone, let us know if you have success getting adb working - I can't stand having an un-rooted tablet in the house!
Magic numbers for XO Tablet
microwiz said:
I hooked up with USB debugging turned on and tried adb, but it couldn't see the device. I'm guessing this is due to a generic adb driver not working, but I suppose there could be other secret sauce (e.g. adb.ini magic numbers) needed too.
Click to expand...
Click to collapse
Interested too but I found the magic numbers !
If I add following lines to the Google generic USB driver, I could see the XO Tablet from ADB:
;XO Tablet
%SingleAdbInterface% = USB_Install, USB\VID_16D5&PID_8007
%CompositeAdbInterface% = USB_Install, USB\VID_16D5&PID_8007&MI_01
Hope that help and you could find a way to root it
Let us know !
Vivitar Camelio Tablet Root Method (no fastboot or bootloader)
I have a Vivitar Camelio tablet for my kids and I have rooted several tablets and phones and understand as a tech myself what to do in most cases...
I want to root and remove bloatware and test some customized JB roms on this basic tablet.
I can connect and see it using PdaNet drivers and I can only backup/restore via adb but when I try to run any fastboot commands I get errors such as fastboot device not detected.
This vivitar stock tablet has a custom 4.1.1 JB rom on it stock. I cannot boot into download mode. However I can boot into its stock recovery with just a few options available such as sideload, wipe cache, factory reset and also reboot. I can see the device from ADB but cannot use fastboot commands without the no device error.
*****
A way to root this tablet and without the bootloader accessibility I cannot do this. I will pay via paypal 10 whole US dollars for the first person that can successfully walk me through this. We can use gotomypc or to video conference or simply you can draft up the steps I need to perform. I am ok with bricking this toy my kid is 3 and the device is a bit much for her at this point so I'll try anything to unlock the bootloader so I can root and rom it.
I was able to gather tablet information but this is all that was displayed via ADB.
DEVICE INFORMATION:
Product Description: Camelio Family Tablet
Device Product: (Blank)
Device Type: PI070H04CA
Firmware Version: 4.1.1
Firmware Build: JRO03H
Firmware Region Code: (Blank)
Bootloader Version: (Blank)
Boot Image Status: Secure
ANY HELP I S GREATLY APPRECIATED!
This tablet is pretty good for the $99 price tag so this should be a question that will be asked again and again by others in the future. Help me on this one and you can post the Vivitar Camelio Root method update and take all the credit for it
Thanks!!!!!!!
Jason
Problem Solved!
Root your device with Kingo. here is the link! Enjoy!
Google Kingo Root and you will find it quick and easy.
Jason
Rooted Camelio Tablet and S4 Mini with Kingo.
lionel911 said:
Interested too but I found the magic numbers !
If I add following lines to the Google generic USB driver, I could see the XO Tablet from ADB:
;XO Tablet
%SingleAdbInterface% = USB_Install, USB\VID_16D5&PID_8007
%CompositeAdbInterface% = USB_Install, USB\VID_16D5&PID_8007&MI_01
Hope that help and you could find a way to root it
Let us know !
Click to expand...
Click to collapse
I found another way of waking up adb and getting it to see the "XO Learning Tablet" over USB debugging - I kind of cheated by launching Moborobo :/ but at least I got connected.
Anyhow, after that, I checked with the SRT AppScanner and both existing Master Key vulns were still present on the 4.1.1 build of Android that the tablet ships with. I tried the first option in the Cydia Impactor ("# drop SuperSU su to /system/xbin/su") and had immediate success! Both a shell (which allowed me to su) and activating the Root Explorer in ES File Explorer (after installing SuperSU) worked flawlessly.
Hope this is helpful to folks desiring to root their XO Tablet. Please feel free to ask any other questions you may have!
ReaperMMA said:
Root your device with Kingo. here is the link! Enjoy!
Google Kingo Root and you will find it quick and easy.
Jason
Rooted Camelio Tablet and S4 Mini with Kingo.
Click to expand...
Click to collapse
Kingo root does work on the XO Learning tablet. Also the button combo to get into recovery mode is Vol- & Power at the same time. When it starts up release the power button.
SnoopyII said:
Kingo root does work on the XO Learning tablet. Also the button combo to get into recovery mode is Vol- & Power at the same time. When it starts up release the power button.
Click to expand...
Click to collapse
Kingo Root only worked for me after I ran Moborobo. Before that adb would not find the device, moborobo fixed that.
So I root the Vivitar XO but how would i flash a clean version on android on to it or maybe even sugar.
Camelio F.T ROOT
ReaperMMA said:
I have a Vivitar Camelio tablet for my kids and I have rooted several tablets and phones and understand as a tech myself what to do in most cases...
I want to root and remove bloatware and test some customized JB roms on this basic tablet.
I can connect and see it using PdaNet drivers and I can only backup/restore via adb but when I try to run any fastboot commands I get errors such as fastboot device not detected.
This vivitar stock tablet has a custom 4.1.1 JB rom on it stock. I cannot boot into download mode. However I can boot into its stock recovery with just a few options available such as sideload, wipe cache, factory reset and also reboot. I can see the device from ADB but cannot use fastboot commands without the no device error.
*****
A way to root this tablet and without the bootloader accessibility I cannot do this. I will pay via paypal 10 whole US dollars for the first person that can successfully walk me through this. We can use gotomypc or to video conference or simply you can draft up the steps I need to perform. I am ok with bricking this toy my kid is 3 and the device is a bit much for her at this point so I'll try anything to unlock the bootloader so I can root and rom it.
I was able to gather tablet information but this is all that was displayed via ADB.
DEVICE INFORMATION:
Product Description: Camelio Family Tablet
Device Product: (Blank)
Device Type: PI070H04CA
Firmware Version: 4.1.1
Firmware Build: JRO03H
Firmware Region Code: (Blank)
Bootloader Version: (Blank)
Boot Image Status: Secure
ANY HELP I S GREATLY APPRECIATED!
This tablet is pretty good for the $99 price tag so this should be a question that will be asked again and again by others in the future. Help me on this one and you can post the Vivitar Camelio Root method update and take all the credit for it
Thanks!!!!!!!
Jason
Click to expand...
Click to collapse
Hey Jason, I have the same tablet someone gave it to me. So I've been playing with it seeing what happens but an answer to your question is by Geohot at towelroot DL the file and run it the DL busybox and install it and let it run oh, DL superSU after that try Root Checker from play store you should be rooted. Hope this helps.
After We have Root access, is there a rom We can flash to make this a normal
Tablet?
My kid doesnt like the interface at all.
Just a stock jb 4.1.1?
Thanks much.
Thanks in advance
microwiz said:
I found another way of waking up adb and getting it to see the "XO Learning Tablet" over USB debugging - I kind of cheated by launching Moborobo :/ but at least I got connected.
Anyhow, after that, I checked with the SRT AppScanner and both existing Master Key vulns were still present on the 4.1.1 build of Android that the tablet ships with. I tried the first option in the Cydia Impactor ("# drop SuperSU su to /system/xbin/su") and had immediate success! Both a shell (which allowed me to su) and activating the Root Explorer in ES File Explorer (after installing SuperSU) worked flawlessly.
Hope this is helpful to folks desiring to root their XO Tablet. Please feel free to ask any other questions you may have!
Click to expand...
Click to collapse
...i am very new to android mods.. ive modded xbox1 ,360 ,ps3, jb ipods n iphones but never anything android .. kids got xo tablet for Christmas ..2 kids 2 tablets 1 of which .. my oldest daughter .. 7 .. insist her dad can modify anything lol .. i dont want to brick it and a detailed tutorial or at least point me in the right direction would be greatfully appreciated .. ive looked into it with not many results..if u could walk me through the proper procedure on backing up and reinstalling stock im up to try anything and post results
r2161984 said:
...i am very new to android mods.. ive modded xbox1 ,360 ,ps3, jb ipods n iphones but never anything android .. kids got xo tablet for Christmas ..2 kids 2 tablets 1 of which .. my oldest daughter .. 7 .. insist her dad can modify anything lol .. i dont want to brick it and a detailed tutorial or at least point me in the right direction would be greatfully appreciated .. ive looked into it with not many results..if u could walk me through the proper procedure on backing up and reinstalling stock im up to try anything and post results
Click to expand...
Click to collapse
Did you ever find anything about this? I'm killing myself trying to install cyanogenmod on this tablet after I rooted it.
I'm a little unclear on the appropriate rom to install over the old one. I assume Cyanogenmod, but I can't find the correct version. Any help?
This really needs a root or firmware if you ever intend on repurposing it. Will have to experiment with ADB and see if I can at least clear out the excess media files. My middle-schooler could probably still make use of it as it is (having a restricted "child" mode might still be a good idea), but would like to clean up the cruft that's not needed (like a lot of undeletable sample files). But yes, if it could also be permanently set to "parent" mode, and I could put MS Launcher on it, that would be nice too.
I actually ended up with 4 of them, two or three that aren't charging. I'm going to open the two that don't charge and see if I can fix that, at which point they could be available for dev work. (now that I re-located my bricked Nabi2, I should send that one out for dev work too).
If it's of any use, when it's attached to my Linux box, "lsusb" will report it as this:
Bus 001 Device 013: ID 0bb4:0c02 HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo (Debug)
"adb devices" shows:
XO8801114002af6
as the device name.
Since I can connect it and am able to navigate through the directories on internal storage, I could pull system information if you tell me what you need.
For something that was supposedly an open-specification device, this tablet is sorely lacking in documentation and other critical information. Wasn't the who purpose of the OLPC project (which was selling this tablet) that it was supposed to be open and customizable? Or was Nicholas Negroponte lying to us?
---------- Post added at 10:29 PM ---------- Previous post was at 09:50 PM ----------
Actually, at this point the tablet is garbage. I can't even force it into a factory reset, because I can't get to the bootloader menu. And somehow it has decided to add a secondary password (after the parental password), so there is ***NO*** way to get into a system menu to do a reset from the settings screen. Short of finding a way to short something on the system board, the only thing to do with this thing is to take a sledgehammer to it.
(yeah, it failed just as harshly as the entire OLPC project did, I guess).
So I still haven't found an answer to what the deal *IS* with the XO Tablet. It has all the pretensions of being part of the OLPC Project, but unlike the laptop itself, which was an OPEN design, fully specced, available for experimentation and customization, this tablet seems to be much the OPPOSITE of that, being pretty-much undocumented, and no one wants to touch the things.
I mean seriously, I'd be willing to pull an image from a fresh factory-reset system so that someone could experiment with it. I'd send it to someone to hack themselves, but really, the device doesn't exude any noxious odors, it doesn't spontaneously spring out poison-laced spikes, at worst it looks kind-of 'meh' as far as design goes. So you don't have to be afraid to touch one.
(for that matter, I'd also send someone my bricked Nabi 2S (was that the name for the later revision?); it does nothing for me sitting unused in a closet)
From what I was able to get from someone who had worked/still works for the OLPC project, this tablet was something some execttive had pushed through without Engineering's knowledge, and therefore it was little more than a sugar UI slapped on top of a proprietary device. Released under their name, but that's about it.
System information from the "Hardware Info" tool shows:
System (Android 4.1.1)
Model XO Learning tablet
Manufacturer XiangDe
Device PI070H08XO
Product PI070H08XO
Brand Vivitar
Android Version 4.1.1 (Jelly Bean)
API Level 16
Build ID JRO03H
Fingerprint Vivitar/PI070H08XO/PI070H08XO:4.1.1/JRO03H/XD-XO-BN-29052013.V010:user/release-keys
Although it will prove to be about as useful as anything else, since the configuration files for it haven't magically sprung out of netherspace.
Yes, you can "root" this tablet (it's pretty much open anyway), but even if you leave it at it's default Android version, the UI is still a serious problem. If you want to repurpose it as a normal tablet and not the dumbed-down kids version, you need to get rid of the built-in launcher. I had thought I found how to disable the launcher in ADB, but it only made it not boot, and I had to wipe to the factory image again. How do you even figure out what it's running for it's launcher so you can disable/remove it at the system level?
I know it must be possible to edit the system image itself (that reloads when you do a factory wipe) because I had at some point managed to delete the on-screen keyboard app (when you factory wipe, you have to plug in a USB keyboard with OTG and eventually re-load a KB device). But Android seems intent upon making the internals of the device incomprehensible. Even with all the cruft Microsoft forces on you with their systems, I'd still think the Windows Mobile devices were probably MORE open than Android.
Since I have two of these (the other is stock) I could factory wipe the other one and pull an image, if there were actually some documentation on how to do that. But with Android, you can never do something for the first time unless you've already done it 10 times previously.
Hello! So this should be an interesting first post. First, a little background:
I'm relatively new to this, and I've been trying to root my NEC Terrain for a little while now. I've followed the instructions on numerous pages in order to understand how to do things. And now I have been able to rip any partition from the phone. I've looked through everything I could in both the boot and recovery partitions but I haven't found anything I can use (I also explored /system but there doesn't seem to be anything in there either). Also, I tried to do everything on this page: http://forum.xda-developers.com/showthread.php?t=2337642 but I can't get SuperSU or TiBu to work. (As an aside, if anybody can point me in the right direction for the most recent su binary, that would be awesome). SuperSU wants to update the binary but fails. I would assume it's because it tries to install it directly into /system/bin, which isn't writable. If I could make it install it into /data/sbin, it might work, but that's off topic right now.
I would like to explore more of the partitions to understand what they are and what they do (I can't seem to find much information about them anywhere). I'm hoping to find something in the code to give a hint as to how to get into the bootloader. So, I have things like "aboot", "firmware", "MM", and "GROW", among others. Is there any way to decode or decompile those images so I can see what coding goes into them? Am I going about this the wrong way?
Thanks in advance to anyone that can help!
Maybe this will help you
In this post by E:V:A you can find some information about partitions and links to more!
I think latest SuperSU should be with latest SU binary (I can be wrong about this), so you could download "CWM / TWRP / MobileODIN installable ZIP" from this post and take one from "x86" folder.
Good luck.
Thanks for the links! Some of these may be very helpful. However, the su binary I got from that link was much older than the other most recent I had. It's a version 2.0 and they're up to at least 3.2 (I'll check the link again to see if I missed something). Also, for these phones, if anybody is wondering, they are ARM, not x86.
There seems to be only one direction I can go with this: Find an exploit that can run at boot that will interrupt it at the right time and allow editing of the /system partition. I can get a root shell with that script and a bind mount, but it's not enough to get anything else to work (ro.secure is still active, so there's no way to change it after the system is booted). Root is granted to root, and that's all. Any app requesting root does not get it.
The guys on that other thread said they got SuperSU and TiBu to work, but they provided very limited information and I can't seem to make them work. I wonder though, if that would matter as long as ro.secure is still enabled.
OK so during the last few years i have added a few Panasonic toughbook and toughpad devices to my collection.
And this is about the toughpad FZ-A1B i have, as it seems Panasonic is not gonna be making any worthwile updates for the tablet and we are stuck with Android 4.0.3
The FZ-A1B i have is build IML74K.V1.01L65M0000
I know that the issue of rooting the tablet and building you own rom is very difficult, due to some security stuff Panasonic have stuck on the tablet.
But as this device is out of warrenty and i wanna see if there is any way to get a new rom on to it, i do need some help on where to start and what the approach will be to try and root it and get a custom rom on the tablet.
So if any one in here can help and guide me to extract information there is needed to root the tablet, i will be happy to give it my best.
Thanks
freetechdk said:
OK so during the last few years i have added a few Panasonic toughbook and toughpad devices to my collection.
And this is about the toughpad FZ-A1B i have, as it seems Panasonic is not gonna be making any worthwile updates for the tablet and we are stuck with Android 4.0.3
The FZ-A1B i have is build IML74K.V1.01L65M0000
I know that the issue of rooting the tablet and building you own rom is very difficult, due to some security stuff Panasonic have stuck on the tablet.
But as this device is out of warrenty and i wanna see if there is any way to get a new rom on to it, i do need some help on where to start and what the approach will be to try and root it and get a custom rom on the tablet.
So if any one in here can help and guide me to extract information there is needed to root the tablet, i will be happy to give it my best.
Thanks
Click to expand...
Click to collapse
Have you been able to find anything? I also have this ToughPad and when I contacted Panasonic Support I got a reply:
"However, the A1 as a model series is no longer listed on the Product page. It is unlikely, there will be any further development for any units in this line."
It's a shame this hasn't been looked at since a "New" FZ-A1 can be had for under $350
Geo
Hi,
Was anyone lucky to find a custom build for Panasonic Toughpad FZ-A1B tablet?
Thanks
curious about this as well
howdy ,
i am a member of the panasonic forum over at "notebook review" and have finally gotten around to seriously wanting to upgrade the OS on my FZ-A1 .
like the other member(s) here have mentioned , i too am on version 4.xx and there are a lot of improvements that have happened in four years .
in checking around , i have found some references to "rooting" and "upgrading to version blablabla" , however , they seem to be a bit on the bogus side as in one example a bunch of links to music and whatnot were included in the *more* section of the description and comments .
it sure seems like there in no lack of individuals wanting to abuse other people .
however , i shall digress ....
maybe i didn't find the information here (yet) but does anyone have any ideas on how to or even if an OS upgrade can be effected on the 'A1 ?
thanks in advance .
Hi,
Was anyone lucky to find Root for Panasonic Toughpad FZ-A1B tablet? If there any way to do this?
Thanks
Gesendet von meinem SM-N935F mit Tapatalk
My tablet Panasonic Toughpad FZ-A1 is running an early version of 4.x and if I wanted to upgrade it, is that possible without too much risk of 'bricking' the tablet if the OEM vendor isn't supporting OS upgrades beyond vendor-supplied patch updates?
Good news for everyone still interested in achieving root on FZ-A1 (4.0.3). It's possible, but there's no easy solution that I know of. Some time ago I searched the net myself and found nothing related, so this is what I came up with:
- compile CVE-2016-5195 dirtycow exploit with Android Studio: android-ndk-r15b-linux-x86_64, armeabi-v7a
- trigger the dcow exploit via adb and get a root terminal: sadly remounting system partition rw triggers reboot
- install matching busybox binary and extract blockdevice system image with dd
- gather offsets of filename & data section of /system/xbin/tcpdump from the system image
- using the offsets replace data section of tcpdump with contents of your su file with dd using seek command,
- in addition rename filename of tcpdump to msu, again by letting dd write directly to the blockdevice
- reboot and let /init.toughpad.rc do it's magic.. it's a fw-backdoor chmod 06755 /system/xbin/msu
- fire up dcow again and rename msu to su via dd.... voila!
sepp2021 said:
Good news for everyone still interested in achieving root on FZ-A1 (4.0.3). It's possible, but there's no easy solution that I know of. Some time ago I searched the net myself and found nothing related, so this is what I came up with:
- compile CVE-2016-5195 dirtycow exploit with Android Studio: android-ndk-r15b-linux-x86_64, armeabi-v7a
- trigger the dcow exploit via adb and get a root terminal: sadly remounting system partition rw triggers reboot
- install matching busybox binary and extract blockdevice system image with dd
- gather offsets of filename & data section of /system/xbin/tcpdump from the system image
- using the offsets replace data section of tcpdump with contents of your su file with dd using seek command,
- in addition rename filename of tcpdump to msu, again by letting dd write directly to the blockdevice
- reboot and let /init.toughpad.rc do it's magic.. it's a fw-backdoor chmod 06755 /system/xbin/msu
- fire up dcow again and rename msu to su via dd.... voila!
Click to expand...
Click to collapse
Thanks! But I know not what this means :/
I would love to try this if someone could walk me through it?
I'm with sepp2021. I've written code, done some Linux and cmd line commands are familiar because I remember DOS, but could you make the steps a little more clear? I call it a "where's the 'on' switch" error. Sometimes we need the starting point.