Database Info

back up/restore

I have h-boot 1.14 withe twrp recovery, I backed up my phone with a previous rom i had and my question is would I have to install the image again after i restore the phone or should the phone restore without any problems.

cal4877 said:
I have h-boot 1.14 withe twrp recovery, I backed up my phone with a previous rom i had and my question is would I have to install the image again after i restore the phone or should the phone restore without any problems.
Click to expand...
Click to collapse
Most of the time yes you will have to install the boot .img manually coming from a different base or Rom... But say if you're on viper and your back up is the same base sense Rom you probably wouldn't have to reflash it... But if coming from cm10 or anything else yes

a box of kittens said:
Most of the time yes you will have to install the boot .img manually coming from a different base or Rom... But say if you're on viper and your back up is the same base sense Rom you probably wouldn't have to reflash it... But if coming from cm10 or anything else yes
Click to expand...
Click to collapse
Awesome thanks man, also im currently running nocturnals dirty rom I believe this is a AOKP rom, now if i want to flash another AOKP or any other CM10 base rom wouldnt the image be the same? or the i have to flash another image of the rom aswell?

cal4877 said:
Awesome thanks man, also im currently running nocturnals dirty rom I believe this is a AOKP rom, now if i want to flash another AOKP or any other CM10 base rom wouldnt the image be the same? or the i have to flash another image of the rom aswell?
Click to expand...
Click to collapse
Be safe and flash it

Is it necessary to reflash rom before restore or can you just fastboot flash boot.IMG and just restore backup?
Sent from my One X using xda premium

I believe you have to flash boot. IMG and than restore according to the comments up there

I just wish we had to option to downgrade the software/hboot without going thru all those steps listed, I remeber i had the htc inspire and you will be able to downgrade hboot by choosing a downgraded version of Ruuu files.

cal4877 said:
I just wish we had to option to downgrade the software/hboot without going thru all those steps listed, I remeber i had the htc inspire and you will be able to downgrade hboot by choosing a downgraded version of Ruuu files.
Click to expand...
Click to collapse
Yeah I loved the inspire that's what got me into android... But I got my phone on hboot 1.09 I've never done the downgrade process but I heard it can be pretty simple

[Q] Changing Stock kernels

Hi,
I have managed to put on a kernel that's not working. Is there a way to revert back to the original kernel? I do have a nandroid backup, but re-installing that didn't put on the old kernel.
I am using Liquidsmooth ROM. Any help would be appreciated.
Thanks.

if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.

DvineLord said:
if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.
Click to expand...
Click to collapse
I did exactly that, presuming that it was working... But I have been facing issues. The phone restarts every once in a while and I have managed to get to this condition after multiple wipes and restoring a backup. Anyways I don't know what the issue is I was just wondering how to revert back to the original kernel.

im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.

DvineLord said:
im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.
Click to expand...
Click to collapse
I do not have s-off does the flashimagegui works even without it?

strommer666 said:
I do not have s-off does the flashimagegui works even without it?
Click to expand...
Click to collapse
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.

DvineLord said:
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.
Click to expand...
Click to collapse
Thanks I'll make sure I do that..

also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.

DvineLord said:
also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.
Click to expand...
Click to collapse
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.

strommer666 said:
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.
Click to expand...
Click to collapse
you need everything. you don't need to extract the kernel. just load the whole zip file.

DvineLord said:
you need everything. you don't need to extract the kernel. just load the whole zip file.
Click to expand...
Click to collapse
I did load the full file and the flash gui image extracted the kernel. The thing is I have the kernel now, but still I can't seem to be able to install the new version of the LiquidSmooth build. I am doing a nandroid backup of this thing and try installing it again.

well new liquidsmooth is nice, im using cwm now as recovery since ive had tons of issues with twrp since version 2.2.2.0

[Q] Installing the updated kernel and firmware for CM

