Related
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?
Edit: Problem Solved!
This problem is caused by an auto-restore script in Canadian ICS notes. When the phone boots up, it restores the recovery image to the stock Android recovery. To fix this problem, follow the link kindly supplied by zaptor99:
zaptor99 said:
Detailed instructions for flashing CWM and rooting Canadian Note can be found here: http://forum.xda-developers.com/showthread.php?t=1775263
Click to expand...
Click to collapse
It worked for me!
Initial Post: So, after my ICS OTA update, I set about reinstalling CWM, then re-rooting the phone.
Steps followed:
Put phone into Download Mode(Power+Down Vol, then Up Vol at warning screen), successful.
Open ODIN, select CWM-i717-120305.tar.md5 (Also done with cwm-touch-i717-120414.tar.md5) as PDA
Plug in phone - Odin detects correctly.
Click Start; ODIN steps through it's business:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cwm-touch-i717-120414.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
Seems successful, no?
Phone reboots, works normally.
Shut down phone, disconnect from PC
Boot into Recovery Mode (Vol Up+Vol Down+Power, as normal)
Aaaaaand, into Android System Recovery (3e).
Other information:
Before doing the Rogers OTA update, I reflashed to stock Rogers firmware using this post: http://forum.xda-developers.com/showthread.php?t=1657262
This process worked perfectly from Gingerbread - I installed CWMTouch, then a rooted kernel via ODIN.
I've no idea why I can't boot into CWM? I figure, either the ODIN write is failing (though it reports success), or it's writing to the wrong place. But without root, I'm not sure how I can check.
I'd be eternally grateful for any help. The phone works fine, now, but I *REALLY* don't want to be forever stuck on stock firmware with no way to make proper nandroid backups.
I am not sure why it is like that but it's exactly same on my i717m.
For me, I just went to CWM mode by pressing those keys before giving Note a full reboot.
I could get into CWM mode without a problem so I installed superuse. And my phone is fully rooted.
darknoon77 said:
I am not sure why it is like that but it's exactly same on my i717m.
For me, I just went to CWM mode by pressing those keys before giving Note a full reboot.
I could get into CWM mode without a problem so I installed superuse. And my phone is fully rooted.
Click to expand...
Click to collapse
I can't get into CWM. It seems to flash fine, but when I try to reboot into CWM, it loads the stock Android Recovery instead, so I have no way to flash superuser.
Edit: To be clear, my problem isn't getting root. It's getting CWM working, so I can move forward in any way. Once I've got CWM running, there's zounds of different ways to get root.
Further Edit: Attempts to flash CWM *are* increasing my flash counter.
Wintersdark said:
I can't get into CWM. It seems to flash fine, but when I try to reboot into CWM, it loads the stock Android Recovery instead, so I have no way to flash superuser.
Edit: To be clear, my problem isn't getting root. It's getting CWM working, so I can move forward in any way. Once I've got CWM running, there's zounds of different ways to get root.
Further Edit: Attempts to flash CWM *are* increasing my flash counter.
Click to expand...
Click to collapse
try TWRP or try to redownload CWM maybe you just got a bad zip
Bradl79 said:
try TWRP or try to redownload CWM maybe you just got a bad zip
Click to expand...
Click to collapse
How can I install TWRP on an unrooted phone without cwm installed? Is there an ODIN friendly tar kicking about? I looked but without success.
My zips are known good, though, used them to install CWM back on Gingerbread.
I just came to the q&a forums to post the same think. I tried flashing CWM 3 times and Im still going into stock recovery. I managed to go into CWM once and was able to flash SU so I have root but when I try to go back to recovery, I end up at stock recovery.
Sent from my SGH-I717M using xda app-developers app
id_mew said:
I just came to the q&a forums to post the same think. I tried flashing CWM 3 times and Im still going into stock recovery. I managed to go into CWM once and was able to flash SU so I have root but when I try to go back to recovery, I end up at stock recovery.
Sent from my SGH-I717M using xda app-developers app
Click to expand...
Click to collapse
You're freshly into ICS as well? did you upgrade OTA or with Kies? Bdfore upgrading, did you flaah the "stock Rogers original firmware" from here on XDA?
Trying to pin down the common thread, as this appears to be happening to several people.
Wintersdark said:
You're freshly into ICS as well? did you upgrade OTA or with Kies? Bdfore upgrading, did you flaah the "stock Rogers original firmware" from here on XDA?
Trying to pin down the common thread, as this appears to be happening to several people.
Click to expand...
Click to collapse
I reverted back to Bell stock firmware and updated ics OTA.
I tried flashing CWM recovery a couple of times and I noticed the only time I can get into CWM is when I flash and press the volume up + down and the power button before my phone full reboots after the flash.
That way It works but right after the phone reboot for the first time after flashing CWM, it will not fo back into it.
Can anybody help us?
How can we try TWRP if we can't get into CWM?
Sent from my SGH-I717M using xda app-developers app
Interesting! If you can get into CWM that way (reflash and squeeze in) try doing that and using cwm to flash SuperUser.
Then, once rooted, install ROM Manager and have it reflash the latest CWM, maybe that will get us a good cwm install.
cwm 5.8.4.8 works flawlessly.
Sent from my SGH-I717M using xda app-developers app
Wintersdark said:
Interesting! If you can get into CWM that way (reflash and squeeze in) try doing that and using cwm to flash SuperUser.
Then, once rooted, install ROM Manager and have it reflash the latest CWM, maybe that will get us a good cwm install.
Click to expand...
Click to collapse
I actually flashed CWM went into it before my phone rebooted and flashed TWRP and same think happened, when my phone rebooted I loose my flashed recovery.
I doubt Rom manager would work.
Sent from my SGH-I717M using xda app-developers app
id_mew said:
I actually flashed CWM went into it before my phone rebooted and flashed TWRP and same think happened, when my phone rebooted I loose my flashed recovery.
I doubt Rom manager would work.
Sent from my SGH-I717M using xda app-developers app
Click to expand...
Click to collapse
It seems like its somehow reverting the restore partition on boot. i suspect it may be a scripted event "on next boot" after ODIN, so flashing another recovery then wouldnt help - the on next boot event happening again when you reboot.
However, ROM Manager would give you a chance to reflash recovery after that happens. Its a xhance, anyways. Seems to have worked for dark? I can't try until after work today.
Plz update me when u give Rom manager a try.
Sent from my SGH-I717M using xda app-developers app
Wintersdark said:
So, after my ICS OTA update, I set about reinstalling CWM, then re-rooting the phone.
Steps followed:
Put phone into Download Mode(Power+Down Vol, then Up Vol at warning screen), successful.
Open ODIN, select CWM-i717-120305.tar.md5 (Also done with cwm-touch-i717-120414.tar.md5) as PDA
Plug in phone - Odin detects correctly.
Click Start; ODIN steps through it's business:
Phone reboots, works normally.
Shut down phone, disconnect from PC
Boot into Recovery Mode (Vol Up+Vol Down+Power, as normal)
Aaaaaand, into Android System Recovery (3e).
Other information:
Before doing the Rogers OTA update, I reflashed to stock Rogers firmware using this post: http://forum.xda-developers.com/showthread.php?t=1657262
This process worked perfectly from Gingerbread - I installed CWMTouch, then a rooted kernel via ODIN.
I've no idea why I can't boot into CWM? I figure, either the ODIN write is failing (though it reports success), or it's writing to the wrong place. But without root, I'm not sure how I can check.
I'd be eternally grateful for any help. The phone works fine, now, but I *REALLY* don't want to be forever stuck on stock firmware with no way to make proper nandroid backups.
Click to expand...
Click to collapse
I did EXACTLY as you did. But I used cwm-i717-120305.tar instead. Does it make a difference if the file is .tar and not .md5? Because CWM recovery stayed on mine and works perfectly.
Agoattamer said:
I did EXACTLY as you did. But I used cwm-i717-120305.tar instead. Does it make a difference if the file is .tar and not .md5? Because CWM recovery stayed on mine and works perfectly.
Click to expand...
Click to collapse
Did you install ICS OTA over pure stock Gingerbread? This doesnt seem to happen to people who had a modded recovery before installing the ICS update.
Wintersdark said:
Did you install ICS OTA over pure stock Gingerbread? This doesnt seem to happen to people who had a modded recovery before installing the ICS update.
Click to expand...
Click to collapse
It was pure stock Gingerbread. I was running an ATT leaked ICS version with CWM installed. But to get the Rogers update I used odin to restore the gingerbread version from here: http://forum.xda-developers.com/showthread.php?t=1657262
I did not install CWM or root before I used Kies to get the ICS update. But I see the difference now. I used Kies to get the update and you used OTA. Maybe if you went back to gingerbread and used Kies this time to get the update, it might fix your issue??
Any luck from Rom Manager?
I'm at at a wedding now so I won't be able to try it.
Sent from my SGH-I717M using xda app-developers app
Detailed instructions for flashing CWM and rooting Canadian Note can be found here: http://forum.xda-developers.com/showthread.php?t=1775263
zaptor99 said:
Detailed instructions for flashing CWM and rooting Canadian Note can be found here: http://forum.xda-developers.com/showthread.php?t=1775263
Click to expand...
Click to collapse
That's fantastic! Thanks so much for the linkage there
zaptor99 said:
Detailed instructions for flashing CWM and rooting Canadian Note can be found here: http://forum.xda-developers.com/showthread.php?t=1775263
Click to expand...
Click to collapse
Thanks Zaptor! it worked.
Finally, this gave me enough trouble.
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
I9300 International (EU)
I can flash .pit files, in my case the GT-I9300_mx_20120220.pit for the 16 GB variant (passes in various ODIN versions). However, when I start flashing a kernel, firmware or recovery ODIN 1.03, 1.83, 1.85, 3.04, 3.07, 3.09 get stuck at NAND Write Start!!
I can't get into recovery, previously had TWRP 2.7.0.0.
I've tried flashing: stock firmware for my phone, Siyah, CM 11 M5 Snapshot (which previously worked)
Any and all ideas welcome! PLEASE HELP!
StevenZan said:
I9300 International (EU)
I can flash .pit files, in my case the GT-I9300_mx_20120220.pit for the 16 GB variant (passes in various ODIN versions). However, when I start flashing a kernel, firmware or recovery ODIN 1.03, 1.83, 1.85, 3.04, 3.07, 3.09 get stuck at NAND Write Start!!
I can't get into recovery, previously had TWRP 2.7.0.0.
I've tried flashing: stock firmware for my phone, Siyah, CM 11 M5 Snapshot (which previously worked)
Any and all ideas welcome! PLEASE HELP!
Click to expand...
Click to collapse
Nand write start failure usually means you need a new motherboard suggest service repair but try this first >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << but it may not flash.
42548324 407
tallman43 said:
Nand write start failure usually means you need a new motherboard suggest service repair but try this first >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << but it may not flash.
Click to expand...
Click to collapse
Oh, great, thanks! I looked through topics for the better part of the last 48 hours. Will try it immediately!
StevenZan said:
Oh, great, thanks! I looked through topics for the better part of the last 48 hours. Will try it immediately!
Click to expand...
Click to collapse
OMG, it actually is writing data!
:highfive:
THANKS!
Lets me get into recovery now with error "failed to mount /efs".
Recovery flashed, device rooted, CM 11 M5 flashed.
Stuck at Samsung logo with a little red exclamation mark in the upper left corner (appeared when it worked, too).
-Bought a used S3.
-It enters dowload mode and recovery (CWM)
-If you turn it on normaly, it get stuck at Samsung Logo
-Tried to flash via ODIN but CSC, PDA, MODEM says
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
-Tried to flash pit files and re-partition but I get stuck at "Get pit for mapping" or "No partion" (depending on the version of ODIN)
I think there's no solution, I've already searched a LOT around XDA and no one has a solution for this
So this is my last call before replacing motherboard (maybe eMMC chip is broken)
Please, keep in mind that I'm not a noob (or at least not that bad noob) and I've already tested ODIN with different cables, ODIN versions, pit versions, USB ports, different computers, no KIES installed, drivers unistalled and reinstalled over and over so this is not the problem.
More details
-The man who sold me this phone told me that he was updating by KIES and electricity went off in his house (It's possible that this is not true, don't have evidence to confirm this)
-Wipes by recovery don't work. Only wipe battery stats. If I try to wipe cache, data, system or anything else, recovery gets stucked or phone rebooted
-SD card is not recognzied in recovery. Can't make a backup or flash files to external SD card. Internal SD card can't be mounted.
-Format system, or cache or data by Mounting settings neither work. It freezes the recovery
-Saw that there is a method to recover Verizon S3 phones by a sort of factory image. Didn't tried in my 9300 interntional, but read a few people who said that method didn't worked on her 9300. Wonder if it's posible to make a factory image of 9300. (Here is the thread http://forum.xda-developers.com/showthread.php?t=2660566)
Try downgrading just the boot loader to BLFB, if that flashes then try pit & firmware together.
The age of this model means nand wear is becoming more common, so it might mean nothing will flash.
boomboomer said:
Try downgrading just the boot loader to BLFB, if that flashes then try pit & firmware together.
The age of this model means nand wear is becoming more common, so it might mean nothing will flash.
Click to expand...
Click to collapse
I tried just flash only Bootloader file that comes with each firmawre I tried (didn't understand what do you mean by BLFB) but no difference.
jutopa said:
I tried just flash only Bootloader file that comes with each firmware I tried (didn't understand what do you mean by BLFB) but no difference.
Click to expand...
Click to collapse
After a year or so I have tried to flash again my old i9300, but I'm stacked in the same problem! I have tried with Odin 3.12.3 with different PIT files, and also with Heimdall under Ubuntu... I'm not also a super noob (i have flashed several time this and other phones)
Have you found a way to force to rewrite the PIT file? the only mode available in my phone (i9300 International) is the Download Mode (i have broken even the Bootloader and the Recovery trying to Flash it )
Nothor said:
After a year or so I have tried to flash again my old i9300, but I'm stacked in the same problem! I have tried with Odin 3.12.3 with different PIT files, and also with Heimdall under Ubuntu... I'm not also a super noob (i have flashed several time this and other phones)
Have you found a way to force to rewrite the PIT file? the only mode available in my phone (i9300 International) is the Download Mode (i have broken even the Bootloader and the Recovery trying to Flash it )
Click to expand...
Click to collapse
Tried J-tag yet?