Related
No longer supporting TWRP.
Does this build include the charging under recovery, aroma fix? Also, just out of curiosity, why not use 2.4.0.0 alpha as base?
PowerPC said:
Does this build include the charging under recovery, aroma fix? Also, just out of curiosity, why not use 2.4.0.0 alpha as base?
Click to expand...
Click to collapse
It does support that. Aroma my testers said it work. I was talkin with dees_troy, He said 2.4.0.0 isn't exactly ready yet. So 2.3.3.0 is stable.
Flyhalf205 said:
It does support that. Aroma my testers said it work. I was talkin with dees_troy, He said 2.4.0.0 isn't exactly ready yet. So 2.3.3.0 is stable.
Click to expand...
Click to collapse
The build in OP boots and ADB works, so it must be the right one....right?
cenobite138 said:
The build in OP boots and ADB works, so it must be the right one....right?
Click to expand...
Click to collapse
Yes! thank you for checking! I want a vacation when CWM is good lol
Re: [RECOVERY]TWRP v2.3.3.0 [1/22/2013]
Backed up perfectly. We shall see what this puppy can do later on. Just cause I can't recall, must I install the HTC Dumlock files?
Sent from my HTC6435LVW using Tapatalk HD
idkwhothatis123 said:
Backed up perfectly. We shall see what this puppy can do later on. Just cause I can't recall, must I install the HTC Dumlock files?
Sent from my HTC6435LVW using Tapatalk HD
Click to expand...
Click to collapse
You must if you want to use it. That hasn't been tested actually.
Hey Fly,
Thank you again for all of your hard work on this! I have tested every function that I usually use in TWRP and so far so good. No issues with 3 separate backups now, even changing the name. It is especially fast at making backups, only a minute or so. Flashing (even with Aroma) seems to be quick and painless. Add in the Flash Image app and this phone is worth some of my time now. No longer am I stuck getting my flash fix on my other 4 devices. If I had any thanks left you would get them all...but you already did.
Cheers
Re: [RECOVERY]TWRP v2.3.3.0 [1/22/2013]
jschill31 said:
Hey Fly,
Thank you again for all of your hard work on this! I have tested every function that I usually use in TWRP and so far so good. No issues with 3 separate backups now, even changing the name. It is especially fast at making backups, only a minute or so. Flashing (even with Aroma) seems to be quick and painless. Add in the Flash Image app and this phone is worth some of my time now. No longer am I stuck getting my flash fix on my other 4 devices. If I had any thanks left you would get them all...but you already did.
Cheers
Click to expand...
Click to collapse
I meant to check if changing names would cause issues. Good looking out
Re: [RECOVERY]TWRP v2.3.3.0 [1/22/2013]
Went to factory reset and recovery hot booted... Weird
Sent from my HTC6435LVW using Tapatalk HD
does the x920d versions support external SD cards?
Re: [RECOVERY]TWRP v2.3.3.0 [1/22/2013]
katsuya82 said:
does the x920d versions support external SD cards?
Click to expand...
Click to collapse
No. Didn't know you guys had an external. So you guys have internal and external storage? If you do what is the mount point of the external then?
Sent from my ADR6425LVW using Tapatalk 2
Here are some more themes:
http://forum.xda-developers.com/showthread.php?t=2058212
Flashing now.. had lots of AROMA problems with 2.4.0.0, hopefully this version will be better!
EDIT:
Can't get adb to recognize the device D: Worked fine in 2.4.0.0...
skmpowdjy said:
Here are some more themes:
http://forum.xda-developers.com/showthread.php?t=2058212
Flashing now.. had lots of AROMA problems with 2.4.0.0, hopefully this version will be better!
EDIT:
Can't get adb to recognize the device D: Worked fine in 2.4.0.0...
Click to expand...
Click to collapse
which device? There are three And is Aroma working well for you on this build?
Can't be the DLX because of this post. http://forum.xda-developers.com/showpost.php?p=37060618&postcount=4
Haha sorry I am using the Verizon Droid DNA, so I downloaded the _DLX.zip package and flashed it in fastboot.. is that correct?
EDIT: I see that other have had success, so I'm going to try re installing the drivers and see what happens.
EDIT 2: Reinstalled the drivers (from HTC Sync) on 2 computers and still no adb I can't test AROMA quite yet because I need to get the files onto the phone first through adb
skmpowdjy said:
Haha sorry I am using the Verizon Droid DNA, so I downloaded the _DLX.zip package and flashed it in fastboot.. is that correct?
EDIT: I see that other have had success, so I'm going to try re installing the drivers and see what happens.
EDIT 2: Reinstalled the drivers (from HTC Sync) on 2 computers and still no adb I can't test AROMA quite yet because I need to get the files onto the phone first through adb
Click to expand...
Click to collapse
If I can get other feedback of it not working i'll look into it. I wiped my linux box(my way of building recoveries) clean as can be. Got to rebuild it today. So if I can get other feedback of it not working i'll look into it more. But all the code looks right to make ADB turn on.
Try doing this. I learned this on the Rezound. Go under advanced. ADB Sideload. Go into it and back out of sideload. That usually jump started ADB for me.
Flyhalf205 said:
Try doing this. I learned this on the Rezound. Go under advanced. ADB Sideload. Go into it and back out of sideload. That usually jump started ADB for me.
Click to expand...
Click to collapse
Oh, hey, that did the trick! Thanks! Will report back with Aroma status in a bit.
EDIT:
adb will connect automatically sometimes, but sometimes I have to do the sideload trick to get it to connect.
Aroma seems to work perfectly on installer pages without a whole lot of content, but on pages like those found in CODIS with tons of options, it still freezes sometimes. Much more stable, though
Thanks for all your work and dedication!
Just another confirmation that this version of TWRP worked with aroma
http://forum.xda-developers.com/showpost.php?p=37133875&postcount=612
past 3 posts showed him having issues with aroma. This version of TWRP set him straight :good:
i cant get the real icon theme to change anything on viperdna using twrp 2.3.3.0 but i did get the red reload theme to work for it though
idkwhothatis123 said:
Went to factory reset and recovery hot booted... Weird
Sent from my HTC6435LVW using Tapatalk HD
Click to expand...
Click to collapse
I was having the same issue last night. But it happened on any type of wipe I tried. So I tried reflashing recovery, still did the same thing. It's odd because I was able to wipe everything before I installed a different ROM yesterday morning.
Edit: Removed the custom theme I was using and all is well. Go figure.
Hey guys, I'm new but have been reading these forums for a while. I've rooted and unlocked 3 phones of mine with no problems but My HTC Evo LTE was ready for an upgrade so I tried to install a new rom, in the process I accidentally erased my back up. I have apps and system back up on titanium. I've read the don't panic thread, nothing helped. I've tried flashing the kernel and just about everything I know how to do.
So right now I have an unlocked device Jewel S-on, hboot 1.12, radio 1.02.12.0427 with TWRp Recovery installed. I have tried Vipers jellybean rom, Mean Rom ICS, and and a rooted stock rom.
All do the same thing, TWRP starts installing the rom and then it reboots real quick before the bar gets to 1/2, it reboots in the HTC quietly brilliant screen and the bar in the upper right goes up twice and then it just freezes and sits on the screen forever until i power it down and reboot into bootloader and nothing is installed. any ideas?
What version of twrp are you using?
You may not have the latest twrp recovery. Older versions will reboot or fail on install. There have been a few changes to the installers, especially with son users since hboots have become more restricted
bigdaddy619 said:
What version of twrp are you using?
Click to expand...
Click to collapse
Let's see, I'm running.....TWRP 2.4.1.0
mxbmx930 said:
Let's see, I'm running.....TWRP 2.4.1.0
Click to expand...
Click to collapse
download this and try 2.3.1.0 http://d-h.st/R9E
2.4.1.0 does not work properly unless you are using a 3.16 rom with updated binaries and you have the latest firmware installed
Glad I decided to hold off on updating twrp then
om4 said:
Glad I decided to hold off on updating twrp then
Click to expand...
Click to collapse
There is nothing wrong with the latest twrp, but the rom you are installing has to be compatible with it. The newest MeanBean is. It's kind of funny that the op has the most out of date phone firmware you can have but somehow updated his twrp to the newest available.
Sent from my icrap 2 using Tapatalk HD
bigdaddy619 said:
download this and try 2.3.1.0
2.4.1.0 does not work properly unless you are using a 3.16 rom with updated binaries and you have the latest firmware installed
Click to expand...
Click to collapse
Wow, so easy. I can't believe I spent all those hours frustrated trying to figure what I was doing wrong. I put 2.3.1 on and first try, installed fine. I have one more question, I downloaded titanium to reinstall everything and it's saying ERROR: I could not acquire root privileges, this app will not work. I installed Viperboys Stock Rooted 3.15.651.16 deodexed and SU is on there, I even updated it. Any ideas?
thanks a lot for the help so far.
cruise350 said:
There is nothing wrong with the latest twrp, but the rom you are installing has to be compatible with it. The newest MeanBean is. It's kind of funny that the op has the most out of date phone firmware you can have but somehow updated his twrp to the newest available.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
I usually wait at least a week to see if any problems come up
Anyone have an idea why every time I install an aosp rom it glitches at the Samsung boot screen then just goes black and I have to pull the battery? I've installed clean, jelly beans and jedi Rom without issue. Any help is appreciated.
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
dudeicles said:
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
Click to expand...
Click to collapse
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
dudeicles said:
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
Click to expand...
Click to collapse
Odin to stock then re unlock and try this all again? I'm not sure what else you can try. I flip between aosp and tw almost daily
Sent from my SCH-I605 using Tapatalk 2
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Heh I think I can I think I can...I was thinken are you trying to flash the file that the post links to because thats not the right one you need to get the note 2 lte one tolte..just a though I downloaded the wrong one first but caught it
http://changelog.bbqdroid.org/#t0lte/cm10.1/next
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Yeah it can't hurt even if they don't say that
Sent from my SCH-I605 using Tapatalk 2
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Would it help in any way to change to CWM when flashing my AOSP roms?
dudeicles said:
Would it help in any way to change to CWM when flashing my AOSP roms?
Click to expand...
Click to collapse
I would try cwm, I had a gs3 that couodnt flash anything with cwm but could with twrp, my note was the opposite, cwm was awful on it.
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
dudeicles said:
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
Click to expand...
Click to collapse
I've heard too many issues with cwm to even try it. Twrp has been flawless for me so why switch? If it ain't broke, don't fix it.
Sent from my SCH-I605 using Tapatalk 2
Ok, so update - Odin'd back to stock and re-rooted using the Casual method. I have the most recent TWRP installed and when i install the AOSP rom it does the exact same thing. I'm thinking about videotaping what the boot animation does and maybe someone can look at it and see what the cause may possibly be.
If anyone has any other suggestions i'm all ears. Again, any rom based on STOCK works without issue (Clean Rom, Jelly Beans and Jedi), but only AOSP roms (And CWM) crash the phone at "Samsung Galaxy Note II" screen on startup.
Thanks for the suggestions so far, just weird it's not working. I may have the single note 2 to never run AOSP roms. LOL
so... oddly enough i still have trouble installing AOSP roms. the only AOSP rom i have been able to install so far is Paranoid Droid. I am slowly trying each one just to see which one i can force to work. Am I the only person who can't just flash whichever rom I want whenever?
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Follow the advice to Odin back to stock and start over. Otherwise, get a replacement and tell them it's acting weird and slow haha.
Sent from my SCH-I605 using xda app-developers app
Same here!!
spydersilk said:
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Click to expand...
Click to collapse
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
slinky42 said:
I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
This is standard on 4.2.2 ROMs. It is related to the multi-user implementation.
slinky42 said:
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
Did you ever get your phone to install the AOSP Roms? Mine worked when l just let the phone sit. Now it works fine all the time.
Sent from my SCH-I605 using xda app-developers app
I have just recently received my replacement evo after smashing my old one. The phone was already fully upgraded to the latest JB software and hboot 2.09. The first thing i did was S-OFF using the DirtyRacun method all went well except for a few user errors but eventually achieved S-OFF. After that was done i installed TWRP recovery v2.3.3.0. After flashing Viper Rom my phone had random reboots spanning from minutes apart to a few hours apart. I redownloaded the same rom wiped everything again and the problem stayed consistent. so i decided to switch roms and tried PACman aokp rom and the same problem exist there also. is this a hardware issue or a result of an error during S-OFF? i have a couple logs from the app "Bootlog Uptime" if that may be of any assistance.
S-OFF using DirtyRacun
HBoot 2.09
TWRP v2.3.3.0
Roms Tried: Viper Rom and PACman aokp
Stock kernels
logs attached.
Try the latest TWRP?
... Sent from my 'Oops! Should've bought the S3!' via XDA-Developers App.
Delakit said:
Try the latest TWRP?
... Sent from my 'Oops! Should've bought the S3!' via XDA-Developers App.
Click to expand...
Click to collapse
I've heard nothing but bad things about the latest TWRP such as the touch screen not working so i decided it would be best to just stay away from it.
kcdre said:
I've heard nothing but bad things about the latest TWRP such as the touch screen not working so i decided it would be best to just stay away from it.
Click to expand...
Click to collapse
Try twrp 2.4.1.0 all my firmware including the touch panel drivers and have zero issues
Sent from my PoS MoPho
bigdaddy619 said:
Try twrp 2.4.1.0 all my firmware including the touch panel drivers and have zero issues
Sent from my PoS MoPho
Click to expand...
Click to collapse
I guess i could try updating the recovery and flashing again but ive never had this problem previously with 2.3.3.0. I just want to be sure its not hardware related before the return window closses for me to return this device for a new one.
I updated my recovery to the latest version and did a fresh install of viper rom and just had another random reboot. starting to think the problem is hardware related. ill have a log attached and hopefully someone will have a little insight on what's going on.
kcdre said:
I updated my recovery to the latest version and did a fresh install of viper rom and just had another random reboot. starting to think the problem is hardware related. ill have a log attached and hopefully someone will have a little insight on what's going on.
Click to expand...
Click to collapse
Post the log in the Viper thread, unless you've already done so. One of the devs will be able to take a look at it and hopefully be able to tell you what the problem is.
Sent from my EVO using xda premium
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