Database Info

[Q] [i9003] Bootloop after flashing

Hello everyone!
I had some stability issues on my Samsung GT-I9003, so I flashed it . And, as the title says it, I'm stuck in a bootloop. I've tried 3 or 4 flashings with different packages. Some where "One packages", with one unique PDA, or I tried the XXKPE with everything. And I'm lost. I never get past the first boot screen.
[EDIT]
I found a way to boot it, but the touchscreen isn't working, so I'm now stuck on the language selection page...
Is it my ROM who doesn't fit?
[/EDIT]
Thanks!

Before going to download mode try wiping everything, then flash xxkpe TWICE then wipe again. Make sure you flash it correctly. And odin shows PASS. Try flashing the latona.pit included in xxkpe.
Press thanks if it helped..
Sent from my GT-I9003 using XDA

Thanks for the answer!
Problem is it didn't work!
I got a little deeper in the problem. In order to boot to android, I need to flash the bagaria root file. It contains the normalboot image. So I assume that the boot is corrupted. I'd add that after the rooting, the android recovery boots and wipes everything, but he says that the CSC wasn't installed, because "[...]/stl11" is not there. Is it the .pit?
I'm lost, again...
Thanks a lot for your help!

jonasdu91 said:
Thanks for the answer!
Problem is it didn't work!
I got a little deeper in the problem. In order to boot to android, I need to flash the bagaria root file. It contains the normalboot image. So I assume that the boot is corrupted. I'd add that after the rooting, the android recovery boots and wipes everything, but he says that the CSC wasn't installed, because "[...]/stl11" is not there. Is it the .pit?
I'm lost, again...
Thanks a lot for your help!
Click to expand...
Click to collapse
so weird. Where did you download your xxkpe. Try here
http://forum.xda-developers.com/showthread.php?t=1004647
then follow the guide here
http://forum.xda-developers.com/showthread.php?p=14933114
I think you just fail a step on flashing a rom.
---------- Post added at 09:16 PM ---------- Previous post was at 09:14 PM ----------
Flashing bagaria root is done after flashing a stock rom for it to be rooted. You failed to put CSC file in odin maybe. Follow the guide above perfectly then everything will be fine.
You start the procedure on Step 3 if your done downloading XXKPE here
http://forum.xda-developers.com/showthread.php?t=1004647

jonasdu91 said:
Thanks for the answer!
Problem is it didn't work!
I got a little deeper in the problem. In order to boot to android, I need to flash the bagaria root file. It contains the normalboot image. So I assume that the boot is corrupted. I'd add that after the rooting, the android recovery boots and wipes everything, but he says that the CSC wasn't installed, because "[...]/stl11" is not there. Is it the .pit?
I'm lost, again...
Thanks a lot for your help!
Click to expand...
Click to collapse
/stl11 is the /cache partition.
look like you fail to flash pit file, or u flash "one package .tar file" with partition ticked in odin.
see below for the samsung recommend setup
flash pit file with all the firmware one short.
if you flash from Froyo to GB, i recommend to flash the bootloader update.
however, flash on you own risk.

100% Work!
Hi.
Flash this Chinese rom, with Odin 1.85.
latona_open_china_20101222_r01.pit---------------->PIT
I9003ZCKC1-REV08-ALL-low-CL961866------------>PDA
MODEM_I9003ZCKC1_REV_00_CL866730------->PHONE
I9003-CSC-MULTI-OZH961866------------------------->CSC
Enjoy.
100% Works for me.

For those who are struck in boot loop or Softbrick their mobile do the following things exactly as they had mentioned. I followed them and boom my phone is back to normal.
For bringing your phone back to download mode (Recovering from Softbrick)
http://forum.xda-developers.com/showthread.php?t=1411768
After entering into download mode (reinstall Ginger bread )
http://forum.xda-developers.com/showthread.php?t=1133787
Note: This step deletes your user data, so be sure what you are doing
Definitely your phone should be back to normal if you follow these steps exactly.....
Million Thanks to all those who helped me in bringing back my mobile to normal function....

Hi, I am facing the same issue with a GT-I9003 as jonasdu91. I tried all the solutions mentioned above, tried all sort of firmwares. The only time the phone responded was when I flashed the bagaria file. That too ended up with a non-responsive touchscreen at the language selection screen.
Could anyone suggest what more could I do to get the phone to upgrade?

ghassir said:
Hi.
Flash this Chinese rom, with Odin 1.85.
latona_open_china_20101222_r01.pit---------------->PIT
I9003ZCKC1-REV08-ALL-low-CL961866------------>PDA
MODEM_I9003ZCKC1_REV_00_CL866730------->PHONE
I9003-CSC-MULTI-OZH961866------------------------->CSC
Enjoy.
100% Works for me.
Click to expand...
Click to collapse
Worked for me too!!! You saved my life! Thanks!

ghassir said:
Hi.
Flash this Chinese rom, with Odin 1.85.
latona_open_china_20101222_r01.pit---------------->PIT
I9003ZCKC1-REV08-ALL-low-CL961866------------>PDA
MODEM_I9003ZCKC1_REV_00_CL866730------->PHONE
I9003-CSC-MULTI-OZH961866------------------------->CSC
Enjoy.
100% Works for me.
Click to expand...
Click to collapse
Good!

