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 ive not done any guides before but since i had to search all over to try find out what i was looking for and stumbled across a lot of good information and thought id share it. None of this was my findings but there isn't anything clear on how to actually accomplish this on a Fire stick.
Im going to attempt to share how i have managed.
This guide assumes you already know how to transfer files to your stick.
First off, current Fire stick os is 5.2.1.0 and is rootable with Kingoroot.
https://root-apk.kingoapp.com
1. Download Kingoroot and ADB to your Fire stick, do this whichever way you normally get apk/files onto your Fire stick.
2. Download Kingoroot superuser and ADB to your Fire stick.
3. Run the Kingoroot tool and let it finish, when you have root, install Kingo roots Superuser. (If you install this before rooting it wont make any difference).
Now you should have a rooted Fire stick on 5.2.1.0 with Kingoroots SuperUser.
Now its time to downgrade your Fire stick. This file was provided by AFTVnews over at another thread and cuki3r3k83bln accomplished downgrade on the thread also so please leave thanks for them as before he posted the file and information i had no idea it was possible. Im suggesting to download the 5.0.5 file as i did because this was when firestarter worked with home button detection.
Download Fire Stick os 5.0.5
http://amzdigitaldownloads.edgesuit...te-kindle-montoya-54.5.3.7_user_537174420.bin
Once you have it downloaded rename the downloaded file to update.bin.
Im going to explain how i did it, i know there is many other variations on how to accomplish this and im not too familiar with adb commands but the way i will show is the way it worked for me.
We need to transfer the downloaded and renamed update.bin to the Fire stick so if you would like to transfer it with apps to fire or through command or any other variation thats fine but ill show commands used from windows laptop using adbLink.
Please note, if your using a different method to transfer you will have to slightly modify step 5 on where your update.bin is stored so cd /sdcard/download. if your update.bin is stored in download folder.
Another note is to make sure your file name is correct, mine was named update.bin.bin rather than update.bin this was fine just make sure to name it correctly or you will have to modify step 6 and step 8.
1. Open up adbLink and connect your device.
2. Push the update.bin to the sdcard. (this takes quite alot of time as your pushing 311mb file so be patient)
3. Once pushed you need to open up ADB Shell.
4. Run the command: su
5. Run the command: cd /sdcard
6. Run the command: mv ./update.bin /cache/
If you get an error about no space on device do the following:
Run the command rm -f /cache/*.bin
Run the command rm -f /cache/*.zip
Run the command exit
Run the command exit then reopen ADB Shell in adbLink repeat step 6.
7. Run the command cd /cache/recovery
8. Run the command echo --update_package=/cache/update.bin > command
9. Run the command reboot recovery
Your Fire stick should automatically start the downgrade and take 10 minutes or so.
As soon as its finished go back to your Kingoroot app and re-root your Fire stick. Then block updates (method 1) using AFTVnews guide at:
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
You should now be on 5.0.5 rooted and have updates blocked
All your apps should be still intact. Make sure you uninstall appstarter/firestopper and reinstall firestarter 3.2.3 (if you use it)
Then follow AFTVnews guide on how to re-enable it here:
http://www.aftvnews.com/how-to-cont...v-and-fire-tv-stick-software-version-5-0-5-1/
Please give the credit deserved to @AFTVnews.com and @cuki3r3k83bln
Its suggested all over to hold off before doing anything that could brick the device until rbox releases a recovery.
Please do not use any type of Su modifying tool/script/apk eg: SuperSume as these do not work and you will end up with a small brick.
Also its been pointed out to me by @deanr1977 that if your going to use this guide and decide to update Fire Stick os in the future, it maybe safer to unroot it first.
With that out of the way please excuse the bad layout of the guide as im no expert and would like to just share my experience.
Would I be able to go back to 5.2.1.0 once custom recovery and rom is released?
FireTho1 said:
Would I be able to go back to 5.2.1.0 once custom recovery and rom is released?
Click to expand...
Click to collapse
i cant see any reason why not, either grab the 5.2.1.0 .bin file and follow the guide using that or let it automatically update after re-enabling updates.
Are there any reasons for downgrading to 5.0.5? Does it have any advantages?
Bierfreund said:
Are there any reasons for downgrading to 5.0.5? Does it have any advantages?
Click to expand...
Click to collapse
As far as im aware upto now, it seems that Firestarter home button detection works as it should, and firmware after this Firestarter will not work with home button detection.
Which is a big thing for me personally as i only use Firestick for netflix and kodi and its much easier to launch from within Firestarter.
Its good to know that the process of upgrading/downgrading is applicable to Fire stick as you never know what Amazon will try to take from you.
You sir are my hero. Kudos for the tutorial!
sconnyuk said:
i cant see any reason why not, either grab the 5.2.1.0 .bin file and follow the guide using that or let it automatically update after re-enabling updates.
Click to expand...
Click to collapse
Its not recommended to let it auto update from root, unroot first then re-enable the update progress.
Also please can you note in your guide that its not recommended to try to swap the Su for Chainfires Su with the Super Sume or Super Sumepro app because so many people on this forum have bricked with this method & if any new users try your way & after want to unroot/swap method after the first boot they could have a non working device.
Ive not tried this guide myself (i dont need too) but if its working fine this info would be good to have here.
deanr1977 said:
Its not recommended to let it auto update from root, unroot first then re-enable the update progress.
Also please can you note in your guide that its not recommended to try to swap the Su for Chainfires Su with the Super Sume or Super Sumepro app because so many people on this forum have bricked with this method & if any new users try your way & after want to unroot/swap method after the first boot they could have a non working device.
Ive not tried this guide myself (i dont need too) but if its working fine this info would be good to have here.
Click to expand...
Click to collapse
Fair point about pointing out about the brickable and dangerous su swapping methods with supersu me etc.
I will add a mention about it after the line that reads:
'Its suggested all over to hold off before doing anything that could brick the device until rbox releases a recovery.'
As for not recommended to auto update while rooted, ive had 2 sticks and a Fire Tv 2 auto update from 5.0.5 to 5.0.5.1 and then to 5.2.1.0 when my router was reset, (im sure im not the only one from what ive read either).
But since im a helping type of guy ill add this also.
Ok mate, just going by what's been said from the AFTVNews & Amazon Firestick forums. Glad you are including this thanks, Its just some only skim through the threads & read only the parts they want to so if this is included it may cut down on the "I've bricked my Amazon device please help threads" which clog up the forum.
Sent from my SM-G900F using Tapatalk
i'm trying to downgrade to the point where display mirroring worked on windows devices, this is before 5.0.5, can i use this method to downgrade to another bin before 5.0.5?
sins07 said:
i'm trying to downgrade to the point where display mirroring worked on windows devices, this is before 5.0.5, can i use this method to downgrade to another bin before 5.0.5?
Click to expand...
Click to collapse
Id take a stab and say if your stick originally came with a firmware below 5.0.5 but I honestly do not know as ive not tried but I cant see why it wouldnt work. You can go from 5.2.1.0 to 5.0.5.1 or to 5.0.5 so id imagine so.
What features have been removed by 5.0.5? Im interested myself and may try this myself if there is features I could use.
Amazing! I can't believe this was hard to find as all the news out there say you can only root the stick using a hardware mod.
I downgraded and rooted both my Sticks. Installed Firestarter 3.2.3, installed Seeder, removed unneeded processes from running and these things are super quick now. You still have to load the crappy slow Amazon launcher to keep the settings but oh well. Nicely done, now I hope a recovery option comes out and I can mess around further . Heatsink and overclocking anyone? lol
@vulcan4d recovery & prerooted rom is being worked on at the moment by rbox in this forum
Sent from my SM-G900F using Tapatalk
vulcan4d said:
Amazing! I can't believe this was hard to find as all the news out there say you can only root the stick using a hardware mod.
I downgraded and rooted both my Sticks. Installed Firestarter 3.2.3, installed Seeder, removed unneeded processes from running and these things are super quick now. You still have to load the crappy slow Amazon launcher to keep the settings but oh well. Nicely done, now I hope a recovery option comes out and I can mess around further . Heatsink and overclocking anyone? lol
Click to expand...
Click to collapse
Can I ask what processes you removed/stopped and how you accomplished this?
Id like to do the same on 2 of my sticks.
sconnyuk said:
Can I ask what processes you removed/stopped and how you accomplished this?
Id like to do the same on 2 of my sticks.
Click to expand...
Click to collapse
I would like to give credit to this post for removing unneeded services:
http://forum.xda-developers.com/fire-tv/help/root-disabling-apps-services-bloat-t3325333
I only found a few from the list but that list was meant for a Fire TV so I'm sure there is more running. Just launch ADB Shell in ADBFire/Link and type pm disable <service_name>
vulcan4d said:
I would like to give credit to this post for removing unneeded services:
http://forum.xda-developers.com/fire-tv/help/root-disabling-apps-services-bloat-t3325333
I only found a few from the list but that list was meant for a Fire TV so I'm sure there is more running. Just launch ADB Shell in ADBFire/Link and type pm disable <service_name>
Click to expand...
Click to collapse
Thanks ive disabled them as per the guide you linked to. Can I further ask what the program seeder does and whether to have it set to aggressive or not?
Thanks for the info.
@sconnyuk i've downgraded successfully kingo root'ed stick 5.2.1->5.0.5 . But funny thing was under root shell command "wipe data " .It wiped device clean but root still stays on . Got OTA disabled and my other king root 5.0.5 stick will have similar treatment .
nicefile said:
@sconnyuk i've downgraded successfully kingo root'ed stick 5.2.1->5.0.5 . But funny thing was under root shell command "wipe data " .It wiped device clean but root still stays on . Got OTA disabled and my other king root 5.0.5 stick will have similar treatment .
Click to expand...
Click to collapse
You will need to unroot it for root to go.
Kingoroot has the option to do this if its what you want.
You need mouse toggle for fire tv to navigate to the 'in app' menu icon if not plug fire stick into pc and run Windows version of Kingoroot to unroot.
Interesting, I just bought a 3rd Amazon stick to root. After running KingRoot, I've noticed I did not need to install KingUser at all. If you launch KingRoot again it allows you to launch KingoUser which is the same thing. I'm assuming that KingUser is just an updated version of what KingRoot already installs.
Sconnyuk, I checked all the boxes and chose Moderate. This was also mentioned in the XDA forums however sadly I cannot find the post anymore. Seeder is an application that has been around for a while which improves the response time on Android devices. There is a lot of technical details into how it works, but the point is the Amazon stick is not the fastest thing in the world and anything helps. Give it a try and see for yourself.
sconnyuk said:
Id take a stab and say if your stick originally came with a firmware below 5.0.5 but I honestly do not know as ive not tried but I cant see why it wouldnt work. You can go from 5.2.1.0 to 5.0.5.1 or to 5.0.5 so id imagine so.
What features have been removed by 5.0.5? Im interested myself and may try this myself if there is features I could use.
Click to expand...
Click to collapse
Miracast display mirroring became non-compliant with windows systems, it still works fine with android.
I'm trying to root SGP412 (sim-free Z Ultra sold in Japan).
The stock firmware (build number 14.3.A.2.21) prevents the rooting via Easy Root Tool, and kingroot does not work either.
Right now there are two options that I can think of:
A. Roll back the firmware to one old enough for the root tool to work, root the tablet, and update the firmware back to the latest one.
B. Find the absolute kernel addresses and use 'iovyroot' to root (this should be able to root the device with the current firmware).
Option B seems a bit daunting, so I've been looking into option A; I got an ftf of an old firmware (14.1.B.3.357)
I downloaded the Flashtool, but following errors occur when I try to run the FlashTool.exe/FlashTool64.exe (tried both).
java.lang.ClassNotFoundException: gui.Main
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
at com.exe4j.runtime.WinLauncher.main(Unknown Source)
EXE4J_JAVA_HOME is set to the root directory of the latest JRE (tried JDK also). I tried the same thing on two different computers (both running Windows 10 Pro 64-bit), but get the same errors.
Update
I loaded the project on eclipse and then it created a 'bin' folder and .class files were generated inside the folder. The 'bin' folder has the subdirectory 'gui' inside and the file 'Main.class' in it, but I'm still getting the same error: java.lang.ClassNotFoundException: gui.Main...
I added the CLASSPATH environment variable and set the value to the directory path of the Flashtool's bin folder, but it didn't change anything.
Has anyone seen anything similar to this in trying to use Flashtool?
My sincere apologies for reviving a necropost. But I suddenly find myself in the same situation. I'd like to root my Xperia Ultra, SGP412 running Android 4.4.2 with a firmware version of 14.3.A.2.21.
I have a very specific usage scenario for it. I want to control an Onyx Boox Max Carta from it, running a VNC streamer on the Xperia and a VNC viewer on the OBMC. The OBMC runs Android 4.0.4 so there are very few clients available for it. RemoteDroid on the Xperia should solve it but it requires a rooted device.
Since this Japanese version of it is a tablet, rather than a phone (the SIM card slot is soldered) there is no phone app and hence I can't do the *#*#number thing on it.
If anyone was able to solve the OP's question, kindly inform in this thread.
Kumabjorn said:
My sincere apologies for reviving a necropost. But I suddenly find myself in the same situation. I'd like to root my Xperia Ultra, SGP412 running Android 4.4.2 with a firmware version of 14.3.A.2.21.
I have a very specific usage scenario for it. I want to control an Onyx Boox Max Carta from it, running a VNC streamer on the Xperia and a VNC viewer on the OBMC. The OBMC runs Android 4.0.4 so there are very few clients available for it. RemoteDroid on the Xperia should solve it but it requires a rooted device.
Since this Japanese version of it is a tablet, rather than a phone (the SIM card slot is soldered) there is no phone app and hence I can't do the *#*#number thing on it.
If anyone was able to solve the OP's question, kindly inform in this thread.
Click to expand...
Click to collapse
mm I have not had much luck with vnc servers on android.
My phone force closes remotedroid..got the server working by lowering the resolution in settings but I get no data to my client.
Tried on another device and the app crashes as soon as I start the server. And it said my devie is rooted in the toast..its not.
And it give me a black screen when I connect as a client...oh..jesus. It says in the app "4. The serve app will ONLY work on a rooted KitKat device and the app must be installed in /system." ..not reading the instructions works really good.
Hang on..I found a vnc server that works! For lollipop.
http://www.apkmonk.com/app/com.pranayc.remotevncserver/
huh..this is the very first time I have got vnc working on android!
I get image but no controls..You can try RemoteDroid and report if it works in case you succeed to root your phone.
You can go the long way and compile a vnc server from source code and run it from terminal but its not the practical way when you can run teamviewer instead..
So next problem:
Its not possible to install the dialer apk?
https://www.apkmirror.com/apk/google-inc/google-dialer/
Its a long shot. But you can try..if it will even install.
There is this guide. But I cant make this work on marshmallow.
I don't have any devices running stock lollipop or older to test the old contacts app with.
http://www.xperiablog.net/2013/06/20/xperia-tablet-z-how-to-access-the-service-menu/
Long pressing in the contacts app does nothing in marshmallow.
I found this thread: https://forum.xda-developers.com/showthread.php?t=2289383
adb shell "am start -a android.intent.action.MAIN -n com.sonyericsson.android.servicemenu/.ServiceMainMenu"
But I get the following: (again running marshmallow)
Code:
Starting: Intent { act=android.intent.action.MAIN cmp=com.sonyericsson.android.s
ervicemenu/.ServiceMainMenu }
Error type 3
Error: Activity class {com.sonyericsson.android.servicemenu/com.sonyericsson.and
roid.servicemenu.ServiceMainMenu} does not exist.
The issue OP was running into with flashtool won't affect you unless you're running the same Windows 10 pro version whatever build op was on and the same flashtool. I recommend running a separate windows 7 machine physical or virtual machine for messing with drivers and this stuff.
Quoting the op post
A. Roll back the firmware to one old enough for the root tool to work, root the tablet, and update the firmware back to the latest one.
B. Find the absolute kernel addresses and use 'iovyroot' to root (this should be able to root the device with the current firmware).
Neither of these are going to work. B...if you have freetime to spend go ahead but its eh. Go out and have fun this summer instead of staring on a hex editor.
Today ..I mean today in july 2017 we have some issues.
That is that its almost impossible to obtain older stock roms.
Xperiafirm removed all but the latest. Filehosts posted here has removed the file due to inactivity.
I found two stock roms for SGP412 to download in case you need it. I can't find it in flashtool.
Dunno if sol24 is the same device or if sol24 and SGP412 are two different models?
https://www.androidfilehost.com/?fid=24566382913913003
https://www.androidfilehost.com/?fid=24562946973630839
But get back to the dialer. My guess to why you want to access the service menu might be to check if bootloader unlocked allow will be yes or no?
And it being impossible to root the device perhaps this is what you want to do? And then root the phone with the bootloader unlocked?
I don't know the mechanisms applied by sony to stop it to being able to root. But hopefully it might be possible to overcome with unlocked bootloader.
...and not WearOS because this is from an Android 5.1.1 build from 2015
I talked about the Wear framework in this thread, and how it can be partially installed onto the Pace and Stratos
THIS DOES NOT MEAN A FULLY WORKING ANDROID WEAR BUILD!
It doesn't connect to the Wear app, even after installing all the APKs required and following the correct setup procedure (some bluetooth error, even after patching it with the supposed workaround for normal apps, it doesn't work - maybe the Bluetooth stack on these watches doesn't work for Wear)
What it does allow is for standalone wear apps with really simple functions to work. Good examples of this are Wear Bottle Spinner (eliseo.wearbottlespinner.wear) and Interval timer for Android Wear (wearablesoftware.wearintervaltimer), which on this list are "not working" due to lack of wear framework, but work after these files have been copied.
Please do not attempt this if you want a fully stable device, or don't feel comfortable debugging. It may not work for you, and you may end up having to post crash logs or have a not-working device. This is a development thread, it's not fully ready for use yet
Installation
- Download this zip
- Extract it and run the following commands from the folder
Code:
adb root
adb remount
adb push com.google.android.wearable.jar /system/framework
adb push clockwork-system.jar /system/framework
adb push com.google.android.wearable.xml /system/etc/permissions
adb push clockwork-system.xml /system/etc/permissions
adb push ClockworkAmbient.apk /system/priv-app/ClockworkAmbient/ClockworkAmbient.apk
adb reboot
I think this is all that's needed for it to work. My test device has more Wear framework APKs on it than are needed, so I'm not totally sure. If it crashes after doing this, please post a logcat and I'll see if anything else is needed - that's why this is a DEV thread!
These files were taken from the last Android 5.1.1 Wear build for the Gear 2 (itself a port): https://forum.xda-developers.com/gear-2/development/please-help-kernel-compiling-android-t2992953
From having followed the AW porting thread for the Samsung Gear S back in the days I can say the following things:
The Bluetooth stack is indeed different between normal Android and Android Wear but IIRC it should be at least theoretically possible to make it work unless Xiaomi/Huami modified it.
To connect to the AW app it will also require to have all the AW GAPPS properly setup AND the fingerprint of a watch it will recognize with said AW version, even an AW port just won't connect with the app unless there is a proper fingerprint setup in build.prop
On another note great job on doing this and I will be testing it out later today when I will have some free time and an easy way of getting said AW apps.
Hello Quinny, I think you're doing a great job, and it's appreciated. What is the scope of this? I am clear that we will not see Android Wear on our devices, but can Google services and applications be installed? Or would it only be used to install certain applications?
Thanks for your contributions.
zodrac said:
Hello Quinny, I think you're doing a great job, and it's appreciated. What is the scope of this? I am clear that we will not see Android Wear on our devices, but can Google services and applications be installed? Or would it only be used to install certain applications?
Thanks for your contributions.
Click to expand...
Click to collapse
It's to make apps that rely on the Wear framework classes work, but only those that are standalone
Ranomez said:
From having followed the AW porting thread for the Samsung Gear S back in the days I can say the following things:
The Bluetooth stack is indeed different between normal Android and Android Wear but IIRC it should be at least theoretically possible to make it work unless Xiaomi/Huami modified it.
To connect to the AW app it will also require to have all the AW GAPPS properly setup AND the fingerprint of a watch it will recognize with said AW version, even an AW port just won't connect with the app unless there is a proper fingerprint setup in build.prop
On another note great job on doing this and I will be testing it out later today when I will have some free time and an easy way of getting said AW apps.
Click to expand...
Click to collapse
@Quinny899 what do you think, would it be possible?
Hi, will this work with this?
https://play.google.com/store/apps/details?id=prox.lab.calclock&hl=cs
urbami said:
Hi, will this work with this?
https://play.google.com/store/apps/details?id=prox.lab.calclock&hl=cs
Click to expand...
Click to collapse
No
Hello there! I think you are doing a fanstastic job! But I have a problem, I can't do adb remount... It says permission denied. Any help is appreciated
Qufy said:
Hello there! I think you are doing a fanstastic job! But I have a problem, I can't do adb remount... It says permission denied. Any help is appreciated
Click to expand...
Click to collapse
You need to be running a rooted boot image and have successfully run "adb root" before remount.
Quinny899 said:
You need to be running a rooted boot image and have successfully run "adb root" before remount.
Click to expand...
Click to collapse
adb root runs successfully. As for the rooted boot image... Does it mean I need a custom recovery image? (Like TWRP?)
Qufy said:
adb root runs successfully. As for the rooted boot image... Does it mean I need a custom recovery image? (Like TWRP?)
Click to expand...
Click to collapse
What does adb root return? Can you send a screenshot?
Quinny899 said:
What does adb root return? Can you send a screenshot?
Click to expand...
Click to collapse
It returns nothing so I am not sure :/
https://imgur.com/TUeo3ky
Qufy said:
adb root runs successfully. As for the rooted boot image... Does it mean I need a custom recovery image? (Like TWRP?)
Click to expand...
Click to collapse
You have to boot (not flash) an boot image with root support and run the commands directly then.
Do a search for root Amazfit, there are some guides.
GreatApo said:
You have to boot (not flash) an boot image with root support and run the commands directly then.
Do a search for root Amazfit, there are some guides.
Click to expand...
Click to collapse
I will try that thanks
Qufy said:
It returns nothing so I am not sure :/
https://imgur.com/TUeo3ky
Click to expand...
Click to collapse
Nothing = it didn't work.
If it works it says "adbd restarting as root"
Quinny899 said:
Nothing = it didn't work.
If it works it says "adbd restarting as root"
Click to expand...
Click to collapse
Oh ok thanks
Quinny899 said:
...and not WearOS because this is from an Android 5.1.1 build from 2015
I talked about the Wear framework in this thread, and how it can be partially installed onto the Pace and Stratos
THIS DOES NOT MEAN A FULLY WORKING ANDROID WEAR BUILD!
It doesn't connect to the Wear app, even after installing all the APKs required and following the correct setup procedure (some bluetooth error, even after patching it with the supposed workaround for normal apps, it doesn't work - maybe the Bluetooth stack on these watches doesn't work for Wear)
What it does allow is for standalone wear apps with really simple functions to work. Good examples of this are Wear Bottle Spinner (eliseo.wearbottlespinner.wear) and Interval timer for Android Wear (wearablesoftware.wearintervaltimer), which on this list are "not working" due to lack of wear framework, but work after these files have been copied.
Please do not attempt this if you want a fully stable device, or don't feel comfortable debugging. It may not work for you, and you may end up having to post crash logs or have a not-working device. This is a development thread, it's not fully ready for use yet
Installation
- Download this zip
- Extract it and run the following commands from the folder
Code:
adb root
adb remount
adb push com.google.android.wearable.jar /system/framework
adb push clockwork-system.jar /system/framework
adb push com.google.android.wearable.xml /system/etc/permissions
adb push clockwork-system.xml /system/etc/permissions
adb push ClockworkAmbient.apk /system/priv-app/ClockworkAmbient/ClockworkAmbient.apk
adb reboot
I think this is all that's needed for it to work. My test device has more Wear framework APKs on it than are needed, so I'm not totally sure. If it crashes after doing this, please post a logcat and I'll see if anything else is needed - that's why this is a DEV thread!
These files were taken from the last Android 5.1.1 Wear build for the Gear 2 (itself a port): https://forum.xda-developers.com/gear-2/development/please-help-kernel-compiling-android-t2992953
Click to expand...
Click to collapse
Can it delete my ROM(PACEfied)?
Hi is it possible to run google fit directly from watch?
With framewotk or any custom build google fit apk? Anyone test it?
Will the application like a "com.huami.watch.deskclock" and another stock application still works ?
A M A Z F I T S T R A T O S
lensSGzaza said:
Will the application like a "com.huami.watch.deskclock" and another stock application still works ?
A M A Z F I T S T R A T O S
Click to expand...
Click to collapse
Yes.
Hi All !
Some of us do know the application a long time but others don't. Therefore this small GUIDE.
Removing system apps without root/unlocked can be done in a few ways like :
manually : with an ADB list and described HERE huge thnx @SirTAVARES
automatic : if you don't like to do it manually, you can use the ADB/Fastboot Tool which will do the job for you.
The XiaomiADBFastbootTools isn't explained in depth afaik and can do a lot more but I'll focus on the removal of those system apps.
HOW TO :
NOTE : do try some apps (not all at once) and see if the phone boots again - if you would have a problem you can always restore the onces you removed or perform a factory reset to restore all apps (as they are not really gone )
0. enable developer options to enable USB debugging ( go to settings/about phone/tap MIUI version 7 times to enable dev. options -> then go to settings/additional settings/ dev. options/enable USB debugging )
1. download the latest version HERE
2. run the .jar application
3. you'll get this screen
As you can see, the tool will start by default in ADB. You'll see a bunch of apps you could de-install under the Uninstaller tab.
If you're sure which apps you want to de-install just check the ones you want and tab UNINSTALL
google where is the nearest gas station
TIP : try one first like Google Chrome f.e. and see if it works
EXAMPLE : Removal of Google Chrome :
Once removed you can check if the app is gone of your home screen apps or under settings/installed apps/tap the 3-dot sign to show all apps/ search for ''chrome'' and the app should be removed.
4. if you want the removed app(s) back, just tap the Reinstaller and check the ones you want to re-install. Easy right !
Once re-installed your Chrome app will appear again on your home screen/app list
5. TIP : before removing, check the app name under settings/installed apps/show all apps/tap on an app and tap the Ⓘ to get the app info
Other functions :
1. As you probably noticed besides running in ADB, this tool can easily boot into Fastboot, Recovery, System or EDL.
When booting into Fastboot you can see some other functions you can apply. Be aware of the risks applying things under fastboot !
2. Very useful option is the possibility to push, pull ,... apps/folders with FILE EXPLORER. Just tap OPEN and you can easily perform some actions afterwards.
(ignore the KB sizes - once pulled you'll get the right folder/apks )
E N J O Y
Nice tuto....will debloat for sure...
SirTAVARES said:
use this list: https://drive.google.com/open?id=1TbofebVTy5U1FDMQEAfv6O1CsxTblpO7
includes some adaway hosts to block Xiaomi Stuff
Click to expand...
Click to collapse
Dear SirTAVARES, Can you tell me, is adaway worked with Global stable NON Root ? How to push it inside system files ??
N.ice tool, but I have a doubt... How I remove the Security Center?
PS. I have a Mi 9, with locked bootloader and now I'm beta 9.6.27
Thank you very much for sharing, i will test for changing system font
Sorry for that stupid question, but I don't get the tool running
Prinz069 said:
Sorry for that stupid question, but I don't get the tool running
Click to expand...
Click to collapse
You must have the JRE environment installed and pointing to the correct path.
omgomg said:
You must have the JRE environment installed and pointing to the correct path.
Click to expand...
Click to collapse
What is "JRE Environment" please? Why same not included in the OP instructions?
All help appreciated!
belerephont said:
What is "JRE Environment" please? Why same not included in the OP instructions?
All help appreciated!
Click to expand...
Click to collapse
This is what you have to install to be able to run .jar files. OP just assumed everyone has java installed (I would too to be honest) and didn't mention it.
I have installed the updated java and am trying to open the windows 10 boot tool and it refuses to open. Yes I did upzip it but the program will not open. Any help please?
gardenwarlord said:
I have installed the updated java and am trying to open the windows 10 boot tool and it refuses to open. Yes I did upzip it but the program will not open. Any help please?
Click to expand...
Click to collapse
What version you installed? I recommend that you install 6.5.1:
https://github.com/Saki-EU/XiaomiADBFastbootTools/releases/tag/6.5.1
That is what I downloaded...Win version. I unzipped and then tried to open but it does not work.
gardenwarlord said:
That is what I downloaded...Win version. I unzipped and then tried to open but it does not work.
Click to expand...
Click to collapse
You don't need unzipped. Download the version .JAR an run it. I made this way
Evidently I have absolutely no idea what I am doing. Nothing opens
gardenwarlord said:
Evidently I have absolutely no idea what I am doing. Nothing opens
Click to expand...
Click to collapse
Lets go from begining:
- First thing that I did, I uninstalled all versions of Java;
- Second, (I made this way, you can jump this step) - reboot my laptop;
- Third, I installed the latest version (in this moment is version 8, update 221) - I installed both 32 bits (x86) and 64 bits (x64);
- Fourth, run the tool (just download .JAR version) and clicked with right botton for open with Java.
When I right click nothing asks to open it in java
If you have java installed, then just a double click on the XiaomiADBFastbootTools-6.5.1.jar is enough.
Opens in 7z
gardenwarlord said:
Opens in 7z
Click to expand...
Click to collapse
Probably you made 7zip as default app. Right botton, "open with...", choose Java
Hello! Tried different versions ... NOT FOUND Redmi 4X MIUI 10 Global 9.6.27 Android 7.1.2 N2G47H