Database Info

[Q] Updating ROM via GooManager

Hi All,
I have posted this on the GooManager thread but there hasn't been much activity there recently so asking here as well. Noob question on GooManager...I have the AOKP rom installed on my Sensation and GooManager notifies me of updates to my ROM every now and then. I just want to know if updating my ROM build with GooManager will reset all my custom ROM settings and preferences or will they all be preserved? I'd like to keep my ROM up to date but if it means spending all the time again to setup my preferences and icons/widgets/home screens etc. then I'd rather stick with what I have.
TIA!

I'd recommend to use GooManager only to download the newest ROM and flash it from recovery.
I asume you're using AOKP Swagger from frankenstine, the same I use.
I just download the update from GooManager, boot to recovery, flash ROM, gapps and 4.2 stuff and are ready to go.
All my settings are their after updating - only AdAway needs a reconfiguration and a reboot (and I need to set my alarm clock since I'm overwriting that). Basically you keep all your settings except those you made to the kernel.
Regards

lolmachine4 said:
I'd recommend to use GooManager only to download the newest ROM and flash it from recovery.
I asume you're using AOKP Swagger from frankenstine, the same I use.
I just download the update from GooManager, boot to recovery, flash ROM, gapps and 4.2 stuff and are ready to go.
All my settings are their after updating - only AdAway needs a reconfiguration and a reboot (and I need to set my alarm clock since I'm overwriting that). Basically you keep all your settings except those you made to the kernel.
Regards
Click to expand...
Click to collapse
Oh perfect, yes indeed I am using that exact ROM.
OK so when I boot to recovery, I shouldn't do any wiping? Just simply flash the new file? Will the updated gapps package be in the download I get from GooManager?

freddysensation said:
Oh perfect, yes indeed I am using that exact ROM.
OK so when I boot to recovery, I shouldn't do any wiping? Just simply flash the new file? Will the updated gapps package be in the download I get from GooManager?
Click to expand...
Click to collapse
I only wipe dalvik & cache after each update.
I can't say something about what GooManager downloads as "gapps", I use some I downloaded some weeks ago + some old version of 4.2 stuff. I might need to update my flash-setup too

lolmachine4 said:
I only wipe dalvik & cache after each update.
I can't say something about what GooManager downloads as "gapps", I use some I downloaded some weeks ago + some old version of 4.2 stuff. I might need to update my flash-setup too
Click to expand...
Click to collapse
Thanks lolmachine, for the benefit of anyone who might have the same question as me the following worked:
- Downloaded latest build of my AOKP Rom via GooManager
- Downloaded latest gapps package for my ROM via GooManager
- Boot to Recovery
- Flash new ROM file and then gapps package
- Restart.
My only question is, I didn't wipe davlik and cache so should I, and what difference does it make if I don't?

I used Goo the other day to flash, ummm, bugger, can't remember if it was an update or a new rom.
Oh now I remember, the latest one was an update to Bruce's Rom. I do believe when I tapped flash rom it booted to recovery (the one it installs) and I may have had to select "Install" from there, don't think so though. Either way, I used Goo to handle the install.
I didn't do a wipe. From what I've picked up, wiping is a good way to cover your butt. So if you're having issues and didn't wipe, you go back and do it all again with a wipe. Doing the wipe to start with means you can eliminate those types of issues from the start.
Someone can correct me if I'm wrong (which I probably am )

Hi there, I also received an update to my ROM via Goo Manager. It is CyanogenMod 10.1 by Albinoman887 for my HTC Sensation XE. I am using the EXT4 bootloader. I just installed it a few nights ago so I am completely new to rooting. My question is that there is no option to wipe dalvik cach. EXT4 just says wipe cache, wipe data and wipe system. Does wipe cache wipe dalvik cache as well. Also do I need to re-flash gapps as well after updating and will this wipe my gmail accounts etc?
Thanks,
Adam

thisisadamh said:
Hi there, I also received an update to my ROM via Goo Manager. It is CyanogenMod 10.1 by Albinoman887 for my HTC Sensation XE. I am using the EXT4 bootloader. I just installed it a few nights ago so I am completely new to rooting. My question is that there is no option to wipe dalvik cach. EXT4 just says wipe cache, wipe data and wipe system. Does wipe cache wipe dalvik cache as well. Also do I need to re-flash gapps as well after updating and will this wipe my gmail accounts etc?
Thanks,
Adam
Click to expand...
Click to collapse
You want to select "wipe dalvik+cache" option when you flash an update.
There's no need to flash gapps after a ROM update.
Sent from my Ouya

AndroidSupporter318 said:
You want to select "wipe dalvik+cache" option when you flash an update.
There's no need to flash gapps after a ROM update.
Sent from my Ouya
Click to expand...
Click to collapse
Thanks very much, downloading it now.

Help
im using albinoman's jelly bean rom
excuse me for noob doubts but
1) goo manager shows i have an update, so ive downloaded it. its a zip just like the rom n not just a small update. i have downloaded it now what should i do?
2) if i have to go to the recovery and flash the zip then i have to wipe only the cache right? Im using 4ext recovery.
3) will all my apps get uninstalled? what about the app data?
4) what about gapps? i have a gapps zip file, will i have to flash it again after the update?
Please reply thanks