ghassir said:
Hi.
Flash this Chinese rom, with Odin 1.85.
latona_open_china_20101222_r01.pit---------------->PIT
I9003ZCKC1-REV08-ALL-low-CL961866------------>PDA
MODEM_I9003ZCKC1_REV_00_CL866730------->PHONE
I9003-CSC-MULTI-OZH961866------------------------->CSC
Enjoy.
100% Works for me.
Click to expand...
Click to collapse
How do I flash other stock rom after that? I've tried to flash XXLE4 rom, and received boot error and unmounted FS

Hello everyone, an acquaintance of mine, had initially given his Galaxy SL device to a friend of his, asking him, to 'update' the software on the device. The device had come with Android 2.2.1, pre-installed on it (PDA: I9003DDKB2; PHONE: I9003DDKA5; CSC: I9003ODDKA6).
Apparently, my acquaintance's friend flashed the I9003DDMF1 stock Gingerbread firmware via PC ODIN, and after my acquaintance gave me the device, I noticed, it did not boot to a home screen. It would boot loop at the Samsung boot animation.
The device boots into Download Mode, but does not get into the stock Recovery Mode. So, I attempted numerous remedial procedures. I used PC ODIN3 v1.85 for all flashing instances.
Keeping Misledz's guide, http://forum.xda-developers.com/showthread.php?t=1133787, as a reference, I flashed the I9003XXKPE firmware package, followed by the I9003XXKPQ_I9003SERKPQ_SER firmware.
After PC ODIN gave a PASS for the I9003XXKPE firmware package flashing instance, the device rebooted, and I observed a process, looking like the stock Recovery Mode, continuing on the device. There were a couple of strings, displayed in red colour. The device rebooted again to the Samsung logo, and I had to pull the battery out, to continue with the I9003XXKPQ_I9003SERKPQ_SER firmware flashing instance. After PC ODIN displayed the PASS sign and the device rebooted, I unplugged the USB cable, but the boot loop at Samsung boot animation persisted.
Since the above mentioned procedure did not solve the boot loop issue, I decided to take the device back to a stock Froyo firmware, and if successful, reattempt to 'update' the device to stock Gingerbread (2.3.6), by following Misledz's guide. I flashed the I9003_XXKB1 stock Froyo firmware, but this time, the device would not go beyond the Samsung logo.
As a momentary last attempt, before seeking help here, I flashed the I9003ZCKC1 firmware package, but yet, the device does not go beyond the Samsung logo.
All the flashing instances completed successfully on PC ODIN.
Is it possible to revive the device, such that it boots to a home screen and is functional again? I desperately need help.

YLNdroid said:
Hello everyone, an acquaintance of mine, had initially given his Galaxy SL device to a friend of his, asking him, to 'update' the software on the device. The device had come with Android 2.2.1, pre-installed on it (PDA: I9003DDKB2; PHONE: I9003DDKA5; CSC: I9003ODDKA6).
Apparently, my acquaintance's friend flashed the I9003DDMF1 stock Gingerbread firmware via PC ODIN, and after my acquaintance gave me the device, I noticed, it did not boot to a home screen. It would boot loop at the Samsung boot animation.
The device boots into Download Mode, but does not get into the stock Recovery Mode. So, I attempted numerous remedial procedures. I used PC ODIN3 v1.85 for all flashing instances.
Keeping Misledz's guide, http://forum.xda-developers.com/showthread.php?t=1133787, as a reference, I flashed the I9003XXKPE firmware package, followed by the I9003XXKPQ_I9003SERKPQ_SER firmware.
After PC ODIN gave a PASS for the I9003XXKPE firmware package flashing instance, the device rebooted, and I observed a process, looking like the stock Recovery Mode, continuing on the device. There were a couple of strings, displayed in red colour. The device rebooted again to the Samsung logo, and I had to pull the battery out, to continue with the I9003XXKPQ_I9003SERKPQ_SER firmware flashing instance. After PC ODIN displayed the PASS sign and the device rebooted, I unplugged the USB cable, but the boot loop at Samsung boot animation persisted.
Since the above mentioned procedure did not solve the boot loop issue, I decided to take the device back to a stock Froyo firmware, and if successful, reattempt to 'update' the device to stock Gingerbread (2.3.6), by following Misledz's guide. I flashed the I9003_XXKB1 stock Froyo firmware, but this time, the device would not go beyond the Samsung logo.
As a momentary last attempt, before seeking help here, I flashed the I9003ZCKC1 firmware package, but yet, the device does not go beyond the Samsung logo.
All the flashing instances completed successfully on PC ODIN.
Is it possible to revive the device, such that it boots to a home screen and is functional again? I desperately need help.
Click to expand...
Click to collapse
Firstm download this XXKPE: https://disk.yandex.ru/public/?hash=mTOUkkpPv4WgFtvIpy07S2CwUoU5gUcna1FTdjKHc90=
and flash it.
Put the files like this:
PIT - latona_20110114.pit
PDA - I9003XXKC1-REV08-PDA-low-CL964212.tar.md5
PHONE - MODEM_I9003XXKC1_REV_00_CL964949.tar.md5
CSC - GT-I9003-CSC-SERKC1.tar.md5
Click to expand...
Click to collapse
It contains all 5 files needed to boot your phone. This will repartition your phone and make it alive, after that, you may flash any 2.3.x ROM you like.

