Develop Bugs

Multiple Roms/Kernels

Please, i know this is nooby and you guys hate these questions, but i have searched, and maybe i typed the wrong thing but i couldn't find anything. Basically i just want to know how to flash another custom rom and kernel on my device. i tried yesterday with a kernel and just got the infinite reset loop again, somehow i fixed it by gettinginto fastboot and reflashing the old kernel but i dont want that happening again. with the roms i heard you can just download the zip to the sd storage and install it via CWM but again, i dont want to take any risks, i did pay $600 for this phone after all. thanks in advance, and sorry for the n00bish questions, i just want to be on the safe side.
also while im here so i dont have to make another topic, i have ARHD 9 installed atm, and it was fine when i first installed it but now the softkeys are always lit up, i cant find an option to turn it off in the Suite tools that came installed with it either.

all custom kernels comes with modules. They are in the zip file.
First you need to flash the kernel through fastboot.
fastboot erase cache
fastboot flash boot boot.img
then go to recovery and flash the zip modules.
Reboot your phone and it should boot up fine.
Don't worry you are not going to brick your phone. Before flashing anything always charge your phone to full.
Flashing rom is simple again. copy the zip in sd card.
copy the boot.img of the rom and put it in fastboot folder.
reboot to bootloader.
again fastboot erase cahce
fastboot flash boot boot.img
reboot to recovery.
wipe data/cache, cache and davik.
install the zip through recovery
Reboot and done
while installing custom kernels you need to flash kernel modules through recovery always.
and read the thread properly what kernels supports what roms.
some roms need repacking, that would be too much to learn at once..
jst do the process step by step and you will be fine.

thanks for the help man, much appreciated

try viperx...it has all the steps there as well

faiz02 said:
while installing custom kernels you need to flash kernel modules through recovery always.
and read the thread properly what kernels supports what roms.
some roms need repacking, that would be too much to learn at once..
jst do the process step by step and you will be fine.
Click to expand...
Click to collapse
If it is mentioned in the thread of the specific rom that repacking a kernel is requried before flashing please tell me if I have got the whole order of things to do wrong, I would really appreciate it.
The specific rom has recommended kernels for trouble free running.
I definitely feel that I have confused myself along the way.
- repack kernel with "Automated Kernel Repack Beta" and download boot-repacked.img to computer
- copy boot-repacked.img to fastboot folder
- fastboot flash boot boot-repacked.img
- fastboot erase cache
- reboot into recovery
- wipe factory data > wipe cache partition > wipe Dalvik cache
- flash kernel.zip for the modules?
- flash rom.zip?
- flash additional gapps.zip (rom specific)
- reboot?
Does this look right to you?
Sorry if this is a troublesome question.
Thank you!

Looks good to me. One thing. Boot your new rom once first before installing Gapps.
Sent from my HTC One X using Tapatalk 2

eyosen said:
Looks good to me. One thing. Boot your new rom once first before installing Gapps.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Thank you! I will give it go and will thank you again if all of it works out. Is it possible for the old Gapps to conflict with the new ones I will be flashing. Or will the Factory wipe sort that out.
Also another hypothetical case;
Say the Rom Dev have repacked the recommended kernels, can a problem arise by repacking a kernel with the Rom.zip again? Will the subsequent boot-repacked.img have an issue? And if the modules of the kernel are flashed over modules that the Rom.zip might have, will the modules be overwritten without problems?
Thank you and apologies for the convoluted question!

sidsat20 said:
Thank you! I will give it go and will thank you again if all of it works out. Is it possible for the old Gapps to conflict with the new ones I will be flashing. Or will the Factory wipe sort that out.
Also another hypothetical case;
Say the Rom Dev have repacked the recommended kernels, can a problem arise by repacking a kernel with the Rom.zip again? Will the subsequent boot-repacked.img have an issue? And if the modules of the kernel are flashed over modules that the Rom.zip might have, will the modules be overwritten without problems?
Thank you and apologies for the convoluted question!
Click to expand...
Click to collapse
Gapps, there wont be conflicts.
If you already find them repacked by rom dev, it means that they were tested.so are safer to use. So use them.
As for modules, usually yes. Unless they are on different bases such as 2.6.39 and 3.x.x.x. just do a nandroid backup first, and then try. Enough hypothetical.

[Q] Need Help, Phone stuck on boot up