I finally rooted phone after silly VMUNE7 thing on Verizon but after I get the install openrecoverscript and hit reboot recovery it does not go to teamwiz bootload instead I get something with a green driod on the bottom saying downloading but above it saying in red can't download Odin mode?? Please help I want to run cleanrom for better battery and less bloatware and keep my touchwiz. :crying:

all3rd said:
I finally rooted phone after silly VMUNE7 thing on Verizon but after I get the install openrecoverscript and hit reboot recovery it does not go to teamwiz bootload instead I get something with a green driod on the bottom saying downloading but above it saying in red can't download Odin mode?? Please help I want to run cleanrom for better battery and less bloatware and keep my touchwiz. :crying:
Click to expand...
Click to collapse
sorry man but i think you are talking for a samsung device am i right?
if yes then this is only for sensation/XE/4G devices

yasho170 said:
im using albinoman's jelly bean rom
excuse me for noob doubts but
1) goo manager shows i have an update, so ive downloaded it. its a zip just like the rom n not just a small update. i have downloaded it now what should i do?
2) if i have to go to the recovery and flash the zip then i have to wipe only the cache right? Im using 4ext recovery.
3) will all my apps get uninstalled? what about the app data?
4) what about gapps? i have a gapps zip file, will i have to flash it again after the update?
Please reply thanks
Click to expand...
Click to collapse
Simple.
Go to recovery.
For s-on you must enable smartflash.
Do a nandroid backup.
Dirty flash the update (meaning flash over the previous rom without wiping).
Dirty flash gapps (signed only).
Wipe cache + dalvik.
Reboot.
If it can't boot/run properly then you can just restore the backup or do a clean flash.

First off I'm not experienced in any way, got my Sensation unlocked, rootet and installed Sultanxda's 4.4.2 ROM for sensation. I'm on S-On, too, if anyone wonders.
Updating didnt affect my apps as far as I can tell. Everything seems to be the way as before and everything seems to be working.
What I did was download the ROM manually since the download with goomanager didn't work. I downloaded gapps as backup because I didnt have the zip on my SD, just in case anything would go wrong.
You only need to boot into recovery, with S-On make sure smartflashing or something like that is on, select the zip, flash it and then select wipe cache +dalvik.
It's pretty much what AndroidSupporter318 wrote, just wanted to give feedback and say what I did in detail in case anyone was still wondering.
LxMaD

I guaranted 4EXT Recovery for this type of problem. U don't need to boot into recovery and work with 4ext is very simple.

[Q] phone will not boot after installing any kernel

