PLEASE HELP Nand Erase all, boot loop - Note Edge Q&A, Help & Troubleshooting

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.

Related

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?

HELP! Brick Bug!

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

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.

S6 - Boot Loop - No Recovery - HELP!!!

Hi All,
I a strange thing happened yesterday. My S6 got stuck and when I did a force restart it ended up in a boot loop. To worsen the problem my device had reactivation enabled. I found out that my recovery is not loading also. I guess its due to the reactivation security.
So far I have tried the following:
1. Tried to install the stock firmware
2. Tried to install new stock firmware (marshmellow)
3. Tried Kies and Smart Connect (did not do anything)
I'm pretty much clueless at this point. Any help is appreciated.
Thanks in advanced...
Any captains to help?
Maybe try flashing ONLY the 'recovery.img' inside the firmware file, and if you can get into the stock recovery after that then clear cache and wipe, then try to flash firmware again
emcardle660 said:
Maybe try flashing ONLY the 'recovery.img' inside the firmware file, and if you can get into the stock recovery after that then clear cache and wipe, then try to flash firmware again
Click to expand...
Click to collapse
Thank you very much for the input. Do you feel that when I flash the original firmware it did not apply the recovery.img that was inside the tar ball? I could manage to create a tar ball with only the recovery image but in that case will it trigger the knox counter and void warranty?
Again, I really appreciate your feedback. Thanks mate
BTW I tried with both Odin and smart connect. Nothing helped. They both complete and say it went well but after restart its simply another boot loop
When you flash stock with odin it should say pass and should boot or visit Samsung for fix
tazaga said:
When you flash stock with odin it should say pass and should boot or visit Samsung for fix
Click to expand...
Click to collapse
It does say PASS. But when it reboots I end up with the boot loop again.
BTW Reactivation lock is ON. Could this be a problem?
Hi Dude
I just flashed my other halfs S6 loads and discovered a working Recovery was Arter97's after MUCH soft bricks etc
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Flashable via odin
For me tho if worst comes to worst getting a fresh rom from sammobile worked okay
Hope you get sorted bro
Jonny5isalivetm said:
Hi Dude
I just flashed my other halfs S6 loads and discovered a working Recovery was Arter97's after MUCH soft bricks etc
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Flashable via odin
For me tho if worst comes to worst getting a fresh rom from sammobile worked okay
Hope you get sorted bro
Click to expand...
Click to collapse
Thank you very much. I will surely try this tonight. I will post my findings here.
Jonny5isalivetm said:
Hi Dude
I just flashed my other halfs S6 loads and discovered a working Recovery was Arter97's after MUCH soft bricks etc
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Flashable via odin
For me tho if worst comes to worst getting a fresh rom from sammobile worked okay
Hope you get sorted bro
Click to expand...
Click to collapse
One quick question before I flash this and trip knox. On your device was Reactivation set to ON?
I was not worried about Knox so much so did not pay attention to it. What Warranty Custom ROMs FTW
Where does it mention Reactivation ? In Download mode ?
I can check later when the misses gets home for ya
One thing I did notice is every recovery I have tried the ones that work now say "recovery not selinux enforcing" or something along those lines..(when entering recovery)
Jonny5isalivetm said:
I was not worried about Knox so much so did not pay attention to it. What Warranty Custom ROMs FTW
Where does it mention Reactivation ? In Download mode ?
I can check later when the misses gets home for ya
One thing I did notice is every recovery I have tried the ones that work now say "recovery not selinux enforcing" or something along those lines..(when entering recovery)
Click to expand...
Click to collapse
Ha ha, very true about Knox. And yes in download mode it shows if Reactivation is ON or OFF. The purpose is to not allow anyone to factory reset the device if this is turned on. Hence the unavailability of the recovery mode.
I would really appreciate it if you could check and let me know. Thanks in advance mate
OK will do but she at work till 5
Jonny5isalivetm said:
OK will do but she at work till 5
Click to expand...
Click to collapse
No worries mate, thanks for been available and the guidance...
Jonny5isalivetm said:
OK will do but she at work till 5
Click to expand...
Click to collapse
Any updates please?
I just got the phone lol soz
turns out download mode in MM has no information is there somewhere else I could find out what you need to know ?
Jonny5isalivetm said:
I just got the phone lol soz
turns out download mode in MM has no information is there somewhere else I could find out what you need to know ?
Click to expand...
Click to collapse
Sorry for the silence on this. But I decided to hand over the device for warranty claim. At no point I did trip Knox so they accepted for warranty claim process. Ideally I should get it back end of this week.
I will update you all on this matter as soon as I have more details.
MAHASONA said:
Sorry for the silence on this. But I decided to hand over the device for warranty claim. At no point I did trip Knox so they accepted for warranty claim process. Ideally I should get it back end of this week.
I will update you all on this matter as soon as I have more details.
Click to expand...
Click to collapse
hello i had the same problem after updating to marshmallow was stuck in boot loop what i did to fix it is go into recovery power home button and volume up factory reset and wipe cache rebooted phone and it worked hope it works for you
huzi7868 said:
hello i had the same problem after updating to marshmallow was stuck in boot loop what i did to fix it is go into recovery power home button and volume up factory reset and wipe cache rebooted phone and it worked hope it works for you
Click to expand...
Click to collapse
Thanks for the info. But as mentioned recovery is not available in Reactiation - ON mode. Its a security feature they provide to prevent people from stealing your phone.
Can't you disable reactivation lock by deleting your Samsung account ? : http://androiding.how/unable-to-disable-reactivation-lock-on-galaxy-s6-try-this-fail-safe-trick/

