Viper Rc 1.3 for Evo 3d - HTC EVO 3D

i would post in the dev forum but it still says that i am a new member even though i have been here for months. I just dont post..no issues before. Ok....so i rooted my evo3d..perfect. I go to install viper 1.3 and it appears to go through as it should. I dodnt get any error messages. Someting is wrong though. It just keeps rebooting to recovery right after white HTC splash screen. I have team win recovery with stock kernel. I wiped EVERYTHING numerous times. Help please. Can someone get this tp viper or repost to the viper dev thread. I really need help

blacjac30 said:
i would post in the dev forum but it still says that i am a new member even though i have been here for months. I just dont post..no issues before. Ok....so i rooted my evo3d..perfect. I go to install viper 1.3 and it appears to go through as it should. I dodnt get any error messages. Someting is wrong though. It just keeps rebooting to recovery right after white HTC splash screen. I have team win recovery with stock kernel. I wiped EVERYTHING numerous times. Help please. Can someone get this tp viper or repost to the viper dev thread. I really need help
Click to expand...
Click to collapse
Your post is pretty vague regarding the circumstances of your problem.
Get the md5 checksum for the ROM, and check it with an md5 checker app. I have been using hashdroid from the market. Or you can get a freeware app for your pc, just Google it.
Alternatively, download the ROM again. And double check the OP's installation instructions.
Sent from my PG86100 using XDA App

Try getting superwipe, or you can go into recovery and format boot, system, data and cache. Unless you have tried this before I'm betting it will solve your problems. Hope this helps. +1 on doublechecking the md5 I never do but it might well b a bad download. I'd still recommend the formatting as this will ensure everything is erased and you are starting fresh.
Transformer Sent

Just download the ROM again. Full wipe and reinstall. You should be fine.

Get a crow-bar, a hammer n some duct tape.... Carefully insert... Nevermind just do what they said.
Sent from 3D A.W.E.S.O.M-O

blacjac30 said:
i would post in the dev forum but it still says that i am a new member even though i have been here for months. I just dont post..no issues before. Ok....so i rooted my evo3d..perfect. I go to install viper 1.3 and it appears to go through as it should. I dodnt get any error messages. Someting is wrong though. It just keeps rebooting to recovery right after white HTC splash screen. I have team win recovery with stock kernel. I wiped EVERYTHING numerous times. Help please. Can someone get this tp viper or repost to the viper dev thread. I really need help
Click to expand...
Click to collapse
I have the same issue, post it in the ViperRom post but basically everyone said never seen it before and suggested all that has been suggested here. I went through all that: re downloading, checking the M5d, even formatting my SD card.
Kept trying till I found out that it is a Kernel issue, my phone doesn't seem to like the stock kernel with that Rom ( the only Rom with the issue), I finally tried showDown Kernel just to test it and that worked, now I am currently using it with natarchy Kernel.
Hopefully this will help you.

try usin CWM recovery i ran viper for awhile no problems in CWM

Adel_2 said:
I have the same issue, post it in the ViperRom post but basically everyone said never seen it before and suggested all that has been suggested here. I went through all that: re downloading, checking the M5d, even formatting my SD card.
Kept trying till I found out that it is a Kernel issue, my phone doesn't seem to like the stock kernel with that Rom ( the only Rom with the issue), I finally tried showDown Kernel just to test it and that worked, now I am currently using it with natarchy Kernel.
Hopefully this will help you.
Click to expand...
Click to collapse
That kind of doesnt make sense cause viper includes its own kernel (stock) so whatever kernel you have will be overwritten with that kernel when you flash viperom.. But good you got it fixed.

aznmode said:
That kind of doesnt make sense cause viper includes its own kernel (stock) so whatever kernel you have will be overwritten with that kernel when you flash viperom.. But good you got it fixed.
Click to expand...
Click to collapse
I overrode the included kernel with another one after flashing the rom.
Another way after it tries to start I pull the battery, push the volume down then power it up to get back to recovery and flash another kernel that works, that is the only way it works for me now.
Sent from my PG86100 using XDA Premium App

Related

Issue with ROM Manager