about a week ago i updated to the newest cm10.1 nightly with gapps 4.2. after flashing those i tried to flash leankernel. my battery was low and the phone turned off when rebooting after the leankernel flash. since then i cannot flash any kernel. i have to do a battery pull to get back into cwm recovery. once in recovery i can wipe data and reinstall cm 10.1 with the standard kernel. i have tried just about every combo of wiping cache, davlik, fix permissions. still not able to flash any kernel. could it have something to do with gapps 4.2 or the phone shutting off mid flash? if so does anyone know how to repair? i already flashed back to stock and rerooted re-unlocked, etc. thanks

and to clarify , it was gapps 4.2.2

Ive found that 3.4 based kernels work with some roms and not with others.
try an older build date its likely not 3.4 based.
or, if your trying a non 3.4 kernel and it wont boot, try a 3.4 kernel.

If you're trying to flash LeanKernel, what's the zip file you're attempting to flash? Also, what are you wiping prior to flashing the kernel?
Sent from my SCH-I535 using xda app-developers app

i tried the mastamoon 3.4 kernel with no luck . the rom i amrunning is the cm-10 nightly 2013-03-24. the leankernel version i am running is lk_s3vzw_aosp_jb42-v2.9. i wipe cache then wipe davlik then flash, it always worked with that procedure before, but since the problem i have tried wiping both after along with fixing permissions. before this issue it was simple as pi, wipe cache, davlik, flash, reboot .

You could always try twrp. Ha. It would make no sense why you couldn't install a kernel.
I would assume since you went back to Odin stock. It would flash factory kernel and give you a clean slate.
So unless cwm is outdated.... ?
Sounds very weird.

actually that is another variable that i didnt think of. cwm updated from 6.0.1 to 6.0.3 or something like that. but then again the original recovery i used after the clean slate was the ez recovery which used 6.0.1 stupid question, but how does twrp work? i always used cwm. i tried flashing twrp but cwm came up when i went to recovery when i tried using twrp?! that was before i did a stock recovery so it couldnt be possible that i am running both? should i delete cwm before i use twrp? if so how? if you dont feel like going into that much detail, i can search it.

i figured out twrp. never gave it achance. ill see if that does the trick

tried twrp. still the same thing going on. gonna go to bed now. ill check back tomorrow after work to see if there are any more ideas. thanks

Problem solved. I went into my internal SD via astro and deleted all old traces of cwm as well as ez unlock and ez recovery. I was getting a generic (showed setting icon instead of regular su icon)super user screen come up prior to that, after deleting those files the regular super user came back. Rebooted into recovery via twrp , cleared cache, Davlik, flashed lean kernel and it worked. What do you think the issue was? Lingering files from ez recovery? That weird su thing?

[Q] ViperOneS 2.2.0 OTA

Hey guys, since my post count is too low to post my problems with this OTA update in the development section of this rom, ill do it here. Sorry for that.
I think im having no problems with flashing the 2.1. ROM yet but i have my concerns if i did that right.
First problem with flashing it, is the question if im having a custom kernel. I flashed ViperOneS a several times but made a fullwipe before.
So am i having a custom kernel or not?
Next issue is that im only able to flash this ROM with CWM. TWRP 2.5 doesnt work and even 2.3.3.0, which should work, but does not for me...
Well with CWM i ll do it that way:
1. Doing Fullwipe in CWM (Factory reset, Wipe Cache, Wipe Dalvik and System).
2. Flashing the ROM and choosing HTC Theme > Custom Kernel? > not sure sometimes "yes" sometimes "no".
3. Flash finished? > asks me if i want to reboot (into system) or save the logs. Since the instruction tells me to flash the boot.img first before rebooting...
4. ... im going into bootloader via adb which works
5. flash the boot.img
6. fastboot erase cache
7. reboot system
8. before doing the first setup i go into recovery and wipe cache.
I think 2.1 works but i want to be sure if i did everything right, especially with the custom kernel question and that i reboot into bootloader right after aroma says that the flash is finished.
Now i want to flash the 2.2.0 OTA because the update function through the ROM didnt work for me last time (it downloads the OTA but wasnt able to flash)
Im not sure how to flash the OTA right via recovery. Everytime i did that the ROM was kinda messed up, like when im turning the screen off and on Sense keeps loading and it takes some sec to unlock. And the venom tweaks app is totally laggy, even with the "trick" to go into app settings and wipe the cache and data which found on any other site (not xda...).
The problem is that they dont keep their instructions up-to-date (+ how to flash the OTA... right)
It looks to my like there are 100 different ways to flash 2.1.0 and 2.2.0 and only 1 is the right way which lets the ROM being amazing...
Hope you can help me. Thanks in advance!