xumix said:
Firstm download this XXKPE: https://disk.yandex.ru/public/?hash=mTOUkkpPv4WgFtvIpy07S2CwUoU5gUcna1FTdjKHc90=
and flash it.
It contains all 5 files needed to boot your phone. This will repartition your phone and make it alive, after that, you may flash any 2.3.x ROM you like.
Click to expand...
Click to collapse
xumix, thank you very much for your response.
I believe, the 5 files contained within the I9003XXKPE_Odin3_1.8.5.zip package, would correspond to the options available in PC ODIN3 v1.85, as follows -
PIT > latona_20110114.pit
BOOTLOADER > APBOOT_I9003XXKPE_CL409735_REV08_user_low_ship.tar.md5
PDA > CODE_I9003XXKPE_CL409735_REV08_user_low_ship.tar.md5
PHONE > MODEM_I9003XXKPE_REV_00_CL1041909.tar.md5
CSC > GT-I9003-CSC-MULTI-OXAKPE.tar.md5
Click to expand...
Click to collapse
Am I right?
:silly:

YLNdroid said:
Am I right?
:silly:
Click to expand...
Click to collapse
You are right

xumix said:
You are right
Click to expand...
Click to collapse
xumix, I flashed the I9003XXKPE_Odin3_1.8.5.zip firmware package using PC ODIN3 v1.85, but to no avail. The boot loop on the Samsung boot animation continues to persist.
EDIT
I have noticed there is a u1_02_20110310_emmc_EXT4.pit, contained within the Odin3-v1.85 folder. What is this, PIT file for?

I re-flashed the I9003XXKPE_Odin3_1.8.5.zip firmware package using PC ODIN3 v1.85, and the process completed successfully. But, since the boot loop at the Samsung boot animation persisted, I pulled the battery out, and booted into Recovery Mode, not once, but on two separate instances. I was able to perform a wipe data/factory reset, on the second instance. I also performed a wipe cache partition and rebooted the device. But, the boot loop issue still continues.
I have attached images of both instances, I clicked using another device, to this post.

If dont mind. Try my step below.
In download mode
Flash pit file alone. Make sure repartition is ticked.
Phone will black screen, you pull out battery and put back.
Download mode again. Flash xxkpe without pit file.
BTW, you error show properly is emmc chip broken, hope it is not.
Sent from my GT-I9003 using Tapatalk

chongns said:
If dont mind. Try my step below.
In download mode
Flash pit file alone. Make sure repartition is ticked.
Phone will black screen, you pull out battery and put back.
Download mode again. Flash xxkpe without pit file.
BTW, you error show properly is emmc chip broken, hope it is not.
Click to expand...
Click to collapse
chongns, I followed your stepwise suggestions, to the word, but unfortunately, the boot loop issue still persists. One distinct error under the stock recovery is, E:format_volume: rfs format failed on /dev/block/mmcblk0p3. Am I correct to believe this error strongly indicates, or rather confirms, the internal SD is damaged?
Also, what are the possible causes (physical, and or, logical) that would damage the internal SD? Is it worth sending the device to an authorised Samsung service centre, for an appropriate repair process?

YLNdroid said:
chongns, I followed your stepwise suggestions, to the word, but unfortunately, the boot loop issue still persists. One distinct error under the stock recovery is, E:format_volume: rfs format failed on /dev/block/mmcblk0p3. Am I correct to believe this error strongly indicates, or rather confirms, the internal SD is damaged?
Also, what are the possible causes (physical, and or, logical) that would damage the internal SD? Is it worth sending the device to an authorised Samsung service centre, for an appropriate repair process?
Click to expand...
Click to collapse
Friends, I still await your expertise.
:fingers-crossed:

Stuck in Update boot loop Please Help!!!

I was rooted with CWM recovery. I odin flashed stock with root injected and then flashed via odin stock kernel and recovery. At this time I was able to pull the update and the device restarted to install. Upon 100% completion the device rebooted as I woudl expect but upon reboot it goes right back into the install, hits 100% and does the same thing. It appears Im stuck in a update boot loop. Has anyone else experienced this?
I did a odin restore with Stock 8013.tar with root injected but upon reboot once odin completes it goes right back into this update loop. Someone please help!!!!

ej_424 said:
I was rooted with CWM recovery. I odin flashed stock with root injected and then flashed via odin stock kernel and recovery. At this time I was able to pull the update and the device restarted to install. Upon 100% completion the device rebooted as I woudl expect but upon reboot it goes right back into the install, hits 100% and does the same thing. It appears Im stuck in a update boot loop. Has anyone else experienced this?
I did a odin restore with Stock 8013.tar with root injected but upon reboot once odin completes it goes right back into this update loop. Someone please help!!!!
Click to expand...
Click to collapse
Just flashed stock kernel and recovery via odin and same thing happens. Just after samsung logo on splash screen it goes into the android character with a percentage for an update being applied. It hits 100% and sits there for a couple minutes, reboots and does the same thing all over.
I"m desperate and need this to get fixed!!

