Hi,
I hope this is right right place.
I used INTERNATIONAL GSM [GT-I9300] and 06. Android 4.1.2 [Build JZO54K ELLA] as that seemed to match my phone model the closest - JZO54K.i9300xxemc2
I had a stock Samsung Galaxy S3 and tried to ROOT it using the Samsung S3 Toolkit so that I can install the Android Revolution ROM v31 but it appears it may have partially rooted, i think.
I didn't want to root it just yet as i wanted backups of the phone but using the backup options i ended up doing "Flash Insecure Boot Image and Root Phone" and then had to manually install Busybox using option 13. "Install BusyBox on Device".
When running most of the backup commands from the Samsung S3 Unified Toolkit, I get [email protected]:/ # su /system/bin/sh: su: not found
I don't know what to do now or know if the phone fully rooted and backed up.
Option 21 shows the below.
DEVICE INFORMATION FOR Samsung Galaxy S3
------------------------------------------------------------------------------------
Device Product Model: GT-I9300
Firmware Build : 4.1.2
Firmware Build ID : JZO54K
Firmware Build PDA : I9300XXEMC2
Firmware Region Code: BTU
------------------------------------------------------------------------------------
Boot Image Status : Insecure [based on ro.secure value]
Note: This is only an indictation if the boot image has been modified
------------------------------------------------------------------------------------
Use another root method like Philz .
jje
I downloaded Root Checker and Titanium Backup and both say the phone is not rooted but it appears may busybox is installed as some backup's seem to be working.
Not sure how could have happened other than I may have selected the incorrect phone model for JZO54K.I9300XXEMC2.
Since the phone seems to be in an inconsistent state, i'm now worried about bricking it.
bbasra said:
Hi,
I hope this is right right place.
I used INTERNATIONAL GSM [GT-I9300] and 06. Android 4.1.2 [Build JZO54K ELLA] as that seemed to match my phone model the closest - JZO54K.i9300xxemc2
I had a stock Samsung Galaxy S3 and tried to ROOT it using the Samsung S3 Toolkit so that I can install the Android Revolution ROM v31 but it appears it may have partially rooted, i think.
I didn't want to root it just yet as i wanted backups of the phone but using the backup options i ended up doing "Flash Insecure Boot Image and Root Phone" and then had to manually install Busybox using option 13. "Install BusyBox on Device".
When running most of the backup commands from the Samsung S3 Unified Toolkit, I get [email protected]:/ # su /system/bin/sh: su: not found
I don't know what to do now or know if the phone fully rooted and backed up.
Option 21 shows the below.
DEVICE INFORMATION FOR Samsung Galaxy S3
------------------------------------------------------------------------------------
Device Product Model: GT-I9300
Firmware Build : 4.1.2
Firmware Build ID : JZO54K
Firmware Build PDA : I9300XXEMC2
Firmware Region Code: BTU
------------------------------------------------------------------------------------
Boot Image Status : Insecure [based on ro.secure value]
Note: This is only an indictation if the boot image has been modified
------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Use Framaroot to root and then install Busybox via BusyBox from PlayStore...
Gesendet von meinem GT-I9300 mit Tapatalk 2
I ended up re-running through recommended rooting options using the Unified Tool kit and it worked.
Now time to put on a custom rom.
Related
Hi,
I tried this procedure to get root access on a Samsung Galaxy S3 I9300 :
http://forum.xda-developers.com/gal...3-07-2012-cf-root-6-4-supersu-cwm5-5-t1695238
The installation worked fine, but I'm not sure whether I need to run SuperSU afterwards to get the "su" root access.
SuperSU comes in version 0.93 and tell it requires being updated.
I'm trying to get root access from the adb shell.
The device is detected and "adb shell" works, but not the "su" command afterwards.
Also, "adb root" tells "adbd cannot run as root in production builds".
I chose the above procedure to root as I don't want to overwrite the kernel, nor data.
Can anyone help ?
Configuration details :
Android 4.3
I9300XUGMK6
Kernel 3.0.31-2429075
[email protected]
JSS15J.I9300XXUGNA5
kaglows controlling
Well, it seems that the new security of Android 4.3 is the cause of the difficulty in rooting with CF-Root 6.4.
Furthermore, CF-Root is no more maintained and was replaced by CF-Autoroot.
But I fear destroying the "/data" folder and "mmssms.db" by installing CF-Autoroot, as this means a new kernel.
I wonder if it would be possible to upgrade SuperSU instead.
So the two options :
a) installing CF-Autoroot
b) upgrading SuperSU
Who tested one of them on the Galaxy S3 I9300, and which were the consequences on the MMS and SMS database ?
Thanks
I'm a newbie.
I tried to root my phone but just unable to root it.
I flash TWRP ( 2.5.0.0) via ODIN sucessfully with a green Pass . Reboot phone to recovery and Hit System and TWRP asked me to swipe if I want to root my phone. I did and my phone reboot after some action performed by TWRP.
I checked with root check basic and it said Root access is not properly installed on this device. I tried to run TWRP manager apk. It said to run the apk phone need rooted. So I know the phone has not been rooted.
I did the following to see if I can correct the problem.
1)Reboot to TWRP recovery and flash CWM_Root_Superuser_3.1.3_Busybox zip file. No success.
2) flash another zip: su-3.0.5-efgh-signed. No sucess.
3) flash another zip: Update superU-1.51 : No success.
4) Flash ClockworkMod Touch Recovery 6.0.2.8 on top of TWRP then try to run Install zip on SD card but CWTR return with an error "E: can not mount sd card "
Below is my phone spec.
Model Number: SGH-T989
Android version: 4.1.2
Baseband version: T989UVMC6
Kernel version: 3.0.31-1003885
[email protected] #1
SMP PREEMPT Mon Mar 11 18:32:51
KST 2013
Build number
JZO54K.T989UVMC6
Please help or guide me to the direction so I can root my phone. Thanks
--------------------------------
Solution:
I found a SU file that work at this thread: http://forum.xda-developers.com/gal...ginner-trying-to-root-flash-rom-t989-t2832408
I'm afraid you're in the wrong forum section here.
This is about the SGH-I9100 model.
Orionbell37 said:
I'm afraid you're in the wrong forum section here.
This is about the SGH-I9100 model.
Click to expand...
Click to collapse
Actually, this part of the forum is for all models of the s2.
---------- Post added at 11:47 AM ---------- Previous post was at 11:43 AM ----------
dukkha2 said:
I'm a newbie.
I tried to root my phone but just unable to root it.
I flash TWRP ( 2.5.0.0) via ODIN sucessfully with a green Pass . Reboot phone to recovery and Hit System and TWRP asked me to swipe if I want to root my phone. I did and my phone reboot after some action performed by TWRP.
I checked with root check basic and it said Root access is not properly installed on this device. I tried to run TWRP manager apk. It said to run the apk phone need rooted. So I know the phone has not been rooted.
I did the following to see if I can correct the problem.
1)Reboot to TWRP recovery and flash CWM_Root_Superuser_3.1.3_Busybox zip file. No success.
2) flash another zip: su-3.0.5-efgh-signed. No sucess.
3) flash another zip: Update superU-1.51 : No success.
4) Flash ClockworkMod Touch Recovery 6.0.2.8 on top of TWRP then try to run Install zip on SD card but CWTR return with an error "E: can not mount sd card "
Below is my phone spec.
Model Number: SGH-T989
Android version: 4.1.2
Baseband version: T989UVMC6
Kernel version: 3.0.31-1003885
[email protected] #1
SMP PREEMPT Mon Mar 11 18:32:51
KST 2013
Build number
JZO54K.T989UVMC6
Please help or guide me to the direction so I can root my phone. Thanks
Click to expand...
Click to collapse
You're supposed to root with odin and not with recovery. This is why cwm doesn't work correctly. Try framaroot (google it and install app) and select the appropriate root method (consult the framaroot q and a or root guide). And also, did you double check that the file you flashed was for your device? There should be device specific root files for your device and it is important to pay attention to thread details.
Regards, gsstudios
gsstudios,
Thanks for answer my call for help.
Unfortunately Framaroot does not work for my model. I searched the forum and somebody already tried but no luck.
Here's the right place to post :
http://forum.xda-developers.com/galaxy-s2-tmobile
I've recently looked into creating my own roms for some fun and learning experience.
The device I'm testing with is a Galaxy S4 (I9505)
I flashed a rom I obtained from Sammobile, the rom is a UK version and doesn't appear to be network locked.
After flashing the device with the rom everything has been fine. I then went on to root the phone and add ClockWorkMod.
ROM FILENAME: I9505XXUHOJ2_I9505YXYHOK1_I9505XXUHOJ2_HOME.tar.md5
All has been fine up until now.
I then downloaded Android Kitchen and got it setup on Ubuntu, added the ROM in and setup the workspace as instructed by nearly all tutorials.
I then added some custom APKs and enabled custom boot animations.
After which I chose to build from the working directory and went with the lazy mode.
This is where everything stops working out well.
To start off with CWM couldn't read the ZIP archive (Of the new ROM from Kitchen)
I couldn't get CWM to mount my SDCard. I tried everything.
In the end I pushed my custom ROM to the device using `adb push`, then CWM decided it would work and install.
However after install the phone reboots and gets stuck at the boot screen with the Samsung logo.
Did I do something wrong?
It feels wrong that Android Kitchen outputs a simple ZIP Archive with the following contents:
- data
- META-INF
- system
- boot.img
- flash_image
- modem.bin
But I don't know any better, tutorials fail to mention what to specifically expect other than a ZIP Archive.
To cut it short.
The ROM worked perfectly fine when I flashed it through Odin.
However after it went through Android Kitchen with no major changes on my part (I didn't touch any files myself other than to add two APKs)
followed by installation via CWM. The ROM suddenly is no longer working and shows "Recovery is not Seandroid Enforcing" followed by a line regarding the Kernel ontop of the boot screen.
I cant full read those two lines as the corner of the screen is cracked.
What changed?
Here's the info output from Kitchen:
Working folder information (v0.224)
Android OS version : 5.0.1
Device : jflte
Model : GT-I9505
ROM Name : TMFKSOFT-I9505
CSC version : I9505YXYHOK1
Rooted (Superuser app + su) : YES
Rooted (unsecured boot.img) : YES
BusyBox installed : NO
BusyBox run-parts support : NO
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : YES
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : NO
/system/app is deodexed : NO
modem.bin found : YES
ROM will wipe all data : NO
Additionally, apologies if I've posted this in the incorrect topic.
I'm completely new to the forums.
Let me know where it belongs if it's in the wrong place.
Quick Edit:
I've reflashed back to the original ROM mentioned, the .tar.md5 file and the device is perfectly fine again :/
Hi
Xperia Tablet Z LTE version
Android version : 5.1.1 / kernel version : 3.4.0-perf-gbccb33a / Platform : 32bits / Build number : 10.7.A.0.228
I've still have stock firmware so I don't have option to boot to recovery mode. I've installed flashtool, bootloader is unlocked, device is rooted with kingrot. I've tried to install TWRP with offical app but without success I've tried to install TWRP manually, but also without success.
C:\Users\szm>adb root
restarting adbd as root
C:\Users\szm>adb wait-for-device
C:\Users\szm>adb push C:\twrp\twrp-3.0.2-0-pollux.img /tmp/twrp.img
failed to copy 'C:\twrp\twrp-3.0.2-0-pollux.img' to '/tmp/twrp.img': Permission denied
C:\Users\szm>adb push C:\twrp\twrp-3.0.2-0-pollux.img /tmp/twrp.img
failed to copy 'C:\twrp\twrp-3.0.2-0-pollux.img' to '/tmp/twrp.img': Permission denied
Click to expand...
Click to collapse
I don't know what do do next. I don't want do do something stupid and brick device. I want to install custom rom from here:
https://forum.xda-developers.com/xp...pment/rom-resurrection-remix-n-6-0-0-t3748092
I'm thinking about flashing kernel with TWRP but don't know where to find correct one, old topics are with old firmware . Any advice?
EDITED:
I wasn't understanding the instructions. Firmware kernel doesn't block the TWRP. If someone has similiar problem to mine with TWRP. Just follow steps from this topic:
https://forum.xda-developers.com/xp...de-tutorial-sony-xperia-tablet-z-lte-t3392831
Solution works with different roms and versions of TWRP. TWRP for me booted after installation so there was no need to use buttons. I'm now happy user of android 8.1 on Xperia tablet Z. Thread can be deleted or closed now.
Hello everyone,
I have a Samsung Galaxy Note 2 GT-N7102 with following details:
Build Number: JSS15J.N7102ZCUEOJ1
Baseband version: N7102ZCUEML1
This is a model from CHN which I believe to be China because almost all default settings are for China.
This model is shipped with Android 4.3.3 and do not allow for new android updates.
I have tried to use TWRP using the model; https://twrp.me/samsung/samsunggalaxynote2n7100.html because I did not find the exact TWRP file for N7102 model.
I have used this model because it shows code name: t03g and using an app that allows me to see some phone informations I found codename t03gduoszc
Problem is after installing TWRP via Odin (version Odin3 v3.13.1), the device does not allow me to boot into recovery mode at all.
Tried to boot into recovery mode by pressing the keys VOL UP+HOME+POWER and also tried by choose to auto-reboot option on Odin after install the file and none of the options works.
I have successfully used CF Auto Root and SuperSU works, but do not know how to upgrade android version for this device using CF Auto Root and all instructions I found are TWRP related.
Can anyone help me find a TWRP file that works for this Galaxy Note 2 model?
Additionally, any step by step guide that allows me to upgrade Android version on the device?
Thank you very mush in advance
Paulo