turnschuh said:
Now i want to flash the 2.2.0 OTA because the update function through the ROM didnt work for me last time (it downloads the OTA but wasnt able to flash)
Im not sure how to flash the OTA right via recovery. Everytime i did that the ROM was kinda messed up, like when im turning the screen off and on Sense keeps loading and it takes some sec to unlock. And the venom tweaks app is totally laggy, even with the "trick" to go into app settings and wipe the cache and data which found on any other site (not xda...).
Click to expand...
Click to collapse
All you have to do ist to flash the OTA with your custom recovery like any other flashable zip if this isn't done automatically. You can simply copy it to your device from your pc or flash it from your mobiles download folder, it doesn't matter which way.
The 'trick' is very well known here at xda, but simply nobody wants to repeat it a hundred times... Here at xda there is even included the fact, that after rebooting you should change your skin once to get things going besides wiping cache and data in venom tweaks and hub.
What EXACTLY doesn't work with TWRP 2.3.3.0?

All you have to do ist to flash the OTA with your custom recovery like any other flashable zip if this isn't done automatically. You can simply copy it to your device from your pc or flash it from your mobiles download folder, it doesn't matter which way.
Click to expand...
Click to collapse
yea i did it like that. i just flashed it in the recovery, but im not sure if i have to wipe caches after or before doing that.
The 'trick' is very well known here at xda, but simply nobody wants to repeat it a hundred times... Here at xda there is even included the fact, that after rebooting you should change your skin once to get things going besides wiping cache and data in venom tweaks and hub.
Click to expand...
Click to collapse
about finding such "tricks": the problem is that those ROM release threads have tons of post (500+ sites of them) and it seems like 90% are from people who didnt even flash the ROM... i think you ll excuse me if i say i got tired of searching for my problems there^^
well can u tell me which skin i have to change? on venom tweaks or the htc skin on personalization? and app settings > venom tweaks > wipe cache and data right?
What EXACTLY doesn't work with TWRP 2.3.3.0?
Click to expand...
Click to collapse
when i flash it with 2.3.3.0 (or 2.5... its the same), the flash process doesnt even take up to 2 seconds and it says its finished and that causes a bootloop but doesnt make me wonder.
dont you have problems with TWRP flashing sense roms either?
ah and another one: did i flash the version 2.1 right and what about the custom kernel question?
well thanks for ur time.
edit: well this time flashing with twrp 2.3.3.0 worked somehow, but i choosed flashing without wipe (made it in recovery) and not to delete apps with aroma installer (which i did before)... just strange.

new problem. dont know whats wrong with my phone but:
wanted to make a backup of my ViperOneS 2.1 with TWRP 2.3.3.0 after lets say 70% of progress it starts turning off my phone and restarts into system. i flashed 2.5.0.0 but its the same issue (edit#1: with CWM too...). strange is that TWRP turned out my phone before when i wiped something there.
i think somethings really messed up atm...
edit#2: had to run a ruu over the system again, flashed twrp and backups seem work again..strange ****

[Q] stuck in boot with CM rom and with back-up rom

Hello,
my tf700 doesn't finish the boot after I've installed CM.
Before flashing a new rom I've tried to make a system back-up from GooManager.
I don't know if the back-up is fully functional because in the "Breaking back-up in multiple archives" it has remained stuck at 100% (or complete progress bar) for like an hour.
After an hour or so I've interrupted the back-up process and entered the TWRP Recovery v2.5 (which I'm still able to access at the moment) and tried to flash a ROM downloaded by GooManager (cm-10.0.0-tf700t.zip). I've wiped the Dalvik cache and Cache in the process.
The flash seemed to be successful but the reboot doesn't finish, even though I've let it for two hours or so.
After that I've reentered the TWRP and tried a different rom cm-10.1-20130513-NIGHTLY-tf700t.zip, but with similar result, after installation it doesn't finish the boot.
I've reentered the TWRP and tried restoring the back-up. It did restored the system, passed the "configuring application" stage and gave the message "Finishing boot" and nothing afterwards, it just stuck in the process.
Right now I'm still able to enter TWRP, and navigate through the folders on the tablet, but I don't have a functional rom.
Can you please help me with some advices?
Thank you.

