I've been reading a lot about the Supercharged ROM that we have available...I'm just wondering if it's a good idea. I don't like BLUR, and I know how to flash the stock rom to my phone...that's about my skill level. But I guess I'm just wondering if it's worth it? and is there much risk?
Just boot in bootstrap recovery and choose the restore option. Ive "restored" it 5 times, never a problem.
Sent from my MB865 using XDA
If you're comfortable with using RSD Lite to flash your phone back to stock, then go ahead and try the ROM. It's, well, supercharged . You may also want to try a recently released ROM, RebelROM. Both ROMs are still in beta so there are some minor issues with each, however they speed increase is enormous.
If you make a backup (using CWM) before you flash then you can also restore the backup to get back your old settings, apps, and stock ROM.
Thanks guys, I went ahead and did it. But...I like the UI changes...however I want the ICS theme that we have available, but I'm having trouble using ADB to push it to my phone...i've seen directions on how to do it but everytime I try it, something seems to go wrong!
Related
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.
I have TWRP installed on my One X and fully backed up my current settings through the Backup function in TWRP as well as Titanium backup, just to be safe.
I want to install MIUI so I've downloaded the zip. Is the best method to wipe the phone and then install the zip, or is it to restore to factory settings and then install the zip?
Also, if I want to go back to my current rom (HTC Sense - that came with the phone) how would I restore the TWRP backup that was created? Also how solid is the TWRP backup? Will I have problems restoring from that with random things like market associations or settings?
Thanks for all the help everyone.
TWRP backups back up EVERYTING (I mean kernel, system, app apks) except for sdcard data. Restoring a backup will look exactly like the moment you backed up the ROM.
In order to flash a new ROM, do this:
1. Back up your apps using some application (Titanium Backup, Ultimate Backup, etc)
2. Create a new TWRP backup
3. Factory Reset
4. Install the ZIP
5. Boot into your ROM and download whatever app you downloaded in step 1
6. Restore your apps from step 1
Enjoy
im looking for a good rom as well but im new.
my att one x was on 1.85 before i rooted it and unlocked the bootloader.
now im just looking for a senseless rom like Jdroids or CM9 that will work with my situation.
id love to get jdroids exodized revoultion, does that work with att? or do i have to wait for an att version to come out?
any suggestions. thnx
veyg said:
im looking for a good rom as well but im new.
my att one x was on 1.85 before i rooted it and unlocked the bootloader.
now im just looking for a senseless rom like Jdroids or CM9 that will work with my situation.
id love to get jdroids exodized revoultion, does that work with att? or do i have to wait for an att version to come out?
any suggestions. thnx
Click to expand...
Click to collapse
Don't flash anything that isn't actually in our dev forum unless you want a buggy POS (best case), a massive bootloop (slightly worse case), a beautiful paperweight (pretty bad), or your phone exploding (yeah that's probably the worst).
I made that last one up, but who knows.
As for Sense-less roms, look for AOKP or CM9. CleamROM DE/Dev Edition is pretty much Sense-less, but it retains some backend Sense things to ensure everything still works properly. It's as close to AOSP as you're gonna get without actually being AOSP.
stnguyen09 said:
Don't flash anything that isn't actually in our dev forum unless you want a buggy POS (best case), a massive bootloop (slightly worse case), a beautiful paperweight (pretty bad), or your phone exploding (yeah that's probably the worst).
I made that last one up, but who knows.
As for Sense-less roms, look for AOKP or CM9. CleamROM DE/Dev Edition is pretty much Sense-less, but it retains some backend Sense things to ensure everything still works properly. It's as close to AOSP as you're gonna get without actually being AOSP.
Click to expand...
Click to collapse
Hello can you help me? i have a paper weight because i installed the wrong rom and i flashed it when i had 20% battery now y one x wont turn on or charge please help
mr.5106411 said:
Hello can you help me? i have a paper weight because i installed the wrong rom and i flashed it when i had 20% battery now y one x wont turn on or charge please help
Click to expand...
Click to collapse
Well there's another lesson in there. Don't flash unless you have sufficient battery (I never do it under 50%....best to do it when fully charged though)
So you're not getting the led indicator to light up when you plug it in? What rom did you flash?
Hello everyone. I received my Verizon SG3 shortly after it came out. I have been doing reading as I am very new to android. This is my first android phone. Previously I had an EnV Touch. Hated that thing, but it did the job. So any who I now have this awesome kick butt phone and it has all the Verizon crap on it I cannot get rid of. I have rooted and the bootloader is unlocked. I used a windows program to gain root and then used EZ unlocker to unlock the bootloader. I have been looking and looking to figure out what rom I want to start with, I want JB, but don't want a lot of bugs ATM as i don't have all that much time to play with flashing and being still so new I don't want to end up with a brick. I tried my harderst to figure this out by reading, but the info seams so spread out, I kinda want to try the CM10 9-6 as I have read it is stable and not many bugs. My main question is about kernels. Am I correct in thinking they will get flashed just like my rom will in ROM manager? Or do I need to flash through CWMR? How do I know what Kernel to use? I have been reading the CM10 takes a different kernel than say synergy or stock. Or will the stock kernel work till I load the proper kernel. If I knew about the kernel and how vital it was to go with the ROM maybe I wouldn't be so paranoid. I have a friend with a GS2 and he told me the kernel has to go with the ROM and if the two don't mach then you could brick. I can't afford a brick my first time around.
If you could give me some advice or point me in the direction of some more reading that would be great.
Thanks
JB
All ROMs come with a kernel in them. Typically you just stay with it unless you want some extra features or what not. There are aosp kernels and kernels based on the stock firmware. If you use a touchwiz based rom you need to use a touchwiz kernel.
I don't think it will brick it if you interchange them. It will just boot loop
Edit: you flash kernels in recovery just like a rom. if you change kernels without changing roms you need to wipe cache and dalvik cache through recovery also.
Sent from my Nexus S 4G using xda premium
Back up your IMEI before flashing anything, alot of horror stories floating around. Development has some fantastic guides. After that, most of the "big gun" rom's here have kernels, and are for the most part consistently the same flash method through recovery. Cwm recovery is solid and reliable, start with that until you feel comfortable enough to venture off. Make sure it's version 6.0.1.2 (regular or touch) for any jelly bean based rom.
Sent from my SCH-I535 using xda premium
I backed up the IMEI with the terminal emulator. So if the error occurred it would restore with the proper IMEI. Should I back it up any other way too?
Also I'm planning on using the Rom manager to flash the Rom. Do you not recommend that or should I do it manually with CWRM?
Thanks for the replies. I'm still getting my feet wet and know all about searching before asking. Used to program dish.
Sent from my Galaxy S3 using Tapatalk.
Your call, depends how paranoid you are! I would flash manually, it's a control thing for me, I know what/how/when all was done. Using 6.0.1.2 touch is awesome, speeds flashing up considerably.
Sent from my SCH-I535 using xda premium
I might have to try the touch. I have standard 6 on there. The one you listed. Rom manager gives me the option to load touch too. Friend uses Rom manager on his s2. Looks to just automate things a little.
What I don't know is if it wipes the appropriate areas first for a clean install or if it's doing it dirty.
Sent from my Galaxy S3 using Tapatalk.
Use the Synergy backup. If you lose your IMEI you just flash it again and it's back. Just make Nandroid backups and flash away. This is my first Android phone too and now I get why people become flash addicts, it's amazing what you can do. It's easy to relock and unroot if need be. Everything is easy if you take it smart and slow.
Sent from my SCH-I535 using Tapatalk 2
Here here!
Sent from my SCH-I535 using xda premium
Just stick to a couple rules and you will be fine. First is backup, backup and backup before flashing. Always stay within the Verizon SGS3 section, Sounds simple but others have made the grave mistake. When flashing kernels, stick to the software, ie flash a JB kernel to a JB rom, flash a ICS kernel to an ICS rom. You should not have any problems but if you do you always have a backup. There are many roms, just flash an try them, make sure to read through the threads to identify any issues that have been discussed. JB roms there are a couple, a TW based JB rom from a T-mobile leak that was ported to VZW SGS3 that works well, there are official and unofficial JB vanilla roms, ie CynogenMod. Stick to those rules, keep a back up, i usually will transfer a copy of my original backup to my pc just in case, and always backup to external sd card. Good luck and have fun.
You can also flash kernels via Odin I believe.
I'm a little lost, I've been reading for days and can't seem to find my answer..here goes
Coming from droid1 were I could flash new to old and vice versa..had the s3 for a couple of weeks, I'm on beans 13 kernel lean1.0 and hd radio..the other day I was on clean 2.5, and before that on synergy..can I keep bouncing around like that, our do I need to do Odin thingie? I see were root'ers are Odin then taking this new update and looks like killer battery life..I don't really have a preference on roms , just nead a little help on doing it proper..txs
You can just keep flashing until you find a ROM you like. Odin is just basically when things are messed up and you need to go back to stock. I think it was RSD on the Droid 1.
Sent from my Galaxy S3 running Eclipse ROM V2.1
kintwofan said:
You can just keep flashing until you find a ROM you like. Odin is just basically when things are messed up and you need to go back to stock. I think it was RSD on the Droid 1.
Sent from my Galaxy S3 running Eclipse ROM V2.1
Click to expand...
Click to collapse
You can flash it just to go back to stock. Doesn't have to be cause you messed the phone up. I think it's also good to do it occasionally with a pit file to wipe/fix all partitions (not just /system and /data, but ones like the hidden radio/GPS partition etc.)
Sent from my SCH-I535 using xda premium
xsteven77x said:
You can flash it just to go back to stock. Doesn't have to be cause you messed the phone up. I think it's also good to do it occasionally with a pit file to wipe/fix all partitions (not just /system and /data, but ones like the hidden radio/GPS partition etc.)
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Well of course you can use it to just go back to stock, but the average user only does it when they mess up. I do agree though I personally even I find my daily driver like to start fresh then flash the keeper ROM.
Sent from my Galaxy S3 running Eclipse ROM V2.1
Have been rooted since day of pre-order delivery. Have flashed multiple ICS/JB TW roms. I stay away from AOKP/CM roms just because of loss of features so can't report on those. I have never lost wifi or GPS. Never had sim card error. Had no problems with TWRP and haven't used CWM since worked with Koush on Tbolt problems. We worked those out and I still run CWM touch on Tbolt. Used Amon on Rezound. Recoveries are what you feel comfortable with. I use whatever works best for the device although that is irrelevant to this subject. I still use the old school clean wipe of data/cache/dalvic cache/system for all flashes on all devices and all recoveries. Ultimately have never had a reason to use Odin or go back to stock since initial root. Only bugs I have seen are rom related and nandroid back to working rom fixed it. There are differing opinions on what I have just posted but I have had no problems with flashing anything on my last 3 devices and have never bricked a phone even though I may flash 10 times a day for multiple devs on multiple devices. Maybe the old school recovery devs were on to something. Beats me.
Kool..I'm catching on., slowly..
Now If I do an Odin with pda can I use a rooted oem Rom to accomplish this newest leak that is said to have killer batt life?
takota6 said:
Kool..I'm catching on., slowly..
Now If I do an Odin with pda can I use a rooted oem Rom to accomplish this newest leak that is said to have killer batt life?
Click to expand...
Click to collapse
Yes you can but they all have killer batter life. No need to Odin you can flash it in recovery. Only have to Odin stock RUU to get firmware update. If you do it could loose root and ability to unlock boot loader. You will have it as long as you keep it. As soon as you flash another rom it will wipe that one and you will be on the base that the rom is based on. This is why the devs update to latest bases whether they be leaks or official. Best you can do is flash newer radios and kernels unless the ROM Gods tell us to update firmware and then it will be checked and deemed safe. Never Odin/flash an OTA/leak unless it has been cleared by the Android Gods. I have only used Odin once and that was because that was only way to root on original pre-order. :laugh:
be sure to back up internal sd card
takota6 said:
I'm a little lost, I've been reading for days and can't seem to find my answer..here goes
Coming from droid1 were I could flash new to old and vice versa..had the s3 for a couple of weeks, I'm on beans 13 kernel lean1.0 and hd radio..the other day I was on clean 2.5, and before that on synergy..can I keep bouncing around like that, our do I need to do Odin thingie? I see were root'ers are Odin then taking this new update and looks like killer battery life..I don't really have a preference on roms , just nead a little help on doing it proper..txs
Click to expand...
Click to collapse
Don't forget to back up internal sd card. Odin will wipe it when you flash.
This is my first time installing a custom ROM, but I keep following all of the right steps but get the same result.
I have a North American Atrix 2 and it was running 4.0.4.
I have succesfully roooted it and this is what I have been doing:
1) Backup with Titanium
2) Installing Atrix2Bootstrap.apk which is saved from my flash drive
3) Once in recovery mode I will wipe all data, cache, and dalvik cache.
4) I then select unzip from SD card and choose the victory .zip ROM I downloaded
Everytime I do this it says it was successful, then just goes to a black screen after the Motorola screen and keeps restarting.
I've downloaded a the .zip of my stock ROM and use RSD Lite to bring it back to factory default, but I have tried this multiple times and get the same result and cannot figure out what I am doing wrong.
Any input would be great, or if maybe Victory is just a bad ROM. I am really looking for a simple, light ROM that will not slow down the phone or drain the battery.
VictoryROM is for Gingerbread (2.3.6) only. You can not install it on 4.0.4
Sent from my MB865 using xda app-developers app
Thank you very much for the clarification! That explains the issues I've been having.
Is there a comparable ROM for 4.0.4? I know there are other ROMs but I am more interested in a clean and simple ROM that will give me the best battery and just be simple and I'm afraid the newer ROMs will push the RAM on my phone and hurt the battery life like ICS did when I switched from GB
cmartin5970 said:
Thank you very much for the clarification! That explains the issues I've been having.
Is there a comparable ROM for 4.0.4? I know there are other ROMs but I am more interested in a clean and simple ROM that will give me the best battery and just be simple and I'm afraid the newer ROMs will push the RAM on my phone and hurt the battery life like ICS did when I switched from GB
Click to expand...
Click to collapse
Numa is your only option. aside from stock or a leak. Dev's are focusing on Kexec. and AOSP JB builds.
Sad, as they suck for stability.
http://forum.xda-developers.com/showthread.php?p=31369428
Here is an excellent ics ROM . Stock ICS with performance and battery improvements.
Sent from my MB865 using xda app-developers app