Hey,
right now I'm on CM 10.1 (2013 03 12 nightly) and I want to update to the latest CM 10.2 nightly.
However after flashing the nightly I get a bootloop. I found out that CM started using a new kernel which I have to update first. And in order to do so, I need to update the firmware as well. http://forum.xda-developers.com/showthread.php?t=2322755
It says that the new firmware is 2.15.0000. But when I enter the bootloader it displays that I am already on 2.15.0000:
http://abload.de/img/img_68993jl4l.jpg
Note: I haven't updated the firmware or anything yet. But it appears that I'm already on the new firmware, right?
But then: why am I getting bootloops when flashing the new nightles? Do I have to flash the new kernel manually in fastboot? Or does TWRP does it all by itself? Do you think I can try flashing the kernel because HBOOT is 2.15.0000 or do I have to do the tutorial?
Sorry, I'm kind of new to this whole flashing thing, so pleas be patient with me..
Oh btw: the model is ville
Thank you guys.
//Oh I just remember that I did the htc sense jb update when it came out _before_ flashing CM. And that jb update should include the new firmware right? So I can just proceed with flashing the new kernel in fastboot?

Your hboot is fine for the ROM. You're S-On so you need to flash boot.img after flashing the ROM. That's your problem.
Sent from my One S using xda app-developers app

abracadabra11 said:
Your hboot is fine for the ROM. You're S-On so you need to flash boot.img after flashing the ROM. That's your problem.
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Okay, I just did that and it seems to work.
There were some problems with the CM account and a lot of crashes but after that it seems to work just fine.
Thank you

[Q] Noob - Help on Sense 5 by Turge

Since I can't post on the original android development thread. I'll ask here.
I'm a noob on all of these rooting and custom roming however I did manage to unlock my bootloader, flash TWRP 2.6.0.0, have root access via Superuser, S-OFF and finally flash Android 4.2.2 Sense 5-5.08.111.2 stock ROM by Turge on my ATT device running JB 3.18 (HBOOT 2.14).
I love the stock rom however I'm having problems such as signal drops throughout the day, random reboots and no signal when I wake up everyday for the past 3 days.
I know the solution is to flash Kernel and update firmware - which is explicitly stated on Turge's thread, which leads me to my questions:
1) What does firmware updating do to my device? I'm pretty clear on what happens when you flash Kernel.
2) Assuming I was able to update firmware (including HBOOT to 2.15?) and Kernel, Would I still be able to revert back before messing with them? Would creating a nandroid backup before updating and restoring that nandroid backup be able to revert them back pre update w/o issues (or bricking)?
3) Lastly, I made an original nandroid backup while still Android 3.18 w/ Sense 4 (my very first nandroid backup) before flashing Sense 5. Assuming I updated firmware and Kernel while on Sense 5, Would restoring the original nandroid backup allow me to restore back to Sense 4 w/o issues (or bricking)?
Hope someone would take time to respond! Thanks!

+1 i have same questions

You might get more responses if this was in the question thread. Mod please move this to the correct area.
Sent from my HTC One XL using xda premium

