[Q] Help, Accidentally damage the "Fonts" folder, My Phone wont start - XPERIA X8 Q&A, Help & Troubleshooting

The situation is like this,
first am new to the android world and i was reckless i know, but some help would be nice
Case:
-Device: Xperia X8
-Rom: Stock 2.1
-USB Debugging Enabled
-Root (SuperOneClick)
-BusyBox v1.18.4
-Bootloader locked ( default state didn't touch it so its locked i guess)
-No Recovery of any kind
-** Very Important to keep the files, so please no solutions includes wiping the internal memory
What happen:
i was using "Font installer" app to change fonts and accidentally replaced "ALL" the font files in "System/Fonts" and that led the device not to boot now stuck on "Sony Ericsson" black screen
So:
- I think i need a copy of the original "System/Fonts" of any Xperia X8, if you guys can upload?
- and i need to know how can i access the phone internal memory so i can replace the content of "System/Fonts" with the new files
Thanks In Advance

Restore via pcc
Sent from my E15i using xda app-developers app

ElmirBuljubasic said:
Restore via pcc
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
As i said "-** Very Important to keep the files, so please no solutions includes wiping the internal memory"

medomoo said:
As i said "-** Very Important to keep the files, so please no solutions includes wiping the internal memory"
Click to expand...
Click to collapse
Then I guess you are outta luck.. You have to re-flash your ROM. That'll delete data from internal memory. Data on SD Card will be safe..

May be you can use adb to push folder or files you want to its location. It will save your precious data.
Sent from my R800i using xda premium

creative_md said:
May be you can use adb to push folder or files you want to its location. It will save your precious data.
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Thank you i will try that, but still i need the original "Fonts Folder", can any one please upload ?

Try to download any ftf file extract it then copy fonts folder from there
Sent from my R800i using xda premium

creative_md said:
Try to download any ftf file extract it then copy fonts folder from there
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Thanks, got the fonts folder still working on how to push it

tried adb, but i cant get root
After adb shell i get $ when i type su i get "[1] segment fault su"
i tried and i searched every where with no luck !! any help please
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

!!!!! Any Help !!!!!

1. Hope u have enabled usb debugging !
2. Go to recovery (if u have it,if not you are in the trouble)
3. Go to mount/storage
4. Mount system,data
5. Download Android Commander or QtADB !
6. Connect usb cable to pc and x8
7. Open Android Commander and QtADB
8 If phone is sucessfuly connected,u can copy Fonts folder from working rom and replace it with damaged fonts folder.
9. Reboot
10. Enjoy!:laugh:

2010matej said:
1. Hope u have enabled usb debugging !
2. Go to recovery (if u have it,if not you are in the trouble)
3. Go to mount/storage
4. Mount system,data
5. Download Android Commander or QtADB !
6. Connect usb cable to pc and x8
7. Open Android Commander and QtADB
8 If phone is sucessfuly connected,u can copy Fonts folder from working rom and replace it with damaged fonts folder.
9. Reboot
10. Enjoy!:laugh:
Click to expand...
Click to collapse
Reading would have saved you some precious minutes that you now will never get back:
medomoo said:
Case:
-Device: Xperia X8
-Rom: Stock 2.1
-USB Debugging Enabled
-Root (SuperOneClick)
-BusyBox v1.18.4
-Bootloader locked ( default state didn't touch it so its locked i guess)
-No Recovery of any kind
Click to expand...
Click to collapse
@medomoo - There might be a way to access the internal memory with specialized equipment, but don't quote me on that one. Go to a phone repair shop or try talking directly to Sony.
The only thing you can do by yourself now is close your eyes and lose the information. You screwed things up really badly with no backup and no recovery. Learn, let it go and move on.

Fortun said:
@medomoo - There might be a way to access the internal memory with specialized equipment, but don't quote me on that one. Go to a phone repair shop or try talking directly to Sony.
The only thing you can do by yourself now is close your eyes and lose the information. You screwed things up really badly with no backup and no recovery. Learn, let it go and move on.
Click to expand...
Click to collapse
Thank you, But why i cant get root access in ADB

Let's put it another way. When your PC freezes, is there anything you can do to manipulate the files? No. Let's take one step further: when you get the blue screen of death while starting the system, is there anything you can do to anything inside your harddrive? No.
It's the same with your phone. Your phone is freezed even before mounting all of the partitions fully and correctly. So, ADB will do nothing. In short, in this regard, there's nothing you can do.
So, take your phone directly to Sony or to a phone repair shop. Or just lose the information.

OK lets say am going to flash a new ROM,
BTW just to take a lesson from that:- what is the safety steps i should take to prevent situation like this from happening again etc what kind of recovery and what else than recovery i can do ??

Backup all apps through titanium backup. And always make nandroid backup through recovery. Its advantage is that if you messed with your phone(like in this case) you can recover backup and you get your old phone back (with data of any kind).
Sent from my R800i using xda premium

Thank god, its working now and didn't have to flash new ROM and all my files are save,
1- Got "Shell Root" with SuperOneClick v2.3.3
2- Used "Android Commander" to push the Original Fonts to its place. and done.
Thanks everyone

Related

[RECOVERY] 4/Apr: 3.0.1.4 r1 - ClockworkMod Recovery for the LG Optimus 2X

DO NOT RUN THIS ON THE G2X! The partition layout is different, doing so will do bad things to your device. I will release a G2X compatible version when I am back online in a week's time!
For the past couple of days I have been working on creating a ClockworkMod recovery image for the LG Optimus 2X. I'm pleased to announce that the first full release is available!
Some points to note - READ THESE CAREFULLY!
Use at your own risk! I have successfully used the backup and restore functionality (nandroid), and am currently testing other functions.
If you manage to break your device completely, this ROM should get you back up and running.
Download
I have packaged the recovery itself and the installation system together in one download zip.
3.0.1.4 r1 DOWNLOAD (ROMraid Load Balancing) - MD5: 7145b425f95a87dc5bde29ac4eba48ff
Installation automatically on your device
NEW: If your device is rooted, my 99p 2X Recovery Boot app (mentioned below) can now flash the recovery image for you the first time you run the app and on subsequent version updates!
Installation on Windows, Linux and OSX
- Download the zip file above and extract to a directory
- Connect your device and ensure 'USB debugging' is enabled
- WINDOWS - double click 'install-clockworkmod-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-clockworkmod-mac.sh' followed by './install-clockworkmod-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-clockworkmod-linux.sh' followed by './install-clockworkmod-linux.sh'
If you wish, you can also manually install the recovery by pushing the clockworkmod.img file to /data/local/ with adb and running 'dd if=/data/local/clockworkmod.img of=/dev/block/mmcblk0p7' from a root shell.
Launching Recovery
To boot ClockworkMod Recovery, either:
Turn the device on while holding the volume down and power buttons until recovery loads
Download the OPTIONAL 99p 'LG 2X Recovery Boot' application from the Android Market (NOTE: This app is completely optional - if you do use it, thanks for your support!)
Source / Updates
I'll be posting the device profile and source changes on my GitHub shortly, and will issue fixes / new Betas as required.
Enjoy!
P
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks Paul !
You are the best. I am wating for the crowd to test this so I can use it for my mission critical work phone but the future seems bright.
Hi Paul... first of all - Great job here
Second - if one can't get root access via SuperOneClick, like myself, is this still usable?
Inebriatef said:
Hi Paul... first of all - Great job here
Second - if one can't get root access via SuperOneClick, like myself, is this still usable?
Click to expand...
Click to collapse
Root access is not a pre-requisite.
P
mirror (if it's ok with you Paul)
http://www.mediafire.com/?udkabus35wlr2w3
Great job paul
THANKS! Installing now
Update:
If you get error in windows just change adb-windows.exe to adb.exe
First, thank you very much, Paul. Great job!
Two questions.
1) This method overwrites the standard recovery on the phone, correct?
2) To revert back to standard recovery, one have to flash the whole phone using nvflash, correct?
ULJ said:
First, thank you very much, Paul. Great job!
Two questions.
1) This method overwrites the standard recovery on the phone, correct?
2) To revert back to standard recovery, one have to flash the whole phone using nvflash, correct?
Click to expand...
Click to collapse
1) Yes
2) No, you could just dd the stock recovery.img from the NVFlash archive.
P
<- This is me "patiently" waiting for CyanogenMod and Paul's online kitchen for the 2x
GREAT work as always, Paul!
paulobrien said:
1) Yes
2) No, you could just dd the stock recovery.img from the NVFlash archive.
P
Click to expand...
Click to collapse
Okay. Thanks.
Im just curious, who supplies the NVFlash archive? And is the standard recovery image supplied by Nvidia or LG? Since it is part of the NVFlash archive.
Found out why i can get no root access... i got no adb access at all.
First time pluggin in phone after install of LG drivers, it says that the adb interface thingy can't install.
This also causes that i can't install CWM.
Any suggestions as to what is wrong?
Thank you, Paul!
Successful nandroid backup I will try to make a custom rom.
Paul its was a good idea to let clockworkmod make backup to external sd because its not possible to mount usb storage in recovery menu yet.
Inebriatef said:
Found out why i can get no root access... i got no adb access at all.
First time pluggin in phone after install of LG drivers, it says that the adb interface thingy can't install.
This also causes that i can't install CWM.
Any suggestions as to what is wrong?
Click to expand...
Click to collapse
I hade the same problems. Download the LG drivers from this site, worked for me.
www {dot} junefabrics.com/android/driver.php
(could not post links, so replace {dot} with a .)
Inebriatef said:
Hi Paul... first of all - Great job here
Second - if one can't get root access via SuperOneClick, like myself, is this still usable?
Click to expand...
Click to collapse
Tried Z4root?
Nilssonnet said:
I hade the same problems. Download the LG drivers from this site, worked for me.
www {dot} junefabrics.com/android/driver.php
(could not post links, so replace {dot} with a .)
Click to expand...
Click to collapse
thx, it works now
yipeee! now i can expect a real custom rom
Ok first backup done! Works perfect! Thanks for all the effort!
Korumera said:
Ok first backup done! Works perfect! Thanks for all the effort!
Click to expand...
Click to collapse
Same here. Thank you very much, Paul!

