Database Info

Need Help rooting and Flashing on Sprint?

Hello. I am sick from school today and decided to make a thread to help out some people.
DOWNLOADS ARE BELOW(AT THE BOTTOM!!!)
All of these steps are posted on TheUnlockr.com in a Video but The video is for the GSM version. The difference is just the recovery image. (http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click/)
Ok lets get started.
This method works on all Sprint phones with updates. I am not sure how long this will last unpatched.
First YOU HAVE TO HAVE ADB WORKING!!!
Download my zip file if you do not want to download the entire SDK.
1)After it is downloaded, extract the files to C:\Windows\System32\
(you can copy and past the file-path)
2) Now pickup your phone and go into Settings-Applications and Enable Unknown Sources then from there go into Development and make sure that USB Debugging is enabled.
3) Now connect your phone to your computer and open up command prompt (Start-Run(or search) cmd.exe.
4)When it is open type: ADB Devices.
You should see your'r phone's serial.
Now download flashrec-1.1.3-20091107-2.apk (the download is below)
1) Copy the file to your sdcard.
2) Download any File Manager from the android market.
3) Go to your Sdcard in the file manager app on your phone.
4) Press flashrec-1.1.3-20091107-2.apk
Let it install.
5) When it is complete, go to your apps drawer and open the Recovery Flasher app.
My method requires you to have a recovery image before root.
6) In the recovery flasher app, Press Backup Recovery Image
7) Let it work. You may have to try twice for Success.
8) Now Mount your phone back on the computer and replace the recovery-backup.img with the recovery-backup.img on this thread(MAJOR thanx to Amon_RA)
9) Now unmount your phone and go back into the Recovery Flasher app on your phone.
10) Now press restore and let it flash recovery-RA-heroc-v1.2.3.img(Amon_RA's Sprint custom recovery image)
YOU NOW HAVE A CUSTOM RECOVERY IMAGE!!! WOOT WOOT
the work is still not done.
Download the Superuser.zip(http://forum.xda-developers.com/attachment.php?attachmentid=211569&d=1249225060 or in the downloads below) and extract it to your Sdcard
Now go into your new recovery image (power off the phone and then power it on by holding the Power and Home buttons)
Connect your phone to a computer and run command prompt.
IN COMMAND PROMPT TYPE:
Code:
adb shell
mount /sdcard
mount /system
cp /sdcard/su /system/bin/
chmod 4755 /system/bin/su
cp /sdcard/Superuser.apk /system/app/
reboot
(you can copy and past the code into command prompt from the thread)
Download the Better Terminal Emulator app from the market and type:
Code:
$ su
if you get a
Code:
#
then...YOU NOW HAVE ROOT!!
now you can install custom ROMs and root-required apps
FlashREC(Recovery Flasher): http://zenthought.org/system/files/asset/2/flashrec-1.1.3-20091107-2.apk
Amon RA's Sprint Recovery: http://www.mediafire.com/file/uozzgzmmnym/recovery-backup.img
Superuser.zip: http://www.mediafire.com/file/3mddanwztzd/superuser.zip
ADB and Fastboot(for those who need it): http://www.mediafire.com/file/tyib2wmomym/ADB_Fastboot.zip

app2sd Step for step for any device (even 1.6 dount)

You need a rooted device
1.Step
Patitioning your sd-Card
forum .xda-developers.com/wiki/index.php?title=SD_card_partitioning
here is a great Howto for this
2. Step
plug on your device via usb to the computer
if you don't have it enable usb debugging
now extract the zip from the Attachment into the root of your sdcard
3. Step
open and adb shell with
Code:
adb shell
now instert the folloing command
Code:
sh /sdcard/app2sd.sh
4. Step
to install app2sd youst press enter
after some time your phone should be reboot
info : on the x10 they will the led lights show you if there is an error
with the sdcard
but my script creates a failsafe it's on /data/appbak
it will be used if you had an sdcard malfunktion
please say me all errors you have
wolfilein

I may need to edit something because I get this error on my M003 (Via8505) :
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument
mount: mounting /dev/block//vold/179:2 on /system/sd failed: Invalid argument
busybox is /busybox/bin/busybox
tet
rm: can't remove '/etc/mount_sd.sh': No such file or directory
Partitioned SDcad with three partitions 1. 7gig Fat32 2. 96MB Swap 3. (1GB-96MB) as ext2
System will not complete boot now. Sits at initial boot screen then goes dark. Never get to animated logos.
Time to reflash ROM
Wanted swapfile. If it's the issue I'll remove it and try again

wolfilein said:
You need a rooted device
1.Step
Patitioning your sd-Card
forum .xda-developers.com/wiki/index.php?title=SD_card_partitioning
here is a great Howto for this
2. Step
plug on your device via usb to the computer
if you don't have it enable usb debugging
now extract the zip from the Attachment into the root of your sdcard
3. Step
open and adb shell with
Code:
adb shell
now instert the folloing command
Code:
sh /sdcard/app2sd.sh
4. Step
to install app2sd youst press enter
after some time your phone should be reboot
info : on the x10 they will the led lights show you if there is an error
with the sdcard
but my script creates a failsafe it's on /data/appbak
it will be used if you had an sdcard malfunktion
please say me all errors you have
wolfilein
Click to expand...
Click to collapse
so there is a chance that I can brick my phone (kyocera zio 1.6) and since phone doesnt have a recovery i would be screwed? correct?

i would like to know as well...
jcaf77 said:
so there is a chance that I can brick my phone (kyocera zio 1.6) and since phone doesnt have a recovery i would be screwed? correct?
Click to expand...
Click to collapse
i've been looking into this as well and was wondering the same thing as jcaf.. i have 0 space on this phone and would love to be able to install stuff onto sd card, thanks in advance

please help me..I got on Xperia X8..
busybox: not found
mkdir failed for /system/xbin, file exists
[2]
rm failed for /etc/mount_sd.sh, No such file or directory
sed: cannot create temp file /init.rccfoXyj: Read only file system
:::finished going reboot now:::
and he keeps restarting after SE logo..

Does it work on i5800 with ROOT?

help Root lenovo A60+

Help Me how to root this device.
lenovo A60+.
i'm try used how root A60 can't use.
Tolong dong bagaimana root Lenovo A60+. sudah mencoba tutorial yg A60 blm berhasil. pakai Oneclik juga gagal. adakah kawan dan saudaraku semua yg pernah root.
android 2.3.6
A60+_row_s310_120823 (build NUmber)
baseband
MAUI.11AMD.W11.50.V13.p7 2012/08/03
terima kasih bantuannya.

Go to Kaskus. There is a lounge for lenovo a60 there.

iswanptr18 said:
Go to Kaskus. There is a lounge for lenovo a60 there.
Click to expand...
Click to collapse
driver A60+ its differrent with A60

if you have linux as your system, you won't need a driver, but please do it at your own risks.
for first step, download SuperOneClick from shortfuse.org *it's for windows? yes, but it have adb for linux
make your device debug-able: Settings -> Applications -> Development -> Check USB Debug then connect it using USB to your PC
open your terminal on linux, mount to SuperOneClick directory
follow this step:
Code:
linux:~$ cd ADB
linux:~$ chmod 755 adblinux
linux:~$ ./adblinux devices
and it will show:
Code:
List of devices attached
4257323032BC4C34385A device
back to terminal and follow this step to copy all file that needed to exploit your android:
Code:
linux:~$ ./adblinux push Exploits/psneuter /data/local/tmp
linux:~$ ./adblinux push Root/su-v3 /data/local/tmp
linux:~$ ./adblinux push Root/Superuser.apk /data/local/tmp
after all files copied to your device, use shell on the droid
Code:
linux:~$ ./adblinux shell
$ cd /data/local/tmp
$ chmod 755 psneuter
$ ./psneuter
after that step above, USB connectivity will restarting for a seconds.
back to shell using ./adblinux shell on your terminal, and there will displaying # symbol if your root process is successful.
on the adb shell, type mount and find the /system mount point, for example: /dev/block/mtdblock0 on /system type yaffs2 (rw)
and then on adb shell, use this command below to finish your root process
Code:
# mount -o remount,rw /dev/block/mtdblock0 /system
# cat su-v3 > /system/bin/su
# cat Superuser.apk > /system/app/Superuser.apk
# chmod 06755 /system/bin/su
# chmod 0755 /system/app/Superuser.apk
check your app drawer, if you found Superuser on it, it was completed and successful. Good Luck!

Root Lenovo A60+ successfully
You need these tool:
1. Flash Tool: dropbox.com/s/f7gfyqtwyn5qkpa/ISO-8859-1__Flash tool.rar
2. Firmware Upgrade: mediafire.com/?ehiyzbdmlauo7i7
3. ROM MOD S317 by MAKIS V1.3the best one so far)
mediafire.com/download.php?u3ehud5ttldijca
4. Recovery: mediafire.com/?bo12ktkrrn57314
5. Driver: 4shared.com/archive/pimdjzA8/MT6575_USB_VCOM_drivers.html
Follow these step by step:
Step 1: Copy zip file ROM MOD S317 ( downloaded link number 3) and 2 file Recovery (link number 4) into the SD card
Step 2: Turn off the phone, take the battery out, plug usb cable and install Driver for the device (link number 5)
Step 3: unplug usb cable, insert the battery (not turn on the device yet). Run Flash Tool
Click scatter-loading. Browse to the MT6575_Android_scatter.txt file locate in the Firmware update extracted folder (link number 2). Tick all 9 options. Click Firmware-Upgrade
Step 4: Hold volume + key and plug the cable until the process running, release the key. Wait around 5 minutes until the green circle appear mean success
Step 5: After turn on the device we notice the default language are Chinese.
Install file Mobileuncle.apk that you copied in step 1.
Run the application and choose FLASH RECOVERY FROM SD CARD > select Recovery.img
The device will be restarted automatically
Step 6: Press Volume + during the device turned on to enter Recovery and do the following:
+ Wipe data/factory reset
+ Wipe cache partition
+ install zip from sdcard
+ choose zip from sdcard
Browse to the zip fle that you copied on step 1. wait for 30 seconds
Finished. Enjoy!

maihuuluong said:
You need these tool:
1. Flash Tool: dropbox.com/s/f7gfyqtwyn5qkpa/ISO-8859-1__Flash tool.rar
2. Firmware Upgrade: mediafire.com/?ehiyzbdmlauo7i7
3. ROM MOD S317 by MAKIS V1.3the best one so far)
mediafire.com/download.php?u3ehud5ttldijca
4. Recovery: mediafire.com/?bo12ktkrrn57314
5. Driver: 4shared.com/archive/pimdjzA8/MT6575_USB_VCOM_drivers.html
Follow these step by step:
Step 1: Copy zip file ROM MOD S317 ( downloaded link number 3) and 2 file Recovery (link number 4) into the SD card
Step 2: Turn off the phone, take the battery out, plug usb cable and install Driver for the device (link number 5)
Step 3: unplug usb cable, insert the battery (not turn on the device yet). Run Flash Tool
Click scatter-loading. Browse to the MT6575_Android_scatter.txt file locate in the Firmware update extracted folder (link number 2). Tick all 9 options. Click Firmware-Upgrade
Step 4: Hold volume + key and plug the cable until the process running, release the key. Wait around 5 minutes until the green circle appear mean success
Step 5: After turn on the device we notice the default language are Chinese.
Install file Mobileuncle.apk that you copied in step 1.
Run the application and choose FLASH RECOVERY FROM SD CARD > select Recovery.img
The device will be restarted automatically
Step 6: Press Volume + during the device turned on to enter Recovery and do the following:
+ Wipe data/factory reset
+ Wipe cache partition
+ install zip from sdcard
+ choose zip from sdcard
Browse to the zip fle that you copied on step 1. wait for 30 seconds
Finished. Enjoy!
Click to expand...
Click to collapse
I finished root my lenovo a60+ but i have a problem with recieve the message, it don't display my friend's name in contact, it only display +849xxx . Can you fix it ?
--- sorry about my english is bad

