Ok, I have read through everything. I have followed all the directions. Here is my situation. Hoping someone can help...
Ok, I purchased a white skyrocket off ebay. It works. Kinda. I can make calls and send txts. Data works. But it is obviously a custom ROM and there is a lot wrong with it. For one, the screen NEVER times out. Even when I set a timeout in the settings. I can push the power button and turn the screen off. I can set a security pattern to unlock the screen, but it never prompts me for it when I power the screen on. The bluetooth radio won't turn off. Many other issues.
I followed the "return to stock method" using ODIN an the ko-kane .TAR, but all it seems to is overwrite SOME of the issues I am having. It's not truly returning to stock. My email settings and txt's are still there even after flashing. It also doesn't prompt me for my gmail setup, do the phone tutorial etc, etc.
So, is there a way for me to TRULY go back to stock? Am I just missing something here? I want to have this be as if it had never powered on before. Is that possible? Thanks in advance for the assistance...
theshifter said:
Ok, I have read through everything. I have followed all the directions. Here is my situation. Hoping someone can help...
Ok, I purchased a white skyrocket off ebay. It works. Kinda. I can make calls and send txts. Data works. But it is obviously a custom ROM and there is a lot wrong with it. For one, the screen NEVER times out. Even when I set a timeout in the settings. I can push the power button and turn the screen off. I can set a security pattern to unlock the screen, but it never prompts me for it when I power the screen on. The bluetooth radio won't turn off. Many other issues.
I followed the "return to stock method" using ODIN an the ko-kane .TAR, but all it seems to is overwrite SOME of the issues I am having. It's not truly returning to stock. My email settings and txt's are still there even after flashing. It also doesn't prompt me for my gmail setup, do the phone tutorial etc, etc.
So, is there a way for me to TRULY go back to stock? Am I just missing something here? I want to have this be as if it had never powered on before. Is that possible? Thanks in advance for the assistance...
Click to expand...
Click to collapse
Yeah, you have to wipe it manually in cwm. Then flash the sammobile tar in odin
xcrazydx said:
Yeah, you have to wipe it manually in cwm. Then flash the sammobile tar in odin
Click to expand...
Click to collapse
OK, I found it, its a zip with a bunch of TAR inside. I cant use CWM to install the zip. I looked for what to do and I am stuck...
theshifter said:
OK, I found it, its a zip with a bunch of TAR inside. I cant use CWM to install the zip. I looked for what to do and I am stuck...
Click to expand...
Click to collapse
found it where? you download from sammobile.com. You have to extract it with 7zip and flash it in odin, not cwm.
slow down and read a bit, no sense in rushing and making a brick
xcrazydx said:
found it where? you download from sammobile.com. You have to extract it with 7zip and flash it in odin, not cwm.
slow down and read a bit, no sense in rushing and making a brick
Click to expand...
Click to collapse
Well, I found it, ran the flash in ODIN. Nothing. Still having all the same issues. I have no clue where to go from here...
theshifter said:
Well, I found it, ran the flash in ODIN. Nothing. Still having all the same issues. I have no clue where to go from here...
Click to expand...
Click to collapse
Did you wipe everything a bunch of times and format everything before flash?
xcrazydx said:
Did you wipe everything a bunch of times and format everything before flash?
Click to expand...
Click to collapse
I did wipe davlik, cache, format, and fix permissions. I can try it again and see what happens...
theshifter said:
I did wipe davlik, cache, format, and fix permissions. I can try it again and see what happens...
Click to expand...
Click to collapse
that was before the ODIN flash though...
theshifter said:
I did wipe davlik, cache, format, and fix permissions. I can try it again and see what happens...
Click to expand...
Click to collapse
wipe data/factory reset x3
wipe cache x3
wipe dalvik cache x3
Format system x3
Format emmc x3
Format sdcard x3
boot back into download mode and odin sammobile tar
That will wipe everything on your internal and external sd cards, so back up whatever you dont wanna lose forever.
Try darkside wipe (search for it and read the thread) and then flash one of the custom GB Roms floating around. It doesn't matter which one, just pick a popular and similar (close to stock) one. If you can find the CWM flashable version of the stock ROM that would be even better. Make sure you flash the necessary radio / modem for the ROM you pick before you flash the ROM just to be safe. After you make sure the phone boots properly but before you set anything up (Email, etc...) do a factory reset. Again, reboot to make sure everything is working. Then, go back and flash (with ODIN) either K0nane's TAR or the SamMobile TAR. The SamMobile Tar will have the proper radio / modem with it.
If you flash the SamMobile TAR without wiping first (ie installing a new ROM that hasn't been set up), the Sammobile TAR will port certain settings over to the new flash. It did for me anyway. If you don't understand the things I posted make sure you take the time on your own to research the topics and find the correct links on your own. All you need is the search function and the time to do the reasearch you need to do and you should be fine. Good luck.
scott14719 said:
Try darkside wipe (search for it and read the thread) and then flash one of the custom GB Roms floating around. It doesn't matter which one, just pick a popular and similar (close to stock) one. If you can find the CWM flashable version of the stock ROM that would be even better. Make sure you flash the necessary radio / modem for the ROM you pick before you flash the ROM just to be safe. After you make sure the phone boots properly but before you set anything up (Email, etc...) do a factory reset. Again, reboot to make sure everything is working. Then, go back and flash (with ODIN) either K0nane's TAR or the SamMobile TAR. The SamMobile Tar will have the proper radio / modem with it.
If you flash the SamMobile TAR without wiping first (ie installing a new ROM that hasn't been set up), the Sammobile TAR will port certain settings over to the new flash. It did for me anyway. If you don't understand the things I posted make sure you take the time on your own to research the topics and find the correct links on your own. All you need is the search function and the time to do the reasearch you need to do and you should be fine. Good luck.
Click to expand...
Click to collapse
I did all the above (darkside wipe, new ROM, etc) and I am still stuck with all the same issues after the new flash. This makes NO SENSE to me at all. I am... frustrated
theshifter said:
I did all the above (darkside wipe, new ROM, etc) and I am still stuck with all the same issues after the new flash. This makes NO SENSE to me at all. I am... frustrated
Click to expand...
Click to collapse
Goto "settings" "about phone". What does the Android version, Baseband version, Kernel version, and Build number say?
It is possible you may need to reformat your internal and external SD cards. You could also have a corrupt Efs partition. Read this:
http://forum.xda-developers.com/showthread.php?t=1611796
If you reformat your SD cards, make sure you backup any information you want to keep.
Even reflash your radio / modem just for the hell of it.
If you try all of this and everything else you said you have tried it would be near impossible for your phone to retain any information from previous flashes.
scott14719 said:
Goto "settings" "about phone". What does the Android version, Baseband version, Kernel version, and Build number say?
It is possible you may need to reformat your internal and external SD cards. You could also have a corrupt Efs partition. Read this:
http://forum.xda-developers.com/showthread.php?t=1611796
If you reformat your SD cards, make sure you backup any information you want to keep.
Even reflash your radio / modem just for the hell of it.
If you try all of this and everything else you said you have tried it would be near impossible for your phone to retain any information from previous flashes.
Click to expand...
Click to collapse
It was the corrupt EFS partition. Ran method #2 (did that first, it seemed easier to be honest) and when the phone rebooted, it had prompted me for the screen lock password. Thanks so much for the advice everybody. Took awhile but I am glad it did because I learned quite a bit going through all of the steps.
Restoring Skyrocket ICS->GB (ClockworkMod Recovery v5.0.2.6 installed)
Need Help,
I want to go back to the gingerbread stock ROM as the ICS installed currently is giving me a lot of problems. My GPS has also stopped working.
I started here http://forum.xda-developers.com/showthread.php?t=1342348 and followed all instructions. But i get stuck because when using Odin i get the following output and that's it, it does not go ahead.
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
I have the SGH-I727 from AT&T but with leaked ICS and also rooted with ClockworkMod Recovery v5.0.2.6. I cannot seem to go to the "Download Mode" as the process after power off takes me directly to the Recovery options.
Would I need to unRoot the device? or can i use any option available right now in this recovery mode?
What am i doing wrong? or not doing anything at all?
Sorry if this was the wrong thread to post to.
tapan_skyrocket said:
Need Help,
I want to go back to the gingerbread stock ROM as the ICS installed currently is giving me a lot of problems. My GPS has also stopped working.
I started here http://forum.xda-developers.com/showthread.php?t=1342348 and followed all instructions. But i get stuck because when using Odin i get the following output and that's it, it does not go ahead.
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
I have the SGH-I727 from AT&T but with leaked ICS and also rooted with ClockworkMod Recovery v5.0.2.6. I cannot seem to go to the "Download Mode" as the process after power off takes me directly to the Recovery options.
Would I need to unRoot the device? or can i use any option available right now in this recovery mode?
What am i doing wrong? or not doing anything at all?
Sorry if this was the wrong thread to post to.
Click to expand...
Click to collapse
Pull battery
put battery back in
plug usb cable into computer but not into phone yet
Hold both volume buttons and plug the cable into phone at the same time
after screen pops up press volume up to enter dl mode
I'm in a bit of a similar position, but I simply need to recover from a boot loop.
Can I extract the MD5 from the downloaded SamMobile zip and simply flash away in Odin?
I can access both CWM and download mode, but I've got nothing to flash on the internal SD, don't have an external SD.
I do not have a nandroid backup.
anonomike said:
I'm in a bit of a similar position, but I simply need to recover from a boot loop.
Can I extract the MD5 from the downloaded SamMobile zip and simply flash away in Odin?
I can access both CWM and download mode, but I've got nothing to flash on the internal SD, don't have an external SD.
I do not have a nandroid backup.
Click to expand...
Click to collapse
Yeah.
http://forum.xda-developers.com/showthread.php?t=1668792
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Going back to Gingerbread
I flashed the update sucessfully, thank you for the tip xcrazydx. But started to get errors as soon as i swipe my logonscreen, try to use the phone, calender, change volume etc. Sometimes i got 2-3 errors in succession. An example would be
"Sorry! The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly. Please try again." - On trying to make a call and then two more errors after that before i go back to home screen.
Also the trip counter on cusom ROM on the download screen shows 1 and it says "current ROM: Custom"
I have now flashed with another ICS ROM which suceeded. My GPS is also working now
Just thought others shoudl know!!
Related
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?
So long story short, my tab was running stock ICS (rooted, with temp CWM/cwm.zip). I decided to try a new rom (paranoid android) so I backed up everything via CWM and I flashed the new rom. But I forgot to do a factory reset before doing so which resulted in a bootloop. I returned to CWM to try to restore the previous ROM, all seemed to be fine and the tab restarted but was also bootlooped. Now I can't even access the stock recovery to acess CWM, I get an error message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC code : THL
Successfully applied multi-CSC
E :failed to mount / system (invalid argument) <in red.
Is there anything I can do to return to my stock ROM?!
Do I have the Brick Bug?
rumpypumpy said:
So long story short, my tab was running stock ICS (rooted, with temp CWM). I decided to try a new rom (paranoid android) so I backed up everything via CWM and I flashed the new rom. But I forgot to do a factory reset before doing so which resulted in a bootloop. I returned to CWM to try to restore the previous ROM, all seemed to be fine and the tab restarted but was also bootlooped. Now I can't even access the stock recovery to acess CWM, I get an error message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC code : THL
Successfully applied multi-CSC
E :failed to mount / system (invalid argument) <in red.
Is there anything I can do to return to my stock ROM?!
Click to expand...
Click to collapse
Can it get into download mode? If so try flash a stock rom with odin. Im not a sgt user but i am a samsung phone user and usualy when i forget to wipe all i have to do is go back into recovery. Then wipe everything and flash the same rom. NEVER go straight to a backup unless you pass setup. Then it can create a link almost so it supports going back. Or so thats what ive been told by devs on other forums...sounds kinda wierd tho but anyway if you forget to do something while flashing roms then go back indo recovery and do it again
Sent from the phone of Gamers
gmaster1 said:
Can it get into download mode? If so try flash a stock rom with odin. Im not a sgt user but i am a samsung phone user and usualy when i forget to wipe all i have to do is go back into recovery. Then wipe everything and flash the same rom. NEVER go straight to a backup unless you pass setup. Then it can create a link almost so it supports going back. Or so thats what ive been told by devs on other forums...sounds kinda wierd tho but anyway if you forget to do something while flashing roms then go back indo recovery and do it again
Sent from the phone of Gamers
Click to expand...
Click to collapse
It loads the amination for the stock recovery, then I get the error message I posted above. I need to get onto the stock recovery to get into CWM. Im not too sure what to do at the moment...
rumpypumpy said:
It loads the amination for the stock recovery, then I get the error message I posted above. I need to get onto the stock recovery to get into CWM. Im not too sure what to do at the moment...
Click to expand...
Click to collapse
Thats a messege saying the system has broke basicly because you went straight to a backup. Download mode and odin are your only hope
Sent from the phone of Gamers
gmaster1 said:
Thats a messege saying the system has broke basicly because you went straight to a backup. Download mode and odin are your only hope
Sent from the phone of Gamers
Click to expand...
Click to collapse
I forgot about download mode. I'll have a go then I'll report back.
Thanks
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
rumpypumpy said:
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
Click to expand...
Click to collapse
From CWM wipe data, cache & dalvik & reboot.
And flash this ICS zip file from CWM. if yours is 6800.
http://forum.xda-developers.com/showthread.php?t=1796866
rumpypumpy said:
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
Click to expand...
Click to collapse
If cwm works then we both know theres hope
Sent from the phone of Gamers
lsherif said:
From CWM wipe data, cache & dalvik & reboot.
And flash this ICS zip file from CWM. if yours is 6800.
http://forum.xda-developers.com/showthread.php?t=1796866
Click to expand...
Click to collapse
I did everything you said, but the progress bar has been stuck at 75% for over an hour, this has happened with all the ROMs I've tried to install. Is there anything else I could do? I red somewhere that a low battery doesn't allow ROMs to be installed properly.
Although I have no idea of my battery life, I'm just gonna leave it to charge for a bit. I hope everything turns out fine eventually
rumpypumpy said:
I did everything you said, but the progress bar has been stuck at 75% for over an hour, this has happened with all the ROMs I've tried to install. Is there anything else I could do? I red somewhere that a low battery doesn't allow ROMs to be installed properly.
Although I have no idea of my battery life, I'm just gonna leave it to charge for a bit. I hope everything turns out fine eventually
Click to expand...
Click to collapse
Battery life has nothing to do with it. People just say make sure you have high battery incase something happens. I think that it might be a very expensive brick now. Unless anyone else knows then i habe no idea
Sent from the phone of Gamers
gmaster1 said:
Battery life has nothing to do with it. People just say make sure you have high battery incase something happens. I think that it might be a very expensive brick now. Unless anyone else knows then i habe no idea
Sent from the phone of Gamers
Click to expand...
Click to collapse
:crying:
I was reading the following articles:
http://www.xda-developers.com/android/samsung-diligently-working-towards-hardbrick-fix/
http://forum.xda-developers.com/showthread.php?t=1810954
Could this Brick Bug be the source of my problems?
I was running a leaked version of ICS AND I have been using the cwm.zip so there is the possibility
Being unable to flash through either Odin or CWM surely sounds a lot like the brickbug.
If I were you, I'd reboot to download mode, and install a full ROM with repartition + PIT file. If it works, install locerra's CWM (it's one of the few recoveries for our tablet that's confirmed to be brickbug-free), and work as usual. But remember to wipe everything before installing anything through CWM...
If Odin doesn't work, you probably have been hit by the brickbug. However, all is not lost: this guy seems to have found a "fix" for many devices. It involves giving up on all your data and making your onboard storage a couple of GB smaller than it used to be, but it can make your device work again. Read the thread, try to understand it, and (if you can't find another way out) use the PIT file for the GT-6800 provided. If your tab isn't the international WiFi+3G GT-P6800, you may have to ask the guy (hg42) for a PIT tailored to your device.
The other option, in the case of a eMMC-related brick, is to remove all traces of CWM, go to a Samsung store and repair it under warranty, saying "its broke down when I were running that backie upppe thing in kies".
The other option is the better one, as i bricked my note. When i am able to revive it, i am left with 8GB space and it seems real laggy. Change a new motherboard would be better if still cover undr warrantly.
Sent from my GT-P6800 using xda premium
Thanks for the replies guy.
I have decided I will return it as faulty, in the hope it is repaired. I haven't been able to boot into CWM anymore, only the download mode, so I am guessing it is fine to return it as it is?
Thanks
rumpypumpy said:
Thanks for the replies guy.
I have decided I will return it as faulty, in the hope it is repaired. I haven't been able to boot into CWM anymore, only the download mode, so I am guessing it is fine to return it as it is?
Thanks
Click to expand...
Click to collapse
If I were you, I'd return it to something as close to stock as possible.
One suggestion: grab the latest Odin-flashable ROM for your country. You'll get a .tar.md5 file, such as P6800UBLA2_P6800ZTOLA2_ZTO.tar.md5. Try to flash it through Odin, just to see if it works; if it doesn't, write down the name of the .img file that gave you problems. If it works, congratulations, you have your tablet back, and you can stop reading.
Now, Rename that file to .tar (or, remove the .md5 extension), and open it in WinRAR/7zip/whatever. You'll see a lot of .img files inside, including the one that gave you problems. Remove it, and try to flash this new .tar file. If the flash works, proceed to the next paragraph. If it doesn't, write down the name of the .img file that gave you problems, and repeat this paragraph using your new .tar file.
After a flash that works, your device should be as close to stock as possible. Maybe it will even boot, but I wouldn't count on it (try anyway). I'd send it to the repair centre only when it is at this stage.
Steve_max said:
If I were you, I'd return it to something as close to stock as possible.
One suggestion: grab the latest Odin-flashable ROM for your country. You'll get a .tar.md5 file, such as P6800UBLA2_P6800ZTOLA2_ZTO.tar.md5. Try to flash it through Odin, just to see if it works; if it doesn't, write down the name of the .img file that gave you problems. If it works, congratulations, you have your tablet back, and you can stop reading.
Now, Rename that file to .tar (or, remove the .md5 extension), and open it in WinRAR/7zip/whatever. You'll see a lot of .img files inside, including the one that gave you problems. Remove it, and try to flash this new .tar file. If the flash works, proceed to the next paragraph. If it doesn't, write down the name of the .img file that gave you problems, and repeat this paragraph using your new .tar file.
After a flash that works, your device should be as close to stock as possible. Maybe it will even boot, but I wouldn't count on it (try anyway). I'd send it to the repair centre only when it is at this stage.
Click to expand...
Click to collapse
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
rumpypumpy said:
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
Click to expand...
Click to collapse
Thats...a...problem...if it takes longer then 15 mins its bricked...i have been a gt user and devs on other sites told me it was bricked. Maybe there is a solution but...i havnt found one. It should never take too long on one thing in odin.
Sent from the phone of Gamers
rumpypumpy said:
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
Click to expand...
Click to collapse
Even so, flash the other .imgs. You want to be closest to stock, including the recovery (imagine the guys at the Samsung centre manage to enter recovery, just to see CWM: your warranty is now gone). Having all partitions on stock, or at least most of them, can only help your case.
Steve_max said:
Even so, flash the other .imgs. You want to be closest to stock, including the recovery (imagine the guys at the Samsung centre manage to enter recovery, just to see CWM: your warranty is now gone). Having all partitions on stock, or at least most of them, can only help your case.
Click to expand...
Click to collapse
The warrenty is not void unless they find proof of tampering with system files. So basicly yeah...everything that guy said. Get it as close to stock as possible and send.
Sent from the phone of Gamers
Right OK, I definately don't want my warrenty void!
So would it be ok if I flashed 'P6800OXALQ1_P6800XXLQ1_HOME.tar.md5' (minus the factoryfs.img) to my tab?
Thanks
First of all thanks for your help in advance.
I have a Galaxy Tab 2 10.1 GT-P5113 which I bought the way it is right now. It turns on and I can access recovery and download mode without any problems, but it will not boot into the actual OS. After turning on it will go straight to recovery. When rebooted from within recovery or by ODIN after flashing a ROM it will simply turn off and start charging. It will not turn on without having to unplug the cable. This is what I have tried:
- Flashed stock 4.1.1 from SamMobile using Odin 3.09 and Odin 1.85 there were no errors but same problem
- Flashed stock 4.2.2 from SamMobile using Odin 3.09 and Odin 1.85 there were no errors but same problem
- Installed CWM Touch 6.0.1.2 and wiped Dalvik cache and factory reset a few times after flashing each firmware version
- Installed TWRP 2.7.0.1 and wiped Dalvik cache, cache, data and factory reset a few times after flashing each firmware version
- Flashed each firmware and did stock factory reset and wiped cache each time
- Took it apart and removed battery for a few hours and tried every combination of what was mentioned again
- Downloaded "signed_espresso_20120220_16G.pit" and flashed a few times and redid all combinations again
On CWM no command gives any errors but on TWRP I do not get the "successful" notice when wiping Data, it kicks me out to the lock screen with no errors mentioned. Also on TWRP, when trying to fix permissions I get a failed error. When flashing stock 4.2.2 I get the "No command" and an error while trying to wipe cache follow by the device turning off. On the stock 4.1.1 ROM I get no errors whatsoever.
So as you may imagine I have spent numerous hours on Google and this forum and have not found a way to make it work. Please let me know if there is anything else I might be able to try. Thanks
I have the same problem but I know what I did to cause it.
Well, I don't know if you solved your problem, but I just registered to ask the same question. ONLY I KNOW HOW IT GOT THAT WAY. while messing around with learning how to flash new ROMs I executed a command that I didn't know what expect... mkntfs and followed through with mmcblk0p1 or mmcblk0p10... i'm not real sure which partition I messed up. but now I don't know how to reverse the thing and I have the exact problem you have.
Also I can't find a good reference source for Aroma File Manager's Terminal console. I'm just learning about Linux, CPM/android or whatever we call it these days.
Do I have to fix the kernel or is there a way to undo that command "mkntfs" in AromaFM??????
I TOO have the GT-P5113XAR but one of the aborted rom installations said it's a GT-5113RF, what is that????
GalaxyBrickMaker said:
Well, I don't know if you solved your problem, but I just registered to ask the same question. ONLY I KNOW HOW IT GOT THAT WAY. while messing around with learning how to flash new ROMs I executed a command that I didn't know what expect... mkntfs and followed through with mmcblk0p1 or mmcblk0p10... i'm not real sure which partition I messed up. but now I don't know how to reverse the thing and I have the exact problem you have.
Also I can't find a good reference source for Aroma File Manager's Terminal console. I'm just learning about Linux, CPM/android or whatever we call it these days.
Do I have to fix the kernel or is there a way to undo that command "mkntfs" in AromaFM??????
I TOO have the GT-P5113XAR but one of the aborted rom installations said it's a GT-5113RF, what is that????
Click to expand...
Click to collapse
Thanks for the reply. I frankly don't know much about what you said, but I decided to order a new board for the device and got it to work again. Now, super-duper-mega-smart-me decided to flash the same 4.2.2 ROM I got from Sammobile and guess what, the EXACT same problem occurred. I am hoping someone can helps us! Right now I am researching different ROM's and realized there are 2 kinds, XAR and XAC so I will experiment and let you know if I get any progress!
hopefully someone will read the problem and give us some advice.
I still haven't learned how to reverse a mkntfs command.
Flash P5113UEUCMK3 using PDA in Odin while in download mode should be all. You shouldn't have needed any other files or whatever...
Sent from my Nexus 4 using XDA Premium HD app
shakatu said:
Flash P5113UEUCMK3 using PDA in Odin while in download mode should be all. You shouldn't have needed any other files or whatever...
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the reply. Actually you are right, all that had to be done was exactly that. However in my case the real problem, mentioned just so other people can see this if they have the same problem, was that the flex cable that charges the tablet was defective. I took the device apart and decided to unplug piece by piece turning the device on after each cable was unplugged and low and behold after disconnecting the charger flex it went straight to the OS instead of recovery. Weirdest thing ever, hope it helps someone else.
GalaxyBrickMaker said:
I still haven't learned how to reverse a mkntfs command.
Click to expand...
Click to collapse
In your case, based on what I have researched here is what you can try. Get into download mode, open ODIN, click on PIT and flash file "signed_espresso_20120220_16G.pit" which can be found in this forum, just do a search. After flashing the PIT go to SamMobile and download a ROM, preferably MK3 and flash using ODIN. After this it should work, hope it does for you!
Edit: Here is the link for the PIT: http://forum.xda-developers.com/showthread.php?t=2552155
thanks
"signed_espresso_20120220_16G.pit"
which can be found in this forum, just do a search.
After flashing the PIT go to SamMobile and download a ROM, preferably MK3 and flash using ODIN. After this it should work, hope it does for you!
Edit: Here is the link for the PIT:
http://forum.xda-developers.com/showthread.php?t=2552155
thank you for the informaiton I will let you know how it goes.. also can I flash any ROM after this or should I do the SAMMOBILE one first no matter what?
I already have the P5113XARUEU_P5113CSC...... file, but right before3 i messed it up I had Kit Kat running.
GalaxyBrickMaker said:
"signed_espresso_20120220_16G.pit"
which can be found in this forum, just do a search.
After flashing the PIT go to SamMobile and download a ROM, preferably MK3 and flash using ODIN. After this it should work, hope it does for you!
Edit: Here is the link for the PIT:
http://forum.xda-developers.com/showthread.php?t=2552155
thank you for the information I will let you know how it goes.. also can I flash any ROM after this or should I do the SAMMOBILE one first no matter what?
I already have the P5113XARUEU_P5113CSC...... file, but right before3 i messed it up I had Kit Kat running.
Click to expand...
Click to collapse
Sorry for the late reply, had a busy week. You probably already fixed it but it is my understanding you need to flash a stock ROM to get things going again and once that works make a backup of the working ROM using CWM recovery or similar and then flash whatever else on top of that to prevent further bricks. Thanks
more info please
Danz777 said:
First of all thanks for your help in advance.
I have a Galaxy Tab 2 10.1 GT-P5113 which I bought the way it is right now. It turns on and I can access recovery and download mode without any problems, but it will not boot into the actual OS. After turning on it will go straight to recovery. When rebooted from within recovery or by ODIN after flashing a ROM it will simply turn off and start charging. It will not turn on without having to unplug the cable. This is what I have tried:
- Flashed stock 4.1.1 from SamMobile using Odin 3.09 and Odin 1.85 there were no errors but same problem
- Flashed stock 4.2.2 from SamMobile using Odin 3.09 and Odin 1.85 there were no errors but same problem
- Installed CWM Touch 6.0.1.2 and wiped Dalvik cache and factory reset a few times after flashing each firmware version
- Installed TWRP 2.7.0.1 and wiped Dalvik cache, cache, data and factory reset a few times after flashing each firmware version
- Flashed each firmware and did stock factory reset and wiped cache each time
- Took it apart and removed battery for a few hours and tried every combination of what was mentioned again
- Downloaded "signed_espresso_20120220_16G.pit" and flashed a few times and redid all combinations again
On CWM no command gives any errors but on TWRP I do not get the "successful" notice when wiping Data, it kicks me out to the lock screen with no errors mentioned. Also on TWRP, when trying to fix permissions I get a failed error. When flashing stock 4.2.2 I get the "No command" and an error while trying to wipe cache follow by the device turning off. On the stock 4.1.1 ROM I get no errors whatsoever.
So as you may imagine I have spent numerous hours on Google and this forum and have not found a way to make it work. Please let me know if there is anything else I might be able to try. Thanks
Click to expand...
Click to collapse
Fortunately I got mine working again and now I have some more insight for you. Are there any errors showing when you're trying to install aarom?also if you use console in aroma file managercan you list all 11 or 12 partitions and aer they all available for you to access?
---------- Post added at 11:39 AM ---------- Previous post was at 11:25 AM ----------
I tried both things that you told me to try the pit file it might have helped but it didn't make it any different, there was still an error trying to find efs while flashing and I tried it almost everything the other guy here tried and nothing worked so I had to go learn some Linux and some Unix. After a couple weeks of studying what command does what, and realizing I should have learned Unix with the rest of my friends and back in high school. I came up with that make FS ext4 command.. as I said before I knew which command I used to mess it up so I figured since the mkntfs command was the one that messed itt up with them this one might work and I used it and it worked I was able to install a ROM 2 days ago. Apologize for my typing my hands hurt and I'm just using voice.
GalaxyBrickMaker said:
Fortunately I got mine working again and now I have some more insight for you. Are there any errors showing when you're trying to install aarom?also if you use console in aroma file managercan you list all 11 or 12 partitions and aer they all available for you to access?
---------- Post added at 11:39 AM ---------- Previous post was at 11:25 AM ----------
I tried both things that you told me to try the pit file it might have helped but it didn't make it any different, there was still an error trying to find efs while flashing and I tried it almost everything the other guy here tried and nothing worked so I had to go learn some Linux and some Unix. After a couple weeks of studying what command does what, and realizing I should have learned Unix with the rest of my friends and back in high school. I came up with that make FS ext4 command.. as I said before I knew which command I used to mess it up so I figured since the mkntfs command was the one that messed itt up with them this one might work and I used it and it worked I was able to install a ROM 2 days ago. Apologize for my typing my hands hurt and I'm just using voice.
Click to expand...
Click to collapse
I am glad you finally got it working. I never did play much with Aroma since my problem ended up being that defective cable but I will definitely consider learning those commands just in case.
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.
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.