ej_424 said:
Just flashed stock kernel and recovery via odin and same thing happens. Just after samsung logo on splash screen it goes into the android character with a percentage for an update being applied. It hits 100% and sits there for a couple minutes, reboots and does the same thing all over.
I"m desperate and need this to get fixed!!
Click to expand...
Click to collapse
I flashed the stock n8000 recovery file via odin and it booted me out of the update loop. I had to do it twice tho. I rooted via odin so our fixes may be different.
I used file posted here http://forum.xda-developers.com/showthread.php?p=30450339#post30450339 post 45
Hope this helps a little

ej_424 said:
I was rooted with CWM recovery. I odin flashed stock with root injected and then flashed via odin stock kernel and recovery. At this time I was able to pull the update and the device restarted to install. Upon 100% completion the device rebooted as I woudl expect but upon reboot it goes right back into the install, hits 100% and does the same thing. It appears Im stuck in a update boot loop. Has anyone else experienced this?
I did a odin restore with Stock 8013.tar with root injected but upon reboot once odin completes it goes right back into this update loop. Someone please help!!!!
Click to expand...
Click to collapse
ej_424 said:
Just flashed stock kernel and recovery via odin and same thing happens. Just after samsung logo on splash screen it goes into the android character with a percentage for an update being applied. It hits 100% and sits there for a couple minutes, reboots and does the same thing all over.
I"m desperate and need this to get fixed!!
Click to expand...
Click to collapse
Ok I'm backup and running. I had to flash "HighonAndroidCWMRecovery" via odin to get past the update loop. Any ideas why this woudl be? I'm running stock with root and custom recovery. If I flash stock recvoery again and attempt the update do you think the same thing will occur?

ej_424 said:
Ok I'm backup and running. I had to flash "HighonAndroidCWMRecovery" via odin to get past the update loop. Any ideas why this woudl be? I'm running stock with root and custom recovery. If I flash stock recvoery again and attempt the update do you think the same thing will occur?
Click to expand...
Click to collapse
This need not be so complicated follow directions here http://forum.xda-developers.com/showthread.php?t=1847054&page=6 see post 58 and 39

Stuck, can't restore factory settings
I tried to unroot my Galaxy note 10.1 wi-fi and have caused such damage that it won't boot up. I have tried to press the power and down volume and I either get the Black welcome screen stuck, requesting I download the md5 file (which I have tried and doesn't work) or asks to use Kies to boot, but my laptops won't even pick up the device, they recognizes that there is a new device connected but it can't read it!
In the top left hand corner it reads
ODIN MODE (in red letters)
Product name: GT-N8010
Customer binary: yes (20 counts)
Current Binary: Custom
System status: Custom
PLEASE HELP!!!!
Thanks in advance

bee_rob said:
I tried to unroot my Galaxy note 10.1 wi-fi and have caused such damage that it won't boot up. I have tried to press the power and down volume and I either get the Black welcome screen stuck, requesting I download the md5 file (which I have tried and doesn't work) or asks to use Kies to boot, but my laptops won't even pick up the device, they recognizes that there is a new device connected but it can't read it!
In the top left hand corner it reads
ODIN MODE (in red letters)
Product name: GT-N8010
Customer binary: yes (20 counts)
Current Binary: Custom
System status: Custom
PLEASE HELP!!!!
Thanks in advance
Click to expand...
Click to collapse
I have same Problem

My only response would be to go to sammobile and download as close to shipped rom as you can (must be for your region and carrier, if from carrier), updated rom is fine. Make sure the download ISN'T corrupted by doing an MD5 check.. Also before f;lashing, make sure you exit KIES as this can screw up the connection in ODIN.
Put in Download mode, hold down volume and power until it says a scary warning, ignore the warning and press up volume.
Flash with ODIN making sure re-partition ISN'T ticked, when it finishes flashing turn off power.
Go to recovery by holding up volume and power button until it goes into recovery.
Wipe data/cache and then wipe dalvik cache.
Reboot and see what happens.
Good luck.

ultramag69 said:
My only response would be to go to sammobile and download as close to shipped rom as you can (must be for your region and carrier, if from carrier), updated rom is fine. Make sure the download ISN'T corrupted by doing an MD5 check.. Also before f;lashing, make sure you exit KIES as this can screw up the connection in ODIN.
Put in Download mode, hold down volume and power until it says a scary warning, ignore the warning and press up volume.
Flash with ODIN making sure re-partition ISN'T ticked, when it finishes flashing turn off power.
Go to recovery by holding up volume and power button until it goes into recovery.
Wipe data/cache and then wipe dalvik cache.
Reboot and see what happens.
Good luck.
Click to expand...
Click to collapse
Not working, not go the Recovery Mode, Only Samsung Logo.

I'm having similar issue as Odin keeps failing when trying to flash ROM.
Does anyone know the commands to do it through ADB? I've done it before on my nexus7 but don't know the commands to exactly use for the note. I still can't get into recovery. Only can get into that ODIN mode. I have all drivers and Android ADB installed on PC.
It seems like nothing will write to the NAND. Although my flash count changes now showing my attempts. I might have no choice but to call Samsung and file a warranty claim. I just don't want to lose all the pictures and info that's in my tablet.