Hi everyone.
I'm pretty new to android, but I'm quite good at following instructions. Basically I've tried doing a nandroid backup with ROM Manager and everytime it reboots to make a backup it goes to a black screen with a phone in the middle of the screen with a red warning sign next to it. I've always tried booting into recovery and I get the same result. I first found this out while trying to follow the instructions for replacing the status and battery icons. Has anyone else had this issue?
I'm using ROM Manager v3.0.0.1 on a stock HTC MySense ROM from TMO running Android v2.2.1.
Thanks in advance for anyone that knows what I'm apparently doing wrong.
when you opened ROM Manager did you select "Flash ClockworkMod Recovery"? if not try that, it's the only time mine has what your's is doing. I got a little excited to flash Iced-Glacier when I first got the phone and accidentally skipped that step and had same issue
Yeah I first clicked on Flash ClockworkMod Recovery and it currently says Current Recovery: ClockworkMod 2.5.1.2. I just redid the flash and tried to boot into recovery mode and I'm still getting that error picture upon reboot.
Is there a setting on the phone somewhere that would cause this?
I am not positive 100% but I think I know what you mean; and I had it once due to very low battery charge. See if it is the problem or not.
infraled said:
Yeah I first clicked on Flash ClockworkMod Recovery and it currently says Current Recovery: ClockworkMod 2.5.1.2. I just redid the flash and tried to boot into recovery mode and I'm still getting that error picture upon reboot.
Is there a setting on the phone somewhere that would cause this?
Click to expand...
Click to collapse
The phone with the triangle is the stock recovery image. Others have had to try flash the ClockworkMod Recovery several times. You may need to as well.
this is what i did, not sure if your doing the same thing or not. i clicked on Flash ClockworkMod Recovery, MY4G came up and i clicked that and then clicked on backup current rom.
Alright so I've tried it with a full battery and I had the same result. I also tried reflashing several times with the current version and rebooting. I even tried to load some of the older versions of clockwork through ROM Manager and everytime I tried it spits out an error. I don't understand how I could be having such a hard time with something everyone seems to be able to do effortlessly.
Sent from my HTC Glacier using XDA App
R u sure u r rooted with S-off? If u r then u may have to flash recovery from ADB. Some people have not been able to get recovery to stick through ROM manager. There is a thread in the development section that explains how to do this.
Sent from my HTC Glacier using XDA App
Really? I have not heard that...I'll have to check up on that. It seems that this problem would be more common, but I guess not as I have had little luck in finding information on my own about this problem.
Just in case anyone is following this thread with the same problem as me, this is the post that the previous poster was referring to:
http://forum.xda-developers.com/showthread.php?t=852905&highlight=recovery
UPDATE:
Ok I figured out what was wrong. Apparently although I had root access on my phone and able to run things like Titanium Pro and Adfree and others with root privileges it wasn't good enough.
I followed the instructions here on how to permaroot your phone by pushing gfree to it. Once I did that I attempted to manually flash clockworkmod, which I ended up running into other issues. On a lark I tried installing clockworkmod through ROM Manager after permarooting and it finally installed it properly!
I love doing stuff like this, thanks to everyone for their input as it guided me to finally solving this. I'm off to do a nandroid backup now.
krypto16 said:
R u sure u r rooted with S-off? If u r then u may have to flash recovery from ADB. Some people have not been able to get recovery to stick through ROM manager. There is a thread in the development section that explains how to do this.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I have NEVER been able to flash Recovery with ROM manager. It says it does it but corrupts if everytime! Note: There has been some recent updates to ROM Manager and I haven't tried lately.
krypto16 said:
R u sure u r rooted with S-off? If u r then u may have to flash recovery from ADB. Some people have not been able to get recovery to stick through ROM manager. There is a thread in the development section that explains how to do this.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
IIRC the security protocol doesn't have to be off to flash clockwork ROM you do have to be rooted, VISONary.apk of course. I've turned my S=on just to make sure and it [clockworkROM] works pretty flawlessly.
Hey hey, it's great to see infraled out here! I am rooted/S=Off via the first VISIONary thread that was posted...
http://forum.xda-developers.com/showthread.php?t=834225
I installed Clockwork, flashed Clockwork Recovery and was expecting to have to do it twice, as outlined in this thread...
http://forum.xda-developers.com/showthread.php?t=858021
It only took one shot for me and it worked perfectly. The very first try, I powered off, powered on w/ vol down, went into Recovery and wham, there was Clockwork in its green glory. I figured I was just lucky and that once I rebooted, it would be lost and I'd have to flash again. Not so. Did a backup right away, worked flawlessly.
Looking forward to Iced Glacier, eVil and Cyanogen over the holiday break...
shlongwoodian said:
Looking forward to Iced Glacier, eVil and Cyanogen over the holiday break...
Click to expand...
Click to collapse
Cyanogen Gets my vote... But i've always loved T/DB's ROMS.
Recently rooted My new MyTouch 4G, downloaded the paid version of rom manager. I didn't understand why there are none of the current roms like the iced glacier, roms made by evil and several others listed as possible roms for flashing. The only roms are the cyanogenmod nightly builds. The cyanogenmod 6.1.2 RC2 isn't listed either. Do I need to do anything to get those listed or is that just the way it is???
Thank you,
Vinny