I have had Cyanogenmod 7 for some time now, but ever since yesterday it is stuck on the Cyanogenmod boot screen and does nothing. I can get into Clockworkmod Recovery, but I am scared to do anything past that for fear of messing something up. Do you all know something I could try to get my phone back working (It is an HTC Inspire on AT&T)
Thanks

Ellimistopher said:
I have had Cyanogenmod 7 for some time now, but ever since yesterday it is stuck on the Cyanogenmod boot screen and does nothing. I can get into Clockworkmod Recovery, but I am scared to do anything past that for fear of messing something up. Do you all know something I could try to get my phone back working (It is an HTC Inspire on AT&T)
Thanks
Click to expand...
Click to collapse
Do you remember anything that happened/changed between when it was working and when it wasn't? S-ON or S-OFF?
Since you can get into CWM, I would just flash a new ROM. In fact, I would first dirty flash the same ROM over the one you've got first to see if that fixes it. If that doesn't work, clean flash a different ROM.

bananagranola said:
Do you remember anything that happened/changed between when it was working and when it wasn't? S-ON or S-OFF?
Since you can get into CWM, I would just flash a new ROM. In fact, I would first dirty flash the same ROM over the one you've got first to see if that fixes it. If that doesn't work, clean flash a different ROM.
Click to expand...
Click to collapse
What's the easiest way of going about this, I haven't ever done anything past the initial root and flash

Just put the ROM to be flashed on the SD card, it's a zip - and then choose to "install from zip" and navigate to it in Recovery. You could find a superwipe .zip file - which cleans all caches etc - on this forum, and that will give you the assurance that your phone is squeaky clean for when you flash the ROM zip file.
Just make sure your phone is - preferably - fully charged. The only thing that can go wrong is the battery running out while flashing .
If for whatever reason it still doesn't get past the bootloop, re-flash or try flashing a different ROM.
There are plenty of really good ROMs for the HD in the ROM sub-forum, for a rock-solid alternative, look at the Android Revolution ROMs.

Ellimistopher said:
What's the easiest way of going about this, I haven't ever done anything past the initial root and flash
Click to expand...
Click to collapse
Download the ROM (make sure it's the exact same version as the one you first flashed) onto your computer. Get the ROM onto your phone, either by using an sdcard adapter or by booting into CWM and mounting the sdcard on the computer. In CWM, wipe cache and dalvik, then install the ROM zip. Reboot. (If you're S-ON, say so; there are a couple extra steps.)
If that doesn't work, do it again with a different ROM. Also, instead of wiping only cache and dalvik, also wipe system and data. You will lose all your installed apps and saved data.
Sorry, but I can't give exact step-by-step CWM instructions because I don't use CWM.

So all I did was reflash the exact same file that I already had on my SD card, and that worked. Cleared the data/caches and I'm back online. Thanks for the help.

Any custom Rom and unable to flash a different kernel. Help please...

I am currently running Leedroid and I sometimes switch to Paranoid Android just to see how things are developing there. Great rom but I cant do without sense camera and like the decent weather app with all its animations.
Back to reason, sorry, I cant change my kernel on neither rom. Just gets stuck on boot animation/loop. Knew problem because I used to be able to change kernels but now just cant. Any idea's to why. Much appreciated - I feel handicapped...

Well, did you repack the kernels AND flash modules?

tomascus said:
Well, did you repack the kernels AND flash modules?
Click to expand...
Click to collapse
Cheers for quick response. :good:Yes, as I said I used to be able to try different kernels but just stopped last dozen attempts. Have tried repacking boot image several times, via online repacker but had no joy. Am i doing something wrong.

veroby said:
Cheers for quick response. :good:Yes, as I said I used to be able to try different kernels but just stopped last dozen attempts. Have tried repacking boot image several times, via online repacker but had no joy. Am i doing something wrong.
Click to expand...
Click to collapse
You put the original boot.img in the source img, correct?
Then repacked, flashed the kernel, erased cache and then rebooted to recovery to flash modules?

tomascus said:
You put the original boot.img in the source img, correct?
Then repacked, flashed the kernel, erased cache and then rebooted to recovery to flash modules?
Click to expand...
Click to collapse
Correct. I have tried erasing cache via command line and I have tried erasing cache via cwm as well. Still no joy
Actually because of desperation I have tried everything in different orders as well. Example- flashing boot image before after flashing kernel. Still doesnt boot and eventually after long wait just loops. This problem is with both roms.

Stock kernel works right?

tomascus said:
Stock kernel works right?
Click to expand...
Click to collapse
Yeap, have had to restore to backups everytime. And they function fine but even tho I am a believer in "if it aint broke don't fix it", I cant help but try and fix wat aint broke. If you know what i mean.....

