This is a Heimdall/Odin flashable pre-rooted stock UCLE5. This is the exact version that was released over Kies, and contains the bone stock kernel, plus rooted system, modem, cache.img and hidden.img. There are no bootloaders in this package. With this package, you can root stock ICS without incrementing the flash counter.
WARNING: THIS ALMOST CERTAINLY CONTAINS THE eMMC SUPERBRICK BUG.
See this for my considered opinion.
This package is safe to use as long as you read and follow the instructions here, and replace the stock kernel with a known good kernel.
Before 7/8/2012 there were no actual reports of damage from the eMMC brick bug in this firmware release. However, someone has bricked their phone by doing a wipe data/factory reset from a phone with UCLE5 installed and the stock kernel still installed on the phone. Please see this thread. Read the whole thread, but especially pay attention to posts #12 and 16 by Entropy512, one of our elite developers who is very knowledgable about this phone. The person with the bricked phone has confirmed by testing that eMMC memory block mmcblk0p10 was damaged during the wipe data/facotry reset, thus appearantly confirming that the eMMC brick bug is present in the UCLE5 stock kernel. It is particularly important for anyone using this firmware to be careful. It will be completely safe to use this firmware with a known safe kernel. But with the stock kernel still installed, anyone's phone could potentially be at risk.
If flashing this from another base, you should perform a wipe data/factory reset before you flash this package. The stock kernel in this package can potentially cause eMMC chip damage to phones with suseptable memory chips while performing certain memory erase operations. Therefore, it is imperative to avoid doing a wipe data/factory reset with this kernel, and also a very good idea to replace this kernel with a known safe kernel. If flashing this package from UCLE5 to obtain root, it should be fine to flash it without doing a wipe, and retain your personal settings.
This Rooted package does not include busybox. If you need busybox, you can install it from the Google Play Store.
Kernel + Modem + Cache + Rooted UCLE5 System Package: Hotfile | Dev-Host 292.18 MB
Download and extract the tar package using 7-Zip, which can be downloaded from http://www.7-zip.org/download.html. Put UCLE5_Stock_Rooted.tar in the PDA slot in Odin.
Download the Odin3 v1.85 package from MediaFire or xda-developers, or another source of your choice. Odin3 v1.82 will also work.
To flash with Heimdall command line, extract the individual files from the tar and flash the components with heimdall from the commandline as follows:
Code:
heimdall flash --kernel zImage --factoryfs factoryfs.img --modem modem.bin --cache cache.img --hidden hidden.img
Download and install the latest version of Heimdall Command Line for your operating system from here. (Latest version 1.3.2 at this writing.)
Three different ways to install a customized kernel containing ClockworkMod Recovery onto your Rooted phone without incrementing the flash counter.
You must use an ICS kernel, and it must work with Samsung firmware, and be the no-mic-swap version. If you install a Gingerbread kernel the phone will not boot.
The main Kernel options are: Siyah v4.3.3 by Ktoonsez | Siyah v5.1.1 by AJ Newkirk (use the one without mic swap)
Kernel options are: AJ Newkirk/Siyah v3.3.3d ICS | ktoonsez/Siyah v3.4.3 ICS | N.E.A.K. ICS
How to Install a customized kernel containing ClockworkMod Recovery onto your Rooted phone from your phone, using Mobile Odin Lite or Mobile Odin Pro
This is the preferred method to install a customized kernel onto your phone. In addition, Mobile Odin is a very useful tool that will allow you to install custom software directly on your phone without using a computer.
Mobile Odin Lite (free) can be downloaded and installed directly on your phone, or it can be downloaded to your computer and installed with adb. Alternatively, you can purchase Mobile Odin Pro for under $5.00 and install it directly from the Google Play Store. It's easier, and you'll support the developer!
To use Mobile Odin Lite, download the file attached to the OP of this thread. You may need to be a registerd member of xda forums to download this file. Download directly on your phone, or to your computer and move or copy it to your phones sdcard. Using any file manager such as MyFiles or Root Explorer, select the file and install it. You can also install it from your computer using the following adb command:
Code:
adb install MobileODINLite-v2.45.apk
Download the file containing the kernel you want to flash, and extract from it the zImage, which contains the actual kernel.
Transfer the zImage to the root of your phone's internal or external sdcard, using a usb cable or another method such as dropbox.
On your phone, open the Mobile Odin program. If you installed Mobile Odin Lite, when it prompts you to install the add-in, click cancel. If you installed Mobile Odin Pro, you will have already downloaded and installed the add-in to activate all the features in the program. With Mobile Odin Lite, you will still be able to install the kernel.
In Mobile Odin, click on Kernel or Install Kernel, find and select the zImage on your internal or external SD card, and then click on Flash Firmware.
Mobile Odin will flash the kernel and then reboot the phone. You have now installed a custom kernel containing clockworkMod Recovery without changing the flash counter.
If you want to confirm installation of the new kernel, reboot into recovery to verify that you now have ClockworkMod Recovery. (The stock kernel has 3e recovery.) Or install CPU Spy from the Google Play Store (before you root) and compare the Kernel Info it displays with the same info from the stock kernel.
To reboot into recovery on the SGH-I777: With the phone powered off, hold down the vol up + vol down + power buttons continuously until the initial boot screen appears a second time.
The 5.0.2.3 and later versions of ClockworkMod Recovery have a different button configuration. Home = select, Back = back, Power = back from submenu or toggle logo/main menu. The 5.0.2.7 and later versions of ClockworkMod Recovery retain this button configuration but change it to Power = select.
If you installed Mobile Odin Lite, and you don't want to keep it, you can uninstall it now. If you want to keep it and activate all its features, download the add-on MobileODIN_FlashKernel_I777-v1.0.apk from here and install it on your phone with adb using the instructions above.
How to Install a customized kernel containing ClockworkMod Recovery onto your Rooted phone from a pc, using Android Debug Bridge (Windows, Linux and Mac OS)
Download and install the Android Software Developer Kit (SDK) from here. You may need to run SDK Manager with administrator privledges.
You need to have the USB drivers for SGH-I777 installed on your computer. (It will be "Samsung USB Driver for Mobile Phones" in Control Panel\Uninstall Programs.) Download and install the latest drivers from this thread. (x86 and x64)
You will need busybox. If not already installed, download and install busybox from the Google Play Store.
Download the file containing the kernel you want to flash, and extract from it the zImage, which contains the actual kernel.
Move or copy the zImage into the platform-tools directory (on older installations it is the tools directory) where adb.exe resides. This will be something like (on Windows) c:\android-sdk-windows\platform-tools.
On your phone, first enable USB Debugging (Menu\Settings\Applications\Development\USB Debugging) and then plug in your USB cable, connecting your phone to your computer.
Open a command prompt. Change directory to the tools directory, then enter the following at the command line:
Code:
adb push zImage /sdcard/zImage
adb shell
$ su
# dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
# exit
$ exit
The dd command requires superuser permission on the phone represented by a # prompt. After you type su and hit enter, look for a superuser window on your phone and give the permission. If the permission request doesn't pop up, open superuser on your phone to force the phone to prompt for superuser permission. After approval, the adb session will be listed as Unknown in superuser.
After you've finished, the code in the Command prompt window will look something like this (your command prompt and some numbers will be different):
Code:
C:\android-sdk-windows\platform-tools>adb push zImage /sdcard/zImage
4279 KB/s <4776784 bytes in 1.090s>
C:\android-sdk-windows\platform-tools>adb shell
$ su
su
# dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
10153+1 records in
10153+1 records out
5198492 bytes transferred in 2.558 secs <2032248 bytes/sec>
# exit
exit
$ exit
exit
Reboot the phone. You have now installed a custom kernel containing clockworkMod Recovery without changing the flash counter.
If you want to confirm installation of the new kernel, reboot into recovery to verify that you now have ClockworkMod Recovery. (The stock kernel has 3e recovery.) Or install CPU Spy from the Google Play Store (before you root) and compare the Kernel Info it displays with the same info from the stock kernel.
To reboot into recovery on the SGH-I777: With the phone powered off, hold down the vol up + vol down + power buttons continuously until the initial boot screen appears a second time.
The 5.0.2.3 and later versions of ClockworkMod Recovery have a different button configuration. Home = select, Back = back, Power = back from submenu or toggle logo/main menu. The 5.0.2.7 and later versions of ClockworkMod Recovery retain this button configuration but change it to Power = select.
How to Install a customized kernel containing ClockworkMod Recovery onto your Rooted phone from your phone, using Android Terminal Emulator
Download and Install Android Terminal Emulator onto your phone from the Google Play Store.
You will need busybox. If not already installed, download and install busybox from the Google Play Store.
Download (onto your PC) the file containing the kernel you want to flash, and extract from it the zImage, which contains the actual kernel.
Transfer the zImage to the root of your phone's sdcard, using a usb cable or another method such as dropbox.
On the phone, open a terminal session with Android Terminal Emulator.
A few points to be aware of:
Android is a version of linux so you are using linux commands. Linux commands are case sensitive, so you must for instance type "zImage" and not "zimage", if that is the way the file is spelled on the sd card.
Since this will be the first time you have used superuser.apk with the terminal, you may need to approve it on you phone. After that, superuser permission will be remembered.
When you first open a terminal session, you will be at the root of the phone, or essentially "/". The $ prompt means shell access, the # prompt means root file access.
You need a # prompt to complete this Step.
If your keyboard goes away, use the menu button options to get it back.
In the terminal session, type su and then enter. You will get a superuser request. Once you approve it, you will get the # prompt.
Then type the following:
Code:
dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
Press enter, wait till the zImage is copied over to the named block. (takes about 2 or 3 seconds)
To close the root session, type "exit" and enter. Use the back button to close Android Terminal Emulator.
Reboot the phone. You have now installed a custom kernel containing clockworkMod Recovery without changing the flash counter.
If you want to confirm installation of the new kernel, reboot into recovery to verify that you now have ClockworkMod Recovery. (The stock kernel has 3e recovery.) Or install CPU Spy from the Google Play Store (before you root) and compare the Kernel Info it displays with the same info from the stock kernel.
To reboot into recovery on the SGH-I777: With the phone powered off, hold down the vol up + vol down + power buttons continuously until the initial boot screen appears a second time.
The 5.0.2.3 and later versions of ClockworkMod Recovery have a different button configuration. Home = select, Back = back, Power = back from submenu or toggle logo/main menu. The 5.0.2.7 and later versions of ClockworkMod Recovery retain this button configuration but change it to Power = select.
You are awesome
Thank you for this creepy!
Sent from my SGH-I777 using Tapatalk 2
You da man!!!!
Been having issues with broken CWM for awhile. Used your guides to unroot... then root again and flash custom Kernel with CWM again. Thanks fixed all my issues.
Thanks I will be using this later
Excellent write-up creepy (as usual)...this is what alot of people have been waiting for and you have delivered! Covered all the bases too...now all anyone needs to get the official ICS is this thread and some reading comprehension!
Hi - can this tar be installed using Mobile Odin Lite and the i777 flash kernel? Or do I have to use heimdall or desktop odin only?
Tophaholic said:
Hi - can this tar be installed using Mobile Odin Lite and the i777 flash kernel? Or do I have to use heimdall or desktop odin only?
Click to expand...
Click to collapse
Did you even read the OP?
jack man said:
Did you even read the OP?
Click to expand...
Click to collapse
Dude...i am not asking about custom kernel - my question is can i use mobile odin to flash the root injected stock tar.
Tophaholic said:
Dude...i am not asking about custom kernel - my question is can i use mobile odin to flash the root injected stock tar.
Click to expand...
Click to collapse
Like he said he says you can in the op
transmitted from the Dark Obelisk
Tophaholic said:
Hi - can this tar be installed using Mobile Odin Lite and the i777 flash kernel? Or do I have to use heimdall or desktop odin only?
Click to expand...
Click to collapse
Mobile Oden will flash from a tar file. I haven't tested it but I assume it will flash everything in this tar file, since there are no boot loaders. Since you are asking, I assume you are already rooted in have mobile oden.
Sent from my SGH-I777 using xda app-developers app
creepyncrawly said:
Mobile Oden will flash from a tar file. I haven't tested it but I assume it will flash everything in this tar file, since there are no boot loaders. Since you are asking, I assume you are already rooted in have mobile oden.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Thank You!!!...someone finally gets my question. Its so easy on these forums to say "did you read the OP?" of course I did - not once but 10 times. but did not see anything about using mobile odin for flashing the tar file.
Yes I am rooted and have been toying with various ROMs and kernels. Was thinking about installing the stock UCLE5 with stock kernel (take the risk) and see if I like it. If not will install a custom kernel with CWM.
one more question for you - The brick bug that was there on the leaks was only if u restored from CWM after flashing the leak? So if I flash the above official release and keep the stock kernel whats my risk if I do not restore from CWM?
Tophaholic said:
one more question for you - The brick bug that was there on the leaks was only if u restored from CWM after flashing the leak? So if I flash the above official release and keep the stock kernel whats my risk if I do not restore from CWM?
Click to expand...
Click to collapse
No. I don't understand all the internal details, but I think it is when erasing from eMMC memory. Thus a wipe data/factory reset will also damage the chip, and maybe a few other operations.
You could always untar the whole archive and copy all the pieces to your phone for Mobile Odin.
The eMMC dealio is some erase method they compiled the kernel with that happens to corrupt the memory when you wipe. Its both a kernel problem as well as buggy firmware with the internal memory.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Battery Question.
Installed this ROM with no problems. Interestinly I can once again use KIES which I couldn't since rooting with other kernels, and ROM's. My question is has anyone had issues with batrtery performance since the ROM install as my battery life seems to be really dismal?
Ok so just to get it clear....i can wipe my UnNamed and install the package in cwm without encountering the flash problem and just to be safe i can install a custom kernel to replace the stock. Usually i would install it with cwm then why do i have to use mobile odin or any other methods stated here. is it because of the eMMC chip issue?
dhaval33 said:
Ok so just to get it clear....i can wipe my UnNamed and install the package in cwm without encountering the flash problem and just to be safe i can install a custom kernel to replace the stock. Usually i would install it with cwm then why do i have to use mobile odin or any other methods stated here. is it because of the eMMC chip issue?
Click to expand...
Click to collapse
Yes, you have it right. And the reason you can't use ClockworkMod Recovery is because the stock rom has a stock kernel with 3e recovery.
creepyncrawly said:
Yes, you have it right. And the reason you can't use ClockworkMod Recovery is because the stock rom has a stock kernel with 3e recovery.
Click to expand...
Click to collapse
Ok i see thanks.
dhaval33 said:
Ok so just to get it clear....i can wipe my UnNamed and install the package in cwm without encountering the flash problem and just to be safe i can install a custom kernel to replace the stock. Usually i would install it with cwm then why do i have to use mobile odin or any other methods stated here. is it because of the eMMC chip issue?
Click to expand...
Click to collapse
Yes, you have it right. And the reason you can't use ClockworkMod Recovery is because the stock rom has a stock kernel with 3e recovery.
dhaval33 said:
Ok i see thanks.
Click to expand...
Click to collapse
I mis-read your original question. I gave you the wrong answer. You can not flash a tar in cwm. You will need to use Odin or Heimdall from a personal computer. Or, since you are coming from UnNamed, you can install Mobile Odin and flash it from your phone if you wish.
I'm having trouble getting my s2 recognized by odin, I've tried the drivers on the samsung site and the ones that come with kies mini and odin still doesn't recognize it. Can anyone help me?
Okay now im using the drivers from the not mini version of kies and it detects the phone but it now shows 2 different ID:COMs. I'm not sure if thats normal or not, i think one is the samsung mobile usb modem and the other is the samsung mobile usb cdc composite device.. It lets me select which one i want to use but idk which one i want to use and idk which is which..
Nevermind. idk what the other thing it detected was because i have nothing else plugged into my computer but i unplugged the phone and the first port went away on odin and the modem and cdc composite device both left the device manager so i plugged it back in and just clicked the first one and now it works
creepyncrawly said:
Yes, you have it right. And the reason you can't use ClockworkMod Recovery is because the stock rom has a stock kernel with 3e recovery.
I mis-read your original question. I gave you the wrong answer. You can not flash a tar in cwm. You will need to use Odin or Heimdall from a personal computer. Or, since you are coming from UnNamed, you can install Mobile Odin and flash it from your phone if you wish.
Click to expand...
Click to collapse
Ok so do i need to wipe and then use mobile odin or no wipe will do?
Related
This approach to customizing your phone involves the following steps:
1. Read the flash counter.
2. Root your phone:
- by using DooMLoRD's Easy Rooting Toolkit. (ZergRush Exploit)
- by using SuperOneClick Root. (ZergRush Exploit)
- by flashing Entropy512's Return/Unbrick to stock, Kernel + Rooted System Package using Odin or Heimdall.
3. Install a customized kernel containing ClockworkMod Recovery:
- by using Mobile Odin Lite or Mobile Odin Pro on your phone.
- by using adb on your computer.
- by using Android Terminal Emulator on your phone.
4. Flash the custom ROM package of your choice:
- by using ClockworkMod Recovery and a CWM flashable zip package.
- by using Mobile Odin.
PLEASE NOTE: While the following guide was written before AT&T officially released ICS, the principles contained in this guide are still applicable to our phone regardless of firmware version. However if your phone is currently running stock ICS UCLE5, using this method will install Gingerbread, taking your phone back to an earlier version. To root the phone while retaining ICS, please see the [Heimdall][Odin][Stock][Root]UCLE5 Stock ICS with Root thread.
JANUARY 2013 ROOTING UPDATE: In mid December of 2012, Samsung released an over-the-air update for the SGH-I777UCLK3, taking the operating system to version 4.0.4. Around the same time, XDA developer Chainfire released an application called ExynosAbuse APK which can be used to root the SGH-I777 with SuperSU, without the need to use a PC. ExynosAbuse APK is the best, and probably the only practical method for rooting UCLK3 without flashing some other distribution. In addition, it seems that this application is a good way to root any phone running 4.x operating systems, and possibly phones running 2.x operating systems as well. Be aware, there are possible risks involved with using this application. Please thoroughly read and understand Chainfire's thread linked above before using his application.
Discussion
The Samsung Galaxy S II contains an internal flash counter which is incremented each time a non-stock binary (kernel/rom) is flashed from a computer using Odin or Heimdall. (Using the new Mobile Odin on your phone does not increment the flash counter.) The purpose of the flash counter is believed to be to allow Samsung and or AT&T technicians to detect if the phone has a voided warranty through flashing non-stock firmware. The first time the flash counter is activated, the phone also displays a warning screen on boot up with a yellow warning triangle containing an exclamation point. The warning screen also contains the i9100 logo. (Evidently, Samsung did not change the warning screen from the International version of the Galaxy S II for the AT&T version.) Some rooting methods require that a non-stock kernel be flashed before rooting can be accomplished. So rooting and flashing custom software can both cause the dreaded yellow triangle, and increment the flash counter.
It is possible to remove the warning screen by two methods. One is by using a Jig to place the phone into download mode. The other is by flashing a stock kernel using either Odin or Heimdall. However, there is only one way to reset the flash counter, and that is with a micro usb Jig. This was true for the International version of the Galaxy S II as confirmed by Chainfire on the i9100 forums. This has also been confirmed for the AT&T Galaxy S II by dayv. Please see his post here, and then go to this post and read it and the following five posts for a complete description with screen shots.
pinoymutt adds:
On the newer versions of the i9100 ROMs apparently Samsung has updated the bootloaders to render the "jig trick" to reset the counter useless. This has also been observed in the latest ATT leak that DG posted in the General Forum (UCKJ2), where new bootloaders are included that render the jig reset obsolete.
Click to expand...
Click to collapse
Additionally, there have been rumors that there is a secondary counter hidden in the code of the Galaxy S II which increments each time the primary flash counter is reset to zero. This rumor was either started or strengthened over in the i9100 forums by Chainfire. He never did find any code, and later said he was not fully convinced there ever was any code. But the rumor has already had some discussion in these At&T forums, so it's worth mentioning. My opinion is that a secondary counter doesn't exist, but if it does, this would be an additional reason for this guide.
Some people may be reluctant to root their phone and/or flash custom software onto it, not wishing to take a chance on voiding their warranty. However, there is a way to completely avoid this problem. The solution is to never increment the flash counter in the first place, and never activate the yellow warning triangle. Using this guide to root and modify an AT&T Galaxy S II phone right out of the box, along with the ability to flash back to completely stock firmware followed by a wipe data/factory reset from stock 3e recovery, (see this Guide), will result in a phone that can be returned for warranty purposes to either AT&T or Samsung without fear of the warranty being denied.
Disclaimer: I didn't think all this stuff up. The following information is mainly gleaned from all the great developers and knowledgable users on this forum. A special thanks to Entropy512 for creating the stock + root package that makes this all possible.
Here is some additional information for noobs about the tools and techniques used in this guide.
1.) How to read the flash counter on an AT&T Samsung Galaxy S II
Boot into download mode by this method:
With the phone powered off, plug in the usb cable while holding the vol up + vol down buttons (but not the power button).
When the warning screen appears, press Volume up to continue into download mode.
At the top of the screen you will see:
ODIN MODE
PRODUCT NAME: SGH-I777
CUSTOM BINARY DOWNLOAD: NO --or-- YES (x counts)
CURRENT BINARY: SAMSUNG OFFICIAL --or-- CUSTOM
Once you have verified the information, remove the usb cable, and hold down the power button until the phone begins to reboot. (Do not do this if you are actually flashing the phone. Interrupting a flash can cause bad things to happen.)
You will not see the above information if you enter download mode by another method, ie. by using adb or the power menu, etc.
Now you can check on your flash counter at any stage of the foregoing guide.
To root UCKK6, use method 2c or 2d to flash UCKH7 stock plus root. Immediately after rooting, if you want UCKK6, open Settings and check for updates, download and install the OTA update, and it will retain root. Some have reported this works, and some say not. Alternatively, use Odin3 v1.85 to flash Entropy512's UCKK6 Stock plus Root package from his thread here.
Click to expand...
Click to collapse
2a.) How to root by using DooMLoRD's Easy Rooting Toolkit. (ZergRush Exploit) (Windows)
This rooting method does not work on the UCKK6.
This is the preferred method of rooting for users with the Windows operating system on their computer, and a phone running UCKH7.
Download the "DooMLoRD's Easy Rooting Toolkit v4.0" package from this thread and extract it to a directory on your hard drive using WinZip or a similar program.
You need to have the USB drivers for SGH-I777 installed on your computer. (It will be "Samsung USB Driver for Mobile Phones" in Control Panel\Uninstall Programs.) Download and install the latest drivers from this thread. (x86 and x64)
Both USB Debugging (Menu\Settings\Applications\Development) and Unknown Sources (Menu\Settings\Applications) should be enabled on your phone.
Increase the screen timeout on your phone to 10 minutes. (Menu\Settings\Display\Screen Timeout) Remember to set it back to a shorter interval after you are done rooting.
Connect the USB cable to the phone and the computer. Go to the directory where you extracted the package and execute "runme.bat".
The toolkit will open a command prompt window where you will see the progress of the rooting process. It takes between 5 and 10 minutes for the process to complete.
Success. You're rooted.
2b.) How to root by using SuperOneClick Root. (ZergRush Exploit) (Windows, Linux and Mac OS)
This rooting method does not work on the UCKK6.
Download "SuperOneClick v2.3.1 - Automatic Driver Installation" from DepositFiles (or look for links here) and extract it to a directory on your hard drive using WinZip or a similar program.
Please go the the SuperOneClick thread and read about the tool and how to use it. For Windows XP you need to have .NET Framework v2.0 or above installed. For Mac OS and certain flavors of Linux, you need to install Mono.
I have not tested this tool. It is included here because it claims to work for Mac OS and Linux, and provides a way to use the ZergRush Exploit on those operating systems. Since I am only familiar with Windows, I will be unable to support this rooting method. For problems, try posting questions in the SuperOneClick thread linked above.
If you try SuperOneClick on Linux or Mac, please post your (success or failure) results. Thanks.
2c.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader (Windows)
Download the "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" package from Hotfile | Dev-Host 268.64 MB.
Extract the contents of the zip file to a directory on your hard disk drive. This is a One-Click version of Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package plus stock modem from the development forum. (Contains stock zImage, factoryfs.img with root, and modem.bin.)
Start the Odin3 One-Click Downloader program by double clicking on "I777UCKH7 OCD With Root.exe".
Now Enter Download Mode:
With the phone powered off, plug in the usb cable while holding the vol up + vol down buttons (but not the power button).
When the warning screen appears, press Volume up to continue into download mode.
In Odin, the small edit box in the upper left corner will turn yellow, and say something like [0:COM8]. The number could be different.
Click Start. Watch the progress bar advance in green while the message box in the lower area describes the steps. When the flash is finished, the top left larger edit box will turn green and say PASS! and your phone will automatically reboot.
Unplug the usb cable from you phone after it boots up. Success. You're Rooted.
2d.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package from the command line using Heimdall (Linux and Mac OS)
Tested on Linux, should work on Mac OS
Download and install the latest version of Heimdall Command Line for your operating system from here. (Latest version 1.3.1 at this writing.)
Download Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package from here, or if you have difficulty with the links in his thread, there are alternative links for all his files in the Download Repository toward the bottom. Extract the PDA.tar file from this package to a directory on your hard disk drive, then extract the two component files from the tar - zImage and factoryfs.img.
Place zImage and factoryfs.img both in the directory where you have the Heimdall command line executable, and enter the following at the command prompt:
Code:
heimdall flash --kernel zImage --factoryfs factoryfs.img
Reboot the phone. Success. You're Rooted.
You must use a Gingerbread kernel when using this method. If you use an ICS kernel while your phone is running Gingerbread, it will not boot!!!
Click to expand...
Click to collapse
3a.) How to Install a customized kernel containing ClockworkMod Recovery onto your Rooted phone from your phone, using Mobile Odin Lite or Mobile Odin Pro
This is the preferred method to install a customized kernel onto your phone. In addition, Mobile Odin is a very useful tool that will allow you to install custom software directly on your phone without using a computer.
Mobile Odin Lite (free) can be downloaded and installed directly on your phone, or it can be downloaded to your computer and installed with adb. Alternatively, you can purchase Mobile Odin Pro for under $5.00 and install it directly from the market. It's easier, and you'll support the developer!
To use Mobile Odin Lite, download the file attached to the OP of this thread. You may need to be a registerd member of xda forums to download this file. Download directly on your phone, or to your computer and move or copy it to your phones sdcard. Using any file manager such as MyFiles or Root Explorer, select the file and install it. You can also install it from your computer using the following adb command:
Code:
adb install MobileODINLite-v2.30.apk
Download the file containing the kernel you want to flash, and extract from it the zImage, which contains the actual kernel. There are several kernels available which can be found in the AT&T SGS II Android Development forum. You must use a Gingerbread kernel! Usually choose between the following two Gingerbread kernels: Entropy512's Daily Driver or Siyah 2.6.
Transfer the zImage to the root of your phone's internal or external sdcard, using a usb cable or another method such as dropbox.
On your phone, open the Mobile Odin program. If you installed Mobile Odin Lite, when it prompts you to install the add-in, click cancel. If you installed Mobile Odin Pro, you will have already downloaded and installed the add-in to activate all the features in the program. With Mobile Odin Lite, you will still be able to install the kernel.
In Mobile Odin, click on Kernel or Install Kernel, find and select the zImage on your internal or external SD card, and then click on Flash Firmware.
Mobile Odin will flash the kernel and then reboot the phone. You have now installed a custom kernel containing clockworkMod Recovery without changing the flash counter.
If you want to confirm installation of the new kernel, reboot into recovery to verify that you now have ClockworkMod Recovery. (The stock kernel has 3e recovery.) Or install CPU Spy from the Market (before you root) and compare the Kernel Info it displays with the same info from the stock kernel.
To reboot into recovery on the SGH-I777: With the phone powered off, hold down the vol up + vol down + power buttons continuously until the initial boot screen appears a second time.
The 5.0.2.3 and later versions of ClockworkMod Recovery have a different button configuration. Home = select, Back = back, Power = back from submenu or toggle logo/main menu. The 5.0.2.7 version of ClockworkMod Recovery retains this button configuration but changes it to Power = select.
If you installed Mobile Odin Lite, and you don't want to keep it, you can uninstall it now. If you want to keep it and activate all its features, download the add-on MobileODIN_FlashKernel_I777-v1.0.apk from here and install it on your phone with adb using the instructions above.
3b.) How to Install a customized kernel containing ClockworkMod Recovery onto your Rooted phone from a pc, using Android Debug Bridge (Windows, Linux and Mac OS)
Download and install the Android Software Developer Kit (SDK) from here. You may need to run SDK Manager with administrator privledges.
You need to have the USB drivers for SGH-I777 installed on your computer. (It will be "Samsung USB Driver for Mobile Phones" in Control Panel\Uninstall Programs.) Download and install the latest drivers from this thread. (x86 and x64)
Download the file containing the kernel you want to flash, and extract from it the zImage, which contains the actual kernel. There are several kernels available which can be found in the AT&T SGS II Android Development forum. You must use a Gingerbread kernel! Usually choose between the following two Gingerbread kernels: Entropy512's Daily Driver or Siyah 2.6.
Move or copy the zImage into the platform-tools directory (on older installations it is the tools directory) where adb.exe resides. This will be something like (on Windows) c:\android-sdk-windows\platform-tools.
On your phone, first enable USB Debugging (Menu\Settings\Applications\Development\USB Debugging) and then plug in your USB cable, connecting your phone to your computer.
Open a command prompt. Change directory to the tools directory, then enter the following at the command line:
Code:
adb push zImage /sdcard/zImage
adb shell
$ su
# dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
# exit
$ exit
The dd command requires superuser permission on the phone represented by a # prompt. After you type su and hit enter, look for a superuser window on your phone and give the permission. If the permission request doesn't pop up, open superuser on your phone to force the phone to prompt for superuser permission. After approval, the adb session will be listed as Unknown in superuser.
After you've finished, the code in the Command prompt window will look something like this (your command prompt and some numbers will be different):
Code:
C:\android-sdk-windows\platform-tools>adb push zImage /sdcard/zImage
4279 KB/s <4776784 bytes in 1.090s>
C:\android-sdk-windows\platform-tools>adb shell
$ su
su
# dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
10153+1 records in
10153+1 records out
5198492 bytes transferred in 2.558 secs <2032248 bytes/sec>
# exit
exit
$ exit
exit
Reboot the phone. You have now installed a custom kernel containing clockworkMod Recovery without changing the flash counter.
If you want to confirm installation of the new kernel, reboot into recovery to verify that you now have ClockworkMod Recovery. (The stock kernel has 3e recovery.) Or install CPU Spy from the Market (before you root) and compare the Kernel Info it displays with the same info from the stock kernel.
To reboot into recovery on the SGH-I777: With the phone powered off, hold down the vol up + vol down + power buttons continuously until the initial boot screen appears a second time.
The 5.0.2.3 and later versions of ClockworkMod Recovery have a different button configuration. Home = select, Back = back, Power = back from submenu or toggle logo/main menu. The 5.0.2.7 version of ClockworkMod Recovery retains this button configuration but changes it to Power = select.
3c.) How to Install a customized kernel containing ClockworkMod Recovery onto your Rooted phone from your phone, using Android Terminal Emulator
Download and Install Android Terminal Emulator onto your phone from the Market.
Download (onto your PC) the file containing the kernel you want to flash, and extract from it the zImage, which contains the actual kernel. There are several kernels available which can be found in the AT&T SGS II Android Development forum. You must use a Gingerbread kernel! Usually choose between the following two Gingerbread kernels: Entropy512's Daily Driver or Siyah 2.6.
Transfer the zImage to the root of your phone's sdcard, using a usb cable or another method such as dropbox.
On the phone, open a terminal session with Android Terminal Emulator.
A few points to be aware of:
Android is a version of linux so you are using linux commands. Linux commands are case sensitive, so you must for instance type "zImage" and not "zimage", if that is the way the file is spelled on the sd card.
Since this will be the first time you have used superuser.apk with the terminal, you may need to approve it on you phone. After that, superuser permission will be remembered.
When you first open a terminal session, you will be at the root of the phone, or essentially "/". The $ prompt means shell access, the # prompt means root file access.
You need a # prompt to complete this Step.
If your keyboard goes away, use the menu button options to get it back.
In the terminal session, type su and then enter. You will get a superuser request. Once you approve it, you will get the # prompt.
Then type the following:
Code:
dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
Press enter, wait till the zImage is copied over to the named block. (takes about 2 or 3 seconds)
To close the root session, type "exit" and enter. Use the back button to close Android Terminal Emulator.
Reboot the phone. You have now installed a custom kernel containing clockworkMod Recovery without changing the flash counter.
If you want to confirm installation of the new kernel, reboot into recovery to verify that you now have ClockworkMod Recovery. (The stock kernel has 3e recovery.) Or install CPU Spy from the Market (before you root) and compare the Kernel Info it displays with the same info from the stock kernel.
To reboot into recovery on the SGH-I777: With the phone powered off, hold down the vol up + vol down + power buttons continuously until the initial boot screen appears a second time.
The 5.0.2.3 and later versions of ClockworkMod Recovery have a different button configuration. Home = select, Back = back, Power = back from submenu or toggle logo/main menu. The 5.0.2.7 version of ClockworkMod Recovery retains this button configuration but changes it to Power = select.
4.) Flash the ROM package of your choice using ClockworkMod Recovery and a CWM flashable zip package or Mobile Odin with any package
Your phone is now set up to flash custom software using ClockworkMod zipped install files in ClockworkMod Recovery. If you used and retained Mobile Odin, you can also flash custom software with it. Anything you flash on the phone using ClockworkMod Recovery, Mobile Odin, adb or terminal, will not affect the flash counter or invoke the warning triangle. Therefore, you can flash ROM's Kernels and Modems to your hearts content. Just avoid ever flashing anything containing a non-stock kernel with Odin or Heimdall from your computer. I would also caution against flashing any package with bootloaders. There is no valid reason to flash bootloaders on the SGH-I777 at this time, but some developers may include bootloaders in their CWM flashable zip files, or Odin flashable tar files.
Nice write-up. The info has been floating around on various threads and posts, but you did a great job putting all together into one nice step-by-step for folks looking to learn.
Hopefully it'll also cut down on the million of duplicate threads asking the same question!
---------- Post added at 05:02 PM ---------- Previous post was at 04:58 PM ----------
creepyncrawly said:
Discussion
It has been reported to be possible to remove the warning screen and reset the flash counter by two methods. One is by using a Jig to place the phone into download mode. The other is by flashing a stock kernel using either Odin or Heimdall. However, while it is confirmed that the jig will both remove the triangle and reset the counter, and that flashing a stock kernel with Odin or Heimdall will remove the warning triangle, it is not certain that flashing a stock kernel with Odin or Heimdall will actually reset the flash counter. The developer Chainfire on the i9100 forums says that on the International version of the Galaxy S II, it will not. This is yet to be confirmed or denied on the AT&T version of the phone, as far as I know.
Click to expand...
Click to collapse
On the newer versions of the i9100 ROMs apparently Samsung has updated the bootloaders to render the "jig trick" to reset the counter useless.
This has also been observed in the latest ATT leak that DG posted in the General Forum (UCKJ2), where new bootloaders are included that render the jig reset obsolete.
Great guide, lots of information in here! Thanks for preparing it.
Sent from my SAMSUNG-SGH-I777 using xda premium
I think this guide is sticky worthy.
Sent from my SAMSUNG-SGH-I777 using XDA App
Awesome guide, thank you for putting this all together in one place. Very helpful for a guy coming to Samsung from HTC.
+1 for sticky worthy!
Sent from my SAMSUNG-SGH-I777 using Tapatalk
THANKS! Helped me when I got stuck!
Sent from my SAMSUNG-SGH-I777 using xda premium
This is exactly what I needed.... yesterday (as you know)... my Search and Question buttons almost caught fire from over-use looking for all the pieces of the puzzle. I did the Entropy512 "Kernel + Rooted System Package via Odin3 v1.85.... extracted the zImage from Codeworkx's CWM Kernel, and pushed it to phone via adb push. I got hung up on the "permission" to write to the block, but finally got it solved. Creepyncrawly: you might want to add a bullet step to your OP#1 to open SuperUser app on phone just prior to the adb shell "su" command. When I did this, phone prompted for superuser permission... after acceptance, it is stored as "Unknown" in the superuser app list. Once this occurred, then I got the "#" prompt and could dd write to block to flash CWM.
Absolutely stellar post as it puts it all in one place. This will definitely help others who might stumble in adb as I did. Thanks again to all the forum members who posted helpful advice and links.
DAMN! My JIG just got here!
Thanks for the nice write up!
Great write up OP. however like the above poster my JIG just got here too and I just used it, and it was quick and painless.
Alucardis666 said:
Great write up OP. however like the above poster my JIG just got here too and I just used it, and it was quick and painless.
Click to expand...
Click to collapse
Jigs don't work in 2.3.5 so these methods will be extremely helpful for others
Sent from my SAMSUNG-SGH-I777 using xda premium
This post should be a sticky, or at least the sticky should link to this post.
arctia said:
This post should be a sticky, or at least the sticky should link to this post.
Click to expand...
Click to collapse
It's linked in the sticky FAQ thread. I'd rather not see too many sticky threads. That seems to me to be more confusing than helpful.
Great write up in easy steps tyo follow.
I have a question, on removing the yellow triangle. I rooted with Jivy26 easy root and was wondering can I reroot with Entropy512 to remove the yellow triangle or can I just do step 2a from link?
Would like to be able to return to stock if i need to send in for warranty. Also should we use CWM manager for backing up?
ElCamino said:
Great write up in easy steps tyo follow.
I have a question, on removing the yellow triangle. I rooted with Jivy26 easy root and was wondering can I reroot with Entropy512 to remove the yellow triangle or can I just do step 2a from link?
Would like to be able to return to stock if i need to send in for warranty. Also should we use CWM manager for backing up?
Click to expand...
Click to collapse
Follow the instructions from 2a on, and it will remove the triangle and you will maintain root.
Sent from my SAMSUNG-SGH-I777 using XDA App
Can you check to see if I understood correctly?
I flashed my kernel using Odin to get root , flashed the CWM file to get the recovery using Odin as well. You're saying that I can re-root the phone using your method, and the yellow triangle will disappear, as well as reset my counter?
Also, if I were to get a jig, it resets the counter? Or just removes the triangle?
Sent from my SGH-I777 using XDA App
Blaze9 said:
Can you check to see if I understood correctly?
I flashed my kernel using Odin to get root , flashed the CWM file to get the recovery using Odin as well. You're saying that I can re-root the phone using your method, and the yellow triangle will disappear, as well as reset my counter?
Also, if I were to get a jig, it resets the counter? Or just removes the triangle?
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
You should still be rooted, if I understand what you are saying. Root consists of /system/app/superuser.apk and /system/xbin/busybox. You can verify that you are rooted by looking for the superuser app in your app drawer. If it's not there, then you are not rooted.
If you flash Entropy512's stock + root package with Odin, you will clear the yellow triangle and be rooted, on full stock kernel and stock system image. Then follow the rest of the guide if you want to take it further. We believe flashing the stock kernel with Odin will both remove the warning triangle, and reset the counter, but read the discussion in the Guide, as it points out that over in the i9100 forum, they say flashing the stock kernel will clear the warning but not reset the counter.
The Jig will do both.
creepyncrawly said:
You should still be rooted, if I understand what you are saying. Root consists of /system/app/superuser.apk and /system/xbin/busybox. You can verify that you are rooted by looking for the superuser app in your app drawer. If it's not there, then you are not rooted.
If you flash Entropy512's stock + root package with Odin, you will clear the yellow triangle and be rooted, on full stock kernel and stock system image. Then follow the rest of the guide if you want to take it further. We believe flashing the stock kernel with Odin will both remove the warning triangle, and reset the counter, but read the discussion in the Guide, as it points out that over in the i9100 forum, they say flashing the stock kernel will clear the warning but not reset the counter.
The Jig will do both.
Click to expand...
Click to collapse
Thanks for clarifying that mate. I think Im going to order a jig then. Any "fake" ones I should know about?
Sent from my SGH-I777 using XDA App
Blaze9 said:
Thanks for clarifying that mate. I think Im going to order a jig then. Any "fake" ones I should know about?
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
I don't own a jig. I'm told that the SGS II has a closer tolerance for the 301K ohm value than the Captivate does, so some jigs that work with the Captivate won't work with the SGS II. I've read you can trust the jigs from Mobil Tech Videos, and the owner is quite active in the forums here, so that would be a safe and sensible choice.
but read the discussion in the Guide, as it points out that over in the i9100 forum, they say flashing the stock kernel will clear the warning but not reset the counter.
The Jig will do both.
Click to expand...
Click to collapse
This is correct, the counter that shows the number of times you have flashed a custom kernel does not get reset by flashing a stock kernel - just the warning triangle gets removed by flashing to stock.
And yes the download mode jig does both reset the counter number to "No" as well as remove the triangle.
I have tested with a jig from http://www.mobiletechvideos.com/blo...s-download-mode-jig-so-easy-a-baby-can-do-it/
Sent from my SAMSUNG-SGH-I777 using XDA App
Very awesome, wish there was a guide on how to reset current to default w/o a kernel change.
Phone Details
Motorola Atrix 4G AT&T (bought around June 2011 Time frame)
System Version
4.5.91.MB860.ATT.en.US
Model Number
MB860
Android Version
2.34
Baseband Version
N_01.77.30P
Webtop Version
WT-1.2.0-110
Kernel Version
[email protected] #2
Build Number
4.5.91
I am absolutely new to this Android ROM installs on the phones. Though I decided to install this ROM I absolutely didn’t’ have any idea how to proceed. As a beginner I started doing the following in order.
Download and Keep the CM7 ROM
1. Downloaded Ba2F.zip to my laptop
2. Downloaded and Installed the Motorola USB drivers MotoHelper_2.0.53_Driver_5.2.0.EXE
3. Connect the Atrix and set the USB option on the phone to “USB Mass Storage”
4. Copy both BaTF.zip as well as the Extracted one to Phone internal storage as well as the Ext-SDcard on the phone
Download ROM Manager and Titanium Backup
1. Downloaded both from Android Market (ROM Manager Pro and Titanium Backup Free Version)
2. Both Apps won’t open because I had not ROOTED the phone
Root the Phone
1. I used “Pete's Motorola Root Tools.EXE” file to ROOT the phone
2. Followed step by step as mentioned here http://www.androidauthority.com/how-to-root-motorola-atrix-4g-35233/
Flash ClockworkMod Recovery
1. I used ROM Manager to do this as when you try to do anything in ROM manager it prompts to do this. The version of this is 5.0.2.0 ( I am not sure what is this for why we have to do this)
Unlocking the Bootloader
1. What I learned is, to unlock the bootloader, we have to first flash the phone with the SBF file
a. Installed RSDLite5.3.1.msi
b. Loaded the file 4547-fix-try2.sbf (Downloaded from http://forum.xda-developers.com/showthread.php?t=1136261)
c. Boot the phone with Power+volume UPPER key pressed till "Starting RSD protocol support" comes up
d. Connect to the Laptop and Hit Start button in RSD Lite Program
e. It Did Throw an error saying “FAIL” after showing the following message
i. Failed to boot: error 0x1000'( not word for word). There will also be a list of boot options like Fastboot, RSD, Recovery, etc. And it says Starting Fastboot Protocol
2. Then comes unlocking the phone
a. Though I had the previous error message, it still had the Fastboot Protocol loaded
b. I went to the FASTBOOT folder in command prompt of my laptop executed the following to unlock the phone which worked perfectly as I see the “Unlock” on the left hand corner when phone boots
c. fastboot oem unlock (it gave me the code) then I used the code to unlock
d. fastboot oem unlock #######
e. fastboot reboot
3. Installing the recovery IMG
a. I had downloaded the Recovery IMG file (recovery-atrix5.img) from http://forum.xda-developers.com/showthread.php?t=1204500
b. Booted the phone into Fastboot mode (turn off phone, hold power and volume down key until 'fastboot' appears then use volume up to select so it says 'starting fastboot protocol support').
c. From the CMD promnt and FASTBOOT directory I used fastboot erase recovery
d. Then I executed fastboot flash recovery recovery-atrix5.img (Note: I didn’t rename the file to recovery as suggested by some people)
e. Then gave fastboot reboot to restart.
4. Booting into Recovery mode (This is where I have the problem)
a. The phone is not booting into recovery it’s not going past the Android and yellow Triangle screen
b. I re-flashed the phone same SBF file (this time it was a success showed in the RSD Lite Program), re-installed the same IMG file after renaming to recovery.img
c. Also tried with a different IMG from the same link (recovery-blue-atrix5.img) but no luck
d. Also deleted the file install-recovery.sh from ./etc/ folder (bought the app root manager to delete the file) and then push the recovery.img, no luck
e. Some people said to TAP the bottom right corner while on that screen, did that but nothing is happening
f. Then I saw a note to press both the Volume Keys at the same time, this works but in this mode the cursor (I mean the selection) on the phone doesn’t go to the First TWO (i and iii) shown below, it allows me to select any of the last FOUR (v, vi, vii, viii).
i. Android System Recovery <3e>
ii. <EMPTY LINE >
iii. Android System Recovery utility
iv. <EMPTY LINE >
v. Reboot System now
vi. Apply update from sdcard
vii. Wipe data/factory reset
viii. Wipe cache partition
g. Using the above option I did factory reset but sill no results.
5. Current condition of the phone
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
First of all, I applaud your effort in giving the a very comprehensive description of your issue.
Second, it seems you are having issues with installing a custom recovery because the recovery you're describing is still the stock recovery. I'll look around and see if I can find something that might help.
jhakash said:
4. Booting into Recovery mode (This is where I have the problem)
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
Click to expand...
Click to collapse
---------- Post added at 11:31 AM ---------- Previous post was at 11:28 AM ----------
Have you tried re-installing the CWM from RomManager through RomManager? And then boot into recovery from within the app?
---------- Post added at 11:40 AM ---------- Previous post was at 11:31 AM ----------
EDIT: This might seem trivial, but is "USB Debugging" turned on?
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Glad I can help, also, I think it's recommended to use the RomManager recovery for CM7 so good thing it worked.
jhakash said:
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Click to expand...
Click to collapse
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
If you downloaded the CWM zip file for the romracer recovery and as long as RomManager's recovery is working then, yes, you can.
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
ghost_og said:
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
Click to expand...
Click to collapse
live4nyy said:
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
Click to expand...
Click to collapse
Woops, I should have read more carefully. It's best to remove the file first and then flash the recovery.img, or else the script will install the stock recovery on boot. That would make stock recovery the current one on the phone at the time of the script getting deleted.
I would double check and make sure /system/etc does not have install-recovery.sh. If it is not there, then proceed to the fastboot steps and reflash the recovery.img again. It should stick this time.
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
jhakash said:
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
Click to expand...
Click to collapse
I just checked out my girlfriend's stock, locked, unrooted Atrix and she actually has install-recovery.sh in both /etc and /system/etc. Her file manager does not alphabetize anything in either folder, so I almost overlooked the second one.
If you're already on CM7, then you probably won't need to worry anymore. They have an entirely different set of start up scripts in that folder. Welcome to the community!
At this point I do not know enough to help you any further with this issue. All I knew about is the file that needs to be removed that @ghost_og has mentioned. But if you can flash it from RomManager and access CWM from there as well then I guess that's a good enough workaround for now.
Does anyone else have any idea why the stock recovery cannot be removed?
jhakash said:
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
Click to expand...
Click to collapse
I am good to go now, everything seems to be functioning well after flashing CM7 ROM, no more recovery issues, and the Stock recovery is gone now.
Appreciate for all the info you guys provided, it helped a lot. Have a great day and Merry Christmas.
Regards
Jhakash
So I have been trying to root my samsung phone but it has not been working. I tried downloading towel root, but it says that my phone is not supported. My phone is running build number KOT49H.I545VRUFNG6 and android 4.4.2 with kernel version 3.4. I have tried using Odin 3.09 to flash the NG5 build number to see if towelroot would work with that, but when I plugged my phone into my computer and tried going into download mode on my phone, it would not work. I already factory reset my phone twice to see if that would work, but it has not. Are there any other ways to root my phone, or am I doing something obviously wrong that is easy to fix? Any help would be appreciated.
hamglass - TowelRoot won't root NG6; you will continue to receive that "not supported" error message every time unless you downgrade. Go to this link below, and then scroll down until you find the section I pasted below the link. You'll want to download the second file, the NC5 rar, then follow the steps prescribed.
______________________
http://forum.xda-developers.com/showthread.php?t=2720163
All you need to do is download one of the following 2 all in one upgrade rar files:
I545VRUFNC2-AIO-incl-modem-hlos-nobootloaders-gogolie.rar
or
I545VRUFNC5-AIO-incl-modem-hlos-nobootloaders-gogolie.rar
Each .rar file when unpacked (NC2 or NC5 .rar files must be unpacked!) contains the following apps / odin flashable images:
Odin 3.10 (The newest and best option for Odin.)
SuperSu 1.94 (IN both a flashable thru Safestrap .zip and a .apk - thanks to Chainfire)
SafeStrap 3.72 (Thanks to Hashcode)
SeLinux Permissive Enabler / Mode Changer 1.2 (Thanks to MrBIMC)
TowelRoot v2 (Huge Thanks to geohot)
Android Terminal Emulator v1.0.53.apk
and finally...
I545VRUFNCx-AIO-incl-modem-hlos-nobootloaders-gogolie.tar
YOU CAN KEEP THE ODIN PROGRAM AND FLASHABLE FILE ON YOUR COMPUTER BUT MOVE ALL APKS TO PHONE OR SDCARD 1ST.
which is the magic file you select in Odin under AP slot and press flash to upgrade without bootloaders. This is a modified Odin image I made that also includes a .pit for mapping itself and a modem/hlos so its essentially a 1 and done file! You might need to boot into recovery and do a data wipe if you receive any FC's or issues on 1st boot (then restart and should be good to go). This is a no-wipe odin flashable image with no bootloaders or other crap just firmware and system.img and modem.
Directions to enable Root on NC2 or NC5 stock ROM & to get SafeStrap fully working:
1. Flash the odin image in AP slot for either system you want to upgrade to. (NO BOOTLOADERS OR GARBAGE FLASHED!)
2. Boot up system. If any errors occur restart to recovery (vol-up and power) then wipe data and restart. Or wipe data before flashing!
3. Once booted open TowelRoot.apkl and install and run the app. Then click on the T logo/gray box to root 4.4.2! NO REBOOT REQUIRED!!! [EisBlade: not mentioned is that it's necessary to click the box in settings to allow installs from unknown sources. Do that then return and retry install of TowelRoot apk.]
4. Now open the SeLinux Permissive Enabler / Mode Changer 1.2.apk and install the app. Open the application and click the "Permissive" box.
5. Next install Safestrap and open the app. Click install Recovery once booted. Then you can flash SuperSu .zip like normal in Safestrap. You can also also install from the Playstore or from the .apk in the AIO .rar file. However SuperSu isnt necessary its useful if you intend on controlling your ROOT.
6. Finally for a custom ROM you would reboot to Safestrap and install it in the Main/Stock Slot. Keep root by following any ROM install with SuperSu.zip!!!
7. Enjoy the easiest upgrade method known to man. Be sure and donate or thank, me or one of the fine developers mentioned above.
Hello everyone, my phone is samsung note 10 plus, I have twrp installed and rooted with magisk, I'm on Android 9, I somehow lost root, have no idea how, I'm very careful not to allow updates or google to install something there might affect my root.
when I go to magisk I'm getting the image that I've attached, when I click on install magisk, download the zip file and try to install it I get an an error as show in the 2nd image, saying unsupported/unknown image forma. I've also attached the log file. Is there any way for me to fix this without flashing the rom and start from scratch? Can I repair it somehow, maybe with TWRP?
Thank you all in advance
you have boot.img of the device?
i thought you can only install magisk in 2 way by flashing boot.img unto magisk or flashing magisk.zip unto TWRP as recovery partition
#edit how did you install magisk in the beginning? thats how you will install it again
there a chance you will get your device brick if you install magisk wrong way (A/B partition) but since you already install it previously just reinstall it back
Hmmm, where should I have the boot. Img you mean as if I backed it up on my pc? Or I can download it and use it?
Now I'm confused :/
Before i explain i don't take responsibility for any damages caused on your device if you decided to follow my tutorial .
So basically there's 2 way to install Magisk
• Image Patching - Basically this is what most people do they find stock boot.img and recovery.img for there devices
1. Copy the Stock boot.img or recovery.img to your device
2. Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock boot or recovery image file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Now pull the magisk_patched.img with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot.img or recovery.img to your device and reboot.
For most devices, here is the fastboot command:
fastboot flash boot magisk_patched.img or
fastboot flash recovery magisk_patched.img if you are patching a recovery image
Now you are rooted
•Custom Recovery - This is when you do not have Stock boot.img or recovery.img for your device
( High Chance Of Phone Getting Bricks )
1. Download and install the latest Magisk Manager
2. Download Magisk.zip (https://github.com/topjohnwu/Magisk/releases/) choose the Latest Release
3.Now reboot to recovery (TWRP, CWM ... ETC)
if you use stock recovery it should say "apply update via sdcard"
then just choose Magisk.zip
4. Now if you have TWRP just click Install and choose Magisk.zip
5. wait for the process
6. Now you are Rooted (hopefully xD :fingers-crossed
ineedroot69 said:
Before i explain i don't take responsibility for any damages caused on your device if you decided to follow my tutorial .
So basically there's 2 way to install Magisk
• Image Patching - Basically this is what most people do they find stock boot.img and recovery.img for there devices
1. Copy the Stock boot.img or recovery.img to your device
2. Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock boot or recovery image file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Now pull the magisk_patched.img with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot.img or recovery.img to your device and reboot.
For most devices, here is the fastboot command:
fastboot flash boot magisk_patched.img or
fastboot flash recovery magisk_patched.img if you are patching a recovery image
Now you are rooted
•Custom Recovery - This is when you do not have Stock boot.img or recovery.img for your device
( High Chance Of Phone Getting Bricks )
1. Download and install the latest Magisk Manager
2. Download Magisk.zip (https://github.com/topjohnwu/Magisk/releases/) choose the Latest Release
3.Now reboot to recovery (TWRP, CWM ... ETC)
if you use stock recovery it should say "apply update via sdcard"
then just choose Magisk.zip
4. Now if you have TWRP just click Install and choose Magisk.zip
5. wait for the process
6. Now you are Rooted (hopefully xD :fingers-crossed
Click to expand...
Click to collapse
Thank you very much.
OK, I tried method 2 and didn't work. I downloaded my stock firmware and I have the image file, I can try the first one to place the image in the root of the phone, patch the file with magisk and reflesh it with Odin?
Will I lose all my stuff on the phone by doing this? Thank you
i remember using odin back in 2012 for my samsung galaxy y i didn't know people still using that thing
i search your device on google and it said samsung provide the kernel for it ( https://www.xda-developers.com/samsung-galaxy-note-10-kernel-source-code/amp/ ) thats a good start for rooting your device try looking for it
also visit https://forum.xda-developers.com/galaxy-note-10 it is dedicated section for your device model which means all threads and post are for your device model
ineedroot69 said:
i remember using odin back in 2012 for my samsung galaxy y i didn't know people still using that thing
i search your device on google and it said samsung provide the kernel for it ( https://www.xda-developers.com/samsung-galaxy-note-10-kernel-source-code/amp/ ) thats a good start for rooting your device try looking for it
also visit https://forum.xda-developers.com/galaxy-note-10 it is dedicated section for your device model which means all threads and post are for your device model
Click to expand...
Click to collapse
Im already rooted....
Im having issues how to fix the root as i somehow don't have it any more and i don't want to reflash my rom if I'll lose all my stuff on the phone. Im looking how to fix the root.
drazenm said:
Im already rooted....
Im having issues how to fix the root as i somehow don't have it any more and i don't want to reflash my rom if I'll lose all my stuff on the phone. Im looking how to fix the root.
Click to expand...
Click to collapse
He's just saying to re-root it... If you lost root it's more than likely gone and you'll have to do whatever you did to gain root in the beginning. I constantly backup all my apps, data, pictures and everything to my little USB OTG thumb drive and to my laptop. I do this daily because many times a factory reset is what has to happen depending on what's going on. You can grab a Samsung micro sdcard 128 GB for $18-$19 or so online or thumb drives like I have a SanDisk 128gb.. it was $14. Just some thoughts for moving ahead so you don't have to go through this again. Lots of good suggestions here. If I were you I'd hit the "thanks" button on whenever took time to stop and search for answers to your issue. That's what we do here on xda. I could care less about racking up "thanks" count just throwing that out there so that you know..
Good luck on getting her all fixed. The note 10 is a real gem!
Sent from my marlin using XDA Labs
flash713 said:
He's just saying to re-root it... If you lost root it's more than likely gone and you'll have to do whatever you did to gain root in the beginning. I constantly backup all my apps, data, pictures and everything to my little USB OTG thumb drive and to my laptop. I do this daily because many times a factory reset is what has to happen depending on what's going on. You can grab a Samsung micro sdcard 128 GB for $18-$19 or so online or thumb drives like I have a SanDisk 128gb.. it was $14. Just some thoughts for moving ahead so you don't have to go through this again. Lots of good suggestions here. If I were you I'd hit the "thanks" button on whenever took time to stop and search for answers to your issue. That's what we do here on xda. I could care less about racking up "thanks" count just throwing that out there so that you know..
Good luck on getting her all fixed. The note 10 is a real gem!
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
I can re root it, that's not the problem, i can do it with the patched magisk boot image through Odin, im asking if that's gonna wipe off everything on my phone. Because i can't backup certain things without titanium backup, and titanium requires root access. Thank you for your help and everyone's else's im well aware and grateful for the attempts, suggestions etc.
no it's not gonna wipe anything thats why magisk is called "systemless" . It will essentially modify the system without actually modifying it.
if you flash magisk_patched.zip nothing noticeable will happen except you will have root access
all your installed application will be there
also i notice this some people actually copy magisk_patched.zip thats really bad idea you need to let Magisk generate it.
For example you have 2 phones same model and same build version .
You generate magisk_patched.zip on the phone A
then decided to copy magisk_patched.zip into phone B ofcourse it will still works
but since you just copy it and didnt let magisk generate it . It would not make backup for boot or recovery partition
if you uninstall Magisk on your phone B .There is really high super ultra mega chance of your phone getting bricks. Also it would not revert any changes done on the period while Magisk is installed
ineedroot69 said:
no it's not gonna wipe anything thats why magisk is called "systemless" . It will essentially modify the system without actually modifying it.
if you flash magisk_patched.zip nothing noticeable will happen except you will have root access
all your installed application will be there
also i notice this some people actually copy magisk_patched.zip thats really bad idea you need to let Magisk generate it.
For example you have 2 phones same model and same build version .
You generate magisk_patched.zip on the phone A
then decided to copy magisk_patched.zip into phone B ofcourse it will still works
but since you just copy it and didnt let magisk generate it . It would not make backup for boot or recovery partition
if you uninstall Magisk on your phone B .There is really high super ultra mega chance of your phone getting bricks. Also it would not revert any changes done on the period while Magisk is installed
Click to expand...
Click to collapse
Thanks for the help, please correct me if im wrong.
Im supposed to copy the AP . md5 file to the root directory of my phone, patch it with magisk, get the patched file, copy it on the pc, connect phone to the pc, get it into download mode, flash the patched file with Odin and that should be it?
Or maybe i can do it with twrp?
Any suggestions?
drazenm said:
Any suggestions?
Click to expand...
Click to collapse
1. Install the latest Magisk Manager
2. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
3. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
4. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck "Auto Reboot" in Options!
5. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
6. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
7. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
8. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
9. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
10. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
11. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
12. Voila! Enjoy Magisk
credit to @Magisk github
you can read the full tutorial here https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
ineedroot69 said:
1. Install the latest Magisk Manager
2. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
3. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
4. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck "Auto Reboot" in Options!
5. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
6. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
7. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
8. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
9. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
10. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
11. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
12. Voila! Enjoy Magisk
credit to @Magisk github
you can read the full tutorial here https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
Click to expand...
Click to collapse
Thanks so much for your help, but i just want to get root back on my phone as i had it rooted already, i dont want to wipe off everything and lose my stuff. There are things that i can only backup with titanium backup, which i can't use now without root privileges :/ can i repair root somehow?
how did you lose your root anyway?
your Android OS updated?
you can try restoring apps with titanium backup but i don't think it will restore Magisk being installed again and gaining root access
ineedroot69 said:
how did you lose your root anyway?
your Android OS updated?
you can try restoring apps with titanium backup but i don't think it will restore Magisk being installed again and gaining root access
Click to expand...
Click to collapse
I didn't do the update, but something did mess up the root aa you can see on the photos that I've attached at the beginning of the topic. I just want to reroot my phone again but not to loose all my current stuff on it.
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
ineedroot69 said:
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
Click to expand...
Click to collapse
thank you for taking your time to help me out, i appreciate it.
here is the link to the firmware file:
https://androidfilehost.com/?fid=6006931924117937015
inside are these files:
AP_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_low_ship_meta_OS9.tar.md5
BL_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_low_ship.tar.md5
CP_N975FXXU1ASH5_CP13587367_CL16618471_QB25409313_REV01_user_low_ship.tar.md5
CSC_OMC_OXM_N975FOXM1ASH5_CL16618471_QB25349308_REV01_user_low_ship.tar.md5
HOME_CSC_OMC_OXM_N975FOXM1ASH5_CL16618471_QB25349308_REV01_user_low_ship.tar.md5
ineedroot69 said:
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
Click to expand...
Click to collapse
Any luck?
drazenm said:
Any luck?
Click to expand...
Click to collapse
sorry for late reply i'm kinda busy but to make it easier on my part (downloading 5GB file would take me 5 hours) can you just upload the following ?
AP_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_ low_ship_meta_OS9.tar.md5
BL_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_ low_ship.tar.md5
CP_N975FXXU1ASH5_CP13587367_CL16618471_QB25409313_ REV01_user_low_ship.tar.md5
How to use magisk to twrp from 2.3.5 gingerbread without a computer?
@Didgeridoohan
Do you think its possible to flash twrp from a terminal emulator? Or what are my options?
If you really can't get a hold of a computer you might be lucky with an app like Franco Kernel Manager, Flashify, etc. Problem is that most apps likely won't support or be compatible with that ancient version of Android or whatever root you currently have installed. And, you're also risking bricking your device if you don't have access to a computer...
I really think your best bet is to somehow get access to a computer. Friend/school/work/something...
If you can't install stuff on that borrowed computer you could create a bootable USB with a Linux distro and run everything from there. Linux Mint is quite user friendly, they've got good documentation on how to get things running with a Live Boot USB, and it's not too hard to get adb & fastboot up and running.
Ill try and get a hold of a computer because nothing seems to work on 2.3.5
@Didgeridoohan
I had rooted using framaroot but after a factory reset it wont install supersu or superuser to my app drawer, can you give me a suggestion? Btw im using my xbox one to type this.
@chris1892006
don't waste your time with this: Magisk works only on Android 5.0 and above.
jwoegerbauer said:
@chris1892006
don't waste your time with this: Magisk works only on Android 5.0 and above.
Click to expand...
Click to collapse
thanks so do u know if its possiblle to flash a twrp.zip using terminal on 2.3.5?
chris1892006 said:
thanks so do u know if its possiblle to flash a twrp.zip using terminal on 2.3.5?
Click to expand...
Click to collapse
Is it so hard to read posts carefully?
I found this https://www.youtube.com/watch?v=-YAKGRblIuw
dd Install Method (Requires Root):
Download the latest image file (.img) from the download link above. Place it in the root of your /sdcard folder and rename it to twrp.img. Run the following commands via adb shell or a terminal emulator app:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p9
What part of the command do i change for a yp-g70 venturi? Also can i extract my twrp 2.8.0.0.zip and get the .img out of it or can i flash the .zip?
This what i used to flash cwm/ entropys daily driver kernel
https://forum.xda-developers.com/showthread.php?t=1445840
su
dd if=/sdcard/zImage of=/dev/block/mmcblk0p11
Well i got cwm installed! Now i just need to flash twrp and then a rom
chris1892006 said:
... Now i just need to flash twrp and then a rom
Click to expand...
Click to collapse
Notice, that for Lollipop and up to get it running smoothly, you need a device with minimum 2GB RAM and at least 2GHz dual core processor - what since Android 4.4+ must be a ARMv7 one.
jwoegerbauer said:
Notice, that for Lollipop and up to get it running smoothly, you need a device with minimum 2GB RAM and at least 2GHz dual core processor - what since Android 4.4+ must be a ARMv7 one.
Click to expand...
Click to collapse
Thanks i had 4.4.4 up and running but tried flashing 5.1.1 lollipop on cwm and it corrupted the bootloader. Now i cant get into recovery because twrp wouldnt flash over cwm, i tried to flash twrp 2.8.0.0 & it succeeded yet didnt work after a reboot, why? I read the op but i still cant figure out why it didnt work after a reboot? Still remained cwm.
https://forum.xda-developers.com/galaxy-player/development/recovery-twrp-v2-8-0-0-t2867742
http://www.meticulus.co.vu/p/yp-g70.html
@Didgeridoohan
How do i flash twrp over cwm?
Hey... Look at that, you had some progress. Nice.
I've never used CWM, so I wouldn't know.... Sorry.
@chris1892006
Have you backed up stock recovery IMG through e.g. Flashify app before installing a custom recovery by means of CWM ? Do remember that restoring a backup will essentially wipe any changes made after that backup.
If so then
1. you can restore or flash stock recovery IMG through Fastboot to get CWM out of your system.
2. you can install through TWRP any custom recovery IMG of your choice.
jwoegerbauer said:
@chris1892006
Have you backed up stock recovery IMG through e.g. Flashify app before installing a custom recovery by means of CWM ? Do remember that restoring a backup will essentially wipe any changes made after that backup.
If so then
1. you can restore or flash stock recovery IMG through Fastboot to get CWM out of your system.
2. you can install through TWRP any custom recovery IMG of your choice.
Click to expand...
Click to collapse
thanks only problem is they only make a .zip for twrp for my device... I don't know how to flash it.
That's a really old android version, I'm not sure if it's possible. If you don't have access to a PC, try to ask a friend if they could do it for you, just to be safe. Trying to modify stuff within android, especially on such an old version, with probably unsupported software could result in a bricked device.
Thanks but I finally got TWRP and Lollipop 5.1.1 installed it took an ADB Sideload from a PC to sideload the twrp.zip file for my device and now I'm up and running and very happy to say the very least. Sure I bricked it 3 times in the process but was always able to recover using ODIN and having the proper files on hand.
Now im having an issue with xda on the device where the xda app wont let me sign in and the browser will sign me in but go right back to the sign in page again, idk how to fix it?
I install a dalvik cache wiper with root required and it corrupted the recovery again. So I figured out the exact steps to get this device working perfectly again. Firstly the twrp folder on the external sd card has to be renamed TWRP because it has extra strange characters after the TWRP. Now we know how to restore our backup, we can start by ODIN back to stock, then Framaroot v1.4.1 root the device then download entropys daily driver kernel cwm, the flash it via terminal emulator, reboot, then you have to install meticulous carbon 4.4.4 to fix the partitions and update the cwm to adb sideload the twrp. So you can then flash Meticulus Carbon 5.1.1 and both updates and 5.1.1 pico gapps. Good to go. Meticulus made the kernel overclock to 1.7ghz and it runs pretty darn good honestly. I modded the build.prop vm dalvik heap limit to 384m from 128m to get some extra performance out of it.