How to Restore from Latest S3 Nightly? - Verizon Samsung Galaxy S III

EDIT: 12/23/2012 3:19AM.. Doing a little research I figured out what the issue was. Used Brian Gove's Guide
[How To] Reset your phone in order to return to Verizon(Updated 12/11/2012)
From Step 5 Onwords and everything works great.
.. I am still stumped on exactly what happen. I am almost positive it was because of the new file structure..
Just Proves that with a little patience and smarts anyone can use the resourced and tools here to solve their own android problems without bothering anyone haha.
Thank you all for your articles and Merry Xmas / Happy Holidays to Everyone!!
now.. I gotta unlock my boot loader and start all over..
Soft Brick.....
I was looking around and I cant seem to find a post that really solves my problem.
I have a Verizon S3 that I rooted and flashed to CyanogenMod Nightly build and everything was working great.
I used Rom Manager Premium and it updated me to update to CMW 6023. I went ahead and updated.
I saw that there was an update for my Daily As well 12/22/12 so I went ahead and used Rom Manager to download it and install it for me like It did with my last 16 Roms. That Rom had some strange things going on so I flashed to an older rom 12/20/12 and that rom was buggy as well.
Finally I decided that I should just stop with the Daily's and use the stable. When I loaded the Stable things started to still act strange. Mostly the Keyboard would not work and keep crashing. I decided then to just reload my original backup from Verizon.
Before I went in to recovery i took a look at my files and backed everything up. However then I noticed something that was not there before, a folder /0 with most of my main files inside.
I went into CWM v6.0.2.3. and tried to do a restore to my original nandroid backup from verizon but it looks like it failed.
It Says "Error While Restoring System" and kicked me back to CWM
Now when I reboot all I see is the White "Samsung Galaxy s3"
Did I Screw the pooch on this? Kinda nervous haha.
I am Posiive its a Soft Brik and hoping there is a way to fix it.
I can however get to Download mode. If anyone knows a great guide to help me reflash with Odin that would be fantastic.
thanks guys, been a long time reader and this is the first problem I have really had.
I apologize if this has already been over in a post.
Just a quick step breakdown would be great. I am really hoping that I didnt brick my phone.
Thanks for the help and Merry Christmas / Happy Holidays to everyone.

Related

[Q] Clockwork Recovery problem

First.. I want to say hello and that i've been reading around these forums for quite a while since I got my Droid about a year ago. I haven't posted anything till now.. but that's only because everyone else usually get's the answers typed faster than me. lol
On to the problem... I think I screwed up. I JUST bought this thing today. I got a little too excited about getting this tablet rooted and might have jumped the gun a little. I used the apk that has been around to root. No problems there. I got ROM Manager loaded... and I ended up flashing the newest recovery from there before realizing that everyone else says to use something else.
So... at this point, i'm unable to reboot into recovery at all. It starts up, acts like it's about to, and then just reboots again into the OS instead. Is there a way to fix this and get it on the correct recovery image or have I totally screwed myself over? Maybe through ADB? I can only tolerate this horrid TnT OS for so long. Took me 20 minutes to get it to update without a FC... Browser, weather, calendar, and a bunch of other stuff FC on me when I tried starting.. Fortunately, those issues are less frequent with the update, but still not working keeping.
I need some "stock(CyanogenMod)" Froyo goodness.. lol I can't have my year and a half old phone outclass this tablet for too long. If anyone can offer any help on this, I would greatly appreciate it.
The good news is you are still booting into the OS, so I doubt you've screwed anything up too bad. Most likely Clockwork Mod just never flashed so you are still running with the gimpy stock recovery and it's puking on the update.zip file you have on your internal sd card for some reason.
First suggestion is get a copy of Clockwork Mod 0.8 and try installing it. The instructions here are geared toward installing from an external from an external MicroSD card: http://forum.xda-developers.com/showthread.php?t=865245 I am not certain why they say that's the only way to do it, since I never did it that way.
I just downloaded this: http://www.mediafire.com/?dvleg4oatkfxm7w and stuck the update.zip and recovery folder into my /sdcard directory, then turned my tablet off, then held down Vol+ and turned it back on. Clockwork Mod should install itself and boots into Clockwork Mod, and that was that.
I never used ROM Manager at all on my G Tablet, so I can't speak to doing anything that way, but I would stick with the tried and true methods at least until you have Clockwork Mod running.
If that fails and you really can't get any recovery working, maybe something did get botched and you might need to use nvflash to fix it, but I doubt it.
Once you get Clockwork Mod running properly, just copy over the update.zip for TNT Lite or Vegan ROM, flash, and wipe data, then you should be good to go.
Worked perfectly and entirely from the tablet! I installed CM6.1 and I'm a bit upset at the lack way it looks, but then, its packed for smaller screens, so I understand. Thank you for the quick reply. I'm off to try TnT Lite now.

