I am hoping someone can help me because I have run out of ideas. I had Candy5 5.1.1 rom on my Tab2 10.1 and it was working for a while with intermittent reboots. Then it suddenly would reboot after just a few seconds. Nothing I have tried has worked, including:
1) a hard reset-I have tried wiping and resetting from CWM and from the settings but when I reboot it nothing is wiped or reset.
2) installing a new rom- I have tried installing multiple other roms from both the SD card, the internal sd card, and odin. They flash successfully but when I reboot I am right back to Candy5 and the reboot loop after a few seconds.
3) using odin-I have tried using oding to flash stock firmware, custom firmware, and a new recovery. Odin will say FAIL for the stock firmware, but for the others it will say PASS but there is still the same CWM and Candy5.
4) Sideloading- same results as above
5) installing a new recovery from SD card-nope.
6)Using ADB and fastboot-Fastboot will not recognize my device even though I have the correct drivers installed--I have also tried all the USB ports available with no change. ADB won't recognize my device for a wipe, but it will for installing another custom rom or recovery which of course does not work.
7) A few times I have had time before it reboots to try uninstalling apps. It tells me they are uninstalled but when I reboot they are back.
8) Also when it stayed I tried going into superuser settings to reset them but even though it says they are reset nothing happens after reboot.
A couple things to note:
1) it is a p5113 but has a p5110 rom and identifies itself as p5110 in download mode. This however, has not been a problem before.
2) I am running Clockworkmod Recovery v6.0.2.3
3)When I try to exit recovery I get the error message "Root access possibly lost. Fix?" and then the Yes response is "Yes-Fix root (/system/xbin/su). If I choose yes, though, it does nothing and simply reboots. Same if I choose no.
4) gapps are installed and I am certain I installed the correct version of these.
Thank you for any help you can give me. It's an old tablet but I have gotten a lot of great use from it until now!
Insight67 said:
I am hoping someone can help me because I have run out of ideas. I had Candy5 5.1.1 rom on my Tab2 10.1 and it was working for a while with intermittent reboots. Then it suddenly would reboot after just a few seconds. Nothing I have tried has worked, including:
1) a hard reset-I have tried wiping and resetting from CWM and from the settings but when I reboot it nothing is wiped or reset.
2) installing a new rom- I have tried installing multiple other roms from both the SD card, the internal sd card, and odin. They flash successfully but when I reboot I am right back to Candy5 and the reboot loop after a few seconds.
3) using odin-I have tried using oding to flash stock firmware, custom firmware, and a new recovery. Odin will say FAIL for the stock firmware, but for the others it will say PASS but there is still the same CWM and Candy5.
4) Sideloading- same results as above
5) installing a new recovery from SD card-nope.
6)Using ADB and fastboot-Fastboot will not recognize my device even though I have the correct drivers installed--I have also tried all the USB ports available with no change. ADB won't recognize my device for a wipe, but it will for installing another custom rom or recovery which of course does not work.
7) A few times I have had time before it reboots to try uninstalling apps. It tells me they are uninstalled but when I reboot they are back.
8) Also when it stayed I tried going into superuser settings to reset them but even though it says they are reset nothing happens after reboot.
A couple things to note:
1) it is a p5113 but has a p5110 rom and identifies itself as p5110 in download mode. This however, has not been a problem before.
2) I am running Clockworkmod Recovery v6.0.2.3
3)When I try to exit recovery I get the error message "Root access possibly lost. Fix?" and then the Yes response is "Yes-Fix root (/system/xbin/su). If I choose yes, though, it does nothing and simply reboots. Same if I choose no.
4) gapps are installed and I am certain I installed the correct version of these.
Thank you for any help you can give me. It's an old tablet but I have gotten a lot of great use from it until now!
Click to expand...
Click to collapse
Have you tried TWRP recovery from odin? use android-andi's or try from flashify app from your tab? I think you have done most of the things that needed to be done. the only thing left after this is try flash stock firmware with a pit file. but then if you have some other things as well to try.
it's not a regular bug, it's quiet strange, your candy rom tab looks like invincible here, or maybe the emmc has become read-only?(how on earth that happened??)
billysam said:
Have you tried TWRP recovery from odin? use android-andi's or try from flashify app from your tab? I think you have done most of the things that needed to be done. the only thing left after this is try flash stock firmware with a pit file. but then if you have some other things as well to try.
it's not a regular bug, it's quiet strange, your candy rom tab looks like invincible here, or maybe the emmc has become read-only?(how on earth that happened??)
Click to expand...
Click to collapse
Hi billysam, thanks for the response. I did try TWRP both as a zip install from the external sdcard and a sideload, as well as odin. They all tell me it was successfully installed but when I boot directly into recovery (if I did the auto reboot option I would go straight into the candy rom), I am back at CWM. I also tried the stock firmware with pit which fails during the factoryfs part.
I am not able to install any apps. If there is enough time before reboot, the app says it installed but when I reboot it is not there.
It does seem like the hard drive is read-only, or at least something is preventing me from writing to the disc.
Insight67 said:
Hi billysam, thanks for the response. I did try TWRP both as a zip install from the external sdcard and a sideload, as well as odin. They all tell me it was successfully installed but when I boot directly into recovery (if I did the auto reboot option I would go straight into the candy rom), I am back at CWM. I also tried the stock firmware with pit which fails during the factoryfs part.
I am not able to install any apps. If there is enough time before reboot, the app says it installed but when I reboot it is not there.
It does seem like the hard drive is read-only, or at least something is preventing me from writing to the disc.
Click to expand...
Click to collapse
Was the tab encrypted?
Can you get logs?
Well it's going to be a case study since I too can't find anything that could come close to your tab issue.
billysam said:
Was the tab encrypted?
Can you get logs?
Well it's going to be a case study since I too can't find anything that could come close to your tab issue.
Click to expand...
Click to collapse
It was not encrypted.
When I try to access the logs, this is what I get:
ClockworkMod Recovery v6.0.2.3
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
I Can't partition non-vfat: datamedia
I: Can't format unknown volume: /emmc
Thanks again!
When in recovery, flash twrp. Then reboot recovery. It should go to twrp then. I think your issue is recovery related.
Sent from my GT-P5110 using Tapatalk
Insight67 said:
It was not encrypted.
When I try to access the logs, this is what I get:
ClockworkMod Recovery v6.0.2.3
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
I Can't partition non-vfat: datamedia
I: Can't format unknown volume: /emmc
Thanks again!
Click to expand...
Click to collapse
Looks like a emmc issue my friend. I am afraid anything else going to work than replacing emmc.
The only reason I see here is that your tab emmc is somehow corrupted or there is bad sectors. That has virtually turned the tab into a read only and can't even read certain parts. No kind of flashing can do this to a tab. A virus attacked and is not letting you do it? Chances are no. Cause no virus can let you stop flashing from odin.
Correct Stock firmwares and pit file failed too at factoryfs part. sure you got the right files?
My suspect - the dreaded emmc issue of tab 10.1
Well do post if you find anything else.
Good luck
homephysician said:
When in recovery, flash twrp. Then reboot recovery. It should go to twrp then. I think your issue is recovery related.
Sent from my GT-P5110 using Tapatalk
Click to expand...
Click to collapse
Thank you for replying. I have tried that, but TWRP will not install. I am unable to install anything unfortunately.
billysam said:
Looks like a emmc issue my friend. I am afraid anything else going to work than replacing emmc.
The only reason I see here is that your tab emmc is somehow corrupted or there is bad sectors. That has virtually turned the tab into a read only and can't even read certain parts. No kind of flashing can do this to a tab. A virus attacked and is not letting you do it? Chances are no. Cause no virus can let you stop flashing from odin.
Correct Stock firmwares and pit file failed too at factoryfs part. sure you got the right files?
My suspect - the dreaded emmc issue of tab 10.1
Well do post if you find anything else.
Good luck
Click to expand...
Click to collapse
Yeah, I figures it might be that. It makes sense as to why I can't install anything and why fastboot won't recognize the device. My confusion was that my laptop does recognize it as at p5110 device and I can access the drive and it's folders on my laptop. I just can't delete anything. I don't know of any viruses and I had only a few select video streaming apps on it. I tried the p5110 and the p5113 from sam mobile so if you know of any other stock firmware links or toolkits I would love to try them. I hate to get rid of a tablet that isn't really bricked.
Insight67 said:
I hate to get rid of a tablet that isn't really bricked.
Click to expand...
Click to collapse
Same feeling goes here but wait, it does connect to your laptop and you can access files from it! You can transfer new files on it? And does it stay even after reboot?
Well I am looking for a new way out here, something that hasn't been tried on our devices to recover a tab from a difficult situation, a different approach. But will need help from our community. I will share that on a new thread once I am done researching myself. But sadly I have a P5100. But we will see what can be done.
billysam said:
Same feeling goes here but wait, it does connect to your laptop and you can access files from it! You can transfer new files on it? And does it stay even after reboot?
Well I am looking for a new way out here, something that hasn't been tried on our devices to recover a tab from a difficult situation, a different approach. But will need help from our community. I will share that on a new thread once I am done researching myself. But sadly I have a P5100. But we will see what can be done.
Click to expand...
Click to collapse
Well, it's a bit stranger than that. My laptop recognizes it as a p5110 and I can go into the files. I can even (if it doesn't immediately start rebooting) delete folders. But, when I reboot, the folders are back as if they were never deleted.
I was also able to sideload a rom onto my sdcard (not external sd) and it tells me install is complete. But nothing changes.
This is what I am getting when I install, which makes me think there is a piece of the factory firmware that is still around interfering with the custom rom:
Installing update....
Warning: No file_contextsdetected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
Then after the logo of the rom:
(*) Running backup scripts...
detected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
(*) Done.
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
unmount of /system failed: no such volume
script succeeded: result was [ ]
Install from sd card complete
Thank you again for your help. If I figure anything else out I will post as well in case anyone else has this issue.
Insight67 said:
Well, it's a bit stranger than that. My laptop recognizes it as a p5110 and I can go into the files. I can even (if it doesn't immediately start rebooting) delete folders. But, when I reboot, the folders are back as if they were never deleted.
I was also able to sideload a rom onto my sdcard (not external sd) and it tells me install is complete. But nothing changes.
This is what I am getting when I install, which makes me think there is a piece of the factory firmware that is still around interfering with the custom rom:
Installing update....
Warning: No file_contextsdetected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
Then after the logo of the rom:
(*) Running backup scripts...
detected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
(*) Done.
Patching system image unconditionally...
detected filesystem ext4 for /dev/block/platform/omap/omap)hsmmc.1/by-name/FACTORYFS
unmount of /system failed: no such volume
script succeeded: result was [ ]
Install from sd card complete
Thank you again for your help. If I figure anything else out I will post as well in case anyone else has this issue.
Click to expand...
Click to collapse
it's the same message that I get while installing a custom rom. but mine does write it on the system and it did change my rom.
Okay, we should concentrate on the firmware file that should flash through odin without fail.
why is it not flashing it, while others are getting flashed?
You did download it from sam mobile, that's the best place to get it.
pit file, is almost identical for all the p51xx 16gb variant, I was going through the same right now. so no chance of getting wrong pit partitioned. (by any chance, you ever flashed a different pit file on your tab?)
try to flash on a different pc/laptop? download stock firmware again, this is your best bet. any other options are just beating around bushes.
billysam said:
it's the same message that I get while installing a custom rom. but mine does write it on the system and it did change my rom.
Okay, we should concentrate on the firmware file that should flash through odin without fail.
why is it not flashing it, while others are getting flashed?
You did download it from sam mobile, that's the best place to get it.
pit file, is almost identical for all all the p51xx, I was going through the same right now. so no chance of getting wrong pit partitioned.
try to flash on a different pc/laptop? download stock firmware again, this is your best bet. any other options are just beating around bushes.
Click to expand...
Click to collapse
That is a good idea. I have been using the same laptop for all of this. I will try a different PC and let you know how it goes.
Thanks again!!
billysam said:
it's the same message that I get while installing a custom rom. but mine does write it on the system and it did change my rom.
Okay, we should concentrate on the firmware file that should flash through odin without fail.
why is it not flashing it, while others are getting flashed?
You did download it from sam mobile, that's the best place to get it.
pit file, is almost identical for all the p51xx 16gb variant, I was going through the same right now. so no chance of getting wrong pit partitioned. (by any chance, you ever flashed a different pit file on your tab?)
try to flash on a different pc/laptop? download stock firmware again, this is your best bet. any other options are just beating around bushes.
Click to expand...
Click to collapse
I tried a different computer but still got the fail from odin. If I come up with anything that works I'll be sure to post it. Thanks for all your help!
Just a shot in the dark, but did not see "Factory reset" mentioned.
Nobody wants to hear that but sometimes it's the only solution.
Pp.
PanchoPlanet said:
Just a shot in the dark, but did not see "Factory reset" mentioned.
Nobody wants to hear that but sometimes it's the only solution.
Pp.
Click to expand...
Click to collapse
Oh, yes, tried that numerous times. It won't reset. Thanks for the reply, though!
Insight67 said:
Oh, yes, tried that numerous times. It won't reset. Thanks for the reply, though!
Click to expand...
Click to collapse
http://wiki.cyanogenmod.org/w/EMMC_Bugs
Found it. That explains all.
billysam said:
http://wiki.cyanogenmod.org/w/EMMC_Bugs
Found it. That explains all.
Click to expand...
Click to collapse
Thanks billysam! If I am reading this correctly, only replacing the motherboard would work.
Insight67 said:
Thanks billysam! If I am reading this correctly, only replacing the motherboard would work.
Click to expand...
Click to collapse
Yes, according to that post. For me, I don't know because I haven't faced it myself, for you, you can try the options between changing emmc or changing motherboard or replacing a new tab or Jtag. Of course Whatever the technical guys you take your tab to for repair and which doesn't cost you much. Although people said changing emmc or jtag won't work. But you never know until tried. Also I won't suggest you try yourself. Good luck. It was good learning experience here.
billysam said:
Yes, according to that post. For me, I don't know because I haven't faced it myself, for you, you can try the options between changing emmc or changing motherboard or replacing a new tab or Jtag. Of course Whatever the technical guys you take your tab to for repair and which doesn't cost you much. Although people said changing emmc or jtag won't work. But you never know until tried. Also I won't suggest you try yourself. Good luck. It was good learning experience here.
Click to expand...
Click to collapse
Thank you!
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
Hi,
since this morning I have this problem that my Nexus S just boots until the Google logo appears.
I have no idea what caused this. I was just reinstalling the youtube app and rebooted after that and it booted.
Then I noticed that my phone would not change the screen orientation and because it worked in the past I started another reboot. But then it got stuck at the Google logo.
To solve this problem I just wanted to flash my nandroid backup but that didn't work as well cause the recovery was not able to mount the sdcard.
E:Can't mount /sdcard
Does anyone have an idea how to solve this problem? By the way is it possible to pull the Nandroid backup from the phone to my computer with ADB for example. Would be great because (of course) I just have an backup on my phone... (but if not... well, **** happens)
Thanks in advance!
PedroBustamonte said:
Hi,
since this morning I have this problem that my Nexus S just boots until the Google logo appears.
I have no idea what caused this. I was just reinstalling the youtube app and rebooted after that and it booted.
Then I noticed that my phone would not change the screen orientation and because it worked in the past I started another reboot. But then it got stuck at the Google logo.
To solve this problem I just wanted to flash my nandroid backup but that didn't work as well cause the recovery was not able to mount the sdcard.
E:Can't mount /sdcard
Does anyone have an idea how to solve this problem? By the way is it possible to pull the Nandroid backup from the phone to my computer with ADB for example. Would be great because (of course) I just have an backup on my phone... (but if not... well, **** happens)
Thanks in advance!
Click to expand...
Click to collapse
flasgh stock via fastboot and wipe everything DONE!
i had this problem when i flashed a non-cm kernel on a cm-based rom. try flashing a different kernel. know what kernel your rom is compatible to,
Cascabreu said:
flasgh stock via fastboot and wipe everything DONE!
Click to expand...
Click to collapse
So there's no way to get the content of the sdcard before I wipe everything?
ej8989 said:
i had this problem when i flashed a non-cm kernel on a cm-based rom. try flashing a different kernel. know what kernel your rom is compatible to,
Click to expand...
Click to collapse
I'm using ParanoidAndroid with Mamite (the version for cm based roms since PA is also based on cm)
PedroBustamonte said:
So there's no way to get the content of the sdcard before I wipe everything?
I'm using ParanoidAndroid with Mamite (the version for cm based roms since PA is also based on cm)
Click to expand...
Click to collapse
Go to mounts and storage in CWM Recovery and "mount usb storage". That will let you get to your SD card to backup. Then I suggest just a clean wipe and start over.
Note: mount /sdcard just mounts it to the phone. You are wanting to mount it to your computer to pull the files off the external.
mdean1981 said:
Go to mounts and storage in CWM Recovery and "mount usb storage". That will let you get to your SD card to backup. Then I suggest just a clean wipe and start over.
Note: mount /sdcard just mounts it to the phone. You are wanting to mount it to your computer to pull the files off the external.
Click to expand...
Click to collapse
Yup thank you. Already tried that and a lot of other stuff. Seems like my phone's broken. I can't write on or erase /system or /sdcard. I'll try today to lock the bootloader and then unlock it. Maybe that solves the problem...
It will also wipe everything if I remember well
Envoyé depuis mon Nexus S avec Tapatalk
PedroBustamonte said:
Yup thank you. Already tried that and a lot of other stuff. Seems like my phone's broken. I can't write on or erase /system or /sdcard. I'll try today to lock the bootloader and then unlock it. Maybe that solves the problem...
Click to expand...
Click to collapse
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue
Cascabreu said:
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue
Click to expand...
Click to collapse
Yes you're right. But I really can't think of any thing I could try.
PedroBustamonte said:
Yes you're right. But I really can't think of any thing I could try.
Click to expand...
Click to collapse
It's interesting and maybe fortuite that this is happening to you just as something almost equal happens to me (see here: http://forum.xda-developers.com/showthread.php?t=1972447 ) You should also enter the recovery via adb from your computer if you have it, and check if a) you have mmc* files in /dev/block and b) have mmc error messages in dmesg (in the phone: "dmesg|grep mmc" and look for lines with "error" in them).
Btw to the person who suggested flashing stock thorough fastboot, do you mean stock system, system+boot or system+boot+recovery ? and where could I find those stock .img please? Mine's an i9020a
Blissfull said:
It's interesting and maybe fortuite that this is happening to you just as something almost equal happens to me (see here: http://forum.xda-developers.com/showthread.php?t=1972447 ) You should also enter the recovery via adb from your computer if you have it, and check if a) you have mmc* files in /dev/block and b) have mmc error messages in dmesg (in the phone: "dmesg|grep mmc" and look for lines with "error" in them).
Btw to the person who suggested flashing stock thorough fastboot, do you mean stock system, system+boot or system+boot+recovery ? and where could I find those stock .img please? Mine's an i9020a
Click to expand...
Click to collapse
Factory Images for Nexus Devices
https://developers.google.com/android/nexus/images
Hi ^^
I had the same problem with my Nexus S a long time ago and never found out how to solve it. It seems that the internal memory is corrupted and nothing but replacing the motherboard can solve it. Since I bought mine in the USA but I live in Belgium I never got mine repaired. Sometimes I come back here to see if there is still no solution but each time I'm disappointed...
Sorry.
PedroBustamonte said:
Yes you're right. But I really can't think of any thing I could try.
Click to expand...
Click to collapse
Cascabreu said:
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue
Click to expand...
Click to collapse
I can confirm this. I had the same thing happen to my Nexus S 4G recently. I was never able to salvage any data off the sdcard no matter what I tried (various mounting attempts in recovery, any adb command I thought might be helpful, etc.). As a last resort I tried to lock/unlock the bootloader - once I locked it, I was unable to unlock it again, it just froze up after asking me if I was sure I wanted to unlock. I guess that's what happens when the internal sdcard goes to hell. I ended up taking it to my local Sprint store and they replaced the phone with a refurbished one from Samsung (for approximately $35).
I received a Galaxy Note 1 I717 (AT&T) and it was in a bootloop. I have experience with flashing stock roms through Odin and fixing bootloops that way. So after going through recovery mode, wiping, flashing, I am still getting put into a bootloop after a successful flash on Odin. I've spent 2 days with this and tried all the little suggestions of wiping before flashing, using the original roms from XDA , trying some other stock roms specifically for my model and I'm still left with a bootloop. I'm capable of getting into download and recovery, and I've actually gotten different stock recovery modes! So the flashes are working, but it just won't boot up correctly. I looked around for the U.S. version of the Pit CSC Phone and PDA to try and re partition it, but they are absolutely NOWHERE! Any help would be greatly appreciated, whether it's a ROM suggestion, the re partition files, or whatever else.
Charles Sparkley said:
I received a Galaxy Note 1 I717 (AT&T) and it was in a bootloop. I have experience with flashing stock roms through Odin and fixing bootloops that way. So after going through recovery mode, wiping, flashing, I am still getting put into a bootloop after a successful flash on Odin. I've spent 2 days with this and tried all the little suggestions of wiping before flashing, using the original roms from XDA , trying some other stock roms specifically for my model and I'm still left with a bootloop. I'm capable of getting into download and recovery, and I've actually gotten different stock recovery modes! So the flashes are working, but it just won't boot up correctly. I looked around for the U.S. version of the Pit CSC Phone and PDA to try and re partition it, but they are absolutely NOWHERE! Any help would be greatly appreciated, whether it's a ROM suggestion, the re partition files, or whatever else.
Click to expand...
Click to collapse
A bad kernel can be the cause of this problem. Try and search for a custom kernel for your device and flash it.
I hope this will solve your problem.
Ibrahim9999 said:
A bad kernel can be the cause of this problem. Try and search for a custom kernel for your device and flash it.
I hope this will solve your problem.
Click to expand...
Click to collapse
I already tried flashing the stock Rom then flashed the kernel and got boot loops still from this XDA page http://forum.xda-developers.com/showthread.php?t=1506330 . Having a lot of trouble with this one.
Charles Sparkley said:
I already tried flashing the stock Rom then flashed the kernel and got boot loops still from this XDA page http://forum.xda-developers.com/showthread.php?t=1506330 . Having a lot of trouble with this one.
Click to expand...
Click to collapse
OK, download these files and put them on your device:
Rom: http://goo.gl/81TamM
Gapps (important!): http://goo.gl/ws5KZF
Then follow these steps exactly:
1. Boot to recovery (CWM or whatever you use)
2. Wipe data/factory reset
3. Wipe Cache
4. Wipe Dalvik cache (advanced-> wipe dalvik cache)
5. Flash rom
7. Flash the gapps
This must work, if it doesn't, please say it, maybe I can help you further.
Ibrahim9999 said:
OK, download these files and put them on your device:
Rom: http://goo.gl/81TamM
Gapps (important!): http://goo.gl/ws5KZF
Then follow these steps exactly:
1. Boot to recovery (CWM or whatever you use)
2. Wipe data/factory reset
3. Wipe Cache
4. Wipe Dalvik cache (advanced-> wipe dalvik cache)
5. Flash rom
7. Flash the gapps
This must work, if it doesn't, please say it, maybe I can help you further.
Click to expand...
Click to collapse
My bad for not properly explaining my situation, the note is stuck in a boot loop. So I can't upload files to it through drag and drop in USB. It's still capable of flashing through Odin and going into recovery with CWM, but there's no way I know of putting files onto a boot looping phone.
Charles Sparkley said:
My bad for not properly explaining my situation, the note is stuck in a boot loop. So I can't upload files to it through drag and drop in USB. It's still capable of flashing through Odin and going into recovery with CWM, but there's no way I know of putting files onto a boot looping phone.
Click to expand...
Click to collapse
Doesn't the Galaxy Note 1 I717 has a MicroSD-Card Slot?
I tought it had one..
Ibrahim9999 said:
Doesn't the Galaxy Note 1 I717 has a MicroSD-Card Slot?
I tought it had one..
Click to expand...
Click to collapse
Oh it does, would I just put those files onto a good sd card via a working phone and THEN put it into the Note?
Charles Sparkley said:
Oh it does, would I just put those files onto a good sd card via a working phone and THEN put it into the Note?
Click to expand...
Click to collapse
Yes of course, or put the files with a computer on the SDCard.
If you've put the files onto the SDCard, insert it to your Note, and follow the steps on my previous post.
Charles Sparkley said:
Oh it does, would I just put those files onto a good sd card via a working phone and THEN put it into the Note?
Click to expand...
Click to collapse
Did it work?
Ibrahim9999 said:
Did it work?
Click to expand...
Click to collapse
Just got an extra SD card my friend is letting me borrow. I'm going home tonight, putting the files on, and going to try to flash it. I'll tell you how it goes!
Charles Sparkley said:
Just got an extra SD card my friend is letting me borrow. I'm going home tonight, putting the files on, and going to try to flash it. I'll tell you how it goes!
Click to expand...
Click to collapse
OK, hope the best for you!
Ibrahim9999 said:
OK, hope the best for you!
Click to expand...
Click to collapse
Alright, so on my good phone I threw the 2 zips on my extra SD card. Then I put that SD card in the note, went into CWM, wiped the necessary areas as you said, and the dead android with a red triangle appeared. It's a long error, but the end says Error in /sdcard/cm-10.1.3-quincyatt.zip
(Status 7)
Installation aborted.
Are you sure you gave me the right ROM to install?
Charles Sparkley said:
Alright, so on my good phone I threw the 2 zips on my extra SD card. Then I put that SD card in the note, went into CWM, wiped the necessary areas as you said, and the dead android with a red triangle appeared. It's a long error, but the end says Error in /sdcard/cm-10.1.3-quincyatt.zip
(Status 7)
Installation aborted.
Are you sure you gave me the right ROM to install?
Click to expand...
Click to collapse
Status 7 means the device is incompatible, but that's impossible since we have the right ROM for your device.
OK just be sure, I'll give you another ROM and you must follow the other steps, but with the different files of course.
ROM: http://downloadandroidrom.com/file/...CARBON-JB-NIGHTLY-20131015-0513-quincyatt.zip
Google Apps: http://downloadandroidrom.com/file/gapps/gapps-jb-20130813-signed.zip
This is an Android 4.3.1 ROM so you're really up to date with this one.
Put these on a SD Card and follow the given steps in my other post.
This one has to work.
Ibrahim9999 said:
Status 7 means the device is incompatible, but that's impossible since we have the right ROM for your device.
OK just be sure, I'll give you another ROM and you must follow the other steps, but with the different files of course.
ROM: http://downloadandroidrom.com/file/...CARBON-JB-NIGHTLY-20131015-0513-quincyatt.zip
Google Apps: http://downloadandroidrom.com/file/gapps/gapps-jb-20130813-signed.zip
This is an Android 4.3.1 ROM so you're really up to date with this one.
Put these on a SD Card and follow the given steps in my other post.
This one has to work.
Click to expand...
Click to collapse
Hate to say it, but installed the new ROM file and got the same exact message. Right now I'm on CWM-based Recovery v5.5.0.4 and I flashed to stock before this, thanks for all of the help so far. Any suggestions?
Charles Sparkley said:
Hate to say it, but installed the new ROM file and got the same exact message. Right now I'm on CWM-based Recovery v5.5.0.4 and I flashed to stock before this, thanks for all of the help so far. Any suggestions?
Click to expand...
Click to collapse
Do you know for sure you're on a Galaxy Note i717 AT&T?
Because 2 roms incompatible is almost impossible.
Ibrahim9999 said:
Do you know for sure you're on a Galaxy Note i717 AT&T?
Because 2 roms incompatible is almost impossible.
Click to expand...
Click to collapse
Sorry for not getting back in a while, thanks for all the effort you've been putting into helping out.
I'm 100% positive, I'm looking at the back below where the battery goes and it says SGH-I717. I thought that model number meant for sure it was AT&T. I live in the states also if that helps.
Charles Sparkley said:
Sorry for not getting back in a while, thanks for all the effort you've been putting into helping out.
I'm 100% positive, I'm looking at the back below where the battery goes and it says SGH-I717. I thought that model number meant for sure it was AT&T. I live in the states also if that helps.
Click to expand...
Click to collapse
But don't you think it's maybe a Chinese replica with a different kernel?
If you got it cheap, that might be the case.
And can you please thank my posts?
Because the few clicks you do, help me a lot
Ibrahim9999 said:
But don't you think it's maybe a Chinese replica with a different kernel?
If you got it cheap, that might be the case.
And can you please thank my posts?
Because the few clicks you do, help me a lot
Click to expand...
Click to collapse
No it was definitely bought in the US, legit from a phone store.
Charles Sparkley said:
No it was definitely bought in the US, legit from a phone store.
Click to expand...
Click to collapse
So, for my understanding, you bought it new from the store and rooted it and then got in a bootloop?
Can you please tell me how you came in the bootloop, did you get it with flashing a ROM or a kernel etc.?
Ibrahim9999 said:
So, for my understanding, you bought it new from the store and rooted it and then got in a bootloop?
Can you please tell me how you came in the bootloop, did you get it with flashing a ROM or a kernel etc.?
Click to expand...
Click to collapse
I bought it from a friend because they had it in a boot loop. Everything on it was completely stock since they were your average user, I'm pretty sure this isn't a hardware issue either if that helps because randomly after flashing CWM one time it actually booted up and I was able to use the phone. But after rebooting, it bootlooped again :\. I haven't been able to replicate this again sadly.
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.