[Q] Can I unbrand X10 with my build.prop - XPERIA X10 Q&A, Help & Troubleshooting

My wife and I have the same phone from Vodafone. I have unbranded my phone months ago with SEUS. She hasn't and she still has 024! Now I have read about replacing the build.prop. Can I unbrand her phone with my build.prop? I know I have to root her phone, before I can do so. Then rename her build.prop to build.prop.old, put my in her folder and reboot?
Or is this too easy?

Yes you can
# Push your file to your wifes phone's sdcard: "adb push build.prop /sdcard/build.prop"
# Then: "adb shell" and type "su", grant the root access on her phone and then "rm /system/build.prop" and "./busybox cp /sdcard/build.prop /system/"
# Reboot
# Lastly use the Sony Ericsson Update Service to install the new firmware
Click to expand...
Click to collapse

olafski72 said:
My wife and I have the same phone from Vodafone. I have unbranded my phone months ago with SEUS. She hasn't and she still has 024! Now I have read about replacing the build.prop. Can I unbrand her phone with my build.prop? I know I have to root her phone, before I can do so. Then rename her build.prop to build.prop.old, put my in her folder and reboot?
Or is this too easy?
Click to expand...
Click to collapse
I dont think so. I tried same think once, but came up with exclamation mark...u can still give it a shot...back up the data anyways before attempting..

Nikhil_007 said:
I dont think so. I tried same think once, but came up with exclamation mark...u can still give it a shot...back up the data anyways before attempting..
Click to expand...
Click to collapse
I tried in another post, and I got problems too,
after copying the file try in root mode
Code:
chmod 644 build.prop
to set up the same permits as the file before, give it a try and tell me, I will try again this method with a scandinavian build.prop
One question
Scandinavian
Brand: customized
is a good ROM to have? or is still attached to an operator?

Run steps 1-5 HERE, then run seus which will update to 026, then use X10Root 1.0.8 to root.

Is the build.prop method not working at all?
Sent from my x10 using swype

XperiaX10iUser said:
Run steps 1-5 HERE, then run seus which will update to 026, then use X10Root 1.0.8 to root.
Click to expand...
Click to collapse
I read this works, but the .prop file seems to be easier. Unfortunately, it is my wife's phone, so I cannot just experiment with it. So, to just try the .prop method....
Maybe when 2.1 is out and she sees it at my phone and she wants it badly

olafski72 said:
I read this works, but the .prop file seems to be easier. Unfortunately, it is my wife's phone, so I cannot just experiment with it. So, to just try the .prop method....
Maybe when 2.1 is out and she sees it at my phone and she wants it badly
Click to expand...
Click to collapse
let me know if you succeed I also need to do the same with mine

What if it fails? Can I repair this with PC Companion then?

olafski72 said:
What if it fails? Can I repair this with PC Companion then?
Click to expand...
Click to collapse
I tried twice, and I got the yellow mark the second time, I run the SEUS and I got back my 024 branded vodafone. Just back up everything with titanium and you wont loose anything.
this is the code I run
Code:
adb push build.prop /sdcard/build.prop
adb shell
su
busybox cp /system/build.prop /sdcard/build.prop.old
rm /system/build.prop
busybox cp /sdcard/build.prop /system/
chmod 644 build.prop
I also run
Code:
ls -l build.prop
between the erase and the copy to check it effectively copied the file with the right permit
I could probably fail due to the build.prob that I use from one user, maybe you get better luck, I will try some days later with the scandinavian customized from a friend's X10 phone in a few days.

Related

Deleted build.prop and reboted phone

I got the notice on my Gf's phone that I need to update. after it failed I tried a few things among them replacing the build.prop
Unfortunatilly I removed the build.prop and did not secussfully replace it. I can still use adb but if i try to push the build.prop to the /system folder it says premission denied read only.
I tryed to grand superuser permissions but after the su command the super user permission dialog doesnot come up on my phone. atcually nothing shwes up on the phone but the top information pannel which i can bring down to view notifications. but I cannot acess anything else.
Also the resolution looks to be about half of what it is suposed to be.
PLEASE HELP, my girlfriend is going to have my nutz, and my nexus one.
EDIT:
used the exploit from the first post in this section. then after the ./exploit command I was able to load up the build.prop
Does the $ change to a # when you type su?
porcupineadvocate said:
Does the $ change to a # when you type su?
Click to expand...
Click to collapse
sorry i have not tried using exploid rooting method . why dont you use universal androot. its easy and if you need build.prop then i have attached for you and also universal androot.

