Database Develop

[Q] Switching to Sense Rom to update PRL, etc

I'm trying to flash a sense ROM to update my PRL. I'm currently using:
Jaybob's TeamHeroC Rom, the .35 kernal
Firerats 1.5.8 Partition mod
The issue I'm running into is once I install a sense ROM (have tried NFX and Liquidsense so far) I get a never ending white HTC screen, have to pull the battery and back up using Nandroid.
The order I've been trying to do things:
Wipe, Clear cache and Dalvik
Flash Remove 1.5.8
Wipe, Clear Cache and Dalvik
Reboot Recovery
Flash Sense ROM
White screen/won't boot
From there I have to battery pull, wipe, re-flash Firerats and do a nandroid restore to get back where I was. I'm pretty sure I'm leaving out a step, so I was wondering if anyone could give me a clue on what I'm leaving out.

Is it safe to assume u didn't save a backup of ur original ROM right after u rooted ur hero?
If u did then go there to do the prl update.
If not then, try "fresh ROM" first, then try liquid sense or nfx...
But you may to factory reset twice, then under CMR recovery go to mounts and storage and format all but SD card stuff. Most recommend to do it twice .... just to make sure.
Now flash the ROM by itself since u don't need to sign in for anything so no need to flash gapps if ROM doesn't already have it.
Are you using any tweaks perhaps, firerat's? If so I've read that there are issues with that if your system is partitioned too small.
Good luck
Good luck!
Sent from my HERO200 using Tapatalk

When going from an AOSP ROM to Sense and vice versa you format boot, cache, system, data and dalvik cache.

vidaljs said:
Are you using any tweaks perhaps, firerat's? If so I've read that there are issues with that if your system is partitioned too small.
Click to expand...
Click to collapse
Yes, using the Supercharged V6, 3G Supercharger, KAK and Firerats.
I flash the fr-remove before flashing the new ROM. Taking care to format everything had the same results, as did flashing my old backup just after I rooted. I haven't tried flashing another ASOP rom or CM7, but so far it seems I can only restore my most recent backup.

oldredhat said:
Yes, using the Supercharged V6, 3G Supercharger, KAK and Firerats.
I flash the fr-remove before flashing the new ROM. Taking care to format everything had the same results, as did flashing my old backup just after I rooted. I haven't tried flashing another ASOP rom or CM7, but so far it seems I can only restore my most recent backup.
Click to expand...
Click to collapse
Firerats is the issue. Your /system partition is currently too small. I've never had good luck with FR-remove. Re-flash your recovery image prior to flashing Sense. I triple format my /boot, /system, /data, /cache, and Dalvik cache using Clockwork receovery as well. Thank goodness I don't have to do that very often!

[Q] Installing custom kernel = boot loop

Hello, when i try to install custom kernel i face a boot loop. I only tried with v10, not tried with v20 though. Tried 3 different kernels and the same. Why is that? It just doesn't work.
And can you tell me some working custom kernel for v20l to try?
Thanks in advance.

What rom are you using?
For myself, usually its an issue of partition beinh ext3 or ext4 that will cause bootloop. I will usually try back2ext3 from paul or ext4 converter.. either one usually fix the bootloop depending on kernel requirements.
Cheers!

Not enough details. Which kernel?
On total stock ROM or on custom stock based ROM?
We are talking about kernel do don't use what is mentioned just above, it will wipe your all system.

I had a boot loop problem after installing a custom ROM based on stock ROM. I didn't wipe the phone before updating to custom ROM. After recovering the original ROM, I wiped the phone from CWM and then updated it and all works well now.

Well i have tried Neoblaze, HorsePower, Spica. I don't wipe after/before installing.
I om on stock rom. Then i must go back with back2ext3.

Striatum_bdr said:
Not enough details. Which kernel?
On total stock ROM or on custom stock based ROM?
We are talking about kernel do don't use what is mentioned just above, it will wipe your all system.
Click to expand...
Click to collapse
Sorry if I misunderstood the original question and thanks for clarifying!

martinesko36 said:
Well i have tried Neoblaze, HorsePower, Spica. I don't wipe after/before installing.
I om on stock rom. Then i must go back with back2ext3.
Click to expand...
Click to collapse
After installing the kernel try wiping cache and dalvik and see if that helps.

that's your problem, you have to wipe cache and dalvick cache after flashing. hope this can help

Thanks you, im very happy - working now. Flashed HorsePower.

Does Flashing a Custom Kernal Using Orange Fox Recovery Leads to Bootloop ?

Chroma rom not flashing

Hello, I am trying to flash Chroma rom for my Verizon Nexus 6 but it boots back to the twrp home screen and does not flash the rom. I wipe the phone and the dalvik cache and all that. I was running Blisspop which encrypted my phone I believe. I wiped the phone and tried to flash Chroma and it would just reboot to the twrp home screen. I restored my nandroid backup of my stock rom still being rooted and it still will not flash. Have tried other roms and the only rom it would flash is blisspop. I am currently on the stock rom with franco kernel. Anybody know what is causing the issue? Thanks in advanced.

manofsteel718 said:
Hello, I am trying to flash Chroma rom for my Verizon Nexus 6 but it boots back to the twrp home screen and does not flash the rom. I wipe the phone and the dalvik cache and all that. I was running Blisspop which encrypted my phone I believe. I wiped the phone and tried to flash Chroma and it would just reboot to the twrp home screen. I restored my nandroid backup of my stock rom still being rooted and it still will not flash. Have tried other roms and the only rom it would flash is blisspop. I am currently on the stock rom with franco kernel. Anybody know what is causing the issue? Thanks in advanced.
Click to expand...
Click to collapse
Make sue you have the latest version of TWRP (2.8.6.0) ALso try redownloading the ROM, may you have a bad download?

