Database Info

[Q] Unable to flash CM10 nightly and restore issues

My phone is stuck in the CyanogenMod 10 booting animation.
I did the following:
1. Installed RUU (after changing radio and wanted to go back) , unchecked fastboot in the power setting and checked the USB debugging from
the DEVELOPER OPTIONS.
2. Rooted the phone.
3. Installed TWRP2.2.2.0 recovery.
4. Backed up the stock sense 4.0 rom.
5. flashed the CM10 Nightly 20/9/2012. flashing went well (no errors or anything of the sort)
6. fastboot the boot.img from the rom.
7. After 25 min of waiting in the boot animation of the CyanogenMod 10 I rebooted and restored the backup ,during the restore ,in the part of the boot restoring, it took around 400sec(i'm not sure if its bad) - after the restore was done the phone did not boot past the first HTC screen (with the red warning ).
8. I installed Viper One rom and now its working fine.
Does any one have an idea of what went wrong?
I wanna be able to flash the CM10 nightlys...
Thanks

Bad CM10 download? MD5?
Bad Boot flash?
What hboot version you on--
Not really sure--did you do full wipe including System on both flashes. I usually wipe 3X on new/different roms--

rugmankc said:
Bad CM10 download? MD5?
Bad Boot flash?
What hboot version you on--
Not really sure--did you do full wipe including System on both flashes. I usually wipe 3X on new/different roms--
Click to expand...
Click to collapse
I flashed the boot twice and two different CM10 nightly and I did not flash the system at any time.
I had Hboot 1.06 before the RUU installation, now i have 1.13, could this be an issue?

ok
with .13 you probably need to fastboot boot image anyway
i always wipe System 3x unless just updating nightlies or a rom with a minor version cahnge
try cm10 again with System wipe

rugmankc said:
ok
with .13 you probably need to fastboot boot image anyway
i always wipe System 3x unless just updating nightlies or a rom with a minor version cahnge
try cm10 again with System wipe
Click to expand...
Click to collapse
Well I have Hboot 1.13 and I just cant flash the CM10 nightly or mount the SD card cant be mount (i tried the guide didn't worked).
when i go in to the CWM recovery i see these messages.
can it be the problem?
I think i need to make a video of what Im doing because ever since i updated the Hboot (by mistake) i just cant flesh CM10 nightlis.

You might want to try TWRP recovery from Market

Proper way to update ROM

I was just wondering what steps I need to take in order to install an updated version of my rom. Currently I use the aokp jb version 4. Want to update to the new milestone. Can someone help me out with the procedure? Will I lose any data?
Sent from my One X using xda app-developers app

dan798 said:
I was just wondering what steps I need to take in order to install an updated version of my rom. Currently I use the aokp jb version 4. Want to update to the new milestone. Can someone help me out with the procedure? Will I lose any data?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
. First thing you should do is a nand backup in recovery (so you have something to go back to if all else fails)
. backup your SD card
. move your nand backup and sd card backup to your computer (that way if your sd gets corrupted you can reformat and push your backups to your device)
. you can also backup your apps + data with something like titanium backup (although now at least in JB if you have chosen this option Google will restore your apps, does not always work for me though so beware)
! Note that Tibu is quite controversial some people love it and swear by it and some people claim that it creates lots of issues, if you decide to use it, only use it to backup/restore user apps and not system apps. I personally use the pro version since it can sync backups to my Box and Dropbox account.
in addition to all of this I backup my sms, call log and custom launcher settings (but that's just me i'm a bit paranoid and I love redundancy)
When you're staying with the same rom you typically don't have to factory reset/clean install (unless of course the dev recommends it), just wipe cache and dalvik in recovery and flash your new rom.zip (don't forget to fastboot flash the boot.img if you're on the latest hboot) in recovery.
If you do not factory reset/clean install you will not loose data fingers-crossed. if you start encountering a lot of weirdness after a dirty flash well you will have to factory reset/clean install. I like to clean install most of the time so that I don't have to try to troubleshoot a bunch of stuff when s**T goes wrong plus it's easier to get support for obvious reasons.
In this particular case Milestone release of AOKP (milestone is a "stable" release and this is the first one) I would ABSOLUTELY do a clean install and I believe Rohan requires it because of kernel changes and the likes.
Hope all this makes sense and I did not forget anything.

Crappyvate said:
. First thing you should do is a nand backup in recovery (so you have something to go back to if all else fails)
. backup your SD card
. move your nand backup and sd card backup to your computer (that way if your sd gets corrupted you can reformat and push your backups to your device)
. you can also backup your apps + data with something like titanium backup (although now at least in JB if you have chosen this option Google will restore your apps, does not always work for me though so beware)
! Note that Tibu is quite controversial some people love it and swear by it and some people claim that it creates lots of issues, if you decide to use it, only use it to backup/restore user apps and not system apps. I personally use the pro version since it can sync backups to my Box and Dropbox account.
in addition to all of this I backup my sms, call log and custom launcher settings (but that's just me i'm a bit paranoid and I love redundancy)
When you're staying with the same rom you typically don't have to factory reset/clean install (unless of course the dev recommends it), just wipe cache and dalvik in recovery and flash your new rom.zip (don't forget to fastboot flash the boot.img if you're on the latest hboot) in recovery.
If you do not factory reset/clean install you will not loose data fingers-crossed. if you start encountering a lot of weirdness after a dirty flash well you will have to factory reset/clean install. I like to clean install most of the time so that I don't have to try to troubleshoot a bunch of stuff when s**T goes wrong plus it's easier to get support for obvious reasons.
In this particular case Milestone release of AOKP (milestone is a "stable" release and this is the first one) I would ABSOLUTELY do a clean install and I believe Rohan requires it because of kernel changes and the likes.
Hope all this makes sense and I did not forget anything.
Click to expand...
Click to collapse
Sounds excellent!! Yes this helps a ton, I was not sure of what I needed to wipe if anything. Thanks!

dan798 said:
Sounds excellent!! Yes this helps a ton, I was not sure of what I needed to wipe if anything. Thanks!
Click to expand...
Click to collapse
no problem..

Could you define a clean install and the steps?

RC196 said:
Could you define a clean install and the steps?
Click to expand...
Click to collapse
Clean install: The partitions are empty
Proper steps
Wipe System
Factory Reset
Wipe Cache (Optional, Factory reset should have done it already)
Wipe Dalvik Cache (optional, I usually dont wipe and problems dont occur)

RC196 said:
Could you define a clean install and the steps?
Click to expand...
Click to collapse
1.boot into recovery (twrp)
2. go into wipe menu and hit factory reset (DO NOT FACTORY RESET in FASTBOOT) this will wipe everything so backup first (see above post
3. flash the boot.img taken from your rom.zip of choice (this is if you are on latest version of HBOOT)
4. flash your rom.zip
5. reboot in system

Crappyvate said:
1.boot into recovery (twrp)
2. go into wipe menu and hit factory reset (DO NOT FACTORY RESET in FASTBOOT) this will wipe everything so backup first (see above post
3. flash the boot.img taken from your rom.zip of choice (this is if you are on latest version of HBOOT)
4. flash your rom.zip
5. reboot in system
Click to expand...
Click to collapse
Before I did any flashing, I made a backup of my phone of the latest HTC Sense. It was only unlocked and not rooted. That back up is still there. If I wanted I could wipe and restore this backup correct? I would not have to flash anything right?

RC196 said:
Before I did any flashing, I made a backup of my phone of the latest HTC Sense. It was only unlocked and not rooted. That back up is still there. If I wanted I could wipe and restore this backup correct? I would not have to flash anything right?
Click to expand...
Click to collapse
You will have to flash the boot.IMG from your backup and then restore the backup if you want to revert back to it
Sent from my HTC One XL

absolutelygrim said:
You will have to flash the boot.IMG from your backup and then restore the backup if you want to revert back to it
Sent from my HTC One XL
Click to expand...
Click to collapse
How would I get that boot image from the backup on my phone?

RC196 said:
How would I get that boot image from the backup on my phone?
Click to expand...
Click to collapse
You have to extract the boot.IMG to your computer and flash it with fastboot. Then restore the backup
Sent from my HTC One XL

This is what is in the backup folder in TWRP.

RC196 said:
This is what is in the backup folder in TWRP.
Click to expand...
Click to collapse
You can get the boot.IMG from the ruu zip or a 2.20 stock rooted Rom, which is in the one x pinup sticky in the android development section
Edit: boot.emmc.win is the boot.IMG. just rename it to boot.IMG and flash it from fastboot
Sent from my HTC One XL

absolutelygrim said:
You can get the boot.IMG from the ruu zip or a 2.20 stock rooted Rom, which is in the one x pinup sticky in the android development section
Edit: boot.emmc.win is the boot.IMG. just rename it to boot.IMG and flash it from fastboot
Sent from my HTC One XL
Click to expand...
Click to collapse
Oh OK thanks. So I actually didn't screw this part up LOL.:laugh:

absolutelygrim said:
You can get the boot.IMG from the ruu zip or a 2.20 stock rooted Rom, which is in the one x pinup sticky in the android development section
Edit: boot.emmc.win is the boot.IMG. just rename it to boot.IMG and flash it from fastboot
Sent from my HTC One XL
Click to expand...
Click to collapse
yep just rename boot.emmc as boot.img and now you can use this on one xl http://forum.xda-developers.com/showthread.php?t=1963896
makes it a lot friendlier, you don't need to extract the boot.img from the rom.zip, the app does for you and also you don't need a computer, you can do it all from your device

(Q) jellybam 1.3 won't flash

Hi guys. Al thou this is my first post I've been flashing my i9003 for a year or so and i've never had any problems until now.
I have an stock gingerbread installed (XXKPQ) that I flashed using odin, kernel version (2.6.35.7-CL709629 [email protected] #1)
Just so you know, I'm from Argentina, and in order to be able to use 3g, had to keep the modem in I9003LUBKB1 version.
I also flashed cf root (by Skin1980) and I'm using CWM v1.80
I get the latest jellybam (1.3) from this post: http://forum.xda-developers.com/showthread.php?t=1972087
And followed the instructions in the official website : http://www.igio90.net/how-to-install/
Just in case you're too lazy to follow the link here are the instructions:
What to do if you are coming from a Stock, CyanogenMod, MIUI, AOKP and any other custom ROM different from JellyBam
-Download the latest revision of JellyBam ROM for your device
-Place the zip into your internal SDCard
-Boot into CWM recovery (Home+Power+Volume up until samsung logo appear)
-Wipe data/factory reset
-Wipe dalvik cache (Inside advanced tab)
-Install zip from internal SDCard
-Welcome to JellyBam!
(I had to wipe the data first and then put the zip in the sd card because wiping the data was erasing the jellybam zip)
The first time I run the installer it got stuck at 50% while installing sony's media player. So i just started the process again and uncheked sony walkman player, it installed "successfully".
When the phone restarted, it was just the old gingerbread, in the about phone panel, it was all the same that before installing jellybam.
So it obviously didn't installed. I can make calls, send and receive messages, wifi is working fine.
So can anyone tell me what am I doing wrong? Do i have to flash a jellybean kernel?, I dont really know hoe to do that but I'm sure there's more than one post around here that explains that process.
If this question has already been posted I'm really sorry, I did search for any post that could help me with this problem but I didn't find any real answer.
I really hope somebody can help me, and sorry for the bad english, I did study the language but it was a long time ago.
Thanks everybody, specially to developers, you're awesome.:good:

I think you should fist flash theJellyBam v1.1.0 alpha4 in order to repartition before flash the v1.3. hope it can help u.
Sent from my GT-I9003 using xda app-developers app

friend, 1st thing, you need to flash newer cwm to minimum your problem. now is version 6 on CM10 rom.
2nd flash CM rom or AOSP to use jelly bam
Sent from my Galaxy Nexus using Tapatalk 2

flashing 1.1 first worked great.
I'm having issues thou, don't know if this are known bugs or just happens to me.
I can't get any signal, gonna try flashing this:
http://forum.xda-developers.com/showthread.php?t=2029921&highlight=cm10+signal+fix
And seems like the phone can't detect when it's plugged to a usb port

narshade said:
(I had to wipe the data first and then put the zip in the sd card because wiping the data was erasing the jellybam zip)
Click to expand...
Click to collapse
Wiping the data does not affect your Internal/External storage.

chongns said:
friend, 1st thing, you need to flash newer cwm to minimum your problem. now is version 6 on CM10 rom.
2nd flash CM rom or AOSP to use jelly bam
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
First of all thank you for your helpful answer (I clicked the thank you button).
I have cwm version 5 and I have been having the same problem than the OP. I'd like to flash a CM rom before going on to JB 1.3 so my question is, knowing that I currently have an I9003XXKPR 2.3.6 rom, can I flash CM 10 or should I start by a previous version? And, if so, which one?
Thank you for your help.

jawadlotfi said:
First of all thank you for your helpful answer (I clicked the thank you button).
I have cwm version 5 and I have been having the same problem than the OP. I'd like to flash a CM rom before going on to JB 1.3 so my question is, knowing that I currently have an I9003XXKPR 2.3.6 rom, can I flash CM 10 or should I start by a previous version? And, if so, which one?
Thank you for your help.
Click to expand...
Click to collapse
i think you should start from zero. take a backup of your files, flash a stock rom and then use universal cf root to root your phone. then flash cm 10 alpha 4 and then the jellybam 1.3. that's the way i have flashed mine. i hope it helps.

imboy25 said:
i think you should start from zero. take a backup of your files, flash a stock rom and then use universal cf root to root your phone. then flash cm 10 alpha 4 and then the jellybam 1.3. that's the way i have flashed mine. i hope it helps.
Click to expand...
Click to collapse
Thanks for the advice, I flashed a stock rom in the meantime so I am ready to flash CM 10 alpha 4.
Take care

jawadlotfi said:
Thanks for the advice, I flashed a stock rom in the meantime so I am ready to flash CM 10 alpha 4.
Take care
Click to expand...
Click to collapse
Good luck! i hope you flash it correctly! just read and follow the instructions in the cm10 thread thoroughly so you can avoid any problems.

All custom rom unofficial, not compile, but directly modify our base cyanogen
It is recommended to start on a CM10 origin
Example A3 to A4
KPE> LF2> CF-LF2
Wipe Data / Factory Reset. (MUST DO THIS STEP)
Select the CM10 A4.zip from your SD Card and flash.
Auto rebooted into recovery (if it show error mounting / cache, and cant mount in manually mount and storage, do wipe / cache)
Go to Advanced -> Reboot Recovery
Select the CM10 A4.zip from your SD Card and flash again
Go to Advanced -> Reboot Recovery.
Mounts and Storage -> Format dbdata (you would not find this in CWM so just ignor 6)
8. reboot
You can then flash all based on Unofficial Alpha 4
Just do the basic procedure wipe

Retard... Nooob question about custom roms

Hi guys
I got my one S two days ago, and in thursday ive read everything (as usual), did every single faq/tutorial and always got in the same end.. A dead device.
I don't know if I miss something or some "basic" knowing about it, i have a t-mobile one S and nothing wotks except runing the stock t-mobile update.
I'm coming from a long range nexus family (and i love sense, for sure), and i don't know what im doing wrong now.
And yeah, just in case, im runing a t-mobile stock, deodexed, rooted, init.d and optimized stock rom.
Thanks in advance.

can you list the steps?
I flash say CM10.1 like this:
1. download cm10.1 nightly zipfile from get.cm. Check md5sum
2. extract boot.img from above zip file.
3. copy zipfile to my sdcard
5.. boot into recovery ( I use TWRP )
6. install cm10.1 zip file
7. wipe cache and wipe dalvik cache
8. boot into bootloader
9. fastboot flash boot boot.img ( from you PC )
10. reboot and enjoy
My guess is you aren't doing 9). Indeed if you have S-OFF this step can be superfluous.
Three - that's how many posts I predict will remind you to post questions in the other forum

bluebenno said:
can you list the steps?
I flash say CM10.1 like this:
1. download cm10.1 nightly zipfile from get.cm. Check md5sum
2. extract boot.img from above zip file.
3. copy zipfile to my sdcard
5.. boot into recovery ( I use TWRP )
6. install cm10.1 zip file
7. wipe cache and wipe dalvik cache
8. boot into bootloader
9. fastboot flash boot boot.img ( from you PC )
10. reboot and enjoy
My guess is you aren't doing 9). Indeed if you have S-OFF this step can be superfluous.
Three - that's how many posts I predict will remind you to post questions in the other forum
Click to expand...
Click to collapse
Yes, all your steps listed, I've tried all this steps and got a bootloop, with any rom. That's why I make this thread, im starting to feel retarded.

Menelkir said:
Yes, all your steps listed, I've tried all this steps and got a bootloop, with any rom. That's why I make this thread, im starting to feel retarded.
Click to expand...
Click to collapse
Edit the title and remove Nooob!?!? for sure anyone jump in anyone if we missing something! And both my guesses where wrong
Firmware would be the next thing I'd look at - although CM10.1 is pretty tolerant. Please can you post all the text on your boot loader screen?
=> It is a S4 variant, right?

Do you get a success message when flashing the boot.img?

Was going to say..... We are talking S4?
Can't think what else can be wrong
Sent from my Liquid Smooth One S

CyanogenMod has NEVER worked on my HTC One S (S4), didn't matter how many times i wiped the system / cache / dalvik, didn't matter if i booted boot.img (S-ON), it just stayed on the splash screen.
Other ROMs worked though, an I am currently enjoying the hell out of my liquidsmooth ROM and OC kernel (bubba 3.6b). Maybe i just never let CM10 sit long enough...
But if you say that no ROMs work, are you sure you're not using an S3 device?

WCCobra said:
Do you get a success message when flashing the boot.img?
Click to expand...
Click to collapse
Yep
ATSPerson said:
Was going to say..... We are talking S4?
Can't think what else can be wrong
Sent from my Liquid Smooth One S
Click to expand...
Click to collapse
Yes.

Are you wiping system and data in addition to cache and dalvik?
Sent from my HTC One S using xda app

You say you end up with a bootloop, but are you giving the rom enough time to settle? The first boot can take a minutes to complete. I found this with CM when I first started flashing roms
Sent from my Liquid Smooth One S

i usually reboot one more time after initial boot
did you try reformatting sdcard, use a good formatter like sdformatter and do full format

Have you wiped system, cache and done a factory reset before flashing the ROM zip?
Sent from my HTC One S using xda app-developers app

Well I fixed. After a few tries I just format every single partition (even boot), and then flash the zip.

[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 ****