Showing posts with label Recovery. Show all posts
Showing posts with label Recovery. Show all posts

Friday, May 10, 2013

I9505 :Unofficial Nightly: CyanogenMod 10.1

I9505 :Unofficial Nightly: CyanogenMod 10.1 


 Victorator Developer  present to you a working pure vanilla build of CM10.1 for the I9505! 

Built from source using CyanogenMod Repos and Victorator Repos



Instructions:


1. Flash CWM Recovery for I9505 with Odin as PDA. (TWRP recovery is known to have problems, CWM is recommended)



2. After you boot into recovery backup your current rom in case you want to go back (later you can use the Restore option)




3. After you've made your backup go to 'mounts and storage' and format the following
  • system
  • data
  • cache
4. Install zip from sdcard -> latest build from here 
5. Install zip from sdcard -> gapps-jb-20130301-signed.zip
6. Reboot




What's working:


Audio
GPS
Compass
Proximity Sensor
Wifi
USB mass storage
HW accelerated gui
HW accelerated video
Camera
USB/Wifi tethering
Bluetooth

Not working:


NFC

Sunday, April 28, 2013

Root Samsung Galaxy S4 with Motochopper

Root Samsung Galaxy S4 with Motochopper




Firmware details

PDA: I9505XXUAMDM
Modem: I9505XXUAMDE
CSC: I9505OXAAMDE
Version: Android 4.2.2
Region: Germany
Country: Europe
Carrier: Unbranded
Build date: 12 April, 2013
Pre-requisites
1) Install USB Drivers for Samsung Galaxy S4 to transfer files between the Android device to the computer.
2) Enable USB Debugging Mode on the phone to connect it with the computer and use Android SDK with it. [Press Menu>> Settings>> Applications. From there navigate and click on Development option and ensure the USB Debugging Mode is turned on.]  
3) As the tutorial might wipe out all data of the phone, create a backup. If the device is having custom recovery such as ClockworkMod/TWRP already installed then users are recommended to backup data using the recovery.
4) The Galaxy S4 should have above 80 per cent battery charge.
5) The device should be factory unlocked and not locked to a particular carrier.
6) Rooting the phone will void manufacturer's warranty. However, users can reclaim the warranty back by unrooting the device later.
7) The root file used in the guide works only on Samsung Galaxy S4 I9505. Applying this on any incorrect variant might brick the device. Therefore, verify the model number of the Galaxy S4 by navigating to Settings>> About phone. 
Steps to root Samsung Galaxy S4 I9505 on Android 4.2.2 XXUAMDM Jelly Bean
1) Download CF-Auto-Root package for Samsung Galaxy S4 to the computer. Then extract the downloaded rooting zip file
2) Download Odin3 v1.85 which will help to root the Jelly Bean firmware
3) Turn off the Galaxy S4. Now boot the device into Download Mode by pressing and holding the Volume Down + Home buttons together and then press the Power button until the construction Android robot and a triangle appears on the screen on the phone. Press the Power button again to continue to enter Download Mode
4) Run Odin on the computer
5) Plug in the USB cable to the phone to connect it with the computer while it is in Download Mode. Wait for some time until Odin detects the device. When the device is connected successfully, the ID: COM box will turn yellow with the COM port number. An Added message will appear under Odin window when the phone is connected successfully. If the message does not come then try another USB port, try the one located at the back side of the computer. In case that too does not work, then re-install USB driver
6) In Odin, click on PDA button and select the CF-Auto-Root-jflte-jfltexx-gti9505.zip
7) Ensure that the Auto Reboot and F.Reset Time checkboxes are selected in Odin. Also verify that the Re-Partition option is unchecked
8) Double check everything and click the Start button in Odin. The installation process should begin now and would take few minutes to complete
9) Once the installation process is completed, the phone will reboot into Recovery Mode automatically and install the root package. The ID: COM box will then turn green
10) When the home screen appears on the phone, unplug the USB cable from the device to disconnect it from the computer
Troubleshooting issues
Sometimes the device does not boot into Recovery Mode (after step-9) and root the device. If that happens, then perform the following steps 
a) Perform the tutorial again but ensure that the Auto Reboot option is unchecked. Then after step-9 do the following
b) Pull out the battery to turn off the phone forcefully
c) Now boot the device into recovery mode by pressing and holding the Volume Up, Home and Power buttons together. Doing this will start the installation process to root the phone
Samsung Galaxy S4 I9505 should now be rooted successfully on Android 4.2.2 XXUAMDM Jelly Bean. Open the app list of the phone and check for an app called SuperSU. To ensure the aforementioned root method is installed and working properly, verify with the Root Checker app from Google Play Store.   
[Source: Team Android]









Saturday, March 16, 2013

Chainfire working in Root For Galaxy S4


Chainfire work in Root For Galaxy S4


As some of you might have read on Twitter, I had the chance to remotely(!) play with a Qualcomm-based SGS4 yesterday, and attempted to root it.

So far, it doesn't work. Don't get me wrong, flashing the device and injecting the su binary and app was no problem, but as soon as you actually execute the su binary, the device reboots. Setting ro.secure to 0 and reflashing boot/recovery is also no problem, but there's some added protection that breaks adbd if boot/recovery is modified.

I've only had about an hour (and no time today) so I haven't done more then some really quick tests, but SELinux is certainly present. It appears to be in permissive mode though, so I'm not sure whether it is responsible for this behavior or if it's something else. The SELinux policies and such are inside the boot/recovery ramdisks, and trying to modify those partitions results in adbd not working.

It's probably going to be something simple to disable this behavior, but an hour of remote access is not enough (at least for me) to figure it out. Several ideas, just have to build/upload/flash/test/etc them. To me it did seem there was actually an explicit policy to allow /system/xbin/su, but I'm no SELinux guru, so I might have misinterpreted that.

To prevent any confusion: there does not seem to be any protection from flashing custom firmwares if you want to do so (on this test device at least). The stock firmware just doesn't like being rooted (so far). This is not Samsung locking down the hardware, as some will undoubtedly have assumed.


source : via google plus chainfire