[GUIDE] How to easily re-partition your phone to increase your Data Storage

I don't think anyone has posted a tutorial for this on XDA yet (apologies if they have!!!) and the Google Translate of Mur4ik's original instructions on 4PDA is pretty poor so here's what I did to get my phone set up.
What does this do?
This process flashes a modified KDZ which will change the way your phone's memory is partitioned. The result will be that you have 234mb of internal storage for your apps, 150mb for the system and 64mb for cache.
According to Mur4ik, this is the optimum allocation of memory for best performance.
Once this process has been done, any ROM that you flash will have more internal storage space without any further modification. You should not flash a data2system rom.
With this method you will still be able to apply update.zip files with recovery (like Mur4ik's rom updates). This feature does not work on data2system roms.
Things you'll need:
1) KDZ Updater
2) Mur4ik's modified KDZ (MD5SUM: e582d471ed9aede3dd9279b20f7a948c)
Assumptions:
1) You know how to back up your ROM
2) You have access to a Windows PC with drivers installed for your phone
First of all you should back up your current ROM with recovery.
OK, let's get started:
Turn the phone off, remove the battery, SIM & SD Card.
While holding Volume-Down, connect the phone to your PC and run KDZ Updater. The phone display will show "Download Mode".
Select "CS_Emergency" Phonemode in KDZ Updater and select the "20E 234 150 64.kdz" KDZ file downloaded above. Then click "Launch software update"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The update will now start. During the update the phone screen will display "Download Mode" and eventually an animation of the battery cover being replaced. At this point you can disconnect the phone and replace your SIM, SD Card and battery *
Put your phone into fastboot mode (hold Camera and press Power) - the fastboot screen will now be BLUE and have white text displayed on it (this is correct).
Connect to your PC and in a terminal type:
Code:
fastboot erase system
fastboot erase userdata
fastboot erase cache
flash recovery back on to your phone
Code:
fastboot flash recovery recovery.img
Boot your phone into fastboot or recovery
Your phone is now ready to go and you can either restore a backup with recovery or flash a ROM with fastboot. You must be sure that your backup or fastboot images do not exceed the sizes stated above. So, your system.img must not be larger than 150mb, your data.img must not be larger than 234mb and your cache.img no larger than 64mb.
Note: If you were already using a data2system rom and want to restore your backup after carrying out this process then you must do the following in the backup's folder on your sdcard:
- replace your boot.img with one from a standard version of your rom (i.e. non-data2system)
- rename your "data.img" to "system.img" and your "system.img" to "data.img"
- delete the file "nandroid.md5"
- open an adb shell (or run terminal on your phone) and type "su" <enter>, "cd" to the backup folder, type "md5sum *.img > nandroid.md5" <enter>
- you can then restore the backup with recovery.
How to restore your phone to standard memory allocation?
Follow the steps above but use any standard fastboot enabled kdz (like this one). Then flash your rom or restore your backup - just remember you now have a smaller data partition
Special thanks to Mur4ik, EazyLuke & M1st3r1
You do of course follow these instructons at your own risk. Have fun!
*For me, the update process continued successfully beyond this point but some people have reported errors after the animation appeared so it is safer to remove the USB cable here.
many thanks for your tutorial!
What are the advantages compared to d2sys of lavero.burgos with anton_ch metod?
desmail said:
many thanks for your tutorial!
What are the advantages compared to d2sys of lavero.burgos with anton_ch metod?
Click to expand...
Click to collapse
This method means you can flash any custom rom and it will be data2system automatically instead of having to wait for someone to convert it. Plus you can use your existing backups.
Sent from my GT540 using XDA Premium App
Should not the type of phone in KDZ Updater be 3GQCT instead of CDMA which is what is shown in your picture? Just a thought incase it bricks anyones phone
gizmo001i said:
Should not the type of phone in KDZ Updater be 3GQCT instead of CDMA which is what is shown in your picture? Just a thought incase it bricks anyones phone
Click to expand...
Click to collapse
No. That's not important in CS_EMERGENCY mode.
Sent from my GT540 using XDA Premium App
OK my bad
OK, I have a bit of a problem. The KDZ Update has stopped and my phone has come up with a load of writing which says
[Blue Error Handler] Arm11 is crashed
[Press Volume Up Key] Rebbot&Savelog
[Press Volume Down
Linux Kernel Panic
Process init 9pid: 1)
followed by a load of codes. Does anyone have any ideas?
gizmo001i said:
OK, I have a bit of a problem. The KDZ Update has stopped and my phone has come up with a load of writing which says
[Blue Error Handler] Arm11 is crashed
[Press Volume Up Key] Rebbot&Savelog
[Press Volume Down
Linux Kernel Panic
Process init 9pid: 1)
followed by a load of codes. Does anyone have any ideas?
Click to expand...
Click to collapse
Did the kdz update say "finished"? Or did it hang before then?
Sent from my GT540 using XDA Premium App
It hung before finishing
gizmo001i said:
It hung before finishing
Click to expand...
Click to collapse
Repeat the process from step 1.
Sent from my GT540 using XDA Premium App
til the same, it crashes a step 212. Going to download original KDZ and try that
I think it's fine if it stops at 212, as far as I remember mine stopped also at 212.
Do you do the process without the battery? (you should)
And at some point the phone shows an animation that tells to put the battery back in. I think at this point it's finished.
Try downloading the kdz from this mirror:
http://narod.yandex.ru/disk/10706845001/20E_234-150-64.kdz
@eazyluke My guide looks ok to you?
Sent from my GT540 using XDA Premium App
This happened to me as well. I fixed it by putting sim, sdcard and battery back-in.
Then re-booted to fastboot using camera button + inserting usb cable. Fastboot came up with blue screen.
Then I ran in cmd
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot flash recovery recovery.img
rebooted to fastboot again
then flashed M4 using fastboot and then rebooted and I got my phone back.
Phone showed 234mb of storage free on re-boot
If this behaviour is confirmed then I'll add it to the guide. Mine flashed without error...
Sent from my GT540 using XDA Premium App
Mine didn't show any error, the process just didn't continue at some point, I think at 212. But everything is fine.
ive said that behavior clearly in my slightly-changed-translated from 4pda..
it's here: http://forum.xda-developers.com/showpost.php?p=13184840&postcount=42
m1st3r1 said:
ive said that behavior clearly in my slightly-changed-translated from 4pda..
it's here: http://forum.xda-developers.com/showpost.php?p=13184840&postcount=42
Click to expand...
Click to collapse
I see but mine went all the way through & said "finished" like it should. So that can happen too.
Sent from my GT540 using XDA Premium App
re-downloaded the kdz file and it all went well this time, so the file must have got mucked up a little during download. Either that or it those pesky LG gremlins playing about again. Thanks for everyones help though. I did have a little wobble of a panic for a while there lol.
gizmo001i said:
re-downloaded the kdz file and it all went well this time, so the file must have got mucked up a little during download. Either that or it those pesky LG gremlins playing about again. Thanks for everyones help though. I did have a little wobble of a panic for a while there lol.
Click to expand...
Click to collapse
Glad iit worked for you.
Sent from my GT540 using XDA Premium App