Ok so why do they say not to use rom manager?

Just like the title says why should we not use rom-manager on this phone?
from what i can remember it installs a ****ty version of CWM that doesn't cooperate well with our phones.
Boobie Watcher said:
from what i can remember it installs a ****ty version of CWM that doesn't cooperate well with our phones.
Click to expand...
Click to collapse
gotcha. i wish koush would do something about rom manager because the atrix also had a wipping issues on roms and he never fixed it
From my recent experience with the SGSII, the recovery is integrated into the kernel (unlike HTC devices which have a dedicated partition for it). My guess is ROM Manager can't flash it, since it doesn't have the kernel image.
Phoenix84118 said:
From my recent experience with the SGSII, the recovery is integrated into the kernel (unlike HTC devices which have a dedicated partition for it). My guess is ROM Manager can't flash it, since it doesn't have the kernel image.
Click to expand...
Click to collapse
gotcha thats intresting
You shouldn't use it on any phone anyway, your best bet is going into recovery
Sent from my Inspire 4G using XDA App
Haha too funny I was literally wondering this last night. Glad you asked kuz I couldn't find an answer when I did a quick search.
Edit: so I've been running miui this week and see the app rom manager. I'm fine as long as i don't actually do anything through it correct?
Sent from my SGH-I777 using Tapatalk
It breaks and does weird crap - I've heard it works OK if (and only if) you are currently on CM7.
But since you're most likely using it to move to/from another ROM... Just three-finger into recovery or if the ROM has an extended power menu use that for recovery.
Its best to just use three-finger or the extend menu power menu like Entropy said. I've seen Rom manager mess up leading to a semi-brick phone.
Hey all,
First time poster and new to rooting.
I ended up attempting to use rom manager to load CWM right after root, but I think that borked my wifi.
What can I do if I've already used it? I did it because I hadn't yet seen all the xda threads on NOT using it, and the place I was was not as well informed as you folks.
Also, how do I get CWM if not via ROM Manager?
My brothers EVO was royally effed up from using ROM Manager. Became a paperweight until Sprint authorized a replacement.
karankshah said:
Hey all,
First time poster and new to rooting.
I ended up attempting to use rom manager to load CWM right after root, but I think that borked my wifi.
What can I do if I've already used it? I did it because I hadn't yet seen all the xda threads on NOT using it, and the place I was was not as well informed as you folks.
Also, how do I get CWM if not via ROM Manager?
Click to expand...
Click to collapse
Read through the FAQs and this thread - CWM is included in kernels that support it.
karankshah said:
Hey all,
First time poster and new to rooting.
I ended up attempting to use rom manager to load CWM right after root, but I think that borked my wifi.
What can I do if I've already used it? I did it because I hadn't yet seen all the xda threads on NOT using it, and the place I was was not as well informed as you folks.
Also, how do I get CWM if not via ROM Manager?
Click to expand...
Click to collapse
I ended up figuring most of this out so I wanted to close this out (for anyone that stumbles past my original post).
Here's what I did:
I uninstalled ROM Manager - but this didn't get the wifi going.
I reflashed with the stock ROM and unrooted kernel - this still didn't help.
I did a factory reset - this did manage to get it going.
I was able to track down a CWM standalone that I flashed it with (using Odin).
I followed that up with a root, a wipe, and then a fresh flash of UnNamed.
Phone seems to be working fine.
Andrew149 said:
Just like the title says why should we not use rom-manager on this phone?
Click to expand...
Click to collapse
When I first rooted my phone I installed rom manager because it looked easier to just pick the file that u wanted flashed and it would do it for u, so u wouldn't have to play with the volume keys. But every time I tried to do anything with it, it just said certificate not found. Aborting. So u shouldn't use rom manager. I think it works with the roms that u download of the app but not ones from XDA.
Sent from my SGH-I777 using XDA App
I loaded a kernal with cwm. I use rom manager to install Google apps. After new rom loads up.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Flash entropys kernel. Daily driver
Sent from my Samsung Galaxy S II
If you're on CM7, ROM Manager can be used to install gapps - that's about the only thing it doesn't seem to choke on.
karankshah said:
Hey all,
First time poster and new to rooting.
I ended up attempting to use rom manager to load CWM right after root, but I think that borked my wifi.
What can I do if I've already used it? I did it because I hadn't yet seen all the xda threads on NOT using it, and the place I was was not as well informed as you folks.
Also, how do I get CWM if not via ROM Manager?
Click to expand...
Click to collapse
You cannot get CWM via ROM Manager - that is the point. It comes with certain custom kernels such as Entropy's DD kernel. If you do not have a CWM kernel - you will more than likly need to use Odin to get a kernel with CWM.
If you have totally screwed things up - look in the dev thread for "the return to stock" section and start over doing it the right way
karankshah said:
I ended up figuring most of this out so I wanted to close this out (for anyone that stumbles past my original post).
Here's what I did:
I uninstalled ROM Manager - but this didn't get the wifi going.
I reflashed with the stock ROM and unrooted kernel - this still didn't help.
I did a factory reset - this did manage to get it going.
I was able to track down a CWM standalone that I flashed it with (using Odin).
I followed that up with a root, a wipe, and then a fresh flash of UnNamed.
Phone seems to be working fine.
Click to expand...
Click to collapse
Hi first post as well XDA forums so in depth and helpful decided I wanted to be apart of it. Still a noob though ill work my way up.
I am trying acheive the same goal he is, that is to say Instal the UnNamed (it is exactly what I want) Rom on my Samsung Galaxy S2 Skyrocket.
Keep it brief: Rooted my phone using root exploit:
it will not let me post link. the zergrush one
and bellow flashed clockwork mode using stand alone not ROM because of this forum. Model 5.0.2.6
I wipe catch, battery, then format everything. Then I start to flash the ROM. The installation begins. It cleans and formats everything again, then sais that there was an error in the file and it fails. After this if I dont restore my phone will not start. Ive tried it several times being even more thorough on procedure and its the exact same error every time.
Im just wondering if its the way I rooted it is incorrect, The CWM Im using is not the correct one, or if Im doing something wrong entirely. I think it might be CWM but I have not been able to locate one like he did that worked.
Any help, suggestions, criticism or advice would be very helpful. I just thought Id ask. thanks in advance ^^
Elemblue said:
Hi first post as well XDA forums so in depth and helpful decided I wanted to be apart of it. Still a noob though ill work my way up.
I am trying acheive the same goal he is, that is to say Instal the UnNamed (it is exactly what I want) Rom on my Samsung Galaxy S2 Skyrocket.
Keep it brief: Rooted my phone using root exploit:
it will not let me post link. the zergrush one
and bellow flashed clockwork mode using stand alone not ROM because of this forum. Model 5.0.2.6
I wipe catch, battery, then format everything. Then I start to flash the ROM. The installation begins. It cleans and formats everything again, then sais that there was an error in the file and it fails. After this if I dont restore my phone will not start. Ive tried it several times being even more thorough on procedure and its the exact same error every time.
Im just wondering if its the way I rooted it is incorrect, The CWM Im using is not the correct one, or if Im doing something wrong entirely. I think it might be CWM but I have not been able to locate one like he did that worked.
Any help, suggestions, criticism or advice would be very helpful. I just thought Id ask. thanks in advance ^^
Click to expand...
Click to collapse
UnNamed is not a Skyrocket ROM nor are any other ROMs in this subforum. You want to go here: http://forum.xda-developers.com/forumdisplay.php?f=1399

