Hello guys
I have Verizon's 4G LTE Samsung Galaxy Tab 10.1 running stock Samsung firmware (Model SCH-i905).
Recently, I have updated the device to latest ICS update via Software Update.
I am looking for a safe and an eazy to use method for rooting this device.
Any help?
Thank you!
tweetatoo said:
Hello guys
I have Verizon's 4G LTE Samsung Galaxy Tab 10.1 running stock Samsung firmware (Model SCH-i905).
Recently, I have updated the device to latest ICS update via Software Update.
I am looking for a safe and an eazy to use method for rooting this device.
Any help?
Thank you!
Click to expand...
Click to collapse
Hi Tweetatoo. I'm not saying this to be an A-hole but this information can be found with a simple search on this board.
Here's the thread you are looking for, click thanks button if it helps.
http://forum.xda-developers.com/showthread.php?t=1444714
You will only need to start from step 5. Be sure to read and follow the instructions completely.
eejimen said:
You will only need to start from step 5. Be sure to read and follow the instructions completely.
Click to expand...
Click to collapse
Excellent... but this is not working. I can flash recovery, but I can't get into recovery. When I try to flash a stock ROM with Odin it fails on system.img because the partition is too small. Heimdall fails to "to initialise protocol". I only have access to Odin, fastboot and nvflash. No adb and the device is stuck on a boot loop. Am I simply out of luck?
sgeos said:
Excellent... but this is not working. I can flash recovery, but I can't get into recovery. When I try to flash a stock ROM with Odin it fails on system.img because the partition is too small. Heimdall fails to "to initialise protocol". I only have access to Odin, fastboot and nvflash. No adb and the device is stuck on a boot loop. Am I simply out of luck?
Click to expand...
Click to collapse
What image are you trying to flash via Odin? Have you tried to go back to bone stock 3.1 (http://forum.xda-developers.com/showthread.php?t=1342995) ?
How did you get into this situation, flashed an incorrect ROM? Seems odd to have partition size errors.
muzzy996 said:
What image are you trying to flash via Odin? Have you tried to go back to bone stock 3.1 (http://forum.xda-developers.com/showthread.php?t=1342995) ?
How did you get into this situation, flashed an incorrect ROM? Seems odd to have partition size errors.
Click to expand...
Click to collapse
I tried to install CyanogenMod for the SCH-i905, but it failed to install. ROM Manager recommended the wifi ROM. I installed that and it worked without sound. I figured if one wifi ROM works, another one should too, right? Big mistake. I flashed CleanROM and have been in a bootloop ever since.
I can flash with fastboot, nvflash and Odin, but all of them fail to flash system.img. I dumped the system partition and partition information with nvflash, and it appears to be 256M. The system.img is larger than 256M in all of the ROMs I have found that can be flashed with Odin. I'm pretty sure the system.img in EG01 is 312M, but I will download it again and try to reflash after recharging the unit. There is a custom ROM with a system.img that is less than 256M, but it appears that ROM can only be flashed via recovery and I can not get into recovery.
Unless something is totally wonky, it seems like I should be able to reflash *if* I can repartition. I know how big I want the partitions to be, but I do not know how to repartition the device. PIT files are nowhere to be found. (At this point I have backups of all but the user data partition.)
I downloaded EG01 yet again and tried to flash it. The recovery.img file flashes to SOS without issue. The system.img file fails to flash to APP. Odin fails with the following output:
Code:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The following is displayed on the device:
Code:
WriteExt4Partition: Fail to OpenCompExt4![err:0xa]
DownloadPartition_odin: Fail to WriteExt4Partition![err:0xa]
Tegra_Nand_Write: Fail to DowloadPartition_odin![err:0xa]
A peek inside the tar file indicates the system.img is indeed a little over 312M. I think the flash is failing because the APP partition is only 256M. FWIW, the SOS partition is 5M and recovery.img is ~4.28M so a successful flash makes sense here.
Code:
$ tar -tvf PDA_HC31_EG01Ba_AP352081user_CP1033580_LTE20110704_0708.tar
-rwxr-xr-x 0 0 0 4485120 Jan 1 2009 recovery.img
-rwxr-xr-x 0 0 0 327200196 Jan 1 2009 system.img
-rwxr-xr-x 0 0 0 9376048 May 2 2011 cache.img
-rwxr-xr-x 0 0 0 16 May 2 2011 fusetrigger.bin
-rwxr-xr-x 0 0 0 10747904 Jun 24 2011 lte_modem.bin
-rwxr-xr-x 0 0 0 3962240 Jul 4 2011 modem.bin
-rwxr-xr-x 0 0 0 4051200 Jul 8 2011 boot.img
$
So far as I can tell, there are no tools that I can use to partition my device. I can not find any files to repartition my SCH-i905 with nvflash, Odin or fastboot. Am I simply out of luck? (Anyone who wants to help is free to PM me if that makes sense in this case.)
Had a feeling that the wrong ROM was flashed at some point; ROM manager should not be used for these tabs. As you just found out, the structure of the different variants of the 10.1 is indeed different. I'm not sure how to fix the issue, hopefully someone can chime in who does.
Sent from my SCH-I905 using Tapatalk 2
muzzy996 said:
Had a feeling that the wrong ROM was flashed at some point;
Click to expand...
Click to collapse
Twice, actually. ROM manager recommended CyanogenMod for the wifi tablet. It worked without sound, and I figured if one wifi ROM works they all should, right? Big mistake. I've been in a boot loop ever since flashing CleanROM.
muzzy996 said:
ROM manager should not be used for these tabs. As you just found out, the structure of the different variants of the 10.1 is indeed different.
Click to expand...
Click to collapse
These tablets are confusing at first, but this ordeal has taught me a lot. There should be a sticky post at the top of these forums warning people not to flash anything until they know the version of their device, and the model the ROM will run on. It should also warn about ROM manager and state "when in doubt do not flash anything".
muzzy996 said:
I'm not sure how to fix the issue, hopefully someone can chime in who does.
Click to expand...
Click to collapse
My guess is that I could restore my tablet with nvflash dumps of a working partition table. Maybe parts 2 ~ 4 (BCT, PT, EBT)? I'm not sure what the GP1 partition is. I'm also not sure if partitions like MDM or LTE need to be intact for the tablet to run. I may have wiped something out with fastboot before I figured out how all of this works (this would be after getting stuck in a boot loop.).
If someone with a working SCH-i905 is willing to work with me, I should be able to restore my tablet. If anyone is feeling helpful, please PM me.
The link to the thread is not accurate
eejimen said:
Hi Tweetatoo. I'm not saying this to be an A-hole but this information can be found with a simple search on this board.
Here's the thread you are looking for, click thanks button if it helps.
http://forum.xda-developers.com/showthread.php?t=1444714
You will only need to start from step 5. Be sure to read and follow the instructions completely.
Click to expand...
Click to collapse
Hello - I know you were not trying to be an "A-hole" as i am not either. The link you provided is to a gingerbread root (3.2)... the original post stated ICS (4.04). So though you may not have been trying to be an A-Hole.... i think you may have made yourself look like one I am off to find out how to root my SGT 10.1 LTE (SCH-i905) running ICS 4.04 - If anyone has advice on where to find a How To, please let us know. Thank you -Bryan
See here: http://forum.xda-developers.com/showthread.php?t=1888755.
You DO NOT need to flash the first link in the original post of that thread but you should download superuser using the second link and clockwork mod recovery from droidbasement.com. It is best to disable auto restart in Odin when you flash CWM because the tab will boot into android and erase CWM if you don't catch the proper key presses quickly enough once Odin flashes, so uncheck that option and monitor Odin for a successful flash. Reboot into recovery and install superuser. Get busybox installer via the Play store and install busybox. At this point you can install a root checker from play store to verify root. You will have lost cwm at this first boot into stock ICS but root will have been installed and will remain on subsequent boots from this point on.
I did not try any other kernels to see if I could find one that would allow me to keep cwm so anyone looking to do that is on their own and does so at their own risk.
This is all I remember for stock ICS since once I had it I quickly went into CM9.
Sent from my SCH-I905 using Tapatalk 2
Related
I am a complete newbie and was raised on windows 6 (yes these dinosaurs exist)-so please have patience as I have only had the sgs2 for a week!
After lurking in these forums for a couple of weeks, I rooted the S2 with chainfire's kernel I9100XWKE7_I9100XXKE4_I9100XEUKD1,tar with odin. I already had the KE7 upgrade via Kies. Then to get rid of the pesky yellow triangle I flashed with the I9100XWKE7_StockKernel
Everything seemed OK but when I tried to backup the kernel with CWM, I get to the naming of the backup screen, but then nothing happens.
I also tried to go in download mode to reflash but though ODIN detects the S2 I get stuck at;
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
The download mode shows CWM. I get the following options;
reboot system now
apply update from sdcard
wipe data factory/reset
wipe cache partition
Meanwhile in Updating application...
Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/XEU/system/'
Successfully applied multi-CSC
Why doesnt the CWM access Odin? What should I do? Is the CWM somehoe bugged and allowing me to re-flash?
Mahniex said:
I am a complete newbie and was raised on windows 6 (yes these dinosaurs exist)-so please have patience as I have only had the sgs2 for a week!
After lurking in these forums for a couple of weeks, I rooted the S2 with chainfire's kernel I9100XWKE7_I9100XXKE4_I9100XEUKD1,tar with odin. I already had the KE7 upgrade via Kies. Then to get rid of the pesky yellow triangle I flashed with the I9100XWKE7_StockKernel
Everything seemed OK but when I tried to backup the kernel with CWM, I get to the naming of the backup screen, but then nothing happens.
I also tried to go in download mode to reflash but though ODIN detects the S2 I get stuck at;
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
The download mode shows CWM. I get the following options;
reboot system now
apply update from sdcard
wipe data factory/reset
wipe cache partition
Meanwhile in Updating application...
Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/XEU/system/'
Successfully applied multi-CSC
Why doesnt the CWM access Odin? What should I do? Is the CWM somehoe bugged and allowing me to re-flash?
Click to expand...
Click to collapse
CWM and Download-mode is not the same thing
While CWM can be used to flash zip-files, you will have to use odin to flash stuff in download-mode.
To access:
Recovery-mode: Vol Up + Home + Power
Dowload-mode: Vol Down + Home + Power
seems correct, im pretty sure you use cwm whilst actually in the os.
IS what im doing correct
Have all the files needed on your pc ready to flash with odin, and make back ups with cwm of your current state and save onto sd.
In the event of a soft brick/reboot loop i can reflash custom rom and kernel, then use cwm to recover my phone to the state it was before i modded it which led to the softbrick/reboot loop etc
Thanks! That's great to know even if it makes me feel like a very red faced fool!
Why doesn;t CWM permit me to make a backup?
Further to the above, when I try to make a backup with CWM it goes into the Android system recovery (3e) with the same options;
reboot system now
apply update from sdcard
wipe data factory/reset
wipe cache partition
Mahniex said:
Further to the above, when I try to make a backup with CWM it goes into the Android system recovery (3e) with the same options;
reboot system now
apply update from sdcard
wipe data factory/reset
wipe cache partition
Click to expand...
Click to collapse
Im using VillainROM with CF-Root kernel. CWM in kernel.
When i choose to make a back up it come up with name, i select ok and it reboots into cwm and starts recovery, mounts sd card and starts backing up.
Im no pro, how are you using CWM?
Nothing different from you except am on stock Kernel and when it reboots in CWM it just gives me the options I mentioned before. It doesn't backup.
That's why I was thinking of reflashing the kernel
http://forum.xda-developers.com/showpost.php?p=14283383&postcount=3
reflash ur kernel with this one....
Why is the kernel you pointed me to around 7 MB and the I9100XWKE7_I9100XXKE4_I9100XEUKD1 kernel 508MB? What is going on here?
I flashed with the kernel you pointed me too and now CWM does backup successfully! Thanks for your wonderful help.
Any idea why the difference in size of those kernels? What am I missing?
I also have the yellow triangle again as this is non stock kernel. What kernel should I flash with to remove the triangle and keep CWM funcional?
Mahniex said:
Why is the kernel you pointed me to around 7 MB and the I9100XWKE7_I9100XXKE4_I9100XEUKD1 kernel 508MB? What is going on here?
Click to expand...
Click to collapse
Because I9100XWKE7_I9100XXKE4_I9100XEUKD1 contains more than just a kernel (which is called "zImage"):
$ tar -tvf samsung_firmware/I9100XWKE7_I9100XXKE4_I9100XEUKD1.tar
-rwx------ User/¾øÀ½ 1310720 2011-05-18 09:23 Sbl.bin
-rwx------ User/¾øÀ½ 131072 2011-05-18 09:23 boot.bin
-rwx------ User/¾øÀ½ 18485588 2011-04-08 09:57 cache.img
-rwx------ User/¾øÀ½ 480995252 2011-05-18 09:22 factoryfs.img
-rwx------ User/¾øÀ½ 10678552 2011-04-08 09:57 hidden.img
-rwx------ User/¾øÀ½ 12583168 2011-05-17 14:06 modem.bin
-rwx------ User/¾øÀ½ 667648 2011-05-18 09:22 param.lfs
-rwx------ User/¾øÀ½ 8387840 2011-05-18 09:23 zImage
The other stuff seem to be filesystem images and executables.
I have tried to mount the images:
# mount -o loop cache.img 1
mount: you must specify the filesystem type
But I do not know the filesystem type. I have tried ext2,ext3,ext4.
i think you have to just live with it as its a custom kernel. It don't really matter, its only for a couple of seconds whenever you boot your phone
That first one is firmware.
Its includes
PDA refers to the build version of the firmware
Phone refers to the baseband/modem version
CSC is the consumer specific customisation and is specific to geographical region and carriers. It contains the software packages specific to that region, carrier branding and also APN settings for data connection, MMS etc for your service provider.
The file i directed you to is just a kernel. Not a rom, i dont think the custom stock is compatible with CWM as of yet.
http://forum.xda-developers.com/showthread.php?t=1075278
http://forum.xda-developers.com/showthread.php?t=1108499
http://forum.xda-developers.com/showthread.php?t=1081368
http://forum.xda-developers.com/showthread.php?t=1103399
These 4 threads should help you with everything you need. Like I've said, only had device a couple of days and all I've done is read through these threads and read a few definitions here and there.
In answer to my own problem regarding the yellow triangle removal, here is chainfire's suggestion quoted from his own flashing guide;
It is definitely possible to remove that pesky warning triangle during boot when running a custom kernel, though you should be well aware that this method does NOT reset the custom kernel flash counter. The steps are not complicated, but they aren't easy either, so read well.
(1) Make sure you have CF-Root flashed (see the first post). You must have the "CWM Manager" app available.
(2) Make sure you have the same version of CF-Root extracted until you have the zImage file. (ZIP --> extract --> TAR --> extract --> zImage).
(3) Push the zImage file to /sdcard . It must still be called zImage !
(4) Find an original Samsung signed stock kernel (preferably from the same stock firmware you have, but it's not terribly important)
(5) Reboot into download mode (adb reboot download, or boot the device with home and volume-down pressed)
(6) Fire up ODIN, and flash the Samsung kernel
(7) Boot the device with the stock kernel. CWM Manager will still be available.
(8) Start CWM Manager, select Flash Kernel, and select the zImage from CF-Root you previously put on your SD-card. The kernel will flash and the device will reboot.
(9) You will now notice you no longer have the warning triangle during boot, but you are actually running CF-Root with all it's goodies!
(10) In the future, if you only use the Flash Kernel option inside CWM Manager instead of ODIN, the triangle will not return, neither will your flash counter increase. But keep in mind, that CWM Manager can only handle a direct "zImage" if you are NOT running a kernel with full busybox support (this is currently needed for flashing kernels out of .TAR and .ZIP files)
I have searched a lot of threads and post about bricks before posting here. It would appear that my problem is a unique combination of a lot issues.
Detailed Explanation :
I am using a Samsung Galaxy S II (GT-I9001) with the Omega Custom ROM
[ROM][XXLPH][05Mar]◄Omega ICS v3.2►.
http://forum.xda-developers.com/showthread.php?t=1489197
It was working perfectly fine for a week.
Then suddenly is stopped responding and on reboot , it just showed the Samsung start screen with the yellow triangle and exclamation.
I entered Recovery Mode and tried to restore a backup but it failed. I also tried to install the same ROM again (install from SD card) with CWM from recovery but it stopped halfway and failed to respond for over 2 hours.
With no choice but to pull the battery I did so but now Recovery Mode has stopped working. Just get the same loading screen with Samsung and yellow triangle.
However I was not worried because DOWNLOAD mode was still working. I tried flashing a stock firmware using ODIN but it stopped responding. I waited for an hour and pulled the plug.
Download mode is still working so I tried different stock rom with both single file versions (PDA) and the 3 file versions (PDA,PHONE and CSC) with pit and repartition but all stop responding after a while.
It stops at cache.img for the single file ROMs and for the 3 file roms with pit it stops responding at SET PIT File. DO NOT TURN OFF TARGET. I also tried Lightening Rom and that stopped at factory.fs NAND Write.
I checked and double checked all drivers, chaged USB ports and tried reflashing a number of times.
Now when I try to boot or enter recovery I get the message "Firmware upgrade encountered and issue. Please select recovery mode in Kies and try again"
Kies is able to recognize the device but it tries to connect and then says "The device has stopped responding. Reboot to fix this issue" So I am unable to recover firmware using Kies.
TLDR :
There are no driver issues or interference between Kies and Odin. The device is easily recognized and download mode is working. Just unable to flash back to stock rom using odin, unable to boot or enter recovery mode.
Right now the only consolation is that download mode is still working but I am unable to flash anything. Also I had to get stock roms form external sites and smafirmware.com because the Official Firmware Links are from multiupload and they do not work.
Are there any mirrors for the official stock ROMS?
I am trying to flash different roms with ODIN and hoping for something to happen.
Suggestions/Solution to this unique problem will be much appreciated.
This is an unusual problem.
Try to flash the Kernel only via Odin.
Do let me know if you succeed.
[email protected]!n said:
This is an unusual problem.
Try to flash the Kernel only via Odin.
Do let me know if you succeed.
Click to expand...
Click to collapse
I am now using only ODIN. When you say Kernel I assume just the small stock Kernel File (5-10 MB) and not the entire ROM (~350 MB)
In download mode, in the top left corner, the current Binary was show as "Custom"
I used ODIN to flash Stock Kernel (Kernel_I9100XWKF3) and this was the progress:
Firmware Update Start..
zImage
NAND Write Start..
Now it stops responding (waited 20 mins ) but now the Current Binary is shown as "SAMSUNG OFFICIAL"
However, I am still unable to flash a complete stock ROM and cannot boot or enter recovery.
Stock firmwares are available at samfirmware.com. Try one from there. Once you flash, do a full wipe/factory reset. Seems you'll always have to do this when going from ICS to Gingerbread.
Also, from your post above, it sounds like you are still on an ICS ROM (XXLPH), and tried flashing a Gingerbread kernel (XWKF3). This will never work...
Sent from my GT-I9100 using XDA
ctomgee said:
Stock firmwares are available at samfirmware.com. Try one from there. Once you flash, do a full wipe/factory reset. Seems you'll always have to do this when going from ICS to Gingerbread.
Also, from your post above, it sounds like you are still on an ICS ROM (XXLPH), and tried flashing a Gingerbread kernel (XWKF3). This will never work...
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
I tried firmwares from samfirmware.com. The problem is that I am unable to complete the flash process as odin always gets stuck at some point (Mostly KERNEL Stage) .
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> boot.bin
<ID:0/010> NAND Write Start!!
<ID:0/010> Sbl.bin
<ID:0/010> param.lfs
<ID:0/010> zImage
It stops here.Unless I complete a flash I cannot full wipe/factory reset.
Also, I tried flashing an older XWKE8 Rom from samfirmware and the message "Firmware upgrade encountered and issue. Please select recovery mode in Kies and try again" has disappeared. Now when I try to boot or enter recovery there is just a mobile icon and a PC icon connected my an exclamation mark inside an orange triangle
Like you said, it may be because I was on an ICS ROM and then tried to switch to Gingerbread. If So, What ROM do I try to flash now?
Have a search for the GB bootloader and try flashing just that first .
GT-I9100_OLD_BOOTLOADER is the name of the file .
jje
JJEgan said:
Have a search for the GB bootloader and try flashing just that first .
GT-I9100_OLD_BOOTLOADER is the name of the file .
jje
Click to expand...
Click to collapse
Ok I got the bootloader and flashed it using ODIN. This is the first file that ODIN was finally successful in flashing. Thanks.
Something has changed. There is no longer a semi brick screen with the icons previously mentioned.The device now displays the boot screen showing "Samsung Galaxy S II GT-i9100" There is NO YELLOW TRIANGLE now. Finally some Progress. But it is stuck on this screen. Still no Recovery mode or normal boot.
This has however given me some hope. What do I do next?
Try a custom kernel i.e.
http://dl.dropbox.com/u/55089648/Siyah-v2.5.2.tar
download an unrar it.
Flash it with Odin.
Hopefully it works
lordtoeknee said:
Ok I got the bootloader and flashed it using ODIN. This is the first file that ODIN was finally successful in flashing. Thanks.
Something has changed. There is no longer a semi brick screen with the icons previously mentioned.The device now displays the boot screen showing "Samsung Galaxy S II GT-i9100" There is NO YELLOW TRIANGLE now. Finally some Progress. But it is stuck on this screen. Still no Recovery mode or normal boot.
This has however given me some hope. What do I do next?
Click to expand...
Click to collapse
If you have download mode just flash a stock rom if no download mode grab a USB recovery jig from ebay etc .
jje
[email protected]!n said:
Try a custom kernel i.e.
//dl.dropbox.com/u/55089648/Siyah-v2.5.2.tar
download an unrar it.
Flash it with Odin.
Hopefully it works
Click to expand...
Click to collapse
Tried flashing this. It get stuck at this stage :
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> zImage
<ID:0/006> NAND Write Start!!
Actually all kernels I have tried so far are getting stuck at this stage.
[email protected]!n said:
Try a custom kernel i.e.
http://dl.dropbox.com/u/55089648/Siyah-v2.5.2.tar
download an unrar it.
Flash it with Odin.
Hopefully it works
Click to expand...
Click to collapse
Dude. It still looks like he hasn't flashed a gingerbread firmware successfully yet. Which means he's really still on ICS. Siyah doesn't support ICS yet.
And typically, flashing only a kernel when in a situation as he describes won't get you out of that situation. Unless the reason you got into that situation in the first place was by flashing a kernel that wasn't meant for you.
Sent from my GT-I9100 using XDA
JJEgan said:
If you have download mode just flash a stock rom if no download mode grab a USB recovery jig from ebay etc .
jje
Click to expand...
Click to collapse
There was never any problem in getting into download mode. The actual problem is that ODIN gets stuck at some stage when I try to flash anything. I am unable to complete the flash.
The only success was the old bootloader which you suggested. Other than that all other kernels/roms get stuck at some point.
Most other posts/threads say that I will be fine as long as download mode is working. It is, but I am still unable to flash anything as ODIN keeps getting stuck.
Thoughts .
A guess is that something broke using PIT and repartition .
Rom download faulty no you have tried to many .
Bootloader flashes yes so Odin works .
Kies is not running in the task bar is it .
You are using mainboard USB port and Samsung cable .
If it was my phone it would be a service centre job but i would probably try just flashing a CWM and root kernel first to try and get recovery mode to format the system data and cache .
jje
Other possibilities for a stuck flash:
1. Bad cable
2. Cable plugged into a USB hub instead of directly into USB port on PC
3. Cable plugged into a USB passthrough (like keyboard) instead of directly into USB port on PC
EDIT: whoops, JJEgan mentioned bad cable and direct USB connection in his post above.
Thanks for your comments.
I am using the Original Samsung Cable and quite sure it has no problems. Also it is directly connected to my Laptop. And I have made sure there is no interference between Kies and Odin.
Maybe something broke in PIT and repartition, but i can still enter download mode. So I should be able to flash something right?
Not looking forward to taking it to the service center as I have will need to reset my flash counter. I may have to do that as a last resort but i'm hoping something will successfully flash. Like I said, I am hanging onto the fact that Download mode still works.
lordtoeknee said:
Thanks for your comments.
I am using the Original Samsung Cable and quite sure it has no problems. Also it is directly connected to my Laptop. And I have made sure there is no interference between Kies and Odin.
Maybe something broke in PIT and repartition, but i can still enter download mode. So I should be able to flash something right?
Not looking forward to taking it to the service center as I have will need to reset my flash counter. I may have to do that as a last resort but i'm hoping something will successfully flash. Like I said, I am hanging onto the fact that Download mode still works.
Click to expand...
Click to collapse
Hold up. Two things:
1. I just re-read your first post, and you mentioned GT-I9001, which is the Galaxy S plus... which is not the same as the GT-I9100, which is the Galaxy SII international edition. Is this a typo?
2. Have you been putting the .PIT file each time you flash? If so, what .PIT file are you putting, and where did you get it? Could be you flashed using an incorrect .PIT file, and need the right one.
Edit to add: you really don't have to put the .PIT file when you flash unless you ABSOLUTELY have to. I've flashed several times and not once used a .PIT file.
ctomgee said:
Hold up. Two things:
1. I just re-read your first post, and you mentioned GT-I9001, which is the Galaxy S plus... which is not the same as the GT-I9100, which is the Galaxy SII international edition. Is this a typo?
2. Have you been putting the .PIT file each time you flash? If so, what .PIT file are you putting, and where did you get it? Could be you flashed using an incorrect .PIT file, and need the right one.
Edit to add: you really don't have to put the .PIT file when you flash unless you ABSOLUTELY have to. I've flashed several times and not once used a .PIT file.
Click to expand...
Click to collapse
Sorry this was a typo. It is the GT-I9100 - Galaxy S II international edition.
I used the .PIT file and checked repartition whenever it was available with Stock Kernel. ie it came along with the PDA,PHONE and CSC files.
I also tried without the PIT file (No repartition). I did not use any incorrect file.
However, I was unable to do any successful flash. ODIN would stop responding before the PIT flash was completed. if there was no .PIT files it would stop at NAND write at cache.img or zImage
lordtoeknee said:
Sorry this was a typo. It is the GT-I9100 - Galaxy S II international edition.
I used the .PIT file and checked repartition whenever it was available with Stock Kernel. ie it came along with the PDA,PHONE and CSC files.
I also tried without the PIT file (No repartition). I did not use any incorrect file.
However, I was unable to do any successful flash. ODIN would stop responding before the PIT flash was completed. if there was no .PIT files it would stop at NAND write at cache.img or zImage
Click to expand...
Click to collapse
Ok... you said you're using original Samsung USB and you're quite sure it has no problems... but have you tried a different cable? It doesn't have to necessarily be the original Samsung cable. I use a generic micro USB cable for my flashes, and it works fine. Could be the cable went bad... or try a different USB port on your laptop. Maybe the port went bad.
Yes tried another cable as well as different ports. This should not be any problem as i am able to successfully flash bootloaders. Any other type of file, ODIN pauses at some stage and does not respond.
lordtoeknee said:
Yes tried another cable as well as different ports. This should not be any problem as i am able to successfully flash bootloaders. Any other type of file, ODIN pauses at some stage and does not respond.
Click to expand...
Click to collapse
Hmm... could possibly be a corrupted download... try redownloading the files you are flashing?
I had Crodorom working on my SGS2, downloaded the new Omega rom, flashed it and this is what I got: kernel panic upload mode. It doesn't go into recovery mode, only download, but when I try to flash something via odin, my laptop freezes. I don't know what else to do, tried flashing everything I have and every time freezes.
Please HELP ME!!!!:
Search.
http://forum.xda-developers.com/showthread.php?t=1521482
http://www.google.co.uk/search?clie..._upl=3091l3091l0l5344l1l1l0l0l0l0l63l63l1l1l0
jje
kernel panic upload mode
I was flashing custom ROMS from couple of months and did dozens of times.
But when I was flashing resurrection ROM an updated version, it completed but when I rebooted it was stuck in the kernel panic upload mode after the boot screen(galaxy s2). It was not going to clockworkmod recovery too. Then using the odin I tried to flash the stock ROM as well as custom ones. But it will finish, will stuck in the boot screen. Then flashed recovery using Odin and tried to flash custom roms. Couple of ROMS worked but most of them failed and stuck in the boot screen. I could able to restore the stock version which I saved previously.
But I cant try most of the ROMs now. CM9 didnt work.. But MIUI worked.
Can anyone help me.???
Go to formats and storage and delete cache and data before doing full wipes sometimes there is kinda like data blockage you need to get cwm can you flash it with odin
Sent from my GT-I9100 using xda premium
As far as others experience with the same issue, you should also be able to get download mod and flash a ROM from ODIN, freezing issue must be due to your connection or PC problem, try with another PC,
shashankdombe said:
I was flashing custom ROMS from couple of months and did dozens of times.
But when I was flashing resurrection ROM an updated version, it completed but when I rebooted it was stuck in the kernel panic upload mode after the boot screen(galaxy s2). It was not going to clockworkmod recovery too. Then using the odin I tried to flash the stock ROM as well as custom ones. But it will finish, will stuck in the boot screen. Then flashed recovery using Odin and tried to flash custom roms. Couple of ROMS worked but most of them failed and stuck in the boot screen. I could able to restore the stock version which I saved previously.
But I cant try most of the ROMs now. CM9 didnt work.. But MIUI worked.
Can anyone help me.???
Click to expand...
Click to collapse
Follow this http://forum.xda-developers.com/showpost.php?p=24648392&postcount=910
Yes.. but no improvements
djseaneq said:
Go to formats and storage and delete cache and data before doing full wipes sometimes there is kinda like data blockage you need to get cwm can you flash it with odin
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes I can flash using Odin.. It even succed and resets... But when it reboots it just stuck in the boot screen and cant boot in recovery too...
But if I flash just the CMW 4 it flashes and I can just access recovery and flash some ROMS from there..
---------- Post added at 10:54 AM ---------- Previous post was at 10:53 AM ----------
078gregory said:
Follow this http://forum.xda-developers.com/showpost.php?p=24648392&postcount=910
Click to expand...
Click to collapse
Tried it with the stock one which I got with mobile ... But it was not ROM.. just stock firmare... I will try with complete ROM.
Hayelp --- STUCK in KERNEL PANIC UPLOAD MODE
OK, so I did a stupid thing. I decided to use ROM Manager to move from CYANOGENMOD 9 (earlyish variant) to MIUI 2.5.11.
(I'm usually fairly comfortable/confident/competent doing this kind of thing - never bricked anything before - PSP, Galaxy S, Experia min pro, etc...)
I told ROM Manager to backup the ROM, and set it off to do its thing.
Next thing I'm aware of is "KERNEL PANIC UPLOAD MODE" and the text [ RST_STAT = 0x20000000 ] in red in the top left hand corner of the screen.
I've searched the Fora and found some others with a similar issue, so I tried a few things.
1stly I tried to get into ClockwordModRecovery mode, but was unable to.
But I got into Odin upload mode, so I dug out Odin, and an XW ROM, tried to download them to the device. No joy, so I tried another Odin XX ROM - also no joy. (Following various guides as to which ROM to try, and how to do it). Currently the ODIN Mode says.
ODIN MODE
PRODUCT NAME: GT-i9100
Custom Binary Download: Yes (1 counts)
Current Binary: Samsung Official
...
I could flash a new ROM over the existing one(it doesn't seem as if I can now...) and am currently on (I believe) Kernel_I9100XWLP7.
OK, so what to do next...
Well I tried to get back into CWM (on, up volume and home) to get into something which looked like CWMRecovery, but only gave 4 (?) options - reboot now, install update from SD, wipe Cache, wipe data - the wipe data came up with a password required, which I don't know so backed out of.
Oh, I downloaded KIES 2.0 to see if that could help - not in this instance it can't...
Now I'm stuck, I will try some other ODIN ROMs as that seems to be the only point of attack left to me.
Can anyone suggest anything else to try?
Please?
Argon0 said:
ODIN MODE
PRODUCT NAME: GT-i9100
Custom Binary Download: Yes (1 counts)
Current Binary: Samsung Official
Click to expand...
Click to collapse
if your status is above while you enter into Download mod, you should be able to flash a stock ROM from the ODIN, provided you have followed the steps correctly.
find any official stock ROM and flash it from ODIN after leraning well how to flash from ODIN.
prefer GB oficial ROM.
Further info:
Removal of Kies leads me to be able to use ODIN again. I have just been able to "flash" with Kernel_I9100XWLA4.tar.md5.
The phone is now stuck on the
"Samsung
GALAXY SII
GT-I9100"
Screen.
Argon0 said:
Further info:
Removal of Kies leads me to be able to use ODIN again. I have just been able to "flash" with Kernel_I9100XWLA4.tar.md5.
The phone is now stuck on the
"Samsung
GALAXY SII
GT-I9100"
Screen.
Click to expand...
Click to collapse
why do you try only the kernel....flash the same XWLA4 complete ROM.
Kies are installed for getting the required drivers installed, better you install Kies and just kill the application, from system tray too..
Firstly ZACQ8 I have tried that, can you recommend a specific ROM? (This is a UK T-mobile SGS2).
I can now get into the "Android System Recovery <3e>" screen.
It has four options:
reboot
apply update from SDCard
wipe data/factory reset
wipe cache partition.
The "command window" shows (in yellow):
-- Copying media files...
Successfully copied meida[sic] files.
# MANUAL MODE #
-- Updating applicaton...
{this bit in red}
E:check_point2: /sdcard/.ngmoco//53297255e6f7dd7073c89e6dea2da0d1 is not directory
{back to yellow}
Successfully update application.
-- Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/ODK/system/'.
Successfully applied multi-CSC.
that is the stock recovery, did you try both wipes there and reboot?
OMG - I can't believe I missed the "complete ROM" bit before... OK downloading the latest UK (XEU) version of Stock from:
http://skywanker.net/download/downl...9100_XEU_I9100XWLP7_I9100XXLPS_I9100XEULP5.7z
Hope this works... (should have clicked earlier - this is taken a lot longer than the Kernel.. I wonder why!!!).
Thanks ZACQ8 - will click on the Thanks button if this works!
---------- Post added at 02:20 PM ---------- Previous post was at 01:54 PM ----------
OK, having installed that complete ROM. I'm still getting nowhere fast...
Now its stuck at SAMSUNG GALAXY SII GT-I9100 screen... (actually seems to cycle to that screen and go no further).
Now I can't get into the Android Recovery Screen Either...
Output from ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100_XEU_I9100XWLP7_I9100XXLPS_I9100XEULP5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> factoryfs.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> param.lfs
<ID:0/003> Sbl.bin
<ID:0/003> zImage
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
Will now try the XXLPS from: http://skywanker.net/download/downl...9100_XEO_I9100XXLPS_I9100OXALPS_I9100XXLPS.7z
---------- Post added at 02:22 PM ---------- Previous post was at 02:20 PM ----------
Yes, first one asked for a password (which I don't know), 2nd (cache) seemed to do as expected, but made no difference.
The factory reset password - if you do 3 fails at that it says one more go and then I'll damage the contents of the SDCARD - does this matter?
I'll add that there is nothing I don't have elsewhere on either the internal or external SD cards...
try GB roms...
Recovered from "KERNEL PANIC UPLOAD MODE"
GB ROMS from where? The letter coding is a little tricky to understand...
(I understand that XX and XW refer to UK type ROMS, is there a separate section/letter code for GB Roms?) - is this: http://skywanker.net/download/downl...9100_SEB_I9100XXLPQ_I9100OXXLPD_I9100XXLPQ.7z what you refer to as a GB ROM?
I now have a Galaxy SII booting up, into the stock ROM mentioned above. (well it seems to be booting I got the Android with the vector polyhedron in its tummy, and now the screen is showing a glowing S with Samsung Galaxy SII underneath it - I shall leave it at that for a few minutes before... well what next.. if its stuck here..) I guess another reboot and another ROM, or into recovery....
Got into recovery, did wipe cache and factory reset... booting now.... same as last time, but a little quicker to the glowing S...
Now its installing applications.... (KIES AIR, etc...)..
Connecting to WiFi - done (Working SIM is in other phone atm).
Signing in...
Restoring...
Ready to use !!! Y
<YAY>
what up now? from where are you downloading the ROMs from,
ICS roms are 4.0.3 and GB Roms are 2.3+
you can see the coplete list of ROM released here : http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-I9100&r=1#regiona
EDIT : I think you have not given much time to boot your phone....thanks GOD finaly it worked..
AH... GB = GingerBread - I thought you were referring to Great Britain!!!
Ho Hum.
I now have a working phone at least - ICS with Touchwiz (yuk)...
Now how do I put MIUI on it.. (any links to tutorials?)? Or do I go back to CM9?
(And yes I do need root, I want to use some remote desktop apps - such as Remote Call - so I can control the phone from my PC).
Last sucessful flash was LP7 right?
pick the CF-root for the same from the link CF-root below, download the zip, unzip it to get TAR file flash same like u flashed the ROM put it on PDA.
then you will get your phone rooted and CWM installed, then flash watever rom from CWM
Successful flash was GT-I9100_XEO_I9100XXLPS_I9100OXALPS_I9100XXLPS.tar.md5
Is there a reason why Odin doesn't get used to flash things like MIUI?
It would seem to be a good standard (and fairly safe) way to flash Galaxies...
Again, Thanks ZACQ8.
---------- Post added at 04:02 PM ---------- Previous post was at 03:22 PM ----------
DOH... Read the thread he points you to before typing anything new....
OK so if I have ...LPS I need to use this cf-root CF-Root-SGS2_XX_OXA_LPS-v5.4-CWM5.zip right?
---------- Post added at 04:10 PM ---------- Previous post was at 04:02 PM ----------
OK, just to keep this all in the same place, in case its useful for anybody else...
Yup that did seem to be the correct cf-root - I've now got a rooted stock Galaxy S2 - still with the yellow triangle, but that can stay for the moment. I guess the next bit is to put the MiuiAndroid.zip in the root of the sdcard...
Then boot into CWM, then install from sdcard... Lets see....
One other thing which might be useful for others is that I had to restart ODIN every time I wanted to flash, I couldn't flash, then reset reconnect and reflash. This is on Windows 7 Pro. Also I made sure I ran ODIN as administrator.
I did something stupid on my MDK S4.
I used the TWRP app to flash the latest version of TWRP recovery, but instead of selecting JFLTEVZW, I selected the recovery for DEB (my nexus 7 lte tablet).
So, nothing will boot on the phone, and I need to use ODIN to flash a factory recovery.
Can anyone point me where to download the ODIN recovery file for MDK ?
Oh my gosh is this phone in trouble.
Trying to ODIN everything back to stock with PDA file I get:
Initialization..
Get PIT for mapping..
There is no PIT partition.
All threads completed.(succeed 0 / failed 1)
Removed!!
Added!!
So, where can I find a partition (PIT) file for the Verizon S4 ?
OK, solved everything.
I had been using an old USB cable which had come with my ancient droid-x phone.
I switched to a nice newer thicker USB cable, and was able to flash the stock mdk recovery using Odin.
Then booted cyanogenmod 12, ran TWRP app to install latest TWRP recovery.
The end
so, hello. i bought an s8 few days ago and tried to root it. but sadly couldn't. everytime kernel detects that /system partition is changed or mounted through twrp it makes phone stuck in a bootloop with the words "set bit warranty : kernel" so i decided to make a custom kernel to fix that problem, since there aren't many snapdragon custom kernels for s8 (except semi stock by jessec, which only supports android 7.) this is a continuity in legacy of jessec's kernel but updated to android 9. please note that after flashing the kernel you need to format data, so back it up before flashing it.
Steps to flash:
1. Download the attachment
2. Flash twrp for your device
3. Go to Wipe then format data
4. flash the zip
5. viola! you are on a custom kernel now!
For s8+ users, use dream2qltechn.zip instead of kernel.zip otherwise, your phone will be in bootloop.
kernel sources: https://github.com/Katuwu-commits/s8-chinese-custom-kernel
[this is my first post so dont bully me for not knowing how to post, pls]
Can it be flashed on stock passed Rom?! G950w for example?
Seem interesting..
Please some info about if possible
Dash_k said:
Can it be flashed on stock passed Rom?! G950w for example?
Seem interesting..
Please some info about if possible
Click to expand...
Click to collapse
I think so it can be applied on G950w aswell. Since it's a snapdragon. But I have only tested the kernel on Scv36/Sc-02j Also a reply to your question, you can flash it on latest pie stock roms, if that is what you wanted to ask.
Seems pretty good except I find myself running into the problem of frp lock turning itself back on when adding a google account causing the phone to brick itself forcing me to flash again. I guess it does work fine if you never shut down your phone
mlg519 said:
Seems pretty good except I find myself running into the problem of frp lock turning itself back on when adding a google account causing the phone to brick itself forcing me to flash again. I guess it does work fine if you never shut down your phone
Click to expand...
Click to collapse
Hmm, weird I tried restarting, shutting down my phone many times, frp lock doesn't get on. will look into the problem.
Aashir4249 said:
Hmm, weird I tried restarting, shutting down my phone many times, frp lock doesn't get on. will look into the problem.
Click to expand...
Click to collapse
Do you have a google account added in the settings? That seems to be what triggers it back on on my device (SM-G9500)
Hi. I have a G955U (Samsung Galaxy S8+, Verizon & Snapdragon) and whenever I try to flash with Odin, it always comes up with this:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 23 M
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
This occurs whether I am trying to flash completely stock firmware onto my device, or trying to flash TWRP in this case. I cannot get this error to go away. I have tried multiple versions of Odin, I have tried different stock firmware, tried different versions of TWRP, and nothing.
Currently I was attempting this with Android 9 on Bootloader v7 (phone had this already). Is there any way to get TWRP on this phone or is this all for nothing?
Hey, I have a S8+ (dream2qlte) device, so I flashed dream2qltechn.zip
Now it's stuck in boot and all the buttons don't work, I can just wait for the battery to run out ......
mlg519 said:
Seems pretty good except I find myself running into the problem of frp lock turning itself back on when adding a google account causing the phone to brick itself forcing me to flash again. I guess it does work fine if you never shut down your phone
Click to expand...
Click to collapse
The issue is you just have to remove frp from starting in the first place in rom. I accomplished this by removing knox and mdm stuff from system img and frp edit on build.prop to disable it and then it works
ChrisJK7 said:
Hi. I have a G955U (Samsung Galaxy S8+, Verizon & Snapdragon) and whenever I try to flash with Odin, it always comes up with this:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 23 M
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
This occurs whether I am trying to flash completely stock firmware onto my device, or trying to flash TWRP in this case. I cannot get this error to go away. I have tried multiple versions of Odin, I have tried different stock firmware, tried different versions of TWRP, and nothing.
Currently I was attempting this with Android 9 on Bootloader v7 (phone had this already). Is there any way to get TWRP on this phone or is this all for nothing?
Click to expand...
Click to collapse
yes...i faced the same problem...make sure to use usb2.0 / usb 2.0 hub or different PC...
Anyone using this kernel is s8+ snapdragon? Does it work?
Aashir4249 said:
Scv36/Sc-02j A
Click to expand...
Click to collapse
Tried on s8+ sc-o3j ...did not work
Unreal_Hawkzz said:
Tried on s8+ sc-o3j ...did not work
Click to expand...
Click to collapse
Format data in twrp not wipe data must be format!
Flash my zip then the kernel zip from op then magisk 23 zip.
Then reboot and should be good too go.
I dont know if current magisk 25.2 will work or not but 23 does just download full manager when it ask but dont update anything.
Dont use any other encryption remove zips or rmm remove zips just flash my Remove_FRP_Encryption_Knox_S8_S8Plus only
This zip removes encryption, verity via the system/vedor/etc fstab.qcom and removes knox plus frp sets secure storage to false so wifi passwords will safe adds some prop tweeks
works
jrkruse said:
Flash this attached zip, flazh the kernel zip from op and flash magisk 23 then format data and reboot and it should boot
Click to expand...
Click to collapse
works
Thanks for heads-up on this thread, the only way for me before is to use China version BL and the other files from TGY to avoid FRP lock , i will try this files soon.
Dr.][No_WaY said:
Thanks for heads-up on this thread, the only way for me before is to use China version BL and the other files from TGY to avoid FRP lock , i will try this files soon.
Click to expand...
Click to collapse
flash the zip I provided above and you can use tgy stuff
jrkruse said:
flash the zip I provided above and you can use tgy stuff
Click to expand...
Click to collapse
just format not wipe but format data in twrp flash my zip then the kernel zip from op then magisk 23 zip. then good too go. I dont know if current magisk 25.2 will work or not but 23 does just download full manager when it ask but dont update anything
jrkruse said:
just format not wipe but format data in twrp flash my zip then the kernel zip from op then magisk 23 zip. then good too go. I dont know if current magisk 25.2 will work or not but 23 does just download full manager when it ask but dont update anything
Click to expand...
Click to collapse
Thanks, this kernel is not good for G9550 , i lost wifi at 1st run so i returned back to my working kernel but really Thanks for your frp lock fix , now I am using full tgy rom
Link to tgy rom?