[UPDATE] Data2sd for salsa

THIS SCRIPT IS MADE BY MY FRIEND, puppeth13, ALL CREDITS GOES TO HIM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. make sure your sdcard has been partitioned in ext2
2. go to cwm recovery, wipe data, cache and dakvik cache. Reboot.
3. Install busybox, and choose the version v1.17.1
4. now go to cwm recovery again.
5. flash htc-data2sd sdcard
6. Reboot
* now check your internal storage.
* this script is made only for Salsa, can be used also for Wildfire S.
* REMEMBER, Make sure you have partitioned your sdcard using ext2 format and BusyBox v1.17.1 installed on /system/xbin
*made by puppet13th
UPDATE :
htc-data2sd-ext3.zip
download link
Compliments, this is brilliant
sent from my custom HTC Salsa.
where can I find htc-data2sd sdcard
crest_delta said:
where can I find htc-data2sd sdcard
Click to expand...
Click to collapse
just sorting that out matey
check my post.
*************PLz Note*****************
to create a partition on your SD card,firstly make a copy of it, IE back it up!
ie; insert sd card into sd card reader, goto my computer, right click on drive letter which has your sd card in, and copy, paste it to a folder of your choice somewhere on your computer.
this way it allows you to recover your sd card contents if all is lost....
I used mini-tool partition wizard, free download from the net.
follow instructions according to this post.
kanded said:
check my post.
Click to expand...
Click to collapse
The link seems to be expired for DATA2SD
http://www.media*fire..com/?cacv67vvo5ijmmb
OKAY the Correct link is :
http://www.mediafire.com/?cacv67vvo5ijmmb
Regards,
CD
If he's not replaced it ill host it shortly when my computers running.
Sent from my HTC C510e using Tapatalk
Thanks OP for sharing the script..
few questions here:
1. Can i flash it over a running stock odexed ROM?
2. Any precautions after i implement this script?
3. Any correct download link? as the posted links here dont work..
the link for data2sd is here >data2sd.
1. Can i flash it over a running stock odexed ROM? Yes
2. Any precautions after i implement this script? Yes and no, back everything up...make a copy of your sd on your computer. if done correctly no problems should appear
3. Any correct download link? as the posted links here dont work.. see above link
its a permanent host so it shouldn't expire
thanks bear for helping the OP. lol
after trying again, this time creating the ext by cwm which makes a swap drive....nothing. absolutely nothing. fresh install the lot.
back to the drawing board!
I too am having trouble with this, installed exactly as described but still nothing.
scuddnet said:
I too am having trouble with this, installed exactly as described but still nothing.
Click to expand...
Click to collapse
if someone can give a system.img & boot.img from the nandriod dump via cmw then i can give u guys an optimized rom with multilanguage support, data2sd & lot more
Sent from my HTC Desire HD using xda premium
I'm gonna flash my custom rom I found, ie transparent status bar blue icons, see if anything can be done. Main thing we need us data2sd it allowance for more space. It will be a new Image, nothing installed, freshly done.
Sent from my HTC C51o0e using Tapatalk
Img files including cwm recovery
ALL RUU FOR HTC SALSA
USE THIS COMMAND :
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
i replace all recovery.img files with the cwm recovery. so when you flash recovery.img, it means you are flashing the cwm recovery.
say thanks if you are fine with it
download link :
HUTCH AUS :
http://www.mediafire.com/download.php?oto5wj67v1nizdg
HUTCH TUR :
http://www.mediafire.com/download.php?4o4v5yfpopkraac
O2 UK :
http://www.mediafire.com/download.php?g5zj6888c26hb0z
WWE ASIA :
http://www.mediafire.com/download.php?belddvb6g6g9kbm
ASIA INDIA :
http://www.mediafire.com/download.php?2h042ctq0amb4r5
Europe :
http://www.mediafire.com/download.php?15ali46n6y64bs8
Kanded - Do you know if there is any difference between the O2 UK and Europe versions? Is is just that one is branded and the other isn't or are there other changes?
European is as it states, French, Spanish etc. Best use the UK as its more usable with modern languages lol.
I believe the ruu's listed are standard roms in the areas they sell this handset. Alot of users convert to UK, as markets available more lol
Sent from my HTC C510e using Tapatalk
Hello there,
I have a 2gigs sd card. I formated as 756mb ext2 and the rest as fat32. The case is that the CWM can't see the sd card when I do so. Therefore I cannot flash htc-data2sd.
Any clues?
Done, I now over 800mb free space. I didn't wipe data cache etc. I just flashed over my current rom and its fine.
Sent from my HTC C510e using Tapatalk

