Database Info

What went wrong?

I was pulling my hair out for a few hours last night trying to get my phone back to a functional state. Fortunately I was able to do so, but I have no idea what caused all of my problems. Here's what happened:
I was running CM10 on my HOX (from this thread) for awhile now. I was having a few issues with it that were annoying but I didn't want to change the ROM and have to restore everything. I then got a notification for an update to CM10.1 so I downloaded that and installed it. During this process I decided to do a Factory Reset in TWRP.
Once I was booted back into CM10.1 I was having all sorts of strange issues, but the biggest one was that I was unable to connect to my cell network and it kept prompting me to restart. I decided I would just install another ROM so I downloaded CleanROM JL Beta 1 (here) and the Bulletproof-1.0 kernel (here).
I booted into TWPR and proceeded to wipe everything (i.e. clicked all of the buttons under the 'Wipe' menu). I've done this before and haven't had any problems. I then proceeded to install the kernel. It went through the installer fine without any issues. When I tried to install CleanROM JL Beta 1 in TWRP it just kept giving me an error and wouldn't bring up the installer.
I went back and forth trying to install multiple ROMs and every single one would give me an error. I thought I was screwed because I couldn't install an OS on the phone. I also went ahead and installed the stock kernel hoping that would fix the problem but it didn't. I eventually decided on finding the RUU to get me back to bone stock.
I downloaded the 2.20 RUU and relocked my bootloader. I went through the RUU process and everything is fine now, except the fact that I have a stock, bloated phone again.
Was it the kernel that messed me up? I installed it after I wiped everything and I'm not sure if I was supposed to do it that way. I'd like to get back to something stable again but I am not sure if I am able to since I relocked my bootloader and installed the 2.20 RUU. Any help is much appreciated, thanks!
NEW ISSUE #1: I just tried to install the 4.1 OTA update from AT&T. I donwloaded the update and proceeded to install it, but after it restarted everything on my phone was erased and it was set back to factory default on 4.0.1. Now when I check for updates it tells me there are nor updates, the server is full, or 'HtcDm has stopped'. What the hell happened there?
NEW ISSUE #2: I went ahead and tried the OTA update again and now my phone won't turn on and shows no status LED light when plugged in. Back to Best Buy it goes. I need a Nexus...

If you are S-on, did you remember to extract and flash boot.img seperately for each of the ROMs you tried?
Now combo of CleanROM JL and Bulletproof should have worked fine. Don't know what happened there. How did you flash Bulletproof? Using recovery or fastboot?

redpoint73 said:
If you are S-on, did you remember to extract and flash boot.img seperately for each of the ROMs you tried?
Now combo of CleanROM JL and Bulletproof should have worked fine. Don't know what happened there. How did you flash Bulletproof? Using recovery or fastboot?
Click to expand...
Click to collapse
I am S-ON and I did not flash the boot.img via fastboot at first, but then tried that after the ROM wouldn't install. I flashed the Bulletproof-1.0 kernel via TWRP.

afrat said:
I am S-ON and I did not flash the boot.img via fastboot at first, but then tried that after the ROM wouldn't install. I flashed the Bulletproof-1.0 kernel via TWRP.
Click to expand...
Click to collapse
You can't flash kernels in recovery with hboot 1.14 and S-on.
Not sure what you mean by "after the ROM wouldn't install" (the exact sequence of ROM flashing versus flashing boot.img using fastboot). But what you are describing is sounding like ROM-kernel mismatches.

redpoint73 said:
You can't flash kernels in recovery with hboot 1.14 and S-on.
Not sure what you mean by "after the ROM wouldn't install" (the exact sequence of ROM flashing versus flashing boot.img using fastboot). But what you are describing is sounding like ROM-kernel mismatches.
Click to expand...
Click to collapse
I followed the instructions given in the Bulletproof-1.0 post that said to install the zip via TWRP. I did that and everything went fine. I then tried installing CleanROM JL Beta immediately after and it would just give me the zip error.
What I mean by "after the ROM wouldn't install" was after it wouldn't install via TWRP. I then went back and extracted the boot.img, flashed it with fastboot, then went back into TWRP to try and install it again. That didn't work.

