Database Info

[Q] 4g reboots in download mode unless connected to power.

I bought a second hand galaxy s 4g that had a problem. When the phone gets rebooted, such as a battery change, it only restarts in download mode. I tried flashing a new rom in odin hoping it would set right whatever is wrong in there but no good. When the phone is connected to a power source it restarts normally. I know there is a fix for this but I can't find it. Seems most people can't get into download mode but I can't get out! Thanks in advance for whoever can help. How can I fix this?

robthorn2010 said:
I bought a second hand galaxy s 4g that had a problem. When the phone gets rebooted, such as a battery change, it only restarts in download mode. I tried flashing a new rom in odin hoping it would set right whatever is wrong in there but no good. When the phone is connected to a power source it restarts normally. I know there is a fix for this but I can't find it. Seems most people can't get into download mode but I can't get out! Thanks in advance for whoever can help. How can I fix this?
Click to expand...
Click to collapse
Interesting problem. What ROM is it currently running? Have you tried a factory reset, cache wipe, etc?

I did. I just got it yesterday and immediately did a cache wipe and reinstall packages. It has froyo.vuvkb5 kernel 2.6.32.9. I installed the krylon360 stock+rom via odin with no change. I was going to try flashing a team whiskey rom onto it when I have time but wanted to check if this had been a problem for anyone else. I found one post somewhere that may point to a missing .dll but everything is fine when its plugged into power. I am lost.