veroby said:
Yeap, have had to restore to backups everytime. And they function fine but even tho I am a believer in "if it aint broke don't fix it", I cant help but try and fix wat aint broke. If you know what i mean.....
Click to expand...
Click to collapse
Maybe a dumb answer, but i had the same problem. Do you flash in the right order? Do you flash your kernel before or after your rom flash? And you're flashing using fastboot?

KaiseRRUby said:
Maybe a dumb answer, but i had the same problem. Do you flash in the right order? Do you flash your kernel before or after your rom flash? And you're flashing using fastboot?
Click to expand...
Click to collapse
No not dumb, i really appreciate attempt in help. As to right order, have tried right order, fastboot flash boot boot.img with repack and original image to kernel but nothing is working. Just will not allow change kernel. Have tried re-flashing boot image after flash kernel as well. Have tried erasing cache partition with wiping dalvik cache together but no go. Have tried erasing nothing but still boot loop. Any ideas:crying:

veroby said:
No not dumb, i really appreciate attempt in help. As to right order, have tried right order, fastboot flash boot boot.img with repack and original image to kernel but nothing is working. Just will not allow change kernel. Have tried re-flashing boot image after flash kernel as well. Have tried erasing cache partition with wiping dalvik cache together but no go. Have tried erasing nothing but still boot loop. Any ideas:crying:
Click to expand...
Click to collapse
So this is your order:
- Backup
- full wipe
- flash rom
- flash kernel
- flash modules
- restart
?

doesn't matter what order you flash the boot.img, as long as you flash the modules after you flash the ROM.
btw, try another ROM.

ARHD 11.1 jellybean smooth and sense camera full package

tomascus said:
doesn't matter what order you flash the boot.img, as long as you flash the modules after you flash the ROM.
btw, try another ROM.
Click to expand...
Click to collapse
Ok here's what I did, full wipe, Flashed knew copy of Leedroid ( i know you said try another rom but hadnt thought it to be necessary because I was having same problem with Leedroid and Paranoid Android jellybean), kinda custom the rom a little with mods and tweaks. Got a bit ahead of myself because I then fastboot faux kernel boot image and flashed the modules. Gutted BOOt-LooPED...:crying:
Have gone back to my backup Leedroid. At least I know its not the full wipe. Any more ideas welcome.
Forgot to mention I did not repack the boot image until after boot loop. Still did not work.

KaiseRRUby said:
So this is your order:
- Backup
- full wipe
- flash rom
- flash kernel
- flash modules
- restart
?
Click to expand...
Click to collapse
Ok here's what I did, full wipe, Flashed knew copy of Leedroid, kinda custom the rom a little with mods and tweaks. Got a bit ahead of myself because I then fastboot faux kernel boot image and flashed the modules. Gutted BOOt-LooPED...
Have gone back to my backup Leedroid. At least I know its not the full wipe. Any more ideas welcome.
Forgot to mention I did not repack the boot image until after boot loop. Still did not work.

veroby said:
Ok here's what I did, full wipe, Flashed knew copy of Leedroid, kinda custom the rom a little with mods and tweaks. Got a bit ahead of myself because I then fastboot faux kernel boot image and flashed the modules. Gutted BOOt-LooPED...
Have gone back to my backup Leedroid. At least I know its not the full wipe. Any more ideas welcome.
Forgot to mention I did not repack the boot image until after boot loop. Still did not work.
Click to expand...
Click to collapse
Well, the best way to do it as far as i know is:
-boot.img flash (the one included in rom)
-wipe
-flash rom
-reboot
-wait for 10 minutes
-rebooten (full reboot again)
-reboot to fastboot
-boot.img flashen (custom kernel)
-modules flashen (custom kernel)
That 's how things work by me, you can try this?

KaiseRRUby said:
Well, the best way to do it as far as i know is:
-boot.img flash (the one included in rom)
-wipe
-flash rom
-reboot
-wait for 10 minutes
-rebooten (full reboot again)
-reboot to fastboot
-boot.img flashen (custom kernel)
-modules flashen (custom kernel)
That 's how things work by me, you can try this?
Click to expand...
Click to collapse
Yeah understand, I used to be able to just fastboot flash kernel boot image, flash kernel modules via cwm and bobs ya uncle. Done. But no more. Guess I'll have to wait until i jump ship and update firmware to 1.28 for JB roms and re-format or something. Cheers anyways..

