Database Info

[Q] Bootloop on Splashscreen / Don't know what to do

Hi guys,
im really desperate here, my sensation xe (hboot 1.23, s-off), won't let me boot any flashed rom.
My firmware is 3.32 and im using 4ext recovery 1.005 RC3.
Even my Nandroid backup of ARHD 6.6.3 won't boot, the phone gets stuck in a bootloop (it does't even show the boot animation, only the splashscreen for a few seconds, then reboots).
i bet someone on here can help me, because i don't know what to do.
thank you in advance
best regards
el

If your hboot is 1.23 then you DO NOT have 3.32 firmware. Re-flash the firmware and try to reboot...
http://forum.xda-developers.com/showthread.php?p=21711154#post21711154

GROGG88 said:
If your hboot is 1.23 then you DO NOT have 3.32 firmware. Re-flash the firmware and try to reboot...
http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
Click to expand...
Click to collapse
thanks for your reply, yeah i wasn't sure about the firmware since i did't know how to check without rom
i will reflash firmware and see if it boots ...brb.
thanks again for your reply

GROGG88 said:
If your hboot is 1.23 then you DO NOT have 3.32 firmware. Re-flash the firmware and try to reboot...
http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
Click to expand...
Click to collapse
i reflashed the firmware, formatted all partitions in recovery, and flashed ARHD, but no luck i'm still stuck in a splashscreen bootloop.
the recovery (after flashing arhd) prompted something like "boot update pending, will reboot after update is finished"
maybe there is a problem with the latest rc of the 4ext touch recovery?
thanks again for your help

Are you definitely s-off, or are you simply *unlocked*? Also, did you run the superwipe script?

GROGG88 said:
Are you definitely s-off, or are you simply *unlocked*? Also, did you run the superwipe script?
Click to expand...
Click to collapse
i don't know
when i turn it off by pulling battery and then turn it on by pressing vol down and power (i think thats fastboot?) the second line from the top says S-Off RL

Ok, that's s-off.
Did you run superwipe?
Did you run an md5 checker on all of your files?
Is it still reading 1.23 on hboot? (should be 1.27.1100)

GROGG88 said:
Ok, that's s-off.
Did you run superwipe?
Did you run an md5 checker on all of your files?
Is it still reading 1.23 on hboot? (should be 1.27.1100)
Click to expand...
Click to collapse
if by superwipe you mean flash a file that's named superwipe, no i didn't.
i chose format all (except sd) in the 4ext touch wipe menu.
i did run an md5 check on all files.
the hboot version number says 1.27.1100.
i just reflashed recovery from fastboot to see if it helps (altough i flashed the same recovery version, so maybe theres some kind of bug?) but it is still stuck on splashscreen.
aww man i'm really desperate right now, i kind of need this phone because i have no replacement

Go to ARHD thread, download the superwipe script, flash it from recovery, and then flash ARHD again...

GROGG88 said:
Go to ARHD thread, download the superwipe script, flash it from recovery, and then flash ARHD again...
Click to expand...
Click to collapse
did it, flashed arhd afterwards, didn't work.
still stuck on splashscreen.
thank you so much for your help! any other idea?

I'm going to lunch. I'll ponder on it...

okay i got it working and here is what i did:
it seems 4ext recovery was trying to flash a messed up boot image over and over again.
i pulled the boot.img from the arhd zip file and flashed it via fastboot. it now seems to boot (it has gone past the splashscreen and now shows the boot animation).
thanks again for your.
i can not recommend the latest recovery

elgubbo said:
okay i got it working and here is what i did:
it seems 4ext recovery was trying to flash a messed up boot image over and over again.
i pulled the boot.img from the arhd zip file and flashed it via fastboot. it now seems to boot (it has gone past the splashscreen and now shows the boot animation).
thanks again for your.
i can not recommend the latest recovery
Click to expand...
Click to collapse
Cool! Glad you got it sorted out. Which boot.img were you selecting in 4ext, and which one did you pull from the rom.zip? Also, please send a bug report to madmaxx82 so he can look into it...

GROGG88 said:
Cool! Glad you got it sorted out. Which boot.img were you selecting in 4ext, and which one did you pull from the rom.zip? Also, please send a bug report to madmaxx82 so he can look into it...
Click to expand...
Click to collapse
both faux kernel boot.img, but somehow 4ext was stuck with an "old" boot.img from a previous aosp rom.
the feature "smartflash" was activated and somehow could not be deactivated. that way the recovery, everytime when it was done flashing the rom, flashed an aosp kernel afterwards.
at least that is my guess.
thanks again.
best regards
el