robthorn2010 said:
I did. I just got it yesterday and immediately did a cache wipe and reinstall packages. It has froyo.vuvkb5 kernel 2.6.32.9. I installed the krylon360 stock+rom via odin with no change. I was going to try flashing a team whiskey rom onto it when I have time but wanted to check if this had been a problem for anyone else. I found one post somewhere that may point to a missing .dll but everything is fine when its plugged into power. I am lost.
Click to expand...
Click to collapse
The phone runs on Android which does not utilize .dlls (dynamic link libraries; that's a Windows thing). KB5 is an old ROM. If you're trying to stay on Froyo right now, why not flash KD1 (http://forum.xda-developers.com/showthread.php?t=1063696), then do a factory data reset. See if that helps. If you plan on going to Gingerbread then we need to insure you flash a ROM with the correct boot loaders else you could get into the "rainbow screen", soft brick, bootloop, or something of the sort.

I am definitely going to upgrade the phone. I found another thread that had a problem that I also have but didn't mention the download mode problem. When I try to reinstall package I get the same message as this thread
http://forum.xda-developers.com/showthread.php?t=800614
It ends with this message
_Install from sdcard....
Finding update package...
Opening update package...
Verifying update package...
E:failed to open/mnt/internal_sd/update.zip (No such file or directory)
I'm guessing the original owner of the phone boned something up and gave up on fixing it. I'm just getting back into android after a year trying to like the windows phone which is now my nemesis. I don't remember many of the lessons I learned from my Vibrant so any help getting this guy here on point would be much appreciated.

robthorn2010 said:
I am definitely going to upgrade the phone. I found another thread that had a problem that I also have but didn't mention the download mode problem. When I try to reinstall package I get the same message as this thread
http://forum.xda-developers.com/showthread.php?t=800614
It ends with this message
_Install from sdcard....
Finding update package...
Opening update package...
Verifying update package...
E:failed to open/mnt/internal_sd/update.zip (No such file or directory)
I'm guessing the original owner of the phone boned something up and gave up on fixing it. I'm just getting back into android after a year trying to like the windows phone which is now my nemesis. I don't remember many of the lessons I learned from my Vibrant so any help getting this guy here on point would be much appreciated.
Click to expand...
Click to collapse
Yeah, I don't recall that mount point on my phone. I think /sdcard is mounted to /mnt/sdcard. Did you try flashing the KD1 ROM I listed above? You'd have to do it from ODIN.
If you want to get on the latest, RaverX3X did a great favor to many and created an ODIN version of the latest release from Samsung (KJ6). It's found here: http://forum.xda-developers.com/showthread.php?t=1353176

I just finished downloading the above file and will flash as soon as i get home. Thanks for all the help. I'm most def going to use the raver file.

robthorn2010 said:
I just finished downloading the above file and will flash as soon as i get home. Thanks for all the help. I'm most def going to use the raver file.
Click to expand...
Click to collapse
Good luck. Let me know how it goes.

No change. I tried both roms and same result except for gingerbread being much faster. I am not rooted right now so I suppose I will try rooting and looking around my folders for anomolies? Could this be a hardware problem?

robthorn2010 said:
No change. I tried both roms and same result except for gingerbread being much faster. I am not rooted right now so I suppose I will try rooting and looking around my folders for anomolies? Could this be a hardware problem?
Click to expand...
Click to collapse
Hard to say, though it seems odd that it reboots fine when plugged in. Aside from rooting & poking around maybe try installing chadster's KG4 ROM (http://forum.xda-developers.com/showthread.php?t=1183413). Instead of just the PDA file, it has the partition information file (.pit), the PDA, CSC, & phone files. I wonder if flashing that might help? If you try it, just:
Put CODE_T959VUVKG4_CL1385158_REV00_user_low_noship.ta r.md5 in PDA
Put Hawk_Sidekick_VibrantPlus_831.pit in PIT
Put SGH-T959V-CSC-TMB-VIBRANTP.tar.md5 in CSC
Put T959VUVKG4-Phone-CL1037720.tar.md5 in PHONE
Let ODIN decide what needs to be checked & flash.
That backs you off of the latest version of GB, but if it works, you can reflash the KJ6 version afterward.

That sounds like a step in the right direction. I get the feeling something was missing in the phone file wise and needed a full redo to the most deep level. I have to wait til I get home to try. I am very anxious.

robthorn2010 said:
That sounds like a step in the right direction. I get the feeling something was missing in the phone file wise and needed a full redo to the most deep level. I have to wait til I get home to try. I am very anxious.
Click to expand...
Click to collapse
I totally understand. I hope this works!

Nothing. Same result. Also now the gps has stopped working.

robthorn2010 said:
Nothing. Same result. Also now the gps has stopped working.
Click to expand...
Click to collapse
Dang, we made it worse. Sorry about that. I'd definitely push KJ6 back onto it and factory data reset.
I'm wondering whether it would be worth a shot to flash one of drhonk's kernels (http://forum.xda-developers.com/showthread.php?t=1194032) on it with CWM/Root/and voodoo. That way you can go into CWM recovery, wipe the cache, davlik cache, and fix the permissions.
IF you want to try it and see what happens before, download drhonk's KG4 kernel, put it in the PDA section of ODIN, and flash it. If you flash KJ6 first, you can ODIN his KJ1 ROM.
After doing it, boot the phone into recovery mode (you might have to use an app like quick boot), go to advanced, and fix permissions.

Op, you seem to be getting a lot of great help from Stephen, but did you get this working? if not follow the gb guide to flash both sets of bootloaders. wipe you're sd card. Now go back and return to froyo kd1 and use the official upgrade through kies. If that doesn't fix it, you have a hardware problem. After the upgrade to kj6 official, take it to a store and say it started happening once you upgraded
Sent from my T959 using xda premium

My GT7Plus bricked itself again... Help! *** Edit: Fixed!!! See page 6 for details!!

So, this happened recently, and I fixed it. Link: http://forum.xda-developers.com/showthread.php?t=1735119
Well, outta no where, same basic issue, but with a twist.
This afternoon while I was asleep my GTab rebooted. It came back to the "Samsung Galaxy Tab 7.0 Plus" splash screen and is stuck. I *can* get into download mode, and I can almost get into recovery. When I try to go into recovery, it loads what looks like it will be recovery, then says:
# Manual Mode #
-- Updating Application
Then a minute or so later it reboots right back to the GT7+ splash screen and stays there...
Twist:
So, knowing what I did last time, I installed Odin and the Samsung drivers on my POS computer at home, booted into Download Mode, and did the "PDA" option with the correct FW (same as I used last time for the T869 from SamMobile, I saved all the files). It runs through just fine, gets to the end and the Tab reboots. It then goes into recovery and and does a few things (I believe it said it was deleting the cache and a few other processes). Then, lastly, it again says:
"# Manual Mode #
-- Updating Application
... followed by a reboot, and back to hanging on the boot logo.
Any ideas?!? Ironically, I put it on CL today to see if I can sell it for enough to cover a Nexus7. I woke up to an offer, and a bricked Tab. Figures.
Any thoughts/help are greatly appreciated. The sooner the better. lol

Is it possible that I need to flash a good recovery in Odin? If so, what's the procedure. and can someone link me to the one I would need for the US TMobile 4G version of the GT7+?

Also, since flashing the stock FW isn't fixing anything, and it seems like a possible Recovery issue, a friend at work is suggesting I choose the option in Odin to delete the partitions.
Thoughts??? (quickly)

Damn dude, again?
I think there is 3 or 4 threads about this on this forum and same amount on 7.7 forum. None come to a cause our solution, seems like people repeats some procedures and out of nothing it works again.
When it happened to me a let its battery drain fully to the point it won't turn on anymore let it this way for some time. Then fully charged, this is a little harmful to your bat, for the record. Then try to turn on, it will take some time but eventually it could enter on the system.
I think the data partition got corrupted.
Sent from my GT-P6210 using Tapatalk 2

Yup.
So, I tried the option in Odin to re0make the partition, and every time I try it fails with an error of "Can't Open Package" (or something along those lines).
I have reinstalled the FW through Odin no less than 10 times, nogo. The first time I open recovery after flashing, It says it is installing a package, clearing cache, etc, and the last line always says "-- Updating Application". After 10-15 seconds, that goes away and it reboots only to hang on the GT7Plus splash screen again. Then, any time I go into recovery after that first post-Odin instance, if says:
"# Manual Mode #
-- Updating Application
Should I be trying to reinstall Recovery? If so, what do I use (link)? Also, how do I do that in Odin...

I believe that for use remake partition you have to provide the pit file if your stock does not have it.
Anyway I did that also about 3 times, providing the pit and the md5, they flashed ok, but the problem was the same. Did you tried the battery thing? Some guy give a tip to start with the usb plugged.
Sent from my MB525 using Tapatalk 2

leodfs said:
I believe that for use remake partition you have to provide the pit file if your stock does not have it.
Anyway I did that also about 3 times, providing the pit and the md5, they flashed ok, but the problem was the same. Did you tried the battery thing? Some guy give a tip to start with the usb plugged.
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
Where was that tip? Link?
Also, any one have that .pit file I can try with?

http://forum.xda-developers.com/showthread.php?p=28574760
Sent from my MB525 using Tapatalk 2

Hey buddy..
Which fw u using? T869 came shipped with 2 different, search for both of them and try each one...don't use repartition without the correct pit file...
Maybe not here but I google sgh-t869 factory and found a website with both tar
Sent from my Galaxy Nexus using xda app-developers app

statuzz said:
Hey buddy..
Which fw u using? T869 came shipped with 2 different, search for both of them and try each one...don't use repartition without the correct pit file...
Maybe not here but I google sgh-t869 factory and found a website with both tar
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm not sure which file it is that I'm using, I'll have to look at home in a couple of hours. This happened to me a few weeks ago (link in original post), and I flashed this FW with Odin and it recovered, and has been fine since (till now), so I know it's at least a usable FW. I'll try to find the other one today.
I just tried finding the stock pit file for the TMo SGH-T869, but I can't find it. Anyone have a link to it by chance? Also, once I get it, what do I do (options to choose) in Odin to flash it?... and do I do it at the same time as the FW?
Thanks for any help! I was really hoping to sell it in the next day or two to fund the Nexus7, so now I'm really frustrated.
ETA: Also, I let it completely die, to the point it wouldn't boot. Then charged it for a bit and booted. Same issue.

I think that if u find the pit file they should be flash at the same time...fw in pda and pit in phone...(this need to be check to confirm) after flashing.. reboot into factory recovery wipe everything and try to boot
Hopefully u fix that today
Sent from my Galaxy Nexus

When it happened to me, i flashed the pit first and at the same with stock with re partition checked, didnt help. I did everything that I could find and I feel like it only worked again by itself
You can look every single thread of this exact problem, the ones that got it back working can't really say how, they flash everything many times and it suddenly works.
The good things are that flash the stock ones don't increase you flash count, and as long as you can enter download mode you are not really s#%
Sent from my MB525 using Tapatalk 2

Thanks for the help...
Anyone have a link to the .pit for this model (T869)?
Also, I had a thought. When I go into Recovery, I get the following and then it reboots again:
# Manual Mode #
-- Updating Application
1. Is it possible that recovery is hosed, and overwriting it with a fresh version will allow me to wipe the device, set to factory and then boot? Maybe this is the issue?
2. Is it even possible to just flash a fresh copy of the recovery over whatever is there (or replace it)?
2.a. If it is possible, what file should I use, and do I do it though Odin? Anyone have a link to what I should use?
Thanks :good:

VisualOddity said:
Thanks for the help...
Anyone have a link to the .pit for this model (T869)?
Also, I had a thought. When I go into Recovery, I get the following and then it reboots again:
# Manual Mode #
-- Updating Application
1. Is it possible that recovery is hosed, and overwriting it with a fresh version will allow me to wipe the device, set to factory and then boot? Maybe this is the issue?
2. Is it even possible to just flash a fresh copy of the recovery over whatever is there (or replace it)?
2.a. If it is possible, what file should I use, and do I do it though Odin? Anyone have a link to what I should use?
Thanks :good:
Click to expand...
Click to collapse
The problem is that there's is not development for t869 so there's not much to look for...just factory images and root method
Sent from my Galaxy Nexus

Can anyone link me to the proper pit file? Also, in the linked thread a few posts back, there are a couple of files, will those work for this?
Can someone post the proper pit file for me so I can repartition? I'm doing this on my wife's phone because my internet at home is down till tomorrow...
Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad?

VisualOddity said:
Can anyone link me to the proper pit file? Also, in the linked thread a few posts back, there are a couple of files, will those work for this?
Can someone post the proper pit file for me so I can repartition? I'm doing this on my wife's phone because my internet at home is down till tomorrow...
Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad?
Click to expand...
Click to collapse
i think u should forget about the pit file, couz the firmware have the pit repackage with the tar, im gussing u will only need the pit file in case u want to change the phone partitions, try to get those 2 fw and try them :good:

That's why I'd like the pit file, so I can check the option in Odin to re-partition.
So, I have internet at home now. I have now tried again letting it completely die, then completely charge, same issue. I have also tried 2 different versions of the SGH-T869 firmware.
Any thoughts?
Also, given what I have done so far, I posted this yesterday, any thoughts?
"Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad? "

Yes. Unplug is bad. Possibly fatal. you should be able to.find a stock recovery.img in a stock Odin.tar, flash it with heimdall. Recommend factory reset beforeand after doing so.
I dont know about tmobile tabs but international ones look to apply CSC files after displaying that manual mode message. Perhaps something has gone awry with a CSC,etc.

chrisrotolo said:
Yes. Unplug is bad. Possibly fatal. you should be able to.find a stock recovery.img in a stock Odin.tar, flash it with heimdall. Recommend factory reset beforeand after doing so.
I dont know about tmobile tabs but international ones look to apply CSC files after displaying that manual mode message. Perhaps something has gone awry with a CSC,etc.
Click to expand...
Click to collapse
Thank You. A few questions:
Would that stock recovery.img have to be model specific. i.e. for the SGH-T869, or could it be from any GT 7 Plus (or is it generic on all devices with HoneyComb)? I *think* from experience it has to be T869 specific, but it's worth asking.
Also, about Heimdall, where do I get that, and how do I use it to flash? I've heard of it, but never used it.
Lastly, about the CSC files. That makes sense seeing as what it's doing, so that *could* be the whole issue. How can I overcome that? Can I download and flash those files somehow? Do you have a link to them?
Thanks for the help everyone. I'm hoping that in doing all this, maybe whatever ends up fixing this will be a guide for everyone else having the issue...

OK, I saw a couple of you guys mention the 7.7 people having this issue, so I went there to research. If I am reading right, it *sounds* like this could be a solid mix of a data system being corrupted, and the stock recovery (Samsung e3?) being bad.
Someone mentioned that you can pull the stock recovery.img from a the firmware, make a .tar with only that, then flash that. Once that's done you can do a full wipe in recovery, flash the full FW, and hopefully be back in business.
I want to try this, and if it works, maybe we will have a proven solution for the people getting this issue. However, not only have I never created a .tar, I have especially never created a flashable .tar, so...
What do I do? Other than pulling the recovery.img from the FW, how do I do this?

PLEASE HELP Nand Erase all, boot loop

My Note Edge N915F volume down stopped working
i wanted to know if it's software so i went to safe mode, but nothing brought it out of safe mode.
so i flashed the latest Firmware but i realized the (( Nand Erase all )) option was on, ( laptop is touch screen )
now the phone is in boot loop. i reflashed the firmware but nothing.
i can't go to Recovery mode because volume doesn't work but i can only go to download mode with on OTG device i bought before.
is there anything i can do to fix it?

anyone can help? i have a dead expensive phone on my hand now.

omid_freesky said:
anyone can help? i have a dead expensive phone on my hand now.
Click to expand...
Click to collapse
try to flash custom recovery, if any available there... wipe data and cache, then you need to install stock rom. so download stock rom for your country first.
Maybe it helps.

omid_freesky said:
anyone can help? i have a dead expensive phone on my hand now.
Click to expand...
Click to collapse
You may need to take back to Samsung...
No-one wants to give advice that can get you deeper into trouble than you already are...
Let this be a lesson, before you hit "start" make sure nothing but reset and f-reset time is ticked... All else can cause serious problems... Hopefully won't be an expensive lesson...

opethianskies said:
try to flash custom recovery, if any available there... wipe data and cache, then you need to install stock rom. so download stock rom for your country first.
Maybe it helps.
Click to expand...
Click to collapse
here is the problem, i can't go to recovery because volume down didn't work, and this is why i end up flashing firmware.
i want to know if there is another way to go to recovery .

ultramag69 said:
You may need to take back to Samsung...
No-one wants to give advice that can get you deeper into trouble than you already are...
Let this be a lesson, before you hit "start" make sure nothing but reset and f-reset time is ticked... All else can cause serious problems... Hopefully won't be an expensive lesson...
Click to expand...
Click to collapse
i can take any advice at this point. i can't take it to samsung because i might be the only one who owns this phone here. the local service said they can do nothing.
i've flashed a million times and this is the first time this happened to me. and Yes it is an expensive lesson, $1,200 expensive

omid_freesky said:
here is the problem, i can't go to recovery because volume down didn't work, and this is why i end up flashing firmware.
i want to know if there is another way to go to recovery .
Click to expand...
Click to collapse
you don't have to go into the recovery, you need to go download mode and flash custom recovery there...
feel sorry for you, custom roms or the roms that are not verified by samsung, are risky as hell. I flashed my Note II million times, but now i'm not interfering with my Note Edge.
may be you had better bring your phone to an authorized service. this doesn't seem to be a software problem.

opethianskies said:
you don't have to go into the recovery, you need to go download mode and flash custom recovery there...
feel sorry for you, custom roms or the roms that are not verified by samsung, are risky as hell. I flashed my Note II million times, but now i'm not interfering with my Note Edge.
may be you had better bring your phone to an authorized service. this doesn't seem to be a software problem.
Click to expand...
Click to collapse
i flashed the custom recovery, nothing changed.
unfortunately we don't have authorized service here.

omid_freesky said:
i flashed the custom recovery, nothing changed.
unfortunately we don't have authorized service here.
Click to expand...
Click to collapse
Have you tried to flash stock rom for your country. Go sammobile and find your stock rom for your country, at least you can open your phone again.

opethianskies said:
Have you tried to flash stock rom for your country. Go sammobile and find your stock rom for your country, at least you can open your phone again.
Click to expand...
Click to collapse
it is the first thing i did, i flashed stock Firmware when the Nand Erase all was accidentally on, and i flashed it again (without Nand) but it didn't fix.

Possibly your phone has gone into bootloop. Release the battery for one minute. Then plug the battery again, Try to flash Rom with an higher Odin version...
However I found a solution in XDA
Quote:
Originally Posted by samersh72 View Post
before flashing param.tar. go into recovery, if it is possible, wipe data and cache, then flash with odin the stock firmware in pda with the pit file in pit window. just check auto reboot, f.reset and re-partition. when it say "pass" remove battery, re-insert it, go to recovery, wipe data and cache reboot.
if it didnt work, unzip attached file and flash "param_I9505.tar" in pda. (without pit file)(dont tick re-partition)
im afraid that ticking "nand erase all" in odin, usually lead to a hard brick!
Duuude! It worked!!!!
Even without flashing param partition. Just the first step:
Quote:
go into recovery (I flashed CWM with Odin), if it is possible, wipe data and cache, then flash with odin the stock firmware in pda with the pit file in pit window. just check auto reboot, f.reset and re-partition. (then it went into bootloop as usual and after a moment Odin said "pass") when it say "pass" remove battery, re-insert it, go to recovery (the recovery at that moment returned to stock), wipe data and cache reboot.
And ta-daaa! It works now. Ahhh! that was close! )))
You should write this instruction for [email protected] like me.
You can't imagine how I'm grateful to you!