redpoint73 said:
You can't flash kernels in recovery with hboot 1.14 and S-on.
Not sure what you mean by "after the ROM wouldn't install" (the exact sequence of ROM flashing versus flashing boot.img using fastboot). But what you are describing is sounding like ROM-kernel mismatches.
Click to expand...
Click to collapse
In op it says he flashed kernel then rom, the rom would have overwritten the kernel flash if thats the order he did it in wouldn't it have? Im thinking it was a bad Cleanrom download he was trying to flash since it gave an error in recovery when he tried to flash it and wouldn't load it at all. Or maybe a bad TWRP image? Just guessing here.

eraste said:
In op it says he flashed kernel then rom, the rom would have overwritten the kernel flash if thats the order he did it in wouldn't it have? Im thinking it was a bad Cleanrom download he was trying to flash since it gave an error in recovery when he tried to flash it and wouldn't load it at all. Or maybe a bad TWRP image? Just guessing here.
Click to expand...
Click to collapse
I also tried installing multiple other ROMs, all giving me the same zip error in TWRP. I forgot to mention that before I installed CM10.1 I downloaded GooManager and that's what kept prompting me to install the CM10.1 version. I also installed the latest TWRP through GooManager as that was what was recommended in the TWRP post as the best way to do so.

afrat said:
I followed the instructions given in the Bulletproof-1.0 post that said to install the zip via TWRP. I did that and everything went fine.
Click to expand...
Click to collapse
If you keep reading on the Bulletproof instructions, you will see:
hboot 1.14+ and S-ON:
The installer includes a method to flash the boot.img for S-ON devices using hboot 1.14 or higher;
however, some people still have difficulties. If it doesn't work:
1. extract boot.img from the zip, reboot to bootloader and do:
fastboot flash boot boot.img​
---------- Post added at 04:26 PM ---------- Previous post was at 04:21 PM ----------
eraste said:
In op it says he flashed kernel then rom, the rom would have overwritten the kernel flash if thats the order he did it in wouldn't it have?
Click to expand...
Click to collapse
With hboot<1.14, or with S-on yes. But in his case no. For hboot 1.14 and higher and S-on, you can flash the kernel before or after the ROM, it doesn't matter since the kernel can't be flashed from recovery.
---------- Post added at 04:29 PM ---------- Previous post was at 04:26 PM ----------
afrat said:
I also tried installing multiple other ROMs, all giving me the same zip error in TWRP. I forgot to mention that before I installed CM10.1 I downloaded GooManager and that's what kept prompting me to install the CM10.1 version. I also installed the latest TWRP through GooManager as that was what was recommended in the TWRP post as the best way to do so.
Click to expand...
Click to collapse
What version of TWRP? The latest build has some serious problems. zip errors for multiple ROMs is making me think its TWRP that is causing you the headache, for the most part.

redpoint73 said:
What version of TWRP? The latest build has some serious problems. zip errors for multiple ROMs is making me think its TWRP that is causing you the headache, for the most part.
Click to expand...
Click to collapse
I'm not sure. If I did the RUU, does that mean I lost the custom recovery (TWRP) that I've installed as well?

I just tried to install the 4.1 OTA update from AT&T. I donwloaded the update and proceeded to install it, but after it restarted everything on my phone was erased and it was set back to factory default on 4.0.1. Now when I check for updates it tells me there are nor updates, the server is full, or 'HtcDm has stopped'. What the hell happened there?

I went ahead and tried the OTA update again and now my phone won't turn on and shows no status LED light when plugged in. Back to Best Buy it goes. I need a Nexus...