Wanting to Flash my Note 20 Ultra and I don't know where to start...

I've never flashed a cellphone and I don't even know if I can flash this one. I bought the phone through and when I was still with Sprint. I was told flashing it might be tricky if not impossible since I bought it through a carrier and was also told to come here and ask. So that's what I am doing. Thanks for any help!
Even you haven't said what you want to flash and why (mean what you want to achieve with flashing)
SyntheticVirusZ said:
I've never flashed a cellphone and I don't even know if I can flash this one. I bought the phone through and when I was still with Sprint. I was told flashing it might be tricky if not impossible since I bought it through a carrier and was also told to come here and ask. So that's what I am doing. Thanks for any help!
Click to expand...
Click to collapse
As above, what do you want to achieve by flashing it, and what do you want to flash to it?
dr.ketan said:
Even you haven't said what you want to flash and why (mean what you want to achieve with flashing)
Click to expand...
Click to collapse
*Detection* said:
As above, what do you want to achieve by flashing it, and what do you want to flash to it?
Click to expand...
Click to collapse
I'm sorry. It was a little late at night and I was trying to put the child down for sleep and was in a hurry. But I'm looking to just flash a stock ROM to get the vendors (Sprint) pre-installed apps off the phone. So I'm not looking to do anything to fancy.
Try flashing non vendor specific rom. But before that simply keep copy of rom which is installed currently, so in case something went wrong, you can restore it.
You can download stock firmware with friza or Sam firmware tool (little search over xda you can find it)
Okay, so I used Frija to get the file and now I'm using Odin to flash it. I have the BL, Ap, Cp, CSC, and USERDATA files. Only issue I have is I have two CSC files and I'm not sure which one to use? One is called HOME_CSC_OMC_OYN_N986UOYN1DUB5_CL20936746_QB38027387_REV00_user_low_ship_MULTI_CERT.tar.md5 and the other is CSC_OMC_OYN_N986UOYN1DUB5_CL20936746_QB38027387_REV00_user_low_ship_MULTI_CERT.tar.md5. I want to say it's the second one I mentioned but I want to make sure.
Home_CSC* won't delete your data while CSC_* will do.
dr.ketan said:
Home_CSC* won't delete your data while CSC_* will do.
Click to expand...
Click to collapse
What data is the Home file saving? Also what's the USERDATA file?
All other data that you have addled other than factory set.
Some apps install as non system, that known as userdata
Okay, Odin said it passed and my phone restarted to a Android Recovery section giving me a ton of options and now I'm nervous... The options are.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory rest
Wipe cache partition
Mount /system
View recovery logs
Run graphics test
Run locale test
Power off
Repair apps
Do I just want to reboot it?
Okay so I restarted it and the phone works, but everything is still the same. If I do a factory restore will that remove Sprint's apps? Or should I redo the process without adding the CSC and USERDATA files?
Sorry for bumping this but does anybody know the answer to my question?
SyntheticVirusZ said:
Sorry for bumping this but does anybody know the answer to my question?
Click to expand...
Click to collapse
From what I remember once you flash an unlocked firmware (ie. Not carrier branded) you need to factory reset to remove the carrier stuff from the old firmware
But don't quote me on it, just what I remember reading from others threads, I've not had to try it myself
*Detection* said:
From what I remember once you flash an unlocked firmware (ie. Not carrier branded) you need to factory reset to remove the carrier stuff from the old firmware
But don't quote me on it, just what I remember reading from others threads, I've not had to try it myself
Click to expand...
Click to collapse
Sounds good. I'll try it when I get home later and am more prepared and report back. Thanks for the help so far everyone!
SyntheticVirusZ said:
Sounds good. I'll try it when I get home later and am more prepared and report back. Thanks for the help so far everyone!
Click to expand...
Click to collapse
You can kill 2 birds by using CSC instead of HOME_CSC when you flash the firmware, that initiates a factory reset after the flash (ie. Clean install)
*Detection* said:
You can kill 2 birds by using CSC instead of HOME_CSC when you flash the firmware, that initiates a factory reset after the flash (ie. Clean install)
Click to expand...
Click to collapse
Actually I might just do that then tonight.
Unfortunately, it didn't work... Not sure if I did something wrong but Sprint's app's are still on there.
SyntheticVirusZ said:
Unfortunately, it didn't work... Not sure if I did something wrong but Sprint's app's are still on there.
Click to expand...
Click to collapse
Which ROM you have downloaded?
If you are flashing same sprint then it will always remain there. Make sure you are flashing unbranded firmware.
dr.ketan said:
Which ROM you have downloaded?
If you are flashing same sprint then it will always remain there. Make sure you are flashing unbranded firmware.
Click to expand...
Click to collapse
I'm using the one I got through following the instructions using Frija.
What information you have added to friza whie searching ROM? specially CSC

Categories

Resources