Problem with rebooting after flashing CleanROM 4.1 pro ed and dev ed.

Yesterday my phone started to act up so I restarted it and it won't boot ever again. I wasn't able to get to the recovery either. So I relocked and did a ruu and I updated to the latest version. I flashed amon recovery and started to flash different roms like dev CleanROM and rooted 4.03 stock(I did the root fix and flash the image) . After initial setup all I get was reboot. I then flashed CleanROM 3.7 that is in my sd card. It's working fine now. BTW all flashes were done before a full wipe not with the tool but in the amon recovery. I don't know what's causing the reboot problem. I don't see any topics related to this, there might be some posts related to this. But please link me to me if you can. And also the fix would be nice.
Thank you in advance
If this has been answered before sorry
About it
Sent from my ADR6425LVW using xda premium
pagereborn said:
Yesterday my phone started to act up so I restarted it and it won't boot ever again. I wasn't able to get to the recovery either. So I relocked and did a ruu and I updated to the latest version. I flashed amon recovery and started to flash different roms like dev CleanROM and rooted 4.03 stock(I did the root fix and flash the image) . After initial setup all I get was reboot. I then flashed CleanROM 3.7 that is in my sd card. It's working fine now. BTW all flashes were done before a full wipe not with the tool but in the amon recovery. I don't know what's causing the reboot problem. I don't see any topics related to this, there might be some posts related to this. But please link me to me if you can. And also the fix would be nice.
Thank you in advance
If this has been answered before sorry
About it
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
What did you have on your phone to begin with when this problem started?
Which RUU did you flash? Sounds like maybe you did GB which would explain why CR3.7 works, and not 4.1.
Something you can try if you want is try the patch that has been posted letting phones on the original firmware run ROMs dev'ed for the new one.
Also check your HBOOT and check those versions.
Also could be bunk downloads of the newer ROMs. Have you tried re-downloading. Might be a good idea after checking all the other things.