opethianskies said:
if it didnt work, unzip attached file and flash "param_I9505.tar" in pda. (without pit file)(dont tick re-partition)
Click to expand...
Click to collapse
The param_I9505.tar this refers to is for the Note 4(international). Are you REALLY sure this won't cause more problems? It's hard enough to fix something when you don't know what's wrong but adding another ingredient into the mix can REALLY make the brown stuff hit the whirlygig...
Also, Op shouldn't have flashed custom recovery, you need to send back to Samsung... Its possible you may have triggered the Knox warranty void. You may have to pay $$$ now to get it fixed....
Fooling around more will make sure you have a $1200 paperweight...

ultramag69 said:
The param_I9505.tar this refers to is for the Note 4(international). Are you REALLY sure this won't cause more problems? It's hard enough to fix something when you don't know what's wrong but adding another ingredient into the mix can REALLY make the brown stuff hit the whirlygig...
Also, Op shouldn't have flashed custom recovery, you need to send back to Samsung... Its possible you may have triggered the Knox warranty void. You may have to pay $$$ now to get it fixed....
Fooling around more will make sure you have a $1200 paperweight...
Click to expand...
Click to collapse
yeah it's solution for note 4 but i assumed that he already knew that... OP must have flashed proper file for his phone... I'M not referring Note 4 here.

