I currently have busines gingersense ,which by the way is sweet ,thanks Nills ,I have my stock Rom backed up w/ amon ra. Now if I want to try business ICS and then go back to gb, will I be able to reload in recovery like any other Rom or does this require special steps, I have read about other ics roms not being able to recover so easily, if so would anybody care to do a step by step. Thanks ...
Sent from my ADR6425LVW using XDA App
You need to flash the stock kernel to use GB ROMs if you have used an ICS ROM (a copy is located in scotts GB based ROMs, just unzip the file and find the boot.img)
You can flash the kernel before or after you restore the backup.
I find it easier to do before, then selecting the reboot to recovery option, allowing me to then flash the new ROM or backup.
Use the cleanflash tool to flash the kernel (boot.img) if you need a simple method.
Is the boot.img that needs to be flashed from rom to rom different? If it is not, does it need to be flashed bevery time a different rom is loaded or just once? I have installed about 3 different roms each requiring boot.img due to S-on and am curious if each is specific to their respective rom's
When switching roms use the boot.img that came with it. After booting into the new Rom then you can go back and install another kernel. If you're moving from one version of a Rom to another you usually don't need to flash a new kernel.
Hello all, I was running Dual boot with stock sammy as primary and cm as secondary. Tried to reboot into primary and got the cm boot ani loop. Wiped to get primary to boot which it does but I now have 2 installs of CM. I must have made a mistake when updating CM and flashed it to the primary. Now I want to get stock sammy back as primary or secondary and want to know what the easiest way to do this would be. I have my stock rom from samfirmware but want to know how to flash the rom part only using either mobile odin or cwm. I have searched and could easily flash whole new rom in odin PC or mobile and start again but I would like to avoid this if possible. If I am in my primary rom and choose package in mobile odin can I just flash rom only? would that be system? and would this flash to the primary only? or can I get hold of a package to flash via CWM to the primary rom.
This could have all been avoided by KEEPING REGULAR BACKUPS!!!!!!!!!!!!!!!!
All help is appreciated and big thanks to all those involved in dev for gt i9300
Ok so flashed to system from samfirmware download using odin mobile. It flashed OK but primary still boots into cm 10.1. FAIL. I am thinking I need a cwm flashable stock rom so I can flash it in siyahs dual boot recovery. Any ideas? Thinking it may be easier to flash stock rom, root, kernel, second rom all over again.
Would the following work as a way to try out, for example Cyanogenmod 10. I am currently running a 4.1.2 install (pretty much stock just rooted/cwm via Philz as per the tutorial). I have a complete backup made via Philz recovery of this rom along with the kernel (which I believe is still stock from that) and efs.
1) Install a custom kernel (eg. dorimanx 9.x?) via the Philz recovery.
2) Install cm-10.2-20140102-NIGHTLY-i9100.zip.
3) To return to the original rom, reflash the original kernel (with whatever CWM is included in dorimanx) - then reflash the backed up rom via the same recovery?
I hope this is clear enough a question.
I believe you have to flash a stock rom through Odin, to return to complete stock. Just flashing a stock kernel isn't enough, and is surely not going to work (so don't do it).There are also tutorials how to remove the yellow triangle afterwards.
Please correct me if I'm wrong
Donnie Sins said:
I believe you have to flash a stock rom through Odin, to return to complete stock. Just flashing a stock kernel isn't enough, and is surely not going to work (so don't do it).There are also tutorials how to remove the yellow triangle afterwards.
Please correct me if I'm wrong
Click to expand...
Click to collapse
This is the part I'm most unsure of. Ideally I'm trying to figure out the process that lets me go from CM10.2 (and whatever recovery) to the point I am running the backed up rom rooted with PhilZ-cwm6-XWLSW-XEU-5.06.1-signed.zip again. Very confused on how to do so.
TopherBrink said:
This is the part I'm most unsure of. Ideally I'm trying to figure out the process that lets me go from CM10.2 (and whatever recovery) to the point I am running the backed up rom rooted with PhilZ-cwm6-XWLSW-XEU-5.06.1-signed.zip again. Very confused on how to do so.
Click to expand...
Click to collapse
Topher,
If you have rooted and cwm via philz, you already have a modified kernel installed. I believe the philz-cwm6 should be as close to stock kernel with the CWM incorporated. You don't need to add another kernel, because it will be replaced when you install the custom ROM. You should just be able to flash the cm10.2 via philz or via odin. You can then flash the dormanix kernel if you want - can't comment on that kernel - or if it has cwm included.
I would also suggest that you consider backing up you /efs folder (one with you imei information etc) prior to flashing any custom roms. People have been using hcKtool to do the backups and also an actual copy as well.
Depending on the custom rom, you may have connection problems with your network. So you may want to consider keeping a copy of your modem.bin file from your stock rom handy in case you need to flash onto the custom rom.
If you want to go back to stock, then you just need to flash the stock rom - you can check sammobile website for your stock rom or use the backup that you made.
I should point out that I have yet to do any of the above - I gathered this from reading the forums. Some more experienced forum users can add corrections. I rooted my phone a couple of months ago and now considering installing custom rom in the next couple of months.
Thanks.
if u flash a custom rom (cm10.2 for example), it already included kernel as well. so if u want to try out other custom kernel, i can flash it after you are done flashing a custom rom but make sure it is compatible with your android version. (u cant use custom kernel that not support android 4.3 with a custom rom running android 4.3)
Hello ,
since two days i am trying to install a custom rom on my htc desire x. I repeated every single step several times to make sure everything still is fine.
(unlook, flash boot, flash recovery / tried twmp and cwm, etc..)
The only rom which works for me ist the cM10-2-20138004-unofficial. But with restrictions. WLAN doesn't work, media manager isn't starting. Cant hear the partner when calls are incoming.
I tried mySense, Half_Sense, myOnedx, but after finishing installation the device hangs on startup. I waited hours and minutes but nothing happened.
I tried several RUU´s but can't find the right ones for me, or i got the 155 error message.
There is no OS installed on the device. How can i get the device up an running? I would be really happy if somebody can give me a hint whats going wrong.
Thx in advance
Dont worry all ****s can be fixed.Wha is ur hboot ? Or simply before to try to install custom rom U was with ICS rom or JB ?.You have to use the right recovery.Look what rom you want to flash, if you on ics hboot u cant just flash jb room (Some roms already have this funcion)
Ps:
After flasing the rom go in boothloader and flash boot.img And away do full wipe
What you need to make sure when installing a ROM: Install a suitable kernel. When installing a Sense ROM, install a Sense custom kernel or the stock kernel. Installing CM isn't advisable, because it's not ready for daily use yet. Also, make sure you use the right recovery for right hboot.
Good Morning,
thx for reply. I want to install the myOnedx_RC4.0 FX. I extracted the boot.img from zip. Installed the rom, wiped, reboot and installed the boot.img.
But that failed. Again, the cyanogen start up occurs for hours and hours. The device doesnt start.
Also tried the same wir the mySENSEdx5_RC4
I evem tried to install the nexuskernelv3.img
I am on hboot 1.25.002
Anyone an idea what wrong with my installation?
Thx
Again: Which custom recovery are you using? Please post a link to the thread here, so we can see what you've installed. Also, as first time user, you should check this and this.
Sorry i forgot. I am using TWRP 2.6.3.0 as custom recovery
Ok, strange, as this one works for me without problems. However, try the 2.5.0.0 version for JB and see if it goes without problems then. Also be sure to wipe system, dalvik cache, cache and data partition before installing a new ROM.
Same with version 2.5.0.0. I tried clockworkmod recovery, but as soon as i try to wip i got the error messages:
cant mount cache/recovery
cant open cache/revocery
So how can i get back to a stock rom? I tried the way described in here: http://forum.xda-developers.com/showthread.php?p=41327224
, but restore failed.
Any other ideas?
If you want to get back to stock, you need to know your CID first. After that, check this thread: http://forum.xda-developers.com/showthread.php?t=2324815
As you have JB hboot, you need to restore a JB backup. In the thread I linked you to are backups of several CIDs. If yours isn't there, you won't be able to return to stock.
Ok thanks. So it is not in there. I got the cid VODAP102.
Does that mean my device is gone? Or can i even try other workarounds?
Thanks
So i installed odexed rom and this one works fine. Do not know why all the other roms not working to me.
Maybe anyone an idea.
Otherwise thanks for your support.
Lastmenstanding said:
Does that mean my device is gone? Or can i even try other workarounds?
Thanks
Click to expand...
Click to collapse
Your hboot : 1.25.0002
Recovery to flash - JB recovery download from here : http://d-h.st/VjM
fastboot flash recovery command : fastboot flash recovery recovery.img
For a test ROM to flash, flash this stock ROM : http://forum.xda-developers.com/showthread.php?t=2239511
also make sure to fastboot flash boot boot.img
(boot.img is attached on OP)
Once everything run, it is up to you to try any other ROM and any other boot.img
Lastmenstanding said:
So i installed odexed rom and this one works fine. Do not know why all the other roms not working to me.
Maybe anyone an idea.
Otherwise thanks for your support.
Click to expand...
Click to collapse
It's either you flash ROM with wrong recovery type or wrong boot.img type or ROM which is not supported on your hboot.
Simple rules:
1) Recovery must be a recovery for JB.
2) Correct boot.img for correct ROM
ICS ROM that support hboot 1.25.0002
Recovery : JB recovery is a must
Boot.img : ICS boot.img is a must
JB ROM which should run fine on hboot 1.25.0002
Recovery : JB recovery is a must
Boot.img : JB boot.img is a must
ICS ROM that does not support hboot 1.25.002 - you need to manually change the mountpoint in updater-script, then
Recovery : JB recovery is a must
Boot.img : ICS boot.img is a must
Yeah, that was the problem, I see now... Have been blind a bit... The ROMs OP has installed on his phone are all ICS ROMs which need changing of updater-script mountpoints. That's why they won't work. @Lastmenstanding: Try any JB ROM available in Android Development section, should work without problems. The ROMs you tried were ICS ROMs especially written for ICS hboot, that's why they didn't work on your phone.
dansou901 said:
Yeah, that was the problem, I see now... Have been blind a bit... The ROMs OP has installed on his phone are all ICS ROMs which need changing of updater-script mountpoints. That's why they won't work. @Lastmenstanding: Try any JB ROM available in Android Development section, should work without problems. The ROMs you tried were ICS ROMs especially written for ICS hboot, that's why they didn't work on your phone.
Click to expand...
Click to collapse
OP mentioned about installing my ICS ROMs. Both ICS ROMs work on JB hboot without a need to edit the updater-script. My guess is he either use wrong recovery (ICS recovery is wrong) or wrong boot.img (JB boot.img is wrong) as it should be JB Recovery and ICS boot.img
..do not know how to use the thank meter, but..
Thank you guys for your excellent support.
Lastmenstanding said:
..do not know how to use the thank meter, but..
Thank you guys for your excellent support.
Click to expand...
Click to collapse
Just thank them at the bottom of their posts...
There is a thanks button at the bottom of every post.