Well I got my tablet back yesterday from Samsung. They fixed it. The report showed they replaced some piece that burned out. I forgot the name of it. Unfortunately all my info and stuff was erased. So I had to reinstall everything manually. At least my tablet working like new again. So glad to have it back. Been like a month or so since I've been able to use it. My nexus 7 and galaxy s3 was holding me down in the meanwhile.
This note is a great device. IM seeing again why I've missed it so much. Works flawlessly on stock Tom.

[Q] Need help recovering my S3 -- TWRP ADB Sideload not working

I pulled a boneheaded move and ended up formatting my phone from within the TWRP menu. Now the stock operating system is gone.
I wanted to put on one of the Gummy Nightly builds, but I'm new to TWRP and selected the wrong options while wiping.
So now I have the Gummy ROM on my PC, the phone is connected to my PC and in TWRP (in the advanced adb sideload feature), but adb will not recognize my phone.
When I check device manager, SAMSUNG_Android_SCH-I535 is there, but with a yellow "cauton" symbol. When I look at properties, it tells me that "The drivers for this device are not installed (Code 28).
I went out to the Samsung page and got the exe to unpack drivers on my machine... I've tried "update driver" and pointing to the root of the directory containing the Samsung drivers, but my PC claims none of them are applicable.
So what I'm looking for here is:
(1) How do I get this ROM on my phone so that I can install the zip and have a working OS again?
(2) Assuming that using the ADB Sideload feature of TWRP is my best option, how do I get the device drivers for my galaxy s3 installed to my windows 8 PC and get adb to detect it?
Thanks in advance.

Ok, so it seems to have gotten worse.
I cannot get my windows installation to recognize the phone without it being able to boot an android OS, it seems.
I had it in TWRP 2.6.0.0, but as I was trying to reboot to see if I could get into download mode (my thought being to change out TWRP for Clockwork; I seem to remember Clockwork Recovery having a "mount as USB" option which TWRP seems to lack), it tried to root the file system.
After that, the screen went black and nothing happened... the phone was unresponsive. I would remove the battery and replace it to have it vibrate once and then not respond to any key presses.
I removed the battery, SD card, and SIM card, replacing only the battery and got it to turn on and show a Samsung Galaxy SIII logo... but it's just sitting there... I'm assuming it's frozen because there's no OS to boot on the internal storage.
Please help me recover my phone!

Ok, so I've found I can still get into download mode, but not into recovery.
Recovery seems to lead to a black screen with nothing on it.
Trying to boot normally leads to the statis Samsung Galaxy SIII logo.
Can I fix my phone from the download menu?
Please help me.

Install kies and at the end of the install make sure you check install unified drivers. Then flash root66 through Odin. After that you should be good to install ROMs again.

