Develop Bugs

[TUT][DUMP] DUMP Stock ROM (SYSTEM/BOOT/etc) | OneX_SEA_WWE_1.26.707.2_SYSTEM + BOOT

Basically u need adb/android SDK before proceed.
[WITH ROOT ACCESS]
[+] Dump/copy boot.img
Code:
Command prompt :
> adb shell
> su
> dd if=/dev/block/mmcblk0p4 of=/sdcard/boot.img
More partition/img availabe to dump. Will update later.
[WITHOUT ROOT ACCESS]
Currently only /system is usable
1) Android SDK (just need adb)
2) Download busybox
3) Command prompt :
> adb push busybox /data/local/busybox
> adb shell
> cd /sdcard/
> chmod 755 /data/local/busybox
> /data/local/busybox tar cvf sysdump.tar /system
4) Ignore tar: error exit delayed from previous errors'. Is done correctly.
----------------------------------------------------------------------
Just finished dumped my semi-virgin One X system partition from SEA WWE stock ROM .
The file would be OneX_SEA_WWE_1.26.707.2_SYSTEM_DUMP.zip 558.3 MB

Hi,
can you tell me how to dump mine? My phone arrives tomorrow.
Thanks in advance...

@anko
Thread updated with guide.

so, is it true that i can simply download the system dump from the link your provide, and flash it via recovery if i want to go back to stock SEA rom?
by the way, i am using a SEA htc one X too.

ck_looi said:
so, is it true that i can simply download the system dump from the link your provide, and flash it via recovery if i want to go back to stock SEA rom?
by the way, i am using a SEA htc one X too.
Click to expand...
Click to collapse
not sure & never try
it was dumped before i unlock my device.
see here if u want unlock & backup ur stock rom including boot image. do nandroid backup after flashing Interim CWM. Then only restorable. (boot .img still hv to flash thru fastboot to restore or use new method by blubbers)

my current stock is 1.26.707.4
will i be able to flash this and then get update to 707.4 OTA? Just want to make sure i got the right stock rom for my one x.

Picked mine up today going to do system dump of mine its on t-mobile software is 126.110.5
Sent from my HTC One X using XDA

monx® said:
Basically u need adb/android SDK before proceed.
[WITH ROOT ACCESS]
[+] Dump/copy boot.img
Code:
Command prompt :
> adb shell
> su
> dd if=/dev/block/mmcblk0p4 of=/sdcard/boot.img
More partition/img availabe to dump. Will update later.
Click to expand...
Click to collapse
i just dump boot (mmcblk0p4) and system (mmcblk0p12). is that good enough? (maybe recovery partition) I assume i would use fastboot flash to flash this image if I want to revert to stock?

zenkinz said:
i just dump boot (mmcblk0p4) and system (mmcblk0p12). is that good enough? (maybe recovery partition) I assume i would use fastboot flash to flash this image if I want to revert to stock?
Click to expand...
Click to collapse
Yes but RUU 1.26.707.4 is available (at least for our region). better extract *.img directly.

monx® said:
Yes but RUU 1.26.707.4 is available (at least for our region). better extract *.img directly.
Click to expand...
Click to collapse
ok thanks.

I've done Paul's procedure to Unlock + Interim CWM + SU, so now I'm rooted with S-On. After which I've done full backup thru interim CWM recovery prior to uninstalling bloatwares and I'm still now on stock ROM.
How different is this backup then? Back to stock?
Sent from my HTC One X using xda premium

Gday, now this looks like it spits out a tar file, I assume this is flashable through fastboot? I'm just trying to put together a fastboot flashable img of my providers stock rom for another user...
Edit, I might be being stupid, but shouldn't adb pick up the stock rom when connected and booted into rom? Put usb connection into usb host mode...
M.

2nd method works great...
monx® said:
Basically u need adb/android SDK before proceed.
[WITH ROOT ACCESS]
[+] Dump/copy boot.img
Code:
Command prompt :
> adb shell
> su
> dd if=/dev/block/mmcblk0p4 of=/sdcard/boot.img
More partition/img availabe to dump. Will update later.
[WITHOUT ROOT ACCESS]
Currently only /system is usable
1) Android SDK (just need adb)
2) Download busybox
3) Command prompt :
> adb push busybox /data/local/busybox
> adb shell
> cd /sdcard/
> chmod 755 /data/local/busybox
> /data/local/busybox tar cvf sysdump.tar /system
4) Ignore tar: error exit delayed from previous errors'. Is done correctly.
----------------------------------------------------------------------
Just finished dumped my semi-virgin One X system partition from SEA WWE stock ROM .
The file would be OneX_SEA_WWE_1.26.707.2_SYSTEM_DUMP.zip 558.3 MB
Click to expand...
Click to collapse