[Solved] CM9 Bootloop (Android Apps Update then back to logo)

Okay I have been trying to get a CM9 rom to boot on my Atrix for about a week now. I am coming from Nottachtrix 1.3.1 on radio 37p with faux GB24 kernel. My bootloader is unlocked and I perform all necessary wipes before install. The furthest I have gotten any of the CM9 roms to boot is the screen that states Android Apps(or something) updateing. It then states starting system and boots back to the booting logo. I have tried fastboot -w. Formating data, cache, system, osh, pre install in mounts storage menu, and clearing both caches before and after install and I get the same results. This only happens with CM9 roms. I cannot get the CNA, Jokers, Turls, or Atrix tablet past the screen stated. I have tried with the latest rom racer from http://forum.xda-developers.com/showthread.php?t=1204500 and both recovery and touch recovery from rom manager and I get the same results. I have posted my issue in the dev section, but decided this was better as I did not want to clutter up the dev forum with my problems. Could it just be my Atrix or would the 37p radio have something to do with the bootlooping issue. Any help would be very much appreciated.
For some odd reason I decided to pull my external SD card before boot, and freaking BOOM BANG POW NO BOOTLOOP!
htcslic said:
Okay I have been trying to get a CM9 rom to boot on my Atrix for about a week now. I am coming from Nottachtrix 1.3.1 on radio 37p with faux GB24 kernel. My bootloader is unlocked and I perform all necessary wipes before install. The furthest I have gotten any of the CM9 roms to boot is the screen that states Android Apps(or something) updateing. It then states starting system and boots back to the booting logo. I have tried fastboot -w. Formating data, cache, system, osh, pre install in mounts storage menu, and clearing both caches before and after install and I get the same results. This only happens with CM9 roms. I cannot get the CNA, Jokers, Turls, or Atrix tablet past the screen stated. I have tried with the latest rom racer from http://forum.xda-developers.com/showthread.php?t=1204500 and both recovery and touch recovery from rom manager and I get the same results. I have posted my issue in the dev section, but decided this was better as I did not want to clutter up the dev forum with my problems. Could it just be my Atrix or would the 37p radio have something to do with the bootlooping issue. Any help would be very much appreciated.
Click to expand...
Click to collapse
Did you flash twice ?
Sent from my MB860 using XDA
I believe the problem is with the radio, I had this issue (on stock radio), then I upgraded to the newest CM9 Kang (0.4.4) and it went away. I then flashed the 37p radio in an attempt to fix a problem I've been having with my WiFi and bluetooth (they both don't work and cause reboots, I assume now it's a hardware problem) and the boot loop came back. I'm gonna try flashing some other radios to see if that works.
Yes flashed twice to no avail. Gonna try the 36p radio and stock to see if that fixes my issue.
Sent from my Wettest Dream Atrix!
giqbal said:
Did you flash twice ?
Sent from my MB860 using XDA
Click to expand...
Click to collapse
No need to flash any ROM twice. Not going to discuss other than to say its not require
OP......Not your phone or radio. There is something you are doing incorrectly. Quite possibly wipe procedure. If I remember when I am at my PC in the morning I will PM you exact instructions, start to finish, for flashing one of the CM9 builds.
Sent from my MB860 using xda premium
CaelanT said:
No need to flash any ROM twice. Not going to discuss other than to say its not require
OP......Not your phone or radio. There is something you are doing incorrectly. Quite possibly wipe procedure. If I remember when I am at my PC in the morning I will PM you exact instructions, start to finish, for flashing one of the CM9 builds.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Trust me, the CM9 kang (not turl's version, haven't tried that) didn't work unless you flashed it twice up to version 0.4.2 (I skipped 0.4.3 and installed 0.4.4 straight without wiping and only flashed once and it worked, so it's possible they fixed the bug). I don't think anyone knows why, but it's been confirmed many times.
CaelanT said:
No need to flash any ROM twice. Not going to discuss other than to say its not require
OP......Not your phone or radio. There is something you are doing incorrectly. Quite possibly wipe procedure. If I remember when I am at my PC in the morning I will PM you exact instructions, start to finish, for flashing one of the CM9 builds.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
That is what I am hoping, but I have tried every procedure I could find within the forums. Your start to finish is gonna be my last hope.
So I followed the same steps I use for other roms and managed to get this one working http://forum.xda-developers.com/showthread.php?t=1580449
Hey CaelanT any luck on getting me a step by step.
hitmannumber47 said:
Trust me, the CM9 kang (not turl's version, haven't tried that) didn't work unless you flashed it twice up to version 0.4.2 (I skipped 0.4.3 and installed 0.4.4 straight without wiping and only flashed once and it worked, so it's possible they fixed the bug). I don't think anyone knows why, but it's been confirmed many times.
Click to expand...
Click to collapse
Haven't had to do that with jokersax, turl, or CNA versions.
---------- Post added at 12:24 PM ---------- Previous post was at 12:24 PM ----------
htcslic said:
Hey CaelanT any luck on getting me a step by step.
Click to expand...
Click to collapse
Thanks for reminding me. Will get something to you here in a few!
<edit> Check your messages!
Gonna give it a shot soon as I get off work.
EDIT:
Unfortunately that was a no go as well. Followed everything to a tee and tried different kernels. I can only get the AOKP rom to boot, but its is currently without USB storage. Does anyone know a difference in the roms that would cause my Atrix to boot on one and not the other. I can also manage to get the MIUI to boot.
htcslic said:
Gonna give it a shot soon as I get off work.
EDIT:
Unfortunately that was a no go as well. Followed everything to a tee and tried different kernels. I can only get the AOKP rom to boot, but its is currently without USB storage. Does anyone know a difference in the roms that would cause my Atrix to boot on one and not the other. I can also manage to get the MIUI to boot.
Click to expand...
Click to collapse
I think something is going on with the kernel. You may have a bad processor. That's where my train of thought is right now. Sorry I couldn't get you up and running!
CaelanT said:
I think something is going on with the kernel. You may have a bad processor. That's where my train of thought is right now. Sorry I couldn't get you up and running!
Click to expand...
Click to collapse
Thanks for all you help. Finally got it to boot by removing external sd card.
[EDIT] Not sure but I believe the problem I had with m external sd is I still had an ext4 primary partition on it from when I was using Webtop2SD. Copying everything over to pc now and reformating external to see if my assumption is correct.
Looks like the ext4 partition on as was the culprit.
Sent from my Flipping ArtixTab!