Which ROM did you have before, and which bootloader version?

_that said:
Which ROM did you have before, and which bootloader version?
Click to expand...
Click to collapse
Before that I had the stock ROM with the latest OTA firmware from Asus.
I don't know what was the initial version of the bootloader.
I've unlocked the device using Asus apk
I've pushed the TWRP on the tablet using the TF700T-ADB- Tool v3
I've granted super user rights from TWRP, I think using SuperUser application.
Ive installed from market GooManager and after that I've done what I've described in the previous message.
Thanks for your prompt answer.

Maybe CM is confused by existing data - did you wipe data (factory reset) as written in the CM instructions?

_that said:
Maybe CM is confused by existing data - did you wipe data (factory reset) as written in the CM instructions?
Click to expand...
Click to collapse
No, I didn't. I've just wiped the Dalvik cache and Cache.
If I do wipe data, I will still have user data, like downloaded ZIP ROMs or GAPPS zip?
I mean, at the moment I'm still able to try different ROMs and kind of operate the tablet. If I do wipe the data and is something wrong with the flash will I be able the try something else? Before I wipe existing data should I take other precautions?

Mihai_Preda said:
No, I didn't. I've just wiped the Dalvik cache and Cache.
If I do wipe data, I will still have user data, like downloaded ZIP ROMs or GAPPS zip?
I mean, at the moment I'm still able to try different ROMs and kind of operate the tablet. If I do wipe the data and is something wrong with the flash will I be able the try something else? Before I wipe existing data should I take other precautions?
Click to expand...
Click to collapse
From what I've read (but never tried myself), a "Factory Reset" is supposed to delete all your apps, app data and system-specific data, but not the contents of your internal emulated SD card. Your ROM and recovery are definitely not affected. But I'd wait until someone else can confirm.

It seems strange that the back-up isn't fully working either, it gets stuck after "Finishing boot".
I've noticed somtheing while flashing the two CM ROMs. On the instalation, of each of the two, it was a message that the MD5 is being checked, and after that that MD5 is missing and the check is being skipped. The instalation did continued and the message "Instalation succesful" was given.
But I don't know if it's alright not findind the MD5.