Does this work on other models?
helloansuman said:
2nd method works great...
Click to expand...
Click to collapse
Hi, I was curious if this worked on other models specifically the xperia arc so-01c. I wish to dump a japanese docomo rom that I guess is pretty rare for English websites. Thanks in advance. AJ

I already have my boot.img and what not just need to dump my boot.img-kernel... How to?

2nd method works great on other phone thankx man!
just tell us one more thing that how to dump boot/kernel in the same is it possible or not ??

(Q) Best recovery?

What is the most reliable recovery currently? I'm using twrp at the moment. It's probably an older version so I'm curious what is recommended before i update it.
Sent from my Kindle Fire using Tapatalk 2

pwned3 said:
What is the most reliable recovery currently? I'm using twrp at the moment. It's probably an older version so I'm curious what is recommended before i update it.
Sent from my Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
My suggestion would be for you to stay with TWRP. Version 2.1.1 is the latest.

kinfauns said:
My suggestion would be for you to stay with TWRP. Version 2.1.1 is the latest.
Click to expand...
Click to collapse
I agree
Sent from my Galaxy Nexus using XDA

pwned3 said:
What is the most reliable recovery currently? I'm using twrp at the moment. It's probably an older version so I'm curious what is recommended before i update it.
Click to expand...
Click to collapse
You already know that TWRP is intuitive and easy to use. I'm using TWRP 2.1.1 and I have used recovery many times when trying out new ROM builds. Occassionally with 2.1.1 I find that the operation that you want to do just fails with either an error outright or will fail during the recovery process. It even failed on me once while creating a backup. I didn't pay much attention to the backup output log text once and I did want to recover that backup and could not due to an image file being zero bytes in size. I have my own app and data backup script that I wrote that keeps me current so recovery in such a failed case is simply flashing a new ROM and executing my recovery script; couldn't be simpler.
If you pay attention to TWRP's output and not just make an assumption that the backup or recovery succeeded then you can just repeat the operation until it's successful. This is rare but has happened to me more than once but even with that issue, I still like TWRP 2.1.1 (plus my own app backup script).
I'll include my app backup and recovery script here in case others can find it useful (I make no claims that will work to your liking however or that it will even work for you)
rebaseline.sh
Code:
#!/system/xbin/bash
cd /sdcard/BACKUP/
for i in `/system/bin/pm list packages -3 -f`
do
read junk apk pkg <<< =`echo $i | sed -e 's/[=:]/ /g'`
echo "Processing $pkg..."
echo " backing up $apk..."
cp $apk baseline/
touch /sdcard/BACKUP/baseline/`basename $apk`
echo " backing up data..."
busybox tar czf /sdcard/BACKUP/baseline/$pkg.tar.gz --exclude lib --exclude cache /data/data/$pkg 2>/dev/null
done
echo "Processing accounts..."
echo " backing up data..."
busybox tar czf /sdcard/BACKUP/baseline/accounts.tar.gz /data/system/accounts.db 2>/dev/null
Here is my recovery script:
restore-from-baseline.sh
Code:
#!/system/xbin/bash
cd /sdcard/BACKUP
pm set-install-location 1
chmod 777 /data/data
for i in baseline/*apk
do
X=${i/-[0-9].apk}
Y=`basename $i`
Y=${Y/-[0-9].apk}
echo $X
pm install -r $i
# Find out what the new app ID is for the package
OWNER=`/system/bin/ls -l /data/data | grep $Y | awk '{print $3;}'`
echo $OWNER
# Restore data as the app owner ID
chmod 777 /data/data/$Y
su --command "tar xvf /sdcard/BACKUP/$X.tar.gz -C /" $OWNER
echo "tar rc=$?"
chmod 751 /data/data/$Y
echo
done
chmod 771 /data/data
echo "Restoring accounts.db - reboot will be required"
tar xvf /sdcard/BACKUP/baseline/accounts.tar.gz -C /
There is one limitation that I haven't worked into the script yet. Any time there is an app update you will see a duplicate app in the baseline folder differentiated by -1 or -2. Before recovery you can just get rid of the oldest version of the apk file; the data is always current.
I'm sure that there are a lot of apps that this script would not work with but it does work very well with mine and cuts down recovery to a minute or two. I don't use Titanium Backup myself.

I've been sticking with TWRP 2.1.1, simply because I really like how it can compress backups, meaning more space for music and videos. Haven't had any issues with it, but I do prefer the look of CWRecovery, particularly Hashcode's latest release.

Assert Failed Error

Hi!
I have the International Version of the HTC One X.
Today I tried to install Paranoid Android. Originally, I had installed the version 1.99. I did this successfully. However, I saw that 2.00 is available. So I tried to reflash a new rom. I got an error as follows:
assert failed: getprop("ro.product.device") == "endeavoru" || getprop("ro.build.product") == "endeavoru"
I tried a clean rewipe first using a nandriod backup of the stock sense UI, but I couldn't start up after. I then proceed to use the RUU for a complete wipe back to stock. This worked.
When I tried installing again, both 1.99 and 2.00 are giving me the assert failed error.
Would appreciate assistance.
Thanks!

Based on what I've read, the most similar thread I can find is http://forum.xda-developers.com/showthread.php?t=1836023&page=2
Short of editing the check script, I've followed every step in the last post of the thread multiple times. I'm trying to avoid editing the check script if I can.

Ive seen this happen a handful of times. The only way to really get down to this is see what getvar is returning.
If you could go into Recovery (CWM or TWRP) and open up adb shell and issue the command: grep -e 'ro.build.product' -e 'ro.product.device' /system/build.prop
you should see something like this...
~ # grep -e 'ro.build.product' -e 'ro.product.device' /system/build.prop
grep -e 'ro.build.product' -e 'ro.product.device' /system/build.prop
ro.product.device=endeavoru
# ro.build.product is obsolete; use ro.product.device
ro.build.product=endeavoru

koppen_kf said:
Hi!
I have the International Version of the HTC One X.
Today I tried to install Paranoid Android. Originally, I had installed the version 1.99. I did this successfully. However, I saw that 2.00 is available. So I tried to reflash a new rom. I got an error as follows:
assert failed: getprop("ro.product.device") == "endeavoru" || getprop("ro.build.product") == "endeavoru"
I tried a clean rewipe first using a nandriod backup of the stock sense UI, but I couldn't start up after. I then proceed to use the RUU for a complete wipe back to stock. This worked.
When I tried installing again, both 1.99 and 2.00 are giving me the assert failed error.
Would appreciate assistance.
Thanks!
Click to expand...
Click to collapse
see this (ro.product.device) & this (ro.build.product) this is reading from your build.prop file. make sure those two lines are outputting endeavoru. Maybe some dev changed it to there Rom name or some ****. Also don't go deleting assert checks in that script unless you want a very nice & shiny paper weight

As mentioned, my nandroid backup of stock rom is not working (it'll just hang at HTC One X boot screen).
I can't seem to access ADB on recovery mode (I'm on CWM 5.8.2.4).
I can't mount USB either.
So it seems that RUU is the next best solution for me to recheck what getvar is really printing.
What baffles me is that I clearly managed to install Paranoid Android 1.99 once, it was only when I tried 2.00 did this assert failed error occur. After which, both 1.99 and 2.00 throw the assert failed errors.
I've dragged out this round of flashing too long and now its under 30%, so I'm just charging the phone in recovery mode. Do I have any other options for now?

that is an extremely old cwm, why don't you flash 5.8.4.0?
5.8.4.0 has fixes for charging in recovery, adb and usb mounting.

Do you have any custom themes installed via theme manager?

I looked more into the issue, it looks s though ClockworkMod 5.8.2.4 had a typo in the build.prop and that is why your assert is failed.
ro.build.product=endeavouru
ro.product.device=endeavouru
they should be
ro.build.product=endeavoru
ro.product.device=endeavoru
The solution is to go into fastboot mode and flash 5.8.4.0 cwm

Thanks!
I've flashed the new CWM and it worked!
The thing I don't understand is how my first install even worked in the first place.
Thanks all

the older paranoidandroid may have had that script checking either endeavoru or endeavouru. Glad it is working.

Squirrels said:
I looked more into the issue, it looks s though ClockworkMod 5.8.2.4 had a typo in the build.prop and that is why your assert is failed.
ro.build.product=endeavouru
ro.product.device=endeavouru
they should be
ro.build.product=endeavoru
ro.product.device=endeavoru
The solution is to go into fastboot mode and flash 5.8.4.0 cwm
Click to expand...
Click to collapse
Worked Thanks.... :good::good::good::good:

[Q] fastboot karnal problem

hi
i flash a system image in the boot partition using FlashTool progrem
And I changed kernel
Only now I realized I needed to use fastboot and command prompt to flash the img file to the system partition.
And when I do that it tells me "flash operation complete"
But the kernel is not replaced!!??!!
i try QuikIMG-0.2-beta and the fastboot and command prompt to flash the img file to the system partition and this didnt work....
what i can do?
tnx!!!

mmoti6 said:
hi
i flash a system image in the boot partition using FlashTool progrem
And I changed kernel
Only now I realized I needed to use fastboot and command prompt to flash the img file to the system partition.
And when I do that it tells me "flash operation complete"
But the kernel is not replaced!!??!!
i try QuikIMG-0.2-beta and the fastboot and command prompt to flash the img file to the system partition and this didnt work....
what i can do?
tnx!!!
Click to expand...
Click to collapse
Have you tried Flashing Stock Firmware?
Here is a Thread where you can download Official Stock Firmwares for the Xperia Play(Post #2):
Xperia Play Index - ROM'S, FIRMWARE, KERNEL'S, GUIDE'S, THEMES, MOD'S

mmoti6 said:
hi
i flash a system image in the boot partition using FlashTool progrem
And I changed kernel
Only now I realized I needed to use fastboot and command prompt to flash the img file to the system partition.
And when I do that it tells me "flash operation complete"
But the kernel is not replaced!!??!!
i try QuikIMG-0.2-beta and the fastboot and command prompt to flash the img file to the system partition and this didnt work....
what i can do?
tnx!!!
Click to expand...
Click to collapse
TheScriptKitty said:
Have you tried Flashing Stock Firmware?
Here is a Thread where you can download Official Stock Firmwares for the Xperia Play(Post #2):
Xperia Play Index - ROM'S, FIRMWARE, KERNEL'S, GUIDE'S, THEMES, MOD'S
Click to expand...
Click to collapse
i download r800a_N.A+Generic_4.0.A.2.368.rar ---- r800a stock firmware
and i try QuikIMG-0.2-beta and the fastboot and command prompt to flash the img file to the system partition and this didnt work....
And when I do that it tells me "flash operation complete" but still he didnt work....
in FlashTool is tell me
"FAILED (remote: Image won't fit, partition too small!)"
help plizz

mmoti6 said:
i download r800a_N.A+Generic_4.0.A.2.368.rar ---- r800a stock firmware
and i try QuikIMG-0.2-beta and the fastboot and command prompt to flash the img file to the system partition and this didnt work....
And when I do that it tells me "flash operation complete" but still he didnt work....
in FlashTool is tell me
"FAILED (remote: Image won't fit, partition too small!)"
help plizz
Click to expand...
Click to collapse
Are you trying to Flash it via Fastboot Mode?
You have to change the File Extension from .rar to .ftf , and then Flash it via FLASH MODE (NOT Fastboot Mode) in FlashTool.

pliz help
TheScriptKitty said:
Are you trying to Flash it via Fastboot Mode?
You have to change the File Extension from .rar to .ftf , and then Flash it via FLASH MODE (NOT Fastboot Mode) in FlashTool.
Click to expand...
Click to collapse
ok i change to Official Stock Firmwares for the Xperia Play (i think i chose the right one...)
but still tells me "flash operation complete"
but he didnt change the karnal
NexPlay_rk1_GSM/semc-kernel-msm7x30-jellybean
pliz help....
And model of cell phone is R800a
And he shows me "INFO - Current device : R800i - CB5A1GM5GZ - 1247-8563_R13D - 1245-8821_4.0.2.A.0.79 - VFE-1-8_4.0.2.A.0.79"
y?

mmoti6 said:
ok i change to Official Stock Firmwares for the Xperia Play (i think i chose the right one...)
but still tells me "flash operation complete"
but he didnt change the karnal
NexPlay_rk1_GSM/semc-kernel-msm7x30-jellybean
pliz help....
And model of cell phone is R800a
And he shows me "INFO - Current device : R800i - CB5A1GM5GZ - 1247-8563_R13D - 1245-8821_4.0.2.A.0.79 - VFE-1-8_4.0.2.A.0.79"
y?
Click to expand...
Click to collapse
If you Flashed the Stock Firmware for your phone and you say that the kernel has not changed how are you able to see what kernel you have if the phone should not be able to boot(Because it would be like trying to use a Costume ICS kernel on the Stock GB ROM)???

help pliz
TheScriptKitty said:
If you Flashed the Stock Firmware for your phone and you say that the kernel has not changed how are you able to see what kernel you have if the phone should not be able to boot(Because it would be like trying to use a Costume ICS kernel on the Stock GB ROM)???
Click to expand...
Click to collapse
if i Flashed the Stock Firmware for my phone the phone shows me this
(sony logo in boot screen)
and the phone is good and working
but then i Flashed a kernel like this
(LuPuS logo in boot screen)
but it still shows me this
(sony logo in boot screen)
and the phone is stuck on it
y?

mmoti6 said:
if i Flashed the Stock Firmware for my phone the phone shows me this
(sony logo in boot screen)
and the phone is good and working
but then i Flashed a kernel like this
(LuPuS logo in boot screen)
but it still shows me this
(sony logo in boot screen)
and the phone is stuck on it
y?
Click to expand...
Click to collapse
Have you flashed a Custom ROM?
If you have, please specify exactly what version of the Lupus Kernel and what ROM you are using.
And if you have not flashed a Custom ROM, as I said before trying to use a Custom Kernel on the Stock ROM will not work(it will not boot in most cases), you need to Flash a Custom ROM that is compatible with the Lupus Kernel you are using.

TheScriptKitty said:
Have you flashed a Custom ROM?
If you have, please specify exactly what version of the Lupus Kernel and what ROM you are using.
And if you have not flashed a Custom ROM, as I said before trying to use a Custom Kernel on the Stock ROM will not work(it will not boot in most cases), you need to Flash a Custom ROM that is compatible with the Lupus Kernel you are using.
Click to expand...
Click to collapse
you can recmmnded on a Firmwar?
i use to root the phone whit superonclick and this is what i get:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$
export TEMPRANDOM=65947;export PS1=END:$TEMPRANDOM;getprop ro.build.version.release
export PS1=""
$ 2.2.1
END:65947
export TEMPRANDOM=87695;export PS1=END:$TEMPRANDOM;getprop ro.product.manufacturer
export PS1=""
LGE
END:87695
export TEMPRANDOM=35445;export PS1=END:$TEMPRANDOM;getprop ro.product.model
export PS1=""
LG-P500h
END:35445
export TEMPRANDOM=50395;export PS1=END:$TEMPRANDOM;getprop ro.build.version.incremental
export PS1=""
eng.donghyun.seo.20110215.151731
END:50395
export TEMPRANDOM=25205;export PS1=END:$TEMPRANDOM;ls -l /system/xbin/su
export PS1=""
/system/xbin/su: No such file or directory
END:25205
export TEMPRANDOM=29466;export PS1=END:$TEMPRANDOM;ls -l /system/bin/su
export PS1=""
-rwsr-sr-x root root 380532 2012-08-07 13:01 su
END:29466
export TEMPRANDOM=48004;export PS1=END:$TEMPRANDOM;chmod 755 /data/local/tmp/busybox
export PS1=""
END:48004
export TEMPRANDOM=92630;export PS1=END:$TEMPRANDOM;rm /data/local/tmp/boomsh
export PS1=""
rm failed for /data/local/tmp/boomsh, No such file or directory
END:92630
export TEMPRANDOM=17806;export PS1=END:$TEMPRANDOM;rm /data/local/tmp/sh
export PS1=""
rm failed for /data/local/tmp/sh, No such file or directory
END:17806
export TEMPRANDOM=60041;export PS1=END:$TEMPRANDOM;chmod 700 /data/local/tmp/zergRush
export PS1=""
Unable to chmod /data/local/tmp/zergRush: No such file or directory
END:60041
export TEMPRANDOM=98014;export PS1=END:$TEMPRANDOM;cd /data/local/tmp/
export PS1=""
END:98014
export TEMPRANDOM=32459;export PS1=END:$TEMPRANDOM;./zergRush
export PS1=""
./zergRush: not found
END:32459
Click to expand...
Click to collapse
how i install the zergRush?
tnx
editing
i Flashing Stock Firmware r800i 4.0.2.A.0.62 firmware (but my phone is r800a...)
i use to root the phone whit superonclick and this is what i get:
$TEMPRANDOM;getprop ro.build.version.release
2.3.4
END:97116export PS1=""
export TEMPRANDOM=37017;export PS1=END:$TEMPRANDOM;getprop ro.product.manufacturer
Sony Ericsson
END:37017export PS1=""
export TEMPRANDOM=31785;export PS1=END:$TEMPRANDOM;getprop ro.product.model
R800i
END:31785export PS1=""
export TEMPRANDOM=65498;export PS1=END:$TEMPRANDOM;getprop ro.build.version.incremental
wf_v3w
END:65498export PS1=""
export TEMPRANDOM=13472;export PS1=END:$TEMPRANDOM;ls -l /system/xbin/su
/system/xbin/su: No such file or directory
END:13472export PS1=""
export TEMPRANDOM=80897;export PS1=END:$TEMPRANDOM;ls -l /system/bin/su
/system/bin/su: No such file or directory
END:80897export PS1=""
export TEMPRANDOM=71628;export PS1=END:$TEMPRANDOM;chmod 755 /data/local/tmp/busybox
END:71628export PS1=""
export TEMPRANDOM=96072;export PS1=END:$TEMPRANDOM;rm /data/local/tmp/boomsh
rm failed for /data/local/tmp/boomsh, No such file or directory
END:96072export PS1=""
export TEMPRANDOM=66092;export PS1=END:$TEMPRANDOM;rm /data/local/tmp/sh
rm failed for /data/local/tmp/sh, No such file or directory
END:66092export PS1=""
export TEMPRANDOM=93376;export PS1=END:$TEMPRANDOM;chmod 700 /data/local/tmp/zergRush
Unable to chmod /data/local/tmp/zergRush: No such file or directory
END:93376export PS1=""
export TEMPRANDOM=27821;export PS1=END:$TEMPRANDOM;cd /data/local/tmp/
END:27821export PS1=""
export TEMPRANDOM=97862;export PS1=END:$TEMPRANDOM;./zergRush
./zergRush: not found
END:97862export PS1=""
Click to expand...
Click to collapse
y?

mmoti6 said:
you can recmmnded on a Firmwar?
i use to root the phone whit superonclick and this is what i get:
how i install the zergRush?
tnx
editing
i Flashing Stock Firmware r800i 4.0.2.A.0.62 firmware (but my phone is r800a...)
i use to root the phone whit superonclick and this is what i get:
y?
Click to expand...
Click to collapse
Okay first of all, I don't think you understand the difference between a ROM, Kernel, and Firmware so I'll explain that first:
A ROM (In Android) is basically like the OS, it contains all the software you see and use on the phone. The kernel would be what connects the ROM (the OS) with the phone's hardware. A firmware would be a combination of both a Kernel and a ROM and its most commonly used to describe the Original ROM and Kernel of the phone (Stock Firmware). Please confirm that you Understand.
Now, I have never used SuperOneclick to root the Xperia Play so I really can't tell you what you are doing wrong. If you want, use zergRush. You don't have to install it, here is the basic procedure:
download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME.bat"
read and follow the instructions on the screen!
[04/Jan][ROOTING/UNROOTING] Xperia 2011 Easy Rooting Toolkit [v4.0](zergRush Exploit)
I don't think you will have any problems if you Flashed a R800i Firmware on a R800a, but just to be sure use Firmware made for your phone.
And if what you mean by "what Firmware I recommend" is what ROM do I recommend, here it is:
If you want Gingerbread(Android 2.3): Gin2KitKat
If you want ICS(Android 4.0): Xperia Play Z
If you want Jellybean(Android 4.1.2): Racing SPEED EDITION EOL or Super Lite Jelly Bean
For each ROM you have to install the Kernel it tells you to(Read instructions). I also want to add that their is no such thing as a best ROM, each ROM has its Pros and Cons, and what might appeal to me might not to you. I would recommend for you to try different ROMs and see what suits you.
And last, Please Click on the Thanks Button
.
.

TheScriptKitty said:
Okay first of all, I don't think you understand the difference between a ROM, Kernel, and Firmware so I'll explain that first:
A ROM (In Android) is basically like the OS, it contains all the software you see and use on the phone. The kernel would be what connects the ROM (the OS) with the phone's hardware. A firmware would be a combination of both a Kernel and a ROM and its most commonly used to describe the Original ROM and Kernel of the phone (Stock Firmware). Please confirm that you Understand.
Now, I have never used SuperOneclick to root the Xperia Play so I really can't tell you what you are doing wrong. If you want, use zergRush. You don't have to install it, here is the basic procedure:
download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME.bat"
read and follow the instructions on the screen!
[04/Jan][ROOTING/UNROOTING] Xperia 2011 Easy Rooting Toolkit [v4.0](zergRush Exploit)
I don't think you will have any problems if you Flashed a R800i Firmware on a R800a, but just to be sure use Firmware made for your phone.
And if what you mean by "what Firmware I recommend" is what ROM do I recommend, here it is:
If you want Gingerbread(Android 2.3): Gin2KitKat
If you want ICS(Android 4.0): Xperia Play Z
If you want Jellybean(Android 4.1.2): Racing SPEED EDITION EOL or Super Lite Jelly Bean
For each ROM you have to install the Kernel it tells you to(Read instructions). I also want to add that their is no such thing as a best ROM, each ROM has its Pros and Cons, and what might appeal to me might not to you. I would recommend for you to try different ROMs and see what suits you.
And last, Please Click on the Thanks Button
.
.
Click to expand...
Click to collapse
ok
new i get this
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
1407 KB/s (23060 bytes in 0.016s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2949 KB/s (1075144 bytes in 0.356s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
107 KB/s (439 bytes in 0.004s)
df: /mnt/secure/asec: Permission denied
export: 65964: bad variable name
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
y?

mmoti6 said:
ok
new i get this
y?
Click to expand...
Click to collapse
It look like it failed to Root the device at the beginning, so it fail to do the rest of the stuff.
Are you sure you did all this?:
Make sure u have installed adb drivers for ur device
Enable "USB DEBUGGING" from (Menu\Settings\Applications\Development)
Enable "UNKNOWN SOURCES" from (Menu\Settings\Applications)
[OPTIONAL]Increase screen timeout to 10 minutes
Connect USB cable to PHONE and then connect to PC
Skip "PC Companion Software" prompt on device

TheScriptKitty said:
It look like it failed to Root the device at the beginning, so it fail to do the rest of the stuff.
Are you sure you did all this?:
Make sure u have installed adb drivers for ur device
Enable "USB DEBUGGING" from (Menu\Settings\Applications\Development)
Enable "UNKNOWN SOURCES" from (Menu\Settings\Applications)
[OPTIONAL]Increase screen timeout to 10 minutes
Connect USB cable to PHONE and then connect to PC
Skip "PC Companion Software" prompt on device
Click to expand...
Click to collapse
yes i am wure...

Zergrush can't root .62 (and above) firmware. Only .42 and bellow

Bakisha said:
Zergrush can't root .62 (and above) firmware. Only .42 and bellow
Click to expand...
Click to collapse
but onli the North America firmware is 42 and i am not from North America...
what i can do?

mmoti6 said:
but onli the North America firmware is 42 and i am not from North America...
what i can do?
Click to expand...
Click to collapse
It doesn't matter, it works fine with it.

TheScriptKitty said:
It doesn't matter, it works fine with it.
Click to expand...
Click to collapse
i dont see the firmware in the flashtool tool
i change it to ftf and i have 2 firmware
1.R800a_2.3.4_North America Generic (1)
2.R800a_4.0.2.A.0.42_North America
i cant see them....
you can recmmnded what to do?
i must to flash anther firmware ?
or i can only to flashe rom and carnal to get 42 or bellow firmware?

mmoti6 said:
i change it to ftf and i have 2 firmware
Click to expand...
Click to collapse
I recommend unpacking those two rar files to get ftf files, not renaming them from rar to ftf

Bakisha said:
I recommend unpacking those two rar files to get ftf files, not renaming them from rar to ftf
Click to expand...
Click to collapse
i still dont show tham on the flash tool
1.R800a_2.3.4_North America Generic (1) - i unpacking to ftf file
2.R800a_4.0.2.A.0.42_North America - i renaming from rar to ftf
i cant see them....
you can recmmnded what to do?
i must to flash anther firmware ?
or i can only to flashe rom and carnal to get 42 or bellow firmware?
tnx

Use latest version of flashtool http://flashtool.net
Find ftf firmware files at http://forum.xda-developers.com/showthread.php?t=2184897
Make sure you download correct firmware for your model (r800i/a/x)
The easiest way to get root on stock r800i
1: flash .42 firmware and root it with zerg-rush
2: flash .79 firmware and flash doomlord gb kernel
Sent from my R800i using XDA Free mobile app

Stuck in Recovery Mode....!!

Hi Xda This is owais khatri here,,
I haved watch whole xda but still not found help...
I have download all bin total.... 9 bins from xda and 2 from Amazon web site...
i have Adb and fastboot whole correct and recognze device,
bin download most of them is Cant read bin and 2 are running but at end they show (( assert failed: getprop ("ro.product.device") == "kodiak" || getprop ("ro.build.device") e:error in /tmp/update.zip (status 7) installation aborted ))
HURTINGGG..
plz help meeee,,,,

owais khatri said:
(( assert failed: getprop ("ro.product.device") == "kodiak" || getprop ("ro.build.device") e:error in /tmp/update.zip (status 7) installation aborted ))
Click to expand...
Click to collapse
Put the BIN file in the same folder where your ADB files are.
Use the exact name of the BIN file in the command line or rename it to a short & simple name, like your example above (e.g. "update.bin")
(Don't use ZIP files if you work with the official Amazon recovery, it can only process BIN files.)
Did you modify the build.prop on your device? What was the last OS version you had installed?

stuck at fire system recovery
Bingo Bronson said:
Put the BIN file in the same folder where your ADB files are.
Use the exact name of the BIN file in the command line or rename it to a short & simple name, like your example above (e.g. "update.bin")
(Don't use ZIP files if you work with the official Amazon recovery, it can only process BIN files.)
Did you modify the build.prop on your device? What was the last OS version you had installed?
Click to expand...
Click to collapse
i had same problem please someone who help me

owais khatri said:
Hi Xda This is owais khatri here,,
I haved watch whole xda but still not found help...
I have download all bin total.... 9 bins from xda and 2 from Amazon web site...
i have Adb and fastboot whole correct and recognze device,
bin download most of them is Cant read bin and 2 are running but at end they show (( assert failed: getprop ("ro.product.device") == "kodiak" || getprop ("ro.build.device") e:error in /tmp/update.zip (status 7) installation aborted ))
HURTINGGG..
plz help meeee,,,,
Click to expand...
Click to collapse
Do you still have Safestrap installed? What happens when you try to reboot?

owais khatri said:
Hi Xda This is owais khatri here,,
I haved watch whole xda but still not found help...
I have download all bin total.... 9 bins from xda and 2 from Amazon web site...
i have Adb and fastboot whole correct and recognze device,
bin download most of them is Cant read bin and 2 are running but at end they show (( assert failed: getprop ("ro.product.device") == "kodiak" || getprop ("ro.build.device") e:error in /tmp/update.zip (status 7) installation aborted ))
HURTINGGG..
plz help meeee,,,,
Click to expand...
Click to collapse
How are you connecting to the device? In Safestrap or Amazon Recovery? You should be able to sideload the Amazon official update via the Amazon Recovery no matter what condition your build.prop is in.
Download the official Amazon update bin for your device
Boot into Amazon Recovery by holding down Volume Down+Power
Select "Sideload update from ADB"
Run adb sideload <name of update file>.bin
Recommend you do a factory reset afterwards to be safe
Assuming all is well you can reroot now and go back to whatever custom image you desire

I have Amazon fire phone but it continuesly going on recovery mode after update and resetting