watswidme said:
Since I can't post on the original android development thread. I'll ask here.
I'm a noob on all of these rooting and custom roming however I did manage to unlock my bootloader, flash TWRP 2.6.0.0, have root access via Superuser, S-OFF and finally flash Android 4.2.2 Sense 5-5.08.111.2 stock ROM by Turge on my ATT device running JB 3.18 (HBOOT 2.14).
I love the stock rom however I'm having problems such as signal drops throughout the day, random reboots and no signal when I wake up everyday for the past 3 days.
I know the solution is to flash Kernel and update firmware - which is explicitly stated on Turge's thread, which leads me to my questions:
1) What does firmware updating do to my device? I'm pretty clear on what happens when you flash Kernel.
2) Assuming I was able to update firmware (including HBOOT to 2.15?) and Kernel, Would I still be able to revert back before messing with them? Would creating a nandroid backup before updating and restoring that nandroid backup be able to revert them back pre update w/o issues (or bricking)?
3) Lastly, I made an original nandroid backup while still Android 3.18 w/ Sense 4 (my very first nandroid backup) before flashing Sense 5. Assuming I updated firmware and Kernel while on Sense 5, Would restoring the original nandroid backup allow me to restore back to Sense 4 w/o issues (or bricking)?
Hope someone would take time to respond! Thanks!
Click to expand...
Click to collapse
1. The firmware update will update the hboot, radio, and some WiFi and media modules.
2. You can revert using the 3.18 RUU, this will return you to the 2.14 hboot, stock recovery, and stock Sense 4 ROM.
2b. A nandroid backup doesn't backup the partition that is updated by a firmware package. It only backs up the OS/data/boot partitions, so restoring a backup won't change your firmware, use the RUU as suggested above if you need to revert.
3. Restoring your backup will return you to the Sense 4 ROM. Like I mentioned above though it will not change your firmware.
You are s-off so the chance of bricking while running an RUU is minimal. There is always a small chance of bricking no matter what you're doing, whether it be flashing a ROM/kernel, changing hboot (higher risk), flashing a radio, running an RUU. With your current setup, you have no greater risk than anyone else though.
PS. Questions go in the q&a section (for future reference).
Sent from my Evita

I had the same exact issue. I did the easiest thing first - flashed the Beastmode 3.5 kernel, and thankfully that has completely fixed the issues for me. Been running with it for 4 days now and the signal has not dropped once nor have I had random reboots. I did not have to upgrade firmware.
Just a personal note... the stock settings flash did not work for me; I had to choose the custom flash and enter the stock settings. He mentions this in the install notes.
Here's the Beastmode 3.5 thread:
http://forum.xda-developers.com/showthread.php?t=2165880
Here's his post with what the stock settings should be if you need to choose the custom flash:
http://forum.xda-developers.com/showpost.php?p=45195808&postcount=251

timmaaa said:
2. You can revert using the 3.18 RUU, this will return you to the 2.14 hboot, stock recovery, and stock Sense 4 ROM.
Click to expand...
Click to collapse
This^ I was gonna ask about it in Q&A thank goodness I read this thread first. Thank you!
Sent from my HTC One X using Tapatalk 4

Timmaa - Great stuff buddy! One additional question, It sounds like I can restore my backup (made on 2.14) while my firmware is 2.15? Wouldn't this cause any trouble?
rwalterk - I will err on the side of safety and flash my Kernel first, like how you did it. My phones getting more reboots and dead signals after a week of use. If problems still continue I will update my firmware.
pjacanales - noted, questions on the questions thread.

watswidme said:
Timmaa - Great stuff buddy! One additional question, It sounds like I can restore my backup (made on 2.14) while my firmware is 2.15? Wouldn't this cause any trouble?
rwalterk - I will err on the side of safety and flash my Kernel first, like how you did it. My phones getting more reboots and dead signals after a week of use. If problems still continue I will update my firmware.
pjacanales - noted, questions on the questions thread.
Click to expand...
Click to collapse
I can't see any reason why reverting to Sense 4 wouldn't be ok on the newer firmware.
Sent from my Evita

Newbie Question.
rwalterk said:
I had the same exact issue. I did the easiest thing first - flashed the Beastmode 3.5 kernel, and thankfully that has completely fixed the issues for me. Been running with it for 4 days now and the signal has not dropped once nor have I had random reboots. I did not have to upgrade firmware.
Just a personal note... the stock settings flash did not work for me; I had to choose the custom flash and enter the stock settings. He mentions this in the install notes.
Here's the Beastmode 3.5 thread:
http://forum.xda-developers.com/showthread.php?t=2165880
Here's his post with what the stock settings should be if you need to choose the custom flash:
http://forum.xda-developers.com/showpost.php?p=45195808&postcount=251
Click to expand...
Click to collapse
Hey bro
I'm from Venezuela and I'm having the exact same problem as you guys have.
I readed your post and downloaded Beastmode 3.5 and flash it, but i got caught in a bootloop.
I'm using the VIPER 4.2.2 Rom.
Since this is not a solution for me, i was wondering which Rom are you using exactly?

