This is probably just me but I'm starting to think we are over complicating the ROM installation process by having different versions of recovery and flashing. We already have KIES and odin, do we need different recovery installations too?, tegrak, CMR, chainfires etc? We are now seeing ROMS that can only be flashed with one type which cant be good as its causing fragmentation of development. I may also have contributed to two people who have bricked their phones recently.
Why on earth are we doing this?, wouldnt it be much better to use one type of recovery, that way anyone can flash any ROM with it without having to change root / kernels etc.
I am sure each different version has its own advantages but are these really worth the fragmentation it is causing, be nice if devs all decided to get together and come up with a one fits all CWR which is then used on all ROMS and all Phones.
I can dream cant I, feel free to put me straight on this if I am missing something here.
couldn't agree more. i rooted my phone the other day with a kernel change, but now i want to isntall a rom but cant even start to work out the way to get cwm on to flash a rom!!! annoyinh to say the least.... the x10 and sgs1 i had were a breeze
da.trute said:
This is probably just me but I'm starting to think we are over complicating the ROM installation process by having different versions of recovery and flashing. We already have KIES and odin, do we need different recovery installations too?, tegrak, CMR, chainfires etc? We are now seeing ROMS that can only be flashed with one type which cant be good as its causing fragmentation of development. I may also have contributed to two people who have bricked their phones recently.
Why on earth are we doing this?, wouldnt it be much better to use one type of recovery, that way anyone can flash any ROM with it without having to change root / kernels etc.
I am sure each different version has its own advantages but are these really worth the fragmentation it is causing, be nice if devs all decided to get together and come up with a one fits all CWR which is then used on all ROMS and all Phones.
I can dream cant I, feel free to put me straight on this if I am missing something here.
Click to expand...
Click to collapse
But everyone is using CWM anyway...
And the .zip is a standard way to flash a ROM. So in theory, you can use any recovery to flash your zip
So there's no need to come up with some one-size-fits-all, as the zip files used meet a standard
Freedom to choose is a great thing. I like having options.
pulser_g2 said:
But everyone is using CWM anyway...
And the .zip is a standard way to flash a ROM. So in theory, you can use any recovery to flash your zip
So there's no need to come up with some one-size-fits-all, as the zip files used meet a standard
Click to expand...
Click to collapse
I am currently using cognition ROM, are you suggesting I can download any ROM, say Villain and copy to my SD and install without doing anything else?, I dont think that is the case, it mentions a different root, as does extreme. Cog and mui have no mention of changing root.
Intratech said:
Freedom to choose is a great thing. I like having options.
Click to expand...
Click to collapse
It is yes, however you seem to have misunderstood the thread, having different methods being forced up you by different cooks is not choice, choice would be that all methods were compatible and interchangeable, they are not apparently. Some require different roots / kernels.
EDIT. not suggesting anything is really being forced on us, I appreciate all dev work, just hoping for a bit more conformity of installation process.
da.trute said:
I am currently using cognition ROM, are you suggesting I can download any ROM, say Villain and copy to my SD and install without doing anything else?, I dont think that is the case, it mentions a different root, as does extreme. Cog and mui have no mention of changing root.
Click to expand...
Click to collapse
You copy it to internal SD, pull your head out of your ass, turn phone off, turn phone on holding menu and volume up and choose to flash zip from SD card.
Just.
Like.
Every.
Other.
Rom.
seshmaru said:
You copy it to internal SD, pull your head out of your ass, turn phone off, turn phone on holding menu and volume up and choose to flash zip from SD card.
Just.
Like.
Every.
Other.
Rom.
Click to expand...
Click to collapse
Cognition uses CMR root, Villain uses CF-root, I am pretty sure you cannot flash Villain straight of the top of a non CF rooted phone, or I am wrong?
da.trute said:
Cognition uses CMR root, Villain uses CF-root, I am pretty sure you cannot flash Villain straight of the top of a non CF rooted phone, or I am wrong?
Click to expand...
Click to collapse
See, if you actually had developed the ability to read, you would know that all root is is the su script in the ROM and SuperUser.apk, nothing more.
You would also know root has nothing to do with flashing ROMs, since you can have CWM as recovery without having root.
Now if you're flashing an entirely different ROM you might want to select "wipe data/factory reset" before flashing but you can still flash using CWM.
Turn phone off, turn phone on holding volume up and center button, select wipe data/factory reset, and then flash zip from SD card.
Wow. He's just asking a question. Why belittle people for asking?
duuurp said:
Wow. He's just asking a question. Why belittle people for asking?
Click to expand...
Click to collapse
Because I see exactly 3 threads on the same page that could either answer his question or link him to the answer. But people are too lazy to read.
Due to people like this we have a thread here which isn't needed at all since there is conformity to flashing across all ROMs. All because people make claims about things when they don't even know how it works.
The big difference in swapping from one custom rom to another is not the method of flashing but do you need a clean phone to install a custom rom on top of another one .
My personal choice is a fully wiped phone before installing a new custom rom .
Methods CWM or Odin mostly CWM as thats the major choice for devs .Kies is not a rom flash tool .
Choice also gives a better recovery option .
Villain on top of or below Cognition both use same flash method via rooted CWM flash .
The problem on this forum is not three or four choices but a complete refusal by many to even bother reading any instructions .
jje
duuurp said:
Wow. He's just asking a question. Why belittle people for asking?
Click to expand...
Click to collapse
Hi, you get used to these ***** after a while
seshmaru said:
See, if you actually had developed the ability to read, you would know that all root is is the su script in the ROM and SuperUser.apk, nothing more.
You would also know root has nothing to do with flashing ROMs, since you can have CWM as recovery without having root.
Now if you're flashing an entirely different ROM you might want to select "wipe data/factory reset" before flashing but you can still flash using CWM.
Turn phone off, turn phone on holding volume up and center button, select wipe data/factory reset, and then flash zip from SD card.
Click to expand...
Click to collapse
You have to change kernel at the end of flash on Villain which I suppose isnt the same but is still a difference in installation process
what about touch extreme, whats this about then?
Make sure you got CF Root CWM (not the clockworkmod root) go into CWM, flash zip file, done! its that simple!
PS. some roms out there installs through clockworkmod, not the one by Chainfire, in those cases you must flash Chainfires Root with his version of CWM first!
da.trute said:
You have to change kernel at the end of flash on Villain which I suppose isnt the same but is still a difference in installation process
what about touch extreme, whats this about then?
Make sure you got CF Root CWM (not the clockworkmod root) go into CWM, flash zip file, done! its that simple!
PS. some roms out there installs through clockworkmod, not the one by Chainfire, in those cases you must flash Chainfires Root with his version of CWM first!
Click to expand...
Click to collapse
So let me see, it says flash the .zip with CWM.
So... Lets turn phone off, turn phone on holding volume up, center button and power button, wipe data/factory reset, and then flash .zip from SD card.
All of a sudden it magically works.
PROTIP: They're talking about the CWM app, which you don't need, every ROM still has clockworkmod recovery installed so rebooting with volume up, center button and power button will always let you flash the .zip file.
Kernel files should always be flashed with Odin if you are flashing them seperately since it gives better security. Even if they have a flashable .zip.
It may seem like there are a hundred different versions of CWM recovery but they're all based on the same thing; CWM. They all work on the same premise of copying the zip to the phone and then flashing. Some have integrated apps, some don't but the basic premise remains. The other option is Odin/Heimdall but as one is .tar based and the other is .zip there shouldn't be too much confusion here
seshmaru said:
So let me see, it says flash the .zip with CWM.
So... Lets turn phone off, turn phone on holding volume up, center button and power button, wipe data/factory reset, and then flash .zip from SD card.
All of a sudden it magically works.
PROTIP: They're talking about the CWM app, which you don't need, every ROM still has clockworkmod recovery installed so rebooting with volume up, center button and power button will always let you flash the .zip file.
Kernel files should always be flashed with Odin if you are flashing them seperately since it gives better security. Even if they have a flashable .zip.
Click to expand...
Click to collapse
what does this actually mean then?
"Make sure you got CF Root CWM (not the clockworkmod root)"
I have flashed all three roms using the exact same method .
Changed kernels four times this week using CWM .
Revived one bricked phone using Odin .
jje
Hollow.Droid said:
It may seem like there are a hundred different versions of CWM recovery but they're all based on the same thing; CWM. They all work on the same premise of copying the zip to the phone and then flashing. Some have integrated apps, some don't but the basic premise remains. The other option is Odin/Heimdall but as one is .tar based and the other is .zip there shouldn't be too much confusion here
Click to expand...
Click to collapse
which kind of proves my point really, if they all do the same thing then there is no need for them and no need to stipulate their usage, it just makes flashing more confusing for noobs.
da.trute said:
which kind of proves my point really, if they all do the same thing then there is no need for them and no need to stipulate their usage, it just makes flashing more confusing for noobs.
Click to expand...
Click to collapse
No, there is only 1 method for ROM flashing, CWM. Every ROM has CWM, CWM is the end all be all for you, no matter what different apps do, they all use 1 method CWM. CWM CWM CWM. Stop being dense and read up before posting dumb factually wrong claims.
Every single ROM can be flashed by holding volume up, center button and power, how difficult is it to grasp this concept?
Here this video should help you.
http://www.youtube.com/watch?v=JmvCpR45LKA
Related
Read This
http://forum.xda-developers.com/showpost.php?p=9542514&postcount=662
Alternatively, just read my installation instructions:
http://forum.xda-developers.com/showthread.php?t=842004
I think I'm going to start using a rar format - might be a way to differentiate between the actual release and the update.zip inside. Not sure why I didn't think of that, before.
Still not that simple for me, since even a "Gtablet Vet" like myself tried the OP method and failed. My second out of box new Gtablet went in perma-loop when simply installing straight to 2.0, via recovery folder & update.zip. Ended up having to get CW on the device by putting on the sd card, remapping command and stopping the loop with power + volume to get CW installed. I then had to install TnT 1.02 and then finally got 2.0 installed after that (cache and data wipe of course).
Cleanest way seems install 1.02 via recovery folder / update.zip method and then install 2.0 the same way. Thats is unless I just had bad luck with second Gtablet. VERY possible.
added:
Frankly, we seem at the stage now where CW seems a survival requirement- IF you want to keep trying new roms & updates.
roebeet said:
Alternatively, just read my installation instructions:
http://forum.xda-developers.com/showthread.php?t=842004
I think I'm going to start using a rar format - might be a way to differentiate between the actual release and the update.zip inside. Not sure why I didn't think of that, before.
Click to expand...
Click to collapse
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
LRiley said:
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
Click to expand...
Click to collapse
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
roebeet said:
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
Click to expand...
Click to collapse
Installing TnT 1.0 roms appears to zap CW pretty good.
roebeet said:
The only issue with cwm is that it's not easy to remove it, once you have it. I think you need to use nvflash to get rid of it. I love cwm but I can't assume that everyone uses it.
And trust me, not everyone does. I sees posts here and I get PM's as well, and many people are still using standard recovery.
Click to expand...
Click to collapse
I have found that you can put the stock recovery img (let's call it recovery-stock.img) on the sdcard and get an adb shell while booted into cw recovery. Then it's just a
Code:
flash_image recovery recovery-stock.img
That should get you back to stock recovery.
Sent from my Incredible using XDA App
LRiley said:
u didn't think of it because it was only a problem to ppl that half read the instructions, downloaded the zips and just tried to install as-is...
Also don't understand why ppl want to keep standard recovery, clockwork is made to install custom roms so its easier for these task
Click to expand...
Click to collapse
I had to go back to stock at first because I kept getting status 7 errors with CW. Roebeet's suggestion to partition sdcard with CWR seems to have solved that.
Sent from my Incredible using XDA App
Flashed 2.0.0
I liked TnT 2.0.0 and it really helped performance but the gtab is still full of issues....
Out of the box my Gtab's proprietary email and photo app forced closed before ever loading. the viewsonic update didn't fix it and so I flashed it with TnT 2.0.0.
I got a System UID's warning while I did it and I guess that was the cause of those apps not working. I then did a system reset to factory default or whatever its called and lost everything but after flashing TnT 2.0.0 again it worked a lot better and the email app worked great, photo app still doesn't work. My new problems are that the sound and and flash don't work anymore. I reinstalled flash and the browser just crashes whenever flash is involved with a site. Sound will sometimes work when I first boot up but it quits after a while, especially after waking from sleep. A lot of the time I get crackles and pops when I first boot up or wake it from sleep.
I am returning this Gtab and I am going to buy another one from somewhere else in hopes that I don't get these issues out of the box.....I haven't read anywhere that anyone has experienced these specific problems other than the sound; as this is a TnT error; so I warn all, DON'T BUY FROM STAPLES!!!
Hey guys, I'm very much a newbie here so bear with me. I upgraded to the 2.21version about a month ago when some upgrade came out. Thinking it was an official upgrade I did it. I flashed the phone and it seemed to work ok. The problem is the camera doesn't work rendering my bar code not to work either. It seems ok other than that item, but would really like to get the camera up and running, and since Samsung doesn't seem to have the real 2.2 upgrade any time in the near future, I would like to fix this without flashing it again. What can I do to fix? Phone info is Model number sph-d700 baseband version s:d700.0.55.dk28 kernel version 2.6.32.9 fyoyo.dk28
Thanks in advance
Mike
mazspeed said:
Hey guys, I'm very much a newbie here so bear with me. I upgraded to the 2.21version about a month ago when some upgrade came out. Thinking it was an official upgrade I did it. I flashed the phone and it seemed to work ok. The problem is the camera doesn't work rendering my bar code not to work either. It seems ok other than that item, but would really like to get the camera up and running, and since Samsung doesn't seem to have the real 2.2 upgrade any time in the near future, I would like to fix this without flashing it again. What can I do to fix? Phone info is Model number sph-d700 baseband version s:d700.0.55.dk28 kernel version 2.6.32.9 fyoyo.dk28
Thanks in advance
Mike
Click to expand...
Click to collapse
well, are you rooted? i would suggest you follow this guide to get back to stock
http://forum.xda-developers.com/showthread.php?t=773032&highlight=brick
and also, this thread will get moved because it is placed in the wrong section, just a heads up in case you come back and cant find it! it will be moved to the general section
Wow, lot to try and decipher. I'm not sure how or what I should do. everything works but the camera. Is this a bad build or bad software download?
mazspeed said:
Wow, lot to try and decipher. I'm not sure how or what I should do. everything works but the camera. Is this a bad build or bad software download?
Click to expand...
Click to collapse
well, are you rooted? it might just be the build. there are alot of different 2.2.1 builds out there for the epic. if you are rooted, you can just flash another rom, it will fix the issue. if you arent rooted, you will have to follow that guide to get back to stock. and i know its alot to decipher, but just take it ONE STEP AT A TIME. i would search for youtube videos on how to do it too, thats what helps me the most.
Ok, sorry for the dumb question, but how do I know if I am rooted?
mazspeed said:
Ok, sorry for the dumb question, but how do I know if I am rooted?
Click to expand...
Click to collapse
download the app "superuser" from the market, then download "android terminal emulator" from the market, open the terminal emulator, type "su" hit enter, and if you are rooted, a pop up will come up and say "blabbity blah is asking for superuser permission, accept? hit accept. if it worked, you should see this in the terminal emulator now "#" without the quotes, that is how you know if you are rooted. if nothing happens in terminal emulator, you are not rooted.
If there is a newer version, I would not mind going to that, if there is. I did do this about a month ago.
mazspeed said:
If there is a newer version, I would not mind going to that, if there is. I did do this about a month ago.
Click to expand...
Click to collapse
even if there is, you would have to go back to stock and then flash it through odin man
It said "not found" in the blue screen of su. I can only post every 5 min, bear with me, and thanks again for the help. What's next? Ok, going back to stock would be fine till samsung finally goes to a new version. If I go back to stock, will I lose everything? I did download Ti backup and it doesn't work. It says "please verify if the rom is rooted". And then it doesn't work. I guess I could have checked there to see if it was rooted.
he does not have to "go back to stock" to flash a different 2.2 build through odin, im sorry but that made entirely no sense
Check this link
Here this link should give you a better understanding of how to go back to stock.
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700#Odin_Stock_Flashing
Look under the section for odin stock flashing. And btw DK28 is not officially by samsung. It is a leaked build and they do recommend against not installing it since it is not finalized. The current most official kernerl is DI18 so you should grab the tar.md5 for that rom version and flash back to stock using odin. If you still want to try unofficial froyo roms make sure you use the one click root and recovery method to make sure you are rooted after going back to stock DI18. Then you are free to flash any froyo roms you want. Hope this helps man.
Zeinzu said:
he does not have to "go back to stock" to flash a different 2.2 build through odin, im sorry but that made entirely no sense
Click to expand...
Click to collapse
my understanding of odin is that in order to update builds, you have to downgrade. like 3/4's of the roms here make you unroot/downgrade, then re-root in order to install them.
oshizzle1991 said:
my understanding of odin is that in order to update builds, you have to downgrade. like 3/4's of the roms here make you unroot/downgrade, then re-root in order to install them.
Click to expand...
Click to collapse
I have been flashing for a while and never had to downgrade to update builds. If you have already flashed to the leaked stock DK28 you can install as many DK28 based roms as you want through clockwork mod as long as you wipe data/cache. You are definitely right in regards that he should odin back to stock Eclair DI18 since he is having camera issues because that definitely might help as it has helped me many times.
Ok, is there a newer build than what I have now, and if I can run it, how do I do that? Thanks again guys for all the help. I really do appreicate it.
I don't mind trying newer builds, and since this build is well over a month old, I would think there would be newer ones, maybe?
Please post questions in General section.
mazspeed said:
Ok, is there a newer build than what I have now, and if I can run it, how do I do that? Thanks again guys for all the help. I really do appreicate it.
I don't mind trying newer builds, and since this build is well over a month old, I would think there would be newer ones, maybe?
Click to expand...
Click to collapse
Okay i think you may be a little confused. There is no newer build. There is ONE stock DK28 leaked build which is what i assume you have. Now there are custom roms BASED on that leaked build which have various customizations and whatnot. You are more than welcome to flash a custom rom of your liking but they are not "newer builds", just customized roms based from the ONE leaked DK28 build.
Your best bet is to go back to di18 and wait on the ota. Stay there a little bit and do some more reading and learn a little more before you start doing this stuff. Learn about rooting and flashing roms. If you didn't know if you were rooted or not then most likely you were not. Use Odin to go back to di18. I know ut sucks losing all your data but in doesn't take that long to set your phone back up. Good luck.
hgvidal said:
Okay i think you may be a little confused. There is no newer build. There is ONE stock DK28 leaked build which is what i assume you have. Now there are custom roms BASED on that leaked build which have various customizations and whatnot. You are more than welcome to flash a custom rom of your liking but they are not "newer builds", just customized roms based from the ONE leaked DK28 build.
Click to expand...
Click to collapse
This guy is right. What you have is most likely the stock version of the DK28 build. That version is known to have many issues. Being on that stock build of DK28 according to the info you posted, you are welcome to flash a customized DK28 ROM that has addressed these issues.
Again, you will not be required to downgrade your build in order to flash any customized ROM based on the same build (DK28)
For practical purposes, to flash (install) a custom ROM you WILL be required to be "rooted" and install a program onto your phone that gives you the ability to flash. The program that is universally used is called "ClockworkMod Recovery" and employs a simple "one-click" method to install onto your phone. This one-click method also gives you the root access on your phone that is required to flash a ROM. You can find the program and instructions on how to install it here:
http://forum.xda-developers.com/showthread.php?t=770388
Customized ROMs can be found in the Epic 4G Android Development section of this forum. Note that you will ONLY be looking for ROMs based on your DK28 build. ALL of these ROMs will require you (on your stock DK28 build) to do a complete wipe of the data from your phone. Your data can and should be backed up however, and the ClockworkMod Recovery mentioned above allows you to do both the data backup and data wipe.
Instructions on how to install ROMs are often included in their post. They should look something like this:
1. Download the DK28 ROM you want (it will come in .zip format) and move the .zip file to main (base/root) folder of your phone's SD card.
2. Using ClockworkMod Recovery, BACKUP your data by selecting "Backup and Restore" and then "Backup"
3. Using ClockworkMod Recovery, WIPE your data by doing ALL of following:
a. Select "wipe data/factory reset". Do this three times (3x)!
b. Select "wipe cache partition". Do this three times (3x)!
c. Select "advanced" and then "wipe dalvik cache". Do this three times (3x)!
4. Using ClockworkMod Recovery, FLASH (install) the ROM you downloaded by selecting "Install zip from sdcard" and then selecting the ROM's .zip file in the root folder of your sd card.
5. Using ClockworkMod Recovery, select "reboot system now" and WAIT for phone to boot. This will take longer than a normal boot up.
I find these ROMs work well for me:
http://forum.xda-developers.com/showthread.php?t=878944
http://forum.xda-developers.com/showthread.php?t=861367
http://forum.xda-developers.com/showthread.php?t=869295
http://forum.xda-developers.com/showthread.php?t=856715
timothylaws said:
This guy is right. What you have is most likely the stock version of the DK28 build. That version is known to have many issues. Being on that stock build of DK28 according to the info you posted, you are welcome to flash a customized DK28 ROM that has addressed these issues.
Again, you will not be required to downgrade your build in order to flash any customized ROM based on the same build (DK28)
For practical purposes, to flash (install) a custom ROM you WILL be required to be "rooted" and install a program onto your phone that gives you the ability to flash. The program that is universally used is called "ClockworkMod Recovery" and employs a simple "one-click" method to install onto your phone. This one-click method also gives you the root access on your phone that is required to flash a ROM. You can find the program and instructions on how to install it here:
http://forum.xda-developers.com/showthread.php?t=770388
Customized ROMs can be found in the Epic 4G Android Development section of this forum. Note that you will ONLY be looking for ROMs based on your DK28 build. ALL of these ROMs will require you (on your stock DK28 build) to do a complete wipe of the data from your phone. Your data can and should be backed up however, and the ClockworkMod Recovery mentioned above allows you to do both the data backup and data wipe.
Instructions on how to install ROMs are often included in their post. They should look something like this:
1. Download the DK28 ROM you want (it will come in .zip format) and move the .zip file to main (base/root) folder of your phone's SD card.
2. Using ClockworkMod Recovery, BACKUP your data by selecting "Backup and Restore" and then "Backup"
3. Using ClockworkMod Recovery, WIPE your data by doing ALL of following:
a. Select "wipe data/factory reset". Do this three times (3x)!
b. Select "wipe cache partition". Do this three times (3x)!
c. Select "advanced" and then "wipe dalvik cache". Do this three times (3x)!
4. Using ClockworkMod Recovery, FLASH (install) the ROM you downloaded by selecting "Install zip from sdcard" and then selecting the ROM's .zip file in the root folder of your sd card.
5. Using ClockworkMod Recovery, select "reboot system now" and WAIT for phone to boot. This will take longer than a normal boot up.
I find these ROMs work well for me:
http://forum.xda-developers.com/showthread.php?t=878944
http://forum.xda-developers.com/showthread.php?t=861367
http://forum.xda-developers.com/showthread.php?t=869295
http://forum.xda-developers.com/showthread.php?t=856715
Click to expand...
Click to collapse
does he still have to flash the DK28 modem?? i am totally new to odin, im coming from 4 HTC devices, so ODIN is like new territory to me.
oshizzle1991 said:
does he still have to flash the DK28 modem?? i am totally new to odin, im coming from 4 HTC devices, so ODIN is like new territory to me.
Click to expand...
Click to collapse
He does not have to flash the DK28 modem because he's already on it. This is indicated by his baseband version being S:d700.0.5S.DK28
OK so first off I want to apologize, I am a noob. Im on many other differedt types of forums and I know n00bs are universally hated. So bear with me.
I know a decent bit about computers/phones/technology. Well more then your average bear at least. Not as much as you guys though.
My phone is permarooted, and now im looking to put a custom rom on. My brother permarooted it for me.
OK I know you guys are gonna say omgz read all the info on the site it's all here. I went to the android dev forum and there are sooooooo many builds I don't even know where to begin. I know none of the cm mods are 'stable' yet. But surely some more then others, no? What are the differences between 6, 6.1, and 7? Any reccomendations? I will be attempting this tomorrow.
If anyone can give me some pointers, point me in the right direction, newb friendly teks.
Any advice or input in very appreciated.
Thanks.
If you like stock android, I would highly recommend cyanogen mod 7. It turned my mt4g into a speed demon. And it is stable enough to a daily driver.
If you like sense, ( why would anyone) then I'd recommend the ice glacier rom, it is close to stock but with alot of bloatware removed.
Sent from my HTC Glacier using XDA App
http://forum.xda-developers.com/showthread.php?t=916930
I guess.I'd like to go with this build.
The instructions aren't very newb friendly. Is there a guide somewhere that goes a bit more in depth on the steps?
INSTRUCTIONS:
-First time flashing CM 7 to your MT4G (or coming from another ROM)?
1. Unlock/root your device and install Clockwork Recovery via ROM Manager
Clockwork recovery is an app? How does one install via rom manager?
2. Do a Nandroid backup!
What does this entail/what tools would I news to do this?
3. Flash ClockworkMod Recovery 3.x 3. WIPE
???
4. Install the ROM
???
5. Optionally install the Google Addon
Why wouul one want to do this and what would the benefits bbe? How would you go about it as well?
I know y'all are prolly like wtf how annoying. But is really apprexiate the help. I have my reasons for doing this, I don't just think its cool or something.
Im more then willing to do the research myself there's just so much info out there i dontknow where to go. Even a point in the right direction would be appreciated.
Thanks.
kr00kd said:
1. Unlock/root your device and install Clockwork Recovery via ROM Manager
Clockwork recovery is an app? How does one install via rom manager?
Click to expand...
Click to collapse
"ROM Manager" is an app (search the Market). Clockwork Recovery is installed via ROM Manager (do it two or three times, sometimes it won't "stick" right after you are rooted).
kr00kd said:
2. Do a Nandroid backup!
What does this entail/what tools would I news to do this?
Click to expand...
Click to collapse
This is done from Clockwork Recovery. You can either run ROM Manager and choose "Reboot to recovery" or power the phone down then power back up while holding volume down. There will be a backup menu (nandroid). Make a backup (it saves on your SD card).
kr00kd said:
3. Flash ClockworkMod Recovery 3.x 3. WIPE
???
Click to expand...
Click to collapse
Search the forum. Sorry, I'm running a ROM that doesn't require recovery 3.x. Once you find the recovery image you need to flash it via adb or directly from a Terminal Emulator app on the phone. Usually flash recovery <your_recovery_img> or via adb in fastboot mode fastboot flash recovery <your_recovery_img> You can also perform a full (SYSTEM) wipe in recovery mode.
kr00kd said:
4. Install the ROM
???
Click to expand...
Click to collapse
DL the ROM, place the zip on your SD card. Reboot into recovery (should be there already after doing a wipe in step 3) and pick "Install zip from SD card". Scroll to your ROM's zip, select it, confirm, watch the magic happen.
kr00kd said:
5. Optionally install the Google Addon
Why wouul one want to do this and what would the benefits bbe? How would you go about it as well?
Click to expand...
Click to collapse
I don't use a CM ROM on this phone but did on my G1. Search the CM site or the forums here. CM ships "bare android", aka the AOSP (Android Open Source Project). Things Google adds (Gmail, Calendar, Navigate, etc) can not ship with CM due to copyright. You can, however, download and re-install them (since they came with your phone anyhow).
I suggest you read things thoroughly and treat everything like you will brick your shiny new toy before ever attempting it. Make sure you're willing to spend $450 retail on a new phone if you screw up. The first time through any of this is NOT for the faint of heart, and you cannot be overly cautious.
You'll probably get a lot of flames of "OMG DONT DO ANYTHING YOU DIDNT SEARCH AND READ", but good luck. Just seriously, be sure to read everything at least three times before doing it. It gets easier once you've been doing it for a few years, but the first trip....It's a deep rabbit hole
I'm no longer providing support for this thread due to time constrains with school, thank you for your support and it been nice sharing this method with you all. I may be gone but this method has still been reported as working, but it is possible that the next updates pushed to your phone might break the rooting and this method might not work anymore. But there is no harm in trying, at most you get an error in recovery saying file is invalid.
This method works on the released ICS rom from Germany and I would expect it to work for the rest of the ICS roms due for release..
This method does not increase the binary counter or causes a yellow exclamation mark
Update :
Due to rising numbers of phone being bricked based on rumors and stuff, I strongly suggest NOT trying to use any nandroid backup or restore on this CWM and it is best we keep CWM out of our devices to do major I/O stuff. So far I have never seen anyone bricked their devices on this small rooting/unrooting process but JUST DO NOT MAKE BACKUPS OR RESTORES!
Rooting
Download the Files first and put in your EXTERNAL SD
Reboot to stock recovery. - Shutdown your device completely, press and hold Vol Up + Power button + Home, releasing the power buttons once you see the Samsung GALAXY Note N7000 screen but continue to hold the Vol Up and Power buttons still until you enter recovery
Choose apply update from external storage. - Touch the screen as if you are using the phone to choose the options.
Choose CWM.zip and wait until CWM recovery appear.
( From this point on, the volume rockers and power buttons do not work! It is now a Touch interface like how you use the phone normally )
Choose install zip from external SD
Choose and Install SU-Busybox-Installer.zip
Reboot
You are done and now your device is Rooted
Unroot
Download this File first and put in your EXTERNAL SD
Reboot to recovery.- Shutdown your device completely, press and hold Vol Up + Power button + Home, releasing the power buttons once you see the Samsung GALAXY Note N7000 screen but continue to hold the Vol Up and Power buttons still until you enter recovery
Choose apply update from external storage.- Touch the screen as if you are using the phone to choose the options
Choose CWM.zip and wait until CWM recovery appear.
( From this point on, the volume rockers and power buttons do not work! It is now a Touch interface like how you use the phone normally )
Choose install zip from External SD
Choose and Install SU-Uninstaller-Signed.zip
Reboot
You are done and now your device is Unrooted
Partial Root
Alright i managed to obtain partial root myself and a fix for the Partial root is quite simple. You can install SuperSU by Chainfire and update the root. would fix the Partial root. Once you install this.. DO NOT USE the Superuser app and DO NOT uninstall the SuperUser app. Use SuperSU from now.
SuperSU - https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
MOD Edit: cwm.zip removed from the attachments, read Entropy512's post.
Thanks, but does this install CWM as well? id like to know so that I can go straight to flashing roms from it
are you sure this works ? can anyone confirm ?
nightfox11 said:
are you sure this works ? can anyone confirm ?
Click to expand...
Click to collapse
Works perfectly. Just rooted stock ICS.
Got a brand new Note in the box here.....
Trying to get things straight. Seems like I have two options now for rooted official ICS.
1. This method. Update official ICS Via PC odin (no binary counter, ect) and then follow above instructions.
2. Root stock gb via old method (not sure what that is yet) and then use the mobile odin proceedures w/ new ICS CF kernel?
Is the end result gonna be the same?
Bonus question for noob: what is binary counter and red triangle/exclamation point?
Sent from my SPH-D700 using xda premium
kvanlier said:
Works perfectly. Just rooted stock ICS.
Click to expand...
Click to collapse
thanks man!
Did you just copy this thread?
Oh well. No harm done I guess. Of course it works. It's a method for all android phones. Temporary cwm so you can copy busybox to /system.
Yeah it looks like it, but since it actually works i can't see why that would be a bad thing. But i would give the original author credits in the first post; that is if you copied it.
akenis said:
Got a brand new Note in the box here.....
Trying to get things straight. Seems like I have two options now for rooted official ICS.
1. This method. Update official ICS Via PC odin (no binary counter, ect) and then follow above instructions.
2. Root stock gb via old method (not sure what that is yet) and then use the mobile odin proceedures w/ new ICS CF kernel?
Is the end result gonna be the same?
Bonus question for noob: what is binary counter and red triangle/exclamation point?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Yes you will end up with the same result if you take either one of the 2 ways to root
Binary counter is a Samsung measurement of how many times you flashed custom firmwares using PC Odin, and the yellow (not red ) triangle is just a logo to further show that you indeed flashed custom firmware
However, the binary counter will not increase (and therefore no yellow triangle will appear) if you:
1. Flash stock firmware with PC Odin
2. Flash using Mobile Odin app by ChainfireXDA
3. Flash using CWM recovery
I got binary counted to 1 with yellow triangle after flashing ics stock from alba.can i use this method to erase counter and triangle?
Sent from my GT-N7000 using Tapatalk 2
So this gives cwm too looks easy
Sent from my GT-N7000 using Tapatalk 2
Drat?
I didn't have GB root because my previous version had root, but I $%*^ screwed
up and let KIES update it to 2.3.6 and I've got too much work to screw around with back flashing wiping etc.
I went ahead and let kies update to ics, now, my question, will this method work, or will I still have to go though all the other to get it to work.
I see it works on stock ICS, but is that after kies, or after you update via pc odin?
victorator said:
Did you just copy this thread?
Oh well. No harm done I guess. Of course it works. It's a method for all android phones. Temporary cwm so you can copy busybox to /system.
Click to expand...
Click to collapse
LordManhattan said:
Yeah it looks like it, but since it actually works i can't see why that would be a bad thing. But i would give the original author credits in the first post; that is if you copied it.
Click to expand...
Click to collapse
Not many ways to have a drastic difference from the method but hey it works well.
p51d007 said:
I didn't have GB root because my previous version had root, but I $%*^ screwed
up and let KIES update it to 2.3.6 and I've got too much work to screw around with back flashing wiping etc.
I went ahead and let kies update to ics, now, my question, will this method work, or will I still have to go though all the other to get it to work.
I see it works on stock ICS, but is that after kies, or after you update via pc odin?
Click to expand...
Click to collapse
This method works as long as you are on Stock ICS.. Can't really go wrong really.
so i did and have root and root works..
now my question is....
given that we get temp CWM..can i use the temp CWM to flash radios?
AND so if i want to flash LP6 radio via CWM will the steps be.
load Stock recovery
flash CWM.zip in stock recovery
load CWM
flash lp6 radio
will that work?
=============================
After no one answered i took the plunge...
Yes
so can confirm that the above procedure will work
PS: Am amazed how this is not in the sticky
Can anyone tell me any issues with using the CWM offered in this thread??? as in any issues with flashing other roms?? etc??
I fail to see?
The only issue is that CWM is not permanent but u can easily re-enable it by flashing it again...
again..dont understand why ppl are not paying attention to this thread as is great!
how come i only got partial root? i cannot paste into system
deathst said:
This method works as long as you are on Stock ICS.. Can't really go wrong really.
Click to expand...
Click to collapse
You are right, finally got my root back ICS, after the 2.3.6 update, been a while, now I have to remember how to use the freeze program, LBE security etc...all over again LOL. THANKS!
elijahtan said:
how come i only got partial root? i cannot paste into system
Click to expand...
Click to collapse
Try rooting again.. Are you sure your file manager app was given permission? Cause this thing is practically fool proof.
nandihno said:
so i did and have root and root works..
now my question is....
given that we get temp CWM..can i use the temp CWM to flash radios?
AND so if i want to flash LP6 radio via CWM will the steps be.
load Stock recovery
flash CWM.zip in stock recovery
load CWM
flash lp6 radio
will that work?
=============================
After no one answered i took the plunge...
Yes
so can confirm that the above procedure will work
PS: Am amazed how this is not in the sticky
Can anyone tell me any issues with using the CWM offered in this thread??? as in any issues with flashing other roms?? etc??
I fail to see?
The only issue is that CWM is not permanent but u can easily re-enable it by flashing it again...
again..dont understand why ppl are not paying attention to this thread as is great!
Click to expand...
Click to collapse
Glad it works for you Yes I wonder why is not many people taking notice.. :S
...and i thought I was screwed
THANKS MAN. works perfect. much faster than having to redownload the odex vrs
Worked perfectly thanks !
Sent from my HTC One X using xda premium
hmmm.... didn't work for me. CWM looks for update.zip so i renamed it as such. installed and rebooted to CWMR, no touch menu. same old blue colored menu. install su-binary, stuck at unmounting /system = not rooted.
Hi, I used the paid version of ClockWorkMod Recovery to backup, then download the 'Cyclonic Rom'. Well, it rebooted to a 'Cyclonic Rom' startup screen (animated lettering) - but that's it. I'm wary to unplug the battery if it's actually flashing, but this has been going on for 20 minutes or more. Can I pull the battery and see what happens? How long does a new ROM take to install, this is my first one. Thanks.
BTW: These CAPTHCA's are getting tough! This will be the 4th try!
fixed it
I unplugged the battery and did a factory reset/format in ClockWorkMod. I rebooted and all seems well so far.
20 minutes is a looong time for Cyclonic to boot. Is it still working ok? As far as CW goes, I only use Rom Manager to downlod what I want/need. When it comes to flashing I wipe everything manually and flash from recovery. I don't trust the app. But thats me.
Sent from my PG06100 using xda premium
+1 to that. I always use the same Method for Flashing Roms ( The one linked in my Sig ) . Clear everything Manually. I try to never deviate from that. Reason being, after Flashing literally hundreds of times I've found it to be the most reliable way to Flash a Rom. Meaning the least amount of possibilities for issues later on down the road .
alarmpro said:
Hi, I used the paid version of ClockWorkMod Recovery to backup, then download the 'Cyclonic Rom'. Well, it rebooted to a 'Cyclonic Rom' startup screen (animated lettering) - but that's it. I'm wary to unplug the battery if it's actually flashing, but this has been going on for 20 minutes or more. Can I pull the battery and see what happens? How long does a new ROM take to install, this is my first one. Thanks.
BTW: These CAPTHCA's are getting tough! This will be the 4th try!
Click to expand...
Click to collapse
Flash newsense.
And don't forget to wipe dalvik.
I have been searching (as in using the 'search' function) for a solution or answer to this, but couldn't find anything. This seemed to be the best thread to dig up instead of starting a new one.
Within Clockworkmod, whenever I try to go into recovery (either trying to 'reboot into recovery' or installing a ROM from SD card), it always throws me into Android System Recovery 3e instead of CWM recovery. Of course the stock recovery doesn't recognize my downloaded ROM.
I've also noticed that trying to update a ROM in HBOOT via a new PG06IMG.zip file on SD root is not working, except to wipe all my system and apps data, and then returning me back to rooted 2.2. HBOOT seems to read the new zip file fine, but when I reboot nothing has changed.
I've read wiki and lots of other stuff, but I can't seem to find an answer except that MAYBE that I need a new kernel first??? Okay, let the flaming begin.
jdjohn said:
I have been searching (as in using the 'search' function) for a solution or answer to this, but couldn't find anything. This seemed to be the best thread to dig up instead of starting a new one.
Within Clockworkmod, whenever I try to go into recovery (either trying to 'reboot into recovery' or installing a ROM from SD card), it always throws me into Android System Recovery 3e instead of CWM recovery. Of course the stock recovery doesn't recognize my downloaded ROM.
I've also noticed that trying to update a ROM in HBOOT via a new PG06IMG.zip file on SD root is not working, except to wipe all my system and apps data, and then returning me back to rooted 2.2. HBOOT seems to read the new zip file fine, but when I reboot nothing has changed.
I've read wiki and lots of other stuff, but I can't seem to find an answer except that MAYBE that I need a new kernel first??? Okay, let the flaming begin.
Click to expand...
Click to collapse
You need to flash recovery first, it is the first option in ROM Manager. You can't update a ROM with PG06IMG.zip, nor can you do it in the bootloader. Flash the recovery, wipe everything (data, cache, dalvik cache, system, sd-ext) then flash a ROM.
Did you get this sorted?
bilgerryan said:
You need to flash recovery first, it is the first option in ROM Manager. You can't update a ROM with PG06IMG.zip, nor can you do it in the bootloader. Flash the recovery, wipe everything (data, cache, dalvik cache, system, sd-ext) then flash a ROM.
Click to expand...
Click to collapse
Chad The Pathfinder said:
Did you get this sorted?
Click to expand...
Click to collapse
No, still having trouble. I have flashed ClockworkMod Recovery (version 5.0.2.0) in the ROM Manager app, but when I 'reboot into recovery' within the app, it goes to the Android System Recovery. I'm also confused about the 'apply sdcard:update.zip' option in ASR...seems like that would update something if the file was set up properly.
I guess I need to search for a tutorial on how ASR and HBOOT work. Sorry to bother you guys with the basics.
Try this onehttp://forum.xda-developers.com/showthread.php?t=1663531
bilgerryan said:
Try this onehttp://forum.xda-developers.com/showthread.php?t=1663531
Click to expand...
Click to collapse
Will check it out, thanks! I'm leaving town today, so not sure if I will be able to experiment before I go, but I will not give up!
The only thing I use Rom Manager for is to get the recovery. The way I go into recovery is to turn my shift completely off (do a battery pull to make sure its completely off) then hold the volume down and power buttons at the same time until the bootloader screen comes on. (While there see if it says S-off near the top) then using the volume buttons highlight the recovery option and push the power button. Then when you're there use the volume buttons to navigate through the various fields and hit enter to select. I hope this is helpful to you. Good luck!
Edit: by the way, when you first get to the bootloader screen, it will automaticly do a check showing a few green lines. Thats ok. Just wait until its finnished then go into recovery the way I stated.
jdjohn said:
Will check it out, thanks! I'm leaving town today, so not sure if I will be able to experiment before I go, but I will not give up!
Click to expand...
Click to collapse
How did you root? It seems as if you have a locked bootloader and/or S-ON if the custom recovery is not taking
Sent from my PG06100 using xda premium
CNexus said:
How did you root? It seems as if you have a locked bootloader and/or S-ON if the custom recovery is not taking
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
From bootloader screen:
Speedy XE Eng S-OFF
Hboot-0.93.2011 (PG0610000)
Radio-1.08.01.0111
eMMC-boot
Nov 15 2010, 13:16:46
I haven't tried Dread's CW-Enhanced yet. I just don't understand why the standard CWM recovery from ROM Manager doesn't work. I'm probably missing something obvious.
jdjohn said:
From bootloader screen:
Speedy XE Eng S-OFF
Hboot-0.93.2011 (PG0610000)
Radio-1.08.01.0111
eMMC-boot
Nov 15 2010, 13:16:46
I haven't tried Dread's CW-Enhanced yet. I just don't understand why the standard CWM recovery from ROM Manager doesn't work. I'm probably missing something obvious.
Click to expand...
Click to collapse
Just flash Dread's in bootloader, make sure it is named PG06IMG.zip (that is a zero) and place on the root of your SD and go back into the bootloader and hit update when it tells you to.
bilgerryan said:
Just flash Dread's in bootloader, make sure it is named PG06IMG.zip (that is a zero) and place on the root of your SD and go back into the bootloader and hit update when it tells you to.
Click to expand...
Click to collapse
Was thinking that myself. Will have to wait til I get back, though...headed out of town. Thanks guys!
jdjohn said:
From bootloader screen:
Speedy XE Eng S-OFF
Hboot-0.93.2011 (PG0610000)
Radio-1.08.01.0111
eMMC-boot
Nov 15 2010, 13:16:46
I haven't tried Dread's CW-Enhanced yet. I just don't understand why the standard CWM recovery from ROM Manager doesn't work. I'm probably missing something obvious.
Click to expand...
Click to collapse
Hmm, never mind then, it seemed as if your bootloader was still locked if the recovery wouldnt flash
bilgerryan said:
Just flash Dread's in bootloader, make sure it is named PG06IMG.zip (that is a zero) and place on the root of your SD and go back into the bootloader and hit update when it tells you to.
Click to expand...
Click to collapse
Yeah, just do what bilgerryan said (make sure that you download the one that says "flash through bootloader" or something along those lines)
Before flashing, download some md5sum tool and make sure it matches the one given on there
Sent from my PG06100 using xda premium
Finally got back to this and was able to install and use Dread's CW-Enhanced. So far I have only flashed the Speedy Rooted OTA 2.77.651.8 (bascially 2.3.4 rooted). GB had some features I was wanting, but missing, after rooting back to Froyo.
But before continuing on to other ROMs, I was wondering how you guys handle restoring basic apps and data each time you flash a new ROM. Or, do you only use extra play phones for new ROMs and not your daily user? It would seem that every time you flash, you need to restore SuperUser, Titanium, ROM Manager (ClockworkMod, then probably Dread's enhanced image file), Terminal Emulator, etc. And of course contacts and messaging history and other stuff like that.
So far, after flashing a ROM, I usually download Titanium (or MyBackup) and restore apps and data from backups before continuing. Do you just keep certain APK files on your SD card and install from ADB instead of re-downloading from Google Play Store each time?
I flash ROMs on my dd. Usually when I falsh a new ROM (not a nandroid) I fresh install my apps through the play store. Especially if switching between GB, ICS and JB! Some apps work well if carried over by tb but not all. You'll just have to experiment to see what works with your shift and what doesn't.
Also, the recovery only ever needs to be flashed once
What I used to do is backup my current rom with all my data and settings and then wipe + flash a new rom. If i liked it, then I would move my full box of apps and data to the new rom, but restoring data can go wonky so I always made a backup before doing that too. If i didnt like it, I would either restore my original backup for a bit or keep flashing new roms until I either found one I liked or got tired and restored my backup lol