[Q] Help with installing custom rom

Hey guys,
I'm new to the Xperia Arc development and need some help with installing a custom rom. I've done quite a bit of reading but still can't figure out what is wrong and why it's simply not working.
So from what I gathered the steps to ensure a successful flash are:
Firstly flash a stock rom via flashtool ie LT18i_4.1.B.0.587.ftf
flash LT18i_4.1.A.0.562_Kernel > root the device > flash back to LT15a_4.1.B.0.587_Kernel
Then now that the device is rooted, I need to install a recovery such as CWM via RecoverX
So, so far so good as I can access CWM, stock rom works fine as well
So then next step is to unlock the bootloader
pretty sure this worked, as when i tried to unlock it again, it said it failed as it was already unlocked
Now flash a custom kernel, in this case i flashed the 146 FXP CM kernel
This also seemed successful as I was presented with a custom splash screen
So then after custom kernel is installed I enter recovery, wipe the cache and reset factory settings, format the data system and cache as well as wiping the dalvik and battery stats.
After, I installed the custom rom zip file, in this case it was aokp_anzu-ota-eng.kxp_build5 and then google apps and then reboot.
So my problems begin here.
My phone seems to be stuck in the boot process (sometimes), on the "initiating swagger" splash screen and it goes crazy. I've tried flashing this rom with other kernels (fusion 3.9) and sometimes it actually loads up into the rom. But the rom is extremely laggy, applications freeze and close and the wifi never works
So my question is, is there any steps or procedures that I am missing, not doing right or in the correct order?
I don't think it's any hardware issues as wifi works in the stock rom, and it's fairly smooth and fluid.
Also, is there a better way to flash roms so that I don't need to do this entire process of flashing a stock rom, rooting, unlocking bootloader, installing recovery every time I want to flash a new rom? And when I flash a custom kernel first, then flash a custom rom that has a kernel inbuilt (cm10) does the custom rom's kernel replace the one i just flashed, reason for asking is that the instructions say to flash the custom kernels and then the roms, but yeh just hasn't been working for me so not really sure how to do what.
I'd really appreciated any help or insight!
Thanks

http://forum.xda-developers.com/showthread.php?p=18445331#post18445331

XperienceD said:
http://forum.xda-developers.com/showthread.php?p=18445331#post18445331
Click to expand...
Click to collapse
Thanks! I've read your guide (what I based my flashing on) and it seems consistent with what I have done, on the surface of it anyway. If you think I missed or overlooked something, would it be possible to point it out?

If your boot loader is unlocked it's as simple as this...
1. Flash kernel
2. Wipe cache etc
3. Install ROM
...I always reboot before installing anything else as I've found it can break the installation of the ROM.

XperienceD said:
If your boot loader is unlocked it's as simple as this...
1. Flash kernel
2. Wipe cache etc
3. Install ROM
...I always reboot before installing anything else as I've found it can break the installation of the ROM.
Click to expand...
Click to collapse
As ExpirienceD says,just one more thing flash kernel modules if you need to.
So:
1.Flash kernel
2.Full wipe data/cach...etc...
3.Flash ROM
4.Flash kernel modules
Sent from my LT15i using xda premium

[Q] Another noob with a bricked HOX

At the moment it's on a bootloop with the HTC screen, although I've managed (just now) to flash CM10 which is now stuck on a loop of the CM10 Android splash screen
I'm feeling confident that this can be sorted as I can access phone through fastboot/adb and can mount the SD so all isn't lost... I'm on UK O2 HOX
Just looking for a little direction, I used to be fairly confident around the inside of my old HTC desire, but lost interest... Things are rather different with the HOX and I suspect I've maybe screwed up with some misguided bravado...
Mr Hofs has provided some excellent learning material on his responses to issues similar to mine but to no avail...
I've tried a lot of things, bootloader is unlocked, flashed boot.img and recovery.img but when I flashed x.xx.206.x - O2 UK (United Kingdom) firmware.zip with hboot 1.36 it said it failed (with no information as to why)
Just looking for pointers on where to go next!
Starting to become concerned I've made a proper mess...

mathesonewan said:
I've tried a lot of things, bootloader is unlocked, flashed boot.img and recovery.img but when I flashed x.xx.206.x - O2 UK (United Kingdom) firmware.zip with hboot 1.36 it said it failed (with no information as to why)
Click to expand...
Click to collapse
Additional to this - I've been through 10-12 pages of various fixes (searched bootloop within HOX forum) that's why the above is a little vague... They've all merged into one...