elgubbo said:
both faux kernel boot.img, but somehow 4ext was stuck with an "old" boot.img from a previous aosp rom.
the feature "smartflash" was activated and somehow could not be deactivated. that way the recovery, everytime when it was done flashing the rom, flashed an aosp kernel afterwards.
at least that is my guess.
thanks again.
best regards
el
Click to expand...
Click to collapse
That's the culprit there.
It's not the problem of recovery
The smart flash option is for ppl with SON and unlocked bootloader.. And as you said it retains the previous boot.img
As you are soff you should not enable it
.To disable smartflash go to tools in recovery there you will find the smartflash option
Also the latest recovery is awesome..
You just need to know what should be enabled and what should be not before using it
Sent from my pyramid.. Through blazing fast sonic waves

ganeshp said:
That's the culprit there.
It's not the problem of recovery
The smart flash option is for ppl with SON and unlocked bootloader.. And as you said it retains the previous boot.img
As you are soff you should not enable it
.To disable smartflash go to tools in recovery there you will find the smartflash option
Also the latest recovery is awesome..
You just need to know what should be enabled and what should be not before using it
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
yeah, i know that now. there is just one thing: the disabling in the recovery did not work for me.
also: when the recovery is upgradet it asked if i am soff. i misclicked once, but didn't think much of it since it CLEARLY says "if you are not sure, choose no (s-on)".
the thing is it automatically activates smartflash.
the main problem for me was that it could not be deactivated from the recovery. the recovery said "deactivating smartflash" and afterwards "smartflash deactivated" but it wasn't :/
thanks anyways (i know the recovery is the **** i love it, too)

[Q] Evita Can't Boot ROMs

I have been working on my girlfriend's AT&T Evita for about 10 hours now and keep hitting a wall when I try to flash AOKP Milestone 1 or Cyanogenmod 10.
Here's my process:
Unlock Bootloader
Flash TWRP 2.5.0.0
TWRP Factory Reset
Flash AOKP
Flash GAPPs
Clear Cache
Power Off
Fastboot
Flash boot.img from the AOKP ZIP
Reboot
When I run through this process I get the X logo, but the animation just runs and runs, never goes anywhere. Basically the same result when I go through the same process with CM10, but with CM logo stuck just spinning. Only option when that happens is to relock the bootloader and RUU the phone.
S-ON
HBOOT 1.14.0002
RADIO 0.19as32.09.11_2
OpenDSP-v29.1.0.45.0622
RUU version 2.20.502.7 (not sure, will have to check when I get back home in an hour or so.)
Stock Android 4.0.4
Is there any additional information needed? Anyone have any ideas?

