Related
I'm not new to rooting, I'm coming from the Samsung Epic 4G.. My new Epic Touch 4G is stuck at the Samsung Galaxy II GT-I9100 Logo.. Really annoying. Here's what happened...
I rooted my new Epic touch with this link: http://www.forums.acsyndicate.net/s...lus-Stock-Rooted-BusyBox-CWM5-and-Plus-Tweaks
Everything was working fine.. I then wiped the phone (the usual) and flashed the stable Starburst ROM
I rebooted and started getting an error saying "Sorry! The application Status Bar (processcom.android.systemui) has stopped unexpectedly. Please try again."
The notification bar was not present at all.. Soft reboots started recurring so I tried to restart but it didn't work. I ended up pulling the battery.
I then entered CWM and took a different approach.. I followed some steps from "Weltwon" (http://forum.xda-developers.com/showthread.php?t=1276320&page=169) and it didn't even get pass the "Logo" screen.. I pulled the battery once again (uh-oh)...
After putting the battery back in, I entered download mode and tried to Odin back to EG30 but it still stalled at the "Logo" screen.
Being that I wasn't coming from another ROM, is it possible that I messed something up when I formatted system in the "mounts and storage" tab?
Hopefully it's not a goner.. Any help would be appreciated.
Here's my Odin log after using the stock kernal pulled tar file..
No pit was added..
<ID:0/003> Added!!
<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> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
so let me get this straight.. you odin and everything was working properly. then you wanted to flash a custom rom and then you got errors. now you tried to odin again and you get stuck at samsung screen?
have you done this?
- ODIN with a different usb cable, or computer?
- redownload the roms?
ODIn to stock should boot and fix your errors in my expereince..
SocialReject said:
I'm not new to rooting, I'm coming from the Samsung Epic 4G.. My new Epic Touch 4G is stuck at the Samsung Galaxy II GT-I9100 Logo.. Really annoying. Here's what happened...
I rooted my new Epic touch with this link: http://www.forums.acsyndicate.net/s...lus-Stock-Rooted-BusyBox-CWM5-and-Plus-Tweaks
Everything was working fine.. I then wiped the phone (the usual) and flashed the stable Starburst ROM
I rebooted and started getting an error saying "Sorry! The application Status Bar (processcom.android.systemui) has stopped unexpectedly. Please try again."
The notification bar was not present at all.. Soft reboots started recurring so I tried to restart but it didn't work. I ended up pulling the battery.
I then entered CWM and took a different approach.. I followed some steps from "Weltwon" (http://forum.xda-developers.com/showthread.php?t=1276320&page=169) and it didn't even get pass the "Logo" screen.. I pulled the battery once again (uh-oh)...
After putting the battery back in, I entered download mode and tried to Odin back to EG30 but it still stalled at the "Logo" screen.
Being that I wasn't coming from another ROM, is it possible that I messed something up when I formatted system in the "mounts and storage" tab?
Hopefully it's not a goner.. Any help would be appreciated.
Click to expand...
Click to collapse
Silly question, but did you actually flash a ROM or just kernels after performing Weltwon's steps? I don't know what he was posting that regarding, but it seemed his instructions asked you to format /system (ie erase your ROM) but never mentioned flashing your new ROM by CWM or by Odin. Perhaps that was just understood in the context he was replying to, but if you didn't do so, you'd have a kernel on your phone but no ROM, meaning you could boot into Recovery, but there would be no ROM to boot into.
sfhub said:
Silly question, but did you actually flash a ROM or just kernels after performing Weltwon's steps? I don't know what he was posting that regarding, but it seemed his instructions asked you to format /system (ie erase your ROM) but never mentioned flashing your new ROM by CWM or by Odin. Perhaps that was just understood in the context he was replying to, but if you didn't do so, you'd have a kernel on your phone but no ROM, meaning you could boot into Recovery, but there would be no ROM to boot into.
Click to expand...
Click to collapse
I think I'm gonna just throw it away...
I woke up this morning and tried to boot into recovery and got a black screen sorta like this... "Phone . . Triangle with exclamation mark inside . . Computer"
I go into download mode and it says my Product name is GT-9100 !?
No computer ever recognizes it as a device, it's just a paper-weight now smh
if you cant get into download mode you might be screwed.. if you can tho, i recommend flash the eg30 with root, not just a kernel.. using odin and having it put in the pda slot with just auto reboot checked.. flashing just a kernel won't fix your problems
elliwigy said:
if you cant get into download mode you might be screwed.. if you can tho, i recommend flash the eg30 with root, not just a kernel.. using odin and having it put in the pda slot with just auto reboot checked.. flashing just a kernel won't fix your problems
Click to expand...
Click to collapse
I can get into download mode but the phone isn't recognized at all, by any of my computers.. My product name says GT-I9100 rather than SPH-D710. weird
hm.. if you can get into download mode try this guid out.. http://forum.xda-developers.com/showthread.php?t=1282415
Make sure you have correct drivers of course, make sure you try dif usb ports if possible and dif cables if possible.. maybe even a dif. odin
SocialReject said:
I can get into download mode but the phone isn't recognized at all, by any of my computers.. My product name says GT-I9100 rather than SPH-D710. weird
Click to expand...
Click to collapse
when you flash a rooted kernel, all our phones say GTI9100....
wase4711 said:
when you flash a rooted kernel, all our phones say GTI9100....
Click to expand...
Click to collapse
Oh. Well, I've tried different drivers.. Even reinstalled Kies but the phone won't recognize at all. I'll try some more USB cords.
wase4711 said:
when you flash a rooted kernel, all our phones say GTI9100....
Click to expand...
Click to collapse
Yea.. it does say GT I9100 with a exclamation mark in a yellow triangle.. besides that, his phone still isnt booting lol.. all you need is to get your pc to see the phone.. when you open Odin and plug phone in while in download mode, you don't get a COM to light up?? try using different version of Odin.. try restarting your pc etc etc.. try another computer if possible too.. trial and error lol, id keep putting your phone into download mode too.. i had this problem with my OG Epic.. it took a while but I finally got it to read in ODIN
elliwigy said:
Yea.. it does say GT I9100 with a exclamation mark in a yellow triangle.. besides that, his phone still isnt booting lol.. all you need is to get your pc to see the phone.. when you open Odin and plug phone in while in download mode, you don't get a COM to light up?? try using different version of Odin.. try restarting your pc etc etc.. try another computer if possible too.. trial and error lol, id keep putting your phone into download mode too.. i had this problem with my OG Epic.. it took a while but I finally got it to read in ODIN
Click to expand...
Click to collapse
Odin can't recognize it because my computer doesn't even recognize it. I plug it in and go to device manager and there's no signs of it. Maybe it's the drivers, idk. I haven't even activated it to Sprint yet so I doubt that they help a "stranger"
Try a USB jig
Sent from my Samsung Galaxy S2
I heard usb jig only works if I can't already get into download mode.
Sent from the future.
Hi there,
I am going crazy over my wife her Note2. Last night it suddenly rebooted itself and got stock on bootscreen. it was in the middle of the night and connected to the charger. I tried to restart, I tried pulling the battery out and then restart, I tried flashing stock rom. Nothing. I can't get into recovery, I can get in download mode but it won't flash anything. It says that it is missing PIT and odin gives a big red FAILED. But when I flash stock ROM with PIT file it won't flash, even after 3 hours nothing happened. What can I do?
It can't damage the PIT partition by itself.
I had the same missing PIT problem on my old Galaxy Player 5.0 because i entered a Motorola partition code in the Terminal Emulator (Don't ask why....LMAO)
Yeah i couldn't fix it and i got a replacement.
Maybe check the symptoms of an Insane chip,some Note 2's have a hardware issue, maybe the Insane chip became "Insane" ? lol
Ok, bear with me here. It's always a long time between me flashing roms / generally messing with things so I usually am pretty rusty when it comes time to do it again (ie. I'm a bit of an idiot).
I was running Cyanogen 10.2 and everything was going fine since the install weeks ago. Last night I installed MyFitnessPal and again, everything seemed fine.
This morning I woke up, the handset seemed to be all functioning normally and the alarm went off etc.
I got up, got out of the shower, and the phone is bootlooping. What the?!
I've tried going into the bootloader and wiping cache, resorting factory settings, wiping dalvik cache etc. Nothing seems to be having any effect. It's still just booting, sitting there for about 7 seconds maximum with all my normal home screen settings/icons etc, then the screen goes funky colours and it makes a crack sound, and reboots. Just does that over and over.
I even tried the WugFresh toolkit to wipe it clean and force it to flash it back to stock. It hung for about 20mins on the 'writing system' part, so I figured I'd messed things up completely and just pulled the battery (it was otherwise unresponsive) and booted it up again.
Same normal lock screen / home screens, everything. Then rebooting.
I've tried all kinds of guides and nothing seems to be having any effect. Read something about the "emmc" but I don't know how to tell if that's my issue (is it hardware?!) or if it means the phone is unsalvagable apart from sending it for repair.
Any clues would be most appreciated. Pretty bummed with myself for not being able to work this out.
If you want to know if its the emmc that is fried just lock the bootloader. If its still unlocked then your emmc is fried. Backup everything you want to save from your phone first.
Sent from my Galaxy Nexus using xda app-developers app
mrgnex said:
If you want to know if its the emmc that is fried just lock the bootloader. If its still unlocked then your emmc is fried. Backup everything you want to save from your phone first.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Well... thanks but I can't relock the bootloader because WugFresh is telling me I need to be in USB debug mode. It was enabled when I was actually able to boot the phone and have it remain stable but since I can't keep it up for more than 7 seconds before it starts its bootloop again, I can't.
All I have is the bootloader and recovery mode.
And no amount of "Flash Stock + Unroot" seems to do anything. It's not writing any of the information despite saying it does, because all it does it just try and boot up my somehow broken cyanogen when it's done. Tried pushing .zips with adb sideloader but they don't have any effect either.
It's not looking promising. Since I can get into the bootloader and recovery I thought I'd be all good, but it seems not.
Hay so tell me, you tried flash factory image and it didn't work out?
Dont use root kits.. Learn it yourself
Sent from my Galaxy Nexus using xda app-developers app
skhjpz said:
Hay so tell me, you tried flash factory image and it didn't work out?
Click to expand...
Click to collapse
Hey Yep, I tried stock jellybean (takju-jwr66y-factory-5104ab1d) quite a few times and although everything seems to go fine, nothing gets written to memory because it still tries to boot my old bootlooping install. I've wiped everything imaginable in the recovery console and it all has zero effect.
mrgnex: I have tried locking the bootloader manually - I've tried everything I know how to do and everything I've been able to try and learn from all the information online and then went to the toolkits later on in case they did something I wasn't doing or filled in a gap I was missing. Not pretending to be an expert but I've done everything I've been capable of figuring out. The bootloader doesn't re-lock.
With everything I've done to it (including everything I SHOULDN'T be doing!) since it started bootlooping, it should be a doorstop by now. I can't even seem to make it any worse than it is now... let alone better! Hitting my head against a wall here.
Hmm... That's weird... So there is some OS installed, you done factory reset and still not booting up... Try using different toolkit then. Remember to install drivers!
skhjpz said:
Hmm... That's weird... So there is some OS installed, you done factory reset and still not booting up... Try using different toolkit then. Remember to install drivers!
Click to expand...
Click to collapse
Thanks - I've installed all the drivers and it recognises the phone in both bootloader and normal running mode (for as long as it stayed booted up!).
Tried manually flashing, WugFresh toolkit and Skipsoft Toolkit.
Yes, there is an OS installed - Cyanogen 10.2.0 but it bootloops. It was running fine since having been flashed on there weeks ago, up until yesterday morning.
mickeyflip said:
Thanks - I've installed all the drivers and it recognises the phone in both bootloader and normal running mode (for as long as it stayed booted up!).
Tried manually flashing, WugFresh toolkit and Skipsoft Toolkit.
Yes, there is an OS installed - Cyanogen 10.2.0 but it bootloops. It was running fine since having been flashed on there weeks ago, up until yesterday morning.
Click to expand...
Click to collapse
are you able to do factory reset?
mickeyflip said:
Thanks - I've installed all the drivers and it recognises the phone in both bootloader and normal running mode (for as long as it stayed booted up!).
Tried manually flashing, WugFresh toolkit and Skipsoft Toolkit.
Yes, there is an OS installed - Cyanogen 10.2.0 but it bootloops. It was running fine since having been flashed on there weeks ago, up until yesterday morning.
Click to expand...
Click to collapse
So try push to device another ROM (carbon or something) then flash it with clean install. It should work. After that try to flash CM again and do a backup
mickeyflip said:
Thanks - I've installed all the drivers and it recognises the phone in both bootloader and normal running mode (for as long as it stayed booted up!).
Tried manually flashing, WugFresh toolkit and Skipsoft Toolkit.
Yes, there is an OS installed - Cyanogen 10.2.0 but it bootloops. It was running fine since having been flashed on there weeks ago, up until yesterday morning.
Click to expand...
Click to collapse
Do you have twrp recovery? If not flash it from the bootloader. You can use adb push from recovery. Push another rom and flash it see if that helps.
---------- Post added at 08:14 AM ---------- Previous post was at 07:50 AM ----------
DR3W5K1 said:
Do you have twrp recovery? If not flash it from the bootloader. You can use adb push from recovery. Push another rom and flash it see if that helps.
Click to expand...
Click to collapse
If it still bootloops your internal storage is most likely dead. The only other thing I can suggest is to repartition the internal storage. This thread may be of some assistance with that... http://forum.gsmhosting.com/vbb/f63...-p1000-i9023-i9020t-m200s-variations-1619226/
---------- Post added at 08:16 AM ---------- Previous post was at 08:14 AM ----------
DR3W5K1 said:
Do you have twrp recovery? If not flash it from the bootloader. You can use adb push from recovery. Push another rom and flash it see if that helps.
---------- Post added at 08:14 AM ---------- Previous post was at 07:50 AM ----------
If it still bootloops your internal storage is most likely dead. The only other thing I can suggest is to repartition the internal storage. This thread may be of some assistance with that... http://forum.gsmhosting.com/vbb/f63...-p1000-i9023-i9020t-m200s-variations-1619226/
Click to expand...
Click to collapse
One last thing make sure to do a factory reset or data wipe in recovery before flashing the new ROM.
I've tried all of your suggestions, thank you! But none of them have had any effect despite LOOKING like they've worked while I'm actually doing it. It just boots the same old bootlooping OS nonsense. It's just not writing anything - I can't affect it either negatively or positively. So stubborn! Done the data wipes, cache wipes etc. Says it wipes but actually does nothing because it's all still there when I reboot.
I don't have TWRP, no... I do have CWM recovery though. Flashed a few different roms through that just for science, as well as factory resetting, and as I have already stated, it doesn't work. Seems like it works, goes through the whole process... but when I boot up afterwards it's as if nothing was changed and bootloops all over again with the same old OS.
The only thing I haven't tried is repartioning. I've already ordered a new phone now but I'd still like to get this one going again if I can. Going to look into the repartitioning in the morning.
Thank you!
mickeyflip said:
I've tried all of your suggestions, thank you! But none of them have had any effect despite LOOKING like they've worked while I'm actually doing it. It just boots the same old bootlooping OS nonsense. It's just not writing anything - I can't affect it either negatively or positively. So stubborn! Done the data wipes, cache wipes etc. Says it wipes but actually does nothing because it's all still there when I reboot.
I don't have TWRP, no... I do have CWM recovery though. Flashed a few different roms through that just for science, as well as factory resetting, and as I have already stated, it doesn't work. Seems like it works, goes through the whole process... but when I boot up afterwards it's as if nothing was changed and bootloops all over again with the same old OS.
The only thing I haven't tried is repartioning. I've already ordered a new phone now but I'd still like to get this one going again if I can. Going to look into the repartitioning in the morning.
Thank you!
Click to expand...
Click to collapse
I hope your able to fix it! Seems like I have seen allot of threads with this problem lately. I guess even though flash memory is less prone to failure than a mechanical drive it still happens.
Good luck!
DR3W5K1 said:
I hope your able to fix it! Seems like I have seen allot of threads with this problem lately. I guess even though flash memory is less prone to failure than a mechanical drive it still happens.
Good luck!
Click to expand...
Click to collapse
Aaaahhhh damn it. Still no good. It's nothing but a liar I tell you! I guess I'll have to resign myself to the fact that this thing is toast.
I just followed this as a last ditch attempt and that actually failed rather than everything else lying about its success. Not sure if it means anything to anyone, but it sure doesn't to me. (Didn't change anything, it still boots the old bootlooper... lol )
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> odin.takju.4.3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<ID:0/008> Removed!!
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!!
<ID:0/008> bootloader.img
<ID:0/008> radio.img
<ID:0/008> recovery.img
<ID:0/008> system.img
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hi a few days ago my phone was restarted and it got stuck on the samsung galaxy s3 screen. It is a t-mobile sgh-t999 model. It will boot into download mode but not recovery. After trying Kies to no result. I have deleted it from my pc and attempted to recover by flashing the stock rom using odin. I've tried that many times and always fails as well.
I have reinstalled s3 drivers. Made sure Kies is completely gone. I have downloaded the stock rom and three versions of Odin 3.04 3.07 and 3.09 and I get the same results. A write failure. Does anyone have any ideas how to proceed?
One observation I've noticed is that the bar underneath the Android in Download mode never appears. Which leads me to think that it never starts the process of taking the firmware.
Any ideas what to do next?
What is the error message?
Having same trouble
hi Serio22
NAND Write Start!!
FAIL!
Complete(write) operation failed.
serio22 said:
What is the error message?
Click to expand...
Click to collapse
Hi Serio22
NAND Write Start!!
FAIL!
Complete(write) operation failed.
Same exact issue on my sgh-t999
This morning it restarted itself (plugged into charger all night) and stuck at Samsung Galaxy SIII on screen. Recovery doesn't work and it will go into download mode. I am downloading the stock firmware from (sammobile firmwares SGH-T999) and will try installing with Odin tomorrow.
I will likely fail like you guys. I have taken such good care of the phone, never drop it, not a scratch on the screen...and this randomly happens in the middle of the night.
Please update!
Same exact issue on my SGH-T999 which makes me wonder that this is some software update issue that has possibly impacted many phones at this time.
In my case, it also restarted by itself this morning and got stuck at Samsung Galaxy SIII on screen. I started from figuring out if it was a hardware issue but the phone seems OK physically (i.e. the power button is not stuck, etc.). Recovery doesn't work and it will go into download mode like indicated by others above. I tried downloading the stock firmware SGH-T999 from Sammobile (actually a couple of different versions and tried installing via Odin 3.-07 many times but always failed with the error message above or
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
I also tried installing non-stock recovery files (TWRP, trying CWM at the moment) and that worked but without success in changing anything in the initial issue.
Sounds like they are sending bad firmware bricking our phones over night. Sorry I've found no solution yet.
whattheschmidt said:
Same exact issue on my sgh-t999
This morning it restarted itself (plugged into charger all night) and stuck at Samsung Galaxy SIII on screen. Recovery doesn't work and it will go into download mode. I am downloading the stock firmware from (sammobile firmwares SGH-T999) and will try installing with Odin tomorrow.
I will likely fail like you guys. I have taken such good care of the phone, never drop it, not a scratch on the screen...and this randomly happens in the middle of the night.
Please update!
Click to expand...
Click to collapse
Just an observation. I too was only getting the
"Complete (Write) operation failed." message at first.
After trying to flash the stock rom via Odin multiple times, I now get
"NAND Write Start!!"
"FAIL!"
Hope I didn't make it worse.
MarcinT said:
Same exact issue on my SGH-T999 which makes me wonder that this is some software update issue that has possibly impacted many phones at this time.
In my case, it also restarted by itself this morning and got stuck at Samsung Galaxy SIII on screen. I started from figuring out if it was a hardware issue but the phone seems OK physically (i.e. the power button is not stuck, etc.). Recovery doesn't work and it will go into download mode like indicated by others above. I tried downloading the stock firmware SGH-T999 from Sammobile (actually a couple of different versions and tried installing via Odin 3.-07 many times but always failed with the error message above or
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
I also tried installing non-stock recovery files (TWRP, trying CWM at the moment) and that worked but without success in changing anything in the initial issue.
Click to expand...
Click to collapse
SGH -t999 Pit File
Does anyone have any idea if flashing the stock rom with the T999 pit file in Odin possibly fix this problem? I've been reading about it, but can't really determine if this is the next step to troubleshoot this problem.
Write start and immediate fail in my case as well.
Keep looking into this and updating thread. I already ordered a new phone because of this but will want to fix this phone to sell it if not just sell the new one and stick with this longer...
I tried updating to the newest version of ROM using Kies but that did not work, either. Sometimes the phone cannot be recognized by Windows and sometimes Kies says it is "connecting" with the phone. When I tried updating, Kies did not see the phone, so maybe it had a negative impact on the download. I am going to uninstall the drivers and install them again just before connecting the phone to Kies and try updating again. This stuff is really time consuming.
I could not find a good CWM recovery file to flash via Odin so I did not try that. The interesting thing is that successfully flashing TWRP recovery file did not do anything - I still cannot get into recovery mode. Then I tried flashing stock recovery file again - and got the FAIL! message from Odin.
I've seen other threads talking about this issue, but don't remember if it was ever fixed. Have you guys tried different cables or computers?
I've tried a different cable (non-stock) but that did not help at all. I can try a different computer and will report here.
No update on fixing the phone...I tried everything I could on my end really. I think I will have to look at sending it in to Samsung?
I bought a used S5 on ebay. Much faster and nicer...liking it quite a bit. Samsungs update to break my phone and buy a newer Samsung worked I guess.
Daughter's SIII crashed also, her phone was bootlooping. Since her volume button doesn't work, I used a jig to put into D/L mode. Flashed T999LUVUBOH1_T999LTMBBOH1_T999LUVUBOH1_HOME.tar.md5 from Sammobile and ODIN said it passed. The phone will not go passed the "T-Mobile 4G LTE" screen. I've tried several times, always passes, always gets stuck.
Daughter doesn't mind, she's been using the Note II that I didn't want to part with after getting myself the Note 5
When flashing the stock rom with Odin, do not check anything except f.reset time. After flashing, and seeing the word reset in the status window, remove USB cable, remove battery, replace battery, boot into recovery, assuming the volume up me home button work, no perform a factory wipe.
The volume up and down button don't work?
I'm trying to flash stock PIE firmware and the tablet gets stuck at system.img.ext4. It never fails and I let it keep running for 20+ minutes. I tried it a second time and no luck either.
Just to confirm, I should use CSC not HOME CSC if I want it to be formatted to clean stock right?
Any idea what else could be wrong?
Ahhh, noob error. I was using a USB-C to USB-C cable.
I used a USB 2.0 and all is well, flashed smooth.