1: what hboot do you have now ?
2: what recovery are you on ?
and put the phone in the recovery in the mean time. it charges the battery there

Are you flashing cm10 or cm10.1 'cause cm10 does not support hboot 1.36.

Recovery is TWRP v2.4.1
HBoot is 1.36
and I'd read that somewhere about not supporting 1.36 and I've just checked it's 10.1 I was trying to flash

Everything sounds good to me.
Try again with my instructions:
1. Flash boot
2. Full wipe
3. Flash rom
4. Flash gapps
It should boot.

Yep....and otherwise the way around ! because i helped somebody on team-V ...it didnt work the way TT described. but actually did work the other way around
in recovery a full wipe....
install the rom and gapps
adb reboot bootloader
and flash the boot.img followed by
fastboot erase cache
fastboot reboot

TToivanen said:
Everything sounds good to me.
Try again with my instructions:
1. Flash boot
2. Full wipe
3. Flash rom
4. Flash gapps
It should boot.
Click to expand...
Click to collapse
Mr Hofs said:
Yep....and otherwise the way around ! because i helped somebody on team-V ...it didnt work the way TT described. but actually did work the other way around
in recovery a full wipe....
install the rom and gapps
adb reboot bootloader
and flash the boot.img followed by
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Right I'll try these out - If TTs method isn't successful is there anything I would need to be aware of inbetween these two methods? Or are both pretty much starting from scratch? (I hope you understand what I mean..?)

mathesonewan said:
Right I'll try these out - If TTs method isn't successful is there anything I would need to be aware of inbetween these two methods? Or are both pretty much starting from scratch? (I hope you understand what I mean..?)
Click to expand...
Click to collapse
TToivanen said:
Everything sounds good to me.
Try again with my instructions:
1. Flash boot
2. Full wipe
3. Flash rom
4. Flash gapps
It should boot.
Click to expand...
Click to collapse
I've expanded on the above steps to ensure I'm completing them correctly
1. Extracted the boot.img from the firmware zip contained within the CM10.1 zip, then ran fastboot flash boot boot.img from cmd line - this completed and reported "OKAY"
2. Full wipe done using TWRP - system wipe - for good measure wiped everything else too (wasn't sure if system was a catch all for the others or not)
3. Rom Flashed using TWRP install cmd (I've assumed this is the correct way to do it...)
4. Flashed Gapps similarly
It's now past the HTC "quietly brilliant" splash (very very quiet just now...) and is stuck on the CyanogenMod splash just circling round and round...
Going to try the other method see if I have anymore luck!

OK... So haven't had any luck with either method...
When flashing the boot.img it's behaving differently to how it did before - it now triggers the phone to reboot whereas it never did before... Is that normal?
Is there any more information I can give you guys that might narrow down the issue?
Thanks in advance!

i would try a stanrd sense based rom ..... just to check its all fine, i have seen more people that didnt get it booted, why ? no clue....
did a proper wipe....factory reset,wipe caches, dalvik cache, data, system ?
then it should work !

Just downloading the stock rom just now, going to try from there... At this point in time I'll be happy to just have a working phone!

Success!
I tried going back to the stock rom but something mad happened with the recovery (i.e. it didn't work anymore) and was replaced with a graphic of a flat HOX with a sync symbol and then the sync symbol was replaced by a red cross...
So had a minor panic, realised that something wasn't right with TWRP, so flashed on CWM, then flashed the boot.img from the stock zip, and flashed the rom perfectly.
I'm tempting fate but I started this process wanting a new rom and I will finish it, but I'm glad my phone isn't bricked!
Thanks to you both for your input, your faith certainly encouraged me to not give in!
Keep up the awesome work!

Well you can always try again to install CM10.1.....again but now with cwm.

I went with viper - which has flashed successfully, but everytime I unlock the screen it comes up with a white HTC screen... haha time to start trawling the viper forum... or go for CM again!

Strange.....tho i have the idea you missed something in the wiping process ?

Funnily enough for a "low stress" option I wiped everything (CWM > advanced > wipe em all) then reflashed the boot.img from CM10.1, then flashed the rom and it's loading into CM10 but repeatedly flashes "unfortunately the process com.android.phone has stopped"
There is something funny going on if no custom roms are working no?

Wipe data/factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache,data,system
That should do it.....

ohhhhh the mounts and storage one is new to me... I'll try that now with a custom...

Meh didn't work... I'm going to reflash the stock and go to bed I think!