Download 2.3.3.1 Check md5
fastboot flash recovery recoveryfilename.img
fastboot erase cache
fastboot reboot-bootloader
select recovery
wipe cache, dalvik, system, factory reset
flash your rom
reboot to bootloader
fastboot flash boot boot.img (whereby boot.img is extracted from the rom you're flashing)
reboot
twrp 2.4+ has issues wiping.
If that doesn't work, some phones have issues booting newer cm roms unless they are on 2.14 hboot. To fix that you would have to s-off and then ruu up to 3.18 then flash recovery.
Sent from my HTC One X using xda app-developers app

What method did you use to s-off? I tried FacePalm but never got it to go through.

SetTheCat said:
What method did you use to s-off? I tried FacePalm but never got it to go through.
Click to expand...
Click to collapse
I believe facepalm is the only known method for this device. Read through the thread, lots of info about how to get the exploit to work

Ok, followed your instructions exactly, still getting the "This Build is for development only" message, but I'm IN!
Thanks for the help exad.
Edit: FacePalm S-OFF successful on first attempt when run from AOKP.

SetTheCat said:
Ok, followed your instructions exactly, still getting the "This Build is for development only" message, but I'm IN!
Thanks for the help exad.
Click to expand...
Click to collapse
The red text is because bootloader is unlocked if you s-off you can remove it.
Sent from my HTC One XL using xda premium

Unable to install ROMs after failed ViperRom Install? Possibly now a paperweight.

Feel like a noob posting this, but I've been trying to fix this problem for the past 24hrs with no luck.
This is the first HTC device I've rooted in nearly a year, and I have to say even though it's pretty, I'm really disliking the evita.
I rooted it using Hasoon's toolkit, and other than being unable to install twrp (or cwm), or getting s-off, it all went well. I just pushed twrp 2.5 to my phone and left s-on until the toolkit gets updated. (not sure how to do this using adb, it's been awhile. ) I have a working hboot, fastboot, and twrp install, and even usb mass storage is working from twrp.
Now, the horror begins. I downloaded team vipers jb rom, and it seemed that the flash went perfectly. But it went into a loop and it seemed to have really messed up the internal sd. Couln't mount it, twrp couldn't find it during my attempts to install other roms or even a factory ruu. I found nocturnals sd fix and that worked like magic, but now twrp will not install any other roms, and everytime I try to push a factory ruu I get a parsing error? On my first attempt at restoring a factory ruu, I forgot that my cid was "1111111" and the bootloader was unlocked so it would fail immediatly. But, even with s-on I managed to get my cid to CWS__001 (ATT's cid) and relocked the bootloader temporarily. But this still didn't change things. Don't know if it matters, but I used hasoons toolkit to push the ruu to my phone and it's during this I get parsing errors. Attempting to install a rom through twrp (CM10, a stock rooted rom, etc.) will immediatly fail also. It says "error executing updater binary in zip and something else that I'll post after trying a CM nightly install.
Update: CM Nightly hangs at the HTC splash screen :crying:
Sorry it's alot to read, but I'm feeling lost at this point...

Ayahuascaa said:
Feel like a noob posting this, but I've been trying to fix this problem for the past 24hrs with no luck.
This is the first HTC device I've rooted in nearly a year, and I have to say even though it's pretty, I'm really disliking the evita.
I rooted it using Hasoon's toolkit, and other than being unable to install twrp (or cwm), or getting s-off, it all went well. I just pushed twrp 2.5 to my phone and left s-on until the toolkit gets updated. (not sure how to do this using adb, it's been awhile. ) I have a working hboot, fastboot, and twrp install, and even usb mass storage is working from twrp.
Now, the horror begins. I downloaded team vipers jb rom, and it seemed that the flash went perfectly. But it went into a loop and it seemed to have really messed up the internal sd. Couln't mount it, twrp couldn't find it during my attempts to install other roms or even a factory ruu. I found nocturnals sd fix and that worked like magic, but now twrp will not install any other roms, and everytime I try to push a factory ruu I get a parsing error? On my first attempt at restoring a factory ruu, I forgot that my cid was "1111111" and the bootloader was unlocked so it would fail immediatly. But, even with s-on I managed to get my cid to CWS__001 (ATT's cid) and relocked the bootloader temporarily. But this still didn't change things. Don't know if it matters, but I used hasoons toolkit to push the ruu to my phone and it's during this I get parsing errors. Attempting to install a rom through twrp (CM10, a stock rooted rom, etc.) will immediatly fail also. It says "error executing updater binary in zip and something else that I'll post after trying a CM nightly install.
Update: CM Nightly hangs at the HTC splash screen :crying:
Sorry it's alot to read, but I'm feeling lost at this point...
Click to expand...
Click to collapse
I think that if you don't have S-OFF, you need to manually flash boot.img as well when installing a ROM. Also, I had issues flashing ROMs with TWRP 2.5. Try 2.3.3.1.

watameron said:
I think that if you don't have S-OFF, you need to manually flash boot.img as well when installing a ROM. Also, I had issues flashing ROMs with TWRP 2.5. Try 2.3.3.1.
Click to expand...
Click to collapse
Hmm... That could explain alot.
I'll try it and let you know what happens.
I have tried the 2.3.3.1 build of twrp, but for some reason the touchscreen doesn't work.

Ayahuascaa said:
Hmm... That could explain alot.
I'll try it and let you know what happens.
I have tried the 2.3.3.1 build of twrp, but for some reason the touchscreen doesn't work.
Click to expand...
Click to collapse
What HBOOT version do you have?

Did you install Viper or ViperXL? ViperXL is what you want for the EVITA.

redpoint73 said:
Did you install Viper or ViperXL? ViperXL is what you want for the EVITA.
Click to expand...
Click to collapse
ViperXL JB
and my hboot is 2.14

Ayahuascaa said:
ViperXL JB
and my hboot is 2.14
Click to expand...
Click to collapse
TWRP 2.3.3.1 should have a working touchscreen with hboot 2.14 are you sure you didn't try 2.3.3.0? that one requires you to downgrade touchscreen firmware first.
You need to fastboot flash boot boot.img where boot.img is extracted from the rom you're flashing if you're s-on and hboot >= 1.14.
If you have SuperCID, do not RUU without S-OFF or you really will have a paperweight.

exad said:
TWRP 2.3.3.1 should have a working touchscreen with hboot 2.14 are you sure you didn't try 2.3.3.0? that one requires you to downgrade touchscreen firmware first.
You need to fastboot flash boot boot.img where boot.img is extracted from the rom you're flashing if you're s-on and hboot >= 1.14.
If you have SuperCID, do not RUU without S-OFF or you really will have a paperweight.
Click to expand...
Click to collapse
Hmm.. I could have. I did it last night after two hours of frustration.
And I just did that to a new install of Nocturnal's rom, but with no luck. It still just hangs at the HTC dev warning screen. I'm going to try re downloading the ViperXL rom and hope I just had a bad copy..
heh. I did that without thinking last night and spent an hour trying to reverse the damage I did. Not only did I have s-on, but my cid was still "1111111".

./

Androidfilehost is only giving me ~50Kbps, so viper's rom has 3 hours left,
but Cleanrom is almost done.
Is there anyway to s-off the evita without booting into an os?
If not, can someone point me to a thread explaining how to manually s-off?
It seems that it's the cause for all this trouble I'm having and I've never had to do manually.
Thank you everyone for your help,
my phone still doesn't have a working os but I do feel like I'm getting somewhere.
Edit: How many of you have had problems installing roms with twrp 2.5.5.0? I'm thinking about trying 2.3.3.1. I thought this was what I flashed last night, but my touchscreen didn't work and according to exad's post I probably had the wrong one.

Use twrp 2.3.3.1 all versions above 2.4 have one issue or another.
You need a Rom installed and usb debugging turned on to s-off.
Here's the link: http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app

exad said:
Use twrp 2.3.3.1 all versions above 2.4 have one issue or another.
You need a Rom installed and usb debugging turned on to s-off.
Here's the link: http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks,
It seems that now 2.5.5.0 just skips the install and tells me that it was successful...
If so that would explain the hangups on the dev screen.

Ayahuascaa said:
Thanks,
It seems that now 2.5.5.0 just skips the install and tells me that it was successful...
If so that would explain the hangups on the dev screen.
Edit: Can you point me to a link for twrp 2.3.3.1? The only thread on xda for that build doesn't have working download links
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Md5: d903047e6e871acb8f99834c30eb8307
Sent from my HTC One X using xda app-developers app

exad said:
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Md5: d903047e6e871acb8f99834c30eb8307
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
CleanRom boots!
Thanks again to everyone who helped and exad for the 2.3.3.1 link,

Preparing Phone Storage.

First boot on new viper rom...
Boot to ring.. Then "Preparing Phone Storage"
Hang for a while then phone reboot itself.
Boot back to a black screen with the signal, battery, and clock visible.
Hang for a minute then reboot again.
Then back to the black screen...
Loop and loop again and again...
Plz help....

External storage is corrupt. Also, it appears you forgot to factory reset before you flashed this ROM. Go onto TWRP, wipe system, dalvik cache, factory reset and then reboot to bootloader. Flash stock recovery and click "clear storage" on HBOOT. Then reflash TWRP, push Viper back over and flash.
Sent from my GT-I9505 using xda premium

kylepont said:
External storage is corrupt. Also, it appears you forgot to factory reset before you flashed this ROM. Go onto TWRP, wipe system, dalvik cache, factory reset and then reboot to bootloader. Flash stock recovery and click "clear storage" on HBOOT. Then reflash TWRP, push Viper back over and flash.
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
I went back to stock rom and the problem still persist. **** boot loop ****
I also noticed that my IMEI is blank. How can I restore it back???

How the bloody hell did you get rid of your IMEI...? Erm, you'll have to pull whatever partition the CID is on (I've forgotten) and re-enter your IMEI. And if you still bootloop then either you have a faulty USB lead or something else is up. Run an RUU.
Sent from my GT-I9505 using xda premium