My phone refuses to go back to stock, it only works if I stay rooted, please help....

Okay, so I'm having this problem where my phone get stucks in a bootloop when I flash back to stock.
The only way it gets out of bootloop, is if I install root. The problem is I'm trying to go back to stock firmware for now, but my phone refuses to get out of the Samsung logo every single time I try and run stock.
My guess is it might have something to do with the partition.
I notice when I'm doing a factory reset/wipe.
It has consistently said how it can't mount, and I'm guessing something is wrong with my partition, because I got the right firmware for my phone. It's N-902T.
If anyone has advice on this, I'd greatly appreciate it. Right now, I have no choice but to run a rooted phone until I figure out a way to get back to stock.

Ive never seen this before

[email protected] said:
Ive never seen this before
Click to expand...
Click to collapse
Yeah, I've never seen this before either. But I've tried multiple times to simply factory reset/wipe and flash stock.
It simply stays on the Samsung logo every single time. Correct firmware and everything... I even tried smart switch and it didn't help either...

Staying rooted is the best thing you can do did you flash the wrong firmware
Sent from my SM-N920T using Tapatalk

Anthony092 said:
Yeah, I've never seen this before either. But I've tried multiple times to simply factory reset/wipe and flash stock.
It simply stays on the Samsung logo every single time. Correct firmware and everything... I even tried smart switch and it didn't help either...
Click to expand...
Click to collapse
Do this:
Backup your stuff you need first!!!
Flash root
Flash TWRP
FULL WIPE!!! EVERYTHING. Every single partition that shows, cache, internal, system, data...everything. Do it x3.
ODIN stock firmware