_that said:
From what I've read (but never tried myself), a "Factory Reset" is supposed to delete all your apps, app data and system-specific data, but not the contents of your internal emulated SD card. Your ROM and recovery are definitely not affected. But I'd wait until someone else can confirm.
Click to expand...
Click to collapse
I've checked on other sources and the wipe data seems to leave intact the user data.
But I'm still wondering at what state the tablet will be reseted since I've tried flashing to different ROMs and the back-up restore didn't work quite properly.
The last functioning ROM is still available from other means that restore back-up (which doesn't work) even though I've tried flashing new ROMs over it?

Mihai_Preda said:
On the instalation, of each of the two, it was a message that the MD5 is being checked, and after that that MD5 is missing and the check is being skipped. The instalation did continued and the message "Instalation succesful" was given.
Click to expand...
Click to collapse
The missing MD5 file is not a problem. If it says "installation successful", you can assume that it is.
Mihai_Preda said:
I've checked on other sources and the wipe data seems to leave intact the user data.
But I'm still wondering at what state the tablet will be reseted since I've tried flashing to different ROMs and the back-up restore didn't work quite properly.
The last functioning ROM is still available from other means that restore back-up (which doesn't work) even though I've tried flashing new ROMs over it?
Click to expand...
Click to collapse
Your backups not working is somewhat strange, but that's another area where I have very limited experience.
You said you were on the "latest OTA" stock ROM. Was that 10.4.4.25 (Android 4.1) or 10.6.1.14.4 (Android 4.2)? Also check the bootloader version - boot into the bootloader menu with holding volume-left, then read the tiny text near the top of the screen. It should contain the build number of your bootloader, which is identical to the build number of the stock ROM until you flash one of them separately.

_that said:
You said you were on the "latest OTA" stock ROM. Was that 10.4.4.25 (Android 4.1) or 10.6.1.14.4 (Android 4.2)? Also check the bootloader version - boot into the bootloader menu with holding volume-left, then read the tiny text near the top of the screen. It should contain the build number of your bootloader, which is identical to the build number of the stock ROM until you flash one of them separately.
Click to expand...
Click to collapse
It's Android 4.2.1: "Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.4-20130329" A03"
Right now the tablet is left with the attempted back-up recovery. Should I enter TWRP and do the wipe data or wipe data from the bootloader menu?
Or is something else that I should do first?

Ok, I did wipe the data, and even though it erased the user data too (media, docs, zip files etc) it restore the tablet to cyanogen mode not the original stock ROM. It finished the boot restore my gmail account. SuperUser is updated. And it seems the overall responsiveness is better.
Thank you for your time and advice!

Mihai_Preda said:
It's Android 4.2.1: "Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.4-20130329" A03"
Right now the tablet is left with the attempted back-up recovery. Should I enter TWRP and do the wipe data or wipe data from the bootloader menu?
Or is something else that I should do first?
Click to expand...
Click to collapse
OK, your bootloader is the latest one, and it works with Android 4.1 and 4.2 ROMs. There have been several reports of unrecoverable bricks after using "wipe data" from the bootloader menu with a broken or incompatible recovery - so even if your recovery works fine, I would not recommend to take any unnecessary risk.
If you have any important data on your device it would be a good idea to store a backup on an external microSD card, just in case you do wipe all data by accident or something unexpected happens.

_that said:
OK, your bootloader is the latest one, and it works with Android 4.1 and 4.2 ROMs. There have been several reports of unrecoverable bricks after using "wipe data" from the bootloader menu with a broken or incompatible recovery - so even if your recovery works fine, I would not recommend to take any unnecessary risk.
If you have any important data on your device it would be a good idea to store a backup on an external microSD card, just in case you do wipe all data by accident or something unexpected happens.
Click to expand...
Click to collapse
I'm surprised that after wipe data procedure it restored the system to a cyanogen mode not the original rom. I'm surprised by this because the last functional ROM was the stock one and because after flashing the last zip with CM ROM I've tried to restore the back-up ROM. Even though it didn't finish the boot, this back-up seemed to be installed over the previous CM ROMs. I'm not sure what happened, why I do have a CM ROM functioning, even though I did tried to install it I don't know why it managed to be installed.
If you have little more time and you know what happened here please let me know.
Thank you again!

Mihai_Preda said:
I'm surprised that after wipe data procedure it restored the system to a cyanogen mode not the original rom. I'm surprised by this because the last functional ROM was the stock one and because after flashing the last zip with CM ROM I've tried to restore the back-up ROM. Even though it didn't finish the boot, this back-up seemed to be installed over the previous CM ROMs. I'm not sure what happened, why I do have a CM ROM functioning, even though I did tried to install it I don't know why it managed to be installed.
Click to expand...
Click to collapse
The ROM and your data are completely separate. If you install a ROM and it says "install successful", the ROM is installed. "Wipe data" does not touch the ROM. However your data can prevent the ROM from starting up correctly. Apparently the restore fixed something in your data partition so that the last ROM that you installed can now boot.

_that said:
The ROM and your data are completely separate. If you install a ROM and it says "install successful", the ROM is installed. "Wipe data" does not touch the ROM. However your data can prevent the ROM from starting up correctly. Apparently the restore fixed something in your data partition so that the last ROM that you installed can now boot.
Click to expand...
Click to collapse
That means the TWRP didn't actually restore the ROM from back-up even if it did say the restore was successful...The last installed ROM was a CM one.
Thanks for the help!

[Q] Every ROM hangs at startup screen

Flashed several ROMS in my life and have not always wiped all data. Mainly i do dalvik and cache. My phones have always work. Now i have a Razr HD with an unlocked BL with TWRP loaded. I cant seem to get past the initial bootup screen no matter what ROM i flash. What am i missing here guys? Do i need to check the "factory reset" in TWRP along with Dalvik, system and cache?

famac! said:
Flashed several ROMS in my life and have not always wiped all data. Mainly i do dalvik and cache. My phones have always work. Now i have a Razr HD with an unlocked BL with TWRP loaded. I cant seem to get past the initial bootup screen no matter what ROM i flash. What am i missing here guys? Do i need to check the "factory reset" in TWRP along with Dalvik, system and cache?
Click to expand...
Click to collapse
answered here http://forum.xda-developers.com/showthread.php?t=2465695

bweN diorD said:
answered here http://forum.xda-developers.com/showthread.php?t=2465695
Click to expand...
Click to collapse
Not really. The majority of ROMS in question have been 4.2.2 based....

famac! said:
Not really. The majority of ROMS in question have been 4.2.2 based....
Click to expand...
Click to collapse
quote from post 11
"By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot"

bweN diorD said:
quote from post 11
"By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot"
Click to expand...
Click to collapse
Please explain this further to me. My problem is with 4.2.2 ROMS. The fix above is for folks having issues with 4.3 ROMS. Are you suggesting that doing this will also fix my 4.2.2 problems? This is also CWM while i run TWRP. I did a quick look and the two are setup a little difference. I played around with those highlighted instructions and almost accidentally wiped my only backup of my previous state. I actually thought i was toast but somehow i reloaded and went back to my old backup state.

famac! said:
Please explain this further to me. My problem is with 4.2.2 ROMS. The fix above is for folks having issues with 4.3 ROMS. Are you suggesting that doing this will also fix my 4.2.2 problems? This is also CWM while i run TWRP. I did a quick look and the two are setup a little difference. I played around with those highlighted instructions and almost accidentally wiped my only backup of my previous state. I actually thought i was toast but somehow i reloaded and went back to my old backup state.
Click to expand...
Click to collapse
i could be wrong, but in my opinion having the exact same issue even though its a different version, one of the 2 fixes in that thread should work.
the first fix likely doesn't directly apply although i suggest you ensure you have the latest version of your recovery of choice found here http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
second fix (backup ALL data you don't want to loose first as noted above), then do a full wipe as listed above, not just a fdr that doesn't wipe everything on the internal card.
the problem at this point is, you are assuming it wont work because of version differences, i am assuming it will. until you try it, i don't see any point in exploring other options, if there are any.

Dirty flashing when you go to different ROMs is generally not a good idea. Even on 4.2.2, it leaves residual data behind. There's a reason that the devs talk about doing complete wipes in their ROM threads, and there's a reason that they tell you not to talk about bugs unless you use their install directions.

RikRong said:
Dirty flashing when you go to different ROMs is generally not a good idea. Even on 4.2.2, it leaves residual data behind. There's a reason that the devs talk about doing complete wipes in their ROM threads, and there's a reason that they tell you not to talk about bugs unless you use their install directions.
Click to expand...
Click to collapse
Yeah, i am straight now. Did a full wipe and sailed right past the startup animation. Thanks all.

famac! said:
Yeah, i am straight now. Did a full wipe and sailed right past the startup animation. Thanks all.
Click to expand...
Click to collapse
Nice! Glad to see you got it working.