This is what I did.
Rooted
S-Off with moonshine
Install Venon Viper Rom
Booting... Preparing Phone Storage.. then bootloop.
Meanwhile I noticed that my IMEI is blank???

i was running fine, decided to sell the device and return it to stock. I was s-off, unlocked bootloader, supercid. i changed cid to tmob-010, locked bootloader, flashed stock recovery; rebootRUU, ran the latest ruu from tbmobile successfully.....now im stuck in the same bootloop as above. i tried clearing storage and factory reset from hboot; i unlocked bootloader, loaded twrp and wiped all there, no luck either way, just a continuous bootloop after seeing preparing storage.
i might try this out tomorrow.
http://forum.xda-developers.com/showthread.php?t=1990043

driz said:
i was running fine, decided to sell the device and return it to stock. I was s-off, unlocked bootloader, supercid. i changed cid to tmob-010, locked bootloader, flashed stock recovery; rebootRUU, ran the latest ruu from tbmobile successfully.....now im stuck in the same bootloop as above. i tried clearing storage and factory reset from hboot; i unlocked bootloader, loaded twrp and wiped all there, no luck either way, just a continuous bootloop after seeing preparing storage.
i might try this out tomorrow.
http://forum.xda-developers.com/showthread.php?t=1990043
Click to expand...
Click to collapse
I sent mine to get the missing IMEI fixed. Let me know if you managed to get over the bootloop.

