Welcome existing xda members, and new comers.
To clear things up before you read any information is that if you preform any tasks mention from within this thread me, and other members of the XDA community are not responsible for lost data,bricked devices or anything of that nature. If anything like this happens you are on your own, we can try to help you out of the problem if you post in this thread, however, we are not liable for any damages as said before.
Code:
#include
*
* Your warranty is now void.
*By you using my Mods, Roms etc...
* I am not responsible for bricked devices, or dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Before we start there are some words of which some member may not know the meaning of, so to clear things up here we go:
"Dirty flash" This is a word used by people refering to not clering any data or cache before the flash, this can lead to issues depending on the type of rom your flashing
"Clean Flash" This is another word used by member here on XDA, it is where they wipe both the data and cache before a flash to minimise any bugs in the rom what may occour.
The main purpose of this thread is to resolve potential issues such as cache errors, dalvik issues, force closes, sluggishness etc... There will be a FAQ at the end of the main posts, to resolve some of the most common issues reported by other members to me, via another thread or PM.
Currently there are three main roms of which most people are using, these include:
Nameless Rom, all editions mainly build 7.2 and up
Explosion Rom, others may move from this rom to the nameless, due to it being unsupported
Stock Rom, many people will choose custom roms over this, because they are faster.
ReVoluTioN RoM, all editions from v1.0 this includes both the sense and de-sense editions.
Whichever Rom you decide to flash weather it's stock, custom or whatever some of the most common problems are mostly the easiest to fix, for example; Let's say if a member at XDA has Nameless Rom 7.1 and they "dirty" flash 7.2 they may have problems such as force closes and market apps not installing, this is caused by cache errors, so clearing the cache is a simple fix to resolve the issue.
Below there will be a series of posts, which will range from rules of flashing and rom specific bugs and fixes etc... these sections are:
A guide to flashing, make sure your doing it right
Common rom bugs, and recommendations I have found a lot of bugs due to my dirty flashing as a noob lol
Thread rules no spam!
FAQ
Guide to flashing
Have you been hearing about all this custom ROM business on our Desire C and wondering what in the world all those are, and what they are for?
Your maybe you already know what those are but are still afraid of trying custom ROMs on your phone because you don't know how to install them or don't want to lose your data and wreak your phone?
Well today I'm going to show you the most safe way to flash Roms to our phone, there are four main steps involved in this:
First you will want to root your phone, there are guides on the Desire C forums on this, such as the very in detail guide written by air.combat the link to this thread is:
http://forum.xda-developers.com/showthread.php?p=33066306
Download your Rom from XDA, this could be the Nameless Rom
Reboot your phone into the recovery (to do this turn off the phone, hold down VOL- and hold the power button the HBOT menu will show up, press the top button once agin and then select recovery from the list)
Backup your current Rom, this is incase anything goes wrong during flashing, it rare but can happen. (It can be found in the backup and restore section of the recovery)
flash your Rom. (using the flash ZIP section on the recovery, and select the file of your rom.)
For whatever reason, you may want to go back and thats what the backup is for, you can use the backup section in recovery to restore your image before of your system)
Above is a overview of some of the most important steps required to flash a Rom onto your Desire C, however for some new members I will explain in more detail on how to preform these steps listed above, providing you follow these steps you will be fine.
Rooting
Firstly, rooting is usually a 5 minute process, and many guides around the web that explain about rooting our Desire C, but for some users there are issues they can face, such as ADB not working and other things. I think to best way for new members to root would be to use the All-In-One-Toolkit for the HTC Desire C, by hansoon2000 so all credits of this tool go to him. Instructions on how to use this program are easy, and any noobie can do it, if you have any issues with this feel free to post here, or send me a PM.
Downloading your Rom
Second, you will need to download your Rom, now as of now youu have two main choices (This will be updated with time to a list) these are:
Nameless Rom
Explosion Rom (may not be a good choice becasue it is discontinued)
ReVoluTioN RoM
Location of Rom on SD CARD
Once you have downloaded it if you downloaded it on your phone you will find it in the following folders; /sdcard/download/namelessxxx.ZIP (namelessxxx.ZIP being the Rom file you downloaded for your phone)
However if you have downloaded it on your phone I recommend making a folder called ROMS or NAMELESS or something to do with Roms, in the root of your SD CARD, for example; /Sdcard/Roms/namelessxxx.ZIP (it is much easier to keep your Rom folder organised if you have many versions saved)
Once that is done, we will move to the next step, which is wiping your data and why;
Wiping data, cache
Wiping your data and cache when flashing a new Rom, or base is a good option as it can prevent errors, and force closes when the new Rom is installed. If the data and cache is wiped your phone will feel faster a smoother on the new Rom as there are not useless files bloating the system, which is also slowing it down. I STRONGLY recommend wiping the cache because it holds information relating the version of android base etc... and if that data from the old Rom conflicts with the new one which may have a newer base, this will mean trouble!
To wipe the data and cache is easy, hen inside recovery simply select restore to factory defaults, this will prepare your phone for the new Rom flash, without useless files, the next section will explain the flashing part;
Flashing the Rom
Before flashing any Roms flash the required boot.img, this is the kernel without it the Rom will not work properly! remember to flash a boot.img its; [fastboot flash boot boot.img] and then [fastboot erase cache] then finally [fastboot reboot] If you do not flash it things such as WIFI will not work!
When you flash a Rom you will want to make sure you backup your current Rom first, just incase anything goes wrong. To do this inside recovery go to the backup and restores section, and select backup this will make sure you current Rom is safe. (however after backing up your Rom, copy the ClockWorkMod folder in the Root of your SdCard to a safe folder on your computer incase your SD card dies for whatever reason the folder will be laid out like so; /Sdcard/Clockworkmod/backups)
After you have backed up your system, you can safely go to the flash ZIP section in recovery and find your Rom ZIP file on your Sdcard. When you select it it will ask you are you sure select "yes" and proceed, one that is done you can reboot you phone into the new Rom!.
If you have any questions regarding flashing Roms, please read the FAQ before you post on this thread or send me a PM.
Why should I wipe and Not Dirty flash?
When people refer to the term wipe, it is my understanding that it means to delete the old ROM from various locations. This ensures a more clean installation, almost like its better to install Windows afresh instead of an upgrade. However, this is not Windows, its Linux, I am sure the logic behind this is because the way Linux works, it has certain files in certain directories, that if the file is there, the service is loaded automatically. Now if you had to replace a stock rom with something completely different, some of those auto loaded files will be left behind and you will be stuck with loaded services that should not be there, this can cause issues inside the new rom such as force closes.
This is where things might start becoming slightly confusing. Many people seem to argue that when upgrading from a stock version to another stock version that you don't need to wipe, I completely agree with this, as this will almost be the same upgrade process the default upgrade will follow, just with different files. However, if you upgrade to a very different ROM, start paying attention, as things might just get slightly more complicated, for these reasons:
The Rom base is different, this means you could be upgrading android to a newer version, which uses different files, or even the same one but slightly different.
The current Rom could be sense based, where as the new rom may be CM based for example
As a reminder of how to Wipe your data and cache follow these steps:
Boot into Recovery Mode, this can be via the Rom inbuilt "reboot to recovery option, only for custom roms" or turn the phone off, and hold down the VOL- button to boot into HBOOT and then Select recovery from the list with the sleep button
Once the Phone is in recovery mode...
Go to Wipe Data/Factory Reset and select YES
Go to Wipe Cache Partition and select YES
Go to Advanced, Wipe Dalvik Cache and select YES
Now that all to it after these steps your phone will have no useless files, or ny user files on it, once booted it will behave like a new system with it's set up etc...
Potential Bugs in custom Roms
reserved 2
Recommended roms and things to do with it
When it comes to flashing Roms as explained on some of the posts above, there are some guidelines or recommendations of which I think I should mention.
When using roms for a long period of time on this phone it may become slower, mainly due to sense bogging down this lovely phone. So as a NOTE before you post your phone is slow etc, try a reboot sometimes it can make all the difference.
Thread Rules
This thread is about sharing experiences from both me and other members in this forum. I do not want this thread to end up like many others do on xda, this meaning things such as spam, and off topic posts.
The following information which this thread is intended to include is:
Fixes to existing bugs in roms
Questions about flashing, backing up roms etc...
Answers to problems other members are experiencing
Guide lines to flashing roms
If you have any concerns about your phone, and have problems after following all the available information, available on this thread please feel free to ask a question, remember no question is too stupid! You can post on this thread or PM me directly whichever way, Happy flashing!
FAQ
Q: Help my phone will not boot.
A: You did a dirty flash didn't you? Come on admit it, okay well all you need to do is a FULL wipe like you should of done first. Learnt your lesson?
Q: Help my battery life is really bad
A: Fully charge your phone then when it is fully charged wipe the battery stats from recovery, let it fully drain down, then re-charge now your battery is calibrated.
Well I can tell one thing stright away from the poll........ we're a bunch of liars :laugh::laugh:
Haha we have all done it, at least one, haven't we? lol
I've always done clean flashes. And this might be a stupid question... But is there a way to save your settings and configurations? Everytime I've had to redo them.... the apps download by themselves thanks to google play.
Can you FIX CM9 bugs?
I am new to developing things, I find it hard to do update scripts at the moment, when I know more it will be attempted.
Karuko said:
I've always done clean flashes. And this might be a stupid question... But is there a way to save your settings and configurations? Everytime I've had to redo them.... the apps download by themselves thanks to google play.
Click to expand...
Click to collapse
Titanium backup?
---------- Post added at 04:42 AM ---------- Previous post was at 04:38 AM ----------
whoamigriffiths said:
Well I can tell one thing stright away from the poll........ we're a bunch of liars :laugh::laugh:
Click to expand...
Click to collapse
Dirty.
I things go bad do clean.
;- )=
Lazy whenever possible.
It's about right lol, My De-sense rom is updated with a few new apps and a new keyboard.
Updated first post with new roms, and updated FAQ.
Suggestions
russell664 said:
Updated first post with new roms, and updated FAQ.
Click to expand...
Click to collapse
hi, i just installed ReVoluTioN_Sense_Edition_v3.1, i faced following problems.
i was not able to successfully boot using boot.img included in the zipped ROM, instead i tried a couple more and finally was successful when i used boot.img from HTCDesireC_Explos!on_v2.1.1.
i had to restart it a couple of times to finally have a successful boot
lemme try it more and will let u know
---------- Post added at 02:31 AM ---------- Previous post was at 01:33 AM ----------
to add more, senseless / nameless ROM simply doesnt work
mzz163 said:
hi, i just installed ReVoluTioN_Sense_Edition_v3.1, i faced following problems.
i was not able to successfully boot using boot.img included in the zipped ROM, instead i tried a couple more and finally was successful when i used boot.img from HTCDesireC_Explos!on_v2.1.1.
i had to restart it a couple of times to finally have a successful boot
lemme try it more and will let u know
---------- Post added at 02:31 AM ---------- Previous post was at 01:33 AM ----------
to add more, senseless / nameless ROM simply doesnt work
Click to expand...
Click to collapse
If you look inside the Rev rom folder there is a folder for other boot.img's .
The one in Explosion I believe was either a very old stock or a very old oc .img . Either way it's very old and you really need to find one that is newer and works for you , as htc has made updates i believe.
The one that comes as std in rev mod is an 828oc , it only works for so many phones . There are some phones that can only handle a lower oc and some can only the stock speed(600).
So first try the ones in the Rev folder.
Also Nameless is moving to out of date , explosion is very out of date and I believe it was still buggy when the dev changed his phones and stopped developing it.
Hope this helps .
If you need a std boot.img there is one in this stock rom Stock rom
huge thanx
whoamigriffiths said:
If you look inside the Rev rom folder there is a folder for other boot.img's .
The one in Explosion I believe was either a very old stock or a very old oc .img . Either way it's very old and you really need to find one that is newer and works for you , as htc has made updates i believe.
The one that comes as std in rev mod is an 828oc , it only works for so many phones . There are some phones that can only handle a lower oc and some can only the stock speed(600).
So first try the ones in the Rev folder.
Also Nameless is moving to out of date , explosion is very out of date and I believe it was still buggy when the dev changed his phones and stopped developing it.
Hope this helps .
If you need a std boot.img there is one in this stock rom Stock rom
Click to expand...
Click to collapse
u r awesome man. i just solved many problems as i was not able to connect to data/WLAN but using 722 kernel, it worked like charm. Just a couple of questions please, wats the most active ROM for HTC Desire C? wats the difference between 722 and 767 kernel? i am using revolutionmod v3.3
thanx
mzz163 said:
u r awesome man. i just solved many problems as i was not able to connect to data/WLAN but using 722 kernel, it worked like charm. Just a couple of questions please, wats the most active ROM for HTC Desire C? wats the difference between 722 and 767 kernel? i am using revolutionmod v3.3
thanx
Click to expand...
Click to collapse
Glad I could help :good:
Now you are on the most active desire c rom atm . You have these options though depending on preferences.
You can use Rev de-sensed which makes it a bit quicker than the sense. Now I'd have thought this would be the most popular but it seems a lot of the guys love sense.
Then there is super -stripped de-sense . This is for us guys who want our phones as fast as possible .
Next up is SaM's xperialised sense .... Its whats written on the tin , based on sense but themed like a Sony . Take a look as its a cracking looking rom , though in fairness I've not tried it yet.
Next is amans MIUI themed rom which I believe is sense based too .
Then there is the Daddy that spawned it all Nameless but the Dev einstein.frat is not working on it atm and we have no idea if he will work on it again .
Finally there is Explosion but it was buggy and is way behind the times now .
Oh just remembered Sense5 (oops sorry russ) By the Dev of revolution and based on Rev sense but its sense5 themed and this is a real looker , and whilst it is sense based he is stripping away the excess ruthlessly .
I think thats pretty much all the roms , sorry if I missed any .
It's all down to what you like the look of , and how you use the phone .
As to kernels , obviously higher number= faster kernel as all the ones in rev folder are made by nikhil .Now he has some older kernels too and theres no telling if an older higher oc will work for you .
His best kernel to date was what he called "a flakey one for you to test rich" and its the one I've been using as my daily since he sent it to me to test . his thread is here Prometheus Kernel
My advice is to flash every single kernel he has on the first page and the one linked in my sig (my daily). You just never know which one will work for you . We have all found out that there is a lot of variance in our phones behaviour towards overclocking .
good luck just give a shout if you have any more questions
all the best
rich
whoamigriffiths said:
Glad I could help :good:
Now you are on the most active desire c rom atm . You have these options though depending on preferences.
You can use Rev de-sensed which makes it a bit quicker than the sense. Now I'd have thought this would be the most popular but it seems a lot of the guys love sense.
Then there is super -stripped de-sense . This is for us guys who want our phones as fast as possible .
Next up is SaM's xperialised sense .... Its whats written on the tin , based on sense but themed like a Sony . Take a look as its a cracking looking rom , though in fairness I've not tried it yet.
Next is amans MIUI themed rom which I believe is sense based too .
Then there is the Daddy that spawned it all Nameless but the Dev einstein.frat is not working on it atm and we have no idea if he will work on it again .
Finally there is Explosion but it was buggy and is way behind the times now .
Oh just remembered Sense5 (oops sorry russ) By the Dev of revolution and based on Rev sense but its sense5 themed and this is a real looker , and whilst it is sense based he is stripping away the excess ruthlessly .
I think thats pretty much all the roms , sorry if I missed any .
It's all down to what you like the look of , and how you use the phone .
As to kernels , obviously higher number= faster kernel as all the ones in rev folder are made by nikhil .Now he has some older kernels too and theres no telling if an older higher oc will work for you .
His best kernel to date was what he called "a flakey one for you to test rich" and its the one I've been using as my daily since he sent it to me to test . his thread is here Prometheus Kernel
My advice is to flash every single kernel he has on the first page and the one linked in my sig (my daily). You just never know which one will work for you . We have all found out that there is a lot of variance in our phones behaviour towards overclocking .
good luck just give a shout if you have any more questions
all the best
rich
Click to expand...
Click to collapse
again awesome brother, thanx a lot. Really grateful. Downloaded almost all ROMs and will try in next couple of days. Thanx a lot again
Related
I have a Sprint HTC hero with original everything.
I've been wanting to do a mod but that brings up a few questions.
1) A lot of places say the CM7 mod from here is great for this phone but I clicked around and can't find a list of things it changes/improves. Why would I install a mod and will most things continue to work (market places, email, phone utilities, purchased apps).
2) All roms have those warnings that they void warranty. How often do they brick the device? Is this something I should worry about?
Sorry for the noobish questions but I am looking towards modding the hero but I want to make sure I don't make it worse.
1.) well basically MOD's are roms that people cook themselves from the scratch android or from a base like for example the DesireHD android base. They can do things varying from the look and feel of android to adding elements like being able to browse Privately on your browsers. i know that CM7 allows you to do that. Being able to flash different roms opens up a even bigger Android World.
2.) I have been flashing back and forth for a long time and not once have i bricked the device. Besides not like a little system restore wont fix anything. Also if you happen to send you device into maintenance or repair just restore you phone back to factory settings. All of it is reversible. When i first started out it helped me to really read NOOB forums so i didn't do something i would regret, but you should have nothing to really worry about.
reply from a still nearly noob, although i read alot about roms already and flashed my sgs2. ill just attemt to help you a little here.
1) i now flashed lite'ning rom on my phone as there is no cm7 for it yet. once realeased i will also flash it as i also read that it is the most widely used rom with best support. within a thread of the specific rom there should be a list of improvements/major changes or what will be added if you flash the rom. these and mostly more battery life and/or more speed are the reasons people flash roms. after flashing the phone you will have all the things still working, sometimes even better. for apps it depends on the rom. mine for example didnt require a wipe that delets all you data on the phone. others (as i think cm7 also) require a wipe of all you on-phone personal data apps and so on (not sd card if im not mistaken, please correct me!)
2)yes, you void warranty if you flash a custom rom, root or do sth else on the firmware not published by the manufacturer. when i flashed and overflashed my phones rom for several time already i haven't had any problems. and as i read all over the net/xda there is just a very little chance to brick your phone and even there you might have possibilities to revive it, i think. but im not sure on this, cosider others informations first!
hope i could help you a little from noob to noob and enjoy flashing roms. oh and of course have a look in the htc hero android development section for roms!
cheers!
IQHU
Damn - too late, and didnt recognize until now...
Sent from my GT-I9100 using XDA App
Go to this thread and start reading some of the linked threads. All your answers can be found there.
Will updating the firmware affect anything if I wish to flash a custom ROM?
Any other precautions I should take with this virgin phone?
Thanks!
be careful
there is a post in the Development area a sticky that explains a situation
with some ICS leaks that bricked many notes... to the point where you need to pay for a new motherboard .
if you are new .. there are MANY posts and searches you will have to do to find your way around with the kernels and the roms...
yesterday i made a small folder with all the right files you need to root to install CWM and to safely being able to flash any rom you want (as safe as you can offcourse)
i have used this in 3 notes for more than 15 different roms ... and everything is fine...
since i am new to the XDA i can't post a link but i will post the instructions...
and i will send you the link to my dropbox folder for the RAR...
it has everything you need in there..
the last days i send it to friends that don't have experience and need a
1. 2. 3. kind of guide for updating and installing custom roms...
here are the instructions... the link to the rar.exe will be in your personal folder..
----------------------------------------
1. thourgh odin i use the files of the folder
"Rooted_Stock_Odex_N7000XXLC1"
with the order showed in the pic "odin file order"
the rom is now rooted and i need CWM
2. through the folder
"CF-Root-SGN_XX_OXA_LC1-v5.3-CWM5"
i choose the file "already-rooted.bat" (while my phone
is connected and the " usb debugging " pressed
i let the program do it's thing and when it's finished
it will tell me to reboot ...
now i have a safe rooted phone with CWM
3. for ANY custom rom .. GB or ICS
I FOLLOW THESE GOLDEN RULES and i am safe...
Four steps to installing any rom for galaxy note
a. put the file abyss 4.2 into your phone reboot to recovery
choose install zip and then choose the file... now you have Abyss kernel.
b. press reboot to recovery ( just to be sure )
c.chose wipe Data, cache and in advanced the dalvike cache wipe
d. if you want to be extra cool reboot to recovery one more and
chose the custom rom of your choise (the one you have downloaded allready and placed inside the phone waiting
as a zip file..
YOU ARE DONE..
This is the universal instructions for any ics rom installation.
No brick and maintain root.
TL;DR.
Disregard all of the above.
My first advice to you would be to read. Don't be lazy, just read for a couple of days. You are a native speaker and will be able to follow everything with no problems whatsoever.
There's plenty of information in the Note Forum you need to digest before taking a plunge into rooting, installing and tweaking custom Roms etc.
Unfortunately, the Note community is plagued by a series of hard-bricks ATM, and you need to know why, and adjust your actions accordingly. There are safe ways of doing things and there are lethal ways. You don't want to end up having a shiny, expensive paperweight, do you?
You need as much info as you can possibly adopt before doing anything.
chasmodo said:
TL;DR.
Disregard all of the above.
My first advice to you would be to read. Don't be lazy, just read for a couple of days. You are a native speaker and will be able to follow everything with no problems whatsoever.
There's plenty of information in the Note Forum you need to digest before taking a plunge into rooting, installing and tweaking custom Roms etc.
Unfortunately, the Note community is plagued by a series of hard-bricks ATM, and you need to know why, and adjust your actions accordingly. There are safe ways of doing things and there are lethal ways. You don't want to end up having a shiny, expensive paperweight, do you?
You need as much info as you can possibly adopt before doing anything.
Click to expand...
Click to collapse
And as chasmodo said some important thread to be viewed are this,this,this,this
The links include Public service announcements for bricking issues,rooting guides and some threads you must read to understand the problem
Thanks so much!!! )
Hello guys, it's me (nay, not Mario :laugh again. Another question.
Got a new battery which seems to hold charge well so I thought I might flash something in the likes of CM9 or CM10(.1).
I'm starting this thread because I would like to be totally sure what should I do (although I know I will never be 100% sure I'm doing it right). The reason I'm starting this thread is fear from bricking my phone (now troll me).
A little background (might be TLTR so freely skip it):
A year or so ago, I had a LG GT540 in my possession. Spoiled by the painlessness (is this a word?) of flashing Huaweis I fearlessly dared to flash fastboot on it in order to flash custom ROMs and stuff. The installation instructions seemed dead simple. Battery was full. Followed the procedure from letter to letter. Despite the fact that I followed the whole tutorial, in the end I got a hard brick. One hour later I thought it ought to be either finished or terminated due to an error of some kind. But no. It just stuck. Unplugged it and tried to turn it on. Fail, bootloop. Tried to reflash it, in all the modes I knew of. There were two or so modes: emergency and some über-emergency mode thingy. Fail. Then I tried with the official LG update tool. Final fail. That was the worst idea one could ever get, it got hard bricked, with no signs of life at all. RIP.
Back to the question.
As a proof that I used that damned search feature (at least tried to) here goes the procedure as I've understood it (while searching):
do a Nandroid and TB backup (optional, but you might really regret it if you don't do so)
back up your EFS folder
wipe data/factory reset
flash the ROM thru recovery
reboot
if it bootloops, reboot to recovery manually
flash the ROM again to finalize the procedure
eventually flash GApps
So,
did I leave out something?
what's the most reliable procedure/app to backup EFS?
is there a way to verify if EFS is properly backed up?
what's the proper, ahem, primer ROM to flash first and make stuff glue together nicely?
Semaphore's recovery tends to blink when browsing through using the capacitive menu button instead of volume buttons, is that a problem?
is Semaphore's recovery itself, regardless of the before mentioned issue, appropriate for flashing ICS/JB (or should I flash some other kernel/recovery before flashing)?
will I survive on XDA with that much questions at once?
It's SIM unlocked (don't know how, second hand phone, most likely with Helroz's unlock application), other details are in the signature.
Thanks in advance!
EDIT: See last post (#7 if the discussion goes on) for more details and answers to my questions.
http://www.youtube.com/watch?v=2DLySUtI8vo
http://www.youtube.com/watch?v=iRnH13sRAIc
http://www.youtube.com/watch?v=1RoZU5ZPMS4
http://www.youtube.com/watch?v=PwHVm90HO1w
check out these and you wont brick your phone happy flashing
I have already flashed a rooted kernel with CWM (CF-Root and later Semaphore).
Please, I know my English ain't perfect, but try to skim through my post. At least the second half of it.
your english is fine i read your post all of it i was just giving you a bit of direction incase you soft bricked your sgs,and as for what the best rom is they are all good roms the devs spend alot of time developing them its just a matter of what set up you like so try them all till you find one you like darkyrom v11 ,is pretty smooth its ics and stable cm 9 is good also ,remics jb 4.2.2 is good also .sgs i9000 is almost impossible to brick just read or watch the info two or three times just to be sure goodluck
TIGER 123 said:
your english is fine
Click to expand...
Click to collapse
Aw, thank you! Sorry for me being kinda needlessly rude.
TIGER 123 said:
and as for what the best rom is they are all good roms the devs spend alot of time developing them its just a matter of what set up you like so try them all till you find one you like darkyrom v11 ,is pretty smooth its ics and stable cm 9 is good also ,remics jb 4.2.2 is good also .
Click to expand...
Click to collapse
You meant this?
moorkai said:
what's the proper, ahem, primer ROM to flash first and make stuff glue together nicely?
Click to expand...
Click to collapse
In fact I wanted to know (along with the doubts from post #1) what do I need to flash prior to playing with ICS and/or JB because I thought that there are some ROMs (e.g. CM9) that do the necessary repartition process(es) as there are some partition layout differences between stock Gingerbread and the newer ICS and JB ROMs... and that failing to do so might lead to soft/hard bricks.
I know that asking questions like "What's the best ROM for my phone?" might lead to subjective and conflicting answers as some prefer lightweightness over functionality and vice versa, thus I don't prefer to do so, neither I did so in my first post. Sorry if you understood me otherwise.
Hope that I made some things more understandable now.
Okay, solved this doubt:
moorkai said:
what's the most reliable procedure/app to backup EFS? Tar zcvf contents of the /efs folder in terminal.
Click to expand...
Click to collapse
However, in one of the videos you posted here CWM 2.5.1.2 was used and thus it additionally stresses the following question:
moorkai said:
is Semaphore's recovery itself, regardless of the before mentioned issue, appropriate for flashing ICS/JB (or should I flash some other kernel/recovery before flashing)?
Click to expand...
Click to collapse
Help me!
I finally dared to flash CM10.1! Everything went silky smooth. Here are my conclusions for further reference (maybe someone can find them useful). These might be inaccurate, but I didn't brick my phone. After all, don't hesitate to correct me if I'm wrong.
How I flashed CM10.1:
do a Nandroid and TB backup (optional, but you might really regret it if you don't do so)
back up your EFS folder
wipe data/factory reset, wipe cache partition, advanced > wipe dalvik cache
flash the ROM through recovery (install zip from sdcard > choose zip from sdcard)
now it will reboot and finalize the flashing if everything is OK
eventually flash GApps
Questions from the first post and ...answers:
Q: Did I leave out something?
A: Most likely, not.
Q: What's the most reliable procedure/app to backup EFS?
A: Type the following stuff in Terminal Emulator or adb shell (root privileges necessary):
Code:
su
tar zcvf /sdcard/efs-backup.tar.gz /efs
# some users suggest that backing this up can also help if IMEI goes belly up
cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
Q: Is there a way to verify if EFS is properly backed up?
A: Dual File Manager is quite useful for testing archive integrity.
Q: What's the proper, ahem, primer ROM to flash first and make stuff glue together nicely?
A: CM10.1, I guess.
Q: Semaphore's recovery tends to blink when browsing through using the capacitive menu button instead of volume buttons, does that mean it will cause ROM installation to fail?
A: I don't know, maybe, so flash CM10.1 with CF-Root kernel installed instead.
Q: Is Semaphore's recovery itself, regardless of the before mentioned
issue, appropriate for flashing ICS/JB (or should I flash some other kernel/recovery before flashing)?
A: See previous answer.
Hello all
This is sort of a question for finding a solution for my Samsung Galaxy S. I have been using xda for a couple of years now, as all of us for rooting and putting custom roms on our devices so they would be better and quicker. So after all this time i realy dont have time to mess around with custom roms and i would like to install one good stock rom with maybe a good kernel (to reduce the lag etc..) and have a solid stable device.
I have a stock rom now its a GT_I9000_XWJW5_XDJV1_OXXJVC_Sbl with a CF-Root-XX_OXA_JW4-v4.4-CWM3RFS kernel, and the problem is im getting all kinds of self reboots sometimes, and big lags issues, and when i start the device i have some strange let say lines and shapes like it broken, but after a sec or two they desapire. So the final question is could someone recommend me a good stock rom and a kernel so i can finaly leave my device alone and not touch anything on it roms wise again!
Thank you!
Regards!
Luka321 said:
This is sort of a question for finding a solution for my Samsung Galaxy S.
Click to expand...
Click to collapse
over a period of time, all Devices will have this problem as accumulated installations/uninstalltions, app data, downloads etc will have left over junk, that needs to be cleaned out.
Best way to resolve this is to move everything in your SD card to PC. than format SD card, than reinstall latest ROM for your region and copy bac whatever data that you will use and keep rest in your PC or delete.
Prior to flashing, full wipes and a factory reset would be best.
latest Stock ROM's, choose from here , Clean flashing guide, follow this or you like other ROM's check here
Check this out! Links to useful Guides and " Banned " Documentaries
Thank you very much! I hope this helps other people that are looking for what i have found now
Dear Android users,
I am new to the whole rooting procedure and have a few questions regarding installing new roms and kernels.
1. Is it harmful to install new roms one after the other? For example, I just installed a new rom and after one hour of experimenting with it I wanted to try out a different rom so I just re-flashed my device. How often can you flash your device without the risk of bricking it or something else going wrong during the process? I know that in order to find the perfect rom for yourself one must flash their devices a several times until they have found what they want but suppose if i were to install 10 different roms in an entire day, would that be harmful to the device or is it fine as long as you know what you are doing and you are installing it properly and carefully ?
2. Suppose if a certain rom was installed with a preferred kernel of your choice and during the rom installation you did not know exactly what features to install or remove e.g. with Aroma installer or any other kind and then once the installation was complete and you were using the new rom you felt that you wanted to go back and install a few more things which you didn't earlier. Will you then have to Install the rom all over again or do you have the option to modify the rom while its installed?
Sorry if any of the questions sound stupid or irrelevant but these are some things which are important to know
Hi there! Allow me to welcome you to the rooting world! I'll do my best answering your questions. Not to come off as someone who's pompous, I've been using a rooted device for nearly 6 years now, so I've been through the woods quite a bit. I've had my HTC One since June of 2013.
1. Even though sometimes it's looked at as "okay" to dirty flash (flash one ROM over another; this method is mostly used when updating a ROM and the two ROMs are on the same version of Android), I don't take any chances. Besides, if you flash more than one ROM on top of another, it can cause your device to get super slow. So here's my rule of thumb: Almost always wipe before flashing, unless it's a minor update to the ROM you're currently using. Also, when in doubt of whether or not to wipe before flashing a new ROM, ALWAYS DO IT. Haha, better than having a very expensive paperweight! Flashing multiple times in a day isn't a bad thing, as long as your phone is plugged into some power source and you wipe your data and cache before every flash. One thing to keep in mind though, for a ROM to "settle in" to your device, the battery will drop excruciatingly fast the first day you have a new ROM that you decide to keep. I personally let my phone die after I decide to stick with a ROM and leave it off while charging to 100%. Obviously, this can't be done by most because of time restraints and busy lifestyles, so just be aware that you will have pretty... misleading battery results for the first few days of having a new ROM. It's simply optimizing the experience and what you do on your phone around the battery. So to sum up, wiping and flashing is all good as long as you're careful, but don't expect the battery to last you all day for the first few days after deciding on a ROM.
2. This sort of thing depends on the ROM and how the Aroma is set up by the developer. Most of the time, the answer is that you can go back in later and change things at the expense of minor battery issues and sometimes, depending on the modification, it can stop your phone from working correctly. Because of that latter fact, I usually play it safe and wipe before flashing to make the modification to the ROM. If you're installing a separate file to modify the ROM (aka, a mod) then flash it after the ROM is already flashed. A real advantage to having a separate, flashable mod is that you don't have to wipe before flashing it. Just flash it after whatever ROM you plan to use is in place.
Misc. tips:
- Try your best to keep your firmware as up to date as possible. Because we don't get notified of when this updates (roughly every 4 or 5 months), it's our responsibility to make sure we take care of the firmware asap. Not updating it can result in poor performance, low compatibility with newer ROMs, and bad battery life.
- Never, EVER flash more than one GApps package on top of one another. This can cause a ton of issues.
- Speaking of GApps, always flash them (if necessary, of course) after the ROM is flashed, but don't reboot the phone in between those two flashes.
Don't worry about the "irrelevancy" of your questions, man! We were all new to this at a time too, and back then, I bet most of us wished this sort of information was given to us without attitude or the "this guy's a noob" mentality. You should be all good to go! If you have any other questions (or if you want any ROM/mod recommendations) feel free to ask, my friend!