afrat said:
I went ahead and tried the OTA update again and now my phone won't turn on and shows no status LED light when plugged in. Back to Best Buy it goes. I need a Nexus...
Click to expand...
Click to collapse
Ok. Wierd. You think the ota bricked your phone? It wont power on in any way? No recovery or anything?
Note 2 ftw

eraste said:
Ok. Wierd. You think the ota bricked your phone? It wont power on in any way? No recovery or anything?
Note 2 ftw
Click to expand...
Click to collapse
It's completely dead. It's quite alright though, Best Buy said they will replace it for me. Gotta love that insurance!

afrat said:
It's completely dead. It's quite alright though, Best Buy said they will replace it for me. Gotta love that insurance!
Click to expand...
Click to collapse
Thats good. But if this did cause the brick knowing what it was would help others! So you were completely stock on the 2.20 ruu then tried to install the OTA right?
Did you have supercid?

eraste said:
Thats good. But if this did cause the brick knowing what it was would help others! So you were completely stock on the 2.20 ruu then tried to install the OTA right?
Did you have supercid?
Click to expand...
Click to collapse
I was completely stock from the 2.20 RUU and then tried applying the OTA update. I started to OTA update once and it rebooted my phone a few times only to have it reset to factory settings with 4.0.4. I then checked multiple times by bumping my clock forward to get the update again (I am assuming the servers were busy which is what was giving me errors). I was able to get the update to download again and then began installing it for a second time. This time is sat on the screen with the refresh icon over the phone with the status bar underneath for a few minutes, then restarted three times with just the phone icon on it, and then powered off completely, never to turn on again.
I did have supercid, at least I think I did, I can't remember exactly what I did to obtain root/unlocked bootloader/custom roms back when I first started messing with it.

afrat said:
I was completely stock from the 2.20 RUU and then tried applying the OTA update. I started to OTA update once and it rebooted my phone a few times only to have it reset to factory settings with 4.0.4. I then checked multiple times by bumping my clock forward to get the update again (I am assuming the servers were busy which is what was giving me errors). I was able to get the update to download again and then began installing it for a second time. This time is sat on the screen with the refresh icon over the phone with the status bar underneath for a few minutes, then restarted three times with just the phone icon on it, and then powered off completely, never to turn on again.
I did have supercid, at least I think I did, I can't remember exactly what I did to obtain root/unlocked bootloader/custom roms back when I first started messing with it.
Click to expand...
Click to collapse
Strange. Really strange.

eraste said:
Strange. Really strange.
Click to expand...
Click to collapse
It is indeed. I am wondering if all my random flashing attempts at different kernels and boot.img files and ROMs just messed something up. I thought that doing the RUU replaced EVERYTHING I could have done to my phone, minus the unlocked bootloader, so maybe it was just a messed up OTA file.
Regardless, I am very glad I got the BB insurance plan. I can have my device completely replaced multiple times during the 2-year plan and there is no deductible or rate increase, it's crazy.

I seem to recall that some people who took the OTA with supercid on earlier JB updates reported getting bricked.

afrat said:
It is indeed. I am wondering if all my random flashing attempts at different kernels and boot.img files and ROMs just messed something up. I thought that doing the RUU replaced EVERYTHING I could have done to my phone, minus the unlocked bootloader, so maybe it was just a messed up OTA file.
Regardless, I am very glad I got the BB insurance plan. I can have my device completely replaced multiple times during the 2-year plan and there is no deductible or rate increase, it's crazy.
Click to expand...
Click to collapse
Yes ruu would have put you back to stock with the exception of supercid that would have stayed.
iElvis said:
I seem to recall that some people who took the OTA with supercid on earlier JB updates reported getting bricked.
Click to expand...
Click to collapse
Me to this was my initial thought super cid was the culprit!

eraste said:
Me too this was my initial thought super cid was the culprit!
Click to expand...
Click to collapse
But some others insisted that it couldn't have been the issue. SuperCID is supposed to allow flashing of any updates regardless of CID restrictions.

[Q] One S C2 / S3 Not compleating ROM flash?? Bricked?

