You can now have your own custom boot splash. (You must be S-Off!)
(This is the first picture you see when you boot up your device, before the boot animation starts. The one you also see before booting into recovery.)
How to do it:
Upload a picture to the boot splash generator, (Preferably 480x800.)
It generates and downloads a flashable .zip file,
Flash the resulting .zip file in recovery.
Disclaimer:
You have unlocked and rooted your device, flashed custom recoveries, and turned it S-Off, so by now you should know that you have nobody to blame but yourself.
Anyway: This tool is provided as is, with no warranty whatsoever.
Some context:
I had already done this for the One-S Ville and Ville C2. See this thread. (Don't flash the zips posted there on your Desire X!) I own the One S, and mapped out the partitions, and found out that we could change the splash on certain hboot versions while still S-On. When we got S-Off, all hboots could flash a custom splash.
Later I added support for the One M7, and now added support for the Desire X as well.
Thanks to @SecUpwN for identifying the splash partition (this links to how it was done) and for putting his device at risk for testing. I do not own this device myself, so @SecUpwN carried out the research and tested my first flashable .zip and later the php generator. These were all opportunities to destroy the device. As I understand, it isn't even his own device but his girlfriend's which makes it even more dangerous. (But then, I guess he deserves to be the one to take the risk, as it was his idea to add Desire X support in the first place... )
Luckily it all went smoothly, so no device had to be destroyed in the process.
How it works:
On the Desire X, partition 19 (/dev/block/mmcblk0p19) contains the boot splash.
The first 750kB, 768000 bytes (480 x 800 x 2), are raw RGB565 bitmap data.
On boot, this data gets copied into the frame buffer. We can put anything in there.
The boot splash generator resizes your image to 480x800 and then converts it to raw 16 bit RGB data.
It then puts the result into a recovery-flashable .zip file. When run on the phone in recovery, it unpacks the raw image file and copies it into partition 19.
Note: /!\ I have never been able to test this myself, since I don't own the device. At time of posting I have only one confirmation, even tho it comes from @SecUpwN who personally did the research and testing. It would still be nice to see a few confirmations.
Edit: We now have a couple more confirmations. Thanks for that.
Back to stock
The attached .zip is recovery flashable. It contains the stock boot splash. (I took the image from an extracted RUU, turned it into a .bmp and ran that through the generator.) So if you ever want the stock splash back, you can flash this. Running a RUU will also flash the stock splash back.
Enjoy!
If you create any cool splashes, that others might like, post them with a pictures and zips.
-Jobo
I may do something with this. Or not.
Grabbing post number three: THANK YOU for your dedication and heart blood to developing your online generator, @touch of jobo! I hereby confirm that my girlfriend is now a happy user of a modded boot splash with a picture of us two.
All research has been carried out carefully and as thorough as possible. If you closely follow the steps mentiuoned in the OP, nothing can go wrong - although we provide no guarantee whatsoever and are not liable for anything you do to your phone. But rest assured: I love modding and hacking - it was a pleasure to contribute to the work of Mr. jobo.
Flash away and post your fanciest boot splash ZIPs! Oh and hey, don't forget to press "thanks". ENJOY!
Thread cleaned,
Thread has been cleaned as the last few posts do not relate to this topic.
Many thanks,
Ghost
Hello~everybody
Well,I made one in yesterday~
Hope you guys like it!!
First,this photo is the Japanese Animation callatema Inverted Japanese name:サカサマのパテマ
I like PATEMA very very much><
She is so cute........
Full size image:
http://forum.xda-developers.com/attachment.php?attachmentid=2781797&stc=1&d=1401965962
Approximate location:
http://forum.xda-developers.com/attachment.php?attachmentid=2781798&stc=1&d=1401965962
My Boot Splash
Flash .zip file in recovery.
Download
View attachment 2782748
Related
I've been reading through the XDA forums for days on various splash screen solutions. So far, not one of them will work on the P509 Optimus T.
When the P509 is powered up, you get 3 startup images.
#1 - LG Logo - SPLASH.IMG file
#2 - Animated T-Mobile "Stick Together" magenta/white splash screen (THIS MUST DIE)
#3 - Android boot animation (located in /system/bin/bootanimation in t-mobile 2.2.2 V10S firmware)
I am aware of the bootanimation.zip in /system/media/. This is NOT the issue I am referring to, and does not apply to my desired results.
Again - I have read nearly ALL of the other threads on this problem - they do not apply. There is NO fastboot or hboot menu option on this phone like the HTC or samsung, and as far as i can tell there is no "Splash1" partition either.
What I am trying to do is replace the animated T-Mobile splash screen with my own.
I know the boot animation is most likely the initlogo.rle file, or related to it. It gets dropped into the root of the phone at boot and disappears every time the phone is turned off. If I try and manually place my own there, it gets overwritten.
I'm assuming it hides in the boot.img file in the firmware somewhere. What I -DONT- know is how do I rip that damned file apart, replace the animation with my own, and then put it back together again. I have seen a LOT of people ask on various forums about the various LG Optimus models; and they have all been pointed to information that does not apply to these phones.
I know that many other firmware developers have embedded their own splash image in their roms and this will over-write the T-mobile magenta monstrosity. Unfortunately, I have ZERO need or intent on flashing a new ROM. I am happy with my stripped and tweaked stock rom and franco kernel.
Oddly, the SPLASH.IMG file is a RED lg logo, but it's hidden by a Silver LG logo that I assume is hardcoded into the phone somewhere, so the only time you see it is on boot to CWM recovery for 1/2 second or less.
I have managed to decompile my stock KDZ firmware file, and then decrypt the resulting DZ file down to the *.mbn files and the Boot.img, recovery.img, and splash.img files if they are useable for anyone interested in screwing with an old 2.2.2 stock. >.<
Is there anyone that CAN do this, or at least help me figure out how to go about doing it myself?
There is a post on this. U have to recompile the boot.img I thinl
Sent from my LG-P500 using xda premium
As far as I know, changing the the splash screen can not be changed or altered in any form but I'm sure it can be done, unfortunately there isn't much talk about that sort of thing, give me a few days and I'll look into it, I gotta do research
Sent from my LG-P500 using xda premium
Jrhodes85 said:
As far as I know, changing the the splash screen can not be changed or altered in any form but I'm sure it can be done, unfortunately there isn't much talk about that sort of thing, give me a few days and I'll look into it, I gotta do research
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Download the kitchen, put your ROM in the right folder, go to advanced tools in the kitchen, choose extract boot.img
There is a post about this by ciaox / Bytecode
Good luck
I was unable to find the ciaox/Bytecode post.
But the splash screen and sound bothered me,
so some exploring lead to the following ...
You can replace the annoying jingle:
/system/sounds/lgeSounds/Startup.mp3
The T-Mobile "Stick Together" screen are the 8 open*.rle files in /bootimages
You can use pratyush.creed's boot logo editor to generate replacement files
forum dot xda-developers dot com/showthread. php?t=1383396
www dot mediafire dot com/?pyebp4b7ymkcnjd
(sorry, not allowed to post links yet)
For the shutdown splash and sound, you will need to decompile,
replace the images and sounds then rebuild /system/app/PowerOff.apk
Cheers.
me too having the same problem...
Bytecode's thread
Hi guys, has anyone figured out how to change the splash image of the streak 5? i am referring to the dell logo(or the 02/softbank logo) before the android boot animation begins.
I know that HTC phones have their splash image stored in the 'splash1' partition. However this partition doesn't to be to exist on the streak or is named something else. Perhaps someone here has a clue?
Dell Streak 5 partition map -xda wiki
There is a partition named splash, it's also the only partition that I dont know the contents of.
BUT, pkgs can change the splash without ever touching that partition. I'm inclined to say that the splash partition is a red herring and that on the s5 it's stored directly in the bootloaders.
Thanks for the enlightenment, I am aware that PKGs can change the splash screen but also couldn't figure our why. Perhaps I will spend more time researching it.
Chrisrotolo looked into to some of this before giving up, he might have some tidbits but i'm pretty sure overall it's far too risky for the reward.
We can change the image
After splash before bootanim
Its init.rle file
Which is included in kernel
ther's rle to raw converter and again to rle
Try
fards got the closest I believe, it involved a framebuffer image.
I did flash an SoftBank ROM to mess around, and it looks like there are actually 2 of these splash screens, 1 is only seen occassionally, but it is the same Dell logo.
General Tip about splash screens: usually difficult and dangerous, not quite worth bricking a device.
and with that being said off I go to see if I can rebuild a Kernel for GTAB7+ just for splash screen .....
Check this link
this should help.
http://www.slatedroid.com/topic/28946-change-boot-splash-screen/
Okay, first let me totally come clean and admit I've been an idiot.
Secondly let me apologise for posting this in what may be entirely the wrong place, I'm needing help, challenged for time, and hoping that one of you knowledgeable people may be willing and able to give me some advice.
I've been a Cyanogen user for years (on HTC Magic), so when Vodafone UK sent me a spanking new HTC Desire S yesterday, (HBOOT – 2.00.0002), I explored it for a while then quickly wondered what it would be like running cyanogen 7.1.
Now things have changed since my happy old experimenting with nightly builds – we had twins a few months ago and time is not what it used to be. I rushed into things a bit. I unlocked the bootloader through HTCDEV then flashed CWM recovery "touch 5.8.1.5 saga". All fairly straightforward.
I then booted into recovery and attempted to flash "update-cm-7.1.0-DesireS-signed.zip"
I dare say you've spotted the foolish error already, yes, I didn't backup my current rom.
It was 2 a.m. and it was only a matter of time before one of the babies would wake up.
So now I'm stuck on the white screen of frustration.
Is it possible that the update.zip is corrupt? I downloaded it from the Cyanogen link: http://download.cyanogenmod.com/?type=stable&device=saga
but I can't seem to extract the boot.img, Winrar tells me the file is corrupt but that may be because it's not a standard windows format??
ADB is not finding the device so I can't logcat.
What should be my next step?
Can anyone suggest a reliable ROM to try instead?
You can call meanything you like for my foolishness, I'm sure you won't think of any names I haven't thought of myself – I should have left the darn thing alone if I didn't have time to do it properly.
Dead simple you total dork!
copy the boot.img from the ROM zip in windows explorer, put it in your adb folder then "fastboot flash boot boot.img"
Honestly, some people.
has anyone successfully done this? i have a rooted fascinate running aokp milestone 4. i have read all the forums and have studied for hours. i finally got the nerve to try it....and....brick. lol i tried using heimdall. installed the drivers properly, opened the program, flashed the hacked param.lfs, program ran, phone booted into a blank screen for about 25 sec then went into recovery. tried wiping and restoring but right back to recovery i went. lol . had to odin to stock and build back up.
was just wondering if someone got this to work and could maybe give me a clue of what i may have done wrong..thanx.
Are you just wanting to replace the boot animation? In the case of AOPK, this would be the Unicorn animation. I do this all the time, directly from the phone. I use ES Explorer, although Root Explorer or an equivalent should work just as well. You'll need to go to /System/Media and delete the pre-exisiting bootanimation.zip. You can then replace this file with your preferred boot animation and be good to go. You can also move the old bootanimation.zip to your SD card before replacing it, allowing for easy recovery if you decide you want it back. You can also place your preferred boot animation in /data/local and supposedly a re-flash won't overwrite the boot animation. I haven't done this, as I prefer to see what animation is included in the ROM, then change it out if I wish. I'm sure there's other ways to accomplish this, but this procedure is quite simple. My preference at the moment is the rockets animation from makelegs' CM7 Kang, but there are lots available for download. Or, you can make your own if you are so inclined. I have a folder on my SD card that has a half-dozen boot animations in it, allowing me to choose which one I'd like to use.
If you need to download ES Explorer, there are a few options you'll need to enable to be able to manipulate the local filesystem. They are "Root Explorer" and "Mount File System" I think it goes without saying, but you'll need to grant ES Explorer with root permissions when prompted.
WARNING: If modifying your file system like this, BE CAREFUL what you delete. Delete the wrong file, and you could be starting over. I am not responsible for you bricking your phone.
I believe bdogg is referring to the boot splash screen. If you are following the directions that I think you are, I have not yet been successful at getting it to work yet either . If you figure it out let me know.
Sent from my SCH-I500
It is quite possible that I misunderstood which screen it was he was wanting to change. On my phone, all I get during the boot sequence is the black & white "Samsung" screen twice (once when the phone first powers on, and then it flashes quickly and reappears for what I assume is the Glitch kernel), and then the AOKP Unicorn boot animation. Once the Unicorn boot animation finishes, I get the unlock screen, at which point I consider the boot process finished. To my knowledge, you can't change the B&W Samsung screen. I could very much be wrong here, I've just never seen anything stating differently. The Glitch "logo" is set in the kernel, although I'm guessing if you edit the right thing in the .zip before you flash it that could be changed. It's not something I care to attempt, it's not on screen long enough for me to really care, and I have no preference to go messing around in the kernel. That leaves the Unicorn boot animation, which I know can be quite easily changed out to whatever different boot animation you prefer.
I'm currently running AOKP Build 28 with Glitch 14 B6.
EDIT: After a quick Google search, it appears I am wrong and that it is possible to edit the default "Samsung" screen. I didn't fully read up on the process, as I don't care to do it myself, but I did glean enough to know that I probably posted instructions here to something that you already knew, and that didn't help you one bit. I'll do better next time.
Yes, we are talking about the initial samsung logo. It is fun to change it to other things i admit. I only was able to do it per the instructions on the gb roms. I thought I saw new ones for ics but can't remember where I saw them.
Sent from my SCH-I500
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!