[Q] cant fully boot into phone - Galaxy S III Q&A, Help & Troubleshooting

I have a Samsung Galaxy s3 which I successfully rooted over a year ago though I never bothered with a custom rom. I have now purchased a note 3 so in preparation for selling the S3 I did a factory reset through Settings to clear out all my apps, data and personal information. That all went well and the device booted back into the normal system a couple of times (I didn't check to see if root had been maintained or not) This weekend I got it out to sell it only to find that it boots through the first part of the routine with the Samsung moving logo but then sticks on the static SAMSUNG screen and will not go further.
I am able to boot into TWRP so would I be able to download a stock rom from somewhere, insert a micro sd card with the stock rom on it and recover through TWRP? Alternatively I do have an old full back up stored on my computer - I could transfer this to the micro sd and restore this through twrp - I can see this was made through twrm as the openrecovery-twrp-2.3.1.0-i9300.tar.md5 is stored with it. Of course if this works I would still need to perform a reset to get rid of all the personal data etc so could end up in the same situation later.
What recommendations do you helpful guys have?

gbswales said:
I have a Samsung Galaxy s3 which I successfully rooted over a year ago though I never bothered with a custom rom. I have now purchased a note 3 so in preparation for selling the S3 I did a factory reset through Settings to clear out all my apps, data and personal information. That all went well and the device booted back into the normal system a couple of times (I didn't check to see if root had been maintained or not) This weekend I got it out to sell it only to find that it boots through the first part of the routine with the Samsung moving logo but then sticks on the static SAMSUNG screen and will not go further.
I am able to boot into TWRP so would I be able to download a stock rom from somewhere, insert a micro sd card with the stock rom on it and recover through TWRP? Alternatively I do have an old full back up stored on my computer - I could transfer this to the micro sd and restore this through twrp - I can see this was made through twrm as the openrecovery-twrp-2.3.1.0-i9300.tar.md5 is stored with it. Of course if this works I would still need to perform a reset to get rid of all the personal data etc so could end up in the same situation later.
What recommendations do you helpful guys have?
Click to expand...
Click to collapse
try to some firmware dude
u have usb jig? use it to reset u binary :good:
and flash again with odin
if u have backup in cwm u can restore so Do it :good:

As you are going to sell it then follow the guide in general forum, stickies to return to stock. Factory reset before you boot the fresh firmware.

further
VerlyAnanda said:
try to some firmware dude
u have usb jig? use it to reset u binary :good:
and flash again with odin
if u have backup in cwm u can restore so Do it :good:
Click to expand...
Click to collapse
I don't have a usb jig whatever that is
I have an old back up on my computer which I can copy to an external SD card to put in the phone
I can then try using TWRP (I have this not CWM) to try restore the back up
This may work I can only try it - however I will still be in the position of needing to do the reset to clear all my data and put the phone back into "new" state and am concerned this may cause the problem again
Is this the best plan? I suppose once I get it working I can use ODIN to flash a stock rom
The problem is I understood all this a year ago when I rooted it but its all a little vague to me now as I decided not to do more than root the phone so I could back it up

formatting cache solved the problem!
gbswales said:
I don't have a usb jig whatever that is
I have an old back up on my computer which I can copy to an external SD card to put in the phone
I can then try using TWRP (I have this not CWM) to try restore the back up
This may work I can only try it - however I will still be in the position of needing to do the reset to clear all my data and put the phone back into "new" state and am concerned this may cause the problem again
Is this the best plan? I suppose once I get it working I can use ODIN to flash a stock rom
The problem is I understood all this a year ago when I rooted it but its all a little vague to me now as I decided not to do more than root the phone so I could back it up
Click to expand...
Click to collapse
I read someone had the same problem and just cleared the cache - so went into Team Win wiped cache and it restarted - guess I was looking for a complicated solution to something simple!

Related

Phone flashes files but is still on older version

A friend of mine sent me his SGS2 which has some strange issue that happened after trying to root and/or simunlock. (not sure what caused this issue).
The phone has stock rom (Telcel Mexico) and is rooted, has CWM and boots properly, but two issues happen:
* Each time your reboot it kind of "factory resets", deleting wifi networks, apps, settings, etc.
* If you flash anything, it succeeds apparently but after rebooting it's still on the same ROM/kernel versions it was before flashing. NO ERRORS. This applies for Odin, with CWM, I have tried installing CM7 and CM9 roms (downloaded 2-3 times) and all say "Can't open /sdcard............./....zip (bad)"
I was hoping that following this thread would help:
http://forum.xda-developers.com/showthread.php?t=1457458
However, even flashing the bootloader makes no difference. The count on download mode is stuck on 2 no matter if I install ROMs, kernels, bootloader, etc.
Edit: what's even wirder, I put my microSD card in the phone and it formatted it and replaced my content with my friend's last snapshot. How can such a thing happen? It's as if the phone was locked into some strange "restore" mode...
What can I do with this? I feel kind of stuck with this situation... Have not found any information so far...
Regards
there was similar thread some time ago, it seemedvthat I think the whole system was read only, I'll try to search a bit for that
EDIT: I could't find it but try to mount system and data and stuff in cwm and then tey to flash aome rom, then unmount (I'm not pro but this is what I would try)
Sent from my sgs2 running cm9
Well,
I think the FS mounting issue would work with cwm installable roms, but if I have reinstalled everything from odin, even the bootloader, isn't it strange in that way? I also don't understand why rebooting the phone even rewrites an SD card.
Even the counter on the download mode is stuck on 2, no matter how many times I flash a kernel, rom, bootloader. Odin always reports a successfull upload...
Yep, thag sd card thingy is pretty weird and I have no ide what's causing that.
Sent from my sgs2 running cm9
Well,
I have researched a bit more and found this for the Nexus S:
http://forum.xda-developers.com/showthread.php?t=993403
This phone has exactly the same symptoms, but as the yellow triangle is on and it always boots into a rooted version, I would like to see if I can do anything so the phone can be sent back for warranty...
Any thoughts?
If you can .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Still problems use usb jig to set rom counter to zero .
Return to service centre .
Well,
Have tried everything, but no success. This is really weird, it's as if the whole phone had a backup and restores to this point on every reboot including sd card. Every odin flash comes out as "succeed", but nothing changes.
Will try to build a usb jig and test if it at least gets rid of the yellow triangle. I also can't flash anything via CWM as somehow the memory is "locked"... An external SD card is overwritten if inserted...
Regards

Need help think I bricked my GNote

Okay so I was updating my i717 from UCLF5 team perfection to UCLF6 Collective AoCP ROM and think I bricked my phone. T_T
I forgot that I had encrypted both the phone and external SD Card. When I went into CWM Touch 5.8.3.4 I hung on the formatting /cache I then forced reboot back into CWM and went through a manually formatted stuff and wiped the caches. I then went to install the zip ROM and it said read-only bad.. I didn't know what to do so I tried to factory wipe again and no luck. So I then thought well Odin could work, but I couldn't download the hotfile without hotfile host bugging out with too many downloads.. So I final find a default stock official ROM that is a tar that Odin v1.85 can use, but it is taking forever and I don't know if it will complete, it is currently stuck at "SetupConnection.."
I can get the phone into CWM Touch 5.8.3.4 and can get into download mode, but cannot do ****. The external SD card does still have my titan backup of all system apps all user data and all user apps on it. I know the password for the encrypted SD card. However I cannot do anything because it keeps say read-only....
I also for some reason probably me not being patient enough 3 flash counters on the phone. Now if I take the phone back to ATT to exchange or somehow get it un-bricked will I be able to return the flash counter to 0 before turning the phone in...or will I have to cross my fingers and hope that they don't see it lol?
Does anybody know the best way to go about fixing this phone? I don't really know how to use Odin well and since CWM seems to be hanging on reformatting /cache it won't ever finish getting the phone to factory by itself. I have also tried to fix the permissions but doesn't work. Also tried to mount into USB while plugged in and it didn't want to do that either.
I did notice that a couple times it did boot into the UCLF5 ROM that was previously on the phone but it was back to stock ICS theme with no apps but settings and couldn't use the USB mass storage it just kept cycling itself and not connecting.
Okay so I did infact get it on the third try to flash 2.3.6 android factory default back onto the phone and in the process lost CWM recovery and when I went back into the market place to reinstall ROM manager after I put the ROM I want onto the internal it won't connect to Google Play even after getting onto wifi...weird and even said there wasn't an update after trying to update through att to ICS stock...
Your not still rooted right? An official update won't install if you are
Sent from my SAMSUNG-SGH-I717 using xda premium
adramalech707 said:
Okay so I did infact get it on the third try to flash 2.3.6 android factory default back onto the phone and in the process lost CWM recovery and when I went back into the market place to reinstall ROM manager after I put the ROM I want onto the internal it won't connect to Google Play even after getting onto wifi...weird and even said there wasn't an update after trying to update through att to ICS stock...
Click to expand...
Click to collapse
>ok so you got up with GB correct?
>Why not just put CWM back on the touch CWM is very simple to use odin one file in the pda slot and click then put the ROM you wanted to install in your OP. Links are in my signature
>then you can put the AOCP, that you said originally
BTW if you are trying to put the Off ICS use kies while putting your phone in download mode, not sure what you are doing with/thru ATT
There are several thread around for this method.

[Q] Encryption prevents custom ROMs being used

OK so let me start off with, great site. I have read a ton of information.
First: Siyah 4.3.3 (Latest) Kernel which now has been put to AJK v1.48s
ROM; SHOstock3 v2.5.9
PreMod Settings: SGS2 AT&T SGH-i777. Started with GB > AT&T OTA (KIES) 4.0.3 > AT&T OTA WIFI 4.0.4 (caused huge freaking headaches with battery, charging, turn off the phone loop, battery draining, etc.)
Issues:
Original Issue posted in this thread (viewing Single Post) http://forum.xda-developers.com/showpost.php?p=39350619&postcount=18
Creepy offered something to try. That never worked as all I was able to do was download mode or stare at the Samsung Galaxy S2 Splash Screen. Well, I took to his download repository and other links and used his One-Click Recovery to stock GB Rom to make part of my phone usable, using this link here: http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
While it is Gingerbread at least my phone is usable. I want to try his STOCK ICS method but that mentions the eMMC super-brick bug.
So this is what I have tried so far. I have tried installing Siyah 4.3.3 nomswap for my kernel using Mobil-Odin Lite. That works but it never reboots or actually says finished. What it does do is stay at the wicked purple splash with the yin yang symbol. I left it like that last night until I woke up this morning and it never changed. So I rebooted the phone and the Kernel is on there. I reboot into recovery so that I can install SHOstock3 v2.5.9. That goes off flawlessly except here the last few times it won't reboot when I go to the GO BACK. It sticks and doesn't do anything. Rebooting shows the SHOstock3 Engine Boot Animation. Once it stops it goes to ask me for the encryption password. Well I put in my password (was the same one to the unlock screen) and it reboots and you see the nifty Samsung animation logo and then goes to the Samsung Galaxy S2 Animation Logo and then just stays there. It really pisses me off.
So after all that I finally put a new Kernel on there,AJK 1,48s. Pretty cool it loads up and then reboots. Well AJK shows up after the light-blue bar fills up and then goes black and the 4 touch sensitive row keys are lit up for a bit before going dark but the phone is still on. So I rebooted to recovery (CWM now with the Kernel) fixed tweaks, went to advanced and saw all sorts of options. Tried clearing caches for ROM 2 and restarting,no effect. I removed ROM 2 and went through reboot and nothing. Restored ROM 2 and nothing. Re installed SHOstock3 v2.5.9. Did the same thing after install and not backing out when I hit GO BACK. Rebooted, same scenario that happened before with requiring password. Entering password does the same thing with a reboot and then staying on Samsung Splash Screen. If I Don't enter the password and reboot,same thing happens. So after being irritated and pissed off I ran Creepy's One-Click Fix again and paid attention to the phone and noticed it mentioned not being able to access the AT&T section or partition or something like that. So while part of my phone works under normal circumstances I want to figure out how to remove that encryption part of the phone and get full access (even though full memory and space are shown under Windows 7 and the files on the phone). The password I put on there isn't taking and I don't know if using PC methods for removing encryption (which could take awhile I know) needs to be employed (and if so which methods) or if that part is just screwed and I can't put on any other kernels or custom ROMs. Perhaps tell me where I messed up. Should I try swapping the ROMs from Advanced setting in CWM Recovery? Can I try a different ROM (kernel didn't seem to help)? I have done several factory resets dalvik cache wipes cache wipes formats,etc. and it is still there. I can say that before the whole encryption debacle (even though I was encrypted I did get in my phone after encrypting it) my pin unlock for my SIM wouldn't work and I actually SIM locked my phone. Had to go to AT&T and get a new SIM and was up and running. I put a 4 digit pin lock for the SIM (it let me do it) and when I went to unlock it after a reboot, it wanted an 8 pin for the PUK and wouldn't take what I put. I tried to change the PIN but to no avail. Once that happened I guess it snowballed. Any help is appreciated. I have searched and tried some things that looked to match my issue but none have totally helped. I do have ADB set up on my wife's laptop which I use to restore my phone to GB Stock ROM. I haven't been able to reboot the phone into Bootloader to do any fastboot commands as when I tried to do it the commands just sent the phone into normal reboot (though adb reboot recovery does boot to recovery). I Haven't tried booting to the bootloader using the new Kernel though so I will wait for confirmation or additional information before I try. Thanks guys.
Eagle
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
creepyncrawly said:
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
Click to expand...
Click to collapse
Thank you so much creepy. I will give that a try later and see how it goes. I hope the information I gave actually gives enough info. I know folks usually want enough. Ill post back my findings.
Eagle
quick follow up and what I tried
creepyncrawly said:
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
Click to expand...
Click to collapse
Hey Creepy, I have a quick follow up and want to tell you what I have tried.
So I had already used Kies to move to AT&T v 4.0.4 ICS on my phone when I read your post. Rather than flashback again to GB I went ahead and put Siyah 4.3.3 on my phone. Went great, rebooted and installed quick and everything. Well I rebooted into recovery and went to mounts and storage and formatted the data and all that there and even formatted the secondrom data and all that. Did it a couple times to make sure everything was clean and good to go. Even put AJKs kernel on there after I ran the cleanrom script and it went flawlessly. I did factory resets and wipes and all that and installed SHOstock3 v2.5.9 and started up great. Well it got past the animation and the damn Password for encryption popped up. Well I put the wrong password in and it rebooted without the SAMSUNG screen and went through the boot ani and back to the password for encryption screen. I put the right password in, it reboots and you see the Samsung logo flash quickly and then it sticks on the Samsung Galaxy S2 Splash screen. I don't know what is holding it up from going forward unless when I messed up the first go around and it deleted everything if it didn't take out the bootload command or what have you. So I don't know if this idea will work but I am going to flashback to GB and put the siyah version on there that you linked and see if that will work.
One tihng, when Iencrypted the device the first go round, I onlydid the used data and area not the whole thing. Is this affecting it somehow? Any other ideas to try? I figured a full data format would remove the encryption but it never pops up saying all encryption will be removed. What I need is access to that area of the phone if I could just mount it on the computer. Is it possible after formatting the data, or before, that I should mount internal USB, DATA, etc and try another format/wipe or at least mount them to see if they can be used? Thanks for the help. For anyone else viewing this post (which actually is a lot) any help or ideas are appreciated. I am thinking I may need to format everything and get ahold of Samsung to see if they will reset my phone for me. I just wonder if the PIN lock on my SIM card that got locked when it wouldn't take my PIN didn't mess something up as well.
Eagle
WarEagleUS said:
Hey Creepy, I have a quick follow up and want to tell you what I have tried.
So I had already used Kies to move to AT&T v 4.0.4 ICS on my phone when I read your post. Rather than flashback again to GB I went ahead and put Siyah 4.3.3 on my phone. Went great, rebooted and installed quick and everything. Well I rebooted into recovery and went to mounts and storage and formatted the data and all that there and even formatted the secondrom data and all that. Did it a couple times to make sure everything was clean and good to go. Even put AJKs kernel on there after I ran the cleanrom script and it went flawlessly. I did factory resets and wipes and all that and installed SHOstock3 v2.5.9 and started up great. Well it got past the animation and the damn Password for encryption popped up. Well I put the wrong password in and it rebooted without the SAMSUNG screen and went through the boot ani and back to the password for encryption screen. I put the right password in, it reboots and you see the Samsung logo flash quickly and then it sticks on the Samsung Galaxy S2 Splash screen. I don't know what is holding it up from going forward unless when I messed up the first go around and it deleted everything if it didn't take out the bootload command or what have you. So I don't know if this idea will work but I am going to flashback to GB and put the siyah version on there that you linked and see if that will work.
One tihng, when Iencrypted the device the first go round, I onlydid the used data and area not the whole thing. Is this affecting it somehow? Any other ideas to try? I figured a full data format would remove the encryption but it never pops up saying all encryption will be removed. What I need is access to that area of the phone if I could just mount it on the computer. Is it possible after formatting the data, or before, that I should mount internal USB, DATA, etc and try another format/wipe or at least mount them to see if they can be used? Thanks for the help. For anyone else viewing this post (which actually is a lot) any help or ideas are appreciated. I am thinking I may need to format everything and get ahold of Samsung to see if they will reset my phone for me. I just wonder if the PIN lock on my SIM card that got locked when it wouldn't take my PIN didn't mess something up as well.
Eagle
Click to expand...
Click to collapse
Should I try TWRP instead of CWM and if so where should I grab it from?
Status Update
So this is what I have tried so far as of this moment.
I reflashed using your Stock + Root Gingerbread ROM.
Wiped DATA and everything in recovery menu several times.
Used Kernel Wipe and ROM Nuke for extra cleaning power.
Reinstalled the Kernel AJK and SHOstock3 ROM
Haven't installed any themes though I had Johns Blue and Villians Poison Base Theme (I believe that is what it is) on there when this all went down. Should I put them back on there?
Password still pops up. So what it looks like is that unless I stick with the unencrypted portion of the phone, I am screwed with any custom ROMs as the correct password has the phone restart and then stick at the Samsung Galaxy S2 Splash Screen. Apparently I still cannot access that area of the phones memory to wipe it at all no matter what I do. I need to access it somehow. Really driving me crazy and thinking I may need to talk with AT&T(as Samsung told me to earlier this morning lol) and see what they can do.
One thing I do notice is when I use your stock root program it actually removes the encryption or decrypts the section of the phone for the stock ROM to go on the phone which is cool.
Eagle
Any other things to try from anyone is greatly appreciated.
Been away all day. Sorry, I can't offer any other suggestions, but I have no experience with encryption. As you said, what you need to know is where the encryption is stored in memory so you can wipe or format that and restore it to original. If you can get to the right person, probably not level 1 tech support, then maybe you can find out. Somebody somewhere knows the answer to this.
would restoring my original EFS before this whole process help or is the encryption section totally blocked off?
WarEagleUS said:
would restoring my original EFS before this whole process help or is the encryption section totally blocked off?
Click to expand...
Click to collapse
I have no idea whether the encryption is stored there. What kind of efs backup did you take?
creepyncrawly said:
Been away all day. Sorry, I can't offer any other suggestions, but I have no experience with encryption. As you said, what you need to know is where the encryption is stored in memory so you can wipe or format that and restore it to original. If you can get to the right person, probably not level 1 tech support, then maybe you can find out. Somebody somewhere knows the answer to this.
Click to expand...
Click to collapse
Thx bro. yeah I need to run some forensic tools and see if I can mount the whole phone system on my PC and run the tools.
creepyncrawly said:
I have no idea whether the encryption is stored there. What kind of efs backup did you take?
Click to expand...
Click to collapse
a full efs backup. I made two or three actuakky using advanced efs, nitrality, and recovery.
WarEagleUS said:
a full efs backup. I made two or three actuakky using advanced efs, nitrality, and recovery.
Click to expand...
Click to collapse
A little research indicates that there is quite a bit of stuff stored in efs besides carrier specific data. So maybe encryption could be in there. Of those tools, nitrality for sure and maybe advanced efs should be able to restore the entire efs partition. If you are comfortable with the risk - a damaged efs would render the phone useless - then you might try this to see if it clears up the encryption issue. BTW, you should learn how to back up the efs partition yourself using terminal and linux commands.
creepyncrawly said:
A little research indicates that there is quite a bit of stuff stored in efs besides carrier specific data. So maybe encryption could be in there. Of those tools, nitrality for sure and maybe advanced efs should be able to restore the entire efs partition. If you are comfortable with the risk - a damaged efs would render the phone useless - then you might try this to see if it clears up the encryption issue. BTW, you should learn how to back up the efs partition yourself using terminal and linux commands.
Click to expand...
Click to collapse
Yeah I should have used ADB to do that from the get go. I should have used the wife's laptop like I started to instead of my WIN 8 machine has it seems to be finicky with Android SDK (the portion at least needed to run ADB). Linux commands really aren't much different than terminal and I have done both. I was actually trying to get fastboot commands to work but my bootloader wasn't cooperating and for the life of me I couldn't find how to unlock it. I may try restoring that EFS. If nothing else I would love to be able to format that EFS and replace it with my original copy though as you said a damaged EFS may actually cause issues (who knows if it is damaged). I do know that I am fixing to chat with AT&T support. I hope I don't have to drive down to Hoover, AL to the repair facility. I would rather them send me a phone and send this one back. I am on stock 4.0.4 ICS from AT&T and any root that may be on there (though I doubt there is now) I can remove and what not
Thanks for the advice and insight Creepy. I know you tried like hell to get me an answer but in doing research on here with other problems I found out some useful information going forward my friend.
Eagle
Well, looks like I will be getting a special early upgrade and the wife will as well. I will be keeping this phone, however, to mess with this and see if I cannot get this problem fixed. Thanks Creepy so much. I appreciate your research and help more than you know. If possible I would love to keep this thread open for a while just in case I figure this out and fix the issue. It may take me a week or so but I will get back to messing with it again.
A side note. You don't need the whole sdk to get adb. You can download just the files you need from my signature.
Sent from my SGH-I777 using xda premium

