Develop Bugs

[Q] Nonstop rebooting, even after full wipe/reinstall - last_kmsg inside

Hey everyone.
I know there's a couple other threads with this problem, but none of them included their last_kmsg files. It took a bunch of tries before I could stay booted up long enough to grab it, but I have one.
I'm getting a significant number of reboots on my EVO. Like almost unusable at times. It seems fairly random, although there's a slight suspicion is has something to do with the GPS. Maps has been a crash-cause before and the most recent bout last night was brought on by foursquare. (the annoying part is I had just used 4sq fine 30 minutes prior with no issues. Then, booted it up, refreshed locations and my phone was unusable for hours.)
I've done all the standard things. Fix permissions, wipe cache, wipe dalvik, wipe data/system, reinstall the latest CM7 build (update-cm-7.0.2.1-Supersonic-signed.zip), wipe cache, wipe dalvik. I entered my google account info but told it not to sync anything. It is now rebooting less than a minute after it starts up. I haven't installed any apps at all since this most recent wipe/reload of CM7. It reboots with and without the sd card installed.
I'm at a loss here and getting incredibly frustrated. Many replies say it's as easy to fix as wipe everything and re-do it. Obviously something abnormal is screwed up on my phone and I can't figure it out.
Here's the pastebin from this morning: pastebin.com/Ki7H8bH3 (Crap, I don't post here enough to be allowed to post links. Just add the http part to that.)
And then when I got awake enough, I did another complete wipe/reload. The rebooting is even worse now, it's taken me almost an hour to get to a point I can install es explorer to try and pull another file. And when I did, it was blank.
Any ideas?
Thanks!

1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.

Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!

grifta67 said:
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
Click to expand...
Click to collapse
You're very welcome. Sorry for the delayed response. I was having a late lunch and then drove home. Anyway, keep us informed of your progress and enjoy the rest of your day.
posting & replying via the XDA Premium app.

No worried on any delay, just glad to have someone that took a read and time to reply!
Ugh, it's the randomness of this that has me so frustrated. I thought I had a good install again, I left it sit on the "touch the android" screen for a few minutes and it stayed on. Made it through the setup process ok. I allowed the setup to "auto-download" a handful of the google apps it asks if you want. Once they got to about 38%... boom, restart.
So I did another toooootal wipe and I'll manually install those apps one by one. We'll see...

dougjamal said:
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Seems like this gets posted quite often, huh??? lol

Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.

HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
Indeed, my friend...lol...but it works.
posting & replying via the XDA Premium app.

HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
It does and it wish it was that easy. It's frustrating to read that others seem to have no issues at all yet when I follow those directions, which are everywhere, nothing seems to work.

dougjamal said:
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I re-downloaded CM7 this morning thinking that might be the issue, but it hasn't seemed to help. I'll give a different rom a try probably, maybe there's something other than CM7 I'd be content with.

Whelp, I downloaded SalvageMod and their gapps. Wiped everything, installed salvage, installed gapps, rebooted.
I got through set-up, was ok for a couple minutes, then as I was going into my contacts to see if they had sync'd yet... reboot.
This makes me think this can't be a ROM issue.
Any other ideas?

Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.

