Hello! few days ago I installed the viper rom at&t 1.2.2, so good, but now I want to reinstall it to change some options in the Aroma installer. The question is if I have to re-flash the kernel (boot.img) or while I do not move to another rom this is not necessary?
Thanks!
No you do not, as long as the boot is compatible with your ROM you don't need to change it
Slithered from my HTC One X+
I would just make a backup of everything first because although you don't need to reflash the boot.img if your are upgrading the same custom rom, you can never be too safe.
I upgraded elegancia from 4.2.0 to 4.3.0 without wiping anything and the phone booted and everything started like normal although it seems like something wanted to start up and made my phone super hot - had to start like new and wipe everything. thankfully I had a backup.
Related
Okay, I just rooted my brother's HTC Hero (GSM Unlock) and updated it to 2.1 Villain, but there were some bugs, like in the messages app, the key board wouldn't show up in a conversation. FB Sync wouldn't sync pictures to his contacts. Is there any way I can downgrade back to the original 1.5? If so, can anyone give me a link to download that .zip? thanks!
*note* I tried flashing the official 2.1 update, it failed
And what is a Nandroid backup? Can I restore it with that?
simonlcheng said:
Okay, I just rooted my brother's HTC Hero (GSM Unlock) and updated it to 2.1 Villain, but there were some bugs, like in the messages app, the key board wouldn't show up in a conversation. FB Sync wouldn't sync pictures to his contacts. Is there any way I can downgrade back to the original 1.5? If so, can anyone give me a link to download that .zip? thanks!
*note* I tried flashing the official 2.1 update, it failed
And what is a Nandroid backup? Can I restore it with that?
Click to expand...
Click to collapse
You really should have read up before just rooting and flashing. A nandroid backup is a backup of the phone so you can restore to how it was before you started to play with it.
You can download the rom you require here.
You should have done a Nandroid backup before trying to flash a new ROM, this is a MUST DO everytime you plan on messing around with the phone, it would simply let you restore the backup back to normal.
You need to do a full wipe of the phone and flash the new ROM posted above.
Jamie.
Can I just flash a stock rom of the HTC Hero generic? I flashed a rooted one, but I keep getting this notification about an OTA,I tried installing it, but it fails. If I flash a stock rom (if possible) can I install the OTA's?
I seem to be having somewhat the same problem.
Although I didnt flash my hero to that custom rom you're mentioning.
The problem is that I've been running the modaco 3.0 rom for quite a while and wanted to get the stock 2.1 rom.
I've tried to flash it using the HTC tool but couldn't be done. I accidently overrided my nandroid backup of the stock 1.5 rom so I found a stock 1.5 on modaco's forum and flashed it.
Now I'm running 1.5, build 2.73.405.5
Every time I wipe the phone and start from scratch (setting up the phone as if it was new) I get a notification about a new OTA update. When I try to update it, the phone resets (seems fine) and it ends up in Nandroid and doesn't get any further.
Then I chose to reboot the phone and the phone runs as normal but still no new firmware.
What am I doing wrong?
I've also tried the HTC tool for flashing the ROM but end up with a connection error (170).
I have of course wiped the phone but it doesn't help...
Pinnodyr said:
I seem to be having somewhat the same problem.
Although I didnt flash my hero to that custom rom you're mentioning.
The problem is that I've been running the modaco 3.0 rom for quite a while and wanted to get the stock 2.1 rom.
I've tried to flash it using the HTC tool but couldn't be done. I accidently overrided my nandroid backup of the stock 1.5 rom so I found a stock 1.5 on modaco's forum and flashed it.
Now I'm running 1.5, build 2.73.405.5
Every time I wipe the phone and start from scratch (setting up the phone as if it was new) I get a notification about a new OTA update. When I try to update it, the phone resets (seems fine) and it ends up in Nandroid and doesn't get any further.
Then I chose to reboot the phone and the phone runs as normal but still no new firmware.
What am I doing wrong?
I've also tried the HTC tool for flashing the ROM but end up with a connection error (170).
I have of course wiped the phone but it doesn't help...
Click to expand...
Click to collapse
I have the same problem! And when I do flash 2.1, the keyboard never appears when I go to the messages app. I just flashed an official stock 2.73.405.66 build, what if I do the OTA? Will it fail too? 'Cause I think it fails because last time, my phone was rooted.
Anyone got help? :-/
With all the new/updates to ROMS coming out daily, was thinking about trying a Boot Manager. Are there risks is using an app like that?
My assumption is that it allows users to switch roms w/o have to flash everytime. Please correct if that's wrong.
Thoughts on using a boot manager?
Two things. One make sure you do the backup boot partition every time you change the original phone ROM. Also always keep a nandroid of the original ROM on hand in case you lose access to anything but recovery and fastboot because of a bad flash. In that case you would just restore the boot partition and everything would be peachy keen. Also phone ROM refers to the the ROM you flashed in recovery rather than boot manager.
Sent from my tin can using a string.
I ran Boot Manager briefly with each of Nils' ROMs (his Sense 3.6 and his early Sense 4.0). The previous poster is completely accurate with the warnings listed. One other point, if you rely extensively upon Exchange, every time you switch ROMs you'll need to competely resync all your Exchange data from scratch. That's why I ultimately just picked one ROM and stick with it.
I bought the app when it came out but never used it. I thought I would give it a try too. Now that I am s-off, is the install procedure pretty much the same? For example:
Phone rom I have conromv6
rom1 I have ViperRez.
bond32 said:
I bought the app when it came out but never used it. I thought I would give it a try too. Now that I am s-off, is the install procedure pretty much the same? For example:
Phone rom I have conromv6
rom1 I have ViperRez.
Click to expand...
Click to collapse
The key thing to remember is that the install is different if you are going to use a ROM that installs via AROMA. If the "primary ROM" (the one BM calls your "PhoneROM"), you can install via Aroma, then download and install BM, and set up the ROM as your PhoneROM.
If it's in any other slot than slot0 (PhoneROM), then:
1. Do a Nandroid of your PhoneROM with BM installed and your PhoneROM properly installed.
2. Wipe and flash your Slot1 ROM via Aroma, download and install BUT DO NOT SETUP BM. Nandroid that ROM.
3. Wipe, restore the Nandroid of your PhoneROM, go into BM and install the NANDROID of your Slot1 ROM.
In other words, trying to install a ROM in BM within another ROM via Aroma will not work.
I've got a Galaxy S III and it worked more than perfect before I decided to get the JB update in Kies. Now the physical buttons happen to freeze all the time (the phone itself works), if the screen is on, I can touch everything, apps work, but back/home/menu/screen off don't. It's terribly frustrating to have such an expensive phone and having such an experience with it.
Anyway, I flashed from Sammobile every possible stock ICS and all of them get me stuck in the splash screen as if it's soft bricked, and ALL the stock JBs have the same button problem. Now I thought to myself the only way to go is CM.
The question is: how to I install CM (9, 10 whichever!) over my JB? Or better still (although I gave up on it) how do I get back to the good old flawless stock ICS?
Thank you in advance!
It's basic. Install a recovery, then grab your desired Rom (cm10 or whatever) then backup your apps with Titanium, and reboot in recovery, wipe all partitions (data, cache, dalvick, system) then flash your room, bit and restore your apps.
I did just that, but I get error status 7 when flashing with every version of CM10 i downloaded. When I googled the error I saw it has to do with the kernel not matching the ROM or something...
Strange as kernel provided with Rom is designedto work with. What version of cwm are you using? Try with twrp recovery.
I noticed I didn't have the last version of CWM so I installed it but got the same error. Then I tried TWRP and it worked like a charm! I especially like the touch version. Thanks a lot for your advice, help and everything!
SO here is the deal... I am a complete an total rooting noob but i need some help. After unlocking the bootloader with the help of Hansoons2000 tool and then flashing the phone and then pushing SuperSu to the phone i installed super su and that is where my issues began. After installing SUperSu i got stuck on the Quietly Brilliant screen on my first boot i heard this could take a while so i waited about an hour. Thats when i realized I had a problem. Heres a list of all the steps i attempted so far but to no avail..
I went into recovery and did a factory reset and cleared the cache.. Didnt work
I also relocked the phone and unlocked assuming it would wipe it that did not work.
ANy help to save my phone would be greatly appreciated. I am a first time rooter and have been stressing about my phone all day thinking i threw 700 dollars down the Drain. Any help would be greatly appreciated. And i may ask some stuid question because i am a noob. Thanks in Advance!
By the way it is an Att One X+ that i got about 3 weeks ago if that helps
which recovery you have?
you need a custom recovery for rooting
Install the TWRP Recovery if you haven't already. Do it through terminal. Then, go install a custom Rom (I suggest Viper XL+). Make sure you wipe everything your supposed to. You can do this with the installation of. Venom, it is the AROMA Installer. Flash the boot.img through terminal to. Everything should be fine and it will be rooted.
»»»Correct me if I'm wrong.
Sent from my HTC One X+
This might mean that you would need to reinstall a new rom. Now what you can do to avoid the whole fast boot terminal stuff you can try locking the bootloader and running the ruu for the at&t hox+. What that does is it wipes everything and brings the phone back to stock (stock rom, stock recovery)
After the install goes through you can re unlock the bootloader and install a custom recovery (I have an at&t hox+ and use CWM) and flash a new rom (I use desensed stock look Elegancia ROM)
I like doing the ruu method because I like having a clean slate if something went wrong.
Sent from my HTC One X+ using xda premium
Thanks
I got my phone working again and all set up using th ATT ruu so now i wondering how to make a good backup for my phone and go at rooting it again! thanks
albert1854 said:
I got my phone working again and all set up using th ATT ruu so now i wondering how to make a good backup for my phone and go at rooting it again! thanks
Click to expand...
Click to collapse
Gald you got it working again! I had to find out myself how to fix my phone when similar stuff happened to me too, now I am able to flash my phone properly with different roms. It's almost like an addiction .
now on topic, the one method i do use for backup is I use the CWM backup method, because it says your apps and your systems settings etc all in one folder and when you finish installing your new rom you can use the CWM recovery to restore the backup of your phone. CWM will restore your information and apps as well as the screens and where the icons were at in the home screens. Pretty cool I'd have to say
Now as a backup to the backup I keep my text messages call logs MMS alarms near and dear to me so I use My Backup Pro, keeps a backup online on their servers and can restore them without a prob (although I do find it annoying when it saves information when you sync facebook to the contacts. i have about 200 contacts on my phone and somehow it backs up 700 contact information?)
The tool I used to unlock my bootloader, root my phone, and install CWM (Clockworkmod Recovery) is here
pretty self explanatory and easy and has not failed me
Any questions feel free to ask
same
That the same program unused the first time that bricked my phone after installing super su so do I need to install supersu or are there any alternatives? Thanks for all your help.
Hi, first the details
S-Off via dirtyracun
HBoot 1.19.2222
Radio 1.12.11.1210
TWRP 2.4.4.0
Latest Viper ROM
Weird issues I have;
-Can not install any ROM other than Viper.
-Can not perform backup, it creates a backup successfully and while still in recovery you can locate the backup file, but if the card is pulled out or the phone is booted, the file disappears.
-ROM feels buggy and laggy recently (I'm pushing power right now & it takes the phone about 30 seconds to wake up) this is the most annoying issue and it's becoming consistent.
-Images taken with phone camera are all corrupt files afterwards and can not be viewed.
The phone worked PERFECT with absolutely no flaws after first installing viper when I achieved S-off & rooted the phone. These problems started when I tried to install a different ROM, after multiple failed attempts I gave up & went back to Viper. I checked everything that I know of and have no clue what to do to remedy these issues.
Now the phone works OK with Viper ROM but it's getting annoying that Viper is my only option and it's not even working as smoothly as it first did (even after wiping cache etc.)
I guess I could return the phone back to stock & start all over again but I refuse to since it took too much time unbricking & troubleshooting when I went through dirtyracun's S-Off procedure, I absolutely can not go through that ever again.
Any help would be appreciated :good:
does no one have any ideas? I tried to start over but now I have locked bootloader and the message "tampered" I'm pretty much stuck at this point and not sure what to try to get ROMs to successfully flash. Still rooted & still have Viper ROM running.
oceanisbleu said:
does no one have any ideas? I tried to start over but now I have locked bootloader and the message "tampered" I'm pretty much stuck at this point and not sure what to try to get ROMs to successfully flash. Still rooted & still have Viper ROM running.
Click to expand...
Click to collapse
Haven't been around as much as I use to so I'm behind the times a bit. If you are rooted and S-Off then bootloader should not say locked. Can you fix permissions from recovery? You have root access with SU and are htc dev unlocked? Is the rom zip or backup on sd or sd2? Can you read either when booted with a file explorer?
I went through the htc dev unlock process now bootloader says "Tampered" & "Unlocked" after that I did fix permissions in recovery and flashed sinister V10 successfully BUT I can't flash a Kernel, I tried to flash Arc-Reactor and failed.
Thanks for the help getting another ROM flashed
oceanisbleu said:
I went through the htc dev unlock process now bootloader says "Tampered" & "Unlocked" after that I did fix permissions in recovery and flashed sinister V10 successfully BUT I can't flash a Kernel, I tried to flash Arc-Reactor and failed.
Thanks for the help getting another ROM flashed
Click to expand...
Click to collapse
Have you tried flash booting the kernel boot.img prior to flashing the kernel ?
Sent from my EVO using xda premium
so I tried Bulletproof Kernel and that installed fine...
as far as flash booting the kernel boot.img no I'm not sure how to do that!
What wipe process r u using? I had issues similar to this on my og EVO and it came down to I wasn't fully wiping and getting a dirty install.
I'm having a similar problem. My phone is really, really laggy since I recently moved from MeanRom to Viper. I ran Viper previously with no issues that I can remember. In terms of my phone, I have TWRP 2.5, wiped using TWRP to clear cache, dalvik cache, and data. I didn't wipe system or internal/external sd.
SmallPsych said:
I'm having a similar problem. My phone is really, really laggy since I recently moved from MeanRom to Viper. I ran Viper previously with no issues that I can remember. In terms of my phone, I have TWRP 2.5, wiped using TWRP to clear cache, dalvik cache, and data. I didn't wipe system or internal/external sd.
Click to expand...
Click to collapse
You should always wipe Cache/dalvik cache/data/system going to a different rom so that might be why viper is laggy.
Try a new install using the wipe method above or use the superwipe zip attached below
I usually do a full wipe cache/dalvic/system etc. in TWRP before flashing, I actually managed to flash several different roms and ironically enough I ended up back on Viper, it just seems to have all the tools I like to use and work smoothly enough to keep me happy. It works as smooth as it originally did when I first installed it, I'm not sure what I did that fixed the issue
Though for some reason I still can't flash most kernels, currently I'm using whatever kernel that comes with Viper