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.
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
Hello everybody.
This is my first post, and while I am noob at XDA-Developers, I have spent more than 10 years writing and reading in forums, and I know what has to be done before writing on them. And I did. I have a couple of questions that I think they are not easy to answer. Indeed, I spent 8 hours yesterday searching through the interwebs and this forum to try to figure out the most thorough answer. And I think I figured out mine, but I don't know any people that can reinforce my toughts and tell me "Hey Gabriel: you are right, you did well, you are the man: go out for a beer, keep calm and carry on". I will ask the questions first, and later I will explain why I ask such questions, and finally what are the steps I did.
The questions are: How can I remove root from a custom rom, and how can I be sure that I properly did? I know that many of us think that "This is stupid / Why do you want to do such a thing / the power of your phone will... / go to stock / etc". But, any way, I have a deep concern on expanding concepts and knowledge, and I thing that root process, root means and rooted phone securing checklist are not as clear as I would like to find them. And more important: I *have* to remain in a custom rom but I *must not* be root.
So the why's are not the question but, just to add some reasonable context: I have a phone that does not fit my needs with the stock rom, because a hardware component is falling apart and I need a software workaround (YEAH, right LOL: a Nexus One with the power button falling apart and I need to be able to unlock / wake with the trackball; but this thread is Android-wide because it tries to find a deep insight into rooting itself). This software workaround does not work in stock rom when I configure the password / PIN / pattern. And the problem with custom roms is that they run into trouble with certain data-protection aware environments, which do not allow rooted terminals. And more important than all: I have no need at all to be root, at least by now.
So, I spent hours searching, and I figured out that I should remove "su" command and related APK's (ROM Manager, Superuser, ... and some others that I won't need). All by myself and with some posts (I don't remember if they were here or in "HTCMania", a good spanish smartphones board, either) that suggested it.
The exact process I did was to download CyanogenMod 7.2 RC1, check signature & md5 to make sure the zip was what it claimed to be (because later I found that I needed to shut down recovery signature check) open the .zip, remove "/system/xbin/su", install the rom, remove su-related ".apk" with adb, and try to check if it still had any sort of superuser permission scalation. It aparently does not have. I checked /data directory with Root Explorer, I downloaded and ran Root Checker Basic.
The results seem what I expected (and that's the question: they seem, and I don't know if they are): I am running on CyanogenMod, the workaround (wake on trackball) works, the PIN/password works fine with it, and it seems I am not able to gain root access.
But my question are deeper than that: is there any remaining technical mean that could be used to gain root access on my phone? Do I have to get rid of more su-companion tools to be sure and to be "non-root"-compliant? Is there any checklist we should follow to check both if our custom ROM is rooted-but-secure and if our ROM is properly un-rooted? And most important: did I miss / failed to find the correct resource in these forums?
Thanks to every body and congrats for this outrageous boards.
Anyone know how to root a Sharp SH-02E (ICS 4.0.4)? Even a temporary root is fine, I only want to install a particular apk in /system/app.
Many thanks.
I am looking for the Sharp Aquos Zeta root also, not for me but for my friend
I'll subscribe here and repost if I find something somewhere else.
Try this
http://forum.xda-developers.com/showthread.php?t=1886460
:thumbup:
DPK
Sent from my Android Smartphone
dkmali said:
Try this
http://forum.xda-developers.com/showthread.php?t=1886460
:thumbup:
DPK
Sent from my Android Smartphone
Click to expand...
Click to collapse
Tried and failed.
There's a discussion on a Japanese BBS that I think is onto something. Unfortunately there's a stupid rule here that means I can't post a link to it. The page title is '【ROM焼き】docomo AQUOS PHONE ZETA SH-02E root1' and it should be the top result on Google for 'sh-02e root'. The fun starts at post 75.
If we can just get ROOT and Custom Recovery on this device - it simply becomes the most powerful and advanced communicator in the world.. However no root - no life..
Two things:
Any luck with a custom recovery yet?
And can anyone dump the kernel and stock rom?
Happy to give it a crack...
Sent from my SPH-L900 using Tapatalk 2
Updating Aquos Phone
jaseli said:
Tried and failed.
Click to expand...
Click to collapse
Did you manage to get update 01.00.05 anyhow flashed outside Japan?
http://www.nttdocomo.co.jp/support/utilization/product_update/list/sh02e/index.html
jauhien said:
Did you manage to get update 01.00.05 anyhow flashed outside Japan?
http://www.nttdocomo.co.jp/support/utilization/product_update/list/sh02e/index.html
Click to expand...
Click to collapse
it is currently impossible to upgrade this phone out of Japan.
i am still on 01.00.03
I have a sh203 and I would like to root my phone also
>_<
Arrgh, this is so frustrating. You look on the 2ch thread and you can see they've done it. Temp root, MIYABI permanent root, they've done it all. The instructions aren't too hard to follow but I cannot for the life of me find the password (キーワード) required to download the files from axfc.net. If I had those files I could root the phone and post a guide here in English. For goodness sake it's staring me right there in the face and there's not a thing I can do about it. And of course because this is XDA, I can't even post you a link to the thread. It's the same thread title as earlier. You want to start from post 542 onwards, if you want a try yourself.
WithLoveFromExIA said:
Arrgh, this is so frustrating. You look on the 2ch thread and you can see they've done it. Temp root, MIYABI permanent root, they've done it all. The instructions aren't too hard to follow but I cannot for the life of me find the password (キーワード) required to download the files from axfc.net. If I had those files I could root the phone and post a guide here in English. For goodness sake it's staring me right there in the face and there's not a thing I can do about it. And of course because this is XDA, I can't even post you a link to the thread. It's the same thread title as earlier. You want to start from post 542 onwards, if you want a try yourself.
Click to expand...
Click to collapse
yes , please guide me how to root the phone permantly , thanks a lot !!
OK I've made some progress. I've got a temporary root, and am three hex numbers away from a full root. You'll need
The Sharp USB drivers, that are on Sharp's developer site.
ADB, as usual
The guide itself, which I can't like to. Post 672 on the 2ch thread.
The extra files, likewise. Post 680.
.
It's well written and pretty straightforward. Only minimal use of Google Translate will be necessary.
In the guide you'll find three lines of the form
Code:
./acdbwritevalue <address> <value>
where <address> and <value> are hexadecimal numbers.
The problem is that the guide is written for build number 01.00.05, the latest one. Unfortunetely I'm stuck on 01.00.03, so while the <value> numbers are the same, the <address> numbers are differrent, and I need to find the right ones. If you're on 01.00.05 feel free to go through the guide and share your results. Alternatively, if you know how to force the phone to update without being in Japan on Docomo, please share that too.
WithLoveFromExIA said:
OK I've made some progress. I've got a temporary root, and am three hex numbers away from a full root. You'll need
The Sharp USB drivers, that are on Sharp's developer site.
ADB, as usual
The guide itself, which I can't like to. Post 672 on the 2ch thread.
The extra files, likewise. Post 680.
.
It's well written and pretty straightforward. Only minimal use of Google Translate will be necessary.
In the guide you'll find three lines of the form
Code:
./acdbwritevalue <address> <value>
where <address> and <value> are hexadecimal numbers.
The problem is that the guide is written for build number 01.00.05, the latest one. Unfortunetely I'm stuck on 01.00.03, so while the <value> numbers are the same, the <address> numbers are differrent, and I need to find the right ones. If you're on 01.00.05 feel free to go through the guide and share your results. Alternatively, if you know how to force the phone to update without being in Japan on Docomo, please share that too.
Click to expand...
Click to collapse
Although I haven't got SH02E, I have found some extra files, which was mentioned in the Japanese guide for root, expect Busybox, enjoy.
The best phone of 2013 on the worse company in the world
Tommi_Vercetti said:
Although I haven't got SH02E, I have found some extra files, which was mentioned in the Japanese guide for root, expect Busybox, enjoy.
Click to expand...
Click to collapse
Thanks a lot. Luckily I came to Japan for Vacation and was able to find someone else to lend me a Usim card to update. DoCoMo are worse than Motorola, Apple and ATT when it comes to restricting your phone. Hell, I can't even use the native FM function without DoCoMo. How can Sharp expect to come out of the hole of bankruptcy when doing this sort of business? Look at the crappy Samsung company. Awful phones that everyone buys because they decided to be "untied" to companies at the beginning and for that reason they owned the market.
If Japan is really serious into getting its technological market back, better start uncopying the USA practice of enslaving their phones and tablets to telecomunication companies.
It's a shame that the best phone right now, the Sharp Aquos Zeta Sh-02e, with its awesome new screen and specs, is going to the trash as if it was a failure, just because they don't make deals with companies outside Japan.
16MPixel CAMERA!!! IGZO ultra clear screen!!! Quad Core!! 2gb Ram!! all the specs of all the other phones plus like 30 that none of them have!! A total shame, Sharp!
Find it carefully and you will find a good guy have written a script for temp root, I used the script to have my SH-02E rooted.
And, as far as I can read the topic, the unlock file is for NAND crack and may write to recovery area.
I don't test that coz of warranty, the reason I want to root is to put some message backup back(something like LINE) and remote control (VNC server for example)
And, yes, you can find the temp root solution for both 1.0.4 and 1.0.5, but no 1.0.3, good luck!
Do you have some files for rooting sh02e 1.00.04
rotalume said:
Find it carefully and you will find a good guy have written a script for temp root, I used the script to have my SH-02E rooted.
And, as far as I can read the topic, the unlock file is for NAND crack and may write to recovery area.
I don't test that coz of warranty, the reason I want to root is to put some message backup back(something like LINE) and remote control (VNC server for example)
And, yes, you can find the temp root solution for both 1.0.4 and 1.0.5, but no 1.0.3, good luck!
Click to expand...
Click to collapse
Do you have some files for rooting sh02e 1.00.04, I think many guys here are needing the solution
Hi rotalume
thanks for the note... can i ask a favor? i really need some help to install the SH-02E driver in windows.
tried to download the file from sharp's web, but after executing the install exe file, a bundle of unreadable signs come out, and i check my device manager, there is not SH-02E USB handler or SH-02E modem. I just want to make use of Helium (backup) to extract / restore apps and data...
thank you for your help in advance.
P.S. I guess to get the temp root script pushed to SH-02E, this driver is essential as well.
thanks again
jaseli said:
Hi rotalume
thanks for the note... can i ask a favor? i really need some help to install the SH-02E driver in windows.
tried to download the file from sharp's web, but after executing the install exe file, a bundle of unreadable signs come out, and i check my device manager, there is not SH-02E USB handler or SH-02E modem. I just want to make use of Helium (backup) to extract / restore apps and data...
thank you for your help in advance.
P.S. I guess to get the temp root script pushed to SH-02E, this driver is essential as well.
thanks again
Click to expand...
Click to collapse
The one you've installed is not ADB Driver, check ADB driver at developer site(I'm to young to post a link )
File name will be given as this form : usb_driver_SHARP_r6.10.zip
Download and extract, then install the driver by device manager.
And, I've used Carbon before but in vain coz of ADB driver(the author had told me), I don't know if this issue has been solved.
For the files, sorry guys, I've found someone at other forums has used them for commercial purpose(it's a shame that ppl of my country is included), so the best I can give is to tell you the clue.
You can post your question and I will do my best, but no file will be provided atm.
Downloaded Sharp Aquos Zeta ADB drivers for SH-02E
rotalume said:
File name will be given as this form : usb_driver_SHARP_r6.10.zip
Click to expand...
Click to collapse
I was able to find and download that driver by just selecting the name you wrote and making a search on Googl. It was the very first result. thanks a lot. Although I would love the name of the script or the title of the page you downloaded it from.
Thanks a lot.
I found a tutorial on exploiting the most recently released android vulnerability which affects the Google TV platform. This process uses a tool called Cydia Impactor by Saurik which allows execution of commands as the "system" user. On some devices this can easily be leveraged for root and on others there is not a known public privilege escalation available.
Saurik's Analysis of the Bug: http://www.saurik.com/id/17
Exploiting Key Signing Tutorial: http://gtvhacker.com/index.php/Exploiting_Key_Signing_for_Root
This bug is separate from anything we plan to release at DEF CON. If your device is not currently exploitable check back in a few weeks
This thread will be used to help users troubleshoot the exploit process, for updates needing to be made to the wiki in the tutorial, and for anything else relevant to this bug.
_
It's pretty dead there so I'm trying to get help here, until I get my issue solved, then maybe once I get my issue solved I'll be able to take what I've learned and help others to go through the same process if need be....
My Issue Is This
Does the root stick after a reboot?
I'm on a logitech revue, like mentioned before...
I think I got it connected but I get a error "more than one device" message, when I try to run any scripts.
What do I do to resolve this connection error, or whatever it is?
I realize this is a pretty new phone and since it is a lower end device it is probably not a priority for developers, but just wanted to ask.
Does anyone know if there is a way to root this phone?
I just can't find a way to root this phone LG K3, I'm trying to ADB sideload TWRP but I get the failed verification signature + no fastboot available..... Could someone explain please?
Just to update I have tried KingRoot, both the mobile and PC versions, and it did not work.
LG K3 Root
Any further developments with this? Has anyone tried TowelRoot or any of the other methods listed here: http://www.xda-developers.com/root/
Thanks in advance...
I have tried kingo and a few others and they all have failed pretty badly...
I have searched for TWRP but cannot find a version for the k3... its like it doesn't exist..
Anyone found any news?
wolfxwinds said:
I have tried kingo and a few others and they all have failed pretty badly...
I have searched for TWRP but cannot find a version for the k3... its like it doesn't exist..
Anyone found any news?
Click to expand...
Click to collapse
I haven't found anything to date. Google searches lead to dead ends, and there is nothing here or in the Android Central forums. I am encouraged by the fact that a few more people have expressed interest in rooting the K3. In my - admittedly brief - experience with rooting, it seems like the path forward is simply to hope that a tech-oriented person, developer or otherwise, will buy a K3 and take the time to fool around with it.
To anyone who has searched for a method to root the LG K3 and ended up here, please take the time to create a username and post on this forum. Perhaps if more people show interest, it will lead to something...
want root
unclevername said:
I haven't found anything to date. Google searches lead to dead ends, and there is nothing here or in the Android Central forums. I am encouraged by the fact that a few more people have expressed interest in rooting the K3. In my - admittedly brief - experience with rooting, it seems like the path forward is simply to hope that a tech-oriented person, developer or otherwise, will buy a K3 and take the time to fool around with it.
To anyone who has searched for a method to root the LG K3 and ended up here, please take the time to create a username and post on this forum. Perhaps if more people show interest, it will lead to something...
Click to expand...
Click to collapse
Really want root. There is too much bloatware on this device and I would love to get the integrate sd card as internal working. LG disabled it on all their devices sadly. If there is anyone out there who would be willing to help, we would be ever so grateful! Thanks!
I have a spare one with a shattered but working (Thanks to the skinomi on it!) screen I'd be willing to offer up for analysis. I'm trying to root for much the same reasons...bloatware being prime. More than half the internal memory is taken up by system apps and their updates! It wouldn't be so bad if all the amazon crap was moveable, but being system apps, are not...but who the hell puts trial ware on as a system app? It means that I can have only two or three user apps, even with most of their data moved to the sd card, before running into space issues when installing updates.
meowwl said:
I have a spare one with a shattered but working (Thanks to the skinomi on it!) screen I'd be willing to offer up for analysis. I'm trying to root for much the same reasons...bloatware being prime. More than half the internal memory is taken up by system apps and their updates! It wouldn't be so bad if all the amazon crap was moveable, but being system apps, are not...but who the hell puts trial ware on as a system app? It means that I can have only two or three user apps, even with most of their data moved to the sd card, before running into space issues when installing updates.
Click to expand...
Click to collapse
It's a pretty crappy phone as is...way too much boatware, not always responsive, and the battery runs out quickly. Needs root!
---------- Post added at 06:35 PM ---------- Previous post was at 06:28 PM ----------
There is another thread about the K3 here: http://forum.xda-developers.com/general/help/to-root-lg-k3-t3479758
Some of us are offering donations to anyone who can root it and post the instructions.
---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------
Nothing yet huh
tgkobaljr said:
Nothing yet huh
Click to expand...
Click to collapse
Look over here.
It's more active, at least.
Anything yet
How hard is it to find a root for this overly bloated phone? This cheapy phone can't be that hard for some techy to crack.
KingRoot, Z4Root, FramaRoot, TowelRoot omfg NONE of them work. I wasted my time. Please don't waste yours.
Adoptable Storage with LG K3 (K100)
ironsa said:
Really want root. There is too much bloatware on this device and I would love to get the integrate sd card as internal working. LG disabled it on all their devices sadly. If there is anyone out there who would be willing to help, we would be ever so grateful! Thanks!
Click to expand...
Click to collapse
There is a way to enable adoptable storage, I did it & now have my K3 working with an extra 32gb card mounted as adoptable. I found these instructions somewhere online but can't remember the link. Here they are though, thanks to whoever posted them. Note that you will get an error if you get the disk name wrong but I found mine after a couple of attempts (it's mentioned in the instructions below). This also worked for my K8 with a 64gb sd card.
Give it a go.
""""Notes: remember to use PTP rather than MTP option when connecting phone to laptop. If no device shown in ADB, use LG laptop software suite
When ADB is downloaded choose “Run as Administrator”.
Press Y to “install ADB and Fastboot”, Y all users and Y to install the necessary drivers.
Then allow it to install the Google device driver.
OPEN COMMAND PROMPT on your PC
Navigate to SDK Folder ((C:\adb )) and open Command Prompt
(Shift + Right-click anywhere in the folder > Open Command Prompt Here).
Type this command and hit enter.
-----------------------------------------------
adb devices
-----------------------------------------------
You should now see your device listed .
Type the following commands exactly as shown, pressing the ENTER key after each one:
----------------------------------------------------------------------------------------------------------
adb shell sm list-disks
adb shell sm list-volumes all
adb shell sm set-force-adoptable true
adb shell sm partition disk:179,64 private (Note: check the disk name, mine was 179,128)
adb shell sm set-force-adoptable false
adb shell sm list-volumes all
----------------------------------------------------------------------------------------------------------
NOTE: the fourth command partitions your SD card, and may take 2-3 minutes (or longer) to complete, depending on the size of your card. plus make sure you have a reliable and fast SD Card.
Disconnect your phone from the USB cable and reboot it. The reboot is crucial. Your phone may (or may not) take a bit longer to boot this time.
Once your phone is fully booted, tap Settings > Developer Options and disable USB Debugging, clicking “OK” to any messages that may appear.
Go to Settings > Storage & USB and tap your SD card. Tap the three dots in the upper-right corner and choose “Migrate data”:
Done""""
Rooting an lg
SODA8297 said:
I just can't find a way to root this phone LG K3, I'm trying to ADB sideload TWRP but I get the failed verification signature + no fastboot available..... Could someone explain please?
Click to expand...
Click to collapse
lg phones 4.0. And upwards has some malware virus blockers alot of these mods contain phish codes to steal your contacts or passwords also account details...
I got to 90% on my kingroot then it took 9 minutes to finish then after installing i got an error message ..
The only way to bypass the warning is to find a Root recovery program like Twrp so buy some more memory....download that then you can try ......im doing all of this to remove bloat and find deleted files in the 7 days before the system empties the trash