Hello,
Due to the 10 post threshold I am unable to post in the "Samsung Captivate -
Captivate Android Development
[Guide] Encryption Unsuccessful - Reset Android [ICS Issue]" thread.
I have resolved this issue a couple months back.
So, due to the time that has gone by it is a little difficult to explain what I did.
Last night I reproduced the issue, but after a restore, I'm good as new.
So now I am compelled to post this here. Being a "noob" and like I said not able to completely remember what "exactly" was done to accomplish the fix.
I am willing to share any information you wish.
But in a nutshell, I flashed ( a ROM I can't remember at the moment, but I'm sure I will once I get down to it. at work and pressed for time, "lunch time" ) using Heimdall, then downloaded the rom "Imfinitum-blue-v1.1.0 to my external SD, ( using a 34 Gb SD card, seems that is the only card that I could use. From what I remember anyway. ) Mod version "aokp_galaxysmtd_milestone-4"
The kernel version currently being utilized on this device is "[email protected] #1.
Sorry for being so confusing, and vague, but I really wanted to get something out there. I see they are still working on a fix for this issue, I found this resolve before page 30, it's now at 57, and after recreating the issue and then resolving it after a restore.
So, ask any question you want and I will be happy to help.
Hope this helps.
Take care.
By "fixed" do you mean:
a) You have restored access to your INTERNAL sdcard?
b) You have used the emmc/sdcard swap method to use your external as the internal? (ie. your internal sdcard is still not useable)
It would help if you could mention whether your internal card is back in play. And esp. if you were able to access the data that was on there - ie. before you experienced the EU issue.
Or did using Heimdall wipe the internal sdcard - ie. yet you're now able to use the internal though?
Hello,
Because this would save a lot of people's phones including mine, would be great if you post your steps so we can follow.
Take this with a grain of salt guys.
There is very little information in his post, which is his very first post. There is also no information about the process he used. I'm not sure what a 34gb SD card is. I believe the methods he alludes to have been tried by other members with no resolution.
I have a feeling he had a different issue or is just trying to get attention.
For all our sakes I hope I'm just rushing to judgement.
I guess what we want to know is, what have you done?
Say you just got the Enc Unsuccessful screen, turned off the phone and then what?
He's to shy to give anymore details.
Sent from my SGH-I897 using xda premium
yosup said:
By "fixed" do you mean:
a) You have restored access to your INTERNAL sdcard?
b) You have used the emmc/sdcard swap method to use your external as the internal? (ie. your internal sdcard is still not useable)
It would help if you could mention whether your internal card is back in play. And esp. if you were able to access the data that was on there - ie. before you experienced the EU issue.
Or did using Heimdall wipe the internal sdcard - ie. yet you're now able to use the internal though?
Click to expand...
Click to collapse
I just duplicated the issue again, "no sdcard found"..etc... then using did a restore ("Semaphore CWM Recovery v5.5.0.4" by the way) restored the Captivate right back. After it boots I get "prepairing sdcard" then everything is back to normal.
Answer to "a." Yes, full access to both External and Internal drives. Also can mount and unmount all /system, /cache, /datadata, /sdcard, /data, /emmc.
Answer to "b." Sorry, can you elaborate on this. I'm just now sure what you mean by "swap"
You said: "It would help if you could mention whether your internal card is back in play. And esp. if you were able to access the data that was on there - ie. before you experienced the EU issue."
Now here it's difficult to say, I formatted and haphazardly (sorry, dumb I know!) flashed so many times attempting to get back control of this thing, I don't know. Google will restore my apps like before but I disabled this function. However it will detect application updates same 5 updated every time I restore it.
You said: "Or did using Heimdall wipe the internal sdcard - ie. yet you're now able to use the internal though?"
Damn!, I'm just not sure, I'm really sorry but I wish I would have THOUGHT of posting HERE before YESTERDAY!...
Now is there a log file I can send out? So people can see whats going on inside this thing. Like I said so much time has gone by, and once I was able to get the camera working and transfer apps to the external card, and all that I basically went numb and stopped messing around. And I would like to point out, that
"Encryption Unsuccessful" crap ( and knowing better, I DID press Restart by the way) started just a couple days before this thread started. So just to give you an example as to how long this frustration was. I became obsessed, I worked on this phone for most all my waking hours, and I'm sure some of you have, "dreamed" of possible fixes as well!.
If it wasn't for the 10 post threshold I could have been more help. I read every single post in this thread up to the point where I fixed the problem.
Had it all in my head at the time but when I found I couldn't post with-in the >>Encryption Unsuccessful<< thread?! I wasn't sure why.
I even started a separate identity ( Barney Fyfe ) thinking that would allow me to post something.
And from what I read at the time, I thought, rather understood it to mean that I was locked out by some Admin here... Or ?!
Sorry, really, I did not realize I had to get 10 or more posts >>here<<
You know I'm sure I can get details on pretty much exactly what I did. Right now I'm at work, so I'll need a little more time.
Wdustin1 said:
He's to shy to give anymore details.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
No just very busy. I just posted this yesterday!?
Wadda' ya want from me eh!?..............
swayjd said:
I guess what we want to know is, what have you done?
Say you just got the Enc Unsuccessful screen, turned off the phone and then what?
Click to expand...
Click to collapse
Read my first reply.
I did so much to find a resolve, none of the suggestions I tried in the "Encryption Unsuccessful" thread worked at all by the way. didn't attempt EVERY suggestion, but a lot of them.
I'm going to attempt to get the horrifying memories back!
Oh, now here is an odd change in event, not sure if this is related or not but I just realized last night that the phone won't charge, using three different batteries, all fairly new, nor is it being recognized USB wise.
I have a couple other Captivates I'm now having to use to charge my batteries for this one.
It's like the micro usb is damaged?
I'm usually very careful on how I insert them, 4 different cables too. That all work with the other Captivate. It's bricked but does charge the battery.
It's a GT-19000.
Oh and I almost forgot!!
The Samsung Galaxy S SGH-897/Captivate I'm using is fairly new, the date code is " 1111 "
Red_81 said:
Take this with a grain of salt guys.
There is very little information in his post, which is his very first post. There is also no information about the process he used. I'm not sure what a 34gb SD card is. I believe the methods he alludes to have been tried by other members with no resolution.
I have a feeling he had a different issue or is just trying to get attention.
For all our sakes I hope I'm just rushing to judgement.
Click to expand...
Click to collapse
RELAX! I'm not playing around.
It's comments like this that kept me from being more proactive in posting in the first place!
Good lord!!
See, now you could have waited at least another day before this flaming!
Losing interest in this now. I was trying to help.
- - - - - - - - -
Hey people, my name is Pat Doherty.
Because of this dork I'm about done. I Do not NEED this kind of thing. I got my own stresses to deal with these days. And don't need some immature nerd slamming my attempt at helping out here.
I can be reached if you put anything you want in front of patdoherty dot net.
my site patdoherty dot net.
c'ya!
P.S.
You said:
"I'm not sure what a 34gb SD card is."
Really now!?
Are you serious!?
A SanDisk 32GB micro SD chip, "32gb" ( screen printed right on the chip ) = 32 gigabytes
Barney Fyfe said:
RELAX! I'm not playing around.
It's comments like this that kept me from being more proactive in posting in the first place!
Good lord!!
See, now you could have waited at least another day before this flaming!
Losing interest in this now. I was trying to help.
Click to expand...
Click to collapse
but dude, you gave us nothing.
please as another noob could you post exact details of your discovery? like what you did to get the inscription unsuccesful to come up repeatably,and what did you do get your phone to access the internal memory? an what exactly did you flash to get it all to work
You brought up a fix to an issue that is getting very high attention right now. You were not able to tell people how to recreate the fix. People are looking for a scientific method (think repeatable steps) to fix this issue that is affecting quite a few people.
I'm sorry if I hurt your feelings. I've been watching the Encryption Unsuccessful thread for a very long time. I was stating only what I observed. There have been others who had suggested a similar fix, but it has not been repeatable.
You are a talented artist and obviously have alot going on. I hope for others' sake you can give them some steps to follow. If so, you may just be the "chosen one"
Barney Fyfe said:
It's comments like this that kept me from being more proactive in posting in the first place!
Losing interest in this now. I was trying to help.
Click to expand...
Click to collapse
First of all, I'll commend you for sharing a positive outcome despite experiencing this dreaded issue. However, this is something being dicussed at the DEV thread level, which assumes a deeper level of detail than the average General or Q&A topic.
Serious people are giving serious consideration to the matter. Example, Woodrube is a well respected Vibrant / Transformer / Nook user, and he's invested a lot of time collaborating with Captivate users to pool our resources and build our knowledgebase here.
Whether you continue your participation is up to you. Hopefully your method will be a viable part of the discussion.
Barney Fyfe said:
I did so much to find a resolve, none of the suggestions I tried in the "Encryption Unsuccessful" thread worked at all by the way. didn't attempt EVERY suggestion, but a lot of them. I'm going to attempt to get the horrifying memories back!
Click to expand...
Click to collapse
Barney Fyfe said:
You know I'm sure I can get details on pretty much exactly what I did. Right now I'm at work, so I'll need a little more time.
Click to expand...
Click to collapse
Regardless how anxious we get, life always comes first. Take care of business. Just keep in mind that a lot of XDA veterans are putting their minds to this issue, and more details will help isolate the cause & effect. In general, details on your ROM, kernel, and any specifics would be helpful.
Barney Fyfe said:
I just duplicated the issue again, "no sdcard found"..etc
Click to expand...
Click to collapse
By saying "duplicated the issue", we're all going to assume you encountered the "Encryption Unsuccessful" screen again. Do you recall any specific steps you took to "duplicate" this issue? Since you were able to duplicate it several times, people troubleshooting the issue will benefit to know how you induced the matter. The goal is to discover what actually triggers this. Then, we'll get closer to finding a resolution.
Were you using the phone at the time - ie. the EU randomly appeared? Did it just reboot on its own and result in a dimmed boot animation screen? After you hit "reset," did you simply go into recovery and perform a NANDROID restore? Was there anything specific you did after getting the EU screen? Battery pull, reboot into recovery, flash other roms or kernels, etc? Did you previously connect it to your PC using MTP?
Barney Fyfe said:
... then using did a restore ("Semaphore CWM Recovery v5.5.0.4" by the way) restored the Captivate right back. After it boots I get "prepairing sdcard" then everything is back to normal.
Yes, full access to both External and Internal drives. Also can mount and unmount all /system, /cache, /datadata, /sdcard, /data, /emmc.
Click to expand...
Click to collapse
It seems you "resolved" your issue by simply doing a NANDROID restore via recovery. Was it really that simple? Or was there anything else (other roms or kernels flashed) prior to doing the restore.
If this is the case, then your experience starkly contrasts what most others have experienced - ie. no longer having access to the internal sdcard even in recovery (so a saved NANDROID backup wouldn't be accessible, etc).
Barney Fyfe said:
Answer to "b." Sorry, can you elaborate on this. I'm just now sure what you mean by "swap"
Click to expand...
Click to collapse
The "swap" is the work around being used to swap emmc & sdcard in vold.fstab - ie. to then have the phone recognize the external sdcard as the internal (since the internal sdcard is no longer accessible for 99.9% of the others with this issue).
Barney Fyfe said:
Now here it's difficult to say, I formatted and haphazardly (sorry, dumb I know!) flashed so many times attempting to get back control of this thing, I don't know.
And I would like to point out, that "Encryption Unsuccessful" crap ( and knowing better, I DID press Restart by the way) started just a couple days before this thread started. So just to give you an example as to how long this frustration was. I became obsessed, I worked on this phone for most all my waking hours, and I'm sure some of you have, "dreamed" of possible fixes as well!.
Click to expand...
Click to collapse
Everyone who's gone through this has experienced that same level of dread and anxiety. We can all relate.
Thanks for the nod my friend and I am still on the case but as you say life comes first.
There have been some developments in the SGSII threads that I'll post in the Dev thread.
Barney Fyfe said:
Hello,
Due to the 10 post threshold I am unable to post in the "Samsung Captivate -
Captivate Android Development
[Guide] Encryption Unsuccessful - Reset Android [ICS Issue]" thread.
I have resolved this issue a couple months back.
So, due to the time that has gone by it is a little difficult to explain what I did.
Last night I reproduced the issue, but after a restore, I'm good as new.
So now I am compelled to post this here. Being a "noob" and like I said not able to completely remember what "exactly" was done to accomplish the fix.
I am willing to share any information you wish.
But in a nutshell, I flashed ( a ROM I can't remember at the moment, but I'm sure I will once I get down to it. at work and pressed for time, "lunch time" ) using Heimdall, then downloaded the rom "Imfinitum-blue-v1.1.0 to my external SD, ( using a 34 Gb SD card, seems that is the only card that I could use. From what I remember anyway. ) Mod version "aokp_galaxysmtd_milestone-4"
The kernel version currently being utilized on this device is "[email protected] #1.
Sorry for being so confusing, and vague, but I really wanted to get something out there. I see they are still working on a fix for this issue, I found this resolve before page 30, it's now at 57, and after recreating the issue and then resolving it after a restore.
So, ask any question you want and I will be happy to help.
Hope this helps.
Take care.
Click to expand...
Click to collapse
thinks, I wanna try it on t959 with the EU bug.
USB problem
Hello, the same happens to me an hour ago. No charging no connection to computer but if the phone is powered off as soon as I connect the charger the phone boots up but no charge.
Captivate with CM9.
Barney Fyfe said:
Oh, now here is an odd change in event, not sure if this is related or not but I just realized last night that the phone won't charge, using three different batteries, all fairly new, nor is it being recognized USB wise.
I have a couple other Captivates I'm now having to use to charge my batteries for this one.
It's like the micro usb is damaged?
I'm usually very careful on how I insert them, 4 different cables too. That all work with the other Captivate. It's bricked but does charge the battery.
It's a GT-19000.
Oh and I almost forgot!!
The Samsung Galaxy S SGH-897/Captivate I'm using is fairly new, the date code is " 1111 "
Click to expand...
Click to collapse
What the OP said seems more of luck.
B.S. ALERT!!!!
I cant believe i actually came back to this thread to waste my time again!!, reading a thread that is supposed to help fix a problem i am afflicted with, but is instead filled with A BUNCH OF [email protected]$%@# [email protected]#@#$T!!!!!
Dude, if want to help people you must understand that in order to do this you need to explain "exactly" what it is you are talking about. No one can trust your information based on your "belief" in it. Software is a very techinical thing, which means to explain it you need to speak in technical terms. If you cant do that, do some more reading. Otherwise you arent helping anyone but yourself....Thanks, but NoThanks.
Related
When I boot up the phone, I get a message in my notification bar saying:
Damaged Internal SD Card.
Not an external memory card. My internal SD card. The one built into the phone. Anyone know if there's a way to fix this? Is there a way to reformat the built in SD card? My computer can't recognize it anymore. Am I pretty much screwed?
I posted this in androidforums as well.
EDIT: I found the "Format Card" option in settings. It's working fine, although the fact that this came up in the first place is very troublesome. Some further information: I did the GPS thing where you dial *#*# and some number, then rebooted my phone. My internal card was fine until I rebooted. That was the first time I got that message of a damaged internal sd card.
dude same thing happened to me today - any way to fix this ?
Format it, and hope you never see those dreadful words again.
norcal einstein said:
Format it, and hope you never see those dreadful words again.
Click to expand...
Click to collapse
This is a known fact that has been reported on some Galaxy S phones, it is coming from doing multiple Lag fixes of the phone internal SD from RFS to EXT. buyer be ware when flashing lag fixes over and over.
dpmurphy81 said:
This is a known fact that has been reported on some Galaxy S phones, it is coming from doing multiple Lag fixes of the phone internal SD from RFS to EXT. buyer be ware when flashing lag fixes over and over.
Click to expand...
Click to collapse
what about when you flash a ROM that comes with LAg fix by default ? and you Disable it all the time can that happen to you? cuz ive flashed but most roms r being gay now with Lag fix ... i disable always might i get that msg? :/
dpmurphy81 said:
This is a known fact that has been reported on some Galaxy S phones
Click to expand...
Click to collapse
This affects the bell vibrants only, the captivates never had this issue.
peachpuff said:
This affects the bell vibrants only, the captivates never had this issue.
Click to expand...
Click to collapse
One can assume that the captivate can have this problem also the hardware is no different really from the vibrant. And I feel in my opinion that it is related to the quality of the flash memory chip itself weather you have this problem. compound this with the relentless conversion of the RFS file system it is just a matter of time I believe. The trade off of speed is stability. But that is only my opinion...
dpmurphy81 said:
One can assume that the captivate can have this problem also the hardware is no different really from the vibrant. And I feel in my opinion that it is related to the quality of the flash memory chip itself weather you have this problem. compound this with the relentless conversion of the RFS file system it is just a matter of time I believe. The trade off of speed is stability. But that is only my opinion...
Click to expand...
Click to collapse
That actually is a pretty big assumption. Just because two phones appear "similar" based on the published specs doesn't mean their insides are at all related. We already know that from a strictly hardware standpoint, even the two GSM cousins in America (the Vibrant and the Captivate) have different physical hardware inside, and many other versions of the i9000 abroad vary quite a bit too. Samsung produces these phones in very large batches, and who knows exactly what the differences are in the individual components put onto each board.
And as far as I'm aware, there's not been a single case of repeated "lag fix" operations causing damage to the hardware. Which makes sense when you think about it too. If I load a single 720p movie onto my internal SD (OneNAND), that probably requires a lot more NAND cells to be touched than an entire system/data/dbdata/cache lag fix being applied. Since all those operations really do is backup the partition, delete the partition, format a new partition, and then restore the data back over. Not really the most intensive thing you can do with your internal SD...
The OP's problem probably lies somewhere in PEBKAC. Not unmounting storage cleanly from the PC, or accidentally unplugging during a file transfer, battery came out unexpectedly at some point, etc. I end up re-flashing my ROM so regularly that I never really have time for little problems to build into big problems, but that might have happened here. Just so many corrupt sectors before the OS finally gives up trying to deal with it. Either way, since formatting seems to have fixed the problem, and this storage is solid-state, not mechanical, the problem is probably not in the hardware.
I had this issue on my captivate, as did two others that I know of, with a certain release of voodoo lag fix. Haven't heard of complaints since, and although it was tricky to fix haven't had problems since
Its not just with Bell phones. But I agree I think its software not hardware (at least for us Cappy folks!)
Sent from my GT-I9000 using XDA App
fatttire said:
I had this issue on my captivate, as did two others that I know of, with a certain release of voodoo lag fix. Haven't heard of complaints since, and although it was tricky to fix haven't had problems since
Its not just with Bell phones. But I agree I think its software not hardware (at least for us Cappy folks!)
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
What was the fix you applied exactly? I'm interested to it. Thanks
I would like to know what else i can try. I am currently.experiencing the same damaged internal sd card issue and have tried reformatting to no avail. It just seems to skip the actual formating. My pc also cannot see the phone as a drive. Any help would be appreciated.
Bump. Having the same issue. Cant see any files in 'my files' (samsung galaxy s i9000), internal sd wont mount or format in clockworkmod recovery
Hi guys, Did you solve the problem somehow?
I just wanted to state that this may be correctable with JTAG. If you guys are interested in letting me try to correct this with JTAG please let me know. I have been able to fix, what I refer to as partition bricking on the i9000 and T959 Vibrant and this sounds similar.
Nah.... JTAG is fully unnecessary. See, the SDCard is a shared space. It's likely the cause of this problem was flashing an inappropriate PIT file after performing a lagfix. Try flashing the stock pit file... I'd attach it as it's really small, but i seem to have lost it . You're going to need to do a total reset on your phone. Use CWM to wipe and delete and format everything you can.
If this is an ACTUAL bad SDCard, then nothing will bring it back short of replacing the chip. JTAG would not be the way to go for this.
AdamOutler said:
Nah.... JTAG is fully unnecessary. See, the SDCard is a shared space. It's likely the cause of this problem was flashing an inappropriate PIT file after performing a lagfix. Try flashing the stock pit file... I'd attach it as it's really small, but i seem to have lost it . You're going to need to do a total reset on your phone. Use CWM to wipe and delete and format everything you can.
If this is an ACTUAL bad SDCard, then nothing will bring it back short of replacing the chip. JTAG would not be the way to go for this.
Click to expand...
Click to collapse
Not trying to butt heads with you but I've worked on many phones with what I refer to as "partition bricking" and they were not fixable with any method of flashing. I've gotten a few that were able to be fixed with PIT repartitioning but many have not been. Also see the other thread I replied to you in as JTAG could be a fully capable solution in this instance.
As stated, JTAG can address any portion of the NAND, not just the PBL and SBL blocks.
connexion2005 said:
Not trying to butt heads with you but I've worked on many phones with what I refer to as "partition bricking" and they were not fixable with any method of flashing. I've gotten a few that were able to be fixed with PIT repartitioning but many have not been. Also see the other thread I replied to you in as JTAG could be a fully capable solution in this instance.
As stated, JTAG can address any portion of the NAND, not just the PBL and SBL blocks.
Click to expand...
Click to collapse
Sure, it can. By default Riff does not. Also, JTAG is overkill for a bad partition flash. Just reformat from CWM and it should be fine.
AdamOutler said:
Sure, it can. By default Riff does not. Also, JTAG is overkill for a bad partition flash. Just reformat from CWM and it should be fine.
Click to expand...
Click to collapse
RIFF DOES SUPPORT THIS NATIVELY. Also, the phones I obtained were not fixable with CWM repartitioning. I spent hours on the first few to still have mount issue with DBDATA and /dev/block/mmcblk0p1 and /dev/block/mmcblk0p0 errors. I have found a few that were fixable with re-partitioning via ODIN but several that required JTAG to fix. I didn't spend days trying to find the perfect combo before turning to JTAG but I spent a lot of time on many of these phones.
Hi Connexion, I would be interested in trying this, can we do this to Korean Variant of Galaxy SHW M110 (anucall) let me know
Hi,
Unfortunately, that is not a supported model on the RIFF box right now. I sent you a PM I believe with some advice though to hopefully get through it.
Hi forum!!
I've been a happy Samsung Galaxy I9003 owner for a while now, and I've always come to this forum for reference on any issues encountered. But right now I have an issue i'm having a hard time understanding, and it's quite a mistery.
Everything started when I downloaded the new Gingerbread update. The phone was wonderful, worked perfectly, but it had one little issue. I left it one night, and the morning after when i picked it up i saw that it was prompting for the initial data (language, use 3G-Wifi, etc). I completed the form once more, and it was back to factory...but in a weird way. Contacts were gone, SMS were gone, APNs were gone, WiFis were gone...but my apps were still there! They were even ordered alphabetically in the menu! Weird, really weird...Background was back to the factory one, icons on the main desktop were back to factory ones, ringtones were back to factory ones. But all my app configurations were still there, emails, gmail, market, corporate email...it was all there.
I discarded this as an issue with the Gingerbread ROM i installed (from Kkrraazzyy's post, the last one), so I downgraded to Froyo once more. Now, why would I ever want to do that?
Idiot me did not look into what version I was running. So I tried the version i remembered I had installed. Worked nice, installed nice...but....next morning...SAME ISSUE! Once more the initial configuration and the same thing...no APNs, no SMS, no Contacts, no nothing, but apps and configs, purrfect!
Now, what I did was move to other Froyo images thinking that I might have gotten the wrong one. I discarded 4 or 5 of them, with different things not working on my phone exactly.
So, after a bit of debating with myself, I decided to upgrade to another GB, but not the final version, a previous one. When i connected it to Samsung Kies, to restore my backup, Kies greeted me with a "I've got a new firmware for your phone...do you wish to upgrade?". I thought "Why not? Maybe if the Samsung software is performing the upgrade, then it might work, considering that i wouldn't be intervening and possibly not interfering with it. So it upgraded, took a considerable amount of time in comparison to ODIN, but it went through.
How did it go? Smooth as silk...everything was wonderful! Apps worked, hardware worked, phone run well...backup went in perfectly...i was so happy! Last night I was watching a movie with it, it was great! So i went to sleep with a happy smile on my muzzle, only to wake up this morning and find the phone with....THE FRIGGIN' START FORM ONCE MORE!! FFFFFFFFFFFUUUUUUUUUUUUUUU!!!!!!
Once more, no APNs, no SMS, no Contacts, no WiFi, no nothing!!! Back to factory partially!
So now i'm thinking...firmware is out of the question...is there any chance there might be something physically wrong with my phone by now?? Something like...I don't know...I haven't got the slightest idea. So i'm open to ideas about what this might be about..
Oh, a colorful note...don't know if it has something to do, but i consider it sporty to let you know about it. A weird thing about a Froyo version i installed, was that when you woke up the phone, it would show a red sign on the top saying "Internal SD memory removed". I was truly shocked since I thought that the internal memory could not be removed without the phone crashing. But well, i just discarded that data at the time as an issue with the image.
Ideas, anyone? If not, i'm guessing i'll just place it under my car, ran it over, and get another with the insurance...
I think I heared such problem once a time. Try in this way
1. flash kpe with all 4 files
2. flash kpm single file as pda file.
3. do factory reset
if it solve ur problem then its better for u. But if u still face internal sd card error problem then straight way flash stock firmware which is available in ur country & go to samsung center & tell them that suddenly this problem is occured. Dont tell them that u have ever flashed anything on it.
CollieDawg said:
Hi forum!!
I've been a happy Samsung Galaxy I9003 owner for a while now, and I've always come to this forum for reference on any issues encountered. But right now I have an issue i'm having a hard time understanding, and it's quite a mistery.
Everything started when I downloaded the new Gingerbread update. The phone was wonderful, worked perfectly, but it had one little issue. I left it one night, and the morning after when i picked it up i saw that it was prompting for the initial data (language, use 3G-Wifi, etc). I completed the form once more, and it was back to factory...but in a weird way. Contacts were gone, SMS were gone, APNs were gone, WiFis were gone...but my apps were still there! They were even ordered alphabetically in the menu! Weird, really weird...Background was back to the factory one, icons on the main desktop were back to factory ones, ringtones were back to factory ones. But all my app configurations were still there, emails, gmail, market, corporate email...it was all there.
I discarded this as an issue with the Gingerbread ROM i installed (from Kkrraazzyy's post, the last one), so I downgraded to Froyo once more. Now, why would I ever want to do that?
Idiot me did not look into what version I was running. So I tried the version i remembered I had installed. Worked nice, installed nice...but....next morning...SAME ISSUE! Once more the initial configuration and the same thing...no APNs, no SMS, no Contacts, no nothing, but apps and configs, purrfect!
Now, what I did was move to other Froyo images thinking that I might have gotten the wrong one. I discarded 4 or 5 of them, with different things not working on my phone exactly.
So, after a bit of debating with myself, I decided to upgrade to another GB, but not the final version, a previous one. When i connected it to Samsung Kies, to restore my backup, Kies greeted me with a "I've got a new firmware for your phone...do you wish to upgrade?". I thought "Why not? Maybe if the Samsung software is performing the upgrade, then it might work, considering that i wouldn't be intervening and possibly not interfering with it. So it upgraded, took a considerable amount of time in comparison to ODIN, but it went through.
How did it go? Smooth as silk...everything was wonderful! Apps worked, hardware worked, phone run well...backup went in perfectly...i was so happy! Last night I was watching a movie with it, it was great! So i went to sleep with a happy smile on my muzzle, only to wake up this morning and find the phone with....THE FRIGGIN' START FORM ONCE MORE!! FFFFFFFFFFFUUUUUUUUUUUUUUU!!!!!!
Once more, no APNs, no SMS, no Contacts, no WiFi, no nothing!!! Back to factory partially!
So now i'm thinking...firmware is out of the question...is there any chance there might be something physically wrong with my phone by now?? Something like...I don't know...I haven't got the slightest idea. So i'm open to ideas about what this might be about..
Oh, a colorful note...don't know if it has something to do, but i consider it sporty to let you know about it. A weird thing about a Froyo version i installed, was that when you woke up the phone, it would show a red sign on the top saying "Internal SD memory removed". I was truly shocked since I thought that the internal memory could not be removed without the phone crashing. But well, i just discarded that data at the time as an issue with the image.
Ideas, anyone? If not, i'm guessing i'll just place it under my car, ran it over, and get another with the insurance...
Click to expand...
Click to collapse
Did you solved the problem??? I am having the same problem and I tried with some firmwares too.
vishal24387 said:
I think I heared such problem once a time. Try in this way
1. flash kpe with all 4 files
2. flash kpm single file as pda file.
3. do factory reset
if it solve ur problem then its better for u. But if u still face internal sd card error problem then straight way flash stock firmware which is available in ur country & go to samsung center & tell them that suddenly this problem is occured. Dont tell them that u have ever flashed anything on it.
Click to expand...
Click to collapse
I'll try that today and get back to you with the results! Thanks for the answer!
CollieDawg said:
I'll try that today and get back to you with the results! Thanks for the answer!
Click to expand...
Click to collapse
LMAO, I lol'd hard at your post regarding it went overnight FUU.
Firstly, the post was a little long, but interesting. Me gusta.
The problem could be the following
- What class is your SD card? Some tend to buy cheap ones, or some tend to offer when you get a SALE they pitch in a ****ty SD card that literally messes your phone. Made in Taiwan > Made in China. For some. There have been cases when the SD card has not been "ejected" properly the phone tends to receive this as a crash and default sets everything back to stock *Apple does this aswell*. But ofcourse I implore you to try using ANOTHER SD card. If your using one that used to be from a Nokia phone then you need to format that ****. Some files in Nokia cause issues with the Android, this happened when I first got my phone aswell. I would suggest getting one from branded companies, Kingston/SanDisk, IMO, Sandisk is the best. Cheap yet to the mark.
- What put me on edge was your contacts and messages being gone. Maybe it's SD related. Iunno.
PS: Don't use Kies. Kies is horrible. If 2 ugly trolls mated, Kies was probably the result.
To test: Use XXKPH/XXKPM Choice is yours, Don't know how to flash it? Link is under my sig, Remove your SD card. Use it for a day, Fill up the internal memory with atleast 500MB of stuff. Lastly? Pray that overnight the trollfairy doesn't swap your phone with a factory reset one .
Hey Misledz! Thanks for your reply!
About the SD Card, I'm using a Kingston Class 4, 8GB one. But the issue is presenting with "Internal SD Card". While i'm doing this with the phone, just out of precaution, i take it out and i haven't placed it inside my phone yet.
And the whole "Trollfairy" thing, it's starting to look like a viable explanation to it, LOL!!
Misledz said:
LMAO, I lol'd hard at your post regarding it went overnight FUU.
Firstly, the post was a little long, but interesting. Me gusta.
The problem could be the following
- What class is your SD card? Some tend to buy cheap ones, or some tend to offer when you get a SALE they pitch in a ****ty SD card that literally messes your phone. Made in Taiwan > Made in China. For some. There have been cases when the SD card has not been "ejected" properly the phone tends to receive this as a crash and default sets everything back to stock *Apple does this aswell*. But ofcourse I implore you to try using ANOTHER SD card. If your using one that used to be from a Nokia phone then you need to format that ****. Some files in Nokia cause issues with the Android, this happened when I first got my phone aswell. I would suggest getting one from branded companies, Kingston/SanDisk, IMO, Sandisk is the best. Cheap yet to the mark.
- What put me on edge was your contacts and messages being gone. Maybe it's SD related. Iunno.
PS: Don't use Kies. Kies is horrible. If 2 ugly trolls mated, Kies was probably the result.
To test: Use XXKPH/XXKPM Choice is yours, Don't know how to flash it? Link is under my sig, Remove your SD card. Use it for a day, Fill up the internal memory with atleast 500MB of stuff. Lastly? Pray that overnight the trollfairy doesn't swap your phone with a factory reset one .
Click to expand...
Click to collapse
Man this guy should seriously thing of taking writing as a profession.
ganeshbiyer said:
Man this guy should seriously thing of taking writing as a profession.
Click to expand...
Click to collapse
I know right?! Maybe writing is a profession of his. Despite the long nature I was strangely indulged to read it
@Collie, Well the problem happens at times when you don't factory reset. *2767*3855# that should get you in to a manual factory reset. The phone's internal memory sometime's has issues with that, You may however need to flash the latona file to repartition the drive. After the repartition, the flashing of the firmware and lastly, le factory reset. That should serve as a stable ground base
Kingston Nice.
Updates?
KIES really is a POS. Every time i flash a new fw and my phone does the initial boot while its connected to the pc I see the horrid screen on my phone reminding me that KIES is installed on my pc. FUUUUUUUUU
ganeshbiyer said:
Man this guy should seriously thing of taking writing as a profession.
Click to expand...
Click to collapse
Thanks!! I'm actually just a Wintel / Citrix / VMWare administrator. I've written a few fanfics here and there back when i was a filly, but not anymore!
Misledz said:
I know right?! Maybe writing is a profession of his. Despite the long nature I was strangely indulged to read it
@Collie, Well the problem happens at times when you don't factory reset. *2767*3855# that should get you in to a manual factory reset. The phone's internal memory sometime's has issues with that, You may however need to flash the latona file to repartition the drive. After the repartition, the flashing of the firmware and lastly, le factory reset. That should serve as a stable ground base
Kingston Nice.
Updates?
Click to expand...
Click to collapse
About that, maybe I'm doing the reset in an incorrect way. I've been using Vol +, OK, Power to enter the second recovery mode and factory reset the phone. I don't know if this is the same as using the code.
Update on what I did:
I installed the last version of Gingerbread once more, flashed with Odin. This time i did not install any app or register in google, i just left it as it was. This was done saturday afternoon. At night, i took it with me, and i left it in my bag while I was at the club. When i got back to it, around 6 AM, it hadn't rebooted. So i went home, went to sleep, woke up at midday for lunch and....FFFFFFUUUUUUUUUU!!!!!
LOL the irony of the best order. Well did you try without the sdcard? That's your last option from your side, the next possible is getting the unit changed if you are under warranty, just don't mention odin, rather always blame kies LOL. If the end of the world happened, kies. World War 3,kies. There was a user who had the same issue reported like 5months ago, he had internal ROM problem where the phone failed to save the information it was given causing it to say the internal was corrupt? He ended up getting a new unit and found out later the unit he had previously was a faulty handset
Sent from my GT - I9003 in the bathroom
Misledz said:
LOL the irony of the best order. Well did you try without the sdcard? That's your last option from your side, the next possible is getting the unit changed if you are under warranty, just don't mention odin, rather always blame kies LOL. If the end of the world happened, kies. World War 3,kies. There was a user who had the same issue reported like 5months ago, he had internal ROM problem where the phone failed to save the information it was given causing it to say the internal was corrupt? He ended up getting a new unit and found out later the unit he had previously was a faulty handset
Sent from my GT - I9003 in the bathroom
Click to expand...
Click to collapse
SD has been out since day 1, since I started having this issue, first thing i thought is "this idiot is saving its own files to the SD instead of its own memory, and when it reboots for some reason it can't find the files and goes nuts".
So yes, i'm thinking about just taking it to the store and getting a new one...
THAT'S IT! I'm taking it to the store tomorrow...
Now it's just rebooting itself...Samsung logo going on and on....
Thanks everyone for the help!!!
CollieDawg said:
THAT'S IT! I'm taking it to the store tomorrow...
Now it's just rebooting itself...Samsung logo going on and on....
Thanks everyone for the help!!!
Click to expand...
Click to collapse
Get it replaced asap so you can join the "famiry" !
Misledz said:
Get it replaced asap so you can join the "famiry" !
Click to expand...
Click to collapse
If I don't get it changed tomorrow, my next post will be a link to youtube, where you'll find a video of me lighting it up on fire, then dancing around it as it burns, and finally running it over with my car...total destruction, should be covered by my insurance...
CollieDawg said:
If I don't get it changed tomorrow, my next post will be a link to youtube, where you'll find a video of me lighting it up on fire, then dancing around it as it burns, and finally running it over with my car...total destruction, should be covered by my insurance...
Click to expand...
Click to collapse
ROFL, That was literally the funniest thing I heard all month
wish you good luck
CollieDawg said:
If I don't get it changed tomorrow, my next post will be a link to youtube, where you'll find a video of me lighting it up on fire, then dancing around it as it burns, and finally running it over with my car...total destruction, should be covered by my insurance...
Click to expand...
Click to collapse
LOL i would have done the same, only a little different, burn it, dance and wait for the ashes to settle, drink up the ashes or feed it to my dog, then walk upto the nearest samsung retailer and take a dump on the entrance entitled 'Now your phone is ****', I'm pretty sure the insurance covers the carpet too.
Sent from my GT - I9003 in the bathroom
CollieDawg said:
If I don't get it changed tomorrow, my next post will be a link to youtube, where you'll find a video of me lighting it up on fire, then dancing around it as it burns, and finally running it over with my car...total destruction, should be covered by my insurance...
Click to expand...
Click to collapse
Excellent! I loved your whole style of writing although your issue might yet get resolved at the samsung service center but this description is a total Lullzzz.. Lol!
Also I humbly request you to leave a PM with a few links of your fan fic stories! thanks...
Tapashocked via my gt-I9003 with a random keyboard of my choice !
Misledz said:
LOL i would have done the same, only a little different, burn it, dance and wait for the ashes to settle, drink up the ashes or feed it to my dog, then walk upto the nearest samsung retailer and take a dump on the entrance entitled 'Now your phone is ****', I'm pretty sure the insurance covers the carpet too.
Sent from my GT - I9003 in the bathroom
Click to expand...
Click to collapse
Super Duper epic Lol!
Boss you've redefined the whole meaning of taking a ****! :O
Tapashocked via my gt-I9003 with a random keyboard of my choice !
How do I get my android back? Or, Can I?
This will become obvious, so here it is... I/Me = Noob. Thanks for the patience in advance.
I did a good month of research & playing around before, then finally installed ClockWorkMod & rooted my S2. Was up late trying to get something done on it & had just installed cwm. I choose the option within cwm to "backup" and let it run it's course, assumed (never, I know) this was done correctly & I was free to do what I love, customize - optimize - edit - etc. Well, apparently is was not done. I realized this last night and immediately scrambled (panicked) & may have made my matters so bad that I will be walking into the Sprint store with my tail, & ego, between my legs forking over some hard earned cash.
I formatted all files within "Mounts and Storage," cleared all "caches" and did a "wipe data/factory reset" - Basically did every option I could at least 2x's.
I did look for the back up - but it was not there (prior to all wipes)
I feel like I can get my phone back witch is stuck on the Samsung Galaxy S2 screen when on, and the battery pic when on charger. But, I need access to the external SD drive so I can install the files that I have on my CPU. I have researched this all day! Took off work today, and tomorrow seemingly. If this is a hopeless task, for the love of all things righteous, someone please put me out of my misery!
BTW - First post ever on any site. I am smart enough to know that when it comes to this stuff I cannot keep being hard headed and not asking for help. I just hope its not to late.
Thanks. Apparently l only the cool people are allowed to post and actually get a response. I am so glad I paid for this bull$hit. Middle finger at ya
If you can only access cwm them you should be able to download a ROM for your phone and flash it within CWM.
Sent from my HTC Sensation 4G using XDA App
Seriously? That's definitely a good attitude to hold when you don't receive help. Just get hostile with the people you are requesting help from! But I digress. Well, if you did indeed botch a backup somehow, it sounds like all you need to do is just flash another ROM or something and you should be golden. The backups are stored in your external SDcard for future reference though, under CWM -> Backup.
In response to the attitude... what else would you have me do when I need help, I ask, and I am ignored? Plus, my tactic worked, but, I digress.
In the days of emptiness with no help, I list cwm and now have real problem. I can still access default recovery mode, and a screen that says got to kies and do recovery mode. My main issue after several hours troubleshooting, is, I cannot get my phone to be recognized by any drive on my laptop. It will also not respond to being charged.
I have already replaced the dam phone, but I am not giving up on the seemingly fubarred one.
Without sarcasm, thank you for your response and attempted assistance. I do appreciate it, despite what you feel about any prior comments.
Several times this past week, my Galaxy S has complained because it thinks I removed the SD chip, though, of course, I had not. It has also sung the "I'm out of power and will shut down now" song, but when I plug it in, I find it still has plenty of battery life. (Was it complaining about the chip, not the power with that song?)
I don't think anything was lost from the chip the first time or two, but this last time I know that it lost some Kindle books, so who knows what else is gone. The 16G Samsung chip is down to 1.2G free.
I'm currently backing up the SD chip and will install another one, but I thought I'd ask if anyone has other thoughts re the source of the problem. The phone is less than a year old.
Thank you kindly.
Try another card first. My bet would be the card is faulty. If you try another one and still have the same issue I'd call Samsung. As far as the battery issue goes get a new one. There have been a lot of reports of battery issues, ROMs rebooting, etc. Most of them where fixed by just getting a new battery.
I'd definitely try to find the cause of the problem before your warranty expires.
I had my microSD holder fail after about 18 months. The early symptoms were that it didn't quite want to "click in" sometimes when I was inserting it. While a relatively inexpensive fix (under $15 for the part off an eBay vendor), getting someone else to deal with the installation is nice.
NanaSarah said:
Several times this past week, my Galaxy S has complained because it thinks I removed the SD chip, though, of course, I had not. It has also sung the "I'm out of power and will shut down now" song, but when I plug it in, I find it still has plenty of battery life. (Was it complaining about the chip, not the power with that song?)
I don't think anything was lost from the chip the first time or two, but this last time I know that it lost some Kindle books, so who knows what else is gone. The 16G Samsung chip is down to 1.2G free.
I'm currently backing up the SD chip and will install another one, but I thought I'd ask if anyone has other thoughts re the source of the problem. The phone is less than a year old.
Thank you kindly.
Click to expand...
Click to collapse
I suggest you take that card out and keep it out. I was getting the same problem after i flashed a custom rom and it destroyed my 32gb chip and i lost a lot of important data.
u170who said:
I suggest you take that card out and keep it out. I was getting the same problem after i flashed a custom rom and it destroyed my 32gb chip and i lost a lot of important data.
Click to expand...
Click to collapse
The custom rom DID NOT destroy your sdcard. You either accidentally formatted it or did not unmount it from your pc and it corrupted the data. Custom roms from this forum will not and can not destroy the sdcard. More people would be complaining and the devs would be run off xda if that happened. Stop spreading lies.
eollie said:
The custom rom DID NOT destroy your sdcard. You either accidentally formatted it or did not unmount it from your pc and it corrupted the data. Custom roms from this forum will not and can not destroy the sdcard. More people would be complaining and the devs would be run off xda if that happened. Stop spreading lies.
Click to expand...
Click to collapse
I definitely didn't do either, but i know my duties of protecting the the devs. Things happen and something corrupted the Rom. Most definitely my own fault for not flashing properly or just because there are gremlins living in my phone that refuse to move out. But, thats why i didn't name which rom was it that was related to the problem. Chill out eollie, just trying to help.
If you read what you posted you said it happened after flashing a custom rom. That to most people means you are blaming the custom rom. There is safety checks and balances put in place to protect that stuff. Plus flashing a rom will never modify your sdcard. If anything it will just add some folders when you boot. Again if there was rom out there doing that then people would have reported it. User error is the only explainable answer.
You also told the person to take out the sdcard and leave it out...that also implies you are blaming a rom and not yourself.
Furthermore, I dont care if you want to post the name of the rom. Protecting devs is not my job. But stopping false info about the roms is something I will do. To new people they see these kinds of statements and think Im not going to try to flash that it might mess up this or that. And that decision is based on some false accusations. That is not fair to the community nor the devs.
My screen cracked after reading this post ..but I didn't say which post
Sent from my Galaxy Nexus using xda premium
eollie said:
If you read what you posted you said it happened after flashing a custom rom. That to most people means you are blaming the custom rom. There is safety checks and balances put in place to protect that stuff. Plus flashing a rom will never modify your sdcard. If anything it will just add some folders when you boot. Again if there was rom out there doing that then people would have reported it. User error is the only explainable answer.
You also told the person to take out the sdcard and leave it out...that also implies you are blaming a rom and not yourself.
Furthermore, I dont care if you want to post the name of the rom. Protecting devs is not my job. But stopping false info about the roms is something I will do. To new people they see these kinds of statements and think Im not going to try to flash that it might mess up this or that. And that decision is based on some false accusations. That is not fair to the community nor the devs.
Click to expand...
Click to collapse
Eollie, my suggestion to take out the card was so she could avoid losing data on it. There really isn't any animosity toward devs or roms inferred there. Telling her to leave it is not going to solve her problem.
Beastmode said:
My screen cracked after reading this post ..but I didn't say which post
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hey Erik, glad you have a sense of humor, lol. .. Keep it light, keep it real, right? I really do appreciate your hard work and wish i had the time to get into helping you guys dev.
That happened to me on my G1 after I took it in for screen repair.
My screen broke, but my swap file was on my sd card, so I knew that the sd reader was fine because the phone was getting notifications after boot. After I took it in for repair, they fixed the screen, but my phone wasn't booting up, so they told me that I was running a nexus one rom on it and they could fix it for 20 bucks. I yelled at them for blaming me for the problem, then I went into CWM Recovery, and it told me that there was no sd card. I tried pulling the sd card and pushing it around, and even got it to boot once. So yeah, did you take it into any cheap repair shops, cause they can break phones instead of fix them.
I can't say when it happed. Evidently, it has been on my phone for a long time. I can remember seeing some of this funny crap months ago when I first rooted my phone. One of the mods here has a surfaceflinger hack that will take over your entire system. Your accounts will get hacked. First it was my Google drive. There was a zip file in there that I did not place. It said it was a Metro PCS Note5 zip. It was shared to my drive by someone else, and I could not remove it. So any time I did a factory reset and logged into my Google account, it would be loaded onto my phone. I finally got that cleaned up, but they had moved to my OneDrive storage with the same thing under a different file name. This hack is so smooth, that your phone won't even hesitate. It is disguised as Android OS, but if you check the battery stats, it says surfaceflinger. It is located in your data partition. It is a add on script, and it will eventually infect about 20 more apps with add on scripts. It will load up tons of /data/data along with a recovery from boot script, and..... I just discovered a little too late that there is a script that will destroy your device if you remove it the wrong way. I think the name of it is sec_device_destroy but I can't be sure. I saw the code in a system log file, but I do not know what it is yet. I am 100% positive that some of you have the same problem, you just don't know it. I'm gonna start taking apart every singe file in the development threads until I find it. As for now.... My device is stuck in a infinite bootloop. It won't recover from ODIN, and I have a new LED llight that is white. I can answer any questions and provide screenshots, and system logs if anyone wants to help uncover this beast. It is super legit. Best Android hack I've ever seen. It does every thing. Who is gonna help me locate this b.s? My Note 5 is useless now. Somebody here has it, I assure you, and when you discover it, you should ask for help. If you don't remove every bit of it, the device will not boot again. I'm gonna keep playing with mine, but I'm pretty sure it is toast. ( EDIT---> I was able to get to boot again by flashing TWRP and using the wipe option to repair each partition. I had to change them to exFAT then back to EXT4 to get them to mount.)
Sounds like my boot loop of death. Where everything was Odin flashed and still wouldnt load. Quick question when you were on Odin did you select the band erase all option? And do you still have acesss to recovery? Was all this weird stuff going on when you firmware was load? Did anything strange happen while in recovery? And why didn't u send it back to sprint)
---------- Post added at 10:22 PM ---------- Previous post was at 10:19 PM ----------
If I was in your shoes I would select the band erase all and repartition option. Re download stock firmware from sammobile, go back to Odin to root and add twrp, select the erase button again to flash moar ROM and see what happens. If it's a hack like u said then I'd use my insurance
The potential for having your personal security and financial disaster that something like this could cause is why i stopped rooting.
Rumning other none store apps is like letting a guy you dont know come over and say "hey, i have these cool mods i can do to your car's brakes! I take out a few parts, replace others with parts I made in my garage, and load my own software into your anti-lock brake system".
Sent from my SM-N920P using Tapatalk
You can't blame no one if your phone gets fried or blown up, you take the risk at your own discretion . No one force you to flash anything. To avoid any problems don't flash anything your not sure what's going to happen. If i see someone post a s7 edge port, I'm not gonna flash it until i get some good feedback or take one for the team and hope it don't destroy my phone. Goodluck fixing your phone don't seem like it's too hard to fix depending your experience . I would help but it's too time consuming helping fix a phone i can't even see or test out.
Sent from my SM-N920P using XDA-Developers mobile app
I'm really sorry that this happened to you. But @bonebeatz1234 is right. There is a disclaimer at the beginning of every rom, feature add-on, theme, kernel, etc. The whole point of Q&A & replys are so you can find out if something is "okay" to flash. There are so many known developers that have built stuff for so many devices. Its rare to find something on XDA that is "unsafe." I can't even remember ever finding anything that is "unsafe" or nearly as bad as you are describing. Especially for the Sprint Note 5. I'm assuming you have a SM-N920P do to the fact that you're posting it here. There have only been a few roms for this device & maybe a couple handfuls of add-ons. The one or two things I've seen that have caused problems with this device, they were removed with-in a few hours. You weren't very clear on where you got this hack at all. Are you saying it was something you downloaded from one of the Sprint Galaxy Note 5 threads? You are a Senior Member. So, I'm assuming you know what you are talking about. I believe that it is very possible you did get it from some place on here. But, in order for me to believe that, I have to also believe that it is just as possible that it could have came form anywhere else on the web via public WiFi connection, email, file download, text message, USB connection or at least 100 other ways. @DAvid_B made a point about the risk of rooting your device. Although the risk can go up for threats. The same rules apply for rooted device as they do for non-rooted devices. BE CAREFUL! Use software to protect yourself, read reviews, don't be the guinea pig. If you are like me & are addicted to putting yourself at some (if even the smallest) amount of risk, HAVE INSURANCE! Most if not all people have to agree that it's worth the $11 a months & $200 deductible to have as much fun as we all do. Its a hobby. People spend more money on model airplanes, playing golf & hunting. I haven't had to file a claim in over 6 years. I say all that to say this... Anyone that see's this thread & decides its too much of a risk to root, I promise you, IT ISN'T! The advantages out way the risk by about a 1000! The members of XDA are here to help with any issues you may have. There are VERY FEW things that are UNFIX-ABLE! And when I say "very few" I mean little to non! When I say little to non, I mean NONE! AT ALL! Even the problem he described IS FIXABLE! Like he stated, ask for help. @Sleepycloud, I pray you get this resolved. Even if you have to Odin back to stock & backup/wipe your Google Drive & OneDrive account, I know you can fix this. Please don't think that I meant any disrespect for posting this. I just want people to know this is extremely rare & only a one in a million chance it could happen.
Sleepycloud said:
I can't say when it happed. Evidently, it has been on my phone for a long time. I can remember seeing some of this funny crap months ago when I first rooted my phone. One of the mods here has a surfaceflinger hack that will take over your entire system. Your accounts will get hacked. First it was my Google drive. There was a zip file in there that I did not place. It said it was a Metro PCS Note5 zip. It was shared to my drive by someone else, and I could not remove it. So any time I did a factory reset and logged into my Google account, it would be loaded onto my phone. I finally got that cleaned up, but they had moved to my OneDrive storage with the same thing under a different file name. This hack is so smooth, that your phone won't even hesitate. It is disguised as Android OS, but if you check the battery stats, it says surfaceflinger. It is located in your data partition. It is a add on script, and it will eventually infect about 20 more apps with add on scripts. It will load up tons of /data/data along with a recovery from boot script, and..... I just discovered a little too late that there is a script that will destroy your device if you remove it the wrong way. I think the name of it is sec_device_destroy but I can't be sure. I saw the code in a system log file, but I do not know what it is yet. I am 100% positive that some of you have the same problem, you just don't know it. I'm gonna start taking apart every singe file in the development threads until I find it. As for now.... My device is stuck in a infinite bootloop. It won't recover from ODIN, and I have a new LED llight that is white. I can answer any questions and provide screenshots, and system logs if anyone wants to help uncover this beast. It is super legit. Best Android hack I've ever seen. It does every thing. Who is gonna help me locate this b.s? My Note 5 is useless now. Somebody here has it, I assure you, and when you discover it, you should ask for help. If you don't remove every bit of it, the device will not boot again. I'm gonna keep playing with mine, but I'm pretty sure it is toast.
Click to expand...
Click to collapse
If you are willing to send me the phone, I could probably fix it for you and send it back. I know it's hard to trust people these days so it's totally up to you.
bonebeatz1234 said:
You can't blame no one if your phone gets fried or blown up, you take the risk at your own discretion . No one force you to flash anything. To avoid any problems don't flash anything your not sure what's going to happen. If i see someone post a s7 edge port, I'm not gonna flash it until i get some good feedback or take one for the team and hope it don't destroy my phone. Goodluck fixing your phone don't seem like it's too hard to fix depending your experience . I would help but it's too time consuming helping fix a phone i can't even see or test out.
Sent from my SM-N920P using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm not mad. Lol Not at all. I am a true geek to the heart. This is fun stuff to me. You learn more when you are challenged beyond your current skillset. I'm just putting everybody up to the fact that there is something malicious here in the threads. I have a strong feeling of where it came from. I already to apart the "Stock" .tar and found 3 extra files in it. A param.bin file, a carrier .img and a PIT file. I am one hundred percent sure that when I take that PIT file apart later that I will be able to confirm my suspicions. According to the thread here by @tdunham in this thread; http://forum.xda-developers.com/spr...sprint-galaxy-note-5-sm-n920p-partition-There are 19 partitions. I believe that I have 24 or 25. I'll have to get back with y'all on this one. Can anybody confirm that this partition table is still viable for Marshmallow? I'll post screenshots in about an hour or two for everyone to examine. I would love some help on this. I have never removed partitions before and my knowledge on how to go about it is limited. I'm reading, but most of it is unrelated garbage. If anyone has a link that will help me educate myself and remove these partitions, I would be super thankful.
MrMike2182 said:
If you are willing to send me the phone, I could probably fix it for you and send it back. I know it's hard to trust people these days so it's totally up to you.
Click to expand...
Click to collapse
That is pretty awesome of you bro. I am pretty sure I have correctly identified the problem. I have 4 or 5 extra partitions. This is why it keeps coming back, and that is why ODIN and Smart Swithc does not fix it. They are only going to see the 19 partitions they are supposed to see and they will not even look anywhere else. I bought a root partition app on Google Play for $9.99 and that is how I saw the extra partitions. This has been on my phone for a long time. A very long time. Like 6 months, but I never knew it. I can remember seeing about 5 USB folders that I could not open. They are labeled as external usb storage. I'll post screen shots later. So now that I know what the problem is, I see a bright side coming soon. lol
Sleepycloud said:
That is pretty awesome of you bro. I am pretty sure I have correctly identified the problem. I have 4 or 5 extra partitions. This is why it keeps coming back, and that is why ODIN and Smart Swithc does not fix it. They are only going to see the 19 partitions they are supposed to see and they will not even look anywhere else. I bought a root partition app on Google Play for $9.99 and that is how I saw the extra partitions. This has been on my phone for a long time. A very long time. Like 6 months, but I never knew it. I can remember seeing about 5 USB folders that I could not open. They are labeled as external usb storage. I'll post screen shots later. So now that I know what the problem is, I see a bright side coming soon. lol
Click to expand...
Click to collapse
Some times when a Samsung device gets bricked you need whats called a PIT that can reflash the partitions. It's on here somewhere or I have one.
MrMike2182 said:
Some times when a Samsung device gets bricked you need whats called a PIT that can reflash the partitions. It's on here somewhere or I have one.
Click to expand...
Click to collapse
I have one. It doesnt work because a PIT file will only reset the factory image partitions. When there are additional partitions, it does not touch them. I have one extended partition after boot. Everything gets rearranged under /sys/dev/block/8:0 have you ever heard of that? Me neither. Lol I need to disect this and remove the script after a fresh flash before the first boot. Something tells me that it would be easier to deal with then. Ill post some pics from my computer here in a bit. I dont have the option on my phone
Here are some pics of the new extended partition and the logical partitions within.
Sleepycloud said:
I have one. It doesnt work because a PIT file will only reset the factory image partitions. When there are additional partitions, it does not touch them. Inhave one extended partition after boot. Everything gets rearranged under /sys/dev/block/8:0 have you ever heard of that? Me neither. Lol I need to disect b this and remove the script after a fresh flash before the firsy boot. Something tells me that it would be easier to deal with then. Ill post some pics from my computer here in a bit. I dont have the option on my phone
Click to expand...
Click to collapse
I've seen some pretty crazy partition set ups the HTC Desire for instance has over 20 partitions and all of them have close to 200MB of free space on them that you can't even use! Talk about a waste of space lol.. But /sys/dev/block/8:0?!?! The fuuu... What kind of partition is that?!
Damn, your phones using almost all the ram/memory that you have.. Are you running a lot of apps or something else that's memory intensive?
So now the million dollar question is..... What is it gonna take to remove this b.s. from my phone. Removing the folders does not work. They get reinstalled upon every boot. I need to find the script(s) and where they are hidden, and delete them, then remove the partitions form the logical folder. I am tempted to just wipe the logical partition it its entirety then create a whole new partition table based on my unrooted Note 5. However, I am going to wait until I get some solid feedback from one of y'all. Who has an idea of what I need to do here. Repartitioning with a PIT file does not work. IT does not touch these extra partitions. I think they are labeled, sdb, sdc, and sdd.
I'm just gonna go ahead and let the world know who the piece of crap is. Here... go take a look for yourself. Download the "stock" tar and extract it, then extract the .tar itself. You'll find the extra files there. It contains a param.bin file, a carrier.img, and a modified PIT file that will give you the crap on my phone. If I could be my hands on this dude, I would choke him until he was purple. This has been a major pain in my ass for over 3 months now. My accounts were hacked, all of them, files were deleted, and I had no privacy what so ever. Here... This is where it came from. http://forum.xda-developers.com/note5/general/project-noble-firmware-pit-file-galaxy-t3179529
Sleepycloud said:
So now the million dollar question is..... What is it gonna take to remove this b.s. from my phone. Removing the folders does not work. They get reinstalled upon every boot. I need to find the script(s) and where they are hidden, and delete them, then remove the partitions form the logical folder. I am tempted to just wipe the logical partition it its entirety then create a whole new partition table based on my unrooted Note 5. However, I am going to wait until I get some solid feedback from one of y'all. Who has an idea of what I need to do here. Repartitioning with a PIT file does not work. IT does not touch these extra partitions. I think they are labeled, sdb, sdc, and sdd.
Click to expand...
Click to collapse
Deleting them is not going to work no matter which way you remove them they'll come right back after a reboot and the only way to stop that from happening is to flash a custom kernel/boot that's got write protection off. If you don't have that they just keep coming back no matter what.. All the apps are usually always in these 2 places /system/apps and /system/priv-apps
---------- Post added at 11:00 AM ---------- Previous post was at 10:55 AM ----------
Sleepycloud said:
I'm just gonna go ahead and let the world know who the piece of crap is. Here... go take a look for yourself. Download the "stock" tar and extract it, then extract the .tar itself. You'll find the extra files there. It contains a param.bin file, a carrier.img, and a modified PIT file that will give you the crap on my phone. If I could be my hands on this dude, I would choke him until he was purple. This has been a major pain in my ass for over 3 months now. My accounts were hacked, all of them, files were deleted, and I had no privacy what so ever. Here... This is where it came from. http://forum.xda-developers.com/note5/general/project-noble-firmware-pit-file-galaxy-t3179529
Click to expand...
Click to collapse
I'd report this to one of the moderators if I was you so they can check it out and remove it if it's harmful to people's devices I don't think xda would be happy hosting that type of ****!
MrMike2182 said:
Deleting them is not going to work no matter which way you remove them they'll come right back after a reboot and the only way to stop that from happening is to flash a custom kernel/boot that's got write protection off. If you don't have that they just keep coming back no matter what.. All the apps are usually always in these 2 places /system/apps and /system/priv-apps
Click to expand...
Click to collapse
I hava already tried that. These are add on scripts. They work on any kernel. I have to delete the partions themselves but I'm not exactly sure which ones or how to do it without bricking my phone. I'm gonna move slow on this one until I am sure that II have the right solution. I'm certain it is the sda, sdb, sdc, and sdd partitions that need to be deleted. First I need to know if this partition table is still valid for Marshmallow. http://forum.xda-developers.com/note5/general/sprint-galaxy-note-5-sm-n920p-partition-t3190326 Once I know that, I can proceed. Is this PIT still the same in marshmallow?
Sleepycloud said:
I hava already tried that. These are add on scripts. They work on any kernel. I have to delete the partions themselves but I'm not exactly sure which ones or how to do it without bricking my phone. I'm gonna move slow on this one until I am sure that II have the right solution. I'm certain it is the sda, sdb, sdc, and sdd partitions that need to be deleted. First I need to know if this partition table is still valid for Marshmallow. http://forum.xda-developers.com/note5/general/sprint-galaxy-note-5-sm-n920p-partition-t3190326 Once I know that, I can proceed. Is this PIT still the same in marshmallow?
Click to expand...
Click to collapse
Yeah that PIT is fine but if I were you I'd try to flash a different kernel because I had the same problems with apps returning after a reboot and the only way to stop that from happening again was to flash the custom kernel. That stopped them from coming back. <----This was on an HTC device so maybe Samsung is different?
This b.s. has my ADB disabled somehow. Even when I open the IOT Menu and switch from MTP to MTP+ADB it still does not work. It does work upon a fresh flash if I let the stock recovery update the system image then immediately go back into download mode before it boots up. After that, I have no ADB capabilities. Would that be a build.prop issue?
So was my advice useless oo?
djhulk2 said:
So was my advice useless oo?
Click to expand...
Click to collapse
No. It was pretty good, but I already have a good Note 5. I'm trying to learn more about Android bro. I wanna fix this one, not replace it. Give me some more solid ideas!!! I'm open to suggestion. Thank you.