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
Related
I cannot for the life of me coax my Rezound into creating a nandroid backup. I kind of a n00b, so I'll give you my info and how I rooted.
ROOT
I rooted by following Scotty's noob friendly root guide: http://androidforums.com/rezound-al...ys-noob-friendly-root-guide-start-finish.html
I followed his instructions for "temporary recovery" which installed Amon RA 3.14
MY CURRENT SOFTWARE
Android version 2.3.4
HTC Sense version 3.5
Software number 2.01.605.11
FIRST ATTEMPT
I went into Amon.
I selected "Nand backup".
There were several options on the next screen. It looked like this:
- [X] boot
- [X] system
- [X] data
- [X] cache
- [] recovery
- [] sd-ext
- [] .android_secure
- [] .android_secure_internalsd
- [] compress_backup
- Perform Backup
- Return
I left the selections as they were.
I selected "Perform Backup".
Before confirming my selection, it said:
Use Other\recoverylog2sd for errors.
I confirmed my selection.
It gave me the following messages:
Performing backup : ..
Oops... something went wrong!
Please check the recovery log!
SECOND ATTEMPT
I installed ROM Manager.
I selected "Flash ClockworkMod Recovery" ... not realizing exactly what I was doing. None the less ...
I booted into CWM.
CWM freezes while making a nandroid backup. Every time. Battery pull. Every time.
THIRD ATTEMPT
I followed Scotty's "temporary recovery" instructions to install Anon RA 3.15 (different version this time)
The md5 in the command window did not match the md5 at download site (http://forum.xda-developers.com/showthread.php?p=23781936)
Seeing no alternatives, I flashed it anyway ... Nothing catastrophic happened.
Did same thing I did in the first attempt, and it gave me the same message.
Anyone have any other ideas?
Why are you using temporary recovery? Why not just flash AmonRa "fastboot flash recovery <whatever_your_amonra_image_file.img>" ? It works perfectly fine as the recovery partition for almost everyone else.
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
bloodymurderlive said:
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
Click to expand...
Click to collapse
You realize that after the OTA your backup won't work right? If you're just trying to cover yourself between now and then, maybe just copy your whole system and data partitions manually??
bloodymurderlive said:
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
Click to expand...
Click to collapse
Why would you even want to flash a temporary to make nandroid backups? If you are getting the OTA then your best bet would be to backup everything with MyBackup, then copy and paste it from your sdcard to computer.
MrSmith
Couldn't I flash Amon RA after OTA (rooted, of course), and then restore the nandroid? I thought nand backups work independently of whatever ROM you're running ...
uToTMeH8
But I want to keep my current stock ROM backed up, not just my apps and data. And why not flash a temporary to make nandroid backups?
Maybe I need to explain better ...
I want to be rooted.
I like Sense.
I like that OTA updates are automatically pushed to my phone.
I don't understad why I can't enjoy these things and create a nandroid backup of my current ROM in case I decide to try other ROMs.
Are you saying that a permanent recovery is the difference between it working and not working?
Ok, maybe someone can just answer that last question for me:
Are you saying that a permanent recovery is the difference between it working and not working?
bloodymurderlive said:
Ok, maybe someone can just answer that last question for me:
Are you saying that a permanent recovery is the difference between it working and not working?
Click to expand...
Click to collapse
I can't say for certain because I've never gone through that situation before, but if you want to be stock...Why not just let the OTA update you to ICS stock and keep it as it is? Do you really like Gingerbread Stock that much? I guess I just don't understand your reasoning behind all of this. If you were flashing a new ROM after wiping everything in a recovery I would understand your need to nandroid...
---------- Post added at 12:19 PM ---------- Previous post was at 12:13 PM ----------
bloodymurderlive said:
MrSmith
Couldn't I flash Amon RA after OTA (rooted, of course), and then restore the nandroid? I thought nand backups work independently of whatever ROM you're running ...
uToTMeH8
But I want to keep my current stock ROM backed up, not just my apps and data. And why not flash a temporary to make nandroid backups?
Maybe I need to explain better ...
I want to be rooted.
I like Sense.
I like that OTA updates are automatically pushed to my phone.
Click to expand...
Click to collapse
The firmware that is updated with an OTA update will most likely break Gingerbread compatibility if you try to restore a temporary nandroid backup.
With S-Off none of this would be a problem because we would just flash old radios and kernels right from recovery. HTC makes it difficult to downgrade
uToTMeH8
I want to have the option to return to whatever ROM I want.
If I OTA-update to ICS, I want the option to return to GB (especially given how notoriously buggy OTAs are).
If I install a custom ROM, I want the option to return to stock if I don't like it.
So you're saying that I can't just backup any ROM and switch between them at will? That kinda sucks ...
I might just try a permanent recovery anyway, it seems to be the only thing anyone can think of to try to get Amon RA nandroid working ...
bloodymurderlive said:
So you're saying that I can't just backup any ROM and switch between them at will? That kinda sucks ...
I might just try a permanent recovery anyway, it seems to be the only thing anyone can think of to try to get Amon RA nandroid working ...
Click to expand...
Click to collapse
This is why everyone is going mental about s-off in this thread:
http://forum.xda-developers.com/showthread.php?t=1578449
Honestly unlocking your bootloader, flashing Amon-Ra and backing up your stock is the way to go. I've had my phone unlocked for 3 months with no problems and the devs on this site are amazing! You're going to want to try every gingerbread ROM once you get really good at backups and flashing. I was getting around 6-8 hours on the stock ROM for battery life. I flashed NilsP's Business Ginger Sense and I hit 30 hours. It's ridiculous how much better battery life is after stripping the ROM down and adding tweaks.
This Toolkit really makes it very easy...Good Luck!
http://forum.xda-developers.com/showthread.php?t=1504824
The error is commonly not enuff space on the SD,or insufficient battery charge.
It has nothing to do with leaving the stock recovery in place.
The only reason you won't be able to restore your gb backup after ics is the fact that it takes a different hboot and.radio,and until the s off method is released,there is no way to revert those. With htcdev,you can only go fwd,not back.
MrSmith317 said:
Why are you using temporary recovery? Why not just flash AmonRa "fastboot flash recovery <whatever_your_amonra_image_file.img>" ? It works perfectly fine as the recovery partition for almost everyone else.
Click to expand...
Click to collapse
uToTMeH8 said:
Why would you even want to flash a temporary to make nandroid backups? If you are getting the OTA then your best bet would be to backup everything with MyBackup, then copy and paste it from your sdcard to computer.
Click to expand...
Click to collapse
the reason for leaving the stock recovery is simple: a custom recovery will not install an OTA.
if you leave the stock recovery in place,the OTA will happen,quite naturally,and without isrupting your personal data. sure,it will break root,and anything youve frozen will pop back up,so you do have the minor inconvenience of re-freezing some bloat,and re-launching the temp recovery to flash root files. not a big deal,IMO. remember,htcdev is more like s-off in that you will always be able to root,or re-root. its not an exploit that will disapear.
even if a person wishes to permanently install a recovery,i strongly recomend to get into the habit of launching recovery from fastboot when messing with your phone. as we know,htcdev only unlocks boot,recovery,and system,and we cannot write 'boot' from 'recovery'.
however,launching recovery from fastboot(what ive been calling a 'temporary' recovery) does allow recovery to write to boot. it doesnt do much good(yet) for flashing,as rom devs are still not including the neccessary scripts to install the kernel,but it does allow you to restore nandroids without a seperate kernel flash,making them quicker and easier.
until you switch to ICS firmware(i.e.,install the leaked ruu,or take an OTA) you can flash,backup,and restore any gingerbread roms,and GB firmware based ICS roms,as you desire.
again,what the guys were trying to say when the said you cant restore the GB backups after ICS is simply because the hboot and radio are different. sure,you can physically power up your recovery and restore a GB backup with ICS hboot and radio(firmware),and it will restore,and even boot. you will just have issues due to the incompatible firmware,such as the disapearance of your SD card
hope that helps clear a few things up for you. sorry the above reply was short,i was trying to reply on my phone at work
edit:
one last thing: since youve downlooaded rom manager and used it to flash clockwork recovery,you now have a permanently installed clockwork recovery. you can still temp launch amon with cw in place,but you now are missing the stock recovery,and as such will not be recieving OTAs. if this is important to you,you need to download the stock recovery,and permanently install it(fastboot flash recovery recoveryname.img)
http://www.mediafire.com/?wb21d2gdurui2c6
Thanks Scotty!
First, I'm a complete moron and assumed that my 32GB microSD had enough space. I deleted a movie and made my backup.
One question though about the CWM recovery ... I was concerned that it was permanently installed. However, I attempted to boot into recovery from my phone (power + volume down), and it booted into what looked like the stock recovery ... No dark Amon or CWM recoveries ... Is it possible that CWM didn't permanently flash after all? I know that I have been in both Amon and CWM, and CWM was installed from within the ROM Manager app ...
Are you sure you were in recovery, because power and volume down boots to the bootloader, called boot, which is entirely different.
Sent from my ADR6425LVW using xda premium
Yup, you're right ... I even experienced the won't-charge-or-boot-if-battery-is-low issue with CWM. Fortunately, my wife has the Thunderbolt which was able to charge my battery for me.
So ... Even though I can't receive OTA updates, I can still manually install them, right?
bloodymurderlive said:
Yup, you're right ... I even experienced the won't-charge-or-boot-if-battery-is-low issue with CWM. Fortunately, my wife has the Thunderbolt which was able to charge my battery for me.
So ... Even though I can't receive OTA updates, I can still manually install them, right?
Click to expand...
Click to collapse
Yes, Once and OTA is released it should not be long till someone posts here the zip install of the same OTA. Give it another day and I say you will see a cleaned up debloated, rooted etc... zip of the same OTA. These days there is really no need to rush for the OTA downloads, let the Dev's do their magic and offer you something better than Big Red will offer.
I used Hansoons all in 1 toolkit to root my rezound, I unlocked the bootloader, loaded the twrp recovery and flashed supersu. Now when my phone boots all I get is the bar across the top with the signal strength, battery level, and time. What can I do to get my phone to function again??
I had previously unlocked with the toolkit and ran a few root apps and removed some blotware. I then relocked and everything was working fine until I tried to root it again.
Are you s-on then?
Did you RUU first? Might want to do that since you had made changes before. That will bring you back to nice and fresh stock.
The latest one is here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
IF YOU ARE S-ON... you can relock, RUU and then flash the recovery again and get root and see if that helps.
If you are s-off then await someone else's answer, but I think you run the RUU without relocking.
Ya, s-on. That looks like what I need to do, just wasn't sure what to call the process and search for... Unfortunately with my 4g internet via my phone gone, I gotta sit here and wait on the download to complete on my slower internet. Greatly appreciate the fast response!!!!
disdard said:
Ya, s-on. That looks like what I need to do, just wasn't sure what to call the process and search for... Unfortunately with my 4g internet via my phone gone, I gotta sit here and wait on the download to complete on my slower internet. Greatly appreciate the fast response!!!!
Click to expand...
Click to collapse
The answer isn't always RUU. Running an RUU will reverse everything that you just did. You will lose root. You're phone will be wiped. And you'll have to relock. What I recommend trying first is rebooting into recovery. Twrp in this case for you. You can do this by getting into bootloader (power and volume down on boot up) and hitting recovery. Once in recovery try wiping cache and dalvik. Reboot. If that fixes it... Cool. If not.. reboot into recovery again and wipe data. This time it should almost certainly work. You won't have root. But you will be stock.
Flashing a custom ROM will fix your problem as well.
There is almost nothing that you can screw up to the point of HAVING to RUU. Most people only use an RUU to update firmware and radios when new versions are released
Sent from my ADR6425LVW using Tapatalk 2
GetRipped said:
The answer isn't always RUU. Running an RUU will reverse everything that you just did. You will lose root. You're phone will be wiped. And you'll have to relock. What I recommend trying first is rebooting into recovery. Twrp in this case for you. You can do this by getting into bootloader (power and volume down on boot up) and hitting recovery. Once in recovery try wiping cache and dalvik. Reboot. If that fixes it... Cool. If not.. reboot into recovery again and wipe data. This time it should almost certainly work. You won't have root. But you will be stock.
Flashing a custom ROM will fix your problem as well.
There is almost nothing that you can screw up to the point of HAVING to RUU. Most people only use an RUU to update firmware and radios when new versions are released
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Well it's not like one should avoid RUU like the plague, geez.
As to wiping your phone, flashing a custom ROM can/will do that as well. Relocking and unlocking again are really no big deal, just a couple commands. Rerooting is simple. It's really not as bad as you make it out to be, imo. And in fact, there's a ton of threads suggesting running an RUU to solve issues and get a fresh start.
I like to run an RUU since it brings you back to a nice fresh stock install, and yes, it will update if the phone is not up to date. In this case to global, which is a bonus.
feralicious said:
Well it's not like one should avoid RUU like the plague, geez.
As to wiping your phone, flashing a custom ROM can/will do that as well. Relocking and unlocking again are really no big deal, just a couple commands. Rerooting is simple. It's really not as bad as you make it out to be, imo. And in fact, there's a ton of threads suggesting running an RUU to solve issues and get a fresh start.
I like to run an RUU since it brings you back to a nice fresh stock install, and yes, it will update if the phone is not up to date. In this case to global, which is a bonus.
Click to expand...
Click to collapse
Oh hai there.:angel:
disdard said:
I used Hansoons all in 1 toolkit to root my rezound, I unlocked the bootloader, loaded the twrp recovery and flashed supersu. Now when my phone boots all I get is the bar across the top with the signal strength, battery level, and time. What can I do to get my phone to function again??
I had previously unlocked with the toolkit and ran a few root apps and removed some blotware. I then relocked and everything was working fine until I tried to root it again.
Click to expand...
Click to collapse
It sounds like you just need a new launcher. If you're getting to that point are you able to pull it down and see the notification area?
If yes then you could use Droid Explorer to push another launcher to the phone.
If not, yeah you maybe looking at starting over. Have you tried using a different recovery? I know personally I've had issues with every launcher except for Amon Ra.
I ran RUU, and once reset to stock breezed through the process of rerooting. Unfortunately had that done before any of the other replies, because it would have been easier to just do the resetting. But I got into the mess while trying to straighten out the issue of my dialer and people app disappearing so just fully going back to stock ensured I got the entire mission accomplished. And at the point it would boot to, you couldn't pull up the notification window so a new launcher wouldn't have fixed it.
Atleast I learned a bunch through the process!!! Just getting into rooting and customization, took the first step and rooted and kinda figured out how things work. Once I figure out a little more and decide which ROM I want to try, I'd like to try a custom ROM. All stuff I'm familiar doing with computers just gotta figure out exactly how it all works on phones....
Glad you are back up and running! Sorry if my method was more involved/time consuming.
I would suggest that before you flash a custom ROM you make a nandroid of your stock set up. Then you can always flash back to that if you don't like the ROM or run into issues and avoid troubleshooting or RUUing just to fix something.
It's a good safety net and a good habit to always have a nandroid to go back to in case of issues. I usually keep one handy of stock and of any ROMs I like, and always make one before flashing a new ROM or even a theme for a ROM.
Dunno if I'm risking flaming but here goes...
Had my Rez from day one, the phone is HTC unlocked but S-ON. I am still running a stock, rooted and debloated GB rom (based on the very first OTA update we got way back when). The rom has run great for me and so I never really had much reason to update...
The ONLY persistent issue I've had is with 4G cutting out, usually whenever trying to watch vids on Youtube, or trying to use Google Maps. Works fine on 3G. Way back when, someone had posted a thread where a lot of people mentioned they were having this exact same issue, so I figured that it was not an issue with my particular phone or even the rom/firmware. Even non-Rezound Verizon customers were complaining that they were having the same issues at the time (early last summer) so it seemed to be a network issue.
Fast forward a year and no one seems to be complaining about this issue anymore, and my wife has a Galaxy S3 that does not exhibit the problem... so I'm assuming that one of the OTA's that bumped the Rez up to ICS and updated the radios/firmware fixed this issue as well, so I would like to finally update to the latest and hopefully be done with this issue.
I have been reading threads and I think I know what steps I need to take, and wanted to run it by you guys and make sure I'm not missing something or doing something I shouldn't be, and that I have them in the right order... so here's my understanding:
1. Make a nandroid and titanium backups
2. Backup everything on the internal and external SD card
3. Relock device
4. Do I need to flash back to the stock GB OTA (to restore stock bloat apps that I've removed) or can I go straight to next step??
5. Flash latest RUU (can I do this from a PH98IMG.zip or does it have to be an RUU.exe run from my computer? I strongly prefer the PH98IMG method if possible)
6. Unlock device
7. Flash recovery
8. Root device
I don't really have any interest in S-Off or any custom roms, so I have left those steps off. Even back with the Incredible and now with the Rez, I've always been happy with the stock Sense rom just with bloatware removed, and that's my end goal here as well. So, do I have everything covered?
Points 1 & 4
1. Use MyBackup root instead of Titanium.
4. It will do a complete wipe also in the process, not needed.
PH98IMG will work, I highly and strongly suggest contemplating s-off NOW(if you really want to, not needed) versus doing it after. The PH98IMG you might want to look at is 3.14.605.12. If it's of any help, there was a few OTA's on top of that, which VZW may ask if you want to take through an OTA on the Rez's rom.
cool thank you for the tips. I was able to get onto the latest global OTA and firmware without issue.
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!
I bought a note 3 thats rooted already and ive rooted a device before but this root or maybe the kitkat version does not give me 4glte i currently have lidroid official v1.5.1 it has a lot of features i like anything similar that comes with kitkat 4.4.4? i tried the freze rom and its not letting me load it to the phone for some reason any help or input is appreciated thanx
P.Dub said:
I bought a note 3 thats rooted already and ive rooted a device before but this root or maybe the kitkat version does not give me 4glte i currently have lidroid official v1.5.1 it has a lot of features i like anything similar that comes with kitkat 4.4.4? i tried the freze rom and its not letting me load it to the phone for some reason any help or input is appreciated thanx
Click to expand...
Click to collapse
It appears you are running an outdated version of this rom here http://forum.xda-developers.com/showthread.php?t=2485607 if you like the rom down load the latest version and flash with odin. Who is your carrier ? This rom is for SM-N9005 which is AT&T ? As far as 4G LTE go settings/general/system update/update PRL then power down and reboot the device.
If your on a Sprint carrier I would get back to stock NC5 rooted, this thread will answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
jimzweb1 said:
It appears you are running an outdated version of this rom here http://forum.xda-developers.com/showthread.php?t=2485607 if you like the rom down load the latest version and flash with odin. Who is your carrier ? This rom is for SM-N9005 which is AT&T ? As far as 4G LTE go settings/general/system update/update PRL then power down and reboot the device.
If your on a Sprint carrier I would get back to stock NC5 rooted, this thread will answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
Click to expand...
Click to collapse
yea i have sprint and already tried to update the prl i tried another rom with kitkat4.4.4 and it gave me 4glte but it kept crashing on me so switched back im going to take a look at the link you suggested thanx
P.Dub said:
yea i have sprint and already tried to update the prl i tried another rom with kitkat4.4.4 and it gave me 4glte but it kept crashing on me so switched back im going to take a look at the link you suggested thanx
Click to expand...
Click to collapse
This is what I would do. First odin flash back to NC5 stock unrooted. Then boot into stock recovery and do a factory reset. Next odin flash NC5 stock unrooted .tar again, then boot into download mode it should look like this
with official on both lines, sometimes it shows official on one line and custom on the other. That will give you headaches later. Now go ahead root, and install a recovery, beloat the stock rooted rom, for use as a daily driver, and make sure nothing crashes. Next make a backup so you have base to work from. Follow the instructions on the thread I listed above. I know this seems like a pain, but somewhere part of that AOSP rom is being left behind and causing your install of a stock rom to crash.
So I searched and found a ROM its nice and simple but now WiFi doesn't work ?
Sent from my SM-N900P using XDA Free mobile app
P.Dub said:
So I searched and found a ROM its nice and simple but now WiFi doesn't work ��
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Well thats no good!!! What are you looking for in a rom functionality for customization? Touch wiz or some like CyanogenMod? Can you upload a screenshot of what your device is running? Like 4.4.2 or 4.4.4? Do you have custom recovery?
Goat1378 said:
Well thats no good!!! What are you looking for in a rom functionality for customization? Touch wiz or some like CyanogenMod?
Click to expand...
Click to collapse
I want something similar to what I have. The rom I just tried was the cyanogen and wifi didn't work with it and it kept rebooting after an 1 hr of trying it on my phone.... main reason I want to switch is to get the 4glte I like the ability of not holding down the buttons to go into recovery
Sent from my SM-N900P using xda app-developers app
P.Dub said:
I want something similar to what I have. The rom I just tried was the cyanogen and wifi didn't work with it and it kept rebooting after an 1 hr of trying it on my phone.... main reason I want to switch is to get the 4glte I like the ability of not holding down the buttons to go into recovery
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
So you like aosp roms? Ok are you on NC5 or NH7? The screenshots in my last post will show you what you look for under setting/general/about device
Yes custom recovery I believe. And 4.4.2
Sent from my SM-N900P using xda app-developers app
P.Dub said:
Yes custom recovery I believe. And 4.4.2
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Do you have a pc with odin?
Yes sir I do
Sent from my SM-N900P using xda app-developers app
P.Dub said:
Yes custom recovery I believe. And 4.4.2
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Do you want update your firmware to NH7 or stay NC5?
Would like to update. I would need a new rom correct?
Sent from my SM-N900P using xda app-developers app
P.Dub said:
Would like to update. I would need a new rom correct?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Hey Pedro,
I put together this post when helping another person out on another thread. I think it'll work as a step-by-step guide for you:
I'll explain how to install a custom ROM and some common things to think about/check prior to installing anything:
Installing a Custom ROM
Step 1 - Gather Information
First off, you need to know what version of Android your phone currently is running. This is easily done by looking in the Settings Menu -> General -> About Device.
The Main things we are looking at on this screen are Software Version, Model Number, Android Version, and Baseband Version. I'll explain these (to the best of my knowledge) below:
Software Version:
This is the "type" of Android that you're running. Rather than quoting the entire name, we typically only refer to the last 3 characters (MJ4, NAB, NC5, etc.). Stock Note 3 devices will (most-likely) be running one of 3 different versions of TouchWiz (TW):
MJ4 - This is the last Jellybean version of TW for the Sprint Note 3NAB - This is the first KitKat TW version for the Sprint Note 3NC5 - This is the second KitKat TW version for the Sprint Note 3NH7 - This is the latest KitKat TW version for the Sprint Note 3
The reason that we are concerned with the Software Version is that between the MJ4 and NAB versions, there were major changes. So if you're running MJ4, you will have to do additional steps before flashing a custom ROM based on a newer version. And if you're on NAB or NC5, you will not be able to go back to MJ4, so beware what you're flashing.
For the most part, if you're on NH7, you can flash either a NH7 or NC5 custom ROM, but just read the ROM's FAQ to see if there are any issues with doing so.
Model Number:
Most people don't worry about this, but I always do when looking at a new ROM. The Sprint Note 3 is different from the Verizon Note 3, which is also different from the International Note 3. It's always best to double-check that the ROM you're trying to install is truly meant for your device. This simple check will prevent a LOT of potential issues you'll get when installing a ROM.
Android Version:
This is just an additional check to the Software Version. Always best to know.
Baseband Version:
The Baseband is, unless I'm mistaken, the "kernal" for the phone's cellular and 4G radios. Sometimes upgrading (or downgrading) the Baseband can help with signal strength and reception. Some users have noted that they got better reception on older Baseband versions. I haven't personally looked into it and the reports from other users seem somewhat anecdotal, but it's good to know which Baseband you're on.
The Baseband is independent from the ROM version, so you can run an older Baseband (MJ4 or NAB) on a newer ROM (NC5), and vice-versa.
The last bit of information you need to know is the Bootloader Version. The way to find this information is to reboot your device. When you see the text on the screen, you should look for the Bootloader Version. It'll be a long string of characters, but you're only looking for the last 3 (MJ4, NAB, or NC5).
Once you have all the above information, you should be ready to start the fun process of preparing your phone to flash your first ROM.
Step 2 - Backup your Media
First thing: Backup all of your media to your computer. If there's pictures/music/videos/recordings you don't want to lose, back them up. It's just good practice. Don't lose all your cat pictures because you flashed something and it somehow erased your internal storage. I tend to keep everything of importance on the External Storage, but there are times where even external storage can be wiped, so it's best to back up everything to a PC.
Step 3 - Upgrade your Phone to the latest Stock ROM (NH7)
This only is a MUST applies if you're running an older version and want to install a NH7 ROM. Most continually-developed ROMs are either NC5 or NH7 now, so the first things first: Update your phone to NH7.
Go over to micmar's thread and download the One-Click File. It will remove Root, but don't worry, because when you install a new ROM, it will automatically include root access.
Follow the instructions in his thread and your phone will now be fully upgraded.
At this point, your "About Device" should show the following:
Software Version: N900PVPUCNH7
Android Version: 4.4.4
Baseband Version: N900PVPUCNH7
Reboot your phone and let it sit for a minute so it can get it's bearings.
Step 4 - Install a Custom Recovery
So far, we've been flashing everything in ODIN. Now, we're going to use ODIN one last time to flash a custom recovery, so that you can flash custom ROMs without the need of a computer.
The most-commonly used Custom Recovery is TWRP (XDA Link). You'll want to use the latest version, 2.8.0.
Flash this in ODIN. You should use the "PDA" or the "AP" Slot.
Reboot your phone to make sure it works correctly.
Step 5 - Make a Nandroid Backup of your device
If you don't know what a Nandroid backup is, don't worry. It's basically just taking your phone as is and making a backup of it. In case you make a mistake or flash a bad download of a ROM, this allows you to restore your system. I always keep my backups on the External Storage (microSD Card), so in case I have to wipe my internal storage, it's not a big deal. You can also copy the files over to your PC, just to be more paranoind about your nandroid backups (rhyming is fun!).
You do this by restarting into Recovery (power down device, hold down home button and volume up while powering on phone).
Once in TWRP, go to "backup." Make sure the storage selected is "external storage." This screen will have various options of what to backup. I typically choose everything except external storage. Typically, backups range from 1-2 Gigs.
For me, backups typically take 5-10 minutes to do. In my opinion, this is totally worth it, since I can always restore a backup with no issues.
Step 6 - Install a Custom ROM
Once you choose your custom ROM from the Development Section, follow the instructions on the original post to install it. I'll give a general outline of what I do whenever installing a new ROM, but sometimes a custom ROM will have specific instructions, so you want to make sure to read the posts carefully.
Generic Instructions for Installing a ROM:
Download ROM and check the md5
Internet being spotty in my area, I always check the md5 to make sure that the file downloaded correctly. You can check the md5 using this windows program or using a file explorer on your phone like ES File Explorer. I always copy the ROM zip file to my external SDcard.
Reboot to Recovery
Wipe Data, System, Cache, and Dalvik Cache
This is called a "Clean Wipe," meaning it will wipe out your installed Apps and the data associated with them. Some people will claim that "Dirty Flashing" (i.e. not wiping the above) is OK, but I've seen too many apps Force Closing (FC-ing) when dirty flashing. Also, if you dirty-flash and encounter an issue with a ROM, the first piece of advice is to do a clean install. Might as well do that initially and hopefully not run into any issues.
Install the Custom ROM
Pretty straight-forward on how to do this... just click "Install" and then browse to the place your copied the ROM zip file.
Reboot your phone and run through the typical initial start-up information (google account, etc).
Once you get your phone set up the way you like (apps, accounts, wifi passwords, etc), I'd make another Nandroid backup, just so you have one where it's setup with everything you need. This will make any issues less painful, since you'd restore a backup that's already setup.
Step 7 - Further Considerations
If you ever want to try a new ROM, all you have to do is repeat step 6. Beware, though, people easily become flashaholics when they first figure this stuff out.
If you were paying attention to my "Generic Instructions" when installing a ROM, you'd notice that every time you do a Clean Install of a ROM, you lose all your apps... All of your Angry Birds 3-Star levels are gone!
Well, there are ways to get prevent losing that data... One is by "Dirty Flashing" (Not wiping the "system" or "data" partitions before flashing a ROM in TWRP). This is common practice among users here on XDA, but is typically frowned upon by ROM devs. I've noticed that a good number of issues on ROM threads stem from people Dirty Flashing. It typically causes more problems than it solves.
The other way of backup up and restoring app data (prior to wiping) is by using Titanium Backup. I could write up a long post on how to use Titanium Backup (TiBu), but the main things to remember are the following:
White line items are fine to be restored (both Data and Apps).
Restoring Yellow line items is typically OK (Data only).
Restoring system apps or data (red line items in TiBu) is typically a bad idea.
I've been using TiBu for the past 2-3 years and it's typically worked like a charm. Sometimes, when there's a major Android Update (like from JellyBean to KitKat), it can become broken, but the Developer is really responsive and gets it to work within a few weeks. If you upgrade to PRO, you can schedule automatic app backups (I backup all my user apps every night at 3am). You can also restore apps/data from Nandroid Backups (which is great if you do a Nandroid backup but had forgotten to update your TiBu backups).
In Summary
Whew, that was a lot to write... I'm a Structural Engineer, not a Software Engineer, so I don't know the technical side of things like bootloaders or basebands, but hopefully none of the information I provided was false.
Anyways, let me know if you have any problems with the install. I appreciate any feedback!
Click to expand...
Click to collapse
Since you're looking for AOSP ROMs, I'd recommend looking into this section of the forums. You need to make sure whichever ROM you are looking into works for the Sprint version of the phone (HLTESPR).
Alright so I used the last posts links and upgraded to 4.4.4 but now my data doesn't work