Jammol said:
Do this:
Backup your stuff you need first!!!
Flash root
Flash TWRP
FULL WIPE!!! EVERYTHING. Every single partition that shows, cache, internal, system, data...everything. Do it x3.
ODIN stock firmware
Click to expand...
Click to collapse
I'll try and do it and let you know how it goes.

Anthony092 said:
I'll try and do it and let you know how it goes.
Click to expand...
Click to collapse
@Jammol is correct. This method should work. Going back to stock after being rooted almost always requires a full factory reset for our device. I had to do it on my phone.

Jammol said:
Do this:
Backup your stuff you need first!!!
Flash root
Flash TWRP
FULL WIPE!!! EVERYTHING. Every single partition that shows, cache, internal, system, data...everything. Do it x3.
ODIN stock firmware
Click to expand...
Click to collapse
Akw6190 said:
@Jammol is correct. This method should work. Going back to stock after being rooted almost always requires a full factory reset for our device. I had to do it on my phone.
Click to expand...
Click to collapse
I did it, didn't work for me. Still stuck at the Samsung logo, wiped everything too..

Just to add, a few more things I did notice.
After I flashed, My System Binary is listed as Samsung Official, but the System Status is still listed as Custom, this is after I flash Stock.
Then When I go back into Recovery, to another wipe just in case after flashing, it keeps saying.
DM-Verification failed......
Need to check DRK fist...
Also says E:failed to mount/preload (No such file or directory)

Anthony092 said:
I did it, didn't work for me. Still stuck at the Samsung logo, wiped everything too..
Click to expand...
Click to collapse
Alright, try this method:
Flash latest stock firmware in ODIN
Once it's done flashing, reboot to stock recovery
do a factory reset from stock recovery
It should boot after that. This is the method I used.
---------- Post added at 10:39 PM ---------- Previous post was at 10:35 PM ----------
Anthony092 said:
Just to add, a few more things I did notice.
After I flashed, My System Binary is listed as Samsung Official, but the System Status is still listed as Custom, this is after I flash Stock.
Then When I go back into Recovery, to another wipe just in case after flashing, it keeps saying.
DM-Verification failed......
Need to check DRK fist...
Also says E:failed to mount/preload (No such file or directory)
Click to expand...
Click to collapse
In this case, use the method I posted above, but try re-downloading the latest firmware for your device from sammobile.com and flash that. It should overwrite all of your partitions and then simply require a factory reset from stock recovery to boot. If that doesn't work, you may need to flash the PIT file for your device, which I'm sure can be found somewhere around here. I'm not sure the exact method to do that, however.

Akw6190 said:
Alright, try this method:
Flash latest stock firmware in ODIN
Once it's done flashing, reboot to stock recovery
do a factory reset from stock recovery
It should boot after that. This is the method I used.
Click to expand...
Click to collapse
I tried already, didn't work, but I'll keep looking to see if I can fix it. The minute I Put root back on my phone, it immediately started working, however every single time I try to go back to stock, it never gets past the Samsung Logo, No matter how many times I do a wipe. Plus, I don't understand why it keeps showing my device as custom, but the binary as samsung official, after I'm flashing stock...

Anthony092 said:
I tried already, didn't work, but I'll keep looking to see if I can fix it. The minute I Put root back on my phone, it immediately started working, however every single time I try to go back to stock, it never gets past the Samsung Logo, No matter how many times I do a wipe. Plus, I don't understand why it keeps showing my device as custom, but the binary as samsung official, after I'm flashing stock...
Click to expand...
Click to collapse
Hm. Unfortunately this is beyond my realm of comprehension. I've read that flashing the PIT file could help, but I don't know how to do that, unfortunately. I'd do some research on that if I were you.

Anthony092 said:
I tried already, didn't work, but I'll keep looking to see if I can fix it. The minute I Put root back on my phone, it immediately started working, however every single time I try to go back to stock, it never gets past the Samsung Logo, No matter how many times I do a wipe. Plus, I don't understand why it keeps showing my device as custom, but the binary as samsung official, after I'm flashing stock...
Click to expand...
Click to collapse
Try this. Go into developer mode and see if your oem unlocking is off. Turn it on. Make sure you have Odin version .7 and make sure you update to the latest firmware for you device.

