Related
Greeting,
It was heard that rooting T-01D are similar as F-05D.
I found a website regarding rooting F-05D, but I dont read Japanese, just want to know if anyone have tried the enclosed method to root T-01D?
or could anybody do the translation, since the terms become quite strange after using the online translators
The following link is ref. of rooting F-05D:
ttp://ayati.cocolog-nifty.com/blog/2012/01/f-05droot-1d0b.html
(should be "http" rather than "ttp")
The source code of T-01D have been provided also, but I have no idea how to use it and root the machine:
ttp://spf.fmworld.net/oss/t-01d/data/download.html
(should be "http" rather than "ttp")
Thank you very much in advance?
Update of 4/4
the following t-01d rooting procedures is provided by Magimaster
Hello.
I am sending this pm regarding the translation for flashing the Fujitsu f-05d sold by Docomo in Japan. I cannot reply in the development section due to my low post count.
My phone is an f-05d. I do not have a t-01d but, according to the original rooting guide for the f-05d, the users are reporting success in rooting the t-01d as well.
I will not really translate for you. Rather, I will explain what I did to root my f-05d.
Here is a rough summary of the steps I followed:
For starters, you need to make sure that adb recognizes your phone when connected to the PC via USB. This means that you need to install the Android SDK and the USB driver for your t-01d by Fujitsu.
I had trouble getting adb to recognize my phone, as Window$ insisted in recognizing it as an USB drive. What I did, among other things, was:
In the phone settings, go to Applications > Development and check USB Debigging and Stay awake.
Install the Google USB Driver package, in the extras section of the Android SDK Manager.
With the phone connected to the PC, go to Window$ device manager > Universal Serial Bus Controllers and uninstall (use the delete key from your the keyboard) every mass storage device that appeared when my phone was connected. Disconnect and reconnect the usb cable.
Only until I did this final step was my phone recognized and listed as Android Phone > Android Composite ADB Interface in the device manager. If your device is not recognized, you just cannot continue. Look for help about this, or else you cannot move on with this method of rooting.
Confirm that your phone is recognized as Android Phone > Android Composite ADB Interface in the Window$ device manager. Do not continue until it is.
From the Android SDK manager, install the package android sdk platform-tools.
You need download F05Droot.zip from the original blog page your linked before. I will not link to the file directly, but you should have no problem finding it. Extract the files within into the program directory \Android\android-sdk\platform-tools (this is my path).
You need to download a replacement for the file lsm_disabler.ko that is inside the F05Droot.zip. Get it from here and extract it an replace the one inside the platform-tools directory.
By the way, this platform-tools directory is the one that has the adb executable file. Just a heads up.
You need to download su. I cannot tell you where to get it. I just do not know where I got mine from, but was easy so go for it When you have it, extract it and put it in the platform-tools directory.
Confirm that the platform-tools directory includes these files:
Code:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
su
lsm_disabler.ko
f05dsu.bat
There will be more, but these are the ones needed for this to work.
Now, get ready to root. Connect your phone to the PC.
Go to your phone settings > setting my body > step/activity counter app > pedometer use and confirm it is checked on.
In the platform-tools directory, look for f05dsu.bat and run it. A DOS window will open. This is the funny part. Unless you are doing this from a Japanese version of Window$, or from a Window$ with Japanese locale active, you will see a lot of strange symbols instead of Japanese characters... which would be the same for almost anyone anyway Regardless, you will see a prompt to Press any key to continue . . .. At this point, you do not need to do anything on your phone, other than visually checking that the check mark on the pedometer is set.
On the DOS window press any key, your will see more garbage and another prompt to press any key. This is the important part. See if you can find among all those symbols this pattern: OFF/ON. If you do see it, it means we are on track.
Now that you were able to see the OFF/ON, go to your phone and uncheck the pedometer (OFF) and check it again (ON).
In the DOS window, press any key. Your phone will reboot. The message in the DOS window says that you must wait for the phone to boot up and for Window$ to recognize your usb connection to the phone.
When/if your phone is recognized by Window$, go to the DOS window and press any key.
Again, press any key and your phone will reboot.
The DOS window has a message indicating that you must now install superuser and busybox. When your phone reboots, go to the android market and install from there when you have the time.
You can now close the DOS window because, unless there was any error, you are now rooted, my friend
From the market, install a terminal, or an app that includes a terminal. I use Rom Toolbox because it has a terminal and scripts to mount the /system as rw.
Open whatever terminal you chose and, at the $ prompt type su
If new prompt is #, type soff
You will need to run these commands every time before trying to mount /system as rw.
That is all. I hope you can root your phone.
Just a petition, post this message in the forums, as it may help others who have similar difficulties. It sure could have helped me if someone had done before me.
Have a nice one and please forgive my English.
Click to expand...
Click to collapse
update 15/4
On 13/4 finally i got my phone rooted
I have to run f05droot.bat instead of f05dsu.bat
After I have run the f05dsu.bat, for the steps, no error popout.
then I open the terminal type su, it reply me "permission denied".
I know it is not successful, after several run, the situation still the same.
after that have checked the contents of f05droot.bat and f05dsu.bat.
They are very similar but the f05droot.bat will push the superuser and busybox into the device at the same time.
(so I added those files in the directory \Android\android-sdk\platform-tools )
Therefore, i tried that and its works finally.
I feel really exciting at that moment.
I hope this post can help they T-01d user to root the phone.
personally I really like this phone ^~^
the su file is also important
Anyone try it? Does it work?
I have got the source code from its web
But I dont know how to use that and lead me to root the machine
ttp://spf.fmworld.net/oss/t-01d/data/download.html
Can you post a review of this device?
redcarrot said:
Greeting,
It was heard that rooting T-01D are similar as F-05D.
I found a website regarding rooting F-05D, but I dont read Japanese, just want to know if anyone have tried the enclosed method to root T-01D?
or could anybody do the translation, since the terms become quite strange after using the online translators
The following link is ref. of rooting F-05D:
ttp://ayati.cocolog-nifty.com/blog/2012/01/f-05droot-1d0b.html
(should be "http" rather than "ttp")
The source code of T-01D have been provided also, but I have no idea how to use it and root the machine:
ttp://spf.fmworld.net/oss/t-01d/data/download.html
(should be "http" rather than "ttp")
Thank you very much in advance?
Click to expand...
Click to collapse
If you have time, can you please post a mini review of the device? I wanted to buy one too and I'm quite excited reading your review!
Thanks and more power!
Here is the mini review
Screen color is perfect except black and accurate. Speed is good in comparing with SGS2. Battery life is similar to SGS2. Form factor is better than SGS2. Camera is outstanding, thanks to the 1.3MP camera. Waterproofing design is what I like. The bad is upgrading is only possible in Japan. Digital TV is useless. Sound level is a bit low.
personally i like this phone very much especially the outlook.
my personal review is the following:
1. same as above the screen is perfect
2. the camera is also excellent
3. while you have a phone call, it change mode automatically depends on the environment
4. if i switch off all the data things, this phone can stand more than one day
(so i wont blame the battery, because I think we use too many network related stuffs)
5. i have to admit that the firmware is not quite stable (fortunately the phone can be upgrade to 4.0 after july)
for the rooting process, it seems like someone has success:
(i think that is temp root)
search "T-01D 軟解, tofu-keitai" in google (that is chinese unfortunately)
redcarrot said:
Greeting,
It was heard that rooting T-01D are similar as F-05D.
I found a website regarding rooting F-05D, but I dont read Japanese, just want to know if anyone have tried the enclosed method to root T-01D?
or could anybody do the translation, since the terms become quite strange after using the online translators
The following link is ref. of rooting F-05D:
ttp://ayati.cocolog-nifty.com/blog/2012/01/f-05droot-1d0b.html
(should be "http" rather than "ttp")
The source code of T-01D have been provided also, but I have no idea how to use it and root the machine:
ttp://spf.fmworld.net/oss/t-01d/data/download.html
(should be "http" rather than "ttp")
Thank you very much in advance?
Update of 4/4
the following t-01d rooting procedures is provided by Magimaster
Click to expand...
Click to collapse
It really work!~
I rooted my T-01D with this method!
And it's permanent root!!
Many thanks!~
hi HaoyuWen,
i have followed the steps, when i type su in the terminal simulator, it comes out segmentation fault su, do you have any idea.
I use titanium backup to check and it said my t-01d is not rooted.
for the pedometer on/off things, do i need to press the home key and go back to the pedometer to do the switch?
Thank you very much in advance
HaoyuWen said:
It really work!~
I rooted my T-01D with this method!
And it's permanent root!!
Many thanks!~
Click to expand...
Click to collapse
So both F-05D and T-01D can use this ?
yes, but i havnt got that work yet.
just want to know when I get the device rooted, will the device screen shows the device is rooted?
finally i got my phone rooted
you have to run f05droot.bat instead of f05dsu.bat
the su file is also important
redcarrot said:
yes, but i havnt got that work yet.
just want to know when I get the device rooted, will the device screen shows the device is rooted?
Click to expand...
Click to collapse
You can install a root checker to see
^ Please update it on the front page
Gonna get mine soon, so excited to hear this
wth_is_life said:
You can install a root checker to see
^ Please update it on the front page
Gonna get mine soon, so excited to hear this
Click to expand...
Click to collapse
I think I brick my T-01D. Don' know why, I do exactly the same what I have been told here... Now It ends up infinite boot loop
Anybody help me please?
Hey there everyone, sadly this guide isn't working for me. Everything in the guide goes smoothly and I do exactly what is listed but after my phone reboots the final time I still have no root access. I run f05droot.bat instead of f05dsu.bat like the user said but to no avail, I even ran f05dsu.bat and still nothing.
Anyone else have trouble? Maybe it is because I am on a certain FW? I am on 2.3.5
Baseband Version C_L1_M23
Kernel version: 2.6.35.7 [email protected] #1
and Build number is V43R41C
Just wondering as I really want root to disable all of these RAM-hogging default applications.
Bump? Anyone?
As far as I know, this rooting method cannot be done on FW V43R41C.
Sent from my SC-01D using Tapatalk 2
kinchung said:
As far as I know, this rooting method cannot be done on FW V43R41C.
Sent from my SC-01D using Tapatalk 2
Click to expand...
Click to collapse
Aw Thanks for the notice, of course it's my firmware. Any idea about ICS? It was supposed to come out in July but yeah..
I don't know about ICS for t-01d. My sc-01d has been already upgraded to ICS, the performance is improved a lot. sh-01d also gets ICS today.
Sent from my SC-01D using Tapatalk 2
kinchung said:
I don't know about ICS for t-01d. My sc-01d has been already upgraded to ICS, the performance is improved a lot. sh-01d also gets ICS today.
Sent from my SC-01D using Tapatalk 2
Click to expand...
Click to collapse
I see, I read about the T-01D (among many others) getting updated from articles like this: http://forums.hardwarezone.com.sg/e.../docomo-update-ics-4-0-18-models-3662812.html
I'm sure the T-01D would perform pretty awesome and maybe pre-installed software would not be as big a deal as it is now. Maybe since your SH-01D is getting updated, T-01D isn't far behind. The only thing I have to see is if I can update out of Japan.
I don't have sh-01d but galaxy tab 10.1 sc-01d instead. My t-01d also upgraded to V43R41C last month during visiting Japan. Upgrade of t-01d may not be possible outside Japan as Software Update cannot be executed without docomo sim and network.
Sent from my SC-01D using Tapatalk 2
Hi everybody,
Good evening!
I recently came across a post about almost 50% android devices being vulnerable. Duo securities has made this finding using an app 'X-Ray'. They mention following 8 types of vulnerabilities: 1. Ashmem 2. Exploid 3. Gingerbreak 4. Levitator 5. Mempodroid 6. Wunderbar 7. Zergrush, and 8. Zimperlich. Please see this link for details: http://www.xray.io/#vulnerabilitieshttp://www.xray.io/#vulnerabilities
I downloaded the app 'X-Ray' and did a X-ray of my Desire Z. It came out clean for all but one vulnerability, Mempodroid. I've a rooted and S-off desire z and am using Jelly Bean rom (andromadus Test Build, .85). The website gives following details for the Mempodroid:
"Inherited from the upstream Linux kernel, a vulnerability in the /proc/pid/mem interface allows for writing arbitrary memory in the address space of a setuid process. It's about as complicated as it sounds, but attackers are smart like that."
I cross checked the same X-ray with a different rom, this time GenY (Sense 4 based ICS Rom). The results were similar. I don't know much about these vulnerabilities so thought of putting this question in this learned forum. Please clear my following doubts:
1. Is this Mempodroid is a serious problem?
2. Since this is surfacing in different roms, it should not be a ROM-specific issue but a device-specific one. Is there anything that I can do to remove this vulnerability.
3. What possible harm can it do to me?
Thanks,
dcpathak
HTC Desire Z (Rooted & S-Off)
Those sound like root methods, or at least the few I recognize. Basically it would be possible for a malicious app to have a root exploit built it so that it could get su permissions and potentially do some real damage. Even if your device was already rooted with Superuser installed the root exploit would bypass the superuser prompt since it doesn't need root to get su. As long as you download apps straight from Google Play and check the reviews first to make sure its legit, you'll be fine. These malicious apps are turning up on sites that distribute pirated software.
If you've used one of the root methods listed to root your device, don't worry. Any root method is technically a security vulnerability.
Thanks, I also remembered that some of these vulnerabilities are names of root methods, for instance, Gingerbreak, Zergrush etc. Further, I think Mempodroid may have something to do with the processor speed management (just a wild guess).
dcpathak
Just don't install apps from dubious sources and your fine.
While those loop holes could be exploited, you will need to have downloaded an app that does this in the first place.
Guy's the HDX is a fairly new device, the complete line has not even begun shipping yet & development is in it's infancy.
Currently, you can root your device, but it is HIGHLY recommended that you WAIT.
Currently, there are NO, ZERO, NONE, utilities or consistent fixes for soft bricked devices. This is not good, as currently there are several things that can soft brick this device.
In no circumstances should you do any of the following:
Remove apps or any files from the system folder or any sub-directory.
Restore previous veersions of Kindle apps from a Fire HD.
Make any modifications to any of the build.prop settings, or add any lines to the build.prop
Working but not advised at this time:
Adding any files or apks to the system partition or any sub-directory
There are numerous instances of modifications causing bootloops, soft bricks & KILLING ADB access. To my knowledge, I am the only person that has successfully recovered ADB access & for all the money in the world, I could not tell you how.
If you are not extremely proficient with reverse engineering software, or you don't know all the relevant ADB commands because you have been hacking devices for years, I STRONGLY suggest you wait to even root until further development progress has been made.
If you ignore this warning, you are likely going to be on your own in trying fix it, or you may be waiting months for a consistent fix to be found.
If you like taking risk & tinkering & you like to burn hundred dollar bills just for the pretty orange flame, well, by all means, go right ahead. Just realize right now, there may not ever be a recovery for your particular dilemma & in all likelihood by ignoring this warning, you've already made your warranty null & void.
Well said buddy.
I consider myself a fairly advanced android and linux user and I've customised the heck out of my n4 but I'm leaving my hdx as it is for now.
Good advise there.
Now if only mayday had a pro feature to help with rooting... haha
Can we set jcase up with a webcam? Lol
Sent from my Nexus 4 using Tapatalk
GSLEON3 said:
Currently, you can root your device, but it is HIGHLY recommended that you WAIT.
Currently, there are NO, ZERO, NONE, utilities or consistent fixes for soft bricked devices. This is not good, as currently there are several things that can soft brick this device.
Click to expand...
Click to collapse
Safestrap! Safestrap!
http://forum.xda-developers.com/showthread.php?t=2556677
Firstly, this was posted before SafeStrap. Plus, I highly doubt even Hashcode would recommend new users mess with SafeStrap right now. I'm by no means a master developer, but I've been around a long time & I've participated in some pretty cool low level hacking with some of the old timers & I'll be the first to say that there is some funky stuff going on in the HDX. Amazon has not exactly gone out of their way to make modding safe or easy. Plus there's not a whole lot out there yet that requires an custom recovery. It may be fine for you or I, but it can open a whole other host of issues if used improperly.
Sent from my KFJWA using XDA Premium HD app
Hey there I am new to this forums! Got a kindle yesterday (as a gift) and moved straight to xda to see what's cooking unfortunately I was a bit disappointed because there is no "cooking" at all. I hope this has to do with the fact that it's a new device and nobody has tried to make some roms for it yet... Nevertheless I am quite happy with it, although this fire os is a pretty pain in the eyes. Thank God I have managed to get the YouTube app sync with my Google account, plus some other gapps like drive. Well that's it for the moment, I just didn't want to make a new thread so I posted in here. So what do you think, will there be some good roms for this device? And/or maybe we could use those for the kindle fire hd?
Sent from beneath my cloak of magic
Thanks for the info I'm super new at this but was thinking buying one of these. But now that I am acquainted with Flashing ROMs and stuff it's sort of a deal breaker if it's not being done. If I can't modify it, whats the point?
HDX rooting?
I bought a Fire HDX 7" to replace a Nook HD+ for better HW. I thought I read you could root it or at least get the google play store on it, but it appears that is not the case. I guess I misunderstood what I read. Really disappointed now.
Any new news on rooting these things?
blackfox003 said:
I bought a Fire HDX 7" to replace a Nook HD+ for better HW. I thought I read you could root it or at least get the google play store on it, but it appears that is not the case. I guess I misunderstood what I read. Really disappointed now.
Any new news on rooting these things?
Click to expand...
Click to collapse
Patience good people. Each day a few qualified devs get a little closer ... all on their own free time. A crack might be right around the corner.
Well, it's almost June and development for the Kindle tablets seem to still be very slow, what's the story?
blackfox003 said:
I bought a Fire HDX 7" to replace a Nook HD+ for better HW. I thought I read you could root it or at least get the google play store on it, but it appears that is not the case. I guess I misunderstood what I read. Really disappointed now.
Any new news on rooting these things?
Click to expand...
Click to collapse
You can get root and the Google Play Store on an older firmware, just not any of the newest couple. Yet (I hope).
Good to go: I was able to use hdx-toolkit with my router blocking
Hey everyone.
In case this helps, I was able to ensure that my kindle didn't update by blocking all Internet access at my firewall (Verizon FiOS router) for the device. I looked up its MAC address under "Wireless" -> "Wi-Fi" and configured a rule to block all access.
I confirmed my device version via Apps -> Settings -> System Updates -> Current Version: 13.3.1.0 (factory fresh!)
Then, using my PC I ran the hdx-toolkit 0.94 and after resolving an initial snag (the toolkit couldn't access my device) I was able to do steps 1 (driver), 5 (check if rooted which also checks connectivity), 8 (towelroot), 2 (SuperSU), 5 (confirm root), 4 (block OTA) from the toolkit menu.
Note, the toolkit doesn't want to run from a network share. I copied it down onto my computer's local hard disk first.
My specific issue preventing the ADB setup was I didn't realize the Microsoft driver (to make the device show up as a USB phone device) was blocking the ADB driver from coming up. After uninstalling the Microsoft driver (under device manager - Portable devices for the device "kindle") and installing the device driver for Android Composite ADB Interface, I was able to get the ADB driver to install without error. Symptom of the driver conflict was the end of the installer sequence said "driver not installed correctly or need to reboot".
I am using Windows 8 on a Dell desktop
sabasc said:
Hey everyone.
In case this helps, I was able to ensure that my kindle didn't update by blocking all Internet access at my firewall (Verizon FiOS router) for the device. I looked up its MAC address under "Wireless" -> "Wi-Fi" and configured a rule to block all access.
I confirmed my device version via Apps -> Settings -> System Updates -> Current Version: 13.3.1.0 (factory fresh!)
Then, using my PC I ran the hdx-toolkit 0.94 and after resolving an initial snag (the toolkit couldn't access my device) I was able to do steps 1 (driver), 5 (check if rooted which also checks connectivity), 8 (towelroot), 2 (SuperSU), 5 (confirm root), 4 (block OTA) from the toolkit menu.
Note, the toolkit doesn't want to run from a network share. I copied it down onto my computer's local hard disk first.
My specific issue preventing the ADB setup was I didn't realize the Microsoft driver (to make the device show up as a USB phone device) was blocking the ADB driver from coming up. After uninstalling the Microsoft driver (under device manager - Portable devices for the device "kindle") and installing the device driver for Android Composite ADB Interface, I was able to get the ADB driver to install without error. Symptom of the driver conflict was the end of the installer sequence said "driver not installed correctly or need to reboot".
I am using Windows 8 on a Dell desktop
Click to expand...
Click to collapse
I'm sorry I missed this. Great advise though.
A default Microsoft driver was blocking the Amazon ADB driver from coming up. After uninstalling the Microsoft driver (under device manager - Portable devices for the device "kindle") and installing the device driver for Android Composite ADB Interface, I was able to get the ADB driver to install. --Win8/Win8.1
Click to expand...
Click to collapse
The toolkit needs to be run locally because well the adb connection won't go through your share to your computer.
GSLEON3 said:
Guy's the HDX is a fairly new device, the complete line has not even begun shipping yet & development is in it's infancy.
Currently, you can root your device, but it is HIGHLY recommended that you WAIT.
Currently, there are NO, ZERO, NONE, utilities or consistent fixes for soft bricked devices. This is not good, as currently there are several things that can soft brick this device.
In no circumstances should you do any of the following:
Remove apps or any files from the system folder or any sub-directory.
Restore previous veersions of Kindle apps from a Fire HD.
Make any modifications to any of the build.prop settings, or add any lines to the build.prop
Working but not advised at this time:
Adding any files or apks to the system partition or any sub-directory
There are numerous instances of modifications causing bootloops, soft bricks & KILLING ADB access. To my knowledge, I am the only person that has successfully recovered ADB access & for all the money in the world, I could not tell you how.
If you are not extremely proficient with reverse engineering software, or you don't know all the relevant ADB commands because you have been hacking devices for years, I STRONGLY suggest you wait to even root until further development progress has been made.
If you ignore this warning, you are likely going to be on your own in trying fix it, or you may be waiting months for a consistent fix to be found.
If you like taking risk & tinkering & you like to burn hundred dollar bills just for the pretty orange flame, well, by all means, go right ahead. Just realize right now, there may not ever be a recovery for your particular dilemma & in all likelihood by ignoring this warning, you've already made your warranty null & void.
Click to expand...
Click to collapse
Is this still the case? Just wondering if this thread needs to be updated because some of what's written here seem to contradict what I've read people are doing with their hdx.
my 8.9HD ver. 8.5.1
Is my kindle an HDX?
ant17 said:
Is my kindle an HDX?
Click to expand...
Click to collapse
No, you can find anything related to your kindle here
Hello,
Just to make sure I understood all the info published around:
A Kindle Fire HDX running FireOS 4.5.2 cannot be brought to a state where it can be jailbroken and and alternate ROM installed.
Even the downgrade performed by Amazon operators is to a version too high to allow jailbreaking and installing other ROM.
Am I correct with this assessment?
hfpop said:
Hello,
Just to make sure I understood all the info published around:
A Kindle Fire HDX running FireOS 4.5.2 cannot be brought to a state where it can be jailbroken and and alternate ROM installed.
Even the downgrade performed by Amazon operators is to a version too high to allow jailbreaking and installing other ROM.
Am I correct with this assessment?
Click to expand...
Click to collapse
to an extent yes,most custom roms cannot be installed but if you rolled back you can still root and instal the hdx nexus 2.0.2 rom which is pretty much most of what the device needs
@Davengerr: I understand that I can rollback to 3.2.8 and need at most 3.2.6 to install nexus 2.0.2. No?
hfpop said:
@Davengerr: I understand that I can rollback to 3.2.8 and need at most 3.2.6 to install nexus 2.0.2. No?
Click to expand...
Click to collapse
i have it on 3.2.7 on my device and this here lists what you can do with a 3.2.8
http://forum.xda-developers.com/kin...o-13-3-2-7-t2993089/post58150015#post58150015
@Davengerr: Thank you. All worked out greatly.
Hello,
I have an external USB camera(endoscope) that I'd like to use with my Huawei Mediapad tablet. I've been googling and its possible, there is no hardware restrictions since USB OTG is working(tested with thumb drive). I'm not sure about UVC drivers but there are a few other problems that might be causing the problem.
Reading a blog i discovered that since KitKat(this tablet has 4.4.4) the SELinux policy is set to "enforced" and therefore apps can't access external USB camera feeds like they used to straight out of the box. There are 3 workarounds which all require rooting.
1. Start the app with superuser rights
2. Configure SELinux to allow USB cam feed
3. Custrom rom
Blog link: htt ps://droidperception.wordpress. com/2013/12/01/webcams-on-android-4-4/
So it all comes down to this - I need to have this device rooted but I haven't even found a single thread about this model in this forum.
NB! I don't have room for experimentation(read: bricking the device) since the device is not mine.
Thanks for you attention,
Pask
You ask quite a while ago and I see no answer. So, just in case, I did root mine in a way I not necessary would recommend, but ... KingRoot latest version can do a trick, but it definitely not kind of software I would keep on my tablet. So after that I install SuperSU, Link2SD ( using it to get rid of applications I do not like) and RootExplorer + Terminal. Give all of them root access using KingRoot manager and with help of Super-Sume App (will cost you some money) start a process of getting read of all related to KingRoot and Co. It is more tricky that one may think but by freezing and killing some processes in "write" time I manage to install SupeSU binaries and remove left overs. I still have problems to get su requests, so just copy config files from my phone with access rights already given to specific applications and deny access to anything else. So far do not see anything I cannot identify running, so my hope KingRoot is completly gone.
So far I did not fine any other tools/methods to get root
Hi everyone, nice to meet you all! :highfive:
First of all thanks to this great community for the invaluable help provided to countless geeks like me
I purchased 2 Palm PVG100 (Pepito) phones to start working with their ROMs and firmware.
There is very little development on this model and I would like to start a new thread for this.
I have gathered and followed many guides, but I still would need your help if any of you is so kind to collaborate with me
First step I would like to take, to avoid problems, is taking a full EMMC backup of this phone, using a tool named QPST, its components and a program called HDDRawCopy.
Unfortunately I'm getting stuck in this process.
Can anybody please provide me with some guidance?!
Thank you very much in advance!
Very interested to see where you can take this, I just picked up one of these for super cheap as a backup phone. Would love to tweak it.
In an attempt to de-bloat the device I used an adb shell to uninstall the following apps using "pm uninstall -k --user 0 'app name here'". So far no negative effects that I can tell, but still have the darn non-VZW SIM message at top.
com.verizon.cloudsetupwizard
com.verizon.mips.services
com.vzw.hss.myverizon
com.jrd.verizonuriintentservice
com.verizon.messaging.vzmsgs
com.verizon.llkagent
com.vzw.apnlib
com.vzw.hss.myverizon
com.tcl.vzwintents
com.tct.vzwwifioffload
com.vzw.ecid
com.vzw.easvalidation
com.customermobile.preload.vzw
com.vcast.mediamanager
Very excited about this as well. Subscribed.
The first milestone is to unlock the bootloader, correct?
Yeah, and if you can figure out a way to get to the bootloader let me know... Every time I try to reboot to it, it just reboots to system.
source code
Hi guys!
I think I found the source code/bootloader for the PVG100. After a whole lot of digging, I now have this .zip from the founder himself, and it is for the original 2018 firmware, not with any of the updates. I'll attach the link below.
I am definitely a novice tinkerer, not a developer. I don't have any of the skills or tools to make a custom ROM, though I very much want one to remove the bloatware and enable hotspot tethering etc. Stormskeeker, could you please post whatever you have managed to find so far, or explain how you have been able to tweak it?
I also have a couple of these that are inoperable for various reasons that I have thoroughly dissected. So if anyone needs to buy any of my spare parts, or wants to just know more about the Palm's guts, then hit me up!
This is SUCH a rad little phone. Biggest complaint by far is battery life, and I would LOVE if someone help me figure out how to power this phone with a bigger battery. I found a Oneplus battery has the same connector, but it won't work when I connect it (unless it's plugged in to a wall adapter)... does this have something to do with the firmware not accepting a different battery? Does Anyone know how I can get around this??
https://sourceforge.net/projects/palmopensource/[/url]
Sounds like we're off to a good start!
hardbodyrichert said:
Hi guys!
I think I found the source code/bootloader for the PVG100. After a whole lot of digging, I now have this .zip from the founder himself, and it is for the original 2018 firmware, not with any of the updates. I'll attach the link below.
I am definitely a novice tinkerer, not a developer. I don't have any of the skills or tools to make a custom ROM, though I very much want one to remove the bloatware and enable hotspot tethering etc. Stormskeeker, could you please post whatever you have managed to find so far, or explain how you have been able to tweak it?
I also have a couple of these that are inoperable for various reasons that I have thoroughly dissected. So if anyone needs to buy any of my spare parts, or wants to just know more about the Palm's guts, then hit me up!
This is SUCH a rad little phone. Biggest complaint by far is battery life, and I would LOVE if someone help me figure out how to power this phone with a bigger battery. I found a Oneplus battery has the same connector, but it won't work when I connect it (unless it's plugged in to a wall adapter)... does this have something to do with the firmware not accepting a different battery? Does Anyone know how I can get around this??
https://sourceforge.net/projects/palmopensource/[/url]
Click to expand...
Click to collapse
Guys, we have a progress!
See my post on another thread:
https://forum.xda-developers.com/showpost.php?p=80686683&postcount=66
Great team work, guys, I knew this community was great! :laugh:
Special thanks for this achievement to:
Maddie Stone for discovering the cve2019-2215 vulnerability (https://twitter.com/maddiestone/status/1179917132575887360)
Grant Hernandez for writing great code and a great tutorial to explain why and how the magic works (https://hernan.de/blog/2019/10/15/tailoring-cve-2019-2215-to-achieve-root/)
arpruss for writing great code for this exploit and for responding promptly to my messages to guide us in the process (https://github.com/arpruss/cve2019-2215-3.18)
greatjack1 for pointing out that Palm PVG100 (Pepito) kernel version can be associated with vulnerability cve2019-2215 and for starting a new thread with a walkthrough for the rooting process (https://forum.xda-developers.com/android/help/palm-phone-pvg-100-temp-root-guide-t3992043)
Now, guys, what are the next steps? (besides waiting for responses to my email message to "rodrigo", from Palm company)
Can we compile a TWRP version now that we have temporary root privileges, maybe following the following guide?
https://forum.xda-developers.com/showthread.php?p=32965365#post32965365
Is there a way to backtrack what application might be preventing us from unlocking the bootloader?
Maybe Verizon did something like this:
https://www.xda-developers.com/unlock-bootloader-verizon-google-pixel-xl/
Maybe the Verizon app preventing bootloader unlock (if this is what they did) is the same app that pops up a notification saying that the SIM card is not from Verizon, when you boot the phone with a different SIM card...is there a way to catch which app is responsible for that notification?
Permanent root suggestion
Hi, guys, after this great achievement, permanent root might be desirable.
I'll tell you a story...I've always loved qwerty phones and one of the rare phones I've always wanted is NEC Terrain (distributed by AT&T). Unfortunately AT&T has locked it to its network and I found no working solution for unlocking it for other SIM cards (please let me know if you know of a working SIM unlock service!), BUT I've always wanted to gain permanent root privileges for this device. The story of NEC Terrain is very similar to Palm Phone PVG100 (Pepito):
NEC Terrain was released by AT&T and the bootloader locked, while Palm Phone PVG100 (Pepito) was released by Verizon and the bootloader locked...
NEC company is not on the market anymore and Palm company is in a similar condition, which makes contacts with the company difficult and the hope of updates to be released unlikely...
Code for NEC Terrain was developed by enthusiasts (https://github.com/android-rooting-tools/android_run_root_shell) similar to arpruss code for Palm Phone PVG100 (Pepito) (https://github.com/arpruss/cve2019-2215-3.18)...
Temporary root solution for NEC Terrain was achieved (https://github.com/x29a/nec_terrain_root) like root solution for Palm Phone PVG100 (Pepito) was achieved (https://github.com/arpruss/cve2019-2215-3.18/tree/master/release)...
For NEC Terrain a creative permanent root solution was developed by x29a (https://github.com/x29a/nec_terrain_root/blob/master/terroot/README.md) and now my suggestion is that we might want to follow his steps for Palm Phone PVG100 (Pepito)!
Here are the details of "HOW ALEX-KAS DID IT"!:
https://forum.xda-developers.com/showpost.php?p=61542922&postcount=186
Does anyone of you find this path convincing?
Why is there three threads about this?
Mattzees said:
Why is there three threads about this?
Click to expand...
Click to collapse
People started them independently and each one is on a specific thing, but all things are connected (there are interconnections and it's not always clear if rooting helps unlocking bootloader or if unlocking bootloader helps permanently rooting or if for compiling custom recoveries (TWRP) one needs root or bootloader unlocking), so these threads have a reason to exist and there are overlaps, but feel free to let people know if you want to merge something!
Mattzees said:
Why is there three threads about this?
Click to expand...
Click to collapse
StormSeeker1 said:
People started them independently and each one is on a specific thing, but all things are connected (there are interconnections and it's not always clear if rooting helps unlocking bootloader or if unlocking bootloader helps permanently rooting or if for compiling custom recoveries (TWRP) one needs root or bootloader unlocking), so these threads have a reason to exist and there are overlaps, but feel free to let people know if you want to merge something!
Click to expand...
Click to collapse
I would suggest adding comments in this thread requesting a device forum: https://forum.xda-developers.com/showthread.php?t=1660354
It will be much easier to keep track of all the different discussions about this phones if they are all organized in one place.
ssuds said:
I would suggest adding comments in this thread requesting a device forum: https://forum.xda-developers.com/showthread.php?t=1660354
It will be much easier to keep track of all the different discussions about this phones if they are all organized in one place.
Click to expand...
Click to collapse
Please, feel free to do that, move forward
StormSeeker1 said:
Please, feel free to do that, move forward
Click to expand...
Click to collapse
I already had, I was mainly suggesting for more people to chime in. But they created an Enhanced Topic for the PVG100: https://forum.xda-developers.com/t/palm-palm
Once that has more than 3 pages of threads, they can convert it to a full forum.
See https://forum.xda-developers.com/showpost.php?p=80913393&postcount=23641
So I'm confused... If I have read everything correctly, the phone can only be temporarily rooted, meaning every time I reboot I lose root? Thanks in advance to all the smart folks who can figure this stuff out... Is anyone still working on a permanent root solution?
grimez said:
In an attempt to de-bloat the device I used an adb shell to uninstall the following apps using "pm uninstall -k --user 0 'app name here'". So far no negative effects that I can tell, but still have the darn non-VZW SIM message at top.
com.verizon.cloudsetupwizard
com.verizon.mips.services
com.vzw.hss.myverizon
com.jrd.verizonuriintentservice
com.verizon.messaging.vzmsgs
com.verizon.llkagent
com.vzw.apnlib
com.vzw.hss.myverizon
com.tcl.vzwintents
com.tct.vzwwifioffload
com.vzw.ecid
com.vzw.easvalidation
com.customermobile.preload.vzw
com.vcast.mediamanager
com.telecomsys.directedsms.android.SCG
Click to expand...
Click to collapse
com.telecomsys.directedsms.android.SCG is required for SMS.
After uninstalling I reinstalled and now have permission issues in logcat which I'm attempting to fix.
11-25 22:30:58.746 1219 1252 W BroadcastQueue: Permission Denial: receiving Intent { act=android.provider.Telephony.SMS_RECEIVED flg=0x19000010 (has extras) } to ProcessRecord{de99436 7663:
com.telecomsys.directedsms.android.SCG/u0a112} (pid=7663, uid=10112) requires android.permission.RECEIVE_SMS due to sender com.android.phone (uid 1001)
11-25 22:30:58.747 1219 1252 W BroadcastQueue: Permission Denial: receiving Intent { act=android.provider.Telephony.SMS_RECEIVED flg=0x19000010 (has extras) } to com.google.android.gms/.chi
mera.GmsIntentOperationService$GmsExternalReceiver requires android.permission.RECEIVE_SMS due to sender com.android.phone (uid 1001)
Update
I resolved the permissions, rebooted and sms are back.
snoopy20 said:
com.telecomsys.directedsms.android.SCG is required for SMS.
After uninstalling I reinstalled and now have permission issues in logcat which I'm attempting to fix.
11-25 22:30:58.746 1219 1252 W BroadcastQueue: Permission Denial: receiving Intent { act=android.provider.Telephony.SMS_RECEIVED flg=0x19000010 (has extras) } to ProcessRecord{de99436 7663:
com.telecomsys.directedsms.android.SCG/u0a112} (pid=7663, uid=10112) requires android.permission.RECEIVE_SMS due to sender com.android.phone (uid 1001)
11-25 22:30:58.747 1219 1252 W BroadcastQueue: Permission Denial: receiving Intent { act=android.provider.Telephony.SMS_RECEIVED flg=0x19000010 (has extras) } to com.google.android.gms/.chi
mera.GmsIntentOperationService$GmsExternalReceiver requires android.permission.RECEIVE_SMS due to sender com.android.phone (uid 1001)
Update
I resolved the permissions, rebooted and sms are back.
Click to expand...
Click to collapse
Hey Snoop--
I see that you've messed around with the telephony files while debloating. I have removed most of those files as well. However, I recently wanted to switch carriers (from Verizon to Visible), and it looks like PVG100 doesn't let you edit APN settings (no matter what SIM cards you try with). I really need to add an APN address to get the new SIM to work. Do you know of any way to do this with what's available to us currently, and since last I checked we haven't gotten into the bootloader yet?
And while we're at it, have you been able to enable wifi hotspot? Or is the tethering provisioning a file we might just be able to pull out in adb?
Cheers!
---------- Post added at 03:28 AM ---------- Previous post was at 03:21 AM ----------
StormSeeker1 said:
People started them independently and each one is on a specific thing, but all things are connected (there are interconnections and it's not always clear if rooting helps unlocking bootloader or if unlocking bootloader helps permanently rooting or if for compiling custom recoveries (TWRP) one needs root or bootloader unlocking), so these threads have a reason to exist and there are overlaps, but feel free to let people know if you want to merge something!
Click to expand...
Click to collapse
The EU version (Vodaphone) of the firmware has an unlockable bootloader. Can anyone point me in the right direction to find a full firmware image? I have a bricked palm that I'm going to try to flash with the NON-Verizon version of the ROM, so that I can then try to access the bootloader from there.
Hi,
I haven't been able to play as the so called root exploit appears to open a shell but root is still restricted for remounting the partitions.
Wifi tethering is a no go at the moment. You can use USB tethering fine but must remember to disconnect the phone if the power source sleeps with it enabled or battery plummets. I imagine they hid the feature rather than fix this bug.
Palm say a new product they're working on has wifi tethering enabled.
Andrew
hardbodyrichert said:
Hey Snoop--
I see that you've messed around with the telephony files while debloating. I have removed most of those files as well. However, I recently wanted to switch carriers (from Verizon to Visible), and it looks like PVG100 doesn't let you edit APN settings (no matter what SIM cards you try with). I really need to add an APN address to get the new SIM to work. Do you know of any way to do this with what's available to us currently, and since last I checked we haven't gotten into the bootloader yet?
Click to expand...
Click to collapse
There's an ADB command to open the APN settings, have you tried that?
Code:
adb shell am start -a android.intent.action.MAIN content://telephony/carriers
recompile the kernel for special modules
I can't make a new thread yet, because of lack of karma, but I'm wondering if anyone here has tried to compile at least kernel modules?
I got the palm kernel source code from sourceforge.net/projects/palmopensource/files/PVG100/PVG100_OpenSource_SourceCode_20181016.tar.xz/download and I see a lot of files in there, but not a full kernel tree if only due to the missing Kconfig files.
I'm familiar with kernel compilation and cross compiling, but not so much with android
I googled msm-3.18 and found github.com/android-linux-stable/msm-3.18 so I suppose I should add palm files on top of that but I'm not sure. Any help would be appreciated.
My goal is to compile modules like NBD-driver sites.google.com/site/devwom/usb-sharer/nbd-driver which only require adding an extra option during the menuconfig and cross compiling.