TF701 Root

Note1: Do at your own risk. As always, it's your device and you're responsible for your actions.
Note2: Following these steps will, in this order: void your warranty, factory reset your TF701, provide root.
These instructions will show you how to gain root on the Asus TF701 by unlocking the bootloader and using fastboot.
Prerequisites: drivers, adb and fastboot (this), firmware >= 10.14.1.47, asus unlock app
Unlock:
- Download the Asus unlock device app from asus.com
- Install and run the app. This will require a valid google account (if you use one time passwords, you'll need to generate one for this purpose) and internet access.
- When booting with [vol-] + [power] pressed, the transformer will show the message "The device is unlocked"
Root:
As the TF701 is very similar to the Nvidia Shield, this method is based on that.
- Download and unpack View attachment root.zip and cd into that directory
- Boot the transformer to the bootloader with [vol-] + [power] pressed
- fastboot boot zImage_dtb ramfs.img.gz
- When seeing the smeared graphics, wait until the transformer reboots 2 minutes and then hard reset (as I did), or press power once (as menollo did)
- The transformer should boot normally and start optimizing applications
- Check root
Foot note: I compared the TF701 and the Shield, and concluded that they should be similar enough to be able to boot the same ramfs. The root method itself was not developed by me.
This is my first instructional root post, what may or may not explain the general structure/mess.
If this was any help, please consider pressing the thanks button. Thanks.
This is based on previous version of https://github.com/linux-shield/shield-root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you tested this yourself and get it to work successfully?
of course i have
Thanks for the verification and screenshot! I hope there will be more dev support now that we have root.....
Sure.
My dev system's ready, I'm going to have a a try at getting a recovery running for the TF701.
However there's still a fair chance, someone will beat me to it.
Interesting, still a very new device. i think i will wait a bit to mess with it
but thanks for your contribution
fellow users, if this worked for you please leave a feedback for others
The big question, is do you have RW privileges to your /System folder? Try copying or deleting a file in /system, or open build.prop and add
# test
at the bottom and save. Or you can try setting the permissions via ES File explorer.
If you can't, then you really don't have full root access. Only Superuser and SU binary. This can cause problems when a root app tries to remount /system as RW (superuser updating binary for example).
Moscow Desire said:
The big question, is do you have RW privileges to your /System folder? Try copying or deleting a file in /system, or open build.prop and add
# test
at the bottom and save. Or you can try setting the permissions via ES File explorer.
If you can't, then you really don't have full root access. Only Superuser and SU binary. This can cause problems when a root app tries to remount /system as RW (superuser updating binary for example).
Click to expand...
Click to collapse
Using FX File explorer i remounted /system as RW, opened build.prop and added #test to the bottom, then saved the file. It works.
lpdunwell said:
Using FX File explorer i remounted /system as RW, opened build.prop and added #test to the bottom, then saved the file. It works.
Click to expand...
Click to collapse
Good to know
Have anyone tried this method for tf701 from tf300t? I know, it's for different models, but...
http://forum.xda-developers.com/showthread.php?t=2228613
lpdunwell said:
Using FX File explorer i remounted /system as RW, opened build.prop and added #test to the bottom, then saved the file. It works.
Click to expand...
Click to collapse
I confirm we have RW privileges in the /system folder. Titanium Backup wouldn't work at first so i started removing bloatware manually in the /system/app folder. I could do this without any problems. TB is working now, it need a wipe data first...
---------- Post added at 10:02 AM ---------- Previous post was at 10:00 AM ----------
HaPe000 said:
Have anyone tried this method for tf701 from tf300t? I know, it's for different models, but...
http://forum.xda-developers.com/showthread.php?t=2228613
Click to expand...
Click to collapse
I'v tried Motochopper when i got my tablet and is not working on the TF701.
FYI the "fastboot oem unlock" does nothing (atleast on US version) just says unknown command. But the other command works, I didn't even have to press power button rebooted on it own. Attached screen shot showing the command not needed.
adb oem unlock is indeed not needed, the asus app unlocks the bootloader, so you can skip that command.
And i also read the code that installs the superuser app. It copies some files, and after that, there is a reboot command, so it should reboot automatically.. (i dont know what happend in my case beacause you can't see the output.. i thought my power button press rebooted the device, but maybe i was just pressing it while the script was executing the reboot)
so after unlocking, you only have to reboot into fastboot (volume down), and run
Code:
fastboot boot zImage_dtb ramfs.img.gz
(in the folder where you downloaded/extracted the shield root files).
Is it possible to backup Apps and esp. Appdata (game data) with Asus backup tool and restore them again? I would hate to lose all my work in angry birds... :silly:
Yezariael said:
Is it possible to backup Apps and esp. Appdata (game data) with Asus backup tool and restore them again? I would hate to lose all my work in angry birds... :silly:
Click to expand...
Click to collapse
The rooting itself does not wipe anything, but unlocking with the asus tool factory resets your device.. so if you haven't unlcoked yet, your device will be wiped.. and at that moment you do not have root yet to backup your data unfortunately.
menollo said:
The rooting itself does not wipe anything, but unlocking with the asus tool factory resets your device.. so if you haven't unlcoked yet, your device will be wiped.. and at that moment you do not have root yet to backup your data unfortunately.
Click to expand...
Click to collapse
As of my understanding the Asus backup tool (on board by default) does backup data as well. Is this not true?
menollo said:
The rooting itself does not wipe anything, but unlocking with the asus tool factory resets your device.. so if you haven't unlcoked yet, your device will be wiped.. and at that moment you do not have root yet to backup your data unfortunately.
Click to expand...
Click to collapse
You are speaking from experience??
Because on none of the Asus Transformer tablets did unlocking do anything to the data partition.
What you are stating may be true for the Nexus, but I highly doubt it's true for the TF701.
Edit: It seems Asus has changed how the unlock tool works. I have read from two users so far who confirm that using the Unlock Tool will wipe your data - unlike on the TF700 (or the 101 and 300 for that matter) where unlocking did not touch your data. Correct me if I'm wrong - this seems strange.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Recovery File Name
The TF700T recovery file name was EP201_768_SDUPDATE.ZIP. Anyone know what the name is for the TF701T?
berndblb said:
You are speaking from experience??
Because on none of the Asus Transformer tablets did unlocking do anything to the data partition.
What you are stating may be true for the Nexus, but I highly doubt it's true for the TF701.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Unlocking will not only wipe your data partition, but also your internal sdcard. So backup all your stuff before unlocking. It happened on my Nexus 7, my wife's ME301T and with the TF701.
Sent from my GT-N7100 using XDA Premium 4 mobile app
ChrisDos said:
The TF700T recovery file name was EP201_768_SDUPDATE.ZIP. Anyone know what the name is for the TF701T?
Click to expand...
Click to collapse
From what I've read so far (caution: hearsay) the recovery on the TF701 recognizes a firmware file no matter if it sits on internal or microSD.
On the TF700 you had to rename the firmware file if you wanted to flash it from the microSD. This seems no longer necessary. Just download the firmware and unzip it once.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

Link2sd - brick

Hi, recently i got bricked my xsp by using link2sd.
I followed the tutorial to make 2nd ext4 partition on my SDcard.
After that, started link2sd, this screen appear:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I choose ext4, there are some notification after and then my phone suddenly turn off.
Tried the reset button at the back of the phone but no vibration at all.
Anyone can help please.
Thanks
Reflash with either Flashtool (see link in my Signature) or SUS (=Sony Update Service: http://www.sonymobile.com/nl/tools/update-service/)
mrjraider said:
Reflash with either Flashtool (see link in my Signature) or SUS (=Sony Update Service: http://www.sonymobile.com/nl/tools/update-service/)
Click to expand...
Click to collapse
Problem is flashtool not recognize my phone, Volumn down and plug in usb cable not show anything.
Normally it should show up green light but no.
May i have to wait 1 day or more to battery ran out and try again?
Did you made that partition on your External SD?
mrjraider said:
Did you made that partition on your External SD?
Click to expand...
Click to collapse
Yes i did 1027mb ext4 partition on Ex SD
Will it boot when you remove the External SD?
mrjraider said:
Will it boot when you remove the External SD?
Click to expand...
Click to collapse
No, its totally black now, nothing working. Even hard reset button .
I tried remove sdcard, sim... still nothing
Okay; first thing first.
Could you tell me exactly what you've done? I think something went wrong with the partitioning..
mrjraider said:
Okay; first thing first.
Could you tell me exactly what you've done? I think something went wrong with the partitioning..
Click to expand...
Click to collapse
Followd this guide: http://forum.xda-developers.com/showthread.php?t=2142844
I Format my sdcard to 3 partitions:
#1 FAT32 Primary
#2 EXT4 Primary
#3 Swap Primary
Then start link2sd, it asked for Ext2,3,4 i choose ext4. Some message show up and then my phone is now a brick.
Before it was in: .266 rooted Locked bootloader.
- Deleted -
Edit: What I only can suggest is try to get it booting into flashmode and try to reflash Stock ROM..
mrjraider said:
Just a plain simple question: Why? The XSP has plenty of storage for many many big applications...
I think our device or atleast 4.3 isn't compatible with link2SD and this has caused a very expensive brick..
Click to expand...
Click to collapse
Internal storage speed seem suck, try download torrent to internal storage, your phone will unresponsive.
But if download save to Sdcard then all good. I have unresponsive when start a application also, so i think its internal storage problems then i need move it to sdcard.
I guess link2sd make wrong mount point or something like that...
vipseifer said:
Internal storage speed seem suck, try download torrent to internal storage, your phone will unresponsive.
But if download save to Sdcard then all good. I have unresponsive when start a application also, so i think its internal storage problems then i need move it to sdcard.
I guess link2sd make wrong mount point or something like that...
Click to expand...
Click to collapse
Okay then the only thing i can suggest is trying to reflash the Stock ROM.
So I believe we need to fix that problem
So I need some intel:
- What OS
- Which Cable
- Which USB port
- Laptop or desktop
mrjraider said:
Okay then the only thing i can suggest is trying to reflash the Stock ROM.
So I believe we need to fix that problem
So I need some intel:
- What OS
- Which Cable
- Which USB port
- Laptop or desktop
Click to expand...
Click to collapse
I know how to flash using flashtool, did solve bootloop few times.
But now cant get phone in flashmode, for your intel:
- What OS : Win 7 Ultimate 64 bit
- Which Cable: Sony one
- Which USB port: usb 2.0
- Laptop or desktop: Desktop PC( Did flash rom before on this pc)
Click to expand...
Click to collapse
The point is; to fix your unbootable device I think it needs to be fully resets by reflashing the Stock ROM. And because this process will rewrite the entire phone it will undo the partitioning.
Power+Volume down results in a greed led. Does this led stays on or not?
mrjraider said:
The point is; to fix your unbootable device I think it needs to be fully resets by reflashing the Stock ROM. And because this process will rewrite the entire phone it will undo the partitioning.
Power+Volume down results in a greed led. Does this led stays on or not?
Click to expand...
Click to collapse
nothing hapened, no led, no vibration
Even no red Led when connect to wall charger
Perhaps your battery is empty (I know it is a cheap shot but worth trying dont you think) so let it charge for an hour and try again...
mrjraider said:
Perhaps your battery is empty (I know it is a cheap shot but worth trying dont you think) so let it charge for an hour and try again...
Click to expand...
Click to collapse
Thanks, everything worth to try , trying now.
mrjraider said:
Perhaps your battery is empty (I know it is a cheap shot but worth trying dont you think) so let it charge for an hour and try again...
Click to expand...
Click to collapse
No luck
Well.... The last thing I can advise to you is go to a service point and let them repair your phone. I think we can't fix it this way.

Categories

Resources