Hello everyone,
I want to share my experience with rooting (n00b). So for the first time ever, I managed to root my g900t and my p-600 note --needless to say, I was very excited. When everything checked out and Root Checker told me that I was indeed rooted, the first thing I did was going to Youtube to see what I could do first.
The very first thing that came up was to create a Custom Recovery...fair enough. I watched multiple videos that guaranteed to install the CR "easily". Well, I think I'm an idiot because I couldn't get anything to work.
I tried TWRP, CWM, Philz Touch and TWRP and Philz both loaded on my recovery boot but I still kept getting messages on Rom Manager that I didn't have a custom recovery. At times I also got a lot of errors. I not only tried to get information from the forum but their respective sites and matching my device, installing it through flash & Odin--no luck.
Anyways, I soft-bricked both my g900t and my p600 and after reading hundreds of posts here and other forums and spending all day, I managed to get them running again.
Right now, I'm thankful that I have both devices running and rooted but I still don't know if I have a custom recovery and frankly, I'm scared to try it again. How important is it to get a CR?
By the way, is it bad that all those bad CRs that I installed are still there (if they are)?
I read the rules and also a a lot of forum posts with different variations of CRs for my devices with no luck.
For reference:
Galaxy s5 (5.1.1) Rooted SM-G900T
Samsung Note 10.1 (5.1.1) (Wi-fi) Rooted SM-P600
Thanks guys!
Flashing TWRP through ODIN is very simple - lots of guides out there, but here are some steps:
- Install Samsung Mobile Driver
- Download and unzip ODIN 3 (e.g, 3.1.0.7) to a directory
- Download twrp-2.8.7.0-klte.img.tar from twrp.me
- Boot phone into Download Mode (Vol Down - Home - Power), follow instruction to get to the download mode
- Connect phone to PC, wait for the drivers to be ready
- Start Odin, wait for "Added" message to show up
- Click AP and choose the TWRP tar file
- Go
Sometimes a trick is to uncheck "auto reboot", then flash it twice. That is, flash once, when completely done ("success" on Odin), disconnect and remove/replace battery, power up to boot mode again, then flash again. This is rarely needed but I've had to do this for modem flash once or twice in the past.
Alternatively, you can flash it on the phone from a terminal/cmd shell (lots of apps to choose from on Google Play), and if you have twrp.img extracted to /sdcard, you can do this (again, on the phone):
> su
# dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
The dd method is also doable from ADB shell, but that requires ADB to be set up on the PC.
Hope this helps - I wrote the steps the above from memory but others can correct me I stated anything inaccurately.
EDIT: there are also apps that can install custom recovery, such as Flashify, TWRP manager, ROM Toolbox, Nandroid Manager, etc. Of course, root is required.
many thanks
lost_ said:
Flashing TWRP through ODIN is very simple - lots of guides out there, but here are some steps:
- Install Samsung Mobile Driver
- Download and unzip ODIN 3 (e.g, 3.1.0.7) to a directory
- Download twrp-2.8.7.0-klte.img.tar from ]
- Boot phone into Download Mode (Vol Down - Home - Power), follow instruction to get to the download mode
- Connect phone to PC, wait for the drivers to be ready
- Start Odin, wait for "Added" message to show up
- Click AP and choose the TWRP tar file
- Go
Sometimes a trick is to uncheck "auto reboot", then flash it twice. That is, flash once, when completely done ("success" on Odin), disconnect and remove/replace battery, power up to boot mode again, then flash again. This is rarely needed but I've had to do this for modem flash once or twice in the past.
Alternatively, you can flash it on the phone from a terminal/cmd shell (lots of apps to choose from on Google Play), and if you have twrp.img extracted to /sdcard, you can do this (again, on the phone):
> su
# dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
The dd method is also doable from ADB shell, but that requires ADB to be set up on the PC.
Hope this helps - I wrote the steps the above from memory but others can correct me I stated anything inaccurately.
EDIT: there are also apps that can install custom recovery, such as Flashify, TWRP manager, ROM Toolbox, Nandroid Manager, etc. Of course, root is required.
Click to expand...
Click to collapse
Thank you lost_,
my issue wasn't rooting the devices --they both are, it's getting a custom recovery installed. Neither TWRP nor CWM can find a recovery for my device (g900t). I've looked at countless posts with the same luck. At one point at recovery I had TWRP, which from what I was reading, it meant that I had a custom recovery, right? but again, TWRP and CWM say that I don't have one installed and when I tried to reboot out of recovery it would go into a boot loop forcing me to re-root my device. Basically, I'm stuck at this point and all I really want is to backup all my apps so that they run from my SD card, no coding, no custom roms but it gives me issues. Thanks again.
molotovgod said:
Thank you lost_,
my issue wasn't rooting the devices --they both are, it's getting a custom recovery installed. Neither TWRP nor CWM can find a recovery for my device (g900t). I've looked at countless posts with the same luck. At one point at recovery I had TWRP, which from what I was reading, it meant that I had a custom recovery, right? but again, TWRP and CWM say that I don't have one installed and when I tried to reboot out of recovery it would go into a boot loop forcing me to re-root my device. Basically, I'm stuck at this point and all I really want is to backup all my apps so that they run from my SD card, no coding, no custom roms but it gives me issues. Thanks again.
Click to expand...
Click to collapse
No offense intended, I think you're lost and confused. My post was never about rooting. I did understand you were rooted already. I was outlining how to install a custom recovery, which TWRP and CWM are. Yeah, if you're having a hard time sorting things out based on what I outlined, I don't know how else to get you going. Perhaps start over with your research and read up again on some basic Android 101 (not a HOWTO but an explanation on what is what). Good luck!
ps: this thread should be on the Q&A forum, but we're all helpful and friendly here and you should ask specific questions on that forum instead.
if you're using stock samsung recovery & its stock android, they will overwrite what you just flashed when they boot
odin->flash twrp WITHOUT reboot option->remove battery->put battery->turn on phone directly into recovery, you should see TWRP & you'll be able to flash whatever you want from here, i have no idea what happens if you boot to stock after this since i use CM
i came from stock 4.4 november 2014, used odin 3.07 & https://dl.twrp.me/klte/ 2.8.7.0
kn00tcn said:
if you're using stock samsung recovery & its stock android, they will overwrite what you just flashed when they boot
odin->flash twrp WITHOUT reboot option->remove battery->put battery->turn on phone directly into recovery, you should see TWRP & you'll be able to flash whatever you want from here, i have no idea what happens if you boot to stock after this since i use CM
i came from stock 4.4 november 2014, used odin 3.07 &TWRP 2.8.7.0
Click to expand...
Click to collapse
I have the same phone and cannot flash custom recovery either, as I am a linux user I used heimdall and here is my output
Code:
[[email protected] Downloads]# heimdall flash --RECOVERY twrp-2.8.7.0-klte.img --no-reboot
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
[[email protected] Downloads]#
I flashed my wife's Samsung Galaxy S3 (GT-i9300) and my Galaxy Tab 2 (GT-P5113) a successfully using the procedure described in each device wiki in cyanogenmod page, but same procedure in my phone fails.
My Samsung Galaxy S5 (GT-G900T) is running Samsung's stock Android 5.1.1 (not rooted btw) and stock recovery.
Can you spot what I am doing wrong? Thank you in advance.
pablomino said:
I am a linux user I used heimdall
Click to expand...
Click to collapse
https://github.com/Benjamin-Dobell/Heimdall/issues/209 i couldnt use heimdall either, but there is a patch in that thread that might work for you, you just have to recompile yourself if they didnt update the linux binary
if that still doesnt work, i think you should just use virtualbox to run windows7 & odin with whatever the option is called to have usb pass-through/direct usb access
kn00tcn said:
if that still doesnt work, i think you should just use virtualbox to run windows7 & odin with whatever the option is called to have usb pass-through/direct usb access
Click to expand...
Click to collapse
I moved to a physical Win7 PC, it didn't work either, same error. Could it be because the device is already on Android 5?
Thank you a lot.
Code:
Microsoft Windows [Versión 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.
C:\>cd heimdall
C:\heimdall>heimdall version
v1.4.0
C:\heimdall>cd Drivers
C:\heimdall\Drivers>zadig
C:\heimdall\Drivers>zadig
C:\heimdall\Drivers>cd ..
C:\heimdall>heimdall flash --RECOVERY twrp-2.8.7.0-klte.img --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
C:\heimdall>
---------- Post added at 08:42 PM ---------- Previous post was at 08:13 PM ----------
kn00tcn said:
you just have to recompile yourself
Click to expand...
Click to collapse
Anyway I will try compiling the tool from source, I will update with my results. Thank you lot.
pablomino said:
I moved to a physical Win7 PC, it didn't work either, same error.
Click to expand...
Click to collapse
i said to use odin, i have done it several times already, although some people say a newer odin is needed for lollipop based samsung installations... i mentioned 3.07 earlier, today i did 3.10.7 with the latest G900TUVS1FOL1 complete package from sammobile so i can update my baseband & bootloader easily, then once again odin->flash twrp without reboot->remove battery->boot into twrp recovery->flash CM
heimdall does not have the code update that supposedly fixes the PIT error in the official windows binaries, so heimdall will never work on windows unless you compile the fix yourself
(if using odin, always check the exe on virustotal, always get it from someplace reliable like sammobile or an active thread here rather than google)
kn00tcn said:
i said to use odin
Click to expand...
Click to collapse
This solved my problem, thank you a lot.
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.
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Chegger said:
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Click to expand...
Click to collapse
Not the solution, but maybe a cause... did you root your device?
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
harddisk_wp said:
Not the solution, but maybe a cause... did you root your device?
Click to expand...
Click to collapse
Yes I did.
I also thought that was the problem.
delox88 said:
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
Click to expand...
Click to collapse
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Chegger said:
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Click to expand...
Click to collapse
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
harddisk_wp said:
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
Click to expand...
Click to collapse
At least you know this stuff that's half way trough.
I will post this in the original root thread since I already posted the issue there and they are now replying ( I will mention you).
http://forum.xda-developers.com/general/rooting-roms/root-achieved-cat-b15q-t2822015/page11
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've witten you a PM - please send me your original ROM - or could you send me a link where i may download it.
huedlrick said:
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
Click to expand...
Click to collapse
Another one here! Were you able to use link2sd after rooting the phone? Link2sd gave me a mount error when I tried to mount my sd card's 2nd ext3 partition.
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile
1.1019.000 Recovery
Original 1.1019.000 update
Scatter file
To flash the phone you only need the bootimg, recovery,android and scatterfile.
(Edit: I dont have google drive anymore)
bigal1337 said:
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile https : // drive . google . com /file/d/0ByVAMsMZdC8bdEIxWlpBeXBHNUE/view?usp=sharing
1.1019.000 Recovery https : // drive . google . com /file/d/0ByVAMsMZdC8bVXU2RzBGalV0S1U/view?usp=sharing
Original 1.1019.000 update https : // drive . google . com /file/d/0ByVAMsMZdC8bbWQ4dmhSZWVxZVE/view?usp=sharing
Scatter file https : // drive . google . com /file/d/0ByVAMsMZdC8bSkRhREEwakNhUWc/view?usp=sharing
To flash the phone you only need the bootimg, recovery,android and scatterfile.
Click to expand...
Click to collapse
Thank you very much - but how can I determine if my phone is E01/B01 without being able to boot it?
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Great and congrats.
Could you, please, describe the process and which files did you use.
Thanks.
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Can you give some hints how you unbricked it? What tools and commands have to be entered?
Best regards,
Doggy77
Uploads are not done yet. But you can prepare until I'm done... grab the driver package, spFlashTool and the 1.022 RAR from http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774.
You will need a win7 x86 machine for this to work (64-bit systems will need to disable the driver signature enforcement, but this is unreliable), and latest(!) WinRAR for unpacking.
The full backup of your device will take up ~1.5 GB, so you will need at least 3GB free and another 2GB if you also want to backup your userdata (HIGHLY RECOMMENDED).
"PMT changed for the ROM; it must be downloaded"
I'm trying to flash the files of harddisk_wp with his instructions but i keep getting the error "PMT changed for the ROM; it must be downloaded", right after I connect the phone and SP Flash Tool finishes "Download DA". I am trying with the 64bit drivers since I do not have a 32bit system, with digital signature verification disabled.
After some search, I saw in the log files that SP Flash Tool is reading the partition table on the phone and comparing it to the scatter file. There is a mismatch there and throws this exception. Now either the driver is not working correct and does not report the partition table right or there is something else going on. Anybody tried this on a 64bit system? Any ideas?
BTW the scatter file is correct for my phone. I had downloaded it myself also before the bricking and I compared it with harddisk_wp's one. They are identical.
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
walckenaerius said:
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
Click to expand...
Click to collapse
SPFT worked for me good to resurrect the phone with files from 1010 version (first firmware) raw partitions.
Phone came back to last user backup and booted fine.
I applied newer and suggested 1019 update that had bricked the phone even further into the loop of the booting logo stuck and rebooting.
SPFT tool memory scan showed that there is no NAND present. I assume that there is PRELOADER damaged. By trying to flush raw PRELOADER that was a no go area. Connection made red line on 100% and nothing happens after that.
SPFT stopped making connection via USB. Inserting the battery, power on - it didn't came back at all.
Phone is now dead black brick that on Linux shows: as MediaTek Inc. MT6227 phone.
In any case do not try to make the same mistake like me.
I will check if it works on some other Windows machine.
Not being Windows user I cannot tell if it is in USB driver or not.
Used W7 without admin pass, with MTKUsbAll driver.
Eh.
yeah what stupid thing am i doing please?
twrp2870-20150814-p4.zip
Tab 10.1 p7500 3g stock 4.0.4
Heimdall 1.4.0
Ubuntu 14.04
seems to flash fine (blue progress bar ok)
hangs when selecting recovery (VOL-+POWER, select left side icon, VOL+).
is there some way to get into recovery from Heimdall btw? adb doesn’t work in download mode afaik.
*****.********:~/Downloads/TWRP/recovery$ sudo heimdall flash --SOS recovery.img --no-reboot
[sudo] password for ******:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading SOS
100%
SOS upload successful
Ending session...
Releasing device interface...
Click to expand...
Click to collapse
CWM 6031 works! hmmmm not sure if that's ok to use or not, will have to investigate..
Smiff2 said:
CWM 6031 works! hmmmm not sure if that's ok to use or not, will have to investigate..
Click to expand...
Click to collapse
turns out CWM works ok for installing 5.1, but not 6.0.. maybe ROM specific issues, maybe not.. anyone have ideas?
error status 7 when trying to install 6.0 with CWM 6031.
i know i can hack the ROM but would prefer to get TWRP working as recommended by ROM author.
ah i may have the answer! some recovery needs 2 partitions.. SOS and HIDDEN
The recovery partition is only 5 megabytes. This is not enough space for the features of newer recovery software. This version of recovery uses the "hidden" partition to extend the recovery storage space. The hidden partition was used by official Samsung ROMs (Ice Cream Sandwich 4.0.4 and Honeycomb 3.2) to preload apps. It is not being used by most custom ROMs.
Warning: You must be careful with the hidden partition while using this recovery. Since it is a normal partition, it is possible that for whatever reason it is mounted and the recovery files deleted/modified. To protect this partition I've modified the kernel so that this partition can only be mounted as read-only. But you must be careful while using other ROMs with kernels that do not have this.
Click to expand...
Click to collapse
Hi all,
I try to replace PhilZ Touch 3 by TWRP on my (old) galaxy S2 (GT-I9100) to install LineageOS 16 ( lineage-16.0-20191006-UNOFFICIAL-i9100.zip)
I tried using PhilZ:
1) wipe data/factory reset
2)wipe cache partition
3) install zip from sdcard
but it failed and I read that TWRP should be used to do that.
I have no M$ system, only linux OS, also I get Heimdall 1.4.2 and booting in download mode I did:
Code:
$ sudo heimdall flash --RECOVERY twrp-3.3.1-0-i9100.img
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
But after reboot it's Philz is always the recovery system
Any idea of how to success?
Pierre_ said:
Hi all,
I try to replace PhilZ Touch 3 by TWRP on my (old) galaxy S2 (GT-I9100) to install LineageOS 16 ( lineage-16.0-20191006-UNOFFICIAL-i9100.zip)
Click to expand...
Click to collapse
I also followed https://wiki.lineageos.org/devices/i9100/install guide until step 7 where when I reboot the device into recovery mode I have still Philz CWM instead off TWRP.
Perhaps a solution found within the FAQ of PhilZ Touch 6.59.0
5- CMUpdater cannot flash downlaoded files
If you get a /sdcard/0 error, it means you have /sdcard set as /data/media/0 in recovery
The reason is that CM app doesn't support /data/media/0 and is faking recovery with a /sdcard/0 implementation
You still can alter the setting and force it to /data/media in Advanced menu. This will give full compatibility with cwm, CM roms and CM Updater
6- How to flash a boot.img or recovery.img file?
- Put your boot.img or/and recovery.img files under a subfolder in clockworkmod/backup on sdcards
exp: /sdcard/clockworkmod/backup/cm-10.1-nightly_20130713/boot.img
- Navigate to Backup and Restore / Custom Backup and Restore / Custom Restore Job
- Unselect all partitions except boot and/or recovery
- Select >> Start Custom Backup Job <<
- Browse to your backup location until your cm-10.1-nightly_20130713, and select any file inside it
- You are done
Click to expand...
Click to collapse
I'll try it soon
Hi everyone!
I'm using a Samsung gt-n8010. It could be done for due to the age, but maybe there is still hope.
My problem is that the tablet boots always to TWRP recovery and I can switch to download mode as well. Everything seems all right, internal storage and sd card shows exactly how they should, BUT... I can't do anything in TWRP. If I have the Keep system partition read only unticked, it still says the storage is read only and /data/media is not accessable. I can see it and access it with TWRP File manager. I tried flashing ROM and Recovery, also stockROM with Odin, but Failed. Clearing Cache, Data, Dalvik... also ends up with error. Format Data works, and also changing the partition types, but when I reboot device, it all comes back the same as before, no changes take effect. In Download mode I tried to use Adb from computer terminal, but it was stuck saying 'Waiting for device'. If Tab is in Recovery my PC shows both internal storage and sd card, but the internal storage is empty when I open it.
For details: I use Lineage OS 18.1 with TWRP 3.6.1_9-0. On my computer I use Linux Mint 20.3, but I tried with a laptop using Win10 as well, no success.
I've read many solutions on 'Unmodified system partition' or some had 0MB internal storage problem, but in my case that is different, as I have them all, but it seems all is read only and not accessable. I even tried to have the last Backup (2 month old) set using Restore of TWRP, but during the process, the tablet reboots and TWRP comes up again. I can't even turn it off, as TWRP comes up after some minutes.
Please help me somehow to be able to use the Tablet. If you need any further details, just tell me.
TWRP is not out yet on android 12, if you have it as of writing it wont be able to unencrypt your device. So all you can do is use it to install roms (YOU MUST FIRST FACTORY RESET THE DEVICE).
I also have never used odin as I have prefered adb
Code:
adb shell
/sbin/recovery --wipe_data
/sbin/recovery --update_package=SDCARD:romname.zip
adb should work in twrp?
I see your point. I intended to change/downgrade LineageOS version, but I was not successful. Now I am not able to do a factory reset either with success from TWRP, but I give a try to your adb codes. Give me some time
leathan said:
TWRP is not out yet on android 12, if you have it as of writing it wont be able to unencrypt your device. So all you can do is use it to install roms (YOU MUST FIRST FACTORY RESET THE DEVICE).
I also have never used odin as I have prefered adb
Code:
adb shell
/sbin/recovery --wipe_data
/sbin/recovery --update_package=SDCARD:romname.zip
adb should work in twrp?
Click to expand...
Click to collapse
Hi, I gave a try to that code both on TWRP and Linux terminal (from PC). But no effect First I did a FactoryWipe (successful) and went back to the Terminal each time. I tried with ROM zip and TWRP img as well, but after rebooting, TWRP 3.6.1 comes back again. I downloaded Lineage OS 17.1 (with GAPPS pico) and TWRP 3.5.0-9. It seems somehow I got stuck with that TWRP 3.6 and all I get on every attempt of flashing or wiping is it can't see '/data/media (No such file or directory)' or 'Unable to make /cache/recovery: Read-only file system'. I hope there would be a solution to get my system out of Read-only state
Nektarin87 said:
Hi, I gave a try to that code both on TWRP and Linux terminal (from PC).
Click to expand...
Click to collapse
Do you have adb installed and do you see your phone when you type "
Code:
adb devices
"
Usually its as simple as just booting into TWRP -> Factory reset then install the rom and done.
Maybe you do need odin but im pretty sure you can use adb instead like I outlined above, I hated using odin but if you find the right file it should also fix your issue.
What is the codename for your tablet? I cant find it on lineageos's site, what guide did you use its an official lineageos im assuming?
leathan said:
Do you have adb installed and do you see your phone when you type "
Code:
adb devices
"
Usually its as simple as just booting into TWRP -> Factory reset then install the rom and done.
Maybe you do need odin but im pretty sure you can use adb instead like I outlined above, I hated using odin but if you find the right file it should also fix your issue.
What is the codename for your tablet? I cant find it on lineageos's site, what guide did you use its an official lineageos im assuming?
Click to expand...
Click to collapse
Well, I have adb installed, but as my Tablet can only load in recovery it says like these:
adb devices
List of devices attached
4107cd04a2b611b5 recovery
When I load Odin or fastload mode (Download mode as tablet says) I can not list it with 'Fastboot device" command. It says 'waiting for device'.
My tablet is Samsung gt-n8010 (10.1) and I follow this thread to make changes:
LineageOS 16.0 Android 9 for GT-N8000 GT-N8010 GT-N8013 GT-N8020 FINAL VERSION EOL
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in...
forum.xda-developers.com
I had Lineage OS 18.1 installed and maybe what caused the issue is that I did not update the TWRP, or we do not have a TWRP ready for it yet, but currently I have TWRP 3.6.1_9-0 installed and stuck with. As I mentioned, on rebooting tablet always starts with TWRP, asking if I want system read only or not with an Unmodified system partition heading. I can not boot OS at all, I can go to Download mode, but Odin always failed indicating my system is read-only.
Ok yes your device is listed as recovery because it has not booted anything. I'm not sure if the commands I gave work without the system actually booting however.
After you entered adb commands there was no error text?
Also if you cant get odin to recognize your phone (RUN IT AS ADMINISTRATOR) you should figure out that first as thats a last resort fix when you really mess things up which I dont think you have yet. I think you must have something off in your configuration if its not reading anything make sure u can access another phone to rule out your pc, but get this working asap.
Usually if your device boot loops you can wipe the cache, and now days remove magisk modules.
If your device still boots straight to recovery It should be as easy as I outlined above, try not isntalling the apps/plugins after the initial rom, and again make sure you wipe cache/data before hand.
If your device boots straight to the bootloader then your left with Odin.
Man I hate video guides. But it looks good (unless he forgot to wipe) should have been as simple as that. He does not however provide you with the firmware (not rom) file that I believe you are going to need if you improperly downgraded the android a full version number. Post on his youtube and find that firmware file and fix your odin connection and flash it. If odin is also dead I have no idea but I have never in nearly 20 years had a phone fully brick even when I try to brick them. But I know it can be possible but your most likely going to recover from this.
If he doesn't respond just read more and learn, you may need some specific large file though to flash over what I believe may now be missing partitions entirely.
Maybe someone else here can help too. Good luck!
leathan said:
Man I hate video guides. But it looks good (unless he forgot to wipe) should have been as simple as that. He does not however provide you with the firmware (not rom) file that I believe you are going to need if you improperly downgraded the android a full version number. Post on his youtube and find that firmware file and fix your odin connection and flash it. If odin is also dead I have no idea but I have never in nearly 20 years had a phone fully brick even when I try to brick them. But I know it can be possible but your most likely going to recover from this.
If he doesn't respond just read more and learn, you may need some specific large file though to flash over what I believe may now be missing partitions entirely.
Maybe someone else here can help too. Good luck!
Click to expand...
Click to collapse
Hi there, I actually find some videos or instructions useful and some helped me out a lot. But as always, things can only be proper if anyone is qualified to do it or when you have the exact same issue on the device. Now back to my case...
I tried many ways, many aspects, but none helped me out. There was this good and working Samsung 10.1 gt-n8010 and one afternoon I found it turned off. When I charged it for a while I turned it on and all it could load is TWRP and I could not do anything. It seems to be working, but I could not see internal storage, while it showed all the 12 GB amount I had, so the issue is not that it shows 0 GB like in many videos. I tried to wipe cache, data, system, even change partition types, all ended with a fail saying my 'system is read only'. I also tried to use Odin and Heimdall to flash new recovery and ROM, also gave a chance to stockRom with android 4.1 or 4.4, but in all cases it said FAILED. To conclude all: I think it could be a hardware issue and as the machine is more the 10 yrs of age, it would not be a surprise, but it's a same it can't be flashed.
If anyone had a similar issue or may have suggestions I'm all ears and the thread remaines, but I am out of ideas at the moment and put my Samsung tab on the shelves.