Lenovo A60+ ROM MOD S317
maihuuluong said:
3. ROM MOD S317 by MAKIS V1.3the best one so far)
Click to expand...
Click to collapse
Hi,
can anybody write me some more details about ROM MOD S317 by MAKIS V1.3? What languages does it include? Does it have all Google applications, etc ...
I cannot find any "developer" of this ROM site in Google and I would like to know if after installing of this rom there will be more empty space for apps installation.
I found only a discussion of Philipines guys (I suppose) on symbianized forum...

Phyt0n said:
Hi,
can anybody write me some more details about ROM MOD S317 by MAKIS V1.3? What languages does it include? Does it have all Google applications, etc ...
I cannot find any "developer" of this ROM site in Google and I would like to know if after installing of this rom there will be more empty space for apps installation.
I found only a discussion of Philipines guys (I suppose) on symbianized forum...
Click to expand...
Click to collapse
It's only in English (default) and Chinese.
Is there any way to add more languages to an Android ROM?
Or any other custom rom (or a way to build it for this phone)?

[GUIDE] Backing up a phone with broken display

I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Prerequisites
Rooted phone with broken display/digitizer/etc. Display is nonfunctional for whatever reason.
ADB for your platform. Downloads for Windows, Mac, and Linux can be found at my dev-host.
Drivers installed (Windows), rules file set up (Linux + Mac). Drivers for windows can be found here. Rules file for Linux can be found here.
Recovery file attached to this post. (twrp.img)
External sdcard with at least 2 GB free space inserted in your broken phone.
openrecoveryscript.txt file attached to this post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your broken device
Extract the ADB zip somewhere convenient.
Move the twrp.img recovery file into the ADB extracted directory.
Move the openrecoveryscript.txt file into the ADB directory.
Open a command prompt / terminal window in the ADB directory.
Windows: Windows Key + R => Type in "cmd" then click "RUN".
Linux: Open a terminal window by selecting it from your applications.
ALL:
Code:
cd /path/to/ADB/directory
Pull the battery from your phone, place it back in and boot into recovery (VolUp + Home + Power).
Connect your phone to your computer
Make sure that the following command returns "XXXXXX recovery" before proceeding to the next step.
Code:
./adb devices
Expected output:
Code:
List of devices attached
XXXXXXX recovery
Now to install TWRP recovery to your device. Type the following commands ( after each line). Linux users: Make sure you prepend each command with "./", as in "./adb ...". ALL Make sure you type the commands in CAREFULLY.
Code:
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
Wait until the last command above returns an output similar to below before proceeding to the next step:
Code:
12916+0 records in
12916+0 records out
6612992 bytes (6.3MB) copied, 1.094278 seconds, 5.8MB/s
Now pull your phones battery and reboot into recovery once again.
Run the following command to make sure your phone has booted into recovery completely.
Code:
adb devices
Expected output
Code:
List of devices attached
XXXXXXX recovery
Type the following to set up a script that will backup your phone to your external sdcard.
Code:
adb push openrecoveryscript.txt /cache/recovery/openrecoveryscript
Reboot your phone once more. This time, TWRP will begin backing up your ROM.
Wait for the backup to finish. You will know it is finished when you feel your phone reboot once more.
Optionally, you can check the state of your backup by running the following command and reading the last couple lines of it's output.
Code:
adb shell cat /tmp/recovery.log
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!