[Q] Hacked or not?

Hi there just wondered firstly if someone had hacked my android galaxy s3 would rooting it back to its original firmware wipe any hack that had been done?
And secondly - well basically the story is someone dodgy got hold of my s3 phone unlocked when I wasn't looking but they definitely did something on it. It might all be nothing but I did notice in one of the clipboards copy n paste windows the last one had this : *start. now I have searched for what this could be but I have had no luck - if anyone can guess that would be great too but in the mean time I guess I will root back to the original firmware and update to 4.1.2 again (After backing up stuff via kies). Thanks for any help! :laugh:
Mumraa said:
Hi there just wondered firstly if someone had hacked my android galaxy s3 would rooting it back to its original firmware wipe any hack that had been done?
And secondly - well basically the story is someone dodgy got hold of my s3 phone unlocked when I wasn't looking but they definitely did something on it. It might all be nothing but I did notice in one of the clipboards copy n paste windows the last one had this : *start. now I have searched for what this could be but I have had no luck - if anyone can guess that would be great too but in the mean time I guess I will root back to the original firmware and update to 4.1.2 again (After backing up stuff via kies). Thanks for any help! :laugh:
Click to expand...
Click to collapse
"Rooting" is not the correct term. You mean "restoring." Anyways, yes, restoring your device to stock will remove anything which they may have placed on your device.
It could easily be the code to a run a script so be careful. Restoring to stock would be a wise thing to do just to be safe .
Sent from my Nexus 4
thanks
And thanks again ...yer restored - I wiped factory reset and cache but not davik in download mode then flashed the original ROM started up and factory reset in android then wiped the external SD card too. Changed my main account passwords - hope I didn't forget one :S . I was just worried there might be a place to hide that does not get wiped but ill just have to go with this I guess thanks.
Mumraa said:
And thanks again ...yer restored - I wiped factory reset and cache but not davik in download mode then flashed the original ROM started up and factory reset in android then wiped the external SD card too. Changed my main account passwords - hope I didn't forget one :S . I was just worried there might be a place to hide that does not get wiped but ill just have to go with this I guess thanks.
Click to expand...
Click to collapse
Restoring to stock and erasing the SD card would remove anything which may have been placed, so there is no other place to "hide" anything. Cheers .
Sent from my Nexus 4

