Related
I've tried more than twice now, and I'm sure it's something simple, but I can't recover my backup. Last night for example, wanted to try another rom, a 2.3.4, I was quite happy with my mosaic setup, as usual, and I was running xcal's 2.0 kernel without issue so I backed up through cwm 3. Flash got me into a bootloop so I tried to recover the nandroid but it wasn't the right one. I chose the right date but the b/u was the rom that failed, the bootup screen. So I had to start from scratch to get the setup I liked. Of course when I tried to flash the new rom there were different kernels etc. But that shouldn't matter should it. What am I doing wrong? Thanks ahead of time.
Sent from the frozen tundra known as Canada.
Do you're trying to restore a 2.3.3 backup (Mosaic) to a 2.3.4 rom?
*phone sig* If you're not on Gingerbread you should be flogged! *
Uh, no. you misunderstood.
Sent from the frozen tundra known as Canada.
Those back ups are not to use to recover with. Those are to restore your set up and stuff, you flash the rom it was backed up from THEN restore and its like you never flashed the the other rom.
studacris said:
Those back ups are not to use to recover with. Those are to restore your set up and stuff, you flash the rom it was backed up from THEN restore and its like you never flashed the the other rom.
Click to expand...
Click to collapse
Thanks studacris, yeah, tried that and got an error message and couldn't restore. Sorry I didn't take the message down, I'll try again if it happens again, thanks.
Sent from the frozen tundra known as Canada.
Before you flame, I did read this and was still a bit confused.
Basically, I've been using my Verizon-ROM'd Charge (with the latest updates) for about a month now. I'm ready to ODIN over to a new ROM (probably the 8/3/11 HumbleComb ROM), but without a one-click root, I'm not sure how I can install/run/backup all my data with TB if I don't have root access.
So right now, I'm looking for any way to root my Charge, backup all the apps/data before I flash a ROM that seems (from my reading) to do a full wipe.
The other problem I'm having is in regards to my wife's Charge. We both came from Vibrants and she had quite a few important apps (with critical data) she'd like to bring over. However, she could care less about going to a rooted/aftermarket ROM. She just wants her old apps to work.
I've searched fellas... I'd really like some help on this. Please throw me a line... even if it's a link to a thread I missed.
Thanks in advance.
Wrong section but just odin this kernel, it doesnt wipe any of your data. Then you can use Titanium Backup or whatever you use to backup your apps. Dont restore system apps unless you want force closes.
http://forum.xda-developers.com/showthread.php?t=1092114
Nevermind...
mbh87 said:
Wrong section but just odin this kernel, it doesnt wipe any of your data. Then you can use Titanium Backup or whatever you use to backup your apps. Dont restore system apps unless you want force closes.
http://forum.xda-developers.com/showthread.php?t=1092114
Click to expand...
Click to collapse
Awesome! I'll give it a try and see how it goes. I appreciate the helps.
**EDIT**
That worked perfectly. Thanks! Backing up everything with TB now in preparation for flash a real ROM.
Mods, please move as necessary.
most roms nowadays will root you when flashed/odined so yeah just back everything up and load up the rom of your choice
blazing through on my VZ Droid Charge 4G
Things were going so well, I decided to flash HumbleComb 1.5 using Odin. Now I'm stuck at the Samsung logo. I'm guessing it was because the tool originally recommended here enabled the lagfix. Funny thing is, if I reflash HC 1.5 from Odin, the first thing I get is the recovery screen. Inside the voodoo settings there, it says Voodoo is disabled and not scheduled to be enabled on the next boot (this was after the 2nd flash, though). Voodoo had to be enabled. I got a 1400+ quadrant score...
Gotta read the "fix your phone" thread now. Was too tired to fart around with it last night. At least I got everything backed up.
Flapjack said:
Things were going so well, I decided to flash HumbleComb 1.5 using Odin. Now I'm stuck at the Samsung logo. I'm guessing it was because the tool originally recommended here enabled the lagfix. Funny thing is, if I reflash HC 1.5 from Odin, the first thing I get is the recovery screen. Inside the voodoo settings there, it says Voodoo is disabled and not scheduled to be enabled on the next boot (this was after the 2nd flash, though). Voodoo had to be enabled. I got a 1400+ quadrant score...
Gotta read the "fix your phone" thread now. Was too tired to fart around with it last night. At least I got everything backed up.
Click to expand...
Click to collapse
Wipe everything in recovery (data/cache/dalvik) and then plug into Odin and flash. That works every time for me when it sticks on the Samsung logo...
So I left Apple, came to Android, rooted my VZW GS3. First time I've ever done anything like this, so I'm new to it. I backed up EVERYTHING using TiBu, did the IMEI backup, Full system/image backup using CWM, unlocked bootloader, etc. Then I flashed to Synergy r46 (august 20th - yesterday's release).
Now I'm at work and my back-up pulled my contacts via Verizon's server, but how do I get back EVERYTHING else? SMS/MMS logs, call logs, apps, app data, etc? Do I need to download TiBu again (fresh from google market) and then load my backups off my Ext-SD card, or what? I guess I'm a bit confused as to where my TiBu items were even stored/saved...I assume it was the ExtSD card, otherwise I would have lost them all upon flashing to Synergy, correct?
Any help to get all my apps and data back on my newly Synergized phone would be awesome!!!! Thanks in advance!!!
Yes download titanium and then point it to the directory you had your back ups saved to (its sd card by default, and which is your phone storage btw) then tab to backup/restore click the check, then once your app data populates, and select run next to restore apps and data.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 02:56 PM ---------- Previous post was at 02:55 PM ----------
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Sent from my SCH-I535 using Tapatalk 2
I used titanuium backup pro to back up all my Apps and system data. And when I flash a new rom I just redownload titanium pro and it automatically restores all my Apps and system data. It is the easiest app I have used. So to answer ur question.....back up ur apps with titanium then after flashing a new rom go and redownload titanium and restore your system data and apps or just apps alone if that's what u prefer? Does that answer ur question or would u like more detailed instructions?
Sent from my SCH-I535 using xda app-developers app
Welcome to android!
Sent from my SCH-I535 using Tapatalk 2
Another very nice feature of Titanium Backup is its ability to pull data from CWM nandroids. There have been a few times where I was quick to flash a new rom without doing a backup of my apps. This has saved me much time from having to re-flash the nandroid backup, backup via TB, then re-flash to the new rom.
voodoomanx said:
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Click to expand...
Click to collapse
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Weioo said:
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Click to expand...
Click to collapse
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
dan_joegibbsfan said:
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Click to expand...
Click to collapse
I'm fairly certain I did "wipe data/factory reset," I just wasn't sure how it was labeled when I typed that out, but that's really ringing a bell. I think I may have gotten the errors before (using ROM Manager) because I hadn't factory reset? Seems to me I'm good to go! However, my question regarding TiBu still remains.
Edit: In regards to informing you about r46, I'm not sure what to report as I've never used a previous Synergy and have no idea how to compare, other than to the rooted stock ROM. I have heard reports of battery life being worse than the stock ROM, and I can confirm this. I've barely used the phone since I flashed to Synergy and it's dropped 15% battery life in ~3 hours. Seems faster than before but I'm unsure.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
dan_joegibbsfan said:
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
Click to expand...
Click to collapse
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I used the EZ-unlock app in the play store. I did see that a custom kernel was loaded however when i flashed back to my nandroid (stock rooted) I am back on the orignal kernel. Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I agree I have yet to have Synergy boot loop although I'm still on 1.7. I would try to wipe cache and dalvik cache and see if that helps or you could be over clocking to high.
Sent from my Transformer TF101 using xda premium
nguyenvn said:
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
Click to expand...
Click to collapse
I don't know the answer to that specifically. All I know was that I was stable before another modification I made (that said it wouldn't work but I tried it anyway). Since restoring from backup and reloading Synergy and theme I have not seen any weird rebooting anymore.
nguyenvn said:
Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
Click to expand...
Click to collapse
I'm not familiar with that method. I've only used Odin, even when I did have to redo everything I used Odin to stock de-bloated rooted .md5 then CWM'd from there.
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
nguyenvn said:
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
Click to expand...
Click to collapse
That may very well be the issue. 1.9ghz is a very aggressive overclock, and i wouldn't be surprised if was unstable on a good number of phones. Synergy's supposed to boot at 1.5ghz max by default - I don't know whether that was successfully implemented. I personally think it's silly to OC such a capable phone, anyway. Back in the days of the Droid 1, an overclock from the stock 550mhz to 800mhz-900mhz was an enormous improvement. Today, the only thing OCing the S3 gets you is a <10% improvement in Quadrant, more heat, possible instability, and no perceptible difference outside of those silly synthetic benchmarks.
Anyway, in this thread, there seems to be a fair bit of confusion as far as what's what in the android partitions. I'll give you a short rundown.
"aboot" is what's referred to here as the bootloader. It checks to see whether the next partition in the boot sequence, "boot", is authorized. When you unlocked your bootloader, you overwrote aboot with a version that does not perform that check.
"boot" contains your kernel. If your ROM has a custom kernel, it contains a boot.img to overwrite boot.
"system" is the meat of the OS. This is primarily what ROMs flash.
"data" contains all of your apps and settings. When you perform a factory reset, you're reformatting data. If you're flashing a ROM that is significantly different from what you're on now, some of those old settings and data can cause errors, force closes, random reboots, and boot loops. When in doubt, wipe data before flashing a new ROM. When going from one version of a ROM to a newer, very similar version of the same ROM (nightly to nightly), you probably don't need to wipe data, but make a backup just in case. dalvik-cache is also in data; if you wipe data, you've automatically wiped the dalvik cache. It's redundant to wipe data and then wipe dalvik cache.
"cache" is just that, the cache partition. Clearing it won't make you loose anything, at least not anything Android won't silently replace.
So far it seems to be pretty stable on r50. I installed system tuner and brought it down to 1.5 Ghz. I'm not sure why 1.9 is set to default. Doesn't seem like a good idea to me. Thanks all for the help/advice.
i've been using CWM recovery and CM nightlies. they've been just fine. today i restored a two day old backup, as i didn't care for the current nightly.
now the phone black screens after the samsung splash.
i've tried:
factory reset
wipe dalvick/cache
restoring other backups
flashing other nightlies
and the phone will boot for the first time, but if i select 'reboot' or 'power down' on the next boot it's only a samsung splash, then black screen (no cm splash, no response from buttons input), and will not boot again.
what's the problem ?
ohgood said:
i've been using CWM recovery and CM nightlies. they've been just fine. today i restored a two day old backup, as i didn't care for the current nightly.
now the phone black screens after the samsung splash.
i've tried:
factory reset
wipe dalvick/cache
restoring other backups
flashing other nightlies
and the phone will boot for the first time, but if i select 'reboot' or 'power down' on the next boot it's only a samsung splash, then black screen (no cm splash, no response from buttons input), and will not boot again.
what's the problem ?
Click to expand...
Click to collapse
Happens once in a while when you flash over a back up.
Try making a clean flash.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Somcom3X said:
Happens once in a while when you flash over a back up.
Try making a clean flash.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Click to expand...
Click to collapse
i've done that. right now, i've wiped everything, and then flashed a nightly, and it will not reboot !
it will only boot the -one- time directly after flashing a new rom. any reboot attempts after that means it freezes, or fails, with a black screen directly after the samsung splash.
what have i missed ?
ohgood said:
i've done that. right now, i've wiped everything, and then flashed a nightly, and it will not reboot !
it will only boot the -one- time directly after flashing a new rom. any reboot attempts after that means it freezes, or fails, with a black screen directly after the samsung splash.
what have i missed ?
Click to expand...
Click to collapse
Try installing Samsung firmware via Odin. Root it and try again. Wouldn't hurt to try.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Somcom3X said:
Try installing Samsung firmware via Odin. Root it and try again. Wouldn't hurt to try.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Click to expand...
Click to collapse
could you point me to a specific samsung firmware, or is there only one ?
ohgood said:
could you point me to a specific samsung firmware, or is there only one ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=24660137
Make sure repartition is always unchecked in Odin
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
ohgood said:
could you point me to a specific samsung firmware, or is there only one ?
Click to expand...
Click to collapse
Check out this post from the brick fix thread.
http://forum.xda-developers.com/showpost.php?p=44626072&postcount=117
The full fix thread
http://forum.xda-developers.com/showthread.php?t=1591601
Sniped lol
i've wiped everything. flashed back to stock via odin, rooted, just like always.
i've even wiped in between.
after the FIRST clean boot, there is no rebooting. all it does is continue to hang after the samsung splash. no cyanogenmod, no stock rom, no nothing, nothing will boot the SECOND TIME.
i really don't understand this.
i'm using CWM recovery 5.5.0.4, cm-nightly 10-05, and it just don't think it's going to work properly again. it's a real shame, cause i really like the size, weight, and speed of this phone. but if it won't boot, i can't use it.
if anyone has any tips, i'll try them. at this point i really don't mind destroying it, and it might make me feel better to do so.
i meant to add, it doesn't matter if i use a backup, flash a fresh new rom, or use stock. the first boot works fine, but all boots after that wether from powering down or selecting 'reboot' fail.
maybe this part will help -
if i wipe the phone completely, it will boot. let's call this boot 1.
i can setup the phone, or change nothing in settings, doesn't appear to matter, and choose 'power down' or 'reboot'. let's call this reboot 1.
the next time i power on the phone, black screen. no CM splash, nothing. i guess we'll call this hang 1 ?
ideas ?
ohgood said:
i've wiped everything. flashed back to stock via odin, rooted, just like always.
i've even wiped in between.
after the FIRST clean boot, there is no rebooting. all it does is continue to hang after the samsung splash. no cyanogenmod, no stock rom, no nothing, nothing will boot the SECOND TIME.
i really don't understand this.
i'm using CWM recovery 5.5.0.4, cm-nightly 10-05, and it just don't think it's going to work properly again. it's a real shame, cause i really like the size, weight, and speed of this phone. but if it won't boot, i can't use it.
if anyone has any tips, i'll try them. at this point i really don't mind destroying it, and it might make me feel better to do so.
.
i meant to add, it doesn't matter if i use a backup, flash a fresh new rom, or use stock. the first boot works fine, but all boots after that wether from powering down or selecting 'reboot' fail.
Click to expand...
Click to collapse
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Romman0 said:
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Click to expand...
Click to collapse
yes, they're fairly recent nightlies. i skipped back to the 10-5 nightly as i thought that might ahve been part of the problem. since you're pointing to my recovery being an older version, i'll update it. thanks for the clue stick !
Romman0 said:
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Click to expand...
Click to collapse
hey thank you for that. i've removed the old cwm recovery, flashed new, lots of other flashes, and it finally works again. now to dig up a non-corrupted backup and hopefully be back to working.
thanks button was used
well, after all of that i'm going to roll with cm-10.0, cwm 6.xomething, so i can have a working compass on oruxmaps.
i won't be updating until 10.x begins to support compass functions again.
see yall then !
ohgood said:
well, after all of that i'm going to roll with cm-10.0, cwm 6.xomething, so i can have a working compass on oruxmaps.
i won't be updating until 10.x begins to support compass functions again.
see yall then !
Click to expand...
Click to collapse
Make sure you use the latest cm10 nightly, as the old stable one is a lot less "stable" than the name suggests, and is lacking features
Romman0 said:
Make sure you use the latest cm10 nightly, as the old stable one is a lot less "stable" than the name suggests, and is lacking features
Click to expand...
Click to collapse
thanks for the tip !
i finally got all the corrupted files (or whatever was causing problems) rm'd from both the phone and sdcard.
as of yesterday i had CM-10.o + CWM 6.0.3.8 and gapps 2012-8 (i think) working nicely on the phone. backed up a nandroid of all of it two times, and restored them to make sure restores were working. yes, everything fine.
as of today, i have CM-10.2 (latest nightly) + CMW 6.0.3.8 and gapps (current) working nicely on the phone. backed CURRENT up nandroid on sdcard, and restored a few times to make sure. yes, working fine.
seems it was
A) corrupted files/filessystems
and/or
B) too old a clockworkmod recovery
C) unstable CM version( s )
but now all is fine. thanks to all that helped !
I've been trying to upgrade to a LiquidSmooth KitKat (3.0 Nightly Beta) ROM but it's been failing. So I figured it's Sunday, it's early, let me try again. Let's get a baseline:
Last usable (as of earlier this morning) ROM: LS 2.7 (4.2.2)
TWRP 2.6.3.0
SuperSU installed
So I *WAS* unlocked and rooted.... now... I don't know what the heck is wrong.
Saturday I downloaded "EZ Unlock 1.2" and installed it; Unlock Status was "UNKNOWN" and even after clicking the UNLOCK button it still showed "UNKNOWN"
So, this morning, I made sure I had the new ROM (LS KitKat 3.0 Nightly Beta 2) on my external SD card, booted in to TWRP, and updated to the latest TWRP (2.6.3.1). I then cleaned out some old ROM backups and made a new one (using compression) which was successful. Rebooted to system, all looked & worked normally, so I rebooted to TWRP Recovery, did a Factory Reset + system (so cache, dalvik, data, & system) and that went fine. Tried to install the new ROM... FAILED. So I rebooted to Recovery and tried to restore the backup I had just made, and it seemed to succeed, but when the phone rebooted, it only got to where it reads "Samsung Galaxy S III" and got no further. I let it sit like that for 10 minutes, then pulled the battery. I booted back in to Recovery and tried restoring a backup made 2 days ago (that I have previously restored from successfully) and that gave a "successful" result, but same thing after rebooting: stuck at where it reads "Samsung Galaxy S III" and would go no further.
I am in DOWNLOAD mode currently and want to get back to the point of being able to restore my backup from 2 days ago. I'll lose text messages basically, and that's fine. I have downloaded ODIN 3.07 but it's been about a year since I last tinkered with it.
Can someone help please? I either get this phone working in the next few hours, or I have to go buy something else off craigslist... or full retail... and I'd really just prefer to get this phone working again.
If I need to "start from ground zero" and redo the boot unlock and root it, so be it. Basically, how do I unbrick my S3?
papadelogan said:
I've been trying to upgrade to a LiquidSmooth KitKat (3.0 Nightly Beta) ROM but it's been failing. So I figured it's Sunday, it's early, let me try again. Let's get a baseline:
Last usable (as of earlier this morning) ROM: LS 2.7 (4.2.2)
TWRP 2.6.3.0
SuperSU installed
So I *WAS* unlocked and rooted.... now... I don't know what the heck is wrong.
Saturday I downloaded "EZ Unlock 1.2" and installed it; Unlock Status was "UNKNOWN" and even after clicking the UNLOCK button it still showed "UNKNOWN"
So, this morning, I made sure I had the new ROM (LS KitKat 3.0 Nightly Beta 2) on my external SD card, booted in to TWRP, and updated to the latest TWRP (2.6.3.1). I then cleaned out some old ROM backups and made a new one (using compression) which was successful. Rebooted to system, all looked & worked normally, so I rebooted to TWRP Recovery, did a Factory Reset + system (so cache, dalvik, data, & system) and that went fine. Tried to install the new ROM... FAILED. So I rebooted to Recovery and tried to restore the backup I had just made, and it seemed to succeed, but when the phone rebooted, it only got to where it reads "Samsung Galaxy S III" and got no further. I let it sit like that for 10 minutes, then pulled the battery. I booted back in to Recovery and tried restoring a backup made 2 days ago (that I have previously restored from successfully) and that gave a "successful" result, but same thing after rebooting: stuck at where it reads "Samsung Galaxy S III" and would go no further.
I am in DOWNLOAD mode currently and want to get back to the point of being able to restore my backup from 2 days ago. I'll lose text messages basically, and that's fine. I have downloaded ODIN 3.07 but it's been about a year since I last tinkered with it.
Can someone help please? I either get this phone working in the next few hours, or I have to go buy something else off craigslist... or full retail... and I'd really just prefer to get this phone working again.
If I need to "start from ground zero" and redo the boot unlock and root it, so be it. Basically, how do I unbrick my S3?
Click to expand...
Click to collapse
Have you try to wipe cache/dalvik cache/system/ format sd, make sure everything is mounted the do the restore again?
buhohitr said:
Have you try to wipe cache/dalvik cache/system/ format sd, make sure everything is mounted the do the restore again?
Click to expand...
Click to collapse
I am currently backing up my external SD card (all pics & backups go to ExtSDCard) before doing any formatting. I was going to try that next, but am expecting it to fail. What I've found on XDA so far has mostly for those that took an OTA but that is not my case. I am severely pressed for time (use my phone for work as well as personal) and am planning for "worst case scenario" so, assuming your suggestion fails, do I get the original ROM, flash that back using ODIN, then re-do the boot unlock & root?
papadelogan said:
I am currently backing up my external SD card (all pics & backups go to ExtSDCard) before doing any formatting. I was going to try that next, but am expecting it to fail. What I've found on XDA so far has mostly for those that took an OTA but that is not my case. I am severely pressed for time (use my phone for work as well as personal) and am planning for "worst case scenario" so, assuming your suggestion fails, do I get the original ROM, flash that back using ODIN, then re-do the boot unlock & root?
Click to expand...
Click to collapse
That would be the right way..good luck!
buhohitr said:
That would be the right way..good luck!
Click to expand...
Click to collapse
I was hoping for a bit more than "good luck" actually since it's been a good year since my last trip with Odin... but thanks.
papadelogan said:
I was hoping for a bit more than "good luck" actually since it's been a good year since my last trip with Odin... but thanks.
Click to expand...
Click to collapse
I have high confidence that you will have this issue resolved shortly. It's not your fault, lately, some custom roms did not behave accordingly...