ThePagel said:
Install kies and at the end of the install make sure you check install unified drivers. Then flash root66 through Odin. After that you should be good to install ROMs again.
Click to expand...
Click to collapse
Thanks for the reply!
Sorry, I'm a little out of date on the flashing and stuff -- I was just over in the thread where the poster thought he half softbricked his phone and was asking about 4.1.2 vs. 4.3
I see this at the top of my screen sitting here in download mode:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: YES (6 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
It seems my bootloader got relocked somehow -- is this why my phone just goes to black screen when I attempt to boot into recovery -- even if I have TWRP or CWR installed? Odin claims I just pushed philz custom CWR to my PDA section, but it still won't go into recovery.
What are my options here?

You are pre 4.3 I'll help you more in the morning if no one else does first.

ThePagel said:
You are pre 4.3 I'll help you more in the morning if no one else does first.
Click to expand...
Click to collapse
Ok, thanks -- I appreciate that someone's willing to help! Googling stuff is just getting me more and more confused.
I'll stay tuned for help and turn off my phone so I don't screw things up further in the meantime.
My desired result here, I think is to have my bootloader remain unlocked (as I was under the impression it was, since I was running TWRP with rooted stock ROM), with CWR as the custom recovery software and Gummy as my current ROM.
Side note: I've noticed I don't even get a battery indicator on the main screen now when I press the home button -- is this because of whatever's causing my recovery to not work (and the potential lack of an OS)?
Thanks in advance.

corrosivefrost said:
Ok, thanks -- I appreciate that someone's willing to help! Googling stuff is just getting me more and more confused.
I'll stay tuned for help and turn off my phone so I don't screw things up further in the meantime.
My desired result here, I think is to have my bootloader remain unlocked (as I was under the impression it was, since I was running TWRP with rooted stock ROM), with CWR as the custom recovery software and Gummy as my current ROM.
Side note: I've noticed I don't even get a battery indicator on the main screen now when I press the home button -- is this because of whatever's causing my recovery to not work (and the potential lack of an OS)?
Thanks in advance.
Click to expand...
Click to collapse
Once you in download mode, can your Odin see your phone?

buhohitr said:
Once you in download mode, can your Odin see your phone?
Click to expand...
Click to collapse
I believe it can. After TWRP stopped working, I tried to replace it with CWR and the digital flash count went up (Odin showed no errors on the flash) -- recovery still won't work though, holding vol+/home/power simply gives me a black screen after I see the SAMSUNG logo with the recovery boot text in the upper left.

corrosivefrost said:
I believe it can. After TWRP stopped working, I tried to replace it with CWR and the digital flash count went up (Odin showed no errors on the flash) -- recovery still won't work though, holding vol+/home/power simply gives me a black screen after I see the SAMSUNG logo with the recovery boot text in the upper left.
Click to expand...
Click to collapse
What stock version do you have on your phone right now?

buhohitr said:
What stock version do you have on your phone right now?
Click to expand...
Click to collapse
None? :silly:
I think before this fiasco, it was running whatever version was previous to the new VZW update.
It was the fact that the new update was trying to install and failing repeatedly (because my bootloader was unlocked, I think?) that prompted me to look into finally switching to a ROM. However, my unfamiliarity with TWRP led to me formatting my phone (everything, it seems, including the SD card)... so I'm not really sure what' "on the phone right now". :\
I'm really not sure what kind of state anything is in at this point -- other than Odin seemingly working and being able to get into download mode.
Again, short version of what happened:
(1) Accidentally did a full wipe (factory reset?) in TWRP -- this wiped the ROM I was going to install with TWRP off the phone.
(2) While trying to ADB sideload from TWRP and telling TWRP to reboot, TWRP tried to install supersu.
(3) After (2), I was unable to get back into recovery mode. I got into Odin and tried to flash philz customer clockwork recovery and it seemed successful. Reboot and attempt to enter recovery still fails. Samsung logo with recovery mode text appears, but then the screen goes black.
(4) Normal boot leaves the screen stuck on the Samsung Galaxy SIII logo indefinitely.

corrosivefrost said:
None? :silly:
I think before this fiasco, it was running whatever version was previous to the new VZW update.
It was the fact that the new update was trying to install and failing repeatedly (because my bootloader was unlocked, I think?) that prompted me to look into finally switching to a ROM. However, my unfamiliarity with TWRP led to me formatting my phone (everything, it seems, including the SD card)... so I'm not really sure what' "on the phone right now". :\
Click to expand...
Click to collapse
OK, download this image and flash with Odin(you should be using Odin version 3.07) http://goo.im/devs/invisiblek/i535/stock.vzw_root66.tar This should bring your phone back from the dead.
Edit: after you have your phone up and running, download goo manager and install cwm recovery since your phone is pre rooted already.

buhohitr said:
OK, download this image and flash with Odin(you should be using Odin version 3.07) http://goo.im/devs/invisiblek/i535/stock.vzw_root66.tar This should bring your phone back from the dead.
Edit: after you have your phone up and running, download goo manager and install cwm recovery since your phone is pre rooted already.
Click to expand...
Click to collapse
Ok, that looks like some version of the stock vzw ROM with root already installed?
This is what ThePagel seemed to recommend as well before I ended up with more questions about what was going on before I did it.
What part of Odin do I flash to? PDA again, just like a custom recovery?

​
corrosivefrost said:
Ok, that looks like some version of the stock vzw ROM with root already installed?
This is what ThePagel seemed to recommend as well before I ended up with more questions about what was going on before I did it.
What part of Odin do I flash to? PDA again, just like a custom recovery?
Click to expand...
Click to collapse
Yes, it's pre rooted stock image and yes flash with PDA.

buhohitr said:
​
Yes, it's pre rooted stock image and yes flash with PDA.
Click to expand...
Click to collapse
Standard auto-reboot and f_reset_time options? nothing else necessary?

corrosivefrost said:
Standard auto-reboot and f_reset_time options? nothing else necessary?
Click to expand...
Click to collapse
Correct. When you click on PDA and select the image, give it time to showup in Odin cause the size is big.

buhohitr said:
Correct. When you click on PDA and select the image, give it time to showup in Odin cause the size is big.
Click to expand...
Click to collapse
Alright, I'll give it a shot and report back.
Thank you!

corrosivefrost said:
Alright, I'll give it a shot and report back.
Thank you!
Click to expand...
Click to collapse
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.

ThePagel said:
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
Click to expand...
Click to collapse
Yes if the bootloader is still locked he needs boot chain can be found here http://forum.xda-developers.com/showthread.php?t=2046439

ThePagel said:
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
Click to expand...
Click to collapse
It did work! Hooray!
buhohitr said:
Yes if the bootloader is still locked he needs boot chain can be found here http://forum.xda-developers.com/showthread.php?t=2046439
Click to expand...
Click to collapse
Didn't need to go that far -- but now that I'm back up and running, signed into google play, and downloaded goo manager, can you point me in the right direction for getting it to install cwm recovery?
Thanks guys!

Need Help With Bricked Note 5

Tried to root my Note 5 using Zedomax's method for 6.0.1 and I think something went wrong. My phone ran through the Odin flashing process and passed, but on reboot I was left with red letter saying "recovery is seandroid enforcing" or something to that effect along with a boot loop. I was unable to boot into TWRP. I can still get the phone in download mode, but it seems like every firmware/recovery I try to flash leaves me in the same predicament or it freezes odin before I can flash it. My note 5 is a 920p Sprint model and on 6.0.1. Any help is appreciated. Thanks.

timsmooth said:
Tried to root my Note 5 using Zedomax's method for 6.0.1 and I think something went wrong. My phone ran through the Odin flashing process and passed, but on reboot I was left with red letter saying "recovery is seandroid enforcing" or something to that effect along with a boot loop. I was unable to boot into TWRP. I can still get the phone in download mode, but it seems like every firmware/recovery I try to flash leaves me in the same predicament or it freezes odin before I can flash it. My note 5 is a 920p Sprint model and on 6.0.1. Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Uncheck auto reboot in Odin and Odin twrp.
Reboot straight from download mode into twrp and flash either smoar rom or the deodexed rom by tdunham. Did you make sure you oem lock is off ?
Sent from my SM-N920P using Tapatalk

djxn40 said:
Uncheck auto reboot in Odin and Odin twrp.
Reboot straight from download mode into twrp and flash either smoar rom or the deodexed rom by tdunham. Did you make sure you oem lock is off ?
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I already helped him get back to stock so he's at least up and running.

timsmooth said:
Tried to root my Note 5 using Zedomax's method for 6.0.1 and I think something went wrong. My phone ran through the Odin flashing process and passed, but on reboot I was left with red letter saying "recovery is seandroid enforcing" or something to that effect along with a boot loop. I was unable to boot into TWRP. I can still get the phone in download mode, but it seems like every firmware/recovery I try to flash leaves me in the same predicament or it freezes odin before I can flash it. My note 5 is a 920p Sprint model and on 6.0.1. Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Use the twrp 3.0.2.0 tar.tar found via @tdunham moar for mm threads note 5 recoveries link. I had same issue until using it.

This thread can be closed. Mrmike2182 helped me fix my issue in another thread.

Please help me!
MrMike2182 said:
I already helped him get back to stock so he's at least up and running.
Click to expand...
Click to collapse
I have the same exact problem with my phone. Same model and everything. I can make it to Odin mode but when I try and boot the phone I'm stuck on the boot screen with kernel is not seandroid enforcing in red.

N_MBU said:
I have the same exact problem with my phone. Same model and everything. I can make it to Odin mode but when I try and boot the phone I'm stuck on the boot screen with kernel is not seandroid enforcing in red.
Click to expand...
Click to collapse
Download one of these for your phone. .
http://www.sammobile.com/firmwares/database/SM-N920P/
Make sure you uncheck auto reboot in Odin and as soon as it's done and says success disconnect the phone and immediately press and hold the volume down button and the power button at the same time and when the screen comes back up you HAVE to select factory reset wipe if you don't you'll be stuck again just let the little android dude install the update and then the phone will reboot and you'll be ok.
Unzip the md5 you get from the sammobile site and flash only the .tar
This is what he told me that got my phone up and working again. Be warned it is the nuclear option. All of your data will be lost upon recovery good luck.

I hate bringing old posts back to life....But I'm stuck in a series of boot loops that I can't get out of.
I was rooted on MM, decided to go back to stock for a Gallery error I was having.
Downloaded the PD2 from Sammobile, Odin'd it, appears successful.
Reboot
I get to the stock ROM setup screens and the boot loop occurs. I can't complete setup.
I've tried unticking the reboot in Odin and going directly into system recovery...then I do a Factory reset which appears successful.\\Reboot phone, back into the stock ROM Welcome screen....start the setup, and usually after adding WiFi or during Activation reboot.
Any help??

hotspace said:
I hate bringing old posts back to life....But I'm stuck in a series of boot loops that I can't get out of.
I was rooted on MM, decided to go back to stock for a Gallery error I was having.
Downloaded the PD2 from Sammobile, Odin'd it, appears successful.
Reboot
I get to the stock ROM setup screens and the boot loop occurs. I can't complete setup.
I've tried unticking the reboot in Odin and going directly into system recovery...then I do a Factory reset which appears successful.\\Reboot phone, back into the stock ROM Welcome screen....start the setup, and usually after adding WiFi or during Activation reboot.
Any help??
Click to expand...
Click to collapse
It's extremely common and has one simple solution. Let the battery completely die and then charge it up a little and you won't loop anymore

Thanks for the reply. Earlier today I visited my local Sprint store and gave them a crack at it. After about 30 minutes in the store, the tech suggested I leave with it them and they were going to completely wipe it and load the stock image.
After about an hour I went back to the store and he gave me the bad news that he was unable to get it out of the boot loop as well. They've ordered me a new device.
I really trust what you say about letting the phone battery die...but I fear that would fix it and I'd be out a new replacement device.

954wrecker said:
It's extremely common and has one simple solution. Let the battery completely die and then charge it up a little and you won't loop anymore
Click to expand...
Click to collapse
Dude!! It worked. I put the phone in download mode and just let it sit until it died.
Booted it back up and it went straight into hands free activation. And no reboots.
Why does this work?

Trying to unroot Samsung Galaxy S7 manually with Odin

Everytime I try to unroot my phone with Odin it says the process failed and Auth failed, someone please help..

Download stock firmware from the primary root guide. Use Odin and select all three the ap and the two below it. This will recover you to stock. Without root. But first do a titanium backup or a nandroid backup of all your apps and contact.
Sent from my SM-G930V using XDA-Developers mobile app

I tried but it still says failed... in Odin I put in all BL AP CP and CSC files, in the left text box it says FAIL! (Auth). I've tried this multiple times but it failed.. am I doing something wrong? Will I not be able to unroot my phone.. it's a SM-930T

Antaru123 said:
I tried but it still says failed... in Odin I put in all BL AP CP and CSC files, in the left text box it says FAIL! (Auth). I've tried this multiple times but it failed.. am I doing something wrong? Will I not be able to unroot my phone.. it's a SM-930T
Click to expand...
Click to collapse
Have you tried going into super su and hitting on permanent unroot also heres a guide goto the bottom and there should be a part that says full unroot. Link: http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039 goto page 1 wont goto page 1 even after editing it oh well. Lol

I've done that too and it says FAILED then the SuperSU app disappears from my phone

Antaru123 said:
I've done that too and it says FAILED then the SuperSU app disappears from my phone
Click to expand...
Click to collapse
Try rerooting the phone through ODIN also make sure you are using the lastest ODIN if you need to boot into recovery and do factory reset and cleat cache but BACK YOU STUFF UP!!! Also what is you model number ex: SM-G935x
Edit also make sure u have secure start up off and have you lockscreen password off just in case

Well uh. now my phone is stuck in recovery mode and won't even start up normally.. and it's the SM-G930T

Antaru123 said:
Well uh. now my phone is stuck in recovery mode and won't even start up normally.. and it's the SM-G930T
Click to expand...
Click to collapse
Hate to say this again but just to make sure did you try doing factory reset and clear cache. Also if its still stuck then use odin to flash the s7 engineer root file then go into recovery mode and then clear cache and factory reset it should work fixed my boot loop when my phone was doing it.

I did all this Odin still fails, I've tried all three downloads from XDA for SM-930T which is my phone

Antaru123 said:
I did all this Odin still fails, I've tried all three downloads from XDA for SM-930T which is my phone
Click to expand...
Click to collapse
Well if worst come to it goto best buy and goto the samsung depart ment and belike my phone is stuck in a boot loop and they told me to have you guys reflash it. Thats what i did when my recovery was messed up and had a boot loop. Just tell them that the only thing that works is download mode or if they boot into recovery mode be like the factory reset doesnt do any thing. But i would say do this if its and absolute last option. I would say look around the fourms and mess around with it a bit more and ill do the same since you already tried petty much every thing.

Trying to unroot
Same issue here with 930T. Had rooted and was unsatisfied but I tried flashing TWRP and now I can't even boot into recovery, goes straight into home screen. Now I can't unroot after trying ODIN, SuperSU, Samsung Switch etc. Would love some help.

Make sure you actually try each one of these steps - I actually tried all these steps, and the last step worked for me. Took me 5-6 hours to unroot my phone. I use a Samsung S7 (SM-G930W8).
1. USB Cable matters. Try a different USB cable (best if it is the OEM one, if not one that gives enough power)
2. Plug into a USB 2.0 instead of a USB 3.0
3. Uninstall Kies
4. Re-install your Samsung USB drivers
5. Use a different computer
6. Use a older version of Odin (3.10 did not work for me, when I changed to 3.9 it worked)

Why not just initialize using smart switch.

So I would suggest going to this post here and downloading the ODIN 3.12
http://forum.xda-developers.com/showthread.php?t=2711451
I was trying to unroot for a clean root and this one worked for me the one made by PrinceComsy did not work for the flashing the stock ROM but it did work for flashing the ENG Boot ROM. I used 3 out of the 4 file to flash the stock rom I didn't select the BL file at all but you can if you want.
If you need any further assistance/help please reply to this and I will try to assist you further.

bfixer117 said:
So I would suggest going to this post here and downloading the ODIN 3.12
http://forum.xda-developers.com/showthread.php?t=2711451
I was trying to unroot for a clean root and this one worked for me the one made by PrinceComsy did not work for the flashing the stock ROM but it did work for flashing the ENG Boot ROM. I used 3 out of the 4 file to flash the stock rom I didn't select the BL file at all but you can if you want.
If you need any further assistance/help please reply to this and I will try to assist you further.
Click to expand...
Click to collapse
Could the issue be the stock firmware? I tried to get mine from GalaxyS7R.. and not trying from SamMobi...
I receive the same errors on PC and on device I am receiving SW REV CHECK FAIL: [about]Fused 3> Binary 2
[1] eWWC write fail: aboot
I am able to boot back into my phone but simply cannot restore back to original stock.

spaz2045 said:
Could the issue be the stock firmware? I tried to get mine from GalaxyS7R.. and not trying from SamMobi...
I receive the same errors on PC and on device I am receiving SW REV CHECK FAIL: [about]Fused 3> Binary 2
[1] eWWC write fail: aboot
I am able to boot back into my phone but simply cannot restore back to original stock.
Click to expand...
Click to collapse
Figured this out myself..need to use the correct build (there are 4 or 5 for TMO)...