well, i tried to fix it and made it worse, im stuck in qdl now.

driz said:
i was running fine, decided to sell the device and return it to stock. I was s-off, unlocked bootloader, supercid. i changed cid to tmob-010, locked bootloader, flashed stock recovery; rebootRUU, ran the latest ruu from tbmobile successfully.....now im stuck in the same bootloop as above. i tried clearing storage and factory reset from hboot; i unlocked bootloader, loaded twrp and wiped all there, no luck either way, just a continuous bootloop after seeing preparing storage.
i might try this out tomorrow.
http://forum.xda-developers.com/showthread.php?t=1990043
Click to expand...
Click to collapse
Just for the record, did you moonshine or facepalm s-off?

foeti said:
Just for the record, did you moonshine or facepalm s-off?
Click to expand...
Click to collapse
I moonshine mine.

foeti said:
Just for the record, did you moonshine or facepalm s-off?
Click to expand...
Click to collapse
i facepalmed whenever it first came out.
and now im facepalming because i broke it
tmobile is replacing it, they also offered the option for a nexus 4, but i already have a legit nexus 4 so i took a one s

i am at the exact same situation
i have tried multiple roms and many ruus . but all of them stuck after first boot. i have tried hboot 2.15/2.16 and 1.09.
any idea what else should i try ?

anyway, i solved it as said here : http://forum.xda-developers.com/showpost.php?p=41789388&postcount=61

to report; it didn't fix completely. after the Ruu, the signal is a random thing. and 3g is disappeared totally.

finally solved it as described here : http://forum.xda-developers.com/showpost.php?p=50737368&postcount=362

Yes, finally, that worked.
babakgh said:
anyway, i solved it as said here : http://forum.xda-developers.com/showpost.php?p=41789388&postcount=61
Click to expand...
Click to collapse
I had exact same symptoms as OP. Wanted to go back to original ROM, but after this issue appeared, I couldn't even use custom ROMs. .. they had the same symptoms. Anyway, I followed the steps, except I didn't flash the firmware.zip, but it worked for me.
THANKS!!!

Can one you explain what they exactly do?
Yesterday I flash an RUU when I was still s-off and boot-unlocked, then I flash twrp-recovery, make the adb thinks with mmcblk* (dd flash) and flash again a RUU.
But same boot loop problem with "Preparing Phone Storage...".
Would be very thankfull about help.
Greetings by Idijt
Edit:
Because dd flash under linux and with startet recovery did not solve my bootloop / prepairing sd card problem (I had still access to my sd card with twrp-recovery! All the time!) I really think about to enable s-on. Like here written.
I am only scared when I do:
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
How can I re-enable s-off if my os still hangs on "Preparing Phone Storage" after putting s-on and try to flash an ruu to fix my bootloop/Preparing Phone Storage problem?
I did my s-off with rumrunner.
I hope for an answer.
Greetings by I_did_it_just_tmrrow

[Q] Cannot flash stock/any rom

I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?

MAsterokki said:
I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?
Click to expand...
Click to collapse
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?

heavy_metal_man said:
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?
Click to expand...
Click to collapse
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.

MAsterokki said:
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.
Click to expand...
Click to collapse
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk

heavy_metal_man said:
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...

MAsterokki said:
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...
Click to expand...
Click to collapse
Its cool pal it is, but then again ruus won't flash unless your bootloader is relocked
Sent from my Nexus 7 using Tapatalk