Flash and do factory reset on S2 with brickbug? (Want to return totally to stock)

Apologies for bringing up an old topic.
Basically I stopped messing with this phone ages ago and plan to buy a new one.
My S2 was softbricked after trying to use clockwork methods with a semi current rom.
I used the app that verifies my phone has the bad chip.
I managed to get it back to a semi-normal state but now I just want to use odin and flash it back completely stock
I also want to do a factory reset since I plan to sell it. Is there any way to do this?
I just want to stop reading about this since it is an old phone and I have exams coming up. Can someone advise me of the simplest method to turn the phone back to stock + erase all my data, and not brick it in the process?
m0b1liz3 said:
Apologies for bringing up an old topic.
Basically I stopped messing with this phone ages ago and plan to buy a new one.
My S2 was softbricked after trying to use clockwork methods with a semi current rom.
I used the app that verifies my phone has the bad chip.
I managed to get it back to a semi-normal state but now I just want to use odin and flash it back completely stock
I also want to do a factory reset since I plan to sell it. Is there any way to do this?
I just want to stop reading about this since it is an old phone and I have exams coming up. Can someone advise me of the simplest method to turn the phone back to stock + erase all my data, and not brick it in the process?
Click to expand...
Click to collapse
tell me more about which rom & kernel do you have running on your sgs2 right now and i might be able to help you
try considering triangle away zip file to remove the traces off your phone being rooted ever
and wipe cache
wipe dalvik cache
format intsd
mount& wipe preloads
step wise -
1) Open Chainfire's Triangle Away app and press "Reset flash counter" to reset the counter and remove the triangle. It does not matter if there is no triangle already.
2) Do a nandroid backup using Clockworkmod recovery if necessary (to get to it; turn off your phone, press the power button, volume up button, and home button at the same time and hold it down for a while). This is done so that you can restore your original OS like I would want to after getting my phone back from Samsung if you're restoring it for that sole purpose.
3) (Mandatory) Wipe Data/Factory Reset in recovery menu. IF YOU DON'T DO THIS, YOUR PHONE WILL BECOME STUCK ON THE "S" LOADING SCREEN. You also should wipe the cache partition and the internal SD card. The internal SD card in case you have any directories which may link you to rooting your phone, such as clockwork mod.
4) Restart into Download Mode and plug your phone into a windows computer.
5) Open Odin , click PDA, choose the STOCK kernel. Make sure that F. Reset Time, Auto Reboot and the PDA checkboxes are checked and NOTHING ELSE.
don't forget to hit thanks if i helped solve your issue

Categories

Resources