Did you select custom from the Beastmode installer? He's using Turge's stock Sense 5 ROM which can be found in the development section.
Sent from my Evita

rwalterk said:
I had the same exact issue. I did the easiest thing first - flashed the Beastmode 3.5 kernel, and thankfully that has completely fixed the issues for me. Been running with it for 4 days now and the signal has not dropped once nor have I had random reboots. I did not have to upgrade firmware.
Just a personal note... the stock settings flash did not work for me; I had to choose the custom flash and enter the stock settings. He mentions this in the install notes.
Here's the Beastmode 3.5 thread:
http://forum.xda-developers.com/showthread.php?t=2165880
Here's his post with what the stock settings should be if you need to choose the custom flash:
http://forum.xda-developers.com/showpost.php?p=45195808&postcount=251
Click to expand...
Click to collapse
timmaaa said:
Did you select custom from the Beastmode installer? He's using Turge's stock Sense 5 ROM which can be found in the development section.
Sent from my Evita
Click to expand...
Click to collapse
Thank you my friend!
I downloaded Turge's ROM and install it, and actually didnt have to flash the New kernel; i used the one in the Package and it Worked! i almost sold my phone because i couldnt find a ROm taht works but, so far, its been passed one day only and i havent had any signal drop, nor battery fast draining!
Sorry for my english BTW.
Thank you once again!
PS: If u find a way to fix VIPER ROM let me know, cause i've read a lot and cant find a way to fix it, but im to shy to ask in a new post hahahahahhahahahahahahaha.
Let me know if you need my phone specs. (as bootloader version, software version etc.)

The best way to overcome the problems is to get s-off, then you're able to upgrade to the 2.15 firmware which is the best solution to signal loss and reboots on Sense 5 ROMs. In order to get s-off you'd most likely need to flash a different ROM though, I don't think a single person has had the process succeed while running a 4.2.2 ROM.
Sent from my Evita

timmaaa said:
The best way to overcome the problems is to get s-off, then you're able to upgrade to the 2.15 firmware which is the best solution to signal loss and reboots on Sense 5 ROMs. In order to get s-off you'd most likely need to flash a different ROM though, I don't think a single person has had the process succeed while running a 4.2.2 ROM.
Sent from my Evita
Click to expand...
Click to collapse
Yeah, i'm already S-OFF.
Actually, all this problems came out when i was 1.14 FW, but when i checked for the first time this post, i decided to change the FW and now i'm @ 2.15 FW, S-OFF and CID-11111111.
I haven't checked what is gonna happen if i install VIPER ROM, but in the meanwhile, i'm gonna try this ROM which runs smooth.

[Q] Sense v6 Radio Installer; Status 7 error - fix/insight?

Hey all,
Currently trying to change my baseband version from 1.11 to WWE 1.15 on my CM11 S-OFF HTC Ville. Using Tecardo's Sense v6 installer and flashing it as instructed via PhilZ CWM recovery.
The aroma installer fires up and I select Europe>WWE 1.15>Wi-Fi fix>US build.prop edits. However, it's at this point that I get the status 7 error.
I'm well aware that I'll need to do something along the lines of browsing into meta-inf/com/google/android & extracting the updater-script but I do not know how much code (and semi-colons) I need to delete to resolve this error and ALSO not introduce new ones in the process eg. status 6 errors!
Any advice would be appreciated.
Cheers.