Akw6190 said:
Hm. Unfortunately this is beyond my realm of comprehension. I've read that flashing the PIT file could help, but I don't know how to do that, unfortunately. I'd do some research on that if I were you.
Click to expand...
Click to collapse
Well you tried, thank you I appreciate the help nonetheless. I'll try and research it more, for now I'll just stay rooted and explore and find options to fix it, enjoy your day.

Anthony092 said:
Well you tried, thank you I appreciate the help nonetheless. I'll try and research it more, for now I'll just stay rooted and explore and find options to fix it, enjoy your day.
Click to expand...
Click to collapse
You too, buddy. If you figure it out, report back and let us know. It may help someone in the future.

guaneet said:
Try this. Go into developer mode and see if your oem unlocking is off. Turn it on. Make sure you have Odin version .7 and make sure you update to the latest firmware for you device.
Click to expand...
Click to collapse
My OEM is on, I'm downloading the lastest firmware. I'll report back with my results

Anthony092 said:
My OEM is on, I'm downloading the lastest firmware. I'll report back with my results
Click to expand...
Click to collapse
Here is a link to the latest firmware just in case. Really fast download compared to sammobile
http://forum.xda-developers.com/showthread.php?p=64366446

guaneet said:
Here is a link to the latest firmware just in case. Really fast download compared to sammobile
http://forum.xda-developers.com/showthread.php?p=64366446
Click to expand...
Click to collapse
Thank you, very much appreciated it. I'll download from there instead =)

I've been pondering this one all day. It shouldn't be a corrupt storage device that's now dead because it would work regardless of root or not. The pit file suggested earlier should do the trick as it writes over all partitions of your device.
Another thing. It says both official and custom in download mode is an indication that something get wiped. What firmware have you been trying to flash with odin
S?ent from my SM-N920T using Tapatalk

Jammol said:
I've been pondering this one all day. It shouldn't be a corrupt storage device that's now dead because it would work regardless of root or not. The pit file suggested earlier should do the trick as it writes over all partitions of your device.
Another thing. It says both official and custom in download mode is an indication that something get wiped. What firmware have you been trying to flash with odin
S?ent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I was flashing N902TUVU2COI5, however I'm going to try and flash the latest firmware and see how it goes.
Unfortunately, I haven't found anything exactly telling me how to the pit file, so I'm for now going to stay away from that...just waiting for the latest firmware to download and I'll flash it and post my results.

Nothing working for soft bricked tab 2

I am hoping someone can help me because I have run out of ideas. I had Candy5 5.1.1 rom on my Tab2 10.1 and it was working for a while with intermittent reboots. Then it suddenly would reboot after just a few seconds. Nothing I have tried has worked, including:
1) a hard reset-I have tried wiping and resetting from CWM and from the settings but when I reboot it nothing is wiped or reset.
2) installing a new rom- I have tried installing multiple other roms from both the SD card, the internal sd card, and odin. They flash successfully but when I reboot I am right back to Candy5 and the reboot loop after a few seconds.
3) using odin-I have tried using oding to flash stock firmware, custom firmware, and a new recovery. Odin will say FAIL for the stock firmware, but for the others it will say PASS but there is still the same CWM and Candy5.
4) Sideloading- same results as above
5) installing a new recovery from SD card-nope.
6)Using ADB and fastboot-Fastboot will not recognize my device even though I have the correct drivers installed--I have also tried all the USB ports available with no change. ADB won't recognize my device for a wipe, but it will for installing another custom rom or recovery which of course does not work.
7) A few times I have had time before it reboots to try uninstalling apps. It tells me they are uninstalled but when I reboot they are back.
8) Also when it stayed I tried going into superuser settings to reset them but even though it says they are reset nothing happens after reboot.
A couple things to note:
1) it is a p5113 but has a p5110 rom and identifies itself as p5110 in download mode. This however, has not been a problem before.
2) I am running Clockworkmod Recovery v6.0.2.3
3)When I try to exit recovery I get the error message "Root access possibly lost. Fix?" and then the Yes response is "Yes-Fix root (/system/xbin/su). If I choose yes, though, it does nothing and simply reboots. Same if I choose no.
4) gapps are installed and I am certain I installed the correct version of these.
Thank you for any help you can give me. It's an old tablet but I have gotten a lot of great use from it until now!

Insight67 said:
I am hoping someone can help me because I have run out of ideas. I had Candy5 5.1.1 rom on my Tab2 10.1 and it was working for a while with intermittent reboots. Then it suddenly would reboot after just a few seconds. Nothing I have tried has worked, including:
1) a hard reset-I have tried wiping and resetting from CWM and from the settings but when I reboot it nothing is wiped or reset.
2) installing a new rom- I have tried installing multiple other roms from both the SD card, the internal sd card, and odin. They flash successfully but when I reboot I am right back to Candy5 and the reboot loop after a few seconds.
3) using odin-I have tried using oding to flash stock firmware, custom firmware, and a new recovery. Odin will say FAIL for the stock firmware, but for the others it will say PASS but there is still the same CWM and Candy5.
4) Sideloading- same results as above
5) installing a new recovery from SD card-nope.
6)Using ADB and fastboot-Fastboot will not recognize my device even though I have the correct drivers installed--I have also tried all the USB ports available with no change. ADB won't recognize my device for a wipe, but it will for installing another custom rom or recovery which of course does not work.
7) A few times I have had time before it reboots to try uninstalling apps. It tells me they are uninstalled but when I reboot they are back.
8) Also when it stayed I tried going into superuser settings to reset them but even though it says they are reset nothing happens after reboot.
A couple things to note:
1) it is a p5113 but has a p5110 rom and identifies itself as p5110 in download mode. This however, has not been a problem before.
2) I am running Clockworkmod Recovery v6.0.2.3
3)When I try to exit recovery I get the error message "Root access possibly lost. Fix?" and then the Yes response is "Yes-Fix root (/system/xbin/su). If I choose yes, though, it does nothing and simply reboots. Same if I choose no.
4) gapps are installed and I am certain I installed the correct version of these.
Thank you for any help you can give me. It's an old tablet but I have gotten a lot of great use from it until now!
Click to expand...
Click to collapse
Have you tried TWRP recovery from odin? use android-andi's or try from flashify app from your tab? I think you have done most of the things that needed to be done. the only thing left after this is try flash stock firmware with a pit file. but then if you have some other things as well to try.
it's not a regular bug, it's quiet strange, your candy rom tab looks like invincible here, or maybe the emmc has become read-only?(how on earth that happened??)

