I've been trying to understand all the steps necessary to replace the OEM ROM in my HTC Amaze 4G phone, but I can only find a disjointed set of pieces about the various steps and not one overarching document that covers all the stages of custom ROM flashing. A lot of the docs are aimed at the "insiders" of the Android developer community and few to people like me who would just like to try something better than what that ICS update did to my phone.
Having dabbled at one time with Linux from version .98 to 2.6 and being software developer most of my working life, I figure this should be easy for me. Yet, I find the documentation frustrating. I only imagine what it must be for others with less computer experience than me.
Since Android is based on Linux, I don't understand the big fuss about rooting. In Linux having the rooting privilege simply meant having a root password. Why is Android so much more complicated than that? Also, loading a new Linux kernel used to be a fairly simple process if one used compiled modules. The installation script pretty much took care of it. Android totally obscures this process and the disjointed documentation doesn't seem to help much. A lot of it assumes certain knowledge by the reader as if he/she was also an "insider" in that circle.
On my part I would like to so the following steps documented:
1.) How to save user installed content and the factory ROM image before wiping it out so it could be eventually restored if needed.
2.) How to prepare the phone for installing a new ROM
3.) What new and stable ROM images will work with given phone and how to obtain them and in what form? Zip, rar, or what?
4.) In what SD Card directory or in USB-connected PC directory the new ROM should be.
5.) How the flashing process would look like? Expected phases and length?
6.) Do I need to lock the new ROM's root just as the factory ROM was? How would I do that?
7.) Any special issues when booting the new ROM for the first time?
8.) How would I restore the original factory ROM saved in step 1?
Some of you might think I ask too much from guys who do the dev work as a hobby but I always thought that if one does something, might as well do it right, regardless of pay.
Well, that's my 2 cents worth for the day.
Howdy. I'll try to answer some of the questions you asked.
I would also recommend talking with @ravike14 who can easily guide you through the back up and routing and s-off process. It's not that difficult really. The most bizarre thing for me was sticking a piece of wire into a hole in the back of the phone to short out a process to achieve s-off.
With the right recovery image installed, it won't matter where you place the Rom.zip. which may be named just about anything. But it will always be a zip file.
The important one is the PH85img.zip must be placed in the root of your external sdcard. That file is loaded when you boot into the bootloader. And is for updating firmware.
Once you have root, and have made a nandroid backup, flashing is easy.
If you download viper, it is vipera1.7.2.1.zip. you can have it anywhere on you internal or external sdcard.
If you use 4ext recovery, you can select install and it will take you to a directory that you can browse to the place where the Rom, whatever name it is, is stored.
Click the Rom zip file and you will be guided thru the install process, if it has an aroma installer, or it will just install otherwise.
Then reboot and go thru the set up as if it was a brand new phone.
If you don't do the s-off thing, 4ext offers a smart flash option. If you aren't s-off you can't just flash a Rom if it contains a kernel. So smart flash will be required.
There are a few guides in the dev section and the general section on how most of this process works.
Again, talk with ravike and he'll be glad to help. Plus the more people we can keep here and happy, the longer we will be creating roms and fun stuff to play with.
Regards,
Chevy
Sent from my HTC_Amaze_4G using xda app-developers app
Is there a good documentation for all ROM flash steps?
Thanks, Cowboy, for the helpful reply, though I don't see any HELP button to push that the end of your post refers to.
I think at this point I'd like to figure out on my own how to install a custom ROM, though I must say that your S-OFF reference is one of the things that confuses me because the HTC dev site itself spells out that it is not necessary to change S-On to S-Off. Go, figure ...
Also, I think I like what I've read about the Revolution ROM, so that's the one I'd like to install if that is working with T-Mo branded Amaze 4G phones, though mine is no longer locked to T-Mo.
Your welcome!
NWsoccerfan said:
Thanks, Cowboy, for the helpful reply, though I don't see any HELP button to push that the end of your post refers to.
I think at this point I'd like to figure out on my own how to install a custom ROM, though I must say that your S-OFF reference is one of the things that confuses me because the HTC dev site itself spells out that it is not necessary to change S-On to S-Off. Go, figure ...
Also, I think I like what I've read about the Revolution ROM, so that's the one I'd like to install if that is working with T-Mo branded Amaze 4G phones, though mine is no longer locked to T-Mo.
Click to expand...
Click to collapse
If you're using the web to look at xda, there is a thanks button on the lower left side of the screen before the very end of the post line.
If you're using the XDA app, you have to tap on my post, and it should have a thanks selection in the options that come up.
A few more suggestions.
1.) How to save user installed content and the factory ROM image before wiping it out so it could be eventually restored if needed.
A) one you are rooted you should be able to back up all of your user data through a nandroid which is available in TWRP or 4EXT recoveries. This will back up everything to be able to restore exactly like it was before you change roms.
(NRG is my ICS preference, and Afnan has a good modified stock rom. ARHD (revolution) is also a good one without too many frills.
2.) How to prepare the phone for installing a new ROM
B) again, Root - s-off (really a good idea and not too hard to do) - dev unlock - and Super CID
3.) What new and stable ROM images will work with given phone and how to obtain them and in what form? Zip, rar, or what?
C) any roms listed in the dev section in the Amaze forum works. And, they should all be Zip fles. You can restore somone elses nandroid back up, but not adviseable.
4.) In what SD Card directory or in USB-connected PC directory the new ROM should be.
D) anywhere (except the PH85IMG.zip MUST be on the root of your EXTERNAL sdcard)
5.) How the flashing process would look like? Expected phases and length?
E) There are two types of rom flashes, standard and Aroma (thanks @amarullz)
1) Standard just does it's thing and when it's done, it returns you to the recovery menu to reboot.
2) Aroma is a highly configurable installation (preferred for selections of different kernels and adding or removing apps, keyboards, cpu freq's and much more) after it's done, most often it can reboot directly from the installer. ARHD has this type of installer, also NRG roms, and mine!
6.) Do I need to lock the new ROM's root just as the factory ROM was? How would I do that?
F) all of the "Custom" rom's (even thought some may be stock) should be rooted. A rooted rom containd the busybox and super user bianaries and apps (IE chanfireSU or SuperSU)
7.) Any special issues when booting the new ROM for the first time?
G) You shouldn't have any issues when booting a new rom for the first time. Some do require a little bit of behind the scenes set up time. Most users see just the boot animation reach the end, or it may seem like it's not doing anything, but it's doing an unbelievable amount of background processing, dexopting, and some comminucation with the carrier for data and validation set up. Some may take five to ten minutes to complete depending on the amount of apps and goodies that are in the rom.
H) if you see the HTC logo for an extended amount of time, more than five minutes, and you dont see the boot animation (which varies by rom) then you are stuck in a preload loop. This happens when you flash a carrier specific rom without being "Super CID", or you may not have flashed the kernel (if you are S-Off this won't be a problem) because you didn't select smartflash from the recovery settings.
** I had issues trying to install ARHD at first because there is a firmware update, a requirement to be Super CID (probably the easiest of things to do), and some roms specify that you should be using TWRP recovery instead of 4EXT, or vise versa.
8.) How would I restore the original factory ROM saved in step 1?
I) nandroid restore There is also a rooted stock rom based off of the latest OTA ICS Update. It is just like the rom that comes preloaded, or updated to on stock non-rooted phones. If you go that route, flash the "Stock ICS" rooted rom and do an advanced nandroid restore and only restore your data. That will (should) get you back to where you started from but keeping root, S-Off, Dev unlock, and Super CID.
I rewrote some of what I noted befor so maybe other's can benifit from this knowledge. And I wanted to expand on a few items. All good questions!
There's a lot of things that happen in the background that people need to see sometime (pull a logcat) to see the crazy lines of code flying by on a terminal screen.
If more poeple took the time to understand all of this it would reduce the amount of errors while flashing and poeple would be more happy.
And in doing so I think people will learn more about what they are doing, and the more you do it, the better you get at doing it.
Enjoy!
Chevy
chevycowboyusa said:
If you're using the web to look at xda, there is a thanks button on the lower left side of the screen before the very end of the post line.
If you're using the XDA app, you have to tap on my post, and it should have a thanks selection in the options that come up.
Click to expand...
Click to collapse
I use the web for this and the only thing I see on the lower left side is a DONATE button. That's what you mean?
chevycowboyusa said:
A few more suggestions.
1.) How to save user installed content and the factory ROM image before wiping it out so it could be eventually restored if needed.
A) one you are rooted you should be able to back up all of your user data through a nandroid which is available in TWRP or 4EXT recoveries. This will back up everything to be able to restore exactly like it was before you change roms.
(NRG is my ICS preference, and Afnan has a good modified stock rom. ARHD (revolution) is also a good one without too many frills.
2.) How to prepare the phone for installing a new ROM
B) again, Root - s-off (really a good idea and not too hard to do) - dev unlock - and Super CID
Click to expand...
Click to collapse
Can I still use my phone after it is rooted but before the new ROM is installed? How would the phone behavior change on a rooted phone?
You did not comment on why the htcdev site recommends against the S-Off as not being necessary for installing a custom ROM.
chevycowboyusa said:
3.) What new and stable ROM images will work with given phone and how to obtain them and in what form? Zip, rar, or what?
C) any roms listed in the dev section in the Amaze forum works. And, they should all be Zip fles. You can restore somone elses nandroid back up, but not adviseable.
Click to expand...
Click to collapse
OK, I've got that. Does this Nandroid backup the entire image of the phone's content sector-by-sector, or as individual files? To the external SD card or to the PC connected by USB cable? BTW, why are all flashing procedures requiring loading of the HTC USB drivers when such drivers must be on the phone already? Otherwise we could not link the phone to PC in the first place.
chevycowboyusa said:
4.) In what SD Card directory or in USB-connected PC directory the new ROM should be.
D) anywhere (except the PH85IMG.zip MUST be on the root of your EXTERNAL sdcard)
5.) How the flashing process would look like? Expected phases and length?
E) There are two types of rom flashes, standard and Aroma (thanks @amarullz)
1) Standard just does it's thing and when it's done, it returns you to the recovery menu to reboot.
2) Aroma is a highly configurable installation (preferred for selections of different kernels and adding or removing apps, keyboards, cpu freq's and much more) after it's done, most often it can reboot directly from the installer. ARHD has this type of installer, also NRG roms, and mine!
Click to expand...
Click to collapse
Aroma? That doesn't smell too good to me.
chevycowboyusa said:
6.) Do I need to lock the new ROM's root just as the factory ROM was? How would I do that?
F) all of the "Custom" rom's (even thought some may be stock) should be rooted. A rooted rom containd the busybox and super user bianaries and apps (IE chanfireSU or SuperSU)
Click to expand...
Click to collapse
Oh, so this might answer my earlier question about how a rooted phone might behave. Essentially a user might not even know the difference, right? So, I could also do this process in two stages: First just root the factory ROM and use the phone that way till I am ready to actually flash the new ROM in the second stage, right?
chevycowboyusa said:
7.) Any special issues when booting the new ROM for the first time?
G) You shouldn't have any issues when booting a new rom for the first time. Some do require a little bit of behind the scenes set up time. Most users see just the boot animation reach the end, or it may seem like it's not doing anything, but it's doing an unbelievable amount of background processing, dexopting, and some comminucation with the carrier for data and validation set up. Some may take five to ten minutes to complete depending on the amount of apps and goodies that are in the rom.
H) if you see the HTC logo for an extended amount of time, more than five minutes, and you dont see the boot animation (which varies by rom) then you are stuck in a preload loop. This happens when you flash a carrier specific rom without being "Super CID", or you may not have flashed the kernel (if you are S-Off this won't be a problem) because you didn't select smartflash from the recovery settings.
** I had issues trying to install ARHD at first because there is a firmware update, a requirement to be Super CID (probably the easiest of things to do), and some roms specify that you should be using TWRP recovery instead of 4EXT, or vise versa.
Click to expand...
Click to collapse
I've got this.
chevycowboyusa said:
8.) How would I restore the original factory ROM saved in step 1?
I) nandroid restore There is also a rooted stock rom based off of the latest OTA ICS Update. It is just like the rom that comes preloaded, or updated to on stock non-rooted phones. If you go that route, flash the "Stock ICS" rooted rom and do an advanced nandroid restore and only restore your data. That will (should) get you back to where you started from but keeping root, S-Off, Dev unlock, and Super CID.
I rewrote some of what I noted befor so maybe other's can benifit from this knowledge. And I wanted to expand on a few items. All good questions!
There's a lot of things that happen in the background that people need to see sometime (pull a logcat) to see the crazy lines of code flying by on a terminal screen.
If more poeple took the time to understand all of this it would reduce the amount of errors while flashing and poeple would be more happy.
And in doing so I think people will learn more about what they are doing, and the more you do it, the better you get at doing it.
Enjoy!
Chevy
Click to expand...
Click to collapse
Thanks. I like your attitude about this.
When you get time stop by
XDA University.
I learned tons here its a great place to start and much better than trying to Google everything
http://forum.xda-developers.com/general/xda-university
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
been busy
NWsoccerfan said:
I use the web for this and the only thing I see on the lower left side is a DONATE button. That's what you mean?
Can I still use my phone after it is rooted but before the new ROM is installed? How would the phone behavior change on a rooted phone?
You did not comment on why the htcdev site recommends against the S-Off as not being necessary for installing a custom ROM.
OK, I've got that. Does this Nandroid backup the entire image of the phone's content sector-by-sector, or as individual files? To the external SD card or to the PC connected by USB cable? BTW, why are all flashing procedures requiring loading of the HTC USB drivers when such drivers must be on the phone already? Otherwise we could not link the phone to PC in the first place.
Aroma? That doesn't smell too good to me.
Oh, so this might answer my earlier question about how a rooted phone might behave. Essentially a user might not even know the difference, right? So, I could also do this process in two stages: First just root the factory ROM and use the phone that way till I am ready to actually flash the new ROM in the second stage, right?
I've got this.
Thanks. I like your attitude about this.
Click to expand...
Click to collapse
you're welcome! I wish everyone would try to learn this
and the university is also very helpfull as freakboy noted above,
I've been busy working at bringing the comunity the next greatest romz!
Related
★★★ NOOB GUIDE :: Root :: Odin :: Files :: Guides ★★★
PLEASE READ THIS FIRST POST IN IT'S ENTIRITY!!
As of July 2011, I am no longer updating this guide.
Please feel free to check here for updates (if any are made).
STEP ONE – RETURN TO STOCK JFD - USING ODIN
FOLLOW STEPS 2 - 4 :: THIS IS A GUIDE TO GO BACK TO JFD.
IT HAS ALL OF THE FILES NEEDED
I encourage you to use HashTab to verify the MD5 (verify it is a good download). These are large files – if it is NOT a good download you could really cause some issues. It takes 10 seconds – do it.
Once you are done, come back and proceed to ROOT.
GREAT, I AM ON JFD - HOW DO I ROOT?
You are likely still connected to your PC and booted up to the T-Mobile jingle. Great, drop the notification bar down and mount your phone...
There are two options here. Choose which is best for you, before you start.
ROOT ONLY METHOD:
A – This is an update.zip (633KB) that roots your phone only. You can then install Rom Manager from the Market to flash CWR (Clockwork Recovery) and install custom ROMs.
INSTALL CLOCKWORK RECOVERY AND FLASH A ROM THAT WILL GIVE ROOT ACCESS (MY PREFERRED METHOD):
B – use the other update.zip (1.7MB) and this will flash CWR for you – allowing you to immediately flash a custom ROM.. I do this because it's faster.
1.
A: Download this update.zip file to root your phone. You plan to install Rom Manager to flash CWR and a new ROM later.
B: Download this update.zip file to flash CWR... you will need to flash a custom ROM for Root. I prefer this method.
NOW DOWNLOAD THE ROM YOU PLAN TO FLASH
2.
Copy the update.zip (and the ROM) to the INTERNAL SD (not the external SD Card). sdcard/
3.
Unplug the USB (assuming you are still connected after using ODIN)...
Hold down volume up + volume down + Power for about 9 seconds.
If you prefer, you can power off your phone, then hold in all 3 buttons to boot into recovery, I don't see the point in waiting for the phone to power off.
This will get you to a recovery menu (blue/purple text) after some yellow text.
4.
In this (the stock recovery menu) select 'Reinstall Packages'
Use volume to navigate + power to select.
5.
It will cycle a bit, you will see that yellow text again, then it will return to the stock recovery. Select Reinstall packages again.
You are now in CWR (clockwork recovery).
You can either reboot, flash your new ROM or make a backup now...
I COVER HOW TO FLASH ROMS LATER – JUST KEEP READIN BELOW
Yeah, it is that easy!! Read below for more information if needed.... but at this point you probably are done with what you came here for. I would encourage reading below for general knowledge and making sure you are doing things as easily as possible.
OKAY, I HAVE ROOT - NOW WHAT? BACKUP!!!
** Below are a list of several things I suggest backing up **
Titanium Backup – APPS
Download Titanium Backup from the Market and Open it. The Paid version is worth it's weight in gold... it does everything automagically. Buy it if you plan to flash a lot or have a lot of apps.
Click Menu > Batch
Click on "Run" by backup all user apps
Click on Run the batch operation
All your apps are now backed up.
Please note that if you backup/restore System Apps, you are asking for problems. I do not ever mess with system apps and do not encourage it - unless you plan to stay on the same build. If you do, be smart about it.
Clockwork Recovery / Nandroid Backup!
Reboot into CWR (both volume buttons held in) while booting until you see “Vibrant'
Once there, go to Backup and run that. Should take about 5 minutes, maybe more.
If all hell breaks loose, this is a snapshot of your phone at that point... it's important to do this before flashing a new ROM!
Backup your Alternate Launcher (if you use one)
If you use a home replacement like ADW or LauncherPro, you can backup your home screen settings/icons (widgets cannot be restored however).
Launcher Pro: Click Menu > Preferences... scroll down to the bottom and click on backup.
ADW EX: Menu > ADW SETTINGS > BACKUP.
Once you flash your ROM, you can now RESTORE your settings.
Rooted... Got a Backup... let the fun begin!!
WHAT ROM SHOULD I FLASH?!?!?!
This question is asked a LOT. The most often answer? Read the development section and pick the one that seems to fit you... if that does not work, backup your apps and try another. This is a very liquid process. Things change, phones are different, people tastes are different. Try and try again.
I will point out that if you have backed up your apps, moving from rom to rom is NOT a hard process. You can ODIN to JFD and have a new ROM booting in 10 minutes. Easy.
OKAY, HOW DO I FLASH A ROM?
* I typically root/flash immediately after using ODIN. This is assuming you did not.
1 – Download the ROM to your PC. ROMs are typically 140-190+MB’s. So yeah, it’s a big file.
2 – Check the MD5 if so inclined (Using Hastab – linked above).
3 – Mount phone to PC
4 – Drag ROM to root of internal memory (the large SD card where folders like the DCIM folder appears).
Should appear as: sdcard/TheRomName.zip
You DO NOT need to rename the ROM
5 – Unmount and reboot into clockwork recovery (using Rom Manager, or by pressing in both volume buttons and power… holding… and releasing power once the Vibrant logo is up).
6 – OPTIONAL (in CWR): Do a Factory Wipe, Wipe Data, & Wipe Dalvik Cache (advanced menu)
7 – Go to “install zip from sd card”, select zip from sd... choose your ROM and flash it (volume keys move up/down, power selects)
8 – OPTIONAL (I do not do this): After flashing, choose to wipe data and dalvik cache
Do NOT factory wipe again
9 – Reboot phone
10 – Your new ROM is going to boot. Initial boot will take a LONG time (10 minutes maybe).
You may hear a lady's voice (Linda) converting your file system – this is normal if your ROM has the Voodoo lagfix. No worries.
Do not touch the phone for 5-10 minutes after it has booted... Seriously, Do Nothing!. . This helps clear any possible bugs. Once you've waited, reboot phone by holding in power for about 9 seconds (rough guess)... And then....
Click to expand...
Click to collapse
RESTORE!!
After the phone boots and you waited, go to Market, Sign-in, Approve terms, Re-install Titanium Backup. I strongly suggest the Paid version (MUCH better)
Restore all Missing Apps+Data.
Again, I really do little with System apps.. too many issues, but the green ones may be fine to restore.
Restore anything else you have. (ie launcher)
Reboot again.
I dont use Facebook, but I've been told you need to remove it and add it sometimes?
WHAT ABOUT IF THERE IS AN UPDATE TO THE ROM?
Let's assume you flashed Axura 2.2.6 and then a week later 2.2.7 is released... well, how do you update?
Easy, just download it, place it on your internal memory, backup using titanium backup, reboot to recovery, make a nandroid backup, flash the new rom and reboot.
Now... if you are going to try a new rom (not an update to your existing ROM), you may want to go back to stock first, then flash the custom rom.
Why go back to stock? Some say that if you are on one rom and go to another rom there may be ghosts left behind from the previous rom. Using ODIN to get back to stock and then flashing a ROM ensures this is not going to happen.
RECONDITION YOUR BATTERY
AFTER FLASHING A ROM IF BAD BATTERY IS NOTED
Use phone til it dies on it's own, completely dead.
Charge phone completely, plus 30 minutes longer.
Unplug phone from charger
Reconnect, you'll notice it's not full, charge till it is again.
This is bump charging and NOT something you want to do often, a few times is okay, in my opinion. You could skip the bump charge if you like.
Phone remains plugged in.
Boot into recovery (volumes + power)
Advanced > wipe battery stats, reboot.
Use phone til it's literally about to shut off (or does)
Charge till full +
Use phone like normal
Everyone has a method, that's how I feel it works best.
WORSE CASE SCENARIO - YOU BRICK YOUR PHONE - WHAT TO DO?
Almost always a phone is not actually bricked. If you can get into download mode or see ANYTHING you can ODIN back to stock and your phone is good to go.
If you are NOT able to get into download mode, please read the thread below to make a Jig!
TRY A NEW KERNEL/MODEM
New modems can increase signal and data speeds. Here is an incredible list of each thanks to XDA user scrizz.
Please pay notice to the version of android you are running (2.1, 2.2, etc.) CLICK HERE FOR A FULL LIST OF VIBRANT MODEMS
Kernels can overclock your processor, undervolt for battery, or remain stock but optimize things so the phone is snappier. These are always changing and there are always new builds coming out, so PLEASE review and make sure what you installing. These should install just like a rom... download, move to internal memory (sdcard/ ) and flash in clockwork recovery like you would a rom (install zip from sd).
NEED THE STOCK APPS BACK?
1 - Use the app BLOATER by Roman, it is found here!
THIS IS FOR THE MINORITY OF PEOPLE WHO CAN NOT GET INTO DOWNLOAD MODE OR STOCK RECOVERY. This used to be much more detailed, but is no longer an issue. Links saved here, just in case.
http://forum.xda-developers.com/showpost.php?p=9663212&postcount=53
http://forum.xda-developers.com/showthread.php?t=804305]
I think that is an excellent idea. As a noob myself, its easy to get confused. Maybe a noobs guide to odin, or how to back your phone up to your pc. One can never have to much info.
Sent from my SGH-T959 using XDA App
Do something on ODIN. I made a nandroid backup of my stock root but I have no idea what to do with it should something go wrong.
Great idea, I think most will appreciate something like this.
I think you may want to make sure you include a section about the various lagfixes. How to install, the importance of uninstalling and of course their definitions. I think it would help clear up the forums a bit.
I am actually NOT going to mention lag fixes at all. They are not for noobs and really do not benefit the user THAT much. If someone wants to add using lag-fixes, go for it... but it's not something I am going to recommend for a noob. With froyo especially, I consider these pointless (unless you want to see a high quadrant score).
Good point, maybe you'll want to mention them as evil and not meant for the weak at heart or anyone not willing to have a nice paperweight.
How about adding something for those new users who purchased a used phone. Maybe teach then what to look for before they flash anything.
Alright, not even close to being done...but I am at a stopping point right now. Will try and pick it back up later today. Please let me know what you guys want added.
ColorNapkin said:
Do something on ODIN. I made a nandroid backup of my stock root but I have no idea what to do with it should something go wrong.
Click to expand...
Click to collapse
I agree, an "Odin for noobs" would be awesome.
Sent from my SGH-T959 using XDA App
Great tut, but stuff like this will cause more "noobs" even with the simplicity you will get questions regarding how to do something. Lol whats your next step? Record yourself doing it, I.would die if you do.
Sent from my SGH-T959 using Tapatalk
Guide added to WIKI
So added this link to Wiki for the Vibrant. http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#Good_Links
There is already a Odin guide on there under the [GUIDE] FIX AND RESCUE YOUR VIBRICK!
iwillkillyou said:
Great tut, but stuff like this will cause more "noobs" even with the simplicity you will get questions regarding how to do something. Lol whats your next step? Record yourself doing it, I.would die if you do.
Click to expand...
Click to collapse
Actually... I probably was going to ODIN my phone (video 1), root it (video 2) flash clockwork (video 3) and flash a rom (video 4).....
I was cautious to accept the request to make an even simpler tutorial... frankly I spent a lot of time on the sticky and if that was not enough, well... perhaps you should not be rooting. That said, by doing this it will really clean up the sticky when it's done AND I need more space since I am running out, again.
Not many noobs asking for much... perhaps this effort is not needed?
If you want you can also link to my guide on how to fix Vibricks if you get a lot of questions about that as well x)
http://forum.xda-developers.com/showthread.php?p=9370249
If you are going to create the be-all "brick" thread, could you at least explain that they are NOT BRICKED????
I think that this is great thread. I did ryans oclf to root my phone, because it seemed to be the easiest way to root. I think I will undo and start over using this guide. Before There always seems to be some question popping up where I find myself wondering what was meant so I would never take the plunge into flashing a rom.This seems to be more straight forward for me. I personally would love to see the video walk through which would make everything crystal clear. Thanks for this OP
Sent from my SGH-T959 using XDA App
s15274n said:
If you are going to create the be-all "brick" thread, could you at least explain that they are NOT BRICKED????
Click to expand...
Click to collapse
There, I semi-fixed it for now, I'll add more details later
Thanks so much for your wonderful work. I am a nubie and I am sure it will be a great deal of help to me. Is there any way you could include what fastboot is and how to use it? And when to use it? Once again thank you for your kind and generous efforts.
I went ahead and flashed axura 2.0.5 without any problems ( thanks to the vid on axura download page), but now I'm not sure about getting the Black froyo theme. It says to download zip and flash through clockwork recovery. Is that the same steps as flashing the rom? sorry in advance if this is a stupid question, but unless it is crystal clear I am very hesitant. thanks again
roly17 said:
I went ahead and flashed axura 2.0.5 without any problems ( thanks to the vid on axura download page), but now I'm not sure about getting the Black froyo theme. It says to download zip and flash through clockwork recovery. Is that the same steps as flashing the rom? sorry in advance if this is a stupid question, but unless it is crystal clear I am very hesitant. thanks again
Click to expand...
Click to collapse
I think you download the zip to your internal sd card, boot into clockwork recovery and install the zip from there.
As for a ODIN guide for n00bs, not sure how much easier you can get:
http://www.youtube.com/watch?v=AnY7P14JSWQ
Thats what i think too, but not sure. Do i click on install rom from sd card to get to the theme zip file? I tried this and it brought me into clockwork recovery(?), but the install of the zip was not obvious to me. So I just rebooted and nothing happened. I know I did something wrong , just not sure what.
Ok, I've already searched the forums, both in the Evo3D section and outside, I've also have within the last week tried many different sense roms, all of which had the exact same problem: my camera does NOT work.
The closest thing to working was mike1986's Android Revolution HD (so far). The camera app boots into the window that ask to choose between Done or run the Demo Video. The Demo Video sends ye off to the internet browser. Hitting Done goes straight to my problem.
The application opens into a black screen. Sometimes the backlight is on (noticed this is a 'feature' of the newer roms that has came out/updated within the last month). That's it. After hitting home to exit the application, I have noticed I get either dimmer horizontal strips of the screen or the screen has a ghost of the lighter portions of the screen image that slowly moves to the left. After a few seconds of this strangeness, the screen reverts back to normal. A few times I got the impression that the screen's dual layers having synchronization problems.
I'm about ready to give up and go back to the stock rom, maybe I'll even try the 'cleaned' versions before trying the rooted shooter stockers. If all else fails, I'll even try to use the full OEM installer and return the phone back to stock, if this is the only option left to get a working camera. I'd prefer to use a custom rom that allows undervolting/overclocking and has the fat trimmed off, but if I have to, I'll go back to stock rooted. ...now that I think of it, I started to have problems with the camera right after I applied the HTCDev Root method. And, yes I DID follow the instructions to the letter.
This is quite frustrating as I've have as yet to find a rom that has a working camera! I've already tried the following roms:
Shooter-Rewind-3D-RLS2.1+RLS3
WTSB_Evo3d_1.91
CleanROM_2.7
CleanROM_DE_1.2
Chogardjr3D-2.3.4-Stock
Chogardjr3D-Blue-v1.3
STEAL25_inbREDedROM_2.1clock
viperROM_RC1.3
viperROM_RC2_Rebuild_Test28
Android_Revolution_HD-Evo3D_CDMA_1.1.1 (current)
I haven't tried but already downloaded:
Gerbil-6-shooter_v.2.2.4
freEVO+3D+2.1
WTSB Hydro e3d 2.3 (want to try this one, but keep having problems downloading, the server keeps on downloading a 35kb index.html instead of the rom itself)
If the above roms fails, then I going to try reloading the rooted stock rom
shooter_2.08.651.2_cleaned_v0.4.2
Else one of these two...
Shooter_2.08.651.2_deodexed_rooted
Shooter_2.08.651.2_odexed_rooted
If all these fails, sigh, I gonna start over again with the full oem install...
PG85IMG_2.08.651.2.zip
And see if the camera still broken. If so, then gonna apply all OTA updates FIRST before applying the HTCDev root method again. This is the only thing I did not do before. If this doesn't work, I dunno what else to do then.
Any suggestions, rom-wise or camera-wise? I've been reading around and found a thread in the Amaze section that suggested that the camera problem might be kernel-level. Think this may also apply to the e3d?
I've been doing sleepless nights for the past 5 days already trying roms after roms and apk after apks. I'm about reaching the end of my thread (and patience) and figured it's time to ask the pros here on xda.
Thanks in advance...
-Lance (Lanaka)
Reserved for Fixed Post.
I forgot to upload my hardware/software specs. I'm out of time as I have to go to work, so I'll edit it onto this post during a slow period at work.
K here's my hardware/software specs:
---Hardware:
------Hardware Version: .. 0002
------Processor: ............ 1.2 GHz Qualcomm MSM8660 Dual-Core
------Memory: ............... 1GB
------Display: ................ 4.3 inch QHD resolution
------Main Camera: ........ 5Mpx*2
------Front Camera: ....... 1.3Mpx
---Software:
------Android Version: ..... 2.3.4
------HTC Sense version: 3.0
------Software number: .. Android Revolution HD 1.1.1 by mike1986
------Kernel version: ...... 2.6.35.14RCMIX-ACS-EVO3D-CR-V9-g98e7362-dirty
------------------------- [email protected] #6
------------------------- SMP PREEMPT Mon Oct 24 13:13:49 CDT 2011
------Baseband version: . 0.97.10.0808
------Build number: ........ 2.08.651.2 CL130920 release-keys
------Browser version: .... WebKit/533.1
------PRI Version: .......... 1.24_003
------PRL Version: .......... 10602
Bootloader:
------SHOOTER XC SHIP S-0N RL
------HBOOT-1.50.0000
------eMMC-boot
------Aug 7 2011,10:21:40
---Recovery:
------Team Win Recovery Project (twrp) v1.0.3
------Based on Android System Recovery <2e>
Any other information you need, lemme know and where/how get it.
Mahalo Much
-Lan
Infected eternity ROM works...
Sent from my 3vo
http://infectedrom.com/showthread.php/561-ROM-Eternity-2.3.4?p=10369
Sent from my 3vo
nearly ALL the ROMs you posted, nay, all of them, work - if they didn't there would be a hellstorm in those threads. My guess is it has to do with how you're flashing the ROM. Since you have hboot 1.5, customized kernels (which contain camera stuffs) do not fully apply in a normal flash. You need to first fastboot usb INTO recovery and THEN flash the ROM. That should work. Also, update TWRP to 1.1.1. Of course you'll need to do a wipe as well. Hope this works for you.
You might also want to try one of the many superwipes.
User error. Camera works on roms. Maybe ur phone is broken
Sent from my PG86100 using XDA App
I'd go with what il Duce said. You have to flash the kernel seperately. If you do decide to go back to stock you can always add su and also remove what you don't want.
Sent from my PG86100 using XDA App
fsu311 said:
Infected eternity ROM works...
Click to expand...
Click to collapse
Ok, I'll give it a try next after the ones I've already downloaded. I'm a methodical type of guy (don't like leaving thing left undone).
il Duce said:
nearly ALL the ROMs you posted, nay, all of them, work - if they didn't there would be a hellstorm in those threads. My guess is it has to do with how you're flashing the ROM. Since you have hboot 1.5, customized kernels (which contain camera stuffs) do not fully apply in a normal flash. You need to first fastboot usb INTO recovery and THEN flash the ROM. That should work. Also, update TWRP to 1.1.1. Of course you'll need to do a wipe as well. Hope this works for you.
Click to expand...
Click to collapse
That's what I'm figuring. I start reading the original set of posts, then randomly check out a few posts in the middle, and then read the last 10%. The roms i've picked mostly had either minor issues caused by misflashing or other user errors. A few actually said had an issue or two but nothing that'd stop me from giving the rom a try.
Yup, that's the MO I've been using as instructed in the following thread:
http://forum.xda-developers.com/showthread.php?t=1239821
I'll go thru the step-by-step process I used and you can nitpick where I went wrong,
I've placed a copy of adb.exe, AdbWinApi.dll, fastboot.exe and TWRP's recovery.img into folder c:\adb\
A little tip here, as I play with windoze XP a lot, a trick I used to eliminate the need to cd so much with cmd.exe. I did this after the 3rd ROM!
I place a shortcut link to cmd.exe into this same folder with the above files and exes. Next I open the Properties window for this shortcut, I made the following changes:
Start In: c:\adb
Comment: Starts cmd.exe in adb folder.
What happen is that cmd will open its window with the c-prompt already IN the same directory as my android files. Also, when i mouse-over the shortcut icon, it will popup a message reminding me that this link starts cmd.exe in adb folder.
Then I do the following:
I connect the phone to the laptop using the usb cable, set the phone to disk drive mode. Once Windows recognizes the volume and mounts it, I type the following:
c:\adb>adb reboot bootloader
After the e3d reboots into hboot, I then type the following:
c:\adb>fastboot boot recovery.img
downloading 'boot.img'... OKAY [ 1.250s]
booting... OKAY [ 0.000s]
finished. total time: 1.250s
Once TWRP loads, I then switch to the phone (WITHOUT disconnecting the phone from the laptop). Here on, I use the keys on the phone to navigate to the necessary functions. The proceedure I used mirrors what Steel25 suggested in the following thread:
http://forum.xda-developers.com/showthread.php?t=1269610
I initially thought it was an overkill, but figured probably wouldnt hurt to be safe than sorry.
If the installed rom is something I liked, I nand it first...
I then enter the Wipe Menu proceed to hitting each of the following:
Wipe Cache
Wipe Dalvik Cache
Wipe Everything (Data Factory Reset)
Wipe Battery Stats
Then I go to Advanced/Format Menu and hit each of the following:
Format SYSTEM (/system)
Format DATA (/data)
Format CACHE (/cache)
Format SD-EXT (/sd-ext)
Then I go back to top menu and enter Install Zip Menu, and first I hit:
Wipe Cache and Dalvik Cache
Then I enable:
Reboot After Successful Flash
THEN I:
Choose Zip To Flash
(Navigate to where the rom or app zip is located and select it.) Here I take a break and let TWRP does it thingy and check back on the phone in 5 minutes or so.
After recovery reboots the phone back into system, I let the phone sit on the lockscreen for 10 minutes to let the rom complete it's init process. Then I skip thru the entire initial setup prompts (altho I enter NO for Tell HTC). I reboot phone back into system, let it sit for another 5 minutes on the lockscreen before I hit the Android Market app to trigger the process of linking the phone to my google account. I then let my account sync. Once my new email icon pops up on the notification bar, I check out the camera. By the time I've hit the 3rd rom, I've had read about the camera problem possibly being a kernel level issue, I've since then added this step....
Menu/Settings/About Phone/Software information/More
Here I took note on whether the Kernel version info has changed as well. (And for the most part, yes, the kernel information DOES change with each rom).
K, now ye can start thrashing me...
-Lan
Drewmungus said:
You might also want to try one of the many superwipes.
Click to expand...
Click to collapse
I'll try that, altho I've never used it before. Even when I had my e4g, I never heard of this one until I started my current research on the e3d. Any particular one you'd (or anyone else'd) recommend?
Sigh, lotta work rooting and flashing the 1.50 e3d, compared to the good ol' e4g! >8p HTC!
Mahalo Much!
-Lan
cajones42 said:
Maybe ur phone is broken
Click to expand...
Click to collapse
Gods! I certainly HOPE NOT! It'd be a real b!atch if this proves to be the case.
Seriously, tho. I'm thinking it'd probably not be the case as I had the phone and was playing with it stock and unrooted for nearly a week and during the whole time, the phone's camera worked with nary a problem. That's why as a check value, I'm going to restore the phone back to stock unrooted state AFTER I try the last 4 roms I still have en-queued. This doesn't include the cleaned/rooted stocker, the full/rooted stocker nor the full OEM stocker.
-Lan
unCoRrUpTeD said:
I'd go with what il Duce said. You have to flash the kernel seperately. If you do decide to go back to stock you can always add su and also remove what you don't want.
Click to expand...
Click to collapse
Ok, I'll try that next. Altho, I gonna have to read up on how to prepare the kernel for flashing separately. Am I correct in guessing that I probably could get away with making a copy of the zip file and deleting everything in it except for boot.img, then adb boot into recovery and set the flag for check sign off before flashing the custom zip I just made? If that's not correct, mind pointing me to the apropos thread? (...or tell me what I need to do for separate flashing?)
If all else doesn't work, that's what I intend with the stocker roms. SU, TI, RE. Then time for me to research on where what and how to root out all the bloat meself. I'll worry about that later cuz I no need do that IF i can get a pre-made rom and kernel to take root in me e3d!
Mahalo Much!
-Lan
You DON'T have to flash the kernel seperatly using the boot.img method with HBoot 1.50. As long as you access recovery from fastboot you can flash everything normally & the kernel will stick. Just sayin'
SketchyStunts said:
You DON'T have to flash the kernel seperatly using the boot.img method with HBoot 1.50. As long as you access recovery from fastboot you can flash everything normally & the kernel will stick. Just sayin'
Click to expand...
Click to collapse
except he's already doing that and running into problems...
@OP - man you are wordy lol. Just a simple FYI, when you're phone is running and you hook up to usb with the intention of running adb, DO NOT turn on disk drive, leave it as charge only. Also, the way to flash the kernel as a stand alone is pull the "boot.img" from the ROM zip, put in your path, and then "fastboot flash boot boot.img". Also, there's an app made by dev "joeykrim" called "flash image gui" that allows you to flash kernels (boot.img) from your OS and is known to work with hboot 1.5.
il Duce said:
except he's already doing that and running into problems...
@OP - man you are wordy lol. Just a simple FYI, when you're phone is running and you hook up to usb with the intention of running adb, DO NOT turn on disk drive, leave it as charge only. Also, the way to flash the kernel as a stand alone is pull the "boot.img" from the ROM zip, put in your path, and then "fastboot flash boot boot.img". Also, there's an app made by dev "joeykrim" called "flash image gui" that allows you to flash kernels (boot.img) from your OS and is known to work with hboot 1.5.
Click to expand...
Click to collapse
Ah, didn't know that, mebbe that's why I'm having problems. I'll try reinstall one of the earlier ROM and see if there's any difference. If that doesn't fly, I'll try the kernel separately. I went with hard drive mode cuz I got actual confirmation the device was loaded. Charge only, didn't get any indication that the pc seen the e3d, sigh, noticed the sense and adb interface is rather ...crude.
Heh, wordy, that's what you get when you have an English major for a mother and an English/Japanese Translation Specialist (aka Cultural Attache in the US Army) for a grandfather...
I'll give joeykrim's flash_gui a try too. Just downloaded it. Cross fingers for luck. (roll eyes at 1.50)
Thanks dude, if I could, I'd hit yer thanks button again for good measure.
EDIT: clicked the button again...
Update: Back to work on problem...
Been a while guys. Unfortunately, work becons (or more accurately, intruded). Had to deal with a bunch of sht from my job. Things gone to the dumps there. Well, enuff of that.
In meantime, with my phone being activated and in use, I tried to tether (teeether, hehe) my e4g to my e3d and noticed I'm also having wifi issues. What rang a bell is when I noticed my wifi tether issues disappeared after I turned off 3G. It's like, heeeeey, didn't I read something like this in xda??? After doing some researching (on xda, of course ) I've learned that this is also a kernel issue, most often because the new kernel was not properly flashed in conjunction to having the correct matched kernel modules (wifi, CAMERA, 3g/4g, etc.) installed as well. On reading these, I went 'hmmm...' Looks like all of these issues others and I that have been experiencing are all kernel/module misflashes (no thanks to hboot 1.50). Where I think I hit pay dirt is when I found a xda thread that actually explains in depth Flash Image GUI, which was also mentioned earlier in THIS thread (thanks, il Duce).
So, I have downloaded the apk, installed it. Downloaded a new ROM (Olympus Trinity XE Version IV) STRAIGHT to phone...
Oh, just remembered. I've noticed another possible cause of problems. I've originally downloaded the various files from xda and then either push it to phone or more often just enable hardrive mode and drag/dropped it into the phones sdcard directly. Normally, I check the md5 hash on download, but yesterday, I ALSO checked the md5 hash again after moving it to the phone. Meaning, I downloaded ROM to pc, then checked md5 hash, all good. Copied ROM to phone and then checked md5 hash again. NOT good. Somehow, it changed during the copy process. What prompted me to check was I also downloaded Flash Image GUI to pc and copied it to phone and then had phone try install it. It failed to "parse" file correctly, which tells me that the file may have been corrupted. I downloaded Flash Image directly to phone and tried again, and success! Suspicious now, I checked the md5 hash of all three copies of the apk. The laptop downloaded and the phone downloaded copies matched the source's md5, while the COPIED version did NOT match! Whaaa Daaaa FFF(bleep!)!!! I then checked the two copies of the ROM (pc downloaded and phone copied) and they DON'T match!
Sigh. I'm in a area that has poor 3G connection, while ironically, my laptop's 4G was good.
So, I bit the bullet and endured the nearly hour long download of the ROM directly to phone and double checked the hash (which matched the pc downloaded copy, the source didn't provide a hash). THEN I used the Flash Image GUI app to pull the kernel and modules and pop it into phone. Immediately rebooted phone into recovery. Well, tried. Wished Flash Image GUI gave the option to reboot directly into recovery or bootloader, like those 4-/5-/6-1 Reboot options offered in the various ROMs. Because it just simple did a reboot back into System.
I didn't want to take chance with problems with mismatched ROM/kernels (I was on Android Revolution 1.1.1 at the time), so I quickly turned to adb on my laptop and had it reboot phone into recovery.
Once in recovery, I immediately started doing my usual ROM change process. Wiped using every wipe option (except for sdcard) in TWRP (oh btw, I also updated it to 1.1.1 earlier) in both the standard wipe and advanced wipe menus. Once I did so, I then thought, hey where did Flash Image GUI dump the kernels into? Couldn't remember whether it was DATA or SYSTEM. But decided that with Flash Image GUI it's ain't no hassle to reflash the kernel again after the ROM is installed. Besides, read somewhere that some issues was resolved after reflashing the kernel again after the ROM, so wouldn't hurt to try anyway.
Will let ye know how it goes, TWRP is installing Trinity XE as I type this. Gonna continue the SOP by letting it sit for 7-10 minutes. Skip thru init setup. Reboot. Let sit for another 7-10 minutes. Relink my google account. Let first Sync finish. (Basically let it sit again for another 7 minutes). Reboot. Hit Market and download Flash Image GUI, and pay for it, it's well worth IT!!! Flash the ROM's kernel/modules again. Reboot. And hopefully it should be a-ok!
(cross fingers ...on both hands)!
-Lance
PS: Assuming it's fixed, I'm gonna edit the second post and reflag this thread as resolved. Will put what I did to get it fixed, including all necessary links and credits as expected. I know it's premature, but THANKS, I wouldn't have gotten even this far without you guys (and gals) on XDA!
PPS: Also chris.goodman's AnthraX Kernel thread was also quite informative. Mebbe I'll try a ROM that features AnthraX. Somehow, the thought of being over-clocked to ~1.52G sounds appealing!
First off let me start by saying I just rooted my EVO 3d. Yes I'm a noob to this whole thing! I have to say I'm hooked on this though very cool! I was successful with the root, I used the HTC method to root the phone.
I then installed TWRP.
I installed the Olympus Trinity XE rom.
Here is my question
I see that there is an update to this rom do I have to reinstall this whole ROM and and set my phone all up again or can I just update with the new version and keep all of the settings on my phone? example: when i installed the new ROM I had to set up my mail and all applications again. Maybe there is a step I'm missing and I may not be providing enough info like I said I'm a noob right now so all help would be appriciated.
Thanks
Most likely you just need to flash the new rom over your current without wiping and starting over. Just be sure to backup first just in case. Usually the thread with the update will say whether you need to wipe or not.
Comcastrated
Direthreat said:
First off let me start by saying I just rooted my EVO 3d. Yes I'm a noob to this whole thing! I have to say I'm hooked on this though very cool! I was successful with the root, I used the HTC method to root the phone.
I then installed TWRP.
I installed the Olympus Trinity XE rom.
Here is my question
I see that there is an update to this rom do I have to reinstall this whole ROM and and set my phone all up again or can I just update with the new version and keep all of the settings on my phone? example: when i installed the new ROM I had to set up my mail and all applications again. Maybe there is a step I'm missing and I may not be providing enough info like I said I'm a noob right now so all help would be appriciated.
Thanks
Click to expand...
Click to collapse
Cetus Corr said:
Most likely you just need to flash the new rom over your current without wiping and starting over. Just be sure to backup first just in case. Usually the thread with the update will say whether you need to wipe or not.
Comcastrated
Click to expand...
Click to collapse
Yea, it really all depends on the ROM dev and the changes they've made between ROMs. They should let you know whether or not you'll need to wipe "data" partition which is where all your settings for mail and all other applciations are stored.
If you don't have to wipe data, usually you don't between updates of the same ROM, then all your settings will stay in tact which makes the updating process much easier.
Many times, when switching between ROMs, you'll need to wipe the data partition and re-do all the settings.
Personally, I usually flash w/o wiping and if I have issues, I might go back and wipe or run fix_permissions script. But these are definitely more advanced steps so I wouldn't recommend the process.
In all cases though, always make a nandroid as it can save much time and effort! Good luck!
Thanks for the assistance.
This is what I'm working with.
Attention!!
Instructions to flash Trinity
For Users that have used Revolutionary to S-Off
ALL USERS
Wipe Data and Cache
Wipe Dalvik Cache
go into Mounts and Storage and Format System
Install Trinity
Sit back and allow it to finish
Once finished allow your Olympian to rest for 7 minutes
REBOOT
Allow it to rest for 7 minutes AGAIN
REBOOT
ENJOY!!!!
Resources to flash Trinity
For Users that have used the HTC Unlock Tool
Please go here and review Second Post for instructions
http://forum.xda-developers.com/show....php?t=1239821
Please go here for Flash Image GUI
http://forum.xda-developers.com/show...1192527&page=8
So my confusion come after the all user statement and it also does not refer to if you are already running the Rom and just looking for the updated parts.
Direthreat said:
Thanks for the assistance.
This is what I'm working with.
Attention!!
Instructions to flash Trinity
For Users that have used Revolutionary to S-Off
ALL USERS
Wipe Data and Cache
Wipe Dalvik Cache
go into Mounts and Storage and Format System
Install Trinity
Sit back and allow it to finish
Once finished allow your Olympian to rest for 7 minutes
REBOOT
Allow it to rest for 7 minutes AGAIN
REBOOT
ENJOY!!!!
Resources to flash Trinity
For Users that have used the HTC Unlock Tool
Please go here and review Second Post for instructions
http://forum.xda-developers.com/show....php?t=1239821
Please go here for Flash Image GUI
http://forum.xda-developers.com/show...1192527&page=8
So my confusion come after the all user statement and it also does not refer to if you are already running the Rom and just looking for the updated parts.
Click to expand...
Click to collapse
On a side note, the links quoted above don't work and for future reference you can attach a link back to the original post you're quoting...not a big deal. But after seeing my app, Flash Image GUI, mentioned, I was a little curious!
The steps look correct and follow the general pattern when loading all ROMs and most kernels. If you're currently using the ROM and you're only flashing an "updated" version of the ROM, then you shouldn't need to wipe /data, at minimum though I'd suggest wiping /data/dalvik-cache and /cache.
BUT, the ultimate answer lies with the ROM developer as only they know for sure, what files were changed and how they were changed. Best to post up the question in the specific ROM thread and I'm sure either the developer or somebody familar with their work will be able to provide a more specific suggestion!
Hope that helps!
Thanks Great feedback! Sorry about the links too. I purchased and used your tool last night and it seemed to update the kernel to AnthraX-CMDA-Sense-Stock v2.6.38.6 but it did not seem to update the ROM? In the developers post he refers to using your method to flash the ROM. I followed your instructions to the T and did it twice but it seems like it did not update the ROM. In addition I can't post to the thread yet because I'm new to XDA and need ten post before I can submit to that thread.
Direthreat said:
Thanks Great feedback! Sorry about the links too. I purchased and used your tool last night and it seemed to update the kernel to AnthraX-CMDA-Sense-Stock v2.6.38.6 but it did not seem to update the ROM? In the developers post he refers to using your method to flash the ROM. I followed your instructions to the T and did it twice but it seems like it did not update the ROM. In addition I can't post to the thread yet because I'm new to XDA and need ten post before I can submit to that thread.
Click to expand...
Click to collapse
My application, Flash Image GUI, only loads the kernel portion of the ROM. Due to limitations of the OS, not able to overwrite files which are currently in use the ROM/System portion of the ROM .zip file can't be loaded while currently using the OS.
The ROM .zip file needs to be flashed from the custom recovery in order to load the system portion of the ROM.
From your feedback it sounds as if you've only completed half of the process, loading the kernel. To complete the other half, you'll need to flash the exact same ROM file from the custom recovery.
Hopefully that makes sense! Appreciate the support!
joeykrim said:
My application, Flash Image GUI, only loads the kernel portion of the ROM. Due to limitations of the OS, not able to overwrite files which are currently in use the ROM/System portion of the ROM .zip file can't be loaded while currently using the OS.
The ROM .zip file needs to be flashed from the custom recovery in order to load the system portion of the ROM.
From your feedback it sounds as if you've only completed half of the process, loading the kernel. To complete the other half, you'll need to flash the exact same ROM file from the custom recovery.
Hopefully that makes sense! Appreciate the support!
Click to expand...
Click to collapse
By that you mean flash the whole rom again?
Sent From My Nocturnal 3Dimension
I did follow the complete process but it still did not update. Looking at going to another Rom.
Any suggestions on Kernel and Rom to use?
Let me start off by saying I have been reading these forums for a couple days and I am just getting more confused.
Currently I have root, S-On, and no other mods or ROMs. I am getting the popup notification to update literally every time I turn on the screen. I can select defer and set a date about a week in the future from whatever day it is, but the popup comes back within the hour. A few times it even began downloading on its own (while on 4G as well, ~100 mb of data used up every time).
All I would like to do is somehow get my phone to be as if I were complete stock and accepted the OTA, keep root, and not have to wipe any data (or be able to restore a full nandroid). I am getting very frustrated with everything and once I think I understand it, someone throws out something new to me.
If anyone is willing to take some time to help me with this I would gladly make a donation, either to them or another party of their choosing
Spaded21 said:
Let me start off by saying I have been reading these forums for a couple days and I am just getting more confused.
Currently I have root, S-On, and no other mods or ROMs. I am getting the popup notification to update literally every time I turn on the screen. I can select defer and set a date about a week in the future from whatever day it is, but the popup comes back within the hour. A few times it even began downloading on its own (while on 4G as well, ~100 mb of data used up every time).
All I would like to do is somehow get my phone to be as if I were complete stock and accepted the OTA, keep root, and not have to wipe any data (or be able to restore a full nandroid). I am getting very frustrated with everything and once I think I understand it, someone throws out something new to me.
If anyone is willing to take some time to help me with this I would gladly make a donation, either to them or another party of their choosing
Click to expand...
Click to collapse
You can simply flash a stock rom that has the update & flash the newer stock kernel that goes with it but you wont be able to update the radios. You wont lose any info this way unless something goes wrong.(always backup everything just in case something goes wrong).
As for backup, you will only be able to backup aps & data with titanium backup or some sort of program like that because If you do a nandroid backup and then restore after applying the update, you would be restoring your old rom basically over the new one and lose most update enhancements.
You should just follow the thread here http://forum.xda-developers.com/showthread.php?t=2155069 and go S-Off. I know you will have to restore everything because you will wipe your phone when you do this but its only gonna make things easier for you in the future.
Do a nan backup and save it in case you want to use it in the future and go back to what you had. Once you have S-Off, you can flash kernals, radios, & roms and put in any version you want.
Thanks for your response Jrocker,
So it looks like the best way to do this would be to backup my apps with Titanium, get S-off, install a stock ROM with the update, flash the kernel and radio, then restore from Titanium.
Step 1. Make nandroid
Step 2. Backup apps with Titanium, copy backup along with pics and video to PC
Step 3. Get S-off
Step 4. Flash Stock ROM - http://forum.xda-developers.com/showthread.php?t=2149095
Step 5. While still in recovery, flash stock kernel http://forum.xda-developers.com/showthread.php?t=2149951
Step 6. Flash stock radio http://forum.xda-developers.com/showthread.php?t=2155915
Step 7. Restore apps and pics.
Does that look correct? Do I have to worry about flashing a boot.img or modules(don't know what those are)?
Spaded21 said:
Thanks for your response Jrocker,
So it looks like the best way to do this would be to backup my apps with Titanium, get S-off, install a stock ROM with the update, flash the kernel and radio, then restore from Titanium.
Step 1. Make nandroid
Step 2. Backup apps with Titanium, copy backup along with pics and video to PC
Step 3. Get S-off
Step 4. Flash Stock ROM - http://forum.xda-developers.com/showthread.php?t=2149095
Step 5. While still in recovery, flash stock kernel http://forum.xda-developers.com/showthread.php?t=2149951
Step 6. Flash stock radio http://forum.xda-developers.com/showthread.php?t=2155915
Step 7. Restore apps and pics.
Does that look correct? Do I have to worry about flashing a boot.img or modules(don't know what those are)?
Click to expand...
Click to collapse
Have you unlocked the bootloader? (this step is usually done in connection with rooting the phone at the htcdev.com website). If you have an ulocked bootloader, then you can flash an alternate recovery (eithe cwr or twrp) and do a nandroid backup.
Then follow the steps to get s-off. Note: the step where you have your data wiped is unlocking the bootloader, not obtaining s-off. If you already have an alternate recovery, and root, then s-off generally will not wipe your phone. But do an nandroid backup in cwr or twrp just in case Although a nandroid won't backup pictures etc.
Once you have s-off, flash the stock (but rooted) rom you linked to in step 4. This step SHOULD flash the stock kernel if the .zip file was prepared properly. If you boot into the rom and have flickering or wifi issues, then you will need to flash the stock 2.04 kernel (in fastboot). You can also verify if the new kernel was installed when the rom is booted by looking at the Settings:About:Software Information:More (baseband, kernel etc). You should see there kernel version 3.4.10. The baseband (radio) should be 1.01.01.0110 once you have updated the radio (see the step below). The kernel file is the boot.img file you were asking about. The modules will already be built into the stock rom.
While in fastboot (not recovery) you can flash the updated radio files (that will make the baseband referred to above be 1.01.01.0110.
The time when you need to worry about flashing a kernel (boot.img) and modules is if you are s-on, or if you are s-off and the zip file was prepared as you were s-on. When you flash a "kernel", it consists of a boot.img file, along with some extraneous files (the module). When you are s-off, these can both be flashed together while in recovery. When you are s-on, the boot.img file must be flashed from fastboot (or else an alternate method using an app like Flash Image GUI). Because until recently, most DNA's were s-on, the kernel developers prepared their files for s-on devices, with instructions for s-on devices.
When you flash a rom that uses a different kernel than the one you are using, if the .zip file is prepared for a s-off device, then there are no additional steps necessary.
You may want to do a factory reset when you flash the updated 2.04 rom. I think it would be wise. As I said earlier, you shouldn't lose your /sdcard partition UNLESS you haven't already unlocked your bootloader. s-off doesn't reset your device.
Wow, all I can say is thank you so much! That was an awesome, detailed answer. It makes so much more sense when someone fully explains everything all at once, instead of me trying to piece everything together myself from various threads.
Yes my bootloader is unlocked. So you are saying once the bootloader is unlocked wiping data won't touch the SD card partition, just as if I had an actual SD card? When I rooted my Thunderbolt and did subsequent factory resets on that, it never touched the SD card. When I rooted my DNA it wiped everything. Either way I will always make backups and copy those to my PC.
I will be trying this later today and I will report back with the results. Seriously, thank you so much.
Spaded21 said:
Wow, all I can say is thank you so much! That was an awesome, detailed answer. It makes so much more sense when someone fully explains everything all at once, instead of me trying to piece everything together myself from various threads.
Yes my bootloader is unlocked. So you are saying once the bootloader is unlocked wiping data won't touch the SD card partition, just as if I had an actual SD card? When I rooted my Thunderbolt and did subsequent factory resets on that, it never touched the SD card. When I rooted my DNA it wiped everything. Either way I will always make backups and copy those to my PC.
I will be trying this later today and I will report back with the results. Seriously, thank you so much.
Click to expand...
Click to collapse
I was looking for this exact solution as well. This was before we had s-off. For a while my solution was to freeze a couple apps in TB so the OTA pop up would stop popping up. I think it was HTC DM 1.0.2219251543..... and HtcDm 1.0.221982913.... Looks the same but they are different.
I like stock but I eventually flashed ViperDNA. It looks like stock but you are able to customize the $h!!t out of it. Its an awesome ROM that I highly recommend. Although you might want to wait until he comes out with 1.2 (the new version with the latest firmware) becuase you have to wipe data. Data wiping isn't a big deal if you use TB.
Ether way you go - Stock ROM or ViperDNA - The recommended way to wipe your device is this way:
(I'm using TWRP but CR should be similar, might be in different menus)
Backup everything using TB
Backup Pics and other docs on internal SD card (JUST IN CASE)
Make Nandroid Backup in Recovery
Wipe Menu-> Wipe Dalvik Cache (some like to wipe 3 times others think its just a waste of time)
Wipe Menu-> Wipe Cache (Factory Reset wipes cache but I like to wipe cache anyway just for completeness )
Wipe Menu-> Factory Reset
Wipe Menu-> System
Don't Format Data and Don't wipe Internal Storage. You will loose SD card contents.
Once you install your ROMS, flash your kernals, flash radios...whatever you want to do...You can restore apps and data from TB
As always, follow the ROMS instructions on their page for more information.
Only Restore User Apps and Data
Never restore any system apps in RED. May not be compatible with new ROM
You can however restore system Data that is in Yellow or Green (DATA ONLY)
Thanks devilsaces
Once I get everything updated and get a good nadroid of the newest firmware with all my apps I will definitely give ViperDNA a shot. I tried a few custom ROMs on my Thunderbolt, and while they were great to customize, they weren't always stable. Like I said I use my phone for work all day so I really need something dependable, and so far stock hasn't let me down.
Thanks again everyone, a lot of great info in this thread. Hopefully this will be useful to others as well.
Spaded21 said:
Thanks devilsaces
Once I get everything updated and get a good nadroid of the newest firmware with all my apps I will definitely give ViperDNA a shot. I tried a few custom ROMs on my Thunderbolt, and while they were great to customize, they weren't always stable. Like I said I use my phone for work all day so I really need something dependable, and so far stock hasn't let me down.
Thanks again everyone, a lot of great info in this thread. Hopefully this will be useful to others as well.
Click to expand...
Click to collapse
Yeah, I had the same problem on the Thunderbolt, nothing stable. Viper however feels great. I would definitely freeze the HTC apps in Titanium Backup to get rid of the annoying pop ups. I noticed Viper has them uninstalled.
About to start, few more questions. The stock ROM I linked to (http://forum.xda-developers.com/showthread.php?t=2149095) says it doesn't have the new firmware, is that different from kernel or anything else? Do I need to flash that as well?
Spaded21 said:
About to start, few more questions. The stock ROM I linked to (http://forum.xda-developers.com/showthread.php?t=2149095) says it doesn't have the new firmware, is that different from kernel or anything else? Do I need to flash that as well?
Click to expand...
Click to collapse
I'm actually running that rom right now.
You don't need to flash the radio if you don't want. If you are happy with your cell reception, and battery life, as well as wifi, then you can stay on the original radio.
Or if you'd like to try the new radio, you can flash that (once you have s-off) with this thread: http://forum.xda-developers.com/showthread.php?p=38197525
I'm not sure if there is a radio flash prepared to go back to the original radio. Generally speaking, once to are s-off, you can change radios at will.
From what I understand, if you flash the rom you linked to, and the radio above, then you will have everything from the update, except the updated hboot. I haven't bothered changing my hboot. changing hboot won't affect the day to day operation of the phone, but it can change the fast boot commands that are available. Until I see a good reason, I am not going to worry about my hboot.
FYI: about changing radios, from what I understand, the radio file is the code that tells the phone how to communicate with the towers. It tells the phone how to adjust the power output of the radio according to the strength of signal from the cell. This can be very aggressive, leading to better signal, at the expense of battery life (increasing power output of the phone radio takes more power from the battery), or it can be conservative, with a little lower quality signal, but conserving battery life.
It seems that the engineers at the carriers are constantly tweaking the radio code to find a sweet spot between signal quality and battery life. Different carriers may tweak the radio for the same phone with a different priority. Sprint may prioritize signal, while verizon prioritizes battery. So each carrier may have a different radio file for phone that is in the same phone family. And then each carrier may have multiple radios. On the thunderbolt there were about 6 or 7 I think, but it is generally believed that newer radios work better than older ones.
Some people on xda will often experiment to see which radio file works best for them, depending on where they live and work.
I always try to be careful to only flash redid that others have reported to work with my device, rather than experimenting personally. I would think that you can brick your phone flashing the wrong radio file.
Sent from my HTC6435LVW using Tapatalk 2
Is that ROM deodexed? Or would I be better off using this one? http://forum.xda-developers.com/showthread.php?t=2080200
Spaded21 said:
About to start, few more questions. The stock ROM I linked to (http://forum.xda-developers.com/showthread.php?t=2149095) says it doesn't have the new firmware, is that different from kernel or anything else? Do I need to flash that as well?
Click to expand...
Click to collapse
Firmware is the Android system. The Droid DNA is on on 4.1.1 (Jelly Bean). That version has not changed in the new OTA update so I don't know why that ROM even mentioned it.
The Kernal is the interface that alows the software to access the hardware. A more detailed explanation can be found here: http://forum.xda-developers.com/wiki/index.php?title=ROM-VS-Kernel
HBOOT is 'kinda' like your BIOS in windows. It is the bootloader. It is the first thing that is loaded on your phone. This too I believe has not changed with the latest OTA update.
This is the change log for the 2.04.605.2 710RD update
Bluetooth connectivity and volume level for specific models have been improved
Enhanced reliability and stability of the Contacts List have been made
Enhanced Recent Apps functionality has been improved
Incoming messages display with the correct timestamp
Improvements to Hotspot connectivity have been made
Improvements to Audio Quality for wired headsets and earpieces have been made
Improvements to default browser for zooming capability have been made
User can load videos on HuluPlus
Wi-Fi Connectivity has been improved
As you can see it is mostly stuff related to your radio so the radio is the main part you would want. I personally just updated my radio and din't worry about anything else.
---------- Post added at 12:15 PM ---------- Previous post was at 11:56 AM ----------
Spaded21 said:
Is that ROM deodexed? Or would I be better off using this one? http://forum.xda-developers.com/showthread.php?t=2080200
Click to expand...
Click to collapse
I don't think it is deodexed otherwise it would tell you. I think deodexed is good if you want to theme.
I'm using the first one, which isn't deodexed. But I'm keeping my rom close to stock this week
Next week, when the Viper rom has been updated to 2.04, I'll be flashing that, and probably a theme.
You indicated that you aren't currently running any mods or themes. Unless you are looking to change, I would suggest you flash the first rom you linked, which is stock, except for the root capability being added to it.
The de-odexed rom you asked about will have been modified, deleting the .odex files so that the rom can further be customized by themes etc. When a phone boots a rom that is missing the .odex files, it will take longer to boot because it will essentially create the missing .odex files on the fly while booting. But when you are modding your rom, adding themes etc., existing .odex files get in the way, so that is why developers remove the .odex files, even though the rom will take longer to boot. Once the phone is booted, whether the rom was odexed or not becomes irrelevant.
For now, if you are looking to be on the latest radio and HTC rom, I suggest you get s-off, then flash the basic 2.04 rom (the one you linked to first), and the updated radios. Hopefully HTC will soon release the updated source files for the 2.04 kernel, and then we will have more customization.
If you are looking to customize now, I would get s-off, then flash the updated radios, but stay with a rom based on the original released rom and source (like Viper). The latest Viper rom (with updates to 1.1.3) has modifications so that you won't have to worry about getting bugged to update your ROM for 2.04. If you decided to go with Viper, it is a little confusing when viper is updating from 1.1 to 1.1.1 to 1.1.2 to 1.1.3, because it uses an over-the-air (OTA) update process similar to the stock OTA update. So you may see notices for updates - but the updates would be for Viper. Once you have gotten your phone s-off, you don't need to worry about updates causing problems.
Spaded21 said:
Is that ROM deodexed? Or would I be better off using this one? http://forum.xda-developers.com/showthread.php?t=2080200
Click to expand...
Click to collapse
Ok so I have done everything, S-off, deodexed stock ROM, 3.4.10 kernel (it flashed with the ROM), and updated radio. I'm able to boot up but I don't have wifi.
Edit: Flashed the boot.img from the zip and it's working now.
Spaded21 said:
Ok so I have done everything, S-off, deodexed stock ROM, 3.4.10 kernel (it flashed with the ROM), and updated radio. I'm able to boot up but I don't have wifi.
Edit: Flashed the boot.img from the zip and it's working now.
Click to expand...
Click to collapse
Congrats!
I think that rom you used wasn't set up properly to flash the boot.img from recovery, so that is why you had to do it manually. As time goes on (and there are more users with s-off), I think most new roms will be set up properly, so you shouldn't run into that again.
The whole process wasn't that hard, and using TiB made it really easy to get everything back.
So how do I go about removing bloatware now that I have S-Off and I am deodexed?
Although there are several ways to start removing bloatware, one of the easiest ways is to go into TiBu, and freeze apps. Make a nandroid backup first, and start slow.
Some apps have dependencies, you freeze one, and another might not work, like contacts and dialer.
After you have frozen an app, and are confident that it isn't necessary, you can delete it if you want.
Sent from my HTC6435LVW using Tapatalk 2
Spaded21 said:
Let me start off by saying I have been reading these forums for a couple days and I am just getting more confused.
Currently I have root, S-On, and no other mods or ROMs. I am getting the popup notification to update literally every time I turn on the screen. I can select defer and set a date about a week in the future from whatever day it is, but the popup comes back within the hour. A few times it even began downloading on its own (while on 4G as well, ~100 mb of data used up every time).
All I would like to do is somehow get my phone to be as if I were complete stock and accepted the OTA, keep root, and not have to wipe any data (or be able to restore a full nandroid). I am getting very frustrated with everything and once I think I understand it, someone throws out something new to me.
If anyone is willing to take some time to help me with this I would gladly make a donation, either to them or another party of their choosing
Click to expand...
Click to collapse
I would highly recommend using the OTA blocking zip to kill the update messages. I'm not very handy with posting zips yet but search the threads for the disable OTA. I am on the Viper DNA rom also but I put the OTA blocking on just in case. If I were on my PC instead of my phone I could have posted the zip file for you. I'm sure with each rom the developer has added a file to make sure the OTA is killed but you can never be too sure.
Easiest way to get 2.04 OTA for rooted DNA phones
Hat-tip .Torrented from our discussion here: http://forum.xda-developers.com/showthread.php?t=2152993&page=12
Get Facepalm S-Off: http://forum.xda-developers.com/showthread.php?t=2155069
Download stock recovery from: http://goo.im/devs/Flyhalf205/DNA/dlx_recovery_signed.img
Flash the stock recovery using:
fastboot flash recovery dlx_recovery_signed.img
Click to expand...
Click to collapse
Once you are on stock recovery, and assuming you're on stock kernel, it allows you to take the OTA update!
After you take the ota just flash the custom recovery of your choice again. CWM Touch is a good option: http://www.clockworkmod.com/rommanager
Flash the superuser-busybox.zip to root.
This gives you a completely clean "factory" upgrade to 2.04, without losing any of your data (YMMV - so pls always take a backup before you do this).
It worked for me - yippee!!!
Software number: 2.04.605.2 710RD
Kernel version: 3.4.10-ga02d2c6
Baseband version: 1.01.01.0110
Whole procedure took less than 15 minutes
zanyguy said:
Hat-tip .Torrented from our discussion here: http://forum.xda-developers.com/showthread.php?t=2152993&page=12
Get Facepalm S-Off: http://forum.xda-developers.com/showthread.php?t=2155069
Download stock recovery from: http://goo.im/devs/Flyhalf205/DNA/dlx_recovery_signed.img
Flash the stock recovery using:
Once you are on stock recovery, and assuming you're on stock kernel, it allows you to take the OTA update!
After you take the ota just flash the custom recovery of your choice again. CWM Touch is a good option: http://www.clockworkmod.com/rommanager
Flash the superuser-busybox.zip to root.
This gives you a completely clean "factory" up to 2.04, without losing any of your data (YMMV - so pls always take a backup before you do this).
It worked for me - yippee!!!
Software number: 2.04.605.2 710RD
Kernel version: 3.4.10-ga02d2c6
Baseband version: 1.01.01.0110
Whole procedure took less than 15 minutes
Click to expand...
Click to collapse
Thanks zanyguy for the procedure and process outline. I have a question regarding my current format and was wondering if going to a stock rooted version would work for me. Since every end user is different then there are different things they want of course. For me the process is very simple. I like a very lean system. I also like to try and achieve many things to look as close to AOSP as I can get and keep functionality. My current setup has the phone unlocked, rooted, s-off and running Viper 1.1.3. My radio is the OTA update radio of 1.01.01.0110 and my kernel is the same 3.4.10-ga02d2c6. What I wonder is this. Should I even bother trying to flash the stock Rom? Is there any benefits to doing so? And if I do give it a spin should I just restore the Viper DNA rom or re flash anew?
Thanks
Big problem with my I777 running stock Jellybean...
I deleted the wallpaper file from data\system\users\0 and now my phone will not boot. It powers on and gets to the lock screen, but won't allow me to slide to unlock. The phone isn't entirely unresponsive as the clock still updates every minute. But it won't do anything else.
I have my old wallpaper file handy on the computer, so I can surely copy it back to the phone. Question is: how?? I have USB debugging enabled so ADB is possible, but I have absolutely no idea how to use it. If I boot to system recovery the only option I get for ADB is sideload. I can execute ADB on my computer, it finds the device. But when I try to use the "push" command, ADB responds with "error: closed." I tried to use the "sideload" command (with a dummy file) just to see if ANY ADB command would work. "Sideload" works (the phone reports an error about the file being invalid), so I know the connection is fine.
Help appreciated, thanks. I'm stuck with a ****ty iPhone until this situation is resolved.
You're still on the stock kernel/recovery, so I'm not sure that you have any easy options. It is also relevant to know just how much information you want to recover.
File replacement:
Using desktop ODIN to flash a syiah kernel, then reboot to recovery:
You might then be able to adb-push the necessary item to /system, but this is a hack-approach to a problem better suited by a proper flash. <-- will retain all existing data & customization. Maybe worth a try, but I don't recommend it
Dirty-flash:
Using desktop ODIN to flash a syiah kernel, then reboot to recovery:
You will be able to flash a (custom) samsung-based firmware, which WILL overwrite /system, but will NOT overwrite your /data partition, likely allowing you to boot and properly back-up the stuff you want to keep, or even create a nandroid of the existing setup. <-- Will retain all existing data, will lose /system customisations. I have used this method.
Start-fresh:
Use desktop-Odin to flash the official firmware may be your only other option, which will retain everything in internal memory (photos, downloads, music, nandroid backups), but not messages, or any app data.
-Cyril
Mr. Barker said:
Big problem with my I777 running stock Jellybean...
I deleted the wallpaper file from data\system\users\0 and now my phone will not boot. It powers on and gets to the lock screen, but won't allow me to slide to unlock. The phone isn't entirely unresponsive as the clock still updates every minute. But it won't do anything else.
I have my old wallpaper file handy on the computer, so I can surely copy it back to the phone. Question is: how?? I have USB debugging enabled so ADB is possible, but I have absolutely no idea how to use it. If I boot to system recovery the only option I get for ADB is sideload. I can execute ADB on my computer, it finds the device. But when I try to use the "push" command, ADB responds with "error: closed." I tried to use the "sideload" command (with a dummy file) just to see if ANY ADB command would work. "Sideload" works (the phone reports an error about the file being invalid), so I know the connection is fine.
Help appreciated, thanks. I'm stuck with a ****ty iPhone until this situation is resolved.
Click to expand...
Click to collapse
cyril279 said:
You're still on the stock kernel/recovery, so I'm not sure that you have any easy options.
Click to expand...
Click to collapse
Well I do have CWM installed, but am curiously (and annoyingly) unable to boot to it now, for whatever reason. It boots to stock recovery instead, every time.
cyril279 said:
Using desktop ODIN to flash a syiah kernel, then reboot to recovery:
You might then be able to adb-push the necessary item to /system, but this is a hack-approach to a problem better suited by a proper flash. <-- maybe worth a try, but I don't recommend it
Click to expand...
Click to collapse
I think it's worth a try. I really would prefer to get my phone back working as it was, quickest way possible, because I've done a lot of heavy customization that would take many many hours to have to do over if I flash the official firmware again.
Could you please point me in the right direction of the syiah kernel, and proper instructions as to how to flash it? Would be much appreciated.
If it doesn't work out so hot, I'll try one of the other methods you mentioned. Thanks.
Mr. Barker said:
I think it's worth a try. I really would prefer to get my phone back working as it was, quickest way possible, because I've done a lot of heavy customization that would take many many hours to have to do over if I flash the official firmware again.
Could you please point me in the right direction of the syiah kernel, and proper instructions as to how to flash it? Would be much appreciated.
If it doesn't work out so hot, I'll try one of the other methods you mentioned. Thanks.
Click to expand...
Click to collapse
I would be glad to provide more detailed information, but I prefer to do so from a desktop computer, and I won't be near one for several days, so this may be a slow process unless one of our peers steps in to help.
In the meantime, you should gather:
-Odin 1.85 or 3.07
-A Siyah s2-v5.x or s2-v6.x .tar.md5 kernel (for the i777 or i9100)
The latter you can find at http://www.gokhanmoral.com
I will outline the process in a later post, explaining the purpose of each step.
Sure, I'm OK waiting a few days. I appreciate the help, I haven't done any flashing in quite some time and don't want to make a mistake, especially with all the important data that's at stake.
Thanks.
File Replacement Method
1) Use desktop Odin to flash Siyah kernel
-Installs a kernel that will allow you to perform a nandroid backup, and MAY allow you to adb push the missing file to the device.
-This WILL change the initial boot screen (can be corrected later, but does not affect the function of the firmware), and will notch the flash counter (simply doesn't matter).
2) Boot to recovery
3) Create nandroid backup
-If things go sideways, you have a snapshot of where you are. If you have to start from scratch, there are apps that can restore Apps, settings, and more, from a backup.
4) Adb push missing file to /data/path_file_belongs
5) Shell chmod XXX the missing file
-to correct file permissions; that 0.xml file has -rw------ on my device, which translates to 600 (I think)
6) Flash appropriate ajk kernel
-for stock jb, use "NoSwap" http://forum.xda-developers.com/showthread.php?t=2110542
-custom kernel that will boot stock rooted android.
7) Attempt Reboot into android
-If successful, reboot to recovery and perform another backup.
-If not successful, then we use a different method.
This is the trickier method of the three, but will retain all customization if it works. I have not tried it, and we're assuming that the missing file is actually the problem.
Please be sure that you are comfortable with all of the steps before attempting any of them. I will be able to provide step by step instructions, but not for several days.
Happy flashing,
-Cyril
Well, that was fun. Followed the instructions to a "t" and even learned some things. But, sadly, did not achieve the results I'd hoped for.
I was indeed able to push the wallpaper file over to data\system\users\0 and CHMOD it. But after flashing AJK "NoSwap" the phone shows the "Android is upgrading..." message, with "Starting apps." trying to process. But it doesn't. The little circle swirls a bit, then the screen goes black. The "Starting apps." message appears again, then the screen goes black again. And then it repeats this cycle forever. I eventually got irritated and yanked the battery.
So... *sigh*... what's my next best option?
The Nandroid backup completed successfully? If so, that's great, any APP customization is likely captured in the backup. How well they will restore is a different concern, but we need to get the device booted completely into android first.
Before moving onto the next step, lets reboot to recovery, clear cache and dalvik, and fix permissions. It's a bit of a shot in the dark, but I prefer to exhaust the possibility before abandoning this approach.
@Mr. Barker, You say that you've done a lot of heavy customization. What is the nature of the customization? app related? build.prop tweaks? I'm trying to determine how much might be lost by each of the next recovery methods.
@mrcook, what do you think of an attempt to dirty-flash cooked over a stock setup with corrupt /data?
cyril279 said:
Before moving onto the next step, lets reboot to recovery, clear cache and dalvik, and fix permissions. It's a bit of a shot in the dark, but I prefer to exhaust the possibility before abandoning this approach.
@Mr. Barker, You say that you've done a lot of heavy customization. What is the nature of the customization? app related? build.prop tweaks? I'm trying to determine how much might be lost by each of the next recovery methods.
@mrcook, what do you think of an attempt to dirty-flash cooked over a stock setup with corrupt /data?
Click to expand...
Click to collapse
I say wipe caches and fix permissions first. If that doesn't work format /system, and install a ROM of the same version of android.
After that if it's still not booting suck it up do a full wipe and start from scratch.
Sent from my SGH-S959G
@Mr. Barker
If the cache wipes / permissions fix doesn't help, then our next attempt is:
**this assumes that you were running stock Android 4.1.2 when the trouble began**
get i777UCMD8 cooked v2.2 onto a flashdrive, (or prepare it for sideload)
reboot to recovery
format /system
install cooked v2.2
attempt to boot into android
OK, I'll give it a try, thanks.
Hooray! All's well that ends well. Flashing i777UCMD8 cooked v2.2 got me up & running again, near-same as I had everything before. Just a little work to do to get it right back how I had it. Thanks a million, gents! :victory:
Two questions remain, for the moment:
+ How can I get the "AM/PM" to display on the notification bar? I'm in the US, and prefer to have this for the 12-hour clock. But using this ROM, it is omitted even when time is set to 12-hour clock.
+ How can I restore the default battery charging icon from the stock firmware? The one that comes bundled with this cooked ROM is needlessly flashy.
Mr. Barker said:
Hooray! All's well that ends well. Flashing i777UCMD8 cooked v2.2 got me up & running again, near-same as I had everything before. Just a little work to do to get it right back how I had it. Thanks a million, gents! :victory:
Two questions remain, for the moment:
+ How can I get the "AM/PM" to display on the notification bar? I'm in the US, and prefer to have this for the 12-hour clock. But using this ROM, it is omitted even when time is set to 12-hour clock.
+ How can I restore the black notification pull-down menu? This ROM sets it transparent by default, which doesn't work for me.
Click to expand...
Click to collapse
Am/pm is gone forever. I removed because I think it looks better without it. Use the sun. You'll get used to it after a couple days and never miss it.
To change the notification background go to the mods section of the installer, and just install the black notification background.
Sent from my SGH-S959G
mr-cook said:
Am/pm is gone forever. I removed because I think it looks better without it. Use the sun. You'll get used to it after a couple days and never miss it.
Click to expand...
Click to collapse
Oh, no, I was afraid you were going to say that. *sigh*
Unfortunately I will not get used to it, and will miss it. It's the little things that really matter to me, and this is one of them.
Is there absolutely no way I can add it back in? Maybe by editing or replacing a certain file? Or perhaps there's a notification bar replacement that will facilitate this need?
Also, how can I restore the default battery charging icon from the stock firmware? The one that comes bundled with this cooked ROM, I feel, is needlessly flashy.
Other than these two points, I am quite pleased with this ROM. Is it just me or does it run a little quicker than the stock one?
"needlessly flashy"
Simply asking 'how to change the icon' is sufficient, and inherently implies that you prefer something different.
Cooked v2.2 is definitely quicker than stock;
The premise of both cooked and shostock are that they have taken the stock firmware, and stripped it down of unnecessary junk, and run it over a well-optimized kernel for the best touchwiz experience that you could possibly have on this device.
If your firmware desires are different than what cooked v2.2 provides, then I suggest creating a nandroid backup, wiping /system, and giving shostock a try. It's the other touchwiz favorite for the i777, packaged with a different very good kernel, and also runs quicker than stock.
Mr. Barker said:
Oh, no, I was afraid you were going to say that. *sigh*
Unfortunately I will not get used to it, and will miss it. It's the little things that really matter to me, and this is one of them.
Is there absolutely no way I can add it back in? Maybe by editing or replacing a certain file? Or perhaps there's a notification bar replacement that will facilitate this need?
Also, how can I restore the default battery charging icon from the stock firmware? The one that comes bundled with this cooked ROM, I feel, is needlessly flashy.
Other than these two points, I am quite pleased with this ROM. Is it just me or does it run a little quicker than the stock one?
Click to expand...
Click to collapse
To close the loop, now your initial boot screen is a yellow triangle with an exclamation point? It doesn't affect the functionality of the firmware at all, but if you prefer to have the correct initial boot animation, then you'll need to follow an additional procedure.
Summary:
Nandroid-backup desired setup
Flash official stock-firmware to the device via Desktop-Odin (clears the warning)
Root & recovery via Framaroot/Mobile-Odin (a method that does NOT trip the custom-flash monitor)
Restore nandroid to return to the established custom setup
Procedure:
gather onto internal memory, or micro-sd:
-Framaroot
-Mobile Odin APK
-Mobile Odin flash kernel for i777
-Boot.img (extracted from your chosen firmware.zip)
boot to recovery
perform nandroid backup
^^ this MUST complete successfully
perform factory reset
boot to download mode
flash official UCMD8 using Desktop ODIN
^^ clears the custom-flash warning
install and use framaroot
^^ uses an exploit to establish and manage root access
install mobile Odin and the mobile Odin flash-kernel
^^ the method that will NOT trip the custom-flash monitor
flash the boot.img via Mobile Odin
^^ flashes the kernel and recovery of the firmware that you are going to restore
boot to recovery
restore nandroid backup
enjoy
-Cyril
If I am going to be restoring the nandroid backup, must I install & use the very same firmware that was installed when I made the backup? Or could I, say, simply flash the stock firmware and be done with it? (i.e. not use mobile odin to install a custom firmware afterwards) My point is, are nandroid backups firmware-specific?
If I opt to go the custom firmware route, how do I go about getting the boot.img file? Simply rename zimage, or ???
Before all this I've never flashed anything but stock firmware, and never had to create nor restore nandroid backups. So most of this is all new to me. But I enjoy the learning process.
Mr. Barker said:
If I am going to be restoring the nandroid backup, must I install & use the very same firmware that was installed when I made the backup?
Click to expand...
Click to collapse
Different custom firmwares may be structured differently, so for the lowest likelihood of compatibility issues, nandroid backups should be considered firmware specific.
Edit: As Mentioned below, a CWM nandroid will restore the entire backed-up firmware installation, which can be done over ANY firmware.
If the goal is to keep your App data across different firmwares, then a Titanium backup restoration may be what you're after. /Edit
Mr. Barker said:
[...]could I, say, simply flash the stock firmware and be done with it? (i.e. not use mobile odin to install a custom firmware afterwards)[...]
Click to expand...
Click to collapse
I don't think that the stock recovery allows to restore nandroid backups at all. The restrictive nature of the stock recovery is one of the more practical reasons to root the device & use a custom kernel.
Mr. Barker said:
If I opt to go the custom firmware route, how do I go about getting the boot.img file? Simply rename zimage, or ???
Click to expand...
Click to collapse
Mobile Odin will flash a zImage, no need to rename it. I didn't check to see that shostock or cooked use a zImage instead of boot.img.
cyril279 said:
Different custom firmwares may be structured differently, so for the lowest likelihood of compatibility issues, nandroid backups should be considered firmware specific.
Click to expand...
Click to collapse
?? I thought that because a nandroid copied (backup) and then formatted/recopied the 5 partitions (restore), that it didn't matter what firmware you had installed?