hellom0to said:
Hey all,
Currently trying to change my baseband version from 1.11 to WWE 1.15 on my CM11 S-OFF HTC Ville. Using Tecardo's Sense v6 installer and flashing it as instructed via PhilZ CWM recovery.
The aroma installer fires up and I select Europe>WWE 1.15>Wi-Fi fix>US build.prop edits. However, it's at this point that I get the status 7 error.
I'm well aware that I'll need to do something along the lines of browsing into meta-inf/com/google/android & extracting the updater-script but I do not know how much code (and semi-colons) I need to delete to resolve this error and ALSO not introduce new ones in the process eg. status 6 errors!
Any advice would be appreciated.
Cheers.
Click to expand...
Click to collapse
Use TWRP recovery instead (latest 2.7 should be fine). I've flashed it several times without issues. Don't know why it happens on CWM

Rapier said:
Use TWRP recovery instead (latest 2.7 should be fine). I've flashed it several times without issues. Don't know why it happens on CWM
Click to expand...
Click to collapse
Thanks for the info.
Just a quick query: is TWRP 2.7 compatible with flashing CM11 (nightlies)?
Used to rely on TWRP on ICS/JB prior to moving onto CM11. I then switched to PhilZ's CMW because CM11 could not be flashed using TWRP.....this might have been due to it being an older version but I cannot be sure.
Clarification please?

hellom0to said:
Thanks for the info.
Just a quick query: is TWRP 2.7 compatible with flashing CM11 (nightlies)?
Used to rely on TWRP on ICS/JB prior to moving onto CM11. I then switched to PhilZ's CMW because CM11 could not be flashed using TWRP.....this might have been due to it being an older version but I cannot be sure.
Clarification please?
Click to expand...
Click to collapse
Yes, latest TWRP has full SELinux support. This was the isuue with older versions. I use it and have no problems flashing any KK ROM
Sent from nowhere over the air...

I'm obviously doing something wrong because having switched to TWRP 2.7, the radio installer managed to complete success fully albeit at the cost of somehow wiping the CM11 ROM from my ville. I could only enter recovery and the phone black-screens after the HTC screen.
I recovered by wiping system, data, cache and dalvik and flashing stock JB RUU to boot up the phone properly then installed CM11.
Just wondering how people are managing to switch basebands and I can't :/
FYI to recap: trying to switch from 1.11 to WWE 1.15 using Europe>WWE 1.15>WiFi fix>US build.prop edits as my settings in the installer. Tecardo suggests using the build.prop edits if switching to 1.15 which is why I am selecting it.
Any advice/suggestions welcome, please.
Thanks

hellom0to said:
I'm obviously doing something wrong because having switched to TWRP 2.7, the radio installer managed to complete success fully albeit at the cost of somehow wiping the CM11 ROM from my ville. I could only enter recovery and the phone black-screens after the HTC screen.
I recovered by wiping system, data, cache and dalvik and flashing stock JB RUU to boot up the phone properly then installed CM11.
Just wondering how people are managing to switch basebands and I can't :/
FYI to recap: trying to switch from 1.11 to WWE 1.15 using Europe>WWE 1.15>WiFi fix>US build.prop edits as my settings in the installer. Tecardo suggests using the build.prop edits if switching to 1.15 which is why I am selecting it.
Any advice/suggestions welcome, please.
Thanks
Click to expand...
Click to collapse
You still having problems with this? I was just flashing the same radio you want, including the WiFi fix but without the US build.prop edits since I'm in Europe not US. Could you try the same? The build.prop edits can be made manually later directly on the installed ROM, the important thing is to have first the radio installed.
To recap:
- have TWRP 2.7.0 installed and working
- flash the Sense radio installer V6
- chose in aroma installer: EUROPE, 1.15 WWE, WiFi fix
Then we'll see about the build.prop edits

Appreciate the advice but I opted to flash to bilal's 1.35 radio from the One XL along with updated WCNSS and ADSP partitions in the meantime. Can happily report that my data connection is a lot better, especially during my commute to work. WiFi seems just as good as it was, prior to the new partition being flashed and call quality seems good too.