[Q] Why are these roms not working?!? x.x

There were two main roms I wanted to try after I finally S-OFF'd my phone yesterday. Hatka Supreme 1.1.0 and Carbon. Neither of these worked and I'm glad that I backed up my S-OFF rooted stock rom. Hatka Supreme, the guy states its best to use Beast Mode kernal with the rom, which I flashed after I installed the room, and it just randomly reboots at the splash screen/a few seconds after getting into Android, so I restored my stock and everything worked fine. Next, I tried Carbon, and it just sat there at the carbon flash screen for like 20 minutes, so again, I had to restore to stock. Is there something I'm doing wrong? Is there a difference between Original Android Development and Android Development? Should I be looking at the original or what? I'm really lost, I'm going to try another rom, hopefully someone replies to this before it finishes downloading. Thanks for the help.
EDIT: I'd rather just sit and wait to see if someone replies before I waste time downloading another rom...any help would be appreciated.
rejectedjs said:
There were two main roms I wanted to try after I finally S-OFF'd my phone yesterday. Hatka Supreme 1.1.0 and Carbon. Neither of these worked and I'm glad that I backed up my S-OFF rooted stock rom. Hatka Supreme, the guy states its best to use Beast Mode kernal with the rom, which I flashed after I installed the room, and it just randomly reboots at the splash screen/a few seconds after getting into Android, so I restored my stock and everything worked fine. Next, I tried Carbon, and it just sat there at the carbon flash screen for like 20 minutes, so again, I had to restore to stock. Is there something I'm doing wrong? Is there a difference between Original Android Development and Android Development? Should I be looking at the original or what? I'm really lost, I'm going to try another rom, hopefully someone replies to this before it finishes downloading. Thanks for the help.
EDIT: I'd rather just sit and wait to see if someone replies before I waste time downloading another rom...any help would be appreciated.
Click to expand...
Click to collapse
Did you do a full wipe? System, factory reset, dalvik?
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
Did you do a full wipe? System, factory reset, dalvik?
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
It's probably your recoverys fault. On my last DNA I had nothing but failures. Once it took at least 30 times to get a Rom installed. Never solved the issue on that phone. I just soffed my new DNA yesterday, installed the newest cwm touch and flashed 4 different roms with no problem. Try re-flashing cwm touch.
pio_masaki said:
Did you do a full wipe? System, factory reset, dalvik?
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Yes, still the same thing, I'm not saying I didn't do that the first time though, that's like the basics of installing a rom.
str8upx said:
It's probably your recoverys fault. On my last DNA I had nothing but failures. Once it took at least 30 times to get a Rom installed. Never solved the issue on that phone. I just soffed my new DNA yesterday, installed the newest cwm touch and flashed 4 different roms with no problem. Try re-flashing cwm touch.
Click to expand...
Click to collapse
Do you think its TWRP's fault? After I found out there was no way to mount USB storage in TWRP I wanted to switch to CWM, but sadly I don't know how.
rejectedjs said:
Yes, still the same thing, I'm not saying I didn't do that the first time though, that's like the basics of installing a rom.
Do you think its TWRP's fault? After I found out there was no way to mount USB storage in TWRP I wanted to switch to CWM, but sadly I don't know how.
Click to expand...
Click to collapse
You could use the goomanager from the play store or use fastbook flash recovery cwm.img
Edit: for the touch version of cwm fastboot is required.
str8upx said:
You could use the goomanager from the play store or use fastbook flash recovery cwm.img
Edit: for the touch version of cwm fastboot is required.
Click to expand...
Click to collapse
I would rather use goomanager, because it seems easier, but the only thing it seems to be able to download is the twrp image. How would I set it to cwm?
I have canvas 2 running on suvi6 Jupiter rom i have some prob with this when i reboot some icon on home screen will disappear, i found that those apps which r installed on ext sd card its icon will disappear from home screen, but apps working in apps list, only icon from home screen disappeared.
Other problem is that while incoming a call i cannot see full picture of caller becoz half screen is black and half picture can be seen.
Please help me
Sent from my Micromax A110 using xda app-developers app
rejectedjs said:
I would rather use goomanager, because it seems easier, but the only thing it seems to be able to download is the twrp image. How would I set it to cwm?
Click to expand...
Click to collapse
Sorry I was mistaken, goomanager installs twrp not cwm.
Fastboot is easy to use, I'm at work so I can't to a step by step til I get home later. You should be able figure it out but if not I will help when I get home.
str8upx said:
Sorry I was mistaken, goomanager installs twrp not cwm.
Fastboot is easy to use, I'm at work so I can't to a step by step til I get home later. You should be able figure it out but if not I will help when I get home.
Click to expand...
Click to collapse
I don't know if you knew this already but I s-offed using moonshine, is that a problem? I installed cwm and tried installing hatka again and it did the same thing, restart like every three seconds into android. I don't know what to do anymore.
kundan.lohar said:
I have canvas 2 running on suvi6 Jupiter rom i have some prob with this when i reboot some icon on home screen will disappear, i found that those apps which r installed on ext sd card its icon will disappear from home screen, but apps working in apps list, only icon from home screen disappeared.
Other problem is that while incoming a call i cannot see full picture of caller becoz half screen is black and half picture can be seen.
Please help me
Sent from my Micromax A110 using xda app-developers app
Click to expand...
Click to collapse
Pretty sure you're in the wrong forum.
From my S-Off BadSeed DNA
rejectedjs said:
There were two main roms I wanted to try after I finally S-OFF'd my phone yesterday. Hatka Supreme 1.1.0 and Carbon. Neither of these worked and I'm glad that I backed up my S-OFF rooted stock rom. Hatka Supreme, the guy states its best to use Beast Mode kernal with the rom, which I flashed after I installed the room, and it just randomly reboots at the splash screen/a few seconds after getting into Android, so I restored my stock and everything worked fine. Next, I tried Carbon, and it just sat there at the carbon flash screen for like 20 minutes, so again, I had to restore to stock. Is there something I'm doing wrong? Is there a difference between Original Android Development and Android Development? Should I be looking at the original or what? I'm really lost, I'm going to try another rom, hopefully someone replies to this before it finishes downloading. Thanks for the help.
EDIT: I'd rather just sit and wait to see if someone replies before I waste time downloading another rom...any help would be appreciated.
Click to expand...
Click to collapse
I'm no expert, but when u flashed hatka, did u reboot into the system before flashing beast mode kernel? Flashing a kernel in the same recovery session is a no no. Also, beast mode is not compatible with carbon, fyi.
Sent from my HTC6435LVW using Tapatalk 4 Beta
kelvinnotcalvin said:
I'm no expert, but when u flashed hatka, did u reboot into the system before flashing beast mode kernel? Flashing a kernel in the same recovery session is a no no. Also, beast mode is not compatible with carbon, fyi.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I did that the first time, and thats when I started experiencing it, so I figured that was the problem. So I restored to stock, and then just tried flashing the rom and booting, still same thing, rebooting every 5 seconds. Sometimes I'm able to get into settings, scroll up and down a few times, and then it reboots.
EDIT: If I remember correctly, I didn't even flash beast mode kernel after I flashed carbon.
rejectedjs said:
EDIT: If I remember correctly, I didn't even flash beast mode kernel after I flashed carbon.
Click to expand...
Click to collapse
If you had you never would have seen the carbon boot animation I don't think, just a white scrambled screen.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
If you had you never would have seen the carbon boot animation I don't think, just a white scrambled screen.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
What exactly is the problem I'm experiencing here? x.x Of all roms I REALLY wanted to try Hatka, why me...
rejectedjs said:
What exactly is the problem I'm experiencing here? x.x Of all roms I REALLY wanted to try Hatka, why me...
Click to expand...
Click to collapse
I've had the same sort of thing happen to me when we first started working with CM. I had to lock up and run the RUU then unlock again, started flashing normally again after that.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
I've had the same sort of thing happen to me when we first started working with CM. I had to lock up and run the RUU then unlock again, started flashing normally again after that.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
You mean you want me to go back to pure stock and soff all over again?
rejectedjs said:
You mean you want me to go back to pure stock and soff all over again?
Click to expand...
Click to collapse
I don't want you to do anything, in was just saying what I did to correct it when it happened to me.
And no, I didn't day s-on, I said relocked, the RUU won't run on an unlocked device. Locked and son are different.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
I don't want you to do anything, in was just saying what I did to correct it when it happened to me.
And no, I didn't day s-on, I said relocked, the RUU won't run on an unlocked device. Locked and son are different.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
I've never had so many problems just trying to flash a Rom before, this is crazy...I'm seriously at a loss about what to do other than stay on rooted stock
bump?..I really want some help..
Did you figure it out? I'd do what pio said. He's kind of amazing. He's a very smart man who most likely knows what he's doing
Sent from my HTC6435LVW using xda app-developers app

Categories

Resources