[Q] Please help! Cyanogen didn't like my Ascend

I need some serious help ...
I rooted with Z4root, and it worked great, and EASY!!!!!
I downloaded and bought the RoM Manager from the Market because after weeks of reading, reading, and reading some more, I just couldn't bring myself to install a RoM myself. The only 2 RoM's that popped up for me was PlayfulGod & Cyanamogen 7.
I first chose Cyan... and it was great except the Market was gone, and a few other things didn't work all of a sudden. Then when I tried to change with RoM Manager it kept saying I needed to get the newer version. Long story short, I was finally able to switch over to PlayfulGod via RoM Manager. It's been a long few days, I don't remember what it was that made me want to go back to Cyan, but I figured I could just download a new Market and all would be fine. So, RoM Manager again ... download Cyan, install, backup. While it was backing up I went to sleep.
When I woke up this morning, my phone was in a looping bootmode! I get the movie thing that Cyan boots up with, then the android guy - then the movie again, android guy, movie android, over and over. I can't even get to the Volume Down, End, Power spot. When I try, I get the Huawei screen and that's all it'll do.
I was too scared to "flash" a RoM myself, and now I am completely lost. Please help me fix my phone ...
~Ky
txheart0711 said:
I need some serious help ...
I rooted with Z4root, and it worked great, and EASY!!!!!
I downloaded and bought the RoM Manager from the Market because after weeks of reading, reading, and reading some more, I just couldn't bring myself to install a RoM myself. The only 2 RoM's that popped up for me was PlayfulGod & Cyanamogen 7.
I first chose Cyan... and it was great except the Market was gone, and a few other things didn't work all of a sudden. Then when I tried to change with RoM Manager it kept saying I needed to get the newer version. Long story short, I was finally able to switch over to PlayfulGod via RoM Manager. It's been a long few days, I don't remember what it was that made me want to go back to Cyan, but I figured I could just download a new Market and all would be fine. So, RoM Manager again ... download Cyan, install, backup. While it was backing up I went to sleep.
When I woke up this morning, my phone was in a looping bootmode! I get the movie thing that Cyan boots up with, then the android guy - then the movie again, android guy, movie android, over and over. I can't even get to the Volume Down, End, Power spot. When I try, I get the Huawei screen and that's all it'll do.
I was too scared to "flash" a RoM myself, and now I am completely lost. Please help me fix my phone ...
~Ky
Click to expand...
Click to collapse
With any cyanogen mod you Have to flash google apps separate. That will solve for market problems. Since you have to flash GAPPS you might as well re download whichever cm7 check the md5 checksum and reflash that. You can find videos on youtube that give you a step by step of the flashing and backup process. Just search around the web.
Can somebody help me I love cyanogen mod and I'm trying to update my ascend to cm7.2 but it failed everytime I try any ideas please
Sent from my M860 using XDA App

[Q] HELP - Nexus 7 & Beats

okay, where to start.
I've a Nexus 7, and im running P.A 2.54, with twrp.
i got an article from one of my news apps about getting better volume for my nex 7 BeatsLouder, followed the link and downloaded, didn't do any information gathering and consequently i believe i've flashed the beatslouder for android 4.2 it was BeatsLouder v3b8 i believe.
Either way now, my tablet just hangs at the P.A splash screen/boot logo.
needless to say, with my lack of forward planning into researching what i was flashing i didnt make a back up either..
Are there any solutions that don't even a fresh wipe?
edit: so i had a back up in twrp, when i had the forethought to do a backup prior to installing something unknown, however i'm not certain if the back up is of data or system files or both, anyway to find out? the restoring of the back up seemed to happen almost instantaneously, making me think it didnt work?
oh, also i made a backup of everything (in its current broken state) in the hopes i might be able to recover my data?
would love some responses, anything to get the ball rolling
Try dirty flash your ROM then gapps in recovery again. No wipe needed.