Are you also wiping system doing a full wipe coming from another rom

Yes, I have the latest version of TWRP. I will try redownloading the ROM. And yes I am wiping the system before trying to flash.

Flashing other roms than Andro X doesn't work

I just updated my bootloader and whenever i try to flash a rom, the booting process takes forever until i wipe my phone myself. But when i flash Andro X rom than it takes max. 3min to boot and then it works.
But i want another rom, how do i fix this?

Do you mean that when u flash lollipop based rom it gets bootloop? if yes then first flash stock lollipop firmware and then try flashing other rom. I mostly wipe my internal storage when going from Kitkat to lollipop it works for me.

Well Firstly Explain your problem clearly (I didnt quite understand it)
OK so here's my solution from what I understood..
1. Restore your stock rom Backup from recovery. Boot it once.
2. Now clean flash (Wipe System, Data , Cache, Dalvik cache) a lollipop based Rom (preferably try to clean flash cm 12.1 build)
3. Dont flash Gapps. First see if your phone boots up properly.
4. Configure data and reboot to recovery and flash Gapps.
If you dont have a Stock backup, Then download Stock Firmware images from gregor's thread and install via fastboot. Then follow from step2.
Hope this helps you.

Haroun16 said:
I just updated my bootloader and whenever i try to flash a rom, the booting process takes forever until i wipe my phone myself. But when i flash Andro X rom than it takes max. 3min to boot and then it works.
But i want another rom, how do i fix this?
Click to expand...
Click to collapse
Use easy installer first and get stock lollipop then u can simply root and install recovery then try roms?

sagar846 said:
Well Firstly Explain your problem clearly (I didnt quite understand it)
OK so here's my solution from what I understood..
1. Restore your stock rom Backup from recovery. Boot it once.
2. Now clean flash (Wipe System, Data , Cache, Dalvik cache) a lollipop based Rom (preferably try to clean flash cm 12.1 build)
3. Dont flash Gapps. First see if your phone boots up properly.
4. Configure data and reboot to recovery and flash Gapps.
If you dont have a Stock backup, Then download Stock Firmware images from gregor's thread and install via fastboot. Then follow from step2.
Hope this helps you.
Click to expand...
Click to collapse
My problem is that when i try to flash roms like CM12, Blisspop it doesn't stop booting, it was taking more than an hour so i shutdown my phone and when i flashed Andro X the booting took around 3mins.
So can anyone explain in easy steps how to fix this?

OK now I understand what your problem is. Give me your full specs (like which Model and and stuff). But if you follow what I said above it might fix your problem.

sagar846 said:
OK now I understand what your problem is. Give me your full specs (like which Model and and stuff). But if you follow what I said above it might fix your problem.
Click to expand...
Click to collapse
I got the XT1068

Haroun16 said:
I got the XT1068
Click to expand...
Click to collapse
are you fully wiping cache and userdata (factory reset) because this is most common problem moving between Roms that causes bootloops and why I include factory reset in my easy installer.
you can only dirty flash when going up (upgrading) the same rom - changing roms or downgrading nearly always causes bootloop / hang.

Chainfires boot image question

Hello everyone a nexus 6 user here since february and i have a quick question. whenever I flash a new rom I always wipe everything including the internal. I use a usb otg to flash. the question i have is i have yet to flash chainfires boot image. If i flash like i normally do by wiping everything including the internal every time do i have to reflash the boot image each time? or is it a one time thing?

the_rooter said:
Hello everyone a nexus 6 user here since february and i have a quick question. whenever I flash a new rom I always wipe everything including the internal. I use a usb otg to flash. the question i have is i have yet to flash chainfires boot image. If i flash like i normally do by wiping everything including the internal every time do i have to reflash the boot image each time? or is it a one time thing?
Click to expand...
Click to collapse
i have yet to use chainfires boot.img as well. instead, i use any of the custom kernels from the n6 forums instead. but anyways, when you wipe, you only wipe your usrr data. so you would not have to replace it. now, if you wiped system, that would wipe everything, including your rom. if you wipe system, then you have to reflash your rom and kernel(boot.img). btw, boot.img is the kernel.

simms22 said:
i have yet to use chainfires boot.img as well. instead, i use any of the custom kernels from the n6 forums instead. but anyways, when you wipe, you only wipe your usrr data. so you would not have to replace it. now, if you wiped system, that would wipe everything, including your rom. if you wipe system, then you have to reflash your rom and kernel(boot.img). btw, boot.img is the kernel.
Click to expand...
Click to collapse
Well from the issues I am having and questions asked. For marshmallow u need to flash the boot image before u flash most kernels. I tried and keep getting boatloads without doing the boot image

the_rooter said:
Well from the issues I am having and questions asked. For marshmallow u need to flash the boot image before u flash most kernels. I tried and keep getting boatloads without doing the boot image
Click to expand...
Click to collapse
i didnt use his boot.img. again, boot.img and kernel are one and the same. what i did was flash despair kernel right away, then supersu 2.52. booted up roght after with root. anyways, your answer is that his boot.img doesnt get wiped unless you flash another rom, or the same rom again. then itll get wiped.

boot.img and kernel are not the same thing.
boot.img = kernel + ramdisk

stokholm said:
boot.img and kernel are not the same thing.
boot.img = kernel + ramdisk
Click to expand...
Click to collapse
ok, technicality.. not all custom kernels have their own ramdisk, like any of the anykernel kernels.