New Rooting method for 2.1 | updated for 2.0.2.A.0.24 | 9/01/2011

Here comes the latest rooting method that works with 2.0.2.A.0.24 firmware.
Credits to Scotty2 for his psneuter exploit!
1. Download and unpack rootme.tar.bz2
2. Execute ./rootme (linux) or rootme.bat (windows)
3. Done.
---
You may also want to try SuperOneClickv1.5.5-ShortFuse.zip (modified by batman_112 to use the latest exploit).
Cheers,
z
Stop for me at Point 4)
I got back
./ratc: Permission denied
Click to expand...
Click to collapse
after
./ratc
i get ... permission denided
Wow, actually it seems that copying files with adb push via script messes thing up I corrected the instructions, so now it will work for you, but need to copy the files manually.
zdzihu said:
Wow, actually it seems that copying files with adb push via script messes thing up I corrected the instructions, so now it will work for you, but need to copy the files manually.
Click to expand...
Click to collapse
Your link is broken
Try now, I got rid of installation scripts
EDIT: Now it works flawlessly. I still have no clue why copying files with .bat file messes everything up, but manual copying does the job.
why the superone reach the root sometimes so slow?
your method uses the same exploit, and works at first try
check the files plz: Invalid or Deleted File
can't download the ratc-pack --> Invalid or Deleted File
please reup - THX
EDIT: Link is OK now --> THX
Link is OK. Downloading at the moment.
Tried it manually (as described)...
But same problem... :-(
UserX10 said:
Tried it manually (as described)...
But same problem... :-(
Click to expand...
Click to collapse
I just reflashed my phone and it worked for me at 1st attempt.
Could you please got rid of the old files and retry from the beggining?
Cheers!
meta96 said:
after
./ratc
i get ... permission denided
Click to expand...
Click to collapse
Same thing for me
:-( Same Problem
I flashed my X10 with nordic FW and tried it again Step by Step... but "permission denied"... even if i remove and make the tmp directory as described...
Ok, last thing to try... After you copy the files, go with:
Code:
adb shell
chmod 777 /data/local/tmp/*
I added some screenshots to show how the process works for me.
is this a full root? i mean, is root+shell root?
zdzihu said:
Hi guys, I've noticed some people still can't get their phones rooted with SuperOneClick method. So do I, never managed to get it working Here is a simple method of rooting, using the same exploit (rageagainstthecage - credits to author). This is quick and 100% guaranteed to work but I'd rather recommend it to advanced users.
1. Install Android Terminal Emulator from the market http://bit.ly/9B46Nl
2. Download and unpack http://www.mediafire.com/?s0428zxc7n50i28
3. Plug in the phone (usb debugging mode), copy the following files with adb and change permissions:
Code:
adb push ratc /data/local/tmp/ratc
adb push busybox /data/local/tmp/busybox
adb push su /data/local/tmp/su
adb push rootme /data/local/tmp/rootme
adb push superuser.apk /data/local/tmp/superuser.apk
adb shell
chmod /data/local/tmp/*
4. Start Terminal Emulator on your phone and issue those commands:
Code:
cd /data/local/tmp
./ratc
5. Exit out of Terminal Emulator using BACK button.
6. Start any other application and exit out of it using BACK button.
7. Start Terminal Emulator again - note that you're running it as root (#)
8. Issue those commands:
Code:
cd /data/local/tmp
./rootme
Your phone will reboot - and it's done. I suggest installing Busybox from the Market. Hope it helps.
Cheers!
EDIT: Fixed.
Click to expand...
Click to collapse
Finally I was able to root my phone
just one correction, you got to use chmod 777 /data/local/tmp/*
it was not allowing to root otherwise
i kept breaking my head using the "simple" SuperOneCLick but could not show my rage against the machine
thank you for explaining this process for Root.
zdzihu said:
Ok, last thing to try... After you copy the files, go with:
Code:
adb shell
cd /data/local/tmp
chmod 777 *
I added some screenshots to show how the process works for me.
Click to expand...
Click to collapse
chmod 777 *
did it. thanx. btw like your oldstyle-skills
Just saw this thread and wanted to root my phone also...I downloaded the files provided in the first post and extracted onto my PC. When I tried running the adb application, I only get a command window only for a split second and then it disappears. Am I doing something wrong?
Everything works fine until the final step where I write ./rootme in the emulator.
Before the phone reboots, it says something right after, something about superuser.apk.
Once the phone is back on the emulator goes back to $. As well as not being able to download Busybox.
Appreciate your efforts
EDIT: No worries, I managed to get root using SuperOneClick (finally!). It was rather sketchy, would've preferred your way tbh.

Easy way to install CWM or xRecovery

Here is what I believe is a simple way of rooting and installing CWM for Windows.
I have bricked my phone many times now and used SEUS to get it back to 2.1.1.A.0.6 and had to go through the process of rooting and installing CWM again. Here is what I have found.
Download SuperOneClick to a folder, e.g. C:\SuperOneClick
Create a sub-folder under this folder, e.g. C:\SuperOneClick\CWM
Download your preferred version of CWM or xRecovery (should be the 3 files "busybox", "chargemon", "recovery.tar")
Copy these 3 files into the sub-folder you created, e.g. C:\SuperOneClick\CWM
Copy the code snippet below and save as INSTALL.BAT in the sub-folder
Reflash your phone with SEUS to get back to plain 2.1.1.A.0.6
Reboot and set USB debugging mode
Run SuperOneClick and click Root - do not reboot
Once Root has finished click Shell Root - do not reboot
Open a command window and enter CD C:\SuperOneClick\CWM
Run INSTALL.BAT - this will reboot the phone at the end
Press BACK key on the phone at the Sony Ericcson text - you should get into CWM
The benefit of the above is that if you keep the files in the folder above you can repeat from step 6 very easily.
Code:
@echo off
echo.
echo.1) Run SuperOneClick
echo. a) Click Root - do not reboot
echo. b) Click Shell Root - do not reboot
echo.2) Press any key in this window to install CWM - phone will reboot
echo.
pause
..\adb devices
..\adb remount
..\adb push busybox /system/bin
..\adb push chargemon /system/bin
..\adb push recovery.tar /system/bin
..\adb shell chmod 755 /system/bin/busybox
..\adb shell chmod 755 /system/bin/chargemon
..\adb shell chmod 755 /system/bin/recovery.tar
..\adb reboot
This technique does not require installing BusyBox from the Market, setting permissions via Root Explorer or anything like that. It just uses SuperOneClick and a small script using the ADB program in the SuperOneClick folder.
I got SuperOneClick from here http://forum.xda-developers.com/attachment.php?attachmentid=515017&d=1297434892 (from thread http://forum.xda-developers.com/showthread.php?t=950324)
I got 2 files for CWM "chargemon" and "recovery.tar" from the ZIP file here http://forum.xda-developers.com/attachment.php?attachmentid=627115&d=1308237137 (from thread http://forum.xda-developers.com/showthread.php?t=1106146)
I got busybox from the ZIP file here http://forum.xda-developers.com/attachment.php?attachmentid=515016&d=1297434832 (from thread http://forum.xda-developers.com/showthread.php?t=950324)
I hope some people find this useful and that I haven't offended the guys where I got the files from (I did list your threads as well as link to your files so others can see all the useful posts in your threads).
Darren
DarrenNewsgroup said:
Here is what I believe is a simple way of rooting and installing CWM for Windows.
I have bricked my phone many times now and used SEUS to get it back to 2.1.1.A.0.6 and had to go through the process of rooting and installing CWM again. Here is what I have found.
Download SuperOneClick to a folder, e.g. C:\SuperOneClick
Create a sub-folder under this folder, e.g. C:\SuperOneClick\CWM
Download your preferred version of CWM or xRecovery (should be the 3 files "busybox", "chargemon", "recovery.tar")
Copy these 3 files into the sub-folder you created, e.g. C:\SuperOneClick\CWM
Copy the code snippet below and save as INSTALL.BAT in the sub-folder
Reflash your phone with SEUS to get back to plain 2.1.1.A.0.6
Reboot and set USB debugging mode
Run SuperOneClick and click Root - do not reboot
Once Root has finished click Shell Root - do not reboot
Open a command window and enter CD C:\SuperOneClick\CWM
Run INSTALL.BAT - this will reboot the phone at the end
Press BACK key on the phone at the Sony Ericcson text - you should get into CWM
The benefit of the above is that if you keep the files in the folder above you can repeat from step 6 very easily.
Code:
@echo off
echo.
echo.1) Run SuperOneClick
echo. a) Click Root - do not reboot
echo. b) Click Shell Root - do not reboot
echo.2) Press any key in this window to install CWM - phone will reboot
echo.
pause
..\adb devices
..\adb remount
..\adb push busybox /system/bin
..\adb push chargemon /system/bin
..\adb push recovery.tar /system/bin
..\adb shell chmod 755 /system/bin/busybox
..\adb shell chmod 755 /system/bin/chargemon
..\adb shell chmod 755 /system/bin/recovery.tar
..\adb reboot
This technique does not require installing BusyBox from the Market, setting permissions via Root Explorer or anything like that. It just uses SuperOneClick and a small script using the ADB program in the SuperOneClick folder.
I got SuperOneClick from here http://forum.xda-developers.com/attachment.php?attachmentid=515017&d=1297434892 (from thread http://forum.xda-developers.com/showthread.php?t=950324)
I got 2 files for CWM "chargemon" and "recovery.tar" from the ZIP file here http://forum.xda-developers.com/attachment.php?attachmentid=627115&d=1308237137 (from thread http://forum.xda-developers.com/showthread.php?t=1106146)
I got busybox from the ZIP file here http://forum.xda-developers.com/attachment.php?attachmentid=515016&d=1297434832 (from thread http://forum.xda-developers.com/showthread.php?t=950324)
I hope some people find this useful and that I haven't offended the guys where I got the files from (I did list your threads as well as link to your files so others can see all the useful posts in your threads).
Darren
Click to expand...
Click to collapse
Very useful, thank you. I usually spend a couple of minutes re-installing CWMR via a root explorer and it annoys me. This saves 10-20 minutes per restore
It doesn't work..
I bricked my phone 3 timies..
easyyu said:
It doesn't work..
I bricked my phone 3 timies..
Click to expand...
Click to collapse
are you using the same busybox/chargemon and recovery tar that you usually manually install?
svyr said:
are you using the same busybox/chargemon and recovery tar that you usually manually install?
Click to expand...
Click to collapse
I'm used files from first post!
@easyyu
I am sorry that your phone got bricked. Unfortunately you will need to reflash your phone via SEUS. After that check your phone settings are the same as mine below. The 3 files work with my phone settings.
My X10 Mini Pro has the following Settings->About Phone
Model number U20i
Firmware version 2.1-update1
Baseband version M76XX-TSNCJOLYM-53404015
Kernel version 2.6.29 [email protected] #1
Build number 2.1.1.A.0.6​
@svyr
Can you confirm that the above settings are the same as in your phone. This would confirm that the 3 files work for my phone settings.
Darren
DarrenNewsgroup said:
@easyyu
I am sorry that your phone got bricked. Unfortunately you will need to reflash your phone via SEUS. After that check your phone settings are the same as mine below. The 3 files work with my phone settings.
My X10 Mini Pro has the following Settings->About Phone
Model number U20i
Firmware version 2.1-update1
Baseband version M76XX-TSNCJOLYM-53404015
Kernel version 2.6.29 [email protected] #1
Build number 2.1.1.A.0.6​
@svyr
Can you confirm that the above settings are the same as in your phone. This would confirm that the 3 files work for my phone settings.
Darren
Click to expand...
Click to collapse
yes, the above settings from about are the same on my phone.
Hmmm, just reflashed again, ran it and forgot to include busybox/rebooted.
Now it says it can't copy the files/files are read-only and system
Any ideas?
Aside from following the 'do not reboot' (edit: ran superoneclick again and it's all good (re-run the script))
Can't vouch for the busybox/etc set above, but the on I always used still works when installed this way instead of manually.
DarrenNewsgroup said:
@easyyu
I am sorry that your phone got bricked. Unfortunately you will need to reflash your phone via SEUS. After that check your phone settings are the same as mine below. The 3 files work with my phone settings.
My X10 Mini Pro has the following Settings->About Phone
Model number U20i
Firmware version 2.1-update1
Baseband version M76XX-TSNCJOLYM-53404015
Kernel version 2.6.29 [email protected] #1
Build number 2.1.1.A.0.6​
@svyr
Can you confirm that the above settings are the same as in your phone. This would confirm that the 3 files work for my phone settings.
Darren
Click to expand...
Click to collapse
Yes this is the right parameters that you mentioned!
I know how to unbrick my phone..thats not problem!
svyr said:
yes, the above settings from about are the same on my phone.
Hmmm, just reflashed again, ran it and forgot to include busybox/rebooted.
Now it says it can't copy the files/files are read-only and system
Any ideas?
Aside from following the 'do not reboot' (edit: ran superoneclick again and it's all good (re-run the script))
Can't vouch for the busybox/etc set above, but the on I always used still works when installed this way instead of manually.
Click to expand...
Click to collapse
ps here's the one I use. Can't remember where the chargemon is from, but busybox is from xrec mini and CWM is 3.2.0 rc3
I made this, a lot of test give a lot of success, but it's only for mini pro.
CWM recovery by this script easily: http://www.multiupload.com/NDZB8HSIOV
Heres more easy way to install cwm or xrecovery or jit or apps2sd
this is basically quangnhut123's AAIS script, I modified it to add cwm support,
heres the link to download http://www.4shared.com/file/KQf9bym2/AAIS.html
heres the steps to follow
1) Download n extract the aais.zip to /sdcard
2)Open terminal emulator(available on market)
3) enter following commands
su
cd /sdcard/aais
Sh install.sh
Click to expand...
Click to collapse
4) choose ur option and enter the no.
plz note it requires pre rooted device! Only for mini pro! 2.1.1.A.0.6!
Why not try D4rK's recovery installer? It is a one-click installer which lets you choose from xrecovery or CWM...Google search D4 recovery installer
For recovery I made this: http://www.multiupload.com/QE60V6RORD
It works like a charm, thanks to the script xrecovery of mikevhl
Maybe someone could make a script like that for mini ?
D4rK's recovery installer ? I can't find it, even with the google's help...
JBSroid said:
Why not try D4rK's recovery installer? It is a one-click installer which lets you choose from xrecovery or CWM...Google search D4 recovery installer
Click to expand...
Click to collapse
when i tried it, it didn't work on sdk 7 or was it 8...
What do you mean by sdk 7 or sdk 8? Someone mentioned sdk numbers before. Is this something to do with downloading the complete android stuff onto my windows pc just to get the adb command? This is why I thought using the adb in SuperOneClick was so useful.
Darren
DarrenNewsgroup said:
What do you mean by sdk 7 or sdk 8? Someone mentioned sdk numbers before. Is this something to do with downloading the complete android stuff onto my windows pc just to get the adb command? This is why I thought using the adb in SuperOneClick was so useful.
Darren
Click to expand...
Click to collapse
no, I thought it was about downloading the SDK, but it's actually about the runtimes on the phone... I think (the only way to change them is pretty much by getting a rom with newer ones )

I want to install Xrecovery but...

The thing wont recognize my phone and wont show the options to do xrecovery or any of the other options except for Flash...please help im desperate for a rom
You need to root first.
Here: http://forum.xda-developers.com/showthread.php?t=1196421
Then in flashtool click 'ask root permissions' and have your phone unlocked and accept superuser permissions w/the prompt on your phone. Then you're good to go.
*edit- make sure it is the fixed xrec for 2.3.3. I use a Rom w xrec included so I didn't have to install it & I dont remember if that's the one in flashtool now.
Which firmware version are you on?
I have done that already...i am rooted because I have superuser on my phone. Where do I check firmware?
Sent from my X10i using XDA App
zm4 said:
I have done that already...i am rooted because I have superuser on my phone. Where do I check firmware?
Sent from my X10i using XDA App
Click to expand...
Click to collapse
unzip xrecovery file and copy all files manually to the right places using root explorer then check all boxes on permitions.
reboot and try
How do i do that?
zm4 said:
How do i do that?
Click to expand...
Click to collapse
a very old guide written by me HERE
read "2nd mode" but use xrecovery v3 instead the one linked there
will this work for 2.3.3?
zm4 said:
will this work for 2.3.3?
Click to expand...
Click to collapse
these commands still the same you just need to change (eventually) to the right path.
check the zip structure to see that
HTML:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
dd if=/sdcard/busybox of=/system/bin/busybox
dd if=/sdcard/chargemon of=/system/bin/chargemon
dd if=/sdcard/xrecovery.tar of=/system/bin/xrecovery.tar
reboot
chargemon to \system\bin
charger to \system\bin
sh to \system\xbin
xrecovery.tar to \system\xbin
i dont see any busybox file or anything like that...please help i dun think busybox has been installed...
zm4 said:
i dont see any busybox file or anything like that...please help i dun think busybox has been installed...
Click to expand...
Click to collapse
ok...you have a reading problem kiddin´
Crowds said:
these commands still the same you just need to change (eventually) to the right path.
check the zip structure to see that
Click to expand...
Click to collapse
type this:
HTML:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
dd if=/sdcard/chargemon of=/system/bin/chargemon
dd if=/sdcard/charger of=/system/bin/charger
dd if=/sdcard/sh of=/system/xbin/sh
dd if=/sdcard/xrecovery.tar of=/system/xbin/xrecovery.tar
reboot
this should do it
cheers
where do i get this adb thing?
zm4 said:
where do i get this adb thing?
Click to expand...
Click to collapse
forguet it...
copy all files to sdcard then copy/paste to the right places after that use root explorer and do this ON EVERY FILE YOU COPIED:
HTML:
- Press and hold on each file;
- Check all Permitions on the drop down menu;
- After changes were made save and exit;
- Reboot.
try enter on xrec
*Cannot open for read: No such or directory* wth?
where does meta go?
zm4 said:
where does meta go?
Click to expand...
Click to collapse
Anywhere. Just copy the files I told you to. I didn't referred anything about that, did I?
Sent from my X10 Erenz MIUI 1.9.2 using Tapatalk
Just start all over with flashtool it will work then.
Go to settings then applications, then development, check debug mode.
Start flash tool on your pc and connect the phone
IF the phone is rooted, it should be recognized by flash tool
On flash tool click ask root perm, look at your phone screen, superuser should pop up asking if to give permission, simply choose allow.
Then click recovery on flash tool and wait a sec....
should pop up asking which gingerbread version to use. choose 0.3GB, since its gb version you have.
when you're ready to use xrecovery, restart the phone
as soon as the phone comes on and the first sony ericsson name comes up, keep pressing the back button, xrecovery will come up.
i did both kernel things...but the thing is it won't recognize my device as a rooted device...i have superuser and I have used apps that require root...so i guess the problem is well idk...and thats what i need help with sorting out.
1. Install busybox from market (xrec needs busybox)
2. Give root explorer root acces and mount /system writeable (look in settings of your file explorer)
3. Copy files to right place:
chargemon to /system/bin
charger to /system/bin
sh to /system/xbin
xrecovery.tar to /system/xbin
4. Give above files the right permissions (long touch on file and choose property option):
user > read, write, execute
other > read, execute
group > read, execute

[Q] Is there any way to fool stock recovery to re-flash ota firmware on Xperia S?

I am wondering if anyone knows of a way to take the latest ota zip for the Xperia S, decrypt it, edit the version, repack it, then be able to flash it. Right now it will not let me flash over the current version r5 because it is the same version. I am stuck on the blue wave animation perpetually after screwing up my services.jar. I have no adb access and my only hope is to flash in recovery or wait until the next update comes out...
I was told by a Sony tech yesterday the Jelly Bean update for the Xperia S will not be until January...
EDIT: There is a way to fool the recovery. Does anyone have a modified r5 ota for the Xperia edited for a higher incremented version they could share?
bjanice44 said:
I am wondering if anyone knows of a way to take the latest ota zip for the Xperia S, decrypt it, edit the version, repack it, then be able to flash it. Right now it will not let me flash over the current version r5 because it is the same version. I am stuck on the blue wave animation perpetually after screwing up my services.jar. I have no adb access and my only hope is to flash in recovery or wait until the next update comes out...
I was told by a Sony tech yesterday the Jelly Bean update for the Xperia S will not be until January...
EDIT: There is a way to fool the recovery. Does anyone have a modified r5 ota for the Xperia edited for a higher incremented version they could share?
Click to expand...
Click to collapse
If it is the same as Sony Tab S then you would need to disable the signature check to flash a modded update. To add to the bad news, that is no longer able to work with new recovery (that came with r5, for older tab anyway)
Any chance you can take it in under warrantly?? They may not be able to tell that you messed with it
stifilz said:
If it is the same as Sony Tab S then you would need to disable the signature check to flash a modded update. To add to the bad news, that is no longer able to work with new recovery (that came with r5, for older tab anyway)
Any chance you can take it in under warrantly?? They may not be able to tell that you messed with it
Click to expand...
Click to collapse
Thanks for the response. Yeah I guess I am going to have to send it in or .. the other option is to wait for another update, but not knowing when that will be sucks. The Sony tech told me yesterday (when I called to find out my options..and I can send it in) that the Jelly Bean update is coming in January..So the question is will Sony have another update to ICS before then. Perhaps..
bjanice44 said:
Thanks for the response. Yeah I guess I am going to have to send it in or .. the other option is to wait for another update, but not knowing when that will be sucks. The Sony tech told me yesterday (when I called to find out my options..and I can send it in) that the Jelly Bean update is coming in January..So the question is will Sony have another update to ICS before then. Perhaps..
Click to expand...
Click to collapse
The funny thing is that I know which file is corrupted in the system. Its the services.jar. If only there was a way for me to replace that file....It would boot.
bjanice44 said:
The funny thing is that I know which file is corrupted in the system. Its the services.jar. If only there was a way for me to replace that file....It would boot.
Click to expand...
Click to collapse
Yeh guttered. Can you check if you can get adb shell in recovery??? I know it is late now but this is why the AIO tool changes the incremental to a lower one... So we can flash same update if it turns to custard
stifilz said:
Yeh guttered. Can you check if you can get adb shell in recovery??? I know it is late now but this is why the AIO tool changes the incremental to a lower one... So we can flash same update if it turns to custard
Click to expand...
Click to collapse
No ADB shell. I guess I'll send it in. Watch.. 2 days after I send it in there will be an update..
bjanice44 said:
No ADB shell. I guess I'll send it in. Watch.. 2 days after I send it in there will be an update..
Click to expand...
Click to collapse
Lol. That would be awesome
stifilz said:
If it is the same as Sony Tab S then you would need to disable the signature check to flash a modded update. To add to the bad news, that is no longer able to work with new recovery (that came with r5, for older tab anyway)
Any chance you can take it in under warrantly?? They may not be able to tell that you messed with it
Click to expand...
Click to collapse
stifilz is there really no other way we can revert back to the old Recovery? I mean like finding someone who is still on HC 3.2? and asking him to prepare the needed stuffs like the decrypt one? sorry but im really desperate on fixing the issue my tab is experiencing. and can we still hope for an updated AIO tool that might even work with the latest recovery mode?
mawnstermew said:
stifilz is there really no other way we can revert back to the old Recovery? I mean like finding someone who is still on HC 3.2? and asking him to prepare the needed stuffs like the decrypt one? sorry but im really desperate on fixing the issue my tab is experiencing. and can we still hope for an updated AIO tool that might even work with the latest recovery mode?
Click to expand...
Click to collapse
I have tried to flash 11000 (3.2), 0035(3.2.1), 0042(3.2.1R2), ICS, R1A and NONE of these change the recovery back, i also tied NZ and US files, I was lucky enough to locate US files and had the NZ files saved to my PC. I have looked into AIO tool and read through the code, it runs a certain command in adb shell in recovery (WHICH WE NO LONGER HAVE GRR) so it can not be done ATM.
Maybe there is some file we can change on the tab to enable shell in adb again. From memory shell does not work with non-root devices and when we root we can use adb shell. (Can someone verify this, bad memory lol)
Anyway there could be something I am missing, well hoping anyway
You know you can change the incremental in vendor/vendor.prop to a lower one to flash an OLDER OTA.... Right??
Stifilz
stifilz said:
I have tried to flash 11000 (3.2), 0035(3.2.1), 0042(3.2.1R2), ICS, R1A and NONE of these change the recovery back, i also tied NZ and US files, I was lucky enough to locate US files and had the NZ files saved to my PC. I have looked into AIO tool and read through the code, it runs a certain command in adb shell in recovery (WHICH WE NO LONGER HAVE GRR) so it can not be done ATM.
Maybe there is some file we can change on the tab to enable shell in adb again. From memory shell does not work with non-root devices and when we root we can use adb shell. (Can someone verify this, bad memory lol)
Anyway there could be something I am missing, well hoping anyway
You know you can change the incremental in vendor/vendor.prop to a lower one to flash an OLDER OTA.... Right??
Stifilz
Click to expand...
Click to collapse
-.- sadly i dont know how to change such things. can you please tell me how to do it? ive been looking for ways to downgrade to HC but iim getting prohibit basebrand or SKU version or something like that
mawnstermew said:
-.- sadly i dont know how to change such things. can you please tell me how to do it? ive been looking for ways to downgrade to HC but iim getting prohibit basebrand or SKU version or something like that
Click to expand...
Click to collapse
Use AIO tool. Tweaks and mods then install rescue backdoor
Or
Download root explorer or similar. Open riot exolorer and navigate to vendor folder.
Long click vendor.prop and then select edit with text editor
Change the number to a lower one. Take of the last digit will do.
Click three dots for options and save
All done flash what you like
stifilz said:
Use AIO tool. Tweaks and mods then install rescue backdoor
Or
Download root explorer or similar. Open riot exolorer and navigate to vendor folder.
Long click vendor.prop and then select edit with text editor
Change the number to a lower one. Take of the last digit will do.
Click three dots for options and save
All done flash what you like
Click to expand...
Click to collapse
That one needs a rooted tablet right? Im having troubles rootig my tab even with b4narys script. If I choose to downgrade to 3.2 what no should I chane the las t two digits to?
mawnstermew said:
That one needs a rooted tablet right? Im having troubles rootig my tab even with b4narys script. If I choose to downgrade to 3.2 what no should I chane the las t two digits to?
Click to expand...
Click to collapse
Needs root yes. Just delete the last digit
stifilz said:
Needs root yes. Just delete the last digit
Click to expand...
Click to collapse
thanks! BTW im still able to flash to ICS updates right? BTW im not able to install pre rooted ics if i try to reflash to lower versions due to the inability of AIO tool to decrypt?
From AIO you can decrypt and flash anything lol. Except if you have the r5 recovery it wont work at all
i tried with B4nary's script again but all im getting is the terminal emulator. did you do something with the backupandrestore.apk? cuz i tried installing it and im getting forced close everytime i try to open it.
BTW im on r5 so i wont be able to downgrade? im still stuck at rooting it
mawnstermew said:
i tried with B4nary's script again but all im getting is the terminal emulator. did you do something with the backupandrestore.apk? cuz i tried installing it and im getting forced close everytime i try to open it.
BTW im on r5 so i wont be able to downgrade? im still stuck at rooting it
Click to expand...
Click to collapse
You are typing in /data/local/tmp/onload.sh and then /data/local/tmp/onload2.sh????
You can change incremental after root and flash a ICS or R1A or even HC if you have the file
Stifilz
stifilz said:
You are typing in /data/local/tmp/onload.sh and then /data/local/tmp/onload2.sh????
You can change incremental after root and flash a ICS or R1A or even HC if you have the file
Stifilz
Click to expand...
Click to collapse
i just followed the instrucions stated here http://forum.xda-developers.com/showthread.php?t=1886460 i used the normal mode to unlock but then im getting the on the "mount: permission denied and then i tried using special mode to root and finally after everything was done all that was installed in my tablet is a terminal emulator, some applications were lost in the process such as my avast anti virus and play store.
stifilz said:
You are typing in /data/local/tmp/onload.sh and then /data/local/tmp/onload2.sh????
You can change incremental after root and flash a ICS or R1A or even HC if you have the file
Stifilz
Click to expand...
Click to collapse
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ /data/local/tmp/onload.sh
Unable to chmod /data: Operation not permitted
Unable to chmod /data/local/tmp/mkdevsh: Operation not permitted
failed on 'property' - Permission denied
mkdir failed for property, File exists
link failed Permission denied
link failed Permission denied
rm failed for property, Permission denied
failed on 'property.org' - Permission denied
255|[email protected]:/ $ data/local/tmp/onload2.sh
Unable to chmod /data: Operation not permitted
Unable to chmod /data/local/tmp/remount.sh: Operation not permitted
failed on 'property' - Permission denied
mkdir failed for property, File exists
link failed Permission denied
link failed Permission denied
rm failed for property, Permission denied
failed on 'property.org' - Permission denied
255|[email protected]:/ $
btw stifilz, can you share to me your edited bin4ry's script? the one with the re-signed vpnfaker? it tried signing it but it still doesnt work saying something about the vpnfaker. I think there was something wrong with the way i signed it. it might work if i try to use the one you made.
mawnstermew said:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ /data/local/tmp/onload.sh
Unable to chmod /data: Operation not permitted
Unable to chmod /data/local/tmp/mkdevsh: Operation not permitted
failed on 'property' - Permission denied
mkdir failed for property, File exists
link failed Permission denied
link failed Permission denied
rm failed for property, Permission denied
failed on 'property.org' - Permission denied
255|[email protected]:/ $ data/local/tmp/onload2.sh
Unable to chmod /data: Operation not permitted
Unable to chmod /data/local/tmp/remount.sh: Operation not permitted
failed on 'property' - Permission denied
mkdir failed for property, File exists
link failed Permission denied
link failed Permission denied
rm failed for property, Permission denied
failed on 'property.org' - Permission denied
255|[email protected]:/ $
btw stifilz, can you share to me your edited bin4ry's script? the one with the re-signed vpnfaker? it tried signing it but it still doesnt work saying something about the vpnfaker. I think there was something wrong with the way i signed it. it might work if i try to use the one you made.
Click to expand...
Click to collapse
Ok doubt it will work but it is attached. I have zipped it up to add as attachment.
Please unzip it and then replace the file (of same name) in the 'stuff' directory of bin4ry's tool.
Good luck once again

Categories

Resources