Hey all, been a member here for years but dont post offten. Normally able to get the info i need from other posts but this time i am stuck Just wondering if anyone has had the same issue flashing a One S C2 with the S3 CPU that im having now. It was stuck with 4.0.3 with hboot 2.09.001, raido 16.05.2.24_M and CID OPTUS001...
Last night i dev unlocked it via the HTC site and flashed TWRP 2.4.4.0 recovery. Tried to put on luxandroidROM v4 but it failed part way through ROM install. The progess bar just got to a point and stopped?? I noticed i had a hboot that was too old for the JB ROM so tried BackToBasics v3 (ICS) ROM but that did the same thing...
Thinking it was maybe just a issue with the ROMs, i tried TrickDroid 6 and CM10 Unofficial build but that was doing the exact same thing... Tried redownloading all the ROMs and looking into SupoerCID but as other with the S3 CPU have reported, it all appears to have worked but does not change the CID Oddly enough when i was in ADB Shell while the phone was sitting on the TWRP recovery mode the SU command was not working. Relevent?
I'm now thinking the issue is the phone is not getting permissions to write the ROMs but have no idea how to correct this. I made sure TWRP has all sections mounted (not sure if this is needed as i normally use CWM) but didn't help.
TWRP keeps saying device isnt rooted when i go to reboot it but fails to root when i tell it to on exit. I have manually flashed SuperSU through TWRP and tried fixing permissions. Tried full factory wipe, Bulletproof-S3-1.3 Kernal and SuperSU again. Still nothing.
Not able to find a RUU for the OPTUS001 CID. Tried extracted version of RUU_VILLEC2_U_ICS_40_hTC_Asia_WWE_1.11.707.112_Radio_16.12.20.02U_16.05.20.16_M2 with CID changed in texts files but it still saied with carrier ID issue
This would be the first time i think i have bricked a phone Does anyone have any suggestions? At this point i would be happy for a nandroid backup to go back to sock and just like with 4.0.3

$40 reward to whoever provides me the info i need to fix this

On the s4 versions of TWRP newer than 2.4.0.0 have issues. I'm not sure if they affect the c2 version but I shouldn't hurt to try an older version.
Sent from my HTC One S using xda app-developers app

TWRP 2.4.4.0 has known bugs. Downgrade to 2.3.3.0 or 2.3.3.7.
And remember to open (BUT NOT EXTRACT) the .zip and to copy and paste the boot.img into your fastboot working environment and manually flash it with this command:
fastboot flash boot boot.img
Then try to flash the ROM that you got the boot.img from. This should work.
Sent from my One S using xda premium

Managed to get this working, figured i would post in case anyone else runs in this issue.
Tried multiple versions of TWRP and no matter what one i tried the roms were unable to write to the stoage. Had to format the phone storage using boot cd - I used GParted through a virtual to do so.
Once that was done TWRP 2.4.4.0 worked fine to flash rom. Still stuck with 4.0.3 with hboot 2.09.001 due to the optus CID but phone is atleast alive. Thanks all for the input

[Q] Installing Cyanogen mod (or any rom, I just want a usable phone again)