Is this normal?

Hello XDA!
I have some questions about my n8010. It is a tablet that I bought in Greece, in case that is necessary to know, and has an interesting background. It started late May. The tablet was unrooted and without any mods whatsoever. I was running the latest Jelly Bean update and had A TON of lag. I had replaced TouchWiz Launcher with Nova and a different gallery and music app with still a lot of lag. So I decided to flash CM11 since it would be lighter for the tablet. After some research I followed the root guide from Zedomax and everything was fine. I had root and so I proceeded doing a backup. This where everything got weird. The backup started but was stuck for long periods of time. After some time being stuck in a screen I decided I should force restart. After the Galaxy Note 10.1 logo appeared it just hanged there without booting into Jelly Bean. I checked recovery and download mode and they where all working fine so I flashed TWRP. It worked and so I took a backup and proceeded installing CM11. I had it already in my SD. I had followed the instructions in the XDA thread that said about removing a line to make it work on the n8010. The flash went great and after factory resetting I rebooted the tablet and everything was OK. At the first boot WiFi wouldn't work but after a reboot it was. The only thing that wasn't working was the video recording. It is a deal-breaker as I use it a lot. I had to switch ROMs. I tried CM10.2 and it still wouldn't. Same goes for Revolt. At lat I switched to a TouchWiz based ROM. Specifically Hyperdrive RLS8. Video was working so I stayed there. I was noticing that since I flashed CM11 my tablet showed up as an n8013 which was very weird but since these ROMs where designed for the n8013 I thought it was normal.
One ROM also had the front facing camera able to record. Upon further inspection I found that Download Mode had my tablet as an n8010 but with the flash count 0 and the status official! Now, I'm either super lucky or the completely opposite! It also says official under About Device! Fast forward a few months and I am now in a situation where the tablet lags once again like crazy. I uninstalled a couple of apps and also installed lighter alternatives and it's somewhat bearable. I was reading the Official OmniROM thread and saw that others also had issues, most of which had the new KitKat bootloader that I don't have, with YouTube and the Video Recording. The latest nightlies are said to have a fix. So I am thinking of installing OmniROM since I am lagging a lot and I would like Screen Mirroring to the Chromecast. My only concern is that I will either brick the tablet or the camcorder won't work. Many people have bricked their Notes and can't go back without the Samsung Service. Most have the new KitKat bootloader which I don't and I'm happy about. My tablet is in a weird situation, what should I do? Anybody else experiencing these issues? Any advice is appreciated!
Thanks in advance,
Chris
Edit: Forgot to say that I flashed Carbon ROM in September and I got a status 7 while flashing with PhilzCWM that I had installed in order to flash Hyperdrive. I had to flash back to Hyperdrive as it wouldn't boot after the status 7. It probably happened because it didn't have SE Linux support. If I do anything I'll flash the latest TWRP.
chrismin13 said:
Hello XDA!
I have some questions about my n8010. It is a tablet that I bought in Greece, in case that is necessary to know, and has an interesting background. It started late May. The tablet was unrooted and without any mods whatsoever. I was running the latest Jelly Bean update and had A TON of lag. I had replaced TouchWiz Launcher with Nova and a different gallery and music app with still a lot of lag. So I decided to flash CM11 since it would be lighter for the tablet. After some research I followed the root guide from Zedomax and everything was fine. I had root and so I proceeded doing a backup. This where everything got weird. The backup started but was stuck for long periods of time. After some time being stuck in a screen I decided I should force restart. After the Galaxy Note 10.1 logo appeared it just hanged there without booting into Jelly Bean. I checked recovery and download mode and they where all working fine so I flashed TWRP. It worked and so I took a backup and proceeded installing CM11. I had it already in my SD. I had followed the instructions in the XDA thread that said about removing a line to make it work on the n8010. The flash went great and after factory resetting I rebooted the tablet and everything was OK. At the first boot WiFi wouldn't work but after a reboot it was. The only thing that wasn't working was the video recording. It is a deal-breaker as I use it a lot. I had to switch ROMs. I tried CM10.2 and it still wouldn't. Same goes for Revolt. At lat I switched to a TouchWiz based ROM. Specifically Hyperdrive RLS8. Video was working so I stayed there. I was noticing that since I flashed CM11 my tablet showed up as an n8013 which was very weird but since these ROMs where designed for the n8013 I thought it was normal.
One ROM also had the front facing camera able to record. Upon further inspection I found that Download Mode had my tablet as an n8010 but with the flash count 0 and the status official! Now, I'm either super lucky or the completely opposite! It also says official under About Device! Fast forward a few months and I am now in a situation where the tablet lags once again like crazy. I uninstalled a couple of apps and also installed lighter alternatives and it's somewhat bearable. I was reading the Official OmniROM thread and saw that others also had issues, most of which had the new KitKat bootloader that I don't have, with YouTube and the Video Recording. The latest nightlies are said to have a fix. So I am thinking of installing OmniROM since I am lagging a lot and I would like Screen Mirroring to the Chromecast. My only concern is that I will either brick the tablet or the camcorder won't work. Many people have bricked their Notes and can't go back without the Samsung Service. Most have the new KitKat bootloader which I don't and I'm happy about. My tablet is in a weird situation, what should I do? Anybody else experiencing these issues? Any advice is appreciated!
Thanks in advance,
Chris
Edit: Forgot to say that I flashed Carbon ROM in September and I got a status 7 while flashing with PhilzCWM that I had installed in order to flash Hyperdrive. I had to flash back to Hyperdrive as it wouldn't boot after the status 7. It probably happened because it didn't have SE Linux support. If I do anything I'll flash the latest TWRP.
Click to expand...
Click to collapse
I would have fixed the original lag issues first. I would get it back to factory stock 100 percent, once back to factory I would do A factory reset and start all over. Get the system running stock as it should then reinstall apps one at a time. if it can't run stock for whatever reason other roms not going to fix the problem.
at least with factory stock you know what should be working. Instead of guessing if the problem is part of the new ROM
shaun298 said:
I would have fixed the original lag issues first. I would get it back to factory stock 100 percent, once back to factory I would do A factory reset and start all over. Get the system running stock as it should then reinstall apps one at a time. if it can't run stock for whatever reason other roms not going to fix the problem.
at least with factory stock you know what should be working. Instead of guessing if the problem is part of the new ROM
Click to expand...
Click to collapse
Thanks for the response!
Good idea! I was thinking of going back to stock and repeating everything. It should fix all my issues. It's too bad that I don't have a working stock backup and I will have to flash through Odin. The reason that I am not doing this is because I am afraid of making it even worse from the official status state that I have in Download Mode and my device is an n8013 under About Device. A flash back to stock through Odin would probably flash most of the system parts which would be kinda dangerous. But on the other hand that would mean that I could give it a brand new try with better luck possibly! It's not that TouchWiz ROMs don't work, it's AOSP that doesn't. I played a lot with Hyperdrive and seems like it's doing better from the lag prospective. But that's only gonna last 15 days. I am sure! So, I'll have your response in mind! Might try it out when I have some free time. Unfortunately, that will probably be Christmas.
Thanks,
Chris
Going back to stock is good advice.Should certainly fix the video problem which you said was important.
Phil789 said:
Going back to stock is good advice.Should certainly fix the video problem which you said was important.
Click to expand...
Click to collapse
I don't have any video playback issues. It's just the camcorder that doesn't work in AOSP ROMs.
Yes.My use of the word "video" should have been "video recording".
The time has come!
Hello everyone, happy holidays!
The time has come that I follow your instructions. I've done my research and here's how I'll do it. Do you agree? Do you have any other suggestions?
Take full backups with my current configuration (Hyperdrive RLS8, PhilzCWM)
Factory reset the device and clean it up so that there is a lot of space
Install Samsung Drivers
Flash Stock Greek 4.1.2 Frimware (N8010XXUCMK2_N8010OXXCMK2_HOME.tar.md5) through ODIN v3 1.85
Let it boot up and do a factory reset from stock recovery
Flash TWRP 2.8.1.0 for the GT-N8010 (openrecovery-twrp-2.8.1.0-gt-n8010) (I chose this version since it has the most downloads)
Make a full backup once again
Flash Omni ROM 4.4.4 (omni-4.4.4-20141222-n801x-NIGHTLY)
Flash SuperSU (UPDATE-SuperSU-v2.40)
Flash PA GApps (pa_gapps-modular-mini-4.4.4-20141214-signed.zip)
Factory reset
REBOOT!
Check everything (Video, model, download mode, bugs, etc.)
REPORT!
If everything goes correctly I believe I should be OK! Hope my issues will be over since the tablet is slow once again. Kinda scared, so that's why I'm asking you. Will I be (mostly) brick safe? Hope so!
Thank you very much for your support,
Chris
P.S.: Should I root before leaving stock? I mean through TWRP.
chrismin13 said:
Hello everyone, happy holidays!
The time has come that I follow your instructions. I've done my research and here's how I'll do it. Do you agree? Do you have any other suggestions?
Take full backups with my current configuration (Hyperdrive RLS8, PhilzCWM)
Factory reset the device and clean it up so that there is a lot of space
Install Samsung Drivers
Flash Stock Greek 4.1.2 Frimware (N8010XXUCMK2_N8010OXXCMK2_HOME.tar.md5) through ODIN v3 1.85
Let it boot up and do a factory reset from stock recovery
Flash TWRP 2.8.1.0 for the GT-N8010 (openrecovery-twrp-2.8.1.0-gt-n8010) (I chose this version since it has the most downloads)
Make a full backup once again
Flash Omni ROM 4.4.4 (omni-4.4.4-20141222-n801x-NIGHTLY)
Flash SuperSU (UPDATE-SuperSU-v2.40)
Flash PA GApps (pa_gapps-modular-mini-4.4.4-20141214-signed.zip)
Factory reset
REBOOT!
Check everything (Video, model, download mode, bugs, etc.)
REPORT!
If everything goes correctly I believe I should be OK! Hope my issues will be over since the tablet is slow once again. Kinda scared, so that's why I'm asking you. Will I be (mostly) brick safe? Hope so!
Thank you very much for your support,
Chris
P.S.: Should I root before leaving stock? I mean through TWRP.
Click to expand...
Click to collapse
I did it! It worked. Everything went OK but:
- Flash count is 0 and status official
- Back camera records in slow-mo
- Chromecast mirroring does not work
However:
-My device is an N8010
-I use the front camera instead
-Mirroring was not really needed
-LAG IS HISTORY!!! [emoji50] [emoji2] [emoji2] [emoji2]
I am so impressed by the performance, still doesn't best my nexus 4 with KK 4.4.4 but it's a GIGANTIC IMPROVEMENT! Veeery happy! Thank you for your support, I wouldn't be here without you!
Merry Christmas and happy holidays!
Chris.[emoji2]