jesuspgt said:
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
Click to expand...
Click to collapse
Hey jesuspgt,
I haven't tried that yet. I'll look around for a rooted stock ROM later and give that a shot.
My current status is back to uncertainty. At the moment, my evo has been sitting here fine, not rebooting, for the past hour or two. It's still the Salvage ROM I first installed (i.e. I haven't reinstalled it since it rebooted). Now I haven't really used it any, so it might go to hell as soon as I do that, but for now, it's on and only had that one (maybe two, I can't keep track...) initial reboot.
That's what makes it tricky to diagnose. I know using any custom ROM runs the risk of loosing stability and all ROMs probably produce a reboot here and there. Tough to tell if it's just a "comes with the territory" type of reboot or an actual problem.
Even though I'm sure there's some CM features I'll miss, maybe Salvage is my answer.
Thanks!

*sigh* Well I decided to try using some apps and guess what... reboot.
All I was doing was trying to play a game of Androminion, which is about as basic and not-tasking as possible, so I can't imagine that's what crashed things.

The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.

dougjamal said:
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Excellent, I'm going to try that. My hboot is still 0.93!

Hey dougjamal,
Just wanted to drop an update. I know how annoying it is to help someone out and never hear how things ended up!
Who knows what combo helped, but I'm fairly stable now. After updating my hboot, I flashed to Sprint Lovers, did the ##GPSCLRX# trick and then flashed to the latest nightly of CM7 (63 I believe). Only one or two crashes and one bootloop since then.
Of course, as luck would have it, a new problem showed up in the form of a dead spot on my touch screen. Right about where the "Clear" button is for notifications, that entire strip across the phone won't respond to touch. I was hoping it was a nightly issue, but I switched to a different rom and the issue was still there. Looks like it's going in for a warranty claim after-all!
Thanks for all your help
-grifta67

[Q] hensemod problem

Hello,
I've installed Hensemod a few times now, without any problems the first time I boot the phone.
Only after that, when restarting or turning the phone on again, it takes very long to start, like it's installing again and then the internal memory is suddenly full, even though I had about 100mb when turning the phone off. Also, all apps I installed are gone. In the applications list (in settings) they seem to still be there, but they're all 0kb and there's no shortcuts to them in the programs overview... Like I said, I've installed the Hensemod a few times now, and every time this happens.
Anyone knows how to solve this? I really like this rom, I can finally install and update all apps I want without the phone becoming unusable because of full internal memory! Thanks!
Carolien

I used HenseModv3 is a nice ROM, u must have to wipe all the data, cache and dalvick cache in the CWM recovery section, then install the HenseMod ROM.
If any other problem, plz share.

I followed all the steps stated in the development forum post, it works fine, just cant restart the phone because it will stop working...

My phone just continuesly restart...

Plug off ur battery, then go to CWM recovery, try to intall any other/different ROM.
I install each ROM by above method,i didn't use fastboot uncheck option.

Never mind I was just being stupid... I wiped the cache partition and not the dalvik cache. Sorry about that! Let's see if it will work now. Installing rom at the moment.

And again... first boot worked fine, after that I'm stuck in a bootloop now... Just like couldzxz. Too bad! I'll have to try yet another mod. Hope the next update of hensemod will solve this!

yes, u can try different custom ROM if any problems with a particular ROM
wait for next updates from Henry_01

I got stuck in bootloop too. I reqlly like the rom but well.. :/
Sent from my HTC Wildfire S A510e using xda premium

Okay, i've seen your problems.
I've tested latest build, but didnt rebooted it.
I suggest you all use a previous version (3).
Problem can be also kernel related.
I don't have time now (exams), I will make a proper working build after some weeks.
Don't hesitate to post here further, I want to know if it is ROM or phone related.
BIG EDIT: i will include link for version 3.
Thanks to djpc for a new hack which will solve reboot/kernel/overclock problems.
Expect a build and a proper test on friday or saterday.
I will change links now so that you will get a good version lol.

Somehow, the fifth time in installed the latest Hensemod rom, it worked like a charm. I can reboot, have installed and updated all apps I wanted and still got like 90mb remaining. Fantastic! Finally after 6 months I have the phone I wanted.
First and second install I couldn't reboot
Third install I got stuck in a bootloop
Fourth install gapps crashed every 2 seconds (due to calendar and contacts synchronization)
Fifth install = perfect!
I don't know how it happened, I just kept on installing this one so I could copy another rom on the sd card since I don't have an adapter or card reader for it.
Thanks!

A simple root ruined my day

Hello XDA-Forum
As of today this is my first day and post here.
As a noob ( I watched the video on reg, i found it funny yet noobfriendly D: ) i would like to ask some questions that the all-mighty search button could not find me, or atleast i could not find
I whacked my head all day searching for a way to root my HTC Wildfire S a520e running on 2.3.3 stock marvel s-off phone
and after by mistake factory reseting it, twice....
I finally managed to root it with OneClickRoot or something.
Then i tried to to what i originaly wanted to root for, Overclock.
But after downloading the rom i got from a youtube video, it f**ked me up good.
Now my phone is overclocked, but is slower. and the menu's are all glitchy and white and wrong.
I would like to ask how to return to the stock rom of 2.3.3 that i so much desire.
Meanwhile while i await your answears of joy, i am downloading Cyanogen 7.2 Rom that i found on the interwebs and should so-fit my tiddy little wildfire s.
Toodles.

I installed Cyanogen... and .... well i don't like it (Q_Q)!
i want my old 2.3.3 back (cry)
It feels slower, i don't like the UI
EDIT:
Now that i look at it again.. it's not that bad qq
but where's the android market/google play ?

You need to flash Google apps package from clockwork mod recovery:http://cmw.22aaf3.com/gapps/gapps-gb-20110828-signed.zip for market to work.
If you want to go back to stock, download a ruu installer for your region eg euro, Asia etc from here:http://forum.xda-developers.com/showthread.php?t=1074445
Install from a windows pc

As un-adaptable to new stuff i am and as much i hate change.
I find this cyano-genic blue colour to be semi attractive.
and i decided i'll keep it.
I read that cyanogen has built in overclocking.
Where can i see the hardware? i try'd in about settings but it doesn't say there.

For overclocking go:
Settings
Cyanogenmod
Performance
Cpu

I find this slightly more complicated than the normal android sense, but herpyderpderp atleast i'll be the only one in my class with a custom rom 8D
All the others are iOS/IceCreamSandwich richbishes D:
Is there something Cyanogen can't do that the original android stock can do?

intel007 said:
You need to flash Google apps package from clockwork mod recovery:http://cmw.22aaf3.com/gapps/gapps-gb-20110828-signed.zip for market to work.
If you want to go back to stock, download a ruu installer for your region eg euro, Asia etc from here:http://forum.xda-developers.com/showthread.php?t=1074445
Install from a windows pc
Click to expand...
Click to collapse
Nevermind, worked D: I'm a potato.
I know i ask a lot of questions but i'm stuck at "Touch the android" after i flashed this thing
i touch the android and nothing happens... this happens on boot

I find myself in a position where i cannot procceed, this "touch the android" is stopping me ._.
hawp...

You might need to reflash.
Clear your data and dalvik in cwm
Flash cm7 latest nightly
Flash gapps
On first start take your time DONT press the android right away.
Give all background apps and SD time to load, maybe 30-60 seconds then press it and continue setup.
I have had that issue in the past.
Hope it helps you.
CM7 is a great rom, so customisable enjoy and make it your own.

intel007 said:
You might need to reflash.
Clear your data and dalvik in cwm
Flash cm7 latest nightly
Flash gapps
On first start take your time DONT press the android right away.
Give all background apps and SD time to load, maybe 30-60 seconds then press it and continue setup.
I have had that issue in the past.
Hope it helps you.
CM7 is a great rom, so customisable enjoy and make it your own.
Click to expand...
Click to collapse
I factory reseted.. i hate having to do that.....
it got stuck at cyanogen 7 loading boot, will this happen again if i use the thing you gave me for android?
damN! factory reset didn't fix it, how do i reflash when i deleted the file from the SDCard? now i can't put it back on the SDcard
EDIT: I got the file on again, but this software is way too fragile...

http://pockethacks.com/htc-wildfire-s-custom-rom-android-2-3-3-gingerbread/
Is that older or new'r ?
And can i get THAT interface on my now installed rom?
EDIT:
Stuck at HTC, still wown't load after re-flash

Did you wipe data and dalvik?
Its important you do!

Use this cm7, latest nightly build http://cm7-wildfire-s.googlecode.com/files/update-cm-7.2.0-RC1-marvel-03_29_2012.zip

I'm thinking of getting this http://code.google.com/p/cm9-wildfi...rc0-unofficial_rom-alpha0-signed.zip&can=2&q=
So far so good, it has minor problems i don't like
but what can i do -sigh-
there's an option called "Data Enable"
Does that take like money or anything?
also how can i use Voice Speech in this rom?
i wanna be able to talk on skype and it turns out as text

just as a question, could there be a problem during the installation, becouse the clock on the start seems to not be visible, it said some kind of error and i removed it from the screen. also it has 90mb free now
feels like first time i installed it it had like 110

THe clock on the lockscreen? You probably changed a setting. Or a clock widget? You probably deleted it. Just hold on the home screen and re add it form there.

bingzz said:
THe clock on the lockscreen? You probably changed a setting. Or a clock widget? You probably deleted it. Just hold on the home screen and re add it form there.
Click to expand...
Click to collapse
Yes that worked, it wasn't deleted i guess.
I pretty much set up my phone overnight. (now my body hurts from exhausture)
I'm still haveing problems setting things up like voice to text on skype and other stuff.
Overclocking crashes my phone a lot. I know that happens but it happens like every 20 mins or something.
Also can i UPDATE from 7 to 9 without having to start over.
just update?
UPDATE: Also, i loose some files from sdcard (games installed) when it crashes when overclocked sometimes.

What the... i restarted my phone and all the stuff on SDCard is deinstalled, gone D:
EDIT: It came back after 5 mins

EEK!
I was putting some stuff on my SDCard when suddenly i open proccess list and on SC card it says No applications, 1.4 used, 431free but nothing QQ Hawp
all my icons are now with the android pic on them D: helppp
I'm starting to hate this already D:
Also my google play went back to market

If you want to downgrade to 2.3.3, check this tutorial
http://forum.xda-developers.com/showthread.php?t=1540952

[Q] Unusual problem installing Jellytime R16

I have just flashed Jellytime R16 to my DHD but have a slightly damaged touch screen. Unfortunately the part of the touch screen that doesn't work is the bit where you have to press the start button to move off the screen where you select the language on first boot up.
Does anyone have any ideas how I could skip the first configuration screen of the Jellytime R16 ROM?

I don't think it's permanent maybe a bad zip? Did you check MD5 checksum before you flash? And did you full wipe?

Sorry, I don't think I made myself clear. I do have a damaged touch screen nothing to do with the rom. There is a section of the touch screen that just doesn't work. It is this part that sits exactly where the start button is. It is a shame these start screens don't rotate or the start button was slightly bigger.
So if I could skip this fisr language selection screen I would probably be ok for using the rest of the rom.

I had quite a bit of trouble earlier today installing R16 due to the screen not working at all after the bootup. Had to pull the battery 2 times in a row and make sure the charger was unplugged before the screen would react to touch. Maybe you're also experiencing this thing (several others are reporting it in the JT thread).

foxx1337 said:
I had quite a bit of trouble earlier today installing R16 due to the screen not working at all after the bootup. Had to pull the battery 2 times in a row and make sure the charger was unplugged before the screen would react to touch. Maybe you're also experiencing this thing (several others are reporting it in the JT thread).
Click to expand...
Click to collapse
As I said in my last post this is not a Rom problem I do have a damaged touch screen. I Just need a way of getting past the first setup screen or rotating th screen.

Skunkworx said:
As I said in my last post this is not a Rom problem I do have a damaged touch screen. I Just need a way of getting past the first setup screen or rotating th screen.
Click to expand...
Click to collapse
This is a horrible suggestion for any other use and goes against everything we know about proper flashing, but if all else fails maybe try dirty flashing it over another ROM in which you CAN go through the first boot settings (for example, an ICS ROM that doesn't require the START button in that location). If the unexpected problems that sometimes arise from dirty flashes don't come up, you might be able to get into Jelly Time without the first boot menus.
Obviously, all the problems with dirty-flashing different ROMs come with this "solution."

bananagranola said:
This is a horrible suggestion for any other use and goes against everything we know about proper flashing, but if all else fails maybe try dirty flashing it over another ROM in which you CAN go through the first boot settings (for example, an ICS ROM that doesn't require the START button in that location). If the unexpected problems that sometimes arise from dirty flashes don't come up, you might be able to get into Jelly Time without the first boot menus.
Obviously, all the problems with dirty-flashing different ROMs come with this "solution."
Click to expand...
Click to collapse
Thats an interesting suggestion but the question there is which ICS ROM would give the best results?
I think I would prefer to have a full wipe on installation. So having a way of skipping that first configuration screen, or remotly pressing the start button or even been able to force it to rotate the screen would do the trick. However untill you have got past those first configuration screen you are locked into not been able to run any applications.
I was wondering if there was any way via ADB command line to achive this?

Skunkworx said:
Thats an interesting suggestion but the question there is which ICS ROM would give the best results?
I think I would prefer to have a full wipe on installation. So having a way of skipping that first configuration screen, or remotly pressing the start button or even been able to force it to rotate the screen would do the trick. However untill you have got past those first configuration screen you are locked into not been able to run any applications.
I was wondering if there was any way via ADB command line to achive this?
Click to expand...
Click to collapse
Yes there is. You can use the "adb shell input keyevent <event_code>" command.
You'll probably want to send the DPAD_CENTER command to click that button. I think its event code is 23. Try typing "adb shell input keyevent 23".
Try the code for KEYCODE_ENTER as well.. its 66.
There is a whole list of keyevents at this link:
http://developer.android.com/reference/android/view/KeyEvent.html
Just lookup the "Constant Value" in the description of whatever KEYCODE_xxx you're trying to simulate and use that constant value as the event_code for the command.
I've tried simulating the DPAD_LEFT and DPAD_RIGHT keypress and they're working like a charm
---------- Post added at 04:34 PM ---------- Previous post was at 04:14 PM ----------
Yup. I've tried working with these Keycodes and they work fine.
Use event_codes 19 for UP, 20 for DOWN, 21 for LEFT, 22 for RIGHT to navigate to whatever button you need to press and then use 23 for pressing that button.
Should solve your problem.

Skunkworx said:
I have just flashed Jellytime R16 to my DHD but have a slightly damaged touch screen. Unfortunately the part of the touch screen that doesn't work is the bit where you have to press the start button to move off the screen where you select the language on first boot up.
Does anyone have any ideas how I could skip the first configuration screen of the Jellytime R16 ROM?
Click to expand...
Click to collapse
Hi, did you flash Gapps as well? I've moved from ARHD (which has the configuration start screen) to JellyTime and never got the language or any other configuration start screen (which I'm glad to get rid of). I always full wiped, clean flashed just the ROM, then booted into the OS for the first time to check it out. No Gapps and no language/configuration screen - it would always go straight to the lock screen where I would just swipe to the right and it would ask me to choose either the Nova or Trebuchet launcher. I'd then rebooted into recovery again and flashed Gapps. Hope this helps.

if4ctOr, Thanks for your suggestion this is what I was originally looking for however I didn't get around to trying it as the idea that divche put forward was a much easier approach.
Divche: Thanks, that did the trick perfectly. I am also comming from ARHD so I thought I give your idea a try. I was flashing the Gapps at the same time but booting into the OS first then flashing the Gapps after that prevented the configuration popup.
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom. So I am looking for a soloution to that and also a way to move my sms messages over.
Eventually I am planning on using the Jelly time as my full time ROM but there are alot of updates to it at the moment, which is a good thing in making it stable. However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?

Skunkworx said:
if4ctOr, Thanks for your suggestion this is what I was originally looking for however I didn't get around to trying it as the idea that divche put forward was a much easier approach.
Divche: Thanks, that did the trick perfectly. I am also comming from ARHD so I thought I give your idea a try. I was flashing the Gapps at the same time but booting into the OS first then flashing the Gapps after that prevented the configuration popup.
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom. So I am looking for a soloution to that and also a way to move my sms messages over.
Eventually I am planning on using the Jelly time as my full time ROM but there are alot of updates to it at the moment, which is a good thing in making it stable. However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Click to expand...
Click to collapse
For moving SMS, I'd suggest this app : https://play.google.com/store/apps/...mNvbS5yaXRlc2hzYWh1LlNNU0JhY2t1cFJlc3RvcmUiXQ..
And as far as flashing the updates of JellyTime are concerned... It is recommended to always full wipe but you might get away with flashing the update over the previous version without a wipe. In some updates the author of the ROM explicitly says that full wipe is needed... in those cases you must. In other cases you can flash the ROM without the wipe which will keep your apps and data intact. However, it would still be better to wipe your cache and dalvik cache atleast.
Using Titanium Backup is not recommended at all when you're switching between different Android versions.. however I personally think it works ok when used between updates of the same ROM.

Skunkworx said:
Divche: Thanks, that did the trick perfectly.
Click to expand...
Click to collapse
I never encountered the config screen, so it was more of a guess based on what I did, so I'm glad it helped!
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom.
Click to expand...
Click to collapse
I also had all my contacts as phone contacts too. I chose to convert my contacts (and my calendar as well) to google for ease of syncing later on, so I have no tried and tested suggestions on how to maintain them as phone contacts. What I did was let HTC Sync synchronise with Outlook (I created a new PST file for this, then specified it in HTC Sync), then used GO Contact Sync Mod (sorry I can't post links yet) to sync it with my gmail account.
If you really wanted to leave as phone contacts, you could try Titanium Backup - but since your phone contacts are saved as system data it's a bad idea - so I'd recommend against it. If you're backing up your nandroid for ARHD, you could always try TiBu and let us know how it went - I think it was labeled Dialer Storage - filter to system data and just look through all the green-colored items for something that says "CONTACTS" or "PEOPLE".
However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Click to expand...
Click to collapse
+1 to what if4!ct0r said regarding wiping before flashing.
There will always be some system settings that you will have to re-enter manually if you customize them a lot even when updating builds of the same ROM (probably because these are the system items that you shouldn't be restoring). These will depend on the ROM, but for me and JellyTime, the ones I had to redo were developer, lock screen, system/status bar, sound, display, language, as well as ringtone/sound notifications for alarms, messaging and calendar. Also you'll have to manually set up your widgets again - typically ones that require you to configure it as you place it.
As for TiBu not being recommended - personally I didn't have a problem with it when moving over to JellyTime. I actually purchased the Pro version just for this and for flashing new JellyTime builds. There are two things to consider when restoring via TiBu: 1) system data; and 2) app and app data.
System data: The main concern here is, when changing to a completely different ROM, do NOT restore any system data (unless you're aware whether it was updated in the new build or just experimenting). Even when you're updating to a new build of the same ROM, you should at least avoid restoring the red-coloured items and just stick to green and yellow items that may contain useful data such as contacts, sms, call logs, saved wifi access points, bookmarks, etc.
App and app data: I personally think it's ok to restore your apps themselves, but you could always record a list of what you had and download them manually again just to be safe - not a big deal unless you have over a hundred apps. When switching ROMs, try to avoid restoring the app's data unless you really wanted/needed it for certain apps - in that case, be conservative with what you choose. I'm not a programmer or developer, so I don't know how this would affect your system/app if switching to a ROM with a different Android version. Restoring app data between builds of the same ROM should be fine, as I've done it between all my JellyTime flashes with no issue even when it updated to Android 4.1.2.
Tip: after flashing the ROM, and doing your typical post-ROM-flash stuff (like fixing permissions, rebooting, wiping cache+dalvik, flashing Gapps, etc), and you've tested it and are happy with its stability, download TiBu again (or if you had the apk stored somewhere after you purchased it, just install it manually), boot to recovery and make a nandroid of the new ROM as it stands: nice and clean before any apps are installed. This way you've got a recovery option without having to go through the hassle of re-flashing the ROM build again, setting it up, etc if all you did was stuff up while experimenting with restoring data on TiBu.
As always, make a nandroid backup before flashing. As I mentioned, if you're initially happy with the ROM, I recommended also doing one after you flash while the system is fresh and clean. Sorry if this post is a bit wordy, but I thought more info would help, as it helped me in the past.
Skunkworx said:
So I am looking for a soloution ... to move my sms messages over.
Click to expand...
Click to collapse
if4ct0r said:
For moving SMS, I'd suggest this app...
Click to expand...
Click to collapse
+1 for SMS Backup & Restore; I also used it, but keep in mind AFAIK it doesn't save MMS. I also used Call Logs Backup & Restore, in case you're interested in backing this up too. But since I started using TiBu, I don't need either of these apps any more.

Maybe changing the digitizer could help asd
Sent from my Galaxy Nexus using xda app-developers app

[GUIDE]Aroma Freeze FIX (test)

So I was having the same issues as everybody else was with Aroma freezing a million times when trying to install a ROM. I tried a few things but eventually stumbled apon a workaround that seemed to work.
I'll explain what I did then others can try it out. If it works for more/everyone else then happy days. If not then maybe I just got lucky.
OK so firstly I was on rooted stock ROM. I'm sure that it's not important really. But I want to mention every step.
I flashed TWRP recovery.
Rooted etc...Standard stuff
Then I used ROM managed to flash non touch recovery via the app itself.
Then made sure CWM was my default recovery in Rom manager.
Rebooted to recovery from Rom Manager.
Wipe data + caches
Install zip. In my case Trickdroid 5.1.0
Then as Aroma is booting up don't touch your phone for a good 2 minutes. I was actually out doing shopping and got to the till so left my phone untouched as it as on the welcome screen.
Then using the touch screen to select what I wanted etc I just went straight through. Not one freeze or install crash. First time.
I think it could be a few things perhaps. Maybe heat with Aroma putting high loads on the phone. Maybe the extra time sat let it cool a bit before getting going. Also perhaps Aroma just needs a little extra time to fully load properly.
Anyway please try my guide out. Maybe you cab miss some bits out. Hopefully it works. Post up if it did or didn't.
Good luck and happy flashing!
Sent from my Tricked out 'One'

My suggestion is that do not connect the USB cable when using Aroma, you should get less chance of freezing.

willingtonyuan said:
My suggestion is that do not connect the USB cable when using Aroma, you should get less chance of freezing.
Click to expand...
Click to collapse
Yes. I think this may be to do with the heat increase.
Sent from my HTC One using xda app-developers app

I tried your method this morning and Aroma froze on 30%. Tried it again and it froze on 3%.
Restored my nandroid and half an hour later tried the 'normal' method for installing a new Rom and it went though without a problem.
Sent from my HTC One

Tried it ...
It freezed on 80%

Damn seems like I was just lucky then. That sucks a bit.
Sent from my Tricked out 'One'

Actually does it matter if your AROMA freezes or not? Because my AROMA has froze on 2 occasions for both installations (One was 30% and the other was 97%) on both ROMs (Renovate and ARHD) and there were no errors or whatsoever when rebooted right after the freeze. Is it just me or..? Hmmm.

LordKuroda said:
Actually does it matter if your AROMA freezes or not? Because my AROMA has froze on 2 occasions for both installations (One was 30% and the other was 97%) on both ROMs (Renovate and ARHD) and there were no errors or whatsoever when rebooted right after the freeze. Is it just me or..? Hmmm.
Click to expand...
Click to collapse
well if it doesnt go fully through i would not trust it flashed fully one bit. i am too paranoid.

Dont use the touch function in Aroma Installer! Choose the options with volume and power button... It works for me!

LordKuroda said:
Actually does it matter if your AROMA freezes or not? Because my AROMA has froze on 2 occasions for both installations (One was 30% and the other was 97%) on both ROMs (Renovate and ARHD) and there were no errors or whatsoever when rebooted right after the freeze. Is it just me or..? Hmmm.
Click to expand...
Click to collapse
It doesn't harm your phone it just means it hasn't worked. You have to long hold the power then just try again until it works.
Sent from my Tricked out 'One'

yes only with volume and power button to operate the Aroma installer ...
works for my (previously only problems)
send for my HTC One

The War Horse said:
It doesn't harm your phone it just means it hasn't worked. You have to long hold the power then just try again until it works.
Sent from my Tricked out 'One'
Click to expand...
Click to collapse
Yes it has been successfully flashed, I was on Renovate ROM before my AROMA installation (for ARHD) froze on 30%. I might have left it there for awhile, thinking that the installation is still going on. I long hold the power button, rebooted and I've successfully flashed ARHD when I checked my settings. No crashes or errors at all.

Try clockworkmod touch freezes less, also I did what someone mentioned to clear dalvic and cache before attempting to install a rom, flashing everything else like trikdroid tweaks works allright..

LordKuroda said:
Yes it has been successfully flashed, I was on Renovate ROM before my AROMA installation (for ARHD) froze on 30%. I might have left it there for awhile, thinking that the installation is still going on. I long hold the power button, rebooted and I've successfully flashed ARHD when I checked my settings. No crashes or errors at all.
Click to expand...
Click to collapse
It will hang on 30% for a while anyway but still be installing. Perhaps you missed it finishing up?
Sent from my Tricked out 'One'

None of these work for me....I managed to get through a full ROM install ONCE but since then I haven't had any luck. Talk about annoying....

aroma kept freezing on me. what i did to finally get it to complete was dalvik/cache wipe in cwm classic first.
once aroma was booted be quick choosing your selections using the power button/volume controls then stuck my hand in the freezer with the phone monitoring the install so when it would complete i could be quick to click the next and reboot buttons.

I tried all recoveries.
Aroma always freezes/crashes.
This is so annoying.

I think at this point it is more of a luck of the draw type of things. I have tried a lot of combinations and after trying like 20 times, it finally went through. Still freezes if I want to install tweaks or themes but less than for a ROM....go figure.

I think everyone should have a go at unchanging between the home key for advanced and occasionally if it's stops vibrating feedback then use next button.
I've had a lot more success this way
Sent from my HTC One using xda premium

tontondavid said:
I think at this point it is more of a luck of the draw type of things. I have tried a lot of combinations and after trying like 20 times, it finally went through. Still freezes if I want to install tweaks or themes but less than for a ROM....go figure.
Click to expand...
Click to collapse
What works for me EVERY time with zero freezes is when you are at the first Aroma screen, hold both volume up and volume down at the same time, then push power while holding all three. It will advance to the next screen. Do the same for every screen and dont touch the screen unless you are selecting to remove or add something. I also found that if I wait too long on a screen before making a choice, it will freeze.