Related
Hey guys,
I'd like to return to stock samsung rom, resetting the device to factory setting (keep reading).
Reason for this is
1 I'am experiencing fastidious UI lags issue.
2 I've done several "Restore factory Setting/Wipe all data" and I can see folders of applications I installed at least three roms ago (and not installed anymore). Some of them are empty, some are not.
Maybe my device is just imploding bacause of the number of apps he keeps managing.
Maybe he doesn't like me anymore,
or maybe he is dying of cancer. :crying:
Info about my device:
Kernel: Siyah 1.8.9
1st ROM: Samsung 4.1.1
2nd ROM: CM10.1, 20120117 build
Goal:
I'd like to return to Stock Kernel with the stock 4.1.2 Samsung firmware.
So, how can I REALLY reset my device, starting againg form where I indicated?
domenicop said:
Hey guys,
I'd like to return to stock samsung rom, resetting the device to factory setting (keep reading).
Reason for this is
1 I'am experiencing fastidious UI lags issue.
2 I've done several "Restore factory Setting/Wipe all data" and I can see folders of applications I installed at least three roms ago (and not installed anymore). Some of them are empty, some are not.
Maybe my device is just imploding bacause of the number of apps he keeps managing.
Maybe he doesn't like me anymore,
or maybe he is dying of cancer. :crying:
Info about my device:
Kernel: Siyah 1.8.9
1st ROM: Samsung 4.1.1
2nd ROM: CM10.1, 20120117 build
Goal:
I'd like to return to Stock Kernel with the stock 4.1.2 Samsung firmware.
So, how can I REALLY reset my device, starting againg form where I indicated?
Click to expand...
Click to collapse
Anyone help????//??
The absolute cleanest way, is to do a mega wipe. Use Titanium Backup to save all the apps you want/need (NO SYSTEM APPS). Then, Factory Reset/Wipe Data, wipe internal sd card and wipe external sd (if you have one). Backup all pictures, photos and files you want on your pc first, then wipe everything. The Megawipe script can help you with this. Follow up by downloading one of the new 4.1.2 deodexed roms (Preferably LKC or LLA). You can keep the stock kernel or choose from my main 2 - Perseus Kernel or Yank kernel
Umh.. I'm not sure I got it.
First, I should remove Siyah kernel and the second ROM right?
How can I do it?
Will the Siyah Kernel be overwritten when I'll write the Stock Samsung 4.1.2 firmware?
domenicop said:
Will the Siyah Kernel be overwritten when I'll write the Stock Samsung 4.1.2 firmware?
Click to expand...
Click to collapse
Yes.
There is a sticky .
One run Triangle Away reset rom counter to zero .
Two flash your original saved stock rom Via Odin = wipes phone .
Three factory reset .
Four boot to download mode check status original and count is 0.
Boot phone settings about phone Status device status not modified .
Finally check there are no left over root apps on the phone .
jje
Need detailed info on this, anyone willing to help?
all the details are there for you to read
Thank you, anyway I'd like to advise that flashing via Odin doesn't format anything.
Step 0 is: Do a full data wipe (if you do it after triangle remover, I think counter will be incremented to 1, not tried though... )
domenicop said:
Thank you, anyway I'd like to advise that flashing via Odin doesn't format anything.
Step 0 is: Do a full data wipe (if you do it after triangle remover, I think counter will be incremented to 1, not tried though... )
Click to expand...
Click to collapse
Yes, yes, you are right, rest of the XDA community, with special attention to author of this are wrong, otherwise you have the headache and your nanny doesn't know what to do except from calling parents.
Would someone buy this kiddo a happy meal, please?
PS. Following the XDA RULES, especially search BEFORE posting, does not hurt.
Now im ****ed up! Im stuck at boot logo (samsung) need urgent help. it all happens after installing font installer. My phone was rooted. I want a clean format and i ended at this problem.
sometime flashing rom and than flah another rom may cause lag even the rom are really smooth. Try this, it work for me. Wipe Data, Cache Partition, Clear dalvike cache, format system and format preload. As far as i know, preload where it chaching framework. Sometime when flashing and keep flashing rom that different framework, the cache still there. that may cause lag.
zebroid said:
Now im ****ed up! Im stuck at boot logo (samsung) need urgent help. it all happens after installing font installer. My phone was rooted. I want a clean format and i ended at this problem.
Click to expand...
Click to collapse
That coz u replace roboto-bold. Lol. Im using JB multipack v3. It got quite font collection there. No bootloop. And yes, JB multipack replace roboto-bolt but no bootloop
zebroid said:
Now im ****ed up! Im stuck at boot logo (samsung) need urgent help. it all happens after installing font installer. My phone was rooted. I want a clean format and i ended at this problem.
Click to expand...
Click to collapse
If you want a clean install, without lags, I'd recommend not messing about with the fonts. Try running it stock for a while and see if your lags have gone, before fiddling with it.
Sent from my GT-I9300 using Tapatalk 2
What is all the complaining about? Do all of you complaining only have 1GB of RAM? Do you have windows animations turned off which also helps?
Sent from my 32GB Verizon Galaxy S III (SCH-1535) - stock (unrooted) JellyBean ROM with 64GB Class 10 MICROSDXC - using XDA Premium
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
hey there
i hope my phone is not bricked, but i've been looking now for two hours for a solution and haven't found anything.
I have a rooted GT-9100 with jelly bean 4.1.2 XWLS8 official Samsung Rom.
In the last few days i was having problems with many apps, especially the video player and the gallery app, which wouldn't start because there wasn't enough memory (even after having deleted all the trash files and dumpstate files).
as i had not made a data wipe after updating from xwssl to xwls8 (i rooted afterwards, i didn't want to reconfigure everything again), i wanted to make a backup before i would try the data wipe now.
So i made the backup with my Rom Toolbox pro on the sd card, rebooted the phone to recovery mode, wiped the data and rebooted the phone. as always the starter mode wanted me to select the language, which i did and then suddenly the screen went black.
It started to reboot and since then the phone is hanging in the Samsung Logo.
i've tried to wipe data, wipe cache partition, wipe kalvik, no success.
tried to restore from the backup i made this morning, says md5 mismatches.
what now? any suggestions?
kind regards skapo
Sent from my girlfriend's GT-S5830 using xda app-developers app
Back to ICS stock (not 4.0.4) via Odin (Get one from Samfirmware or AndroidFirmwares.net), that will give you a clean slate & you can go from there.
Edit - Or....Search on here for the md5 mismatch thing with your backup. There's been plenty of threads on here over the past 18 mths or so. Not sure if these methods work all the time (or even at all, I've never had the problem so never had to use them), but you might as well find the threads & see if any of the suggestions for fixes work for you. Could save you doing a clean install of stock & starting again (which will obviously be somewhat time consuming).
thx for the fast reply
why ics? isn't jb stable enough?
is there actually a pure rom like the nexus phone for the s2? i was wondering if the touchwiz from samsung might be responsible for so many problems...
Sent from my GT-S5830 using xda app-developers app
Worry about all that once you get the phone working normally again, this should be the only thing you're thinking about right now. First thing's first
yeah, you're right. i'll give it a shot i'll update this post tonight. thx
UPDATE:
Ok, i've reinstalled a ICS 4.0.3 I9100XXLPS, Buildnumber IML74K.XWLP7 (whatever this may be, where is the guide to the structure of Android and all the definitions, can't find any proper introduction).
It seems to work fine, but i had to wipe data and wipe cache partition, otherwise the phone still got stuck in the boot loop.
So what now? I've tested the root access, which of course isn't available anymore after flashing the ICS Stock ROM.
Do i need to install first a JB ROM with root access to (try to) restore from my backup or can i do it right from here rooting the ICS ROM?
Almost Solved
sKapo_daVinci said:
yeah, you're right. i'll give it a shot i'll update this post tonight. thx
UPDATE:
Ok, i've reinstalled a ICS 4.0.3 I9100XXLPS, Buildnumber IML74K.XWLP7 (whatever this may be, where is the guide to the structure of Android and all the definitions, can't find any proper introduction).
It seems to work fine, but i had to wipe data and wipe cache partition, otherwise the phone still got stuck in the boot loop.
So what now? I've tested the root access, which of course isn't available anymore after flashing the ICS Stock ROM.
Do i need to install a JB ROM first with root access to (try to) restore from my backup or can i do it right from here rooting the ICS ROM?
Click to expand...
Click to collapse
OK, i think i've got the problem solved:
The first thing i tried is to root the ICS and restore with the CWM. Interesting that this time it didn't give me any md5 mismatch, but it suddenly stopped during the process and the phone booted normally to ICS, in other words the restore didn't work.
So I downloaded the latest SGS2 JB I9100XWLSJ again (i had that one installed before the whole mess), i thought that the one i had installed before may have been corrupted. I flashed the ROM, wiped data, cache and dalvik cache and rooted the phone with Siyah. From there i tried to restore again, but again it stopped because of the md5 mismatch.
At least the new JB ROM booted successfully, which allowed me to access the backup file in the phone's internal sd with my PC.
I edited the nandroid.md5-file with notepad ++ and the md5 calculator. There's a good instruction from here. The folder distribution from the original instruction is a little bit confusing, that's why i've uploaded another one
I recalculated every md5 number for each file in the backup (except the nandroid.md5-file itseld of course and in some cases the .android_secure.img [i didn't have such a file]) and modified the md5 numbers inside the nandroid.md5-file.
That solved my problem :laugh: I was able to restore from my backup .
Even so, the video player app is still crashing. I restored my files and all the config, but with it the same problems i had before :crying:
Good work on finding a solution & posting it here, I'm sure it will help someone at some point in the future
Re: the FC's with the video player (which one ?), sounds like restoring it/it's settings is causing you problems. You might want to try clearing data on it first - go into settings/apps/all & select the app, then clear data; and if that doesn't work, uninstall it then do a clean install without restoring the app or settings. If the settings were backed up on ICS & you're currently using JB, that may be the cause of the FC's.
sKapo_daVinci said:
I edited the nandroid.md5-file with notepad ++ and the md5 calculator. There's a good instruction from here.
Click to expand...
Click to collapse
Thank you so much for bringing that thread to my notice! Could be useful in the future..:thumbup:
And good work solving it on ur own. XDA needs more guys like u!
If u do manage to solve all ur issues, please add [SOLVED] to the title of ur post, so that others too may benefit from ur solution.
"To err is human, to forgive is divine"
Sent from my SGS II
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!
Hi
I have bricked my samsung galaxy tab 7 v2.2
I followed some stes found here
I rooted the phone , I noticed I had superuser icon
with odin selected pda & file CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS
Everything seemed to go alright but now the phone is in a constant loop with funny coloured lines all over the screen.
Please can some one help
Cheeers
Des
beags64 said:
Hi
I have bricked my samsung galaxy tab 7 v2.2
I followed some stes found here
I rooted the phone , I noticed I had superuser icon
with odin selected pda & file CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS
Everything seemed to go alright but now the phone is in a constant loop with funny coloured lines all over the screen.
Please can some one help
Cheeers
Des
Click to expand...
Click to collapse
Do you have a Custom Recovery? Ex: CWM,TWRP, etc
If he used the CF Autoroot, then not likely he has recovery. Best bet will be to reload the stock OS via Odin to get back to normal. You need to make sure you get the right version of the firmware though because there are different variants of the tab.
es0tericcha0s said:
If he used the CF Autoroot, then not likely he has recovery. Best bet will be to reload the stock OS via Odin to get back to normal. You need to make sure you get the right version of the firmware though because there are different variants of the tab.
Click to expand...
Click to collapse
Thanks Guys.
I don't have any recovery unfortunately. I have tried the 2 optus versions of 2.2 that i found here
but both of them just put the phone / Tab in a loop at the Samsung start up screen.
Any idea where I could find some more to try
GT-p1000 originally optus in australia firmware around 2011 I think cant be sure
Appreciate all the effort
thanks
Des
Did both versions cause lines on the screen, or just not being able to boot? It's not uncommon to need to do a factory reset after restocking with Odin, but if the screen was having issues too then that is most likely something to do with the bootloaders. Try doing a factory reset, then pull the battery, then boot into download and install the latest 2.3.6 for your tablet: http://www.sammobile.com/firmwares/3/?download=8303 . You might have to sign up, sorry, but it's the official version specifically for what you need and if your screen flickering issue IS bootloader related, then this will cure that as well.
Both rom caused the lines & I was unable to read anything in order to do the reset.
I had afriend work on this over Easter & he managed to get it working & installed kit kat my problem now is the resolution is to high
thanks for your assistance
Cheers
Beags
beags64 said:
Both rom caused the lines & I was unable to read anything in order to do the reset.
I had afriend work on this over Easter & he managed to get it working & installed kit kat my problem now is the resolution is to high
thanks for your assistance
Cheers
Beags
Click to expand...
Click to collapse
I just tried to change "ro.sf.lcd_density=160" to 240 as the screen did not look to good with tasker widgets.
It could not save so I followed he instruction to give full root access.
after changing the value it went to save for awhile then said failed.
After that the "Build.prop" was empty.
Now the phone is stuck on the Cyanogen mod front screen.
Is there a way to get back the "Build.prop" or how can I restore it?
Cheers
Beags
Easiest way is just going to be to reinstall the rom, if it is still on your storage. If you just wipe the cache and dalvik cache then reflash rom and Gapps, you should be back to normal without needing to factory reset. There are build prop editor apps in the Play Store. Would probably be a bit easier and make sure to save it correctly for you.
Out of curiousity - the lines on the screen was a bootloader issue, I'm assuming?
help and sorry!!
sorry beags64 for posting this in yours but i need a help!i have a bricked mT6573 Chang jiang G22 (one SIM) and i didn't found any compatible stock ROM for it,i can download (micromax A50,A75 into it) 100% but nothing else than black screen and vibrating!so do you know where can i find a rom for it?!thanks
techlie said:
sorry beags64 for posting this in yours but i need a help!i have a bricked mT6573 Chang jiang G22 (one SIM) and i didn't found any compatible stock ROM for it,i can download (micromax A50,A75 into it) 100% but nothing else than black screen and vibrating!so do you know where can i find a rom for it?!thanks
Click to expand...
Click to collapse
You need to start your own thread.
Yes the rom was still in storage so I reinstalled as suggested & everything back as I left it.
Thanks heaps
beags64 said:
Yes the rom was still in storage so I reinstalled as suggested & everything back as I left it.
Thanks heaps
Click to expand...
Click to collapse
Welcome! Glad all is well.