CNexus said:
I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!
Click to expand...
Click to collapse
wheres the openrecoveryscript.txt??

Sorry. It's attached here
http://forum.xda-developers.com/showthread.php?t=2353828
I'll attach it to this post when I get home, I keep forgetting.
Sent from my buttered S3

[Q] CWM Recovery loading at startup and infinite boot animation issue

Hello,
I have nerve-breaking issue with CWM Recovery wich loads up every time i turn on my tablet. So if i wish to restart or to go to CWM i have to hold volume down button to get to bootloader and then select Android to get back to CWM.
So my first question is how do i resolve this problem with constant booting into CWM Recovery? so it would go to recovery only when i select reboot to recovery option in CWM
My next issue is that i have tried to install Ubuntu Touch for TF101 (from ubuntu touch wiki). And in installation guide it says you have to download cm-10.1-20130404-UNOFFICIAL-tf101.zip, and then quantal-preinstalled-phablet-armhf.zip. The fist zip i got successfully but the second link did not exist, so i checked their repository and found similar zip named saucy-preinstalled-phablet-armhf.zip (i tought it's a newer version) well, then i made data wipe and installed both as stated in guide, i also deleted cache and now when i try to boot my tablet i get to blue spinning CWM logo and it stays there for eternity.
So my second question is how to put some other rom on SD card so i can install another rom? or what i have to do to make Ubuntu Touch work?
My third thing that i noticed (for me it seems wrong) is that with every data wipe it makes new 0/ folder and it keeps everything before wipe in it. I made couple of data wipes and now my data structure looks something like this:
Code:
0/
0/
0/
0/
ASUS/
Alarms/
Albums/
AndroZip/
...other folders (apps and data from stock rom)
Alarms/
Android/
Autodesk/
DCIM/
...other folders (probably from first wipe)
Alarms/
Android/
DCIM/
Downloads/
...other folders (probably from second or third wipe)
legacy/
obb/
obb/
So my third question is if this is the correct data structure because it seems wrong for me? And how to resolve that issue?
My un-educated guess is that all three problems are connected, but my android experience and knowdlege is far to small to have a clue how to begin resolving this twisted problem.
I did some researching and as far it goes with second question i think i have soft-bricked tablet (maybe there is still hope?). So i would like to make it back to original rom or 4.2 jelly bean as i had till now without CWM Recovery issue, if possible of course
(Using ClockworkMod Recovery v5.8.3.4 now, and i think at beginning there was ROM Manager used, i bought used tablet)
Please help, thx

The issues are somewhat intertwined, and run back to using CWM 5.8.X.X
The first thing you MUST do is stop the CWM bootloop or you will not be able to install any other ROM or recovery.
If you can boot to a ROM, run a terminal window with SU permissions. If you cannot boot to a ROM, you will need to run from an ADB Shell from a computer when booted to recovery:
Code:
echo boot | dd of/dev/block/mmcblk0p3 bs=1 seek=0
Then reboot normally and your bootloop to CWM should be fixed.
Next, I HIGHLY HIGHLY recommend upgrading to TWRP 2.3.2.3 or higher. The /0/0/0/0 issue has to do with the new directory structure of Android 4.2 for multi-users. CWM 5.8.X.X cannot handle multi-users properly.
TWRP 2.3.2.3 can be updated using the GooManager app (tap the menu key in the top right and choose Install OpenRecovery Script).
IMO, TWRP is far superior to CWM as it has a file manager and terminal emulator.
I am running SidneyK's TWRP 2.6.3.0. He has a zip that can be flashed from CWM to update, however you have to have the boot loop issue resolved or it will not flash.

Ok, as you said i cannot boot to ROM so i tried with ADB Shell but it says
error: device not found
I have device connected on keyboard dock and cable from dock to pc
Any advices how to reslove that issue? Am i missing some drivers?
In device manager i can see that there is a Transformer device with yellow exclamation. I tried to install drivers from asus webpage but it wont install.
Should i get copy of live linux and try from there?
EDIT:
I got the connection working with ADB Shell but i got this response from code you provided
Code:
~ # echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes (5B) copied, 0.006079 seconds, 822B/s
Ok now i'm not getting to recovery after restart, but now my tablet is constantly restarting... after Asus eee image there is few secodnds of black screen and then it restarts itself.
Could this be due to my Ubuntu Thouch installation attempt?
Or how can i remove CWM Recovery and install TWRP whitout working ROM on tablet?

boonz said:
Maybe i should type?
Code:
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
Click to expand...
Click to collapse
Damn, yeah, it should be ...of=dev/block/...
D'OH!

I made few more edits on previous post as i was trying diffrent things. So currently i'm at this position:
Code:
~ # echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes (5B) copied, 0.006079 seconds, 822B/s
Ok now i'm not getting to recovery after restart, but now my tablet is constantly restarting... after Asus eee logo there is few secodnds of black screen and then it restarts itself.
Could this be due to my Ubuntu Thouch installation attempt or should i push some basic ROM from asus webpage to tablet and replace it with Ubuntu Touch in order to proceed with your instructions?
Or how can i remove CWM Recovery and install TWRP whitout working ROM on tablet?
Thx

boonz said:
I made few more edits on previous post as i was trying diffrent things. So currently i'm at this position:
Code:
~ # echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes (5B) copied, 0.006079 seconds, 822B/s
Ok now i'm not getting to recovery after restart, but now my tablet is constantly restarting... after Asus eee logo there is few secodnds of black screen and then it restarts itself.
Could this be due to my Ubuntu Thouch installation attempt or should i push some basic ROM from asus webpage to tablet and replace it with Ubuntu Touch in order to proceed with your instructions?
Or how can i remove CWM Recovery and install TWRP whitout working ROM on tablet?
Thx
Click to expand...
Click to collapse
There are a few ways.
You can use ADB to push the TWRP.zip from sidneyk's thread in the dev section, install that from the internal storage.
If you have a TF101 (non 3G) you can use one of my repacked EasyFlasher in APX mode to push TWRP: http://forum.xda-developers.com/showpost.php?p=43986513
Another option is to use the .blob file (extracted from the zip) and use adb to install when in CWM recovery.
Push the blob file to the /sdcard/ (called twrp.blob for this example)
Use adb shell and execute:
Code:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (you need to see the progress indicator complete before rebooting to recovery). What I do is just hold the power button for 10 seconds, once the progress bar completes and it flashes black, hold VOL DOWN until you see the RCK message then tap VOL UP to boot to recovery. With any luck you will see TWRP.

Now i downloaded TWRP 2.6 for TF101 from teamw.in page and i got that twrp.blob file.
Then i executed adb push and it says it successfully copied file
But when i check in adb shell it says i cannot go or look into sdcard.
Am i missing some sort of permissions? or would live linux still be better option and using it with su might help?
Or is it ok and i should just run dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4?
Code:
C:\Program Files\Android\sdk\platform-tools>adb push C:\Users\BoonZ\Downloads\twrp.blob sdcard
1322 KB/s (4984908 bytes in 3.682s)
C:\Program Files\Android\sdk\platform-tools>adb shell
~ # cd sdcard
cd sdcard
/sbin/sh: cd: can't cd to sdcard

boonz said:
Now i downloaded TWRP 2.6 for TF101 from teamw.in page and i got that twrp.blob file.
Then i executed adb push and it says it successfully copied file
But when i check in adb shell it says i cannot go or look into sdcard.
Am i missing some sort of permissions? or would live linux still be better option and using it with su might help?
Or is it ok and i should just run dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4?
Code:
C:\Program Files\Android\sdk\platform-tools>adb push C:\Users\BoonZ\Downloads\twrp.blob sdcard
1322 KB/s (4984908 bytes in 3.682s)
C:\Program Files\Android\sdk\platform-tools>adb shell
~ # cd sdcard
cd sdcard
/sbin/sh: cd: can't cd to sdcard
Click to expand...
Click to collapse
Try doing cd /sdcard/
If that does not work, you can also just push the twrp.blob to the / directory and push it from there too.

frederuco said:
Try doing cd /sdcard/
If that does not work, you can also just push the twrp.blob to the / directory and push it from there too.
Click to expand...
Click to collapse
Ok superb, i have TWRP it says v2.3.2.3
How do i perform something like format or delete everything (so there will be no 0/0/0/ folders or whatsoever) and make my tablet usefull again. I would like to run jellybean again because i'm pretty used to it and delete that Ubunto Touch mess i made. Maybe little help here, so i don't mess anything up?
Thx

Go to the Wipe section.
Wipe the system, davlik and also the cache.
Choose the FORMAT DATA option to completely wipe the /data/ partition (this deletes everything in the /data/media/ aka /sdcard/ directory)
Then I would reboot back to recovery (suggested after a format data) and then install your ROM, applicable GAPPS and kernel if necessary.