billysam said:
Have you tried TWRP recovery from odin? use android-andi's or try from flashify app from your tab? I think you have done most of the things that needed to be done. the only thing left after this is try flash stock firmware with a pit file. but then if you have some other things as well to try.
it's not a regular bug, it's quiet strange, your candy rom tab looks like invincible here, or maybe the emmc has become read-only?(how on earth that happened??)
Click to expand...
Click to collapse
Hi billysam, thanks for the response. I did try TWRP both as a zip install from the external sdcard and a sideload, as well as odin. They all tell me it was successfully installed but when I boot directly into recovery (if I did the auto reboot option I would go straight into the candy rom), I am back at CWM. I also tried the stock firmware with pit which fails during the factoryfs part.
I am not able to install any apps. If there is enough time before reboot, the app says it installed but when I reboot it is not there.
It does seem like the hard drive is read-only, or at least something is preventing me from writing to the disc.

Insight67 said:
Hi billysam, thanks for the response. I did try TWRP both as a zip install from the external sdcard and a sideload, as well as odin. They all tell me it was successfully installed but when I boot directly into recovery (if I did the auto reboot option I would go straight into the candy rom), I am back at CWM. I also tried the stock firmware with pit which fails during the factoryfs part.
I am not able to install any apps. If there is enough time before reboot, the app says it installed but when I reboot it is not there.
It does seem like the hard drive is read-only, or at least something is preventing me from writing to the disc.
Click to expand...
Click to collapse
Was the tab encrypted?
Can you get logs?
Well it's going to be a case study since I too can't find anything that could come close to your tab issue.

billysam said:
Was the tab encrypted?
Can you get logs?
Well it's going to be a case study since I too can't find anything that could come close to your tab issue.
Click to expand...
Click to collapse
It was not encrypted.
When I try to access the logs, this is what I get:
ClockworkMod Recovery v6.0.2.3
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
I Can't partition non-vfat: datamedia
I: Can't format unknown volume: /emmc
Thanks again!

When in recovery, flash twrp. Then reboot recovery. It should go to twrp then. I think your issue is recovery related.
Sent from my GT-P5110 using Tapatalk

Insight67 said:
It was not encrypted.
When I try to access the logs, this is what I get:
ClockworkMod Recovery v6.0.2.3
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
I Can't partition non-vfat: datamedia
I: Can't format unknown volume: /emmc
Thanks again!
Click to expand...
Click to collapse
Looks like a emmc issue my friend. I am afraid anything else going to work than replacing emmc.
The only reason I see here is that your tab emmc is somehow corrupted or there is bad sectors. That has virtually turned the tab into a read only and can't even read certain parts. No kind of flashing can do this to a tab. A virus attacked and is not letting you do it? Chances are no. Cause no virus can let you stop flashing from odin.
Correct Stock firmwares and pit file failed too at factoryfs part. sure you got the right files?
My suspect - the dreaded emmc issue of tab 10.1
Well do post if you find anything else.
Good luck

homephysician said:
When in recovery, flash twrp. Then reboot recovery. It should go to twrp then. I think your issue is recovery related.
Sent from my GT-P5110 using Tapatalk
Click to expand...
Click to collapse
Thank you for replying. I have tried that, but TWRP will not install. I am unable to install anything unfortunately.

billysam said:
Looks like a emmc issue my friend. I am afraid anything else going to work than replacing emmc.
The only reason I see here is that your tab emmc is somehow corrupted or there is bad sectors. That has virtually turned the tab into a read only and can't even read certain parts. No kind of flashing can do this to a tab. A virus attacked and is not letting you do it? Chances are no. Cause no virus can let you stop flashing from odin.
Correct Stock firmwares and pit file failed too at factoryfs part. sure you got the right files?
My suspect - the dreaded emmc issue of tab 10.1
Well do post if you find anything else.
Good luck
Click to expand...
Click to collapse
Yeah, I figures it might be that. It makes sense as to why I can't install anything and why fastboot won't recognize the device. My confusion was that my laptop does recognize it as at p5110 device and I can access the drive and it's folders on my laptop. I just can't delete anything. I don't know of any viruses and I had only a few select video streaming apps on it. I tried the p5110 and the p5113 from sam mobile so if you know of any other stock firmware links or toolkits I would love to try them. I hate to get rid of a tablet that isn't really bricked.

Insight67 said:
I hate to get rid of a tablet that isn't really bricked.
Click to expand...
Click to collapse
Same feeling goes here but wait, it does connect to your laptop and you can access files from it! You can transfer new files on it? And does it stay even after reboot?
Well I am looking for a new way out here, something that hasn't been tried on our devices to recover a tab from a difficult situation, a different approach. But will need help from our community. I will share that on a new thread once I am done researching myself. But sadly I have a P5100. But we will see what can be done.