When I started this project I guess I thought I knew more than I did. I had installed Cyanogen on multiple other devices, but this one got me. I apologize profusely, I'm not usually one to ask for help but I promise I've been scouring these forums and the web for about 8 hours straight now to no avail. (In all likelyhood I'm just an idiot). Anyway, I'll spell out my problem as best I can.
Basically what I want as a final result is CM 10.1 RC2 Jelly Bean 4.2.2 on my HTC One X at&t. Right now, I'd just like to be able to install any rom at all. I currently don't have anything working and I believe accidentally wiping "system" did that.
When I try to flash it from CWM it just stops and says (Status 7). It seems every rom I try to install comes up with some error there.
Could rooting be a problem? I tried installing several superuser.zip files I could find online. One seemed to work, though I think it's an old one. The latest one I tried came up with error (status 0).
Do I need s-off? I've been trying the "All in one" tool for that but with no luck. I also tried installing SuperUser with the same tool, but it said "Device not found", even though I could reach it via adb fast boot.
Finally, when I try to boot normally it bootloops between the "HTC quietly brilliant" screen, and the same one with the red text that says "this build is for development purposes only. Do not distribute..."
It's 3 in the morning and I should probably get a little sleep before work tomorow. Thanks a ton for reading!

I have the same problem! My phone doesnt have a rom on it at all after this.. When i go to cmd and try to flash a rom, it says something like "cannot open filename.img"

First things first. What firmware and hboot versions are you on?
Secondly, try using TWRP recovery instead of CWM. It can be found here. Flash it using fastboot with the following command:
fastboot flash recovery recoveryfilename.img (whatever the exact recovery filename is)
Then do:
fastboot erase cache
fastboot reboot-bootloader
Thirdly, where are you downloading cm from? You should only get it from here.
Sent from my Evita
---------- Post added at 07:17 PM ---------- Previous post was at 06:54 PM ----------
PS. flashing a superuser.zip while you have no OS installed will do absolutely nothing.
Sent from my Evita

I think everyone with the evita should be s-off. it helps get rid of many annoyances with this phone. also nothing is being done that uses s-off that is really that dangerous.
You should be supercid,s-off,latest ruu 3.17 or 3.18(at&t) then flash recovery and then flash supersu zip to get stock rooted, or you can just wipe the phone and flash a custom rom. i currently use cwm and havent had trouble with it. you can get latest unofficial cwm builds here http://goo.im/devs/mdmower

[Q] Htc One X Unique problem

So as a n00b, I posted in the wrong forum earlier, lol
Anyways , long story short, htc one x evita, unlocked bootloader, tampered, rooted, will not flash past htc splash screen, when I try to restore, it does nothing, when going into folders there is NOTHING there, so random, I did clear my caches as instructed, maybe I am n00bish and deleted the wrong things, I can read the phone in adb, will go into teamwin screen,
REgardless, If I can get this fixed, I will not be messing with it again, lol(as all noobs say)
IS there anything I can do at this point before I throw my hands in the air and throw my phone at a wall?

Far from unique. It's possible that you've accidentally wiped the sd at some point, or did you possibly do a factory reset from the bootloader? Why haven't you just copied a ROM to the device to flash?
Sent from my Evita

timmaaa said:
Far from unique. It's possible that you've accidentally wiped the sd at some point, or did you possibly do a factory reset from the bootloader? Why haven't you just copied a ROM to the device to flash?
Sent from my Evita
Click to expand...
Click to collapse
HI, I may have wiped the sd, let's say sure to this..lol..
I have tried to copy a rom, I had Viper somewhat load, then it flashes back to htc splash, then to twrp,
Any insite to one that may possibly work?(the others will not load at all, they all fail install)

I need a bit more background on the device, please post your bootloader details (the first five lines). What TWRP version are you using? What had you done to the device directly before encountering this problem?
When you say you had Viper somewhat load what do you mean? Did it boot into the ROM at all? Or did it only boot as far as the Viper boot animation? Or did it only make it as far as the HTC splash screen?
I can't really say what's going to work until we figure out exactly what's wrong. Make sure you answer all the above questions with as much relevant detail as possible and we'll see if we can sort it out.
Sent from my Evita

timmaaa said:
I need a bit more background on the device, please post your bootloader details (the first five lines). What TWRP version are you using? What had you done to the device directly before encountering this problem?
When you say you had Viper somewhat load what do you mean? Did it boot into the ROM at all? Or did it only boot as far as the Viper boot animation? Or did it only make it as far as the HTC splash screen?
I can't really say what's going to work until we figure out exactly what's wrong. Make sure you answer all the above questions with as much relevant detail as possible and we'll see if we can sort it out.
Sent from my Evita
Click to expand...
Click to collapse
First off, thank you for your prompt replies
Venom loaded splash screen, then reboot to htc splash with the red developer on the bottom
twrp is the newest one
first 5 lines are you meaning?
*** TAMPERED ****
*** UNLOCKED ****
Evita put ship s-on rl
hboot-2.14.0000
radio-0.23a.32.09.29
??
Well I tried to load the stock RUU from rogers, (ota one)
then after rooting,unlocking bootloader, I tried to load a custom rom(slimkat IIRC)
then IT shut down, I left it for the night, and then nothing, so I tried to install slimkat again, nothing, so I tried venom, and I had the splash screen for the rom, now I am basically back at square one, nothing lol

Yes those are the bootloader details I needed. When you say the latest TWRP I'm assuming you mean 2.6.3.0? There are two versions of 2.6.3.0, the official version and the modified version.
Official version
Can flash any ROM except 4.4 ROMs. If you're using this one it is why SlimKat (plus any other 4.4 ROM) is failing to install.
Modified version
This is required to flash 4.4 ROMs. It does work on some pre 4.4 ROMs but it doesn't on others.
The most common cause for your current situation to happen is that you've forgotten to flash the boot.img with fastboot. Your phone is s-on, this means that the boot.img is unable to be flashed during the recovery install due to security restrictions on hboots equal to or greater than 1.14. So, make sure you're using the correct recovery for the ROM you want to flash (official 2.6.3.0 for Viper, modified 2.6.3.0 for 4.4 ROMs), and make sure you flash the boot.img with fastboot. I have detailed instructions on how to flash a boot.img in my How-To Guide For Beginners thread, link in my signature.
Do that and report back with how you go.
Sent from my Evita

timmaaa said:
Yes those are the bootloader details I needed. When you say the latest TWRP I'm assuming you mean 2.6.3.0? There are two versions of 2.6.3.0, the official version and the modified version.
Official version
Can flash any ROM except 4.4 ROMs. If you're using this one it is why SlimKat (plus any other 4.4 ROM) is failing to install.
Modified version
This is required to flash 4.4 ROMs. It does work on some pre 4.4 ROMs but it doesn't on others.
The most common cause for your current situation to happen is that you've forgotten to flash the boot.img with fastboot. Your phone is s-on, this means that the boot.img is unable to be flashed during the recovery install due to security restrictions on hboots equal to or greater than 1.14. So, make sure you're using the correct recovery for the ROM you want to flash (official 2.6.3.0 for Viper, modified 2.6.3.0 for 4.4 ROMs), and make sure you flash the boot.img with fastboot. I have detailed instructions on how to flash a boot.img in my How-To Guide For Beginners thread, link in my signature.
Do that and report back with how you go.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so very much, once again with the quick replies and the "dumming" it down for me,
I will try in a little bit, to be honest, im not sure what twrp it is, I know its 2.3.6.0, it was the newest one,
in your instructions is there a way to boot just back to stock rom as well?(my pc is horrible, if I load more then one page it dies off lol) I will try this when I get home in a little bit herre.

I can almost positively say you're on the official version of TWRP, you'd need to go out of your way to find the modified one usually. With your phone in its current state you can't use an RUU to go back to stock. The latest Rogers RUU is older than your current firmware and you can't run an older RUU while s-on. If you made a TWRP backup of your stock ROM before wiping you could restore that backup though.
Your best and easiest option right now is to just flash a ROM. Once you've gotten a custom ROM booted up my guess is you won't want to go back to stock
Once you've gotten a ROM booted you can get s-off on your device which will make life a lot easier for you. It means no more flashing a boot.img, you'll be able to flash radios, you can run any Evita RUU (forwards or backwards, and from any carrier), and more benefits. But for now just concentrate on getting the ROM booting.
I'm assuming you have adb/fastboot installed on your PC already? If not you'll need to do that first, Google search "minimal adb and fastboot", the first result should take you to a thread that can get it done with very little effort.
Sent from my Evita

timmaaa said:
I can almost positively say you're on the official version of TWRP, you'd need to go out of your way to find the modified one usually. With your phone in its current state you can't use an RUU to go back to stock. The latest Rogers RUU is older than your current firmware and you can't run an older RUU while s-on. If you made a TWRP backup of your stock ROM before wiping you could restore that backup though.
Your best and easiest option right now is to just flash a ROM. Once you've gotten a custom ROM booted up my guess is you won't want to go back to stock
Once you've gotten a ROM booted you can get s-off on your device which will make life a lot easier for you. It means no more flashing a boot.img, you'll be able to flash radios, you can run any Evita RUU (forwards or backwards, and from any carrier), and more benefits. But for now just concentrate on getting the ROM booting.
I'm assuming you have adb/fastboot installed on your PC already? If not you'll need to do that first, Google search "minimal adb and fastboot", the first result should take you to a thread that can get it done with very little effort.
Sent from my Evita
Click to expand...
Click to collapse
Yes I have a basic Adb/fastboot setup already, is there a particular rom you recommend?(I will trust your best judgement here) I am home now, I will try and let you know
Thank you again

Asking for a ROM recommendation isn't allowed on XDA so I can't answer that question, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge.
Each user has different tastes anyway. Some people like Sense ROMs, some like aosp ROMs. Personally I'm an aosp guy, aosp ROMs are generally a bit snappier, plus you can run the latest version of Android (Sense ROMs are limited to 4.2.2 for our device). I'd suggest having a look at the ROMs on offer, check out their features and pick one to flash. If you don't end up liking it you can always just flash another, and that's half the fun.
As a side note, getting s-off via Rumrunner s-off seems to work better on Sense ROMs. I know someone very recently got s-off while on the Kickdroid ROM so if you do want to get s-off I'd suggest flashing that ROM purely for the s-off process. You might like it and want to stay on it, if not just flash away.
Sent from my Evita

timmaaa said:
Asking for a ROM recommendation isn't allowed on XDA so I can't answer that question, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge.
Each user has different tastes anyway. Some people like Sense ROMs, some like aosp ROMs. Personally I'm an aosp guy, aosp ROMs are generally a bit snappier, plus you can run the latest version of Android (Sense ROMs are limited to 4.2.2 for our device). I'd suggest having a look at the ROMs on offer, check out their features and pick one to flash. If you don't end up liking it you can always just flash another, and that's half the fun.
As a side note, getting s-off via Rumrunner s-off seems to work better on Sense ROMs. I know someone very recently got s-off while on the Kickdroid ROM so if you do want to get s-off I'd suggest flashing that ROM purely for the s-off process. You might like it and want to stay on it, if not just flash away.
Sent from my Evita
Click to expand...
Click to collapse
I understand and apologize, Never thought of it that way,
Anyways an update, I followed your tutorial, and I am not having much luck here, It still maintains to say NO OS installed (through twrp when rebooting after I do adb and such)
maybe I am missing something ?

Adb or fastboot?
Sent from my Evita

timmaaa said:
Adb or fastboot?
Sent from my Evita
Click to expand...
Click to collapse
Fastboot,
Small update I did manage to get a rootbox rom to load, but its not stable by anymeans...Ugh super frustrated with it

Are you wiping in TWRP before flashing? It's very important to wipe system/factory reset/cache/dalvik cache before installing a ROM. Just never do a factory reset in the bootloader, that'll corrupt your sd card.
Sent from my Evita

timmaaa said:
Are you wiping in TWRP before flashing? It's very important to wipe system/factory reset/cache/dalvik cache before installing a ROM. Just never do a factory reset in the bootloader, that'll corrupt your sd card.
Sent from my Evita
Click to expand...
Click to collapse
Yes to wiping before flashing in TWRP just those ones mentioned, (if you do sd you loose your flash right?), anyways the rom I flashed yesterday was super unstable, just trying a few diff. ones out and trying to find one that will continue to stay working lol!! Your tutorial in your signature is very helpful
thank you so much for all your help,and patience

Yeah you don't want to wipe sd card/internal storage or you'll lose all of your personal data like images, music, ROM zips, backups.
Sent from my Evita

timmaaa said:
Yeah you don't want to wipe sd card/internal storage or you'll lose all of your personal data like images, music, ROM zips, backups.
Sent from my Evita
Click to expand...
Click to collapse
Oh this is a clean phone, I already backed up on pc Before lol
Question though, I installed Viper again(just to try it) and it loads a menu showing ram, one of the memory sections shows -1? is this correct?

On a side note, I got Venom up and running and WOW!!!
once again, a super thank you for your patience and help all along Timmaaa,

I'm not sure what you're talking about, is that after booting into the ROM? Can you show me a screenshot?
Sent from my Evita

timmaaa said:
I'm not sure what you're talking about, is that after booting into the ROM? Can you show me a screenshot?
Sent from my Evita
Click to expand...
Click to collapse
it was while I was installing, everything seems fine, still no wifi(original issue)
im thinking the logic board may be buggered...sad day...lol
But, it is fast as heck now, running venom rom, I will try to get S-off and then maybe try to get it so I can load up the 4.4X roms
Thanks for all the help

Custom ROM Issue... Stuck Booting...

Hey androids, I submitted this question as a reply to the guide thread already earlier... just thought it might get noticed in this forum alittle quicker... any help would be appreciated
I'm working on a recalled tablet that I rooted to keep using, and up until recently the ROM i had installed on it worked famously (bliss pop with android 5.1.1). Now, I was having some issues with it and thought "Well, i'll try out a different rom!"
So, I already had root (obviously) and I had already successfully installed a rom to this tablet... Using TWRP (both the 2.8.x.x I used previously and the newest one available for the shield) I have backed up, wiped, and flashed the images to 3 different roms + gapps for the appropriate versions...
first, I was going an issue with it mounting the \data partition so it wouldn't flash anything... then I repaired and rewiped the partitions, and got (what appeared to me in the logs) a clean and successful install of the roms. Each time I successfully flashed a ROM and GAPPs zips I would go to boot the ROM and my table would sit on the "NVIDIA" boot screen forever, never advancing to boot the ROMs.
I was worried that I had made a mistake and bricked the thing (though, it's been on borrowed time anyways being a recalled tablet). But I was able to force shutdown the tablet and reboot it into TWRP for another try. Each time I cleared the previous flash, wiped the cache and system partitions, and would get another clean install... but each time, it would get stuck on that same boot screen....
Anyone have any suggestions? thoughts? ideas? fixes? answers?.... anything? lol
Thanks folks!

Assuming you are trying to flash MM custom roms: You need the MM bootloader.

edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Is the newest TWRP *not* a MM bootloader?

TWRP is a recovery. A bootloader is a bootloader.

This is covered in every rom thread that updated from L to M.

lafester said:
This is covered in every rom thread that updated from L to M.
Click to expand...
Click to collapse
I'll re-look, the guides i've read have only covered flashing TWRP, then using them to flash the ROM and GAPPs... Which is what I did the first time I rooted it and put on a custom ROM... though maybe I didn't delete the original bootloader the first time and did so accidentally this time?

Thanks for the heads up though people, we'll see if I can straighten it out now that I know what I'm looking for

edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Ok, so I've downloaded the shield recovery zip, flashed the boot.img to the boot... nothing, then I read on one of the guides here that the "blob.img" is the bootloader... but the zip has a blob, without the .img
So I then attempted to add .img, and flash it to "boot" in TWRP, and there was an error, saying the file is too large...
do you (or someone else) know where to find a guide on where to find/how to flash a MM bootloader?
thanks

Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.

MilesD37 said:
Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.
Click to expand...
Click to collapse
Im stuk with the same probem, can you sendme the Link to the gide please