Related
Hi everyone, For the last two weeks I have been trying to develop my own custom Gingerbread + custom view sonic kernel.
Today I finally have them packaged into a update.zip file but it wont install due to status 6. Sadly I really have no clue if thats the last part I need to over come before I can install, or perhaps there is more than just that issue since the only tutorial I could find were dated / incorrect / incomplete / or written by someone who ate pain chips as a child.
So Really all I want is Gingerbread with com.android.future.usb.Accessory / Manager
AND (this is important also)
I also need the Viewsonic kernel to support the Prolific driver 2303 (this is in the menuconfig so it should be easy to add).
In addition, if anyone could please point me to resources when I can accurately learn how to build the OS / Kernel / update.zip file that would be wonderful. My head hurts so badly from reading all these broken english posts where the scrip examples are riddled with typos.
Oh also two weeks ago was the first time I ever saw Ubuntu (thats what im currently working on as well).
Thank you and sorry for the aggravated post but I seriously need help, my job is in the balance. Thanks Again
Anyone know of a rom that has these features already in them? Or perhaps a good couple of tutorials that will allow me to create my own? I dont want anything fancy just plain vanilla.
DKS1282 said:
Hi everyone, For the last two weeks I have been trying to develop my own custom Gingerbread + custom view sonic kernel.
Today I finally have them packaged into a update.zip file but it wont install due to status 6. Sadly I really have no clue if thats the last part I need to over come before I can install, or perhaps there is more than just that issue since the only tutorial I could find were dated / incorrect / incomplete / or written by someone who ate pain chips as a child.
So Really all I want is Gingerbread with com.android.future.usb.Accessory / Manager
AND (this is important also)
I also need the Viewsonic kernel to support the Prolific driver 2303 (this is in the menuconfig so it should be easy to add).
In addition, if anyone could please point me to resources when I can accurately learn how to build the OS / Kernel / update.zip file that would be wonderful. My head hurts so badly from reading all these broken english posts where the scrip examples are riddled with typos.
Oh also two weeks ago was the first time I ever saw Ubuntu (thats what im currently working on as well).
Thank you and sorry for the aggravated post but I seriously need help, my job is in the balance. Thanks Again
Click to expand...
Click to collapse
this is the thread i used to get me started compiling a module for pershoots kernel
http://forum.xda-developers.com/showthread.php?t=916198
obviously run your own menuconfig somewhere in there (i think its in one of the steps) and turn on whatever you want. Also save the modules that you create as the default pershoot ones wont insert into your custom module at that point
[edit] there is a thread in the gtablet devel section for pershoots latest (i think 2.6.32.42) that may have this already: http://forum.xda-developers.com/showthread.php?t=903505 [/edit]
Thanks for the links. I was able to pull the config file from Ginger 2.3.4 and it seems to have the required driver for the prolific usb to serial converter, although when I write a usb detection program and attempt to load it onto the tablet, well I get a missing shared library com.android.future.usb.
So now thats kind of odd because its 2.3.4 and Google specifically says it supports the library I need. So I guess what Im asking is there any Ginger or even honeycomb OS for the Gtablet that supports this?
Once again Thanks for a point in the correct direction.
Is there anyone I can communicate with directly in creating this? Ill be more than willing to donate my work so that it could be built upon. I just can not believe that this has not been added in yet.
Ive pushed android.hardware.usb.accessory.xml to /etc/permissions
and ive pushed the com.android.future.usb.accessory.jar to /system.framework
This seems to do absolutely nothing. Does anyone have a version with the USB accessory working for the G tablet? Or could anyone Communicate with me directly perhaps by IM? Thank you very much again.
So after some tweeking I can now get my program that requires com.android.future.usb.accessory although thats all it does. It wont detect the USB or use any USB features. Im sure im programing it wrong, although It detects USB drives and keyboards and such it will not detect my USB to serial Prolific cable.
Im trying to compile the kernel and install it but really, nothing works... Im typing commands I dont know what they mean, and i get responses like "Permission denied" so I use sudo on the command and get "not a valid command". So I didnt have permission at first, then once I did it wasnt a valid command? No wonder why ****ty old windows stomped ubuntu into the ground... I feel windows phone will destroy google if its this hard to develop a single app that I have on the IPHONE / WINDOWS PHONE / WINDOWS 7 but cant get it on android... WTF
Im just wondering how you successfully compile Gingerbread 2.3.4 and Leave out part of the MAJOR update. Why not just use 2.3.3?
Anyway Ive personally fixed that, although when i pull the kernel it shows the prolific driver is installed but there is no detection when I plug the cable in.. Nothing nadda. just like the replies to this post. Im guessing people dont have any problems at all with all the really bad tutorials out there and the lack of support even on this, a developer site, I cant even ask questions to the developers because I dont even have 10 posts yet. Also it just seems like the only thing people on this site is Over Clocking. It done matter if its a peice of ****, as long as its over clocked, Or some of the roms I installed and they are SO bad, but man they are over clocked... Or the roms that say they are 2.3.4 and happen to be 2.3.3. Or the ones that just wont install. How has android made it this far, its actually pretty bad, but then again im sure Im the only human with these problems, because I really cant find anything on the Internet after a good long while. I tough myself enough law to win a law suit against a company with high priced lawyers in less time than this is taking... And im no good at law at all.
Yes, I definitely mean “wonderful” and “experts.” It is astonishing how much time, effort, and expertise the people who write the ROMs, etc., do for others, just to help us enjoy our cellphones. So, it is with no disrespect that I offer these comments on the instructions the experts give to us noobies to help us try to make our phones work better when they post “complete” instructions about how go to about this.
#1 – Odin.
There’s lots of advice to get Odin, but there are lots of Odin versions out there. Usually (generally in the computer world) what works when there’s a recommendation to get a program is to find the latest version. Even if a forum posting has a link to get a program, we figure that was the latest version available when the post was made and it still makes sense to get the currently latest version. That doesn’t work here. The latest Odin version I found was Odin 4.28. 4.28 totally fails to recognize my Samsung Droid Charge. But, if I use the ones referenced in the postings here (e.g. Odin3 v1.85) it recognizes my phone immediately. I understand the feeling that if we’re noobies we should just follow the directions exactly as written, but a little footnote about how this is different than everything else with computers would help.
I’m sure it isn’t true, but Odin seems to come from a mystical cloud location without any existence in our 3 dimensional universe. So, there seems to be no home website to explain that the latest version shouldn’t necessarily be used by everybody. And, there seems to be nobody on the forum who takes credit for upgrading Odin. Very mysterious.
Also – there’s at least three ways I’ve seen adamantly expressed as the proper way to connect a phone to Odin. #1 – simply attach the phone to the computer in the usual “download” mode, and Odin will find it.
#2 – Take out the phone battery for 5 seconds, replace it, then boot into recovery mode by holding down the up-volume, power, and home keys until “Samsung” flashes twice.
#3 – Take out the battery and don’t return it. Plug the phone into the computer, booting into recovery mode like #2.
As far as I can tell, #2 and #3 were needed for prior versions of Odin. Still, we noobies do Google this process, and it’s scary getting these conflicting directions about how to proceed. So, since you are obviously trying to make things less scary and confusing for us, you could mention this too.
Part of the problem is that there are various “Here’s how to replace your stock ROM with a better one” postings. Maybe each of them works perfectly, and there are many paths to enlightenment. Still, it’s worrisome for a noobie to try to figure out which of these paths to bet our phone on. (Of course, it’s also difficult for people trying to actually achieve spiritual enlightenment to decide on a path, so maybe this confusion is just an inevitable part of human experience.)
(cont. below)
#2 – CWM – Clock Work Mod.
I’m still confused about the need and timing of this one. Some sources say it’s entirely optional, just allowing other cool stuff done later. Others seem to say it’s important to install (flash through Odin) this before installing the new ROM. And, then there seem to be some ROMs that Odin can flash that do it all at the same time. And, then, there’s the issue of what order things are to be done in. If we just use Odin to flash a new Gingerbread ROM, can we, or should we, use Odin to flash in CWM?
As a noobie, I’m inclined to the “the less I mess with, the less chance I have of screwing everything up.” So, I think I’d like to skip the CWM while installing my new ROM, and wait to use CWM until I find some additional cool feature I can’t add without it.
#3 – ROM’s.
Where’s Consumer Reports when we need them? There are apparently various ROM’s we could use to improve our phones (e.g. Samsung Droid Charge). They are listed with somewhat cryptic explanations. Those explanations are probably perfectly explanatory for experts, but as a Noobie I don’t get a clear sense of direction from reading them. For example, Android 2.2 ROM’s (Froyo) are still listed, along with 2.3 (Gingerbread). Why would anybody want 2.2 if 2.3 is available? I assume there’s some reason I should be considering, but have no idea what it is. Among the 2.3’s, there’s also the “bloated” vs. “debloated” versions. Many of the unremovable (until rooted) stock apps seem to be both useless and resource drainers. But, I don’t know if I’m ready to give up all of them. And, the “debloated” versions are written by programmers, not people who want to devote their lives to writing up detailed commentaries about what is, and is not, debloated and why. Is there any reason not to just keep all the stock apps, and freeze or uninstall them with Titanium Backup later, as I identify the ones I do not want?
I feel anxious when I read somebody’s post about their newly released ROM, with lots of compliments, then comments that some feature now isn’t working. It’s hard enough to get answers about how to deal with the stock ROM.
I’m also confused about the difference between the “kernal” and the “ROM”. My impression is that “kernal” is which version of Android we use. “ROM” is broader, including extra’s like CDM and CDW, and Voodoo, etc. Or, not?
Part of the problem, obviously, is that the ROM writers have to do a different version for every [email protected]#$%^&*! phone that is made. Apparently even with the Samsung Galaxy family, there are enough differences that the ROM’s are customized for each one. (My prior phone was a Vibrant.) I am grateful that we have choices, and that these ROM’s are available, at all, but it would help to get a little more commentary (i.e. recommendations) about which ones are best for those of us just wanting a better ROM.
#4 – Voodoo. This is like the other issues. It seems like a great thing, to make the file system more efficient and do things like improve the sound system. But, it’s also confusing about when/if to install it in relation to the general ROM update.
So, maybe one of the wonderful experts will clarify these things here, or tweak their general instructions, for the benefit of noobies. Regardless, I again express my appreciation for all they’ve done for us.
There's a whole lot of "it depends" in this.
#1 - Odin may be up to 4.28, but Odin3 is newer than Odin. That's pretty self explanatory on its own.
#2 - You need CWM. Period. But, if you are flashing a full Odin ROM, it already comes with it, so you won't have to go into it unless you want to flash a theme or a new kernel. If you are installing a CWM ROM image, you need to flash CWM first.
#3 - Froyo (2.2) is still the only offical release for this phone. Gingerbread (2.3) is coming, but it's still in beta, and not officially released. The only GB releases we have are leaked and are not official final builds, therefore, they are not guaranteed to be of the quality or stability of Froyo, and, more importantly for us, there is no source available for the GB releases yet, so we don't have a lot of the cool tweaks available. So, it really does depend on what you are after.
#4 - All the current ROMs pretty much support it out of the box. If you are going with a stock ROM instead, you need a Voodoo enabled kernel to activate it. If you're ever in doubt of whether you have it and if it's enabled, install Voodoo Control and look at the lagfix section of the app.
I built a web page that has compiled all of the software you need to root, kernel update, ROM, and recover your Droid Charge with direct links to all of the software in one place.
http://www.toms-world.org/android
Plus it comes with very detailed instructions on how to do any one the activities mentioned above.
For those experts who do know how to do all of this, I'd like to see some collaboration and opinions on my directions. I'm only one person so I can't think of everything that could be added as far as a tutorial.
My idea is that a lot of us that know how to do this stuff should start a place where people can find the information they need for the Droid Charge all in one place without having to go from thread to thread, page to page, etc. Having it all in one place would benefit the Droid Charge community greatly.
Thanks for the replies.
Also, answering my own questions,
Not only is CWM necessary, but the remove battery 1st instructions, at:
http://forum.xda-developers.com/showpost.php?p=14692818&postcount=1
are correct. The other instructions I found that didn't include this stop didn't work -- Odin just sat there.
Also, at about page 11 of that xda thread, it says (correctly) that after ODIN says it's done, it's OK to unplug your phone, despite the large, brightly colored screen that says "Downloading... Do not turn off Target!!!"
Also, the kernal is different than the OS. So, first we find and install a rooted kernal (I guess this is like the most fundamental part of the phone's operating system), then pick a ROM (i.e. version of Android) to install.
Yes, now that you pointed it out, I agree it should have been obvious that ODIN3 is a later family version of ODIN, so no matter how high the version of ODIN we find, it's not going to be up the ODIN3 level. ...sigh
In the case of loading GummyCharged, you don't need to pick a kernel. The GummyCharged package contains an already rooted kernel (iMoseyOn's Lean Droid Charge Kernel) so basically if you load GummyCharged you have a kernel flashed along side it.
The only time you have to flash a new kernel is if you want to run a different kernel than the one contained in your ROM. Or if you want to update the kernel to a newer version of the kernel.
The kernel is the heart and soul of an operating system. It does all of the work in coordinating memory and process allocation. Think of it as a traffic cop.
trparky said:
In the case of loading GummyCharged, you don't need to pick a kernel...
Click to expand...
Click to collapse
Thanks. Your description of the kernel is much better than mine.
Another bit of noobie confusion:
The GummyCharged thread at
http://forum.xda-developers.com/showthread.php?t=1163123
says to install through CWM, after rooting. So, I already installed a new kernal, so I could have root.
As I understand better, now, I hope -- even with GummyCharged -- I had two choices, as there are two GummyCharged versions available. One is the two-step process (new kernal, then new OS). The other is to do both at the same time, through ODIN, which would have been easier.
I did install a new kernal, through CDW, seeing that path more clearly.
http://forum.xda-developers.com/showthread.php?t=1104634
Just a note that when my phone rebooted, Titanium Backup said I did not have root privileges. On a hunch, I just rebooted again, and that solved the problem. TB is happy, and so am I.
Then install a new OS through CWM.
Another thread that might have some useful information for you can be found here -> http://rootzwiki.com/showthread.php?4643-HOW-TO-quot-Clean-quot-install-GummyCharged-FE-2.0. Theres a lot there (maybe too much?) but if nothing else there are a number of useful links. I hope it helps!
Off topic: trparky I tried to send you a pm yesterday but my computer was acting up - not sure if you got it or not.
Thanks for all the help. Everything seems to be fine. This is just sort of a summary & wind-up post of another noobie's experience and successful quest for cellphone happiness.
First, there seem to be three ways to do scary things to the e-guts of my cellphone.
#1 -- Odin3 (a.k.a. Odin, but Odin3 v.x is the one that works for Samsung/Verizon Droid Charge [SDC]). Odin3 runs on the computer, with the cellphone properly tethered to the computer, and can insert stuff, like CWM. So, mostly the first step is to use Odin3 to insert CWM (superseding the stock recovery program). From some post it seemed it's possible to skip this step and do everything from Odin3, but that post also said that approach wasn't for noobies, even though it seemed easier to me. Odin3 is an elegant program, but you have to find somebody's Betty Crocker instructions for how to use it.
#2 -- Use the ordinary SDC file tethering to put .zip files onto the SDCard, because CWM uses those to install things like kernels and OS's (versions of Android). Sometimes the kernel and OS come bundled. Sometimes not. I ended up flashing a kernel first, then an OS with a bundled kernel, and everything seems fine.
#3 -- there's some other program, starting with an "H" that can also work like Odin, I think, but I ended up anxious enough figuring out #1 and #2, so didn't want to learn a whole other approach that might, or might not, somehow have been better, so I ignored this approach.
After I had my new root kernel, I used Titanium backup to freeze the bloatware. At that point I sort of chickened/burned out because there were too many choices of which version of Android to flash. I decided I didn't really need any of them, since my phone would be efficient enough without the bloatware running to give me everything I needed. What originally got me to start flashing my Android phone was when I would (repeatedly) receive calls on my old Samsung Vibrant, but the phone was so busy doing some [email protected]#$%^&*! thing that it wouldn't let me answer the call. With a more advanced phone (my new SDC), and frozen bloatware, I was confident I wouldn't have that problem, so just stopped there ... ... ... until I was horrified to receive another call which my SDC told me about but was too busy doing some [email protected]#$%^&*! thing that it wouldn't let me answer the call. OMG, it's happening again! At that point the choice of which version of Android to use because less important, because I was sure that nobody's custom Android would let that happen. So, I went with the GummyCharged Froyo [GummyChargedFE_2.0.zip]. At this point, I'd worked with CWM enough that it was all easy. Downloaded the file, copied it to my SDCard, booted to recovery, erased files & Dalvik cache, flashed the GummyCharged, and restarted. Lovely.
One nice aspect I'd not anticipated was that somebody has thoughtfully improved the process, so immediately my phone started re-downloading and installing the apps I had before. It's kind of a hassle to have to re-do all that manually, so special chops/thanks to the GummyCharged team for that feature. My phone works fine. I've tried, and happily failed, to make it too busy to let me answer a call.
What's left? I have to make donations to the Gummycharged people, whose software I now use, and the person who tweaked CWM that I use. It feels like I should make a donation to the Odin3 trolls, but haven't seem a request for that, nor have any who they are or how to do that.
I'll also be keeping my eye on the developing Gingerbread kernels, occasionally, until it looks like those are so mature that there's no reason to not confidently install & flash (through Odin or CWM, both of which I not feel fairly comfortable with) the upgrade.
On the off chance that anybody's still reading this, I do have one last question:
Can I delete the GummyCharged .zip file from my SDCard. I remember, back when I flashed my Vibrant, that I later deleted a seemingly useless .zip file called "update.zip", and that caused a problem. File isn't huge, so except for my mild OCD, no big problem in just leaving it there.
Thanks, again, to the wonderful experts who've helped me and so many others through this.
angelsix said:
...
#3 -- there's some other program, starting with an "H" that can also work like Odin, I think, but I ended up anxious enough figuring out #1 and #2, so didn't want to learn a whole other approach that might, or might not, somehow have been better, so I ignored this approach.
Click to expand...
Click to collapse
I believe the program is called Heimdall - this is more often associated with Mac users, as ODIN is a Windows program.
angelsix said:
...
One nice aspect I'd not anticipated was that somebody has thoughtfully improved the process, so immediately my phone started re-downloading and installing the apps I had before.
Click to expand...
Click to collapse
I'm not positive, but I believe this to be more of a Google thing. Whatever apps you've downloaded from the market are linked to the google account used on the phone, so once you sign back in on your phone post-flash, those apps (whatever ended up being stored as downloaded-by-you by google at least) start getting pushed to your phone.
angelsix said:
...
On the off chance that anybody's still reading this, I do have one last question:
Can I delete the GummyCharged .zip file from my SDCard. I remember, back when I flashed my Vibrant, that I later deleted a seemingly useless .zip file called "update.zip", and that caused a problem. File isn't huge, so except for my mild OCD, no big problem in just leaving it there.
Click to expand...
Click to collapse
You can delete the file, but this is essentially the installer file - if you ever have need to re-install it later on, you will need that (or a more up-to-date one if such a thing exists) file again. I tend to be an electronic pack rat myself, but you can delete the file from your SD card without any immediate adverse effects. If I remember right, the "update.zip" of old was associated with some earlier variants of CWM - without it you would not be able to get to the "custom" recovery (i.e. CWM) to flash things. Seems like such things are no longer necessary anymore, at least not with the recent versions.
dwitherell said:
I'm not positive, but I believe this to be more of a Google thing. Whatever apps you've downloaded from the market are linked to the google account used on the phone, so once you sign back in on your phone post-flash, those apps (whatever ended up being stored as downloaded-by-you by google at least) start getting pushed to your phone.
Click to expand...
Click to collapse
That is correct, and it's something that I strongly dislike, as I have installed plenty of things from the Market that I have since uninstalled and no desire to restore. If you skip account setup when you are first setting up the phone, and then manually go into Settings->Accounts & Sync, it will skip this, which is yet another reason to like aftermarket roms, as the stock roms will not allow you to get to the launcher until you set up a Google Account.
EDIT 12/13/2011:
Instructions to Root the le pan tab tc970 from whatid (THANK YOU!!)
"Here are the steps (to root) for newbies.
1. Download the packages from OP (Post #1). Assume you are using windows, you don't need LinuxDriver.7z.
2. Use http://www.7-zip.org/ to unpack onto your computer.
3. On your TC970, hit home->Menu
4. Applications -> Development
5. Check "USB debugging", optionally some suggest checking "Stay awake"
6. Connect your TC970 to your PC, when prompted new hardware detected. Select the Windows Drivers directory you unpacked in.
7. Once driver is installed, run "SuperOneClick.exe"
8. Just click "Root" under the "Universal" tab and wait.
** It will prompt you to install BusyBox during the first time, just install it **
9. When it is done, it will prompt you.
From dbaybay's experience (thank you for your continual help in leading the le pan community through the growing pains!!!):
If you ever have to root your tab again (say after upgrading the firmware), when you root it the first time, open up SuperUser before rebooting and Menu > Options/Prefs and choose "update binaries". Then reboot and your root will stick the first time around.
If everything seems ok, turn off your TC970 by holding on the power button. Power up again, and see if root stay (use Root Checker Basic).
If not, repeat step 6 (no need to install driver again) until you have root after reboot."
Also a big thanks to nehinbin for giving the community insider info with regard to the tablet and firmware v2 which you can find here:
http://lepan.supportsync.com/articles/view/Latest_Firmware_for_LePan_TC_970_Tablet_Computer_11
For the brave or fool hardy, here is a link which will direct you to directions on how to port CWM to a new, as of yet unsupported device (like the 970):
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
AND HOT OFF THE PRESS FROM cas_xp:
"I am still waiting mine to be shipped. (should be today or tomorrow) Can not wait!
But if anyone is interested, I attached a tool to extract Le Pan update package as
Kernel
ramdisk
recovery
system
...
For somehow, the system is compressed and not yaffs2 or other format. I am trying to figure it out."
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I have achieved root using a modified superoneclick 2.2 on my Le Pan TC 970!!!!!
Credit to all devs who produced superoneclick and associated root methods!!!!
I wish I could take some sort of techie credit for this, but I did it by swapping the adb file and associated .dlls in superoneclick with some that I procured from *somewhere*.
The root is not permanent, but for someone with far more experience in android than i, i am sure it could be used to develop a permanent root.
If there are people out there who would like to take this to the next level, send me a pm and ill see about getting you the files to repeat what i have done.
-DerKoch
NOTE:
After reboot when trying to gain elevated privileges on the device i get the error:
link_image[1995]: failed to link su
CANNOT LINK EXECUTABLE
Could be a useful starting place.
-DK
EDIT:
Nuts to it. The Superoneclick i modified to gain root is now attached. It is only modified for and works in windows as i didnt feel like farting around with the linux version.
Good luck with the permanent root.
-DK
ANOTHER EDIT:
I have updated the post and am including the missing files.
Dont ask where i got them and, as usual, if you screw up your new toy with anything you find here, i am not in any way responsible. Rooting or altering your tablet beyond what is allowed by the eula of your device will almost certainly void your warranty and piss off the people to whom you are trying to return the device once broken beyond your ability to repair.
YOU ARE WARNED
ALSO, It looks like the tablet hardware was designed by innocomm. you can find this if you download the 4431 update from le pan http://www.sendspace.com/file/sunmks . For some reason the firmware update is not openly available...... Well now it is. Just click on the above link and download at your leisure.
the 970 uses the 3e recovery and what looks like a modified 3e or 2e (i cant remember which at the moment) for the firmware update supplied by le pan.
This firmware package contains a MLO file (35.1kB) which i assume is a shell script (although the text encoding eludes me *encrypted maby*), iboot.ism (131.1 kB) which i think it the, you guessed it, bootloader the tablet uses during the flash process, and griffin.ifw (99.1 MB) which is the firmware. There are a whole bunch of apks included as well so non-market apps are enabled by default and you are told to install them after you upgrade the tablet.
all of the documentation for the 970 is written in mandarin, so for all non speakers, good luck with that
I cant seem to decompile griffin.ifw into anything useful, but then again, i am no firmware expert. I am sure some of you would be able to poke around and get it to open-sesamie.
If you are successful, please post how ya done it here so we, myself included, can learn a thing or two.
Best,
DK
Thank you!!
I just wanted to thank you for figuring out as much as you did. I wish I was even on your level but hopefully I will be one day soon. Anyway, you're awesome!
Edit: I was also able to root my le pan tc970 and it is permanent. It got stuck in a rebooting loop but i just hit the reset button on the back and it turned on just fine. I did have to reinstall all my apps as well but everything is fine now so thanks to you and the developers.
Damn. 147 views and no feedback. Kinda quiet in here .....
Sent from my SAMSUNG-SGH-I897 using XDA App
DerKoch, how exactly did you get this to run and root?
When I run the SuperOneClick you posted, it stops responding when it tries to restart the adb server and it just hangs...any thoughts?
Yeah. I forgot to post the other needed files (One might even be able to call them a hardware - software interface if you get my drift. These aren't supposed to be available to the public. ) Im away from my computer, but ill put them up when I get home.
Sent from my SAMSUNG-SGH-I897 using XDA App
hey dadog,
just search the forums for your phone. the answer is out there
PS
be careful about asking questions in the wrong threads (such as this one). people will rip you a new one and you run the risk of having bad things happen.
DK
Help the community
Hey all,
it comes to my attention that i forgot to post all of the files i have from *somewhere* to make this work. i have what one might call a bleeding heart for people who put themselves at risk to help others and the person who helped me was exceptionally kind in this regard.
please do me a personal favor and call le pan customer support and hound them regarding making the files-who-will-not-be-named publicly available. the phone number is: 1-855-537-2672 (1-855-LePanPC). tell them you are developing software, and have to be able to access the tablet through adb, not just mass storage which regularly fails and screen locks the device. also tell them how disappointed you are with the total inability to use it while it is connected to your computer in mass storage mode, because it constantly chokes on itself and requires a hard reset to get it back up and running. if you are lucky, they might help you out.
if there is enough pressure, i hope these required files will become publicly available and my conscience with releasing these files will become clear.
if you need the other files to get this to work because you are a dev working to open the 970 to comply with the gnu/gpl license they have flaunted by taking the froyo os and NOT RELEASING ANY SOURCE CODE *OR DRIVERS* (GRRRRRRR!!!!), please send me a pm and ill get them to you.
Best
DerKoch
Permanent Root - Le Pan TC 970
Thanks again for the drivers. Now that they are public we can post in this thread instead of PM.
In response to your first post, my device seems to be permanently rooted. I have restarted it several times after the initial root and still retain full access to the superuser bin.
Off topic: The USB wall charger just burned out in mine and I've only had it for a day. I'm going to see if Le Pan would just send me a replacement charger instead of having to exchange the whole product with Amazon. I wold like to get some more hands-on time with it.
Other than that charger issue I find it to be a superb tab.
I have no idea why launchers in the market place are blocked on this device but you can get around this by downloading the apk's and manually installing directly on device.
raden2967 said:
Thanks again for the drivers. Now that they are public we can post in this thread instead of PM.
In response to your first post, my device seems to be permanently rooted. I have restarted it several times after the initial root and still retain full access to the superuser bin.
Off topic: The USB wall charger just burned out in mine and I've only had it for a day. I'm going to see if Le Pan would just send me a replacement charger instead of having to exchange the whole product with Amazon. I wold like to get some more hands-on time with it.
Other than that charger issue I find it to be a superb tab.
I have no idea why launchers in the market place are blocked on this device but you can get around this by downloading the apk's and manually installing directly on device.
Click to expand...
Click to collapse
How exactly did you get a permanent root? Or more appropriately, what was your process for doing it in the first place?
I cannot seem to get mine to root at all
Succesfully Applied Root to my TC970
Makes tablet that much more awesome. It's one of the few Android tablets with a 9.7" 4:3 ratio screen. But, the stock resolution on this thing is wayyy to big. I set it down to 180 with LCDDensity, and it looks great. Thanks for the awesome help folks.
nevermind, I got it working. Now all I need to get working is LCDDensity without locking the tablet up on reboot and I'm golden! Thanks a lot guys!
I was having the same problem as you. Actually, when I first rooted, all my apps broke. So, i wiped to factory(on the latest firmware, re-rooted, ran LCDDensity, and was good to go. Then all my apps ran fine, and it didn't lock up on reboot.
Brief Rooting Guide - Le Pan TC970 (Windows)
MK2MR2 said:
How exactly did you get a permanent root? Or more appropriately, what was your process for doing it in the first place?
I cannot seem to get mine to root at all
Click to expand...
Click to collapse
Step 1: Enable USB debugging on device (Settings>Applications>Development>USB debugging)
Step 2: Download windows ADB drivers and modified Super One Click 2.2 from the first post in the thread.
Step 3: Plug in device and install drivers through device manager / new hardware detection wizard.
Step 4: Open modified Super One Click 2.2 (with admin privileges depending on your OS version).
Step 5: Click the "Root" button.
That's it.
raden2967 said:
That's it.
Click to expand...
Click to collapse
... and that's for permanent root? I just bought one of these from Amazon for $170... so I'm hoping I can root it in the hopes of some ICS magic in the weeks/months to come!
I wouldnt hold my breath for a full ics experience. ics is very graphics intensive in comparison to 2.2 and without any hardware acceleration it would be a very slow, somewhat irritating experience.
I believe it would be better to develop an upgraded/modified 2.2 or 2.3 build for the 970 as neither are that demanding in the graphics realm.
Best,
DK
No Official Android OS updates planned for Le Pan TC970
gfinockio said:
... and that's for permanent root? I just bought one of these from Amazon for $170... so I'm hoping I can root it in the hopes of some ICS magic in the weeks/months to come!
Click to expand...
Click to collapse
I have confirmed with Le Pan tech support that this tab wouldn't be getting any more official OS updates but they may publish bug fixes in future firmware updates.
In their words:
"The TC970 runs 2.2 which is a completely different platform than 3.0+.
Google rushed its release to compete against Apple so it's lacking a lot of support. This OS is not upgradable to anything beyond 2.2.
Le Pan plans to release a new tablet with a new OS that will come out early next year.
Sorry for the inconveniences, we really wish 2.2 would be upgradable to 4.0 or even 2.3 but it just isn't possible. "
...
"The current model TC970 will not be getting any OS updates but will receive firmware updates when needed."
We are on our own to port 2.3.x on this tab.
So, I ran the root exploit and then tried to run LCDDensity and my tablet crapped out.
I then booted into recovery and just did a complete reset, when I came back to the tablet interface I found that Superuser was still installed, and it was rooted permanently. Weird, but i'll take it! I've since have tested it out and restarted the tablet to confirm that it is indeed permanent.
It is. DerKoch, I cannot thank you enough for the help here, amazing!
Thank you, but remember to also thank the development people over at superoneclick. I just modifyed their application. A lot of hard work went into their program. All I did was have the right tools at hand to make their stuff work with the 970 and know where the current failings were with accessing the 970.
Please don't think I'm being ungrateful, but the Android development community is really a lot of different people standing on the shoulders of giants taking their work just a little bit further.
Best
-DerKoch
Sent from my SAMSUNG-SGH-I897 using XDA App
raden2967 said:
Le Pan plans to release a new tablet with a new OS that will come out early next year.
Click to expand...
Click to collapse
I just ordered one of these from amazon.ca too - $170 shipped is an amazing deal! I love how it came on super sale the day after someone managed to root it. That was the first thing I went to check when I saw the new price!
BTW it looks like the "Le Pan II" that support was talking about is about to hit the shelves:
http://www.amazon.ca/gp/product/B00...d_t=101&pf_rd_p=1293009622&pf_rd_i=2690953011
1.2GHz dual core running Honeycomb... very interesting.
Does anyone have any plans to try Honeycomb on the TC970? (CyanogenMod7?)
Sandmonkee said:
Does anyone have any plans to try Honeycomb on the TC970? (CyanogenMod7?)
Click to expand...
Click to collapse
I don't think that this tablet can run Honeycomb. It's only single core and 512 megs of ram. Gingerbread is more possible, but i don't think that this tablet could run it.
I have just gotten my hands on a Xoom MZ602 running 4.1.2, and am having one hell of a time getting anywhere in rooting it. I keep finding useful articles, but due to the fact people don't seem to update links, I can not download any of the main tools to root it! I would like a link to the one click root, or something equally easy, but would settle for anything that's not loaded with viruses or adware, or not hosted on a shady filesharing service.
Is this basically stuck as it is, or are any of these files still out there? My Google Nexus 7 is just as old, but there are still an abundance of tools for rooting it, so there is no reason I shouldn't be able to find the files for this, other than people not updating links.
I'm really looking for the best and most reliable way to root this, and if it can be done with no PC, or on a Linux PC, that's a plus, but I do have access to winblows PC's too, if needed.
Kingo root does
You can change kingroot by supersu after.
This change require a little skills, but not much.
Update (5/18/2019)
Since the first tool was released, HappyZ has improved many features so I think I can just refer to
* HappyZ's rooting guide: https://github.com/HappyZ/dpt-tools/wiki/The-Ultimate-Rooting-Guide
- The only thing I want to add as Windows user is (because the guide is for Mac/Linux users) it gets much easier if you use Linux terminal like cygwin, and the port name should be something like COM# where # can be found in Device Manager by comparing before/after you attach the device.
* HappyZ's upgrade guide: https://github.com/HappyZ/dpt-tools/wiki/The-Upgrade-Guide (Recommend to read this before/after you update the new firmware.)
You may donate a cup of coffee to him there Thanks to all others who contributed a lot.
--
Update (12/02/2018) -- These are outdated.
Finally we manage to root the device! Many thanks to all of your efforts.
Just refer to HappyZ's well written guide: https://github.com/HappyZ/dpt-tools
For whom have never used python like me (and probably using Windows):
(1) Install Python 3 and add it to PATH.
(2) Install MINGW64 and run scripts here instead of Powershell due to xxd issue if you are on Windows.
(2) pip httpsig pyserial on bash.
(3) Download HappyZ's dpt-tools and unzip.
(4* this issue is fixed by HappZ)
(5) Follow HappyZ's guide. You should execute dpt-tools.py in the folder you unzipped to use get-su-bin because of how the script is written.
Some suggestions after rooting (let me know if you have better ideas):
Here is my setup: install "E-ink Launcher" and "Multi action home button" using adb install.
Use adb shell am start -a android.intent.action.MAIN to change the main launcher to your launcher.
Then change the setting of Multi Action Home button (say, the height should be large to be visible in the bottom) and assign its function to be Home for click and Back for double-click.
Whenever you want to use Sony's apps (these are good for pdf markup), just push the home button to open the pop-up menu.
Otherwise, touch the Multi Action Home Button to access to other Android apps. So far I've never experience any crash.
Yet more tips:
Some complain fonts are too small after installing generic apps.
adb shell wm density 320 changes your DPI by 2 times (160 is a default value.) EDIT: I found 200 is quite enough that does not distort Sony apps too much.
My application is using "Tasker" to execute the above code when specific apps are open and execute wm density reset when the apps are closed.
The reason why we cannot change the global DPI is sadly because it makes the default apps by Sony so awkward.
Alternatively, I could successfully install Xposed to try App Settings but this app crashed.
You can also install Gboard (but it has no hide button, so prepare with virtual back button) if you need another keyboard.
Enjoy your DPT devices
--
Sony recently released a new digital paper device DPT-RP1, apparently using their own linux firmware but underlying on Android 5.1.1. Few weeks ago, some Chinese successfully hacked it to jailbreak for third-party apps (without changing the original firmware), but they don't share any information to sell those hacked devices. I'm willing to pay for it, but it is too risky to send my device to China so I'm trying to root it by myself.
I don't know much about this world, but I found some information that might be helpful. It uses Marvell A140 IoT Processor a.k.a. PXA1908. There are two Android smartphones (as the same version 5.1.1) with this chip - Samsung Xcover 3 and Samsung Galaxy Grand Prime. Fortunately, they have been both rooted in the past here.
Is this information really helpful to root my device? If so, is there any way to apply the previous methods to easily jailbreak DPT-RP1? I think the problem here is that it does not look like Android at all, so has no setting menu or developer tools. And not sure how to enter to the recovery mode since it only has two buttons - power/menu.
I'd appreciate any help or advice. Thanks!
And here you can find source codes.
oss.sony.net/Products/Linux/dp/DPT-RP1.html
sartrism said:
Sony recently released a new digital paper device DPT-RP1, apparently using their own linux firmware but underlying on Android 5.1.1. Few weeks ago, some Chinese successfully hacked it to jailbreak for third-party apps (without changing the original firmware), but they don't share any information to sell those hacked devices. I'm willing to pay for it, but it is too risky to send my device to China so I'm trying to root it by myself.
I don't know much about this world, but I found some information that might be helpful. It uses Marvell A140 IoT Processor a.k.a. PXA1908. There are two Android smartphones (as the same version 5.1.1) with this chip - Samsung Xcover 3 and Samsung Galaxy Grand Prime. Fortunately, they have been both rooted in the past here.
Is this information really helpful to root my device? If so, is there any way to apply the previous methods to easily jailbreak DPT-RP1? I think the problem here is that it does not look like Android at all, so has no setting menu or developer tools. And not sure how to enter to the recovery mode since it only has two buttons - power/menu.
I'd appreciate any help or advice. Thanks!
Click to expand...
Click to collapse
You must be an iPhone user that isn't familiar with android. Jailbreak in is an Apple thing, not an android thing.
In android it's called "rooting" and it isn't quite the same thing as jailbreaking an Apple device.
This device does not at all seem to be worth the price, especially considering the limitations it has. What a waste of hardware.
I would assume that you could port something from one of those other devices to work on yours but it really depends on how your hardware is designed compared to those devices.
Does your device have a typical bootloader like other android devices?
Is the bootloader unlocked?
If it is locked, can it be unlocked?
Does the device use fastboot or does it have a flash mode that is used with a specific PC flashtool?
If it is unlocked or if you can unlock it and it has a flash mode that can actually be used, you might be able to port a custom recovery from one of the devices you named then use that recovery to somehow root the device. If the device can't install android apps then it would probably involve using adb to root the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
You must be an iPhone user that isn't familiar with android. Jailbreak in is an Apple thing, not an android thing.
In android it's called "rooting" and it isn't quite the same thing as jailbreaking an Apple device.
This device does not at all seem to be worth the price, especially considering the limitations it has. What a waste of hardware.
I would assume that you could port something from one of those other devices to work on yours but it really depends on how your hardware is designed compared to those devices.
Does your device have a typical bootloader like other android devices?
Is the bootloader unlocked?
If it is locked, can it be unlocked?
Does the device use fastboot or does it have a flash mode that is used with a specific PC flashtool?
If it is unlocked or if you can unlock it and it has a flash mode that can actually be used, you might be able to port a custom recovery from one of the devices you named then use that recovery to somehow root the device. If the device can't install android apps then it would probably involve using adb to root the device.
Click to expand...
Click to collapse
Thanks for suggesting a general principle! I just use the word jailbreaking not because I'm an iPhone user. What I actually want to do as the first step is not rooting an android system, but revealing it from the current customized linux system. Rooting is the next step if necessary. If the word choice is still not accurate and bothers you, I apologize.
It has apparently no typical bootloader, and neither PC nor adb recognize it as an android device. In fact, direct USB file transfer is blocked so I need to use Sony's designated software. But an android system surely coexists according to the hacker who already rooted it.
sartrism said:
Thanks for suggesting a general principle! I just use the word jailbreaking not because I'm an iPhone user. What I actually want to do as the first step is not rooting an android system, but revealing it from the current customized linux system. Rooting is the next step if necessary. If the word choice is still not accurate and bothers you, I apologize.
It has apparently no typical bootloader, and neither PC nor adb recognize it as an android device. In fact, direct USB file transfer is blocked so I need to use Sony's designated software. But an android system surely coexists according to the hacker who already rooted it.
Click to expand...
Click to collapse
Without some kind of way to flash or interface with the device there isn't much you can do.
I have a kindle fire HD that didn't come with a typical android system but does have a typical bootloader. The Amazon OS was removed and now it's full blown android but it required a "second" bootloader. You don't have a bootloader so I'm not sure what your options are with that device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
You must be an iPhone user that isn't familiar with android. Jailbreak in is an Apple thing, not an android thing.
In android it's called "rooting" and it isn't quite the same thing as jailbreaking an Apple device.
This device does not at all seem to be worth the price, especially considering the limitations it has. What a waste of hardware.
I would assume that you could port something from one of those other devices to work on yours but it really depends on how your hardware is designed compared to those devices.
Does your device have a typical bootloader like other android devices?
Is the bootloader unlocked?
If it is locked, can it be unlocked?
Does the device use fastboot or does it have a flash mode that is used with a specific PC flashtool?
If it is unlocked or if you can unlock it and it has a flash mode that can actually be used, you might be able to port a custom recovery from one of the devices you named then use that recovery to somehow root the device. If the device can't install android apps then it would probably involve using adb to root the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Jailbreaking is the process of modifying any electronic device in order to remove restrictions imposed by a manufacturer (Apple) or operator (to allow the installation of unauthorized software).
Rooting is the act of gaining access to the root account of a device (such as a smartphone or computer).
There is a huge difference between the two. You can't just say that rooting is Android's version of jailbreaking. Not accurate in the least.
https://www.androidpit.com/jailbreak-android
Sent from my SM-G928T using Tapatalk
MarkBell said:
Jailbreaking is the process of modifying any electronic device in order to remove restrictions imposed by a manufacturer (Apple) or operator (to allow the installation of unauthorized software).
Rooting is the act of gaining access to the root account of a device (such as a smartphone or computer).
There is a huge difference between the two. You can't just say that rooting is Android's version of jailbreaking. Not accurate in the least.
https://www.androidpit.com/jailbreak-android
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
You're reading too much into what I said.
Basically, what I said was that jailbreaking isn't an android thing, it's an Apple thing(didn't say it was exclusively an Apple thing, just NOT an android thing). It applies to more than just Apple devices but on this website dedicated to mobile platforms, I'm only referring to its application in the mobile device world. For the mobile world it's pretty much only an Apple thing(still not exclusively but mostly so).
Then I said that in the android world it's called rooting(not exclusively an android thing, just NOT an Apple thing). And that jailbreaking and rooting aren't the same thing(this does not say that rooting is android's version of jailbreaking, that would imply that they are the same thing, I'm saying they aren't the same thing)
Basically, explaining what they "aren't", you explained what they "are".
I understand the difference, but thank you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
You're reading too much into what I said.
Basically, what I said was that jailbreaking isn't an android thing, it's an Apple thing(didn't say it was exclusively an Apple thing, just NOT an android thing). It applies to more than just Apple devices but on this website dedicated to mobile platforms, I'm only referring to its application in the mobile device world. For the mobile world it's pretty much only an Apple thing(still not exclusively but mostly so).
Then I said that in the android world it's called rooting(not exclusively an android thing, just NOT an Apple thing). And that jailbreaking and rooting aren't the same thing(this does not say that rooting is android's version of jailbreaking, that would imply that they are the same thing, I'm saying they aren't the same thing)
Basically, explaining what they "aren't", you explained what they "are".
I understand the difference, but thank you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I tend to read too deeply into everything. It's the way I am. Lol.
Sent from my SM-G928T using Tapatalk
Could you please post some information about usb device? Just like PID & VID.
Do it like:
Connect DPT-RP1 to Linux, and then type this command 'lsusb'
P.S. Under Windows or MacOS system, you can find the information from system settings...
happy to help with simple things
thisvip said:
Could you please post some information about usb device? Just like PID & VID.
Do it like:
Connect DPT-RP1 to Linux, and then type this command 'lsusb'
P.S. Under Windows or MacOS system, you can find the information from system settings...
Click to expand...
Click to collapse
Bus 001 Device 008: ID 054c:0be5 Sony Corp.
It is good to see some people have been interested in this thread.
So far, I realized that the hacker used a hardware hacking method. I actually obtained the hacked system apps from one of his customer. I guess he did sometihng like directly modifying eMMC to root and put "USBDeviceSwitcher.apk" to allow an usual USB connection. Since I don't want to take such risk, I decided to wait until the first firmware to see if there could be an indirect way to penetrate the system files. But if you want to analyze the hacked system, contact me.
sartrism said:
It is good to see some people have been interested in this thread.
So far, I realized that the hacker used a hardware hacking method. I actually obtained the hacked system apps from one of his customer. I guess he did sometihng like directly modifying eMMC to root and put "USBDeviceSwitcher.apk" to allow an usual USB connection. Since I don't want to take such risk, I decided to wait until the first firmware to see if there could be an indirect way to penetrate the system files. But if you want to analyze the hacked system, contact me.
Click to expand...
Click to collapse
Does it have a web browser? Maybe you can utilize for example the Stagefright Exploit + DirtyC0W to get root.
I have found out some interesting stuff about the device with the help of the Digital Paper App.
The app is built using electron and there is a file: /Applications/Digital\ Paper\ App.app/Contents/Resources/app.asar
This file contains the electron javascript files, which handle all the communication with the device.
It can be extracted with: sudo asar extract app.asar output
(github_com/electron/asar)
This also requires node to be installed: with e.g. brew install node (changelog_com/posts/install-node-js-with-homebrew-on-os-x)
The app communicates with the device via Restlet-Framework/2.3.7 on port 8443 with tcp (no matter if it is the bluetooth, wifi or usb connection).
This is the only port that is open.
In the file: /Applications/Digital\ Paper\ App.app/Contents/Resources/output/node_modules/mw-error/lib/codeparams.js you can find all the relative paths, which are getting called during e.g. file transfer, firmware update and stuff.
Running the app and placing breakpoints reveals that before you can transfer files and stuff:
'/auth'
'/auth/nonce/'
are called in order to authenticate, which looks e.g. like url digitalpaper.local:8443/auth/nonce/1e9ee24d-6613-433a-9770-76b04333ac95
the last part of the call is the "client_id": "1e9ee24d-6613-433a-9770-76b04333ac95", which is retrieved via the url digitalpaper.local:8443/auth call.
digitalpaper.local:8443/auth/
Important:
In /Applications/Digital\ Paper\ App.app/Contents/Resources/output/lib/config.js
change the line
config.DEVBUILD = false;
to
config.DEVBUILD = true;
After you finished your modifications you have pack the output folder again:
sudo asar pack output app.asar
I did not have time to continue, but the following relative urls look promising (especially recovery_mode):
'/testmode/auth/nonce',
'/testmode/auth',
'/testmode/launch',
'/testmode/recovery_mode',
'/testmode/assets/{}',
mcplectrum said:
I have found out some interesting stuff about the device with the help of the Digital Paper App.
The app is built using electron and there is a file: /Applications/Digital\ Paper\ App.app/Contents/Resources/app.asar
This file contains the electron javascript files, which handle all the communication with the device.
It can be extracted with: sudo asar extract app.asar output
(github_com/electron/asar)
This also requires node to be installed: with e.g. brew install node (changelog_com/posts/install-node-js-with-homebrew-on-os-x)
The app communicates with the device via Restlet-Framework/2.3.7 on port 8443 with tcp (no matter if it is the bluetooth, wifi or usb connection).
This is the only port that is open.
In the file: /Applications/Digital\ Paper\ App.app/Contents/Resources/output/node_modules/mw-error/lib/codeparams.js you can find all the relative paths, which are getting called during e.g. file transfer, firmware update and stuff.
Running the app and placing breakpoints reveals that before you can transfer files and stuff:
'/auth'
'/auth/nonce/'
are called in order to authenticate, which looks e.g. like url digitalpaper.local:8443/auth/nonce/1e9ee24d-6613-433a-9770-76b04333ac95
the last part of the call is the "client_id": "1e9ee24d-6613-433a-9770-76b04333ac95", which is retrieved via the url digitalpaper.local:8443/auth call.
digitalpaper.local:8443/auth/
Important:
In /Applications/Digital\ Paper\ App.app/Contents/Resources/output/lib/config.js
change the line
config.DEVBUILD = false;
to
config.DEVBUILD = true;
After you finished your modifications you have pack the output folder again:
sudo asar pack output app.asar
I did not have time to continue, but the following relative urls look promising (especially recovery_mode):
'/testmode/auth/nonce',
'/testmode/auth',
'/testmode/launch',
'/testmode/recovery_mode',
'/testmode/assets/{}',
Click to expand...
Click to collapse
Hope you get some result from wifi side. I also realized they use the port 8443 but couldn't get further as you.
For whom trying to hack it, here is the link for the already 'hacked' system apps (including the original files) - that of the famous hacked RP1 video. Inside the subfolder S1, there are also the hacked system apps for DPT-S1 just in case.
https://www.dropbox.com/sh/dvtvokdzrgwjc83/AACXOJA-E56nUpUfiWUOzrM3a?dl=0
George Malas said:
Does it have a web browser? Maybe you can utilize for example the Stagefright Exploit + DirtyC0W to get root.
Click to expand...
Click to collapse
The stock device has no web browser, no sd-card, no usb connection, and no typical system. I think SONY was haunted by some security issues maybe because they thought the major users are lawyers or very important people? lol
Any chance to create a buffer overflow PDF to attack RP1's pdf reader?
I am unable to help, but wanted to let you know I am definitely interested in and supportive of this. If this device can be unlocked as suggested in that one youtube video then I would buy it, despite the steep price.
jess91 said:
I am unable to help, but wanted to let you know I am definitely interested in and supportive of this. If this device can be unlocked as suggested in that one youtube video then I would buy it, despite the steep price.
Click to expand...
Click to collapse
If you're interested and supportive of this then go buy one anyway and apply yourself to going forward figuring out how to get it done. Other than that, you're not supportive, you're just hopeful that someone figures it out and then you'll probably go get one.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hey guys,
I also recently got the RP1 and am also looking for ways to mod it. Big kudos and thanks to all of you for posting this! This alread is amazing. @sartrism: can you maybe give me a hint how to load the files on the rp1? Sorry if this might be a stupid question but I'm new to adroid and that stuff.
Paderico said:
Hey guys,
I also recently got the RP1 and am also looking for ways to mod it. Big kudos and thanks to all of you for posting this! This alread is amazing. @sartrism: can you maybe give me a hint how to load the files on the rp1? Sorry if this might be a stupid question but I'm new to adroid and that stuff.
Click to expand...
Click to collapse
Just a little update from my side. I'm currently tryng to recreate the steps @mcplectrum was using. It seems that my RP1 also uses other ports. I tried to wireshark the USB and WiFi connection. By that I saw that often GET /registration/information is called for Host: localhost:58052. Moreover the first call is GET /register/serial_number also on port 5808. This was via USB.
Trying to trigger the /auth/ call via Telnet returns nothing unfortunately. But also the 8080 port is open. Trying to call digitalpaper.local:8443/auth/ returns nothing on firefox.
@mcplectrum: how did you get the client_id and what would one need that for?
I also tried to change the config.DEVBUILD to true but that seemed to change nothing at all.
So to sum up what we know:
The device is using some kind of android structure, the source code seems to use the uboot bootloader, all communication is done by a rest restlet framework. So actually there should be some kind of way to use the restlet framework to PUT or POST the modified files.
The other option would be directly flash the eMMC right? I would take the risk and just load it on my device and see what happens. Any hints on how to do that?