billysam said:
Same feeling goes here but wait, it does connect to your laptop and you can access files from it! You can transfer new files on it? And does it stay even after reboot?
Well I am looking for a new way out here, something that hasn't been tried on our devices to recover a tab from a difficult situation, a different approach. But will need help from our community. I will share that on a new thread once I am done researching myself. But sadly I have a P5100. But we will see what can be done.
Click to expand...
Click to collapse
Well, it's a bit stranger than that. My laptop recognizes it as a p5110 and I can go into the files. I can even (if it doesn't immediately start rebooting) delete folders. But, when I reboot, the folders are back as if they were never deleted.
I was also able to sideload a rom onto my sdcard (not external sd) and it tells me install is complete. But nothing changes.
This is what I am getting when I install, which makes me think there is a piece of the factory firmware that is still around interfering with the custom rom:
Installing update....
Warning: No file_contextsdetected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
Then after the logo of the rom:
(*) Running backup scripts...
detected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
(*) Done.
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
unmount of /system failed: no such volume
script succeeded: result was [ ]
Install from sd card complete
Thank you again for your help. If I figure anything else out I will post as well in case anyone else has this issue.

Insight67 said:
Well, it's a bit stranger than that. My laptop recognizes it as a p5110 and I can go into the files. I can even (if it doesn't immediately start rebooting) delete folders. But, when I reboot, the folders are back as if they were never deleted.
I was also able to sideload a rom onto my sdcard (not external sd) and it tells me install is complete. But nothing changes.
This is what I am getting when I install, which makes me think there is a piece of the factory firmware that is still around interfering with the custom rom:
Installing update....
Warning: No file_contextsdetected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
Then after the logo of the rom:
(*) Running backup scripts...
detected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
(*) Done.
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
unmount of /system failed: no such volume
script succeeded: result was [ ]
Install from sd card complete
Thank you again for your help. If I figure anything else out I will post as well in case anyone else has this issue.
Click to expand...
Click to collapse
it's the same message that I get while installing a custom rom. but mine does write it on the system and it did change my rom.
Okay, we should concentrate on the firmware file that should flash through odin without fail.
why is it not flashing it, while others are getting flashed?
You did download it from sam mobile, that's the best place to get it.
pit file, is almost identical for all the p51xx 16gb variant, I was going through the same right now. so no chance of getting wrong pit partitioned. (by any chance, you ever flashed a different pit file on your tab?)
try to flash on a different pc/laptop? download stock firmware again, this is your best bet. any other options are just beating around bushes.

billysam said:
it's the same message that I get while installing a custom rom. but mine does write it on the system and it did change my rom.
Okay, we should concentrate on the firmware file that should flash through odin without fail.
why is it not flashing it, while others are getting flashed?
You did download it from sam mobile, that's the best place to get it.
pit file, is almost identical for all all the p51xx, I was going through the same right now. so no chance of getting wrong pit partitioned.
try to flash on a different pc/laptop? download stock firmware again, this is your best bet. any other options are just beating around bushes.
Click to expand...
Click to collapse
That is a good idea. I have been using the same laptop for all of this. I will try a different PC and let you know how it goes.
Thanks again!!

billysam said:
it's the same message that I get while installing a custom rom. but mine does write it on the system and it did change my rom.
Okay, we should concentrate on the firmware file that should flash through odin without fail.
why is it not flashing it, while others are getting flashed?
You did download it from sam mobile, that's the best place to get it.
pit file, is almost identical for all the p51xx 16gb variant, I was going through the same right now. so no chance of getting wrong pit partitioned. (by any chance, you ever flashed a different pit file on your tab?)
try to flash on a different pc/laptop? download stock firmware again, this is your best bet. any other options are just beating around bushes.
Click to expand...
Click to collapse
I tried a different computer but still got the fail from odin. If I come up with anything that works I'll be sure to post it. Thanks for all your help!

Just a shot in the dark, but did not see "Factory reset" mentioned.
Nobody wants to hear that but sometimes it's the only solution.
Pp.

PanchoPlanet said:
Just a shot in the dark, but did not see "Factory reset" mentioned.
Nobody wants to hear that but sometimes it's the only solution.
Pp.
Click to expand...
Click to collapse
Oh, yes, tried that numerous times. It won't reset. Thanks for the reply, though!

Insight67 said:
Oh, yes, tried that numerous times. It won't reset. Thanks for the reply, though!
Click to expand...
Click to collapse
http://wiki.cyanogenmod.org/w/EMMC_Bugs
Found it. That explains all.

billysam said:
http://wiki.cyanogenmod.org/w/EMMC_Bugs
Found it. That explains all.
Click to expand...
Click to collapse
Thanks billysam! If I am reading this correctly, only replacing the motherboard would work.

Insight67 said:
Thanks billysam! If I am reading this correctly, only replacing the motherboard would work.
Click to expand...
Click to collapse
Yes, according to that post. For me, I don't know because I haven't faced it myself, for you, you can try the options between changing emmc or changing motherboard or replacing a new tab or Jtag. Of course Whatever the technical guys you take your tab to for repair and which doesn't cost you much. Although people said changing emmc or jtag won't work. But you never know until tried. Also I won't suggest you try yourself. Good luck. It was good learning experience here.

billysam said:
Yes, according to that post. For me, I don't know because I haven't faced it myself, for you, you can try the options between changing emmc or changing motherboard or replacing a new tab or Jtag. Of course Whatever the technical guys you take your tab to for repair and which doesn't cost you much. Although people said changing emmc or jtag won't work. But you never know until tried. Also I won't suggest you try yourself. Good luck. It was good learning experience here.
Click to expand...
Click to collapse
Thank you!