Help with B148

Hey guys,
So I went from B145>B148 and now I'm stuck. Can't root or go >B304>B312>B327...what I'm saying is, I'd rather go back to B145. I was very much fine with that version (rooted w/ KingUser then removed and installed w/ SuperSu). Everything else fine. Just wanted to see if there was any difference on B148, not too excited to go LP.
Any ideas how to go back down B145??
thanks!! :good::good:
Anything, anyone?
Downgrade firmware? Something?
Solved!
Alright, so with only a bunch of page views and no real help from anyone here on the forum...I was able to finally figure everything out on my own.
I was originally at C00B145 (and rooted, loved it), got curious with everyone talking bout the many other upgrades so >C00B148 (lost root, hated it. Stuck on firmware, couldn't root and for some reason could't go further), probably just me. Decided and risked on V100R001C900B308 rollback (success) but stuck again on temp transition, couldn't go anywhere. Failed on B137, B137SP03, B141, B145, and B148.
Solved: Re-flashed V100R001C900B308>C900B300 (rollback)>MT7-L09C900B324, backup recovery, system restore>kingroot, then installed SuperSU (deleting kingroot).
Rooted MT7-L09C900B324 5.1. Now, the only thing I'm missing so far is the Motion Control, which I only deal with the slider (not a big deal to me). I really like the double-window, knuckle/screenshot, and the few other interesting new features. Lots of ppl saying they don't have 4g available, but mine's fine...can switch between 3G/4G.
I did use two different region's firmware for the solve. No lags, and actually has good fluid response. Gonna keep on 5.1 for at least a week and see what's good on battery life, response and features...if I like it'll stay, otherwise I had no problem on B145 and might just go back down to KK.
Cheers!
jfer671

Categories

Resources