Hi Guys,
I've been a long time lurker but I have finally registered to ask an important question (well to me anyway)
I fixed one of my friends' LCD and got it working. It turned on and went to the lock screen, all buttons worked but I could not do anything else as there was a password. So today I returned the phone back to him and he about half an hour later he told me he could not get pass the "S" boot logo.
I don't think that I had broken anything while fixing the phone as it booted up successfully multiple times and it is a genuine lcd. So what do you guys think? From previous testing I know that I can get into recovery and download mode so do you think I should factory reset the phone? Will that fix it? From experience I know that some phones are sometimes problematic and require a factory reset after even a general repair. However, he does not have a backup of any of the data and I don't think he would like to lose any data. Is there anyway to get pass this?
I also don't know what firmware it is on nor if it is rooted.
Sounds like a factory reset seems to be the way to go.
Before you reset though, I'd recommend flashing a custom recovery to create a back up of all the data, or just the /data partition. If the factory reset fixes the problem then you can either flash parts of the back up one by one and test for boot loops, or you can search for a back up explorer and just copy out what you need.
amcgavin said:
Sounds like a factory reset seems to be the way to go.
Before you reset though, I'd recommend flashing a custom recovery to create a back up of all the data, or just the /data partition. If the factory reset fixes the problem then you can either flash parts of the back up one by one and test for boot loops, or you can search for a back up explorer and just copy out what you need.
Click to expand...
Click to collapse
Good thinking..
But if the device was not rooted, how would he root (and install a custom recovery) without knowing what firmware it is on?
@OP:
I do not know what caused the issue, but when your phone is stuck at the boot logo, the first thing to try is a factory reset.
immortalneo said:
Good thinking..
But if the device was not rooted, how would he root (and install a custom recovery) without knowing what firmware it is on?
Click to expand...
Click to collapse
Is it necessary to know what the firmware is? When rooting my s2 I installed the custom recovery through odin first, and then installed root through through there. No need to know the firmware!
amcgavin said:
Is it necessary to know what the firmware is? When rooting my s2 I installed the custom recovery through odin first, and then installed root through through there. No need to know the firmware!
Click to expand...
Click to collapse
Then you might wanna try that first.
"To err is human, to forgive is divine."
Sent from my SGS II
Related
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
I'm guessing the infamous brick bug is responsible.
What was your configuration before flashing the new ROM?
What ROM and kernel?
Sent from a GT-I9100 having a mind of its own
TechnicallyImpaired said:
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
Click to expand...
Click to collapse
I'm sorry bro but you might have suffered from the infamous super brick bug and your inability to read.
Solution:
Package the phone and send it to Samsung repair center
Swyped from Samsung Galaxy SII
TechnicallyImpaired said:
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
Click to expand...
Click to collapse
No offense to the two responders above me, but you can ignore them.
The problem is that you attempted to flash a firmware not meant for your phone.
You yourself said you have an SGH-I757. Well, that ICS ROM you linked that you tried to flash is for the GT-i9100. The two models have different hardware, so firmwares, kernels, and ROMs are NOT compatible between them.
This probably screwed up the bootloader. Your only course of action at this point will probably be either JTag repair, or sending it to Samsung for repair.
ctomgee said:
No offense to the two responders above me, but you can ignore them.
The problem is that you attempted to flash a firmware not meant for your phone.
You yourself said you have an SGH-I757. Well, that ICS ROM you linked that you tried to flash is for the GT-i9100. The two models have different hardware, so firmwares, kernels, and ROMs are NOT compatible between them.
This probably screwed up the bootloader. Your only course of action at this point will probably be either JTag repair, or sending it to Samsung for repair.
Click to expand...
Click to collapse
Thanks for not being a douche bag in your response, much appreciated. Thanks for the info BTW, I just got myself a new one and I'll be more careful now. My biggest annoyance with native ICS on this phone is one is looks like gingerbread and two it comes with a tonne of bloatware that you can't remove without rooting ect. At this point should I flash CWM again since it installed successfully last time, root, and use that as a method to remove the unwanted bloatware. I'm so hesitant to flash this phone now, it seems it was much ease on my SGS1.
TechnicallyImpaired said:
Thanks for not being a douche bag in your response, much appreciated. Thanks for the info BTW, I just got myself a new one and I'll be more careful now. My biggest annoyance with native ICS on this phone is one is looks like gingerbread and two it comes with a tonne of bloatware that you can't remove without rooting ect. At this point should I flash CWM again since it installed successfully last time, root, and use that as a method to remove the unwanted bloatware. I'm so hesitant to flash this phone now, it seems it was much ease on my SGS1.
Click to expand...
Click to collapse
Just make sure you stick to flashing things meant for your model. Those things compatible with your device will be clearly labeled with the model number.
Problem is the SGH-i757 doesn't have its own forum, so stuff for it gets posted in here.
ctomgee said:
Just make sure you stick to flashing things meant for your model. Those things compatible with your device will be clearly labeled with the model number.
Problem is the SGH-i757 doesn't have its own forum, so stuff for it gets posted in here.
Click to expand...
Click to collapse
Yup, I've found a few but I also have a few questions maybe you can help me with. According to this thread ( http://forum.xda-developers.com/showthread.php?t=1756242) only stock ICS v 4.0.4 is effected by this superbrick. The SGS2 I hardbricked earlier today was updated to this version via keys to 4.0.4 before installing the custom ROM. So provided I stick to ROMS such as lets say the one here (http://forum.xda-developers.com/showthread.php?t=1740188) and avoid upgrading to 4.0.4 I should be able to CWM + Flash + Root correct? I should also be able to do the standard factory reset / wipe cache / wipe dalvik? I also used the eMMC Brickbug Check app in the first post I liked under how to AVOID the superbrick and it came up saying my chip was sane. Thanks in advance and also I pressed the thank you button
TechnicallyImpaired said:
Yup, I've found a few but I also have a few questions maybe you can help me with. According to this thread ( http://forum.xda-developers.com/showthread.php?t=1756242) only stock ICS v 4.0.4 is effected by this superbrick. The SGS2 I hardbricked earlier today was updated to this version via keys to 4.0.4 before installing the custom ROM. So provided I stick to ROMS such as lets say the one here (http://forum.xda-developers.com/showthread.php?t=1740188) and avoid upgrading to 4.0.4 I should be able to CWM + Flash + Root correct? I should also be able to do the standard factory reset / wipe cache / wipe dalvik? I also used the eMMC Brickbug Check app in the first post I liked under how to AVOID the superbrick and it came up saying my chip was sane. Thanks in advance and also I pressed the thank you button
Click to expand...
Click to collapse
The brick bug may not affect you at all. The most common Galaxy S2 affected is the i9100, which we have established is NOT your device. And you already used the app that said your chip is "sane", so it's confirmed you don't have to worry about it.
Again, you bricked the device by flashing a ROM meant for a different device. Had nothing to do with the brick bug.
ctomgee said:
The brick bug may not affect you at all. The most common Galaxy S2 affected is the i9100, which we have established is NOT your device. And you already used the app that said your chip is "sane", so it's confirmed you don't have to worry about it.
Again, you bricked the device by flashing a ROM meant for a different device. Had nothing to do with the brick bug.
Click to expand...
Click to collapse
Thanks, I wasn't aware flashing a rom not meant for your device can cause a hard brick to the point where you cant turn anything on and no buttons are responsive ect. Thanks for the help.
New here. (also apologies for probable duplicate topic)
I've rooted a phone in the past with no problem. This time round was with an S2, and I flashed an insecure kernel on it, got a green pass on Odin however it's now stuck on the boot screen with the yellow triangle.
I can access recovery mode and download mode but it will never boot properly, always stuck on the yellow triangle. What's the best course of action from here?
Need a lot of help with this guys as I'd rather not have a bricked phone ><
ikradex said:
New here. (also apologies for probable duplicate topic)
I've rooted a phone in the past with no problem. This time round was with an S2, and I flashed an insecure kernel on it, got a green pass on Odin however it's now stuck on the boot screen with the yellow triangle.
I can access recovery mode and download mode but it will never boot properly, always stuck on the yellow triangle. What's the best course of action from here?
Need a lot of help with this guys as I'd rather not have a bricked phone ><
Click to expand...
Click to collapse
Seriously dude? Use some common sense please and give relevant information on what you have. What model/variant do you have, rom are you on, what kernel have you flashed?
How do you expect anybody to be able to help you if you dont give such basic info???
Are you sure the kernel supports the rom/version you have installed?
ikradex said:
New here. (also apologies for probable duplicate topic)
I've rooted a phone in the past with no problem. This time round was with an S2, and I flashed an insecure kernel on it, got a green pass on Odin however it's now stuck on the boot screen with the yellow triangle.
I can access recovery mode and download mode but it will never boot properly, always stuck on the yellow triangle. What's the best course of action from here?
Need a lot of help with this guys as I'd rather not have a bricked phone ><
Click to expand...
Click to collapse
Maybe because you wiped all data....so...there's no ROM to boot up to.
Try flashing one via Odin
gastonw said:
Maybe because you wiped all data....so...there's no ROM to boot up to.
Try flashing one via Odin
Click to expand...
Click to collapse
Wiping data doesnt wipe rom , It just wipes appdata, ie settings etc. All that happens is a factory reset so when you next boot its back to default. For example you would need to re-enter google account and re-install apss either manually or from a backup.
You can only wipe rom by formatting system partition.
TheATHEiST said:
Wiping data doesnt wipe rom , It just wipes appdata, ie settings etc. All that happens is a factory reset so when you next boot its back to default. For example you would need to re-enter google account and re-install apss either manually or from a backup.
You can only wipe rom by formatting system partition.
Click to expand...
Click to collapse
Thought you had me in ignore.
So there's no way you can wipe your OS via recovery? Good to know that, it's like ROM over ROM then. The new one clears the old one.
gastonw said:
Thought you had me in ignore.
So there's no way you can wipe your OS via recovery? Good to know that, it's like ROM over ROM then. The new one clears the old one.
Click to expand...
Click to collapse
I did have you on ignore but I still see little boxes saying this comment has been ignored etc which was actually more annoying so I removed ignore.
Yes you can wipe OS via recovery but only by formatting system/deleting partition etc. All the "wipe" options do is remove files that have been created by rom like app settings/cache etc.
Your confusion was probably also the reason why you made a big thing in a previous topic about you trying to avoid wiping data, because you thought it wiped rom? :silly:
Wiping data/factory reset in cwm is one of the best ways to get rid of system issues, Its basically like doing a clean install of Windows on a PC. After you have wiped you can simply restore your needed apps from a backup using Titanium Backup. Other things like sms/mms etc can be also backed up easily and contacts will be synced via Google account.
TheATHEiST said:
I did have you on ignore but I still see little boxes saying this comment has been ignored etc which was actually more annoying so I removed ignore.
Yes you can wipe OS via recovery but only by formatting system/deleting partition etc. All the "wipe" options do is remove files that have been created by rom like app settings/cache etc.
Your confusion was probably also the reason why you made a big thing in a previous topic about you trying to avoid wiping data, because you thought it wiped rom? :silly:
Wiping data/factory reset in cwm is one of the best ways to get rid of system issues, Its basically like doing a clean install of Windows on a PC. After you have wiped you can simply restore your needed apps from a backup using Titanium Backup. Other things like sms/mms etc can be also backed up easily and contacts will be synced via Google account.
Click to expand...
Click to collapse
hum...okay.
I actually know what Factory Reset does, I mean..."factory"..."reset", kinda......gives it away.
And yes, it made sense to me that you could wipe the ROM you are on before installing a new one, just like the format c:/s days in win98.
You learn something every day, speaking of which, how come no one recommends noobs to root their device with exynos abuse? It's because they're noobs and wouldn't be able to handle/understand the exploit?
I still don't do factory resets because I don't need to, and I avoid needing to perform it.
TheATHEiST said:
Seriously dude? Use some common sense please and give relevant information on what you have. What model/variant do you have, rom are you on, what kernel have you flashed?
How do you expect anybody to be able to help you if you dont give such basic info???
Are you sure the kernel supports the rom/version you have installed?
Click to expand...
Click to collapse
Thanks for the reply Figured if someone was willing to help me I'd give them the information they wanted.
Have Samsung Galaxy S II (GT-I9100) (couldn't tell you what "variant" it is). I was following this guide. It told me to get an insecure kernel from here. The guide said it didn't really matter which kernel I picked so I picked the first one (GT-I9100_BGKF5_insecure) and used Odin to flash it. Got a green pass and the phone began reboot but it's now stuck on the yellow triangle (the warning message that you've flashed an insecure kernel).
I couldn't tell whether there would be compatibility issues as the thread just seems to be one big list of kernels and nothing else. AFAIK the phone was running ICS.
Looking at the replies, I keep seeing factory reset. Is that a liable option to restore my phone back to its original state. I don't care as long the phone works again. If not can someone run through how to fix my predicament I heard if I can access download and recovery mode I should be able to fix it.
ikradex said:
Thanks for the reply Figured if someone was willing to help me I'd give them the information they wanted.
Have Samsung Galaxy S II (GT-I9100) (couldn't tell you what "variant" it is). I was following this guide. It told me to get an insecure kernel from here. The guide said it didn't really matter which kernel I picked so I picked the first one (GT-I9100_BGKF5_insecure) and used Odin to flash it. Got a green pass and the phone began reboot but it's now stuck on the yellow triangle (the warning message that you've flashed an insecure kernel).
I couldn't tell whether there would be compatibility issues as the thread just seems to be one big list of kernels and nothing else. AFAIK the phone was running ICS.
Looking at the replies, I keep seeing factory reset. Is that a liable option to restore my phone back to its original state. I don't care as long the phone works again. If not can someone run through how to fix my predicament I heard if I can access download and recovery mode I should be able to fix it.
Click to expand...
Click to collapse
Of course, you're not bricked yet.
Before trying your back up, why don't you flash a stock ROM via odin and take a long breath?
This is JB leak.
These are ICS, look for 4.0.3 unbranded.
gastonw said:
Of course, you're not bricked yet.
Before trying your back up, why don't you flash a stock ROM via odin and take a long breath?
This is JB leak.
These are ICS, look for 4.0.3 unbranded.
Click to expand...
Click to collapse
I know this is leading onto another thread but my phone now is having trouble connecting to my computer. Keep getting "USB not recognized" error. Installed/Uninstalled kies & drivers then installed drivers again alone and still won't recognize it
Tried another usb port? another pc/laptop? sure kies is not running in background? reinstalled kies?
Don't worry, your pc WILL see your device.
Sent from the little guy
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
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!
I recently tried to re-install root on my device. I used the link below to root:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Everything worked fine, my phone rebooted normally, said it was rooted and I went on my day. Later that day I rebooted my phone and now it wont start up. It just pauses at the verizon logo and never gets past that. I can get into the default LG recovery, but I don't know how much I can really do there.
I really need to recover some of my files, contacts, etc. If I could just fix the issue without losing data that would be better, but at the very least I need to save some files from my phone. Any ideas?
EDIT: I have done some research and found I can fix my issue if I'm able to get my phone to be recognized by my computer. For some reason the MTP USB Device driver fails the install...
Have you gotten into recovery and tried to wipe the cache?
If you can get into the stock recovery you should be able to choose wipe cache and it will take you to twrp if you have it flashed onto your phone. From there you can restore or wipe the cache and see if that helps.
Exact problem
My s3 is soft bricked and i need all my information back, would pay for help
Majnuel said:
My s3 is soft bricked and i need all my information back, would pay for help
Click to expand...
Click to collapse
Your hit there's no way to recover information from a soft/hard brick requires a factory flash