I have been reading multiple threads/posts about the Beastmode v4 kernel. Yet, I am still a little bit confused. I had planned on trying to flash v3 this morning and then I saw v4 got released, so I decided to read up on it. I have it downloaded and waiting along with the cam fix just in case cam doesn't work.
Just curious on what I needed to do? I've read about a lot of bootloops happening because of over clock and under clock issues. I'd really like to try and flash this first time with out getting hung or stuck in a bootloop. I've read the entire http://forum.xda-developers.com/showthread.php?t=1959395&page=4 thread. However, v4 doesn't have a boot.img file in the .zip.
What do?
Also wanted to look at changing my radio to the 2.41 version on the ViperXL thread. If anyone has any links so I can read up on this, please post.
Just flash it in recovery
Sent from my HTC One XL using xda app-developers app
So mount to sd card and flash through TWRP, sweet.
Myrder said:
So mount to sd card and flash through TWRP, sweet.
Click to expand...
Click to collapse
if by mount you mean copy to sd card and then install like a normal ROM, then yes
absolutelygrim said:
if by mount you mean copy to sd card and then install like a normal ROM, then yes
Click to expand...
Click to collapse
Yes, lol. Getting ahead of myself. I tried copying and flashing, now I'm at a 10% hang...
EDIT: Never mind, went past the 10% straight to "finished"
Myrder said:
Yes, lol. Getting ahead of myself. I tried copying and flashing, now I'm at a 10% hang...
EDIT: Never mind, went past the 10% straight to "finished"
Click to expand...
Click to collapse
Did you have to do anything with boot.img? Or just flash the kernel. Did you need the cam fix?
GenuineMP5 said:
Did you have to do anything with boot.img? Or just flash the kernel. Did you need the cam fix?
Click to expand...
Click to collapse
I do need the cam fix, planned on flashing when I got Beastmode v4 installed.
As for the boot.img, the kernel .zip doesn't have one. With this kernel, it makes it in the Aroma installer.
Myrder said:
I do need the cam fix, planned on flashing when I got Beastmode v4 installed.
As for the boot.img, the kernel .zip doesn't have one. With this kernel, it makes it in the Aroma installer.
Click to expand...
Click to collapse
Sweet. Was hoping this was something that could be done 'on the fly'. I didn't want to have to worry about fastboot flashing anything today. lol
GenuineMP5 said:
Sweet. Was hoping this was something that could be done 'on the fly'. I didn't want to have to worry about fastboot flashing anything today. lol
Click to expand...
Click to collapse
Yeah, in one of the folders it has a file "abootimg". Which is where the Aroma installer makes the boot.img.
My only problem is it's not installing... i get a 10% hang for a few min and then it goes straight to finished...
Myrder said:
Yeah, in one of the folders it has a file "abootimg". Which is where the Aroma installer makes the boot.img.
My only problem is it's not installing... i get a 10% hang for a few min and then it goes straight to finished...
Click to expand...
Click to collapse
Mine seemed to work fine. It hung at 10% for what seemed like forever, then finally finished. Booted into Viper and checked the clockspeed in the tweaks app. I was able to move the max speed up to what I had selected in Aroma (1.8). Sweep2wake works too.
Maybe I need to factory reset then install viper again then the kernel?
Sent from my HTC One XL using xda app-developers app
i wiped the caches and flashed the kernel, it took a while to install but when it did it was working. is anyone else seeing their screen flip backwards every now and then? my whole status bar was like a mirror image and on the other side of the phone
Sounds like your kernel is conflicting with your ROM? That's what it sound like to me at least.
Sent from my HTC One XL using xda app-developers app
Myrder said:
I have been reading multiple threads/posts about the Beastmode v4 kernel. Yet, I am still a little bit confused. I had planned on trying to flash v3 this morning and then I saw v4 got released, so I decided to read up on it. I have it downloaded and waiting along with the cam fix just in case cam doesn't work.
Just curious on what I needed to do? I've read about a lot of bootloops happening because of over clock and under clock issues. I'd really like to try and flash this first time with out getting hung or stuck in a bootloop. I've read the entire http://forum.xda-developers.com/showthread.php?t=1959395&page=4 thread. However, v4 doesn't have a boot.img file in the .zip.
What do?
Also wanted to look at changing my radio to the 2.41 version on the ViperXL thread. If anyone has any links so I can read up on this, please post.
Click to expand...
Click to collapse
Can we refrain from starting multiple threads about essentially the same thing http://forum.xda-developers.com/showthread.php?t=1971667
this is not craigslist...
Related
Hello.
I recently bougth a SGS4G, it came with the original 2.2.1, and every thing worked fine.
I started to read about de updating the rom and got interested, after reading, I made de update using the one-click metode. I used the Stock_KJ6_+_root-One-Click.jar, it all went just fine, the phone run smoth, but when I tried to turn on the wifi connection every single time it gives the error message.
Does any one have any ideia on how to solve this problem?
Try it again, you may have had a bad download.
What error message are you seeing?
Posted from my SGS4G, thanks to Team Acid development
HrCorreia said:
Hello.
I recently bougth a SGS4G, it came with the original 2.2.1, and every thing worked fine.
I started to read about de updating the rom and got interested, after reading, I made de update using the one-click metode. I used the Stock_KJ6_+_root-One-Click.jar, it all went just fine, the phone run smoth, but when I tried to turn on the wifi connection every single time it gives the error message.
Does any one have any ideia on how to solve this problem?
Click to expand...
Click to collapse
airfluip1 said:
Try it again, you may have had a bad download.
Click to expand...
Click to collapse
No its not a bad download. He used my oneclick and wifi is broken because blastoff uses the bcm4329 module.
HrCorreia use the kernel in this thread. Just flash it in cwm. Your wifi should be fixed after that. If not post back and Ill see what I can do to help.
http://forum.xda-developers.com/showthread.php?t=1828171&highlight=blastoff
jeffsf said:
What error message are you seeing?
Posted from my SGS4G, thanks to Team Acid development
Click to expand...
Click to collapse
When I try to turn on the wifi connection, it always shows the message saying "error" on the connection status.
eollie said:
No its not a bad download. He used my oneclick and wifi is broken because blastoff uses the bcm4329 module.
HrCorreia use the kernel in this thread. Just flash it in cwm. Your wifi should be fixed after that. If not post back and Ill see what I can do to help.
http://forum.xda-developers.com/showthread.php?t=1828171&highlight=blastoff
Click to expand...
Click to collapse
I'll try that.
I faced same problem previously.. i fixed that by Reflashing the rom & root it again...
Sent from my GT-I9003 using Tapatalk 2
I'll have a fix for the oneclick tonight.
Thanks bhundven Ive been busy all weekend and when I have gotten home fixing that one click has been the least of my thoughts. I know bad eollie no cookie.
eollie, I didn't know he was using blastoff.
airfluip1 said:
eollie, I didn't know he was using blastoff.
Click to expand...
Click to collapse
Its all gravy man, I just happened to notice the name of the one click he used. Its was the one click I created to get root plus stock for coming back to stock. Ive known about the broken wifi I think I even spoke about it in the OP.
Thanks to all who tried to help me, and in fact realy helped me.:laugh::good:
I hope this topic manage to help others.
eollie said:
No its not a bad download. He used my oneclick and wifi is broken because blastoff uses the bcm4329 module.
HrCorreia use the kernel in this thread. Just flash it in cwm. Your wifi should be fixed after that. If not post back and Ill see what I can do to help.
http://forum.xda-developers.com/showthread.php?t=1828171&highlight=blastoff
Click to expand...
Click to collapse
You are a life saver friend
eollie said:
Thanks bhundven Ive been busy all weekend and when I have gotten home fixing that one click has been the least of my thoughts. I know bad eollie no cookie.
Click to expand...
Click to collapse
Eollie - did you ever update the OneClick?
Just curious because just tonight I flashed your OC... or the top one in this thread:
http://forum.xda-developers.com/showthread.php?t=1358498
Downloaded it fresh today. "Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2.5 kernel)"
Anyway, the wifi wasn't working. I flashed AntonX's BwaT kernel to get it back.
Am I missing something?
Thanks!
----
Related: I would've loved to flash straight to Valhalla Black but even though I found a post where VB built an experimental One Click for that, I couldn't actually find a JAR anywhere. Am I missing something here too? Apparently FB isn't accepting PMs....
I'm not sure why you're looking for one-click installers for everything. The typical way to install is using a zip in recovery. You should be able to find a good selection of ROMs and kernels that you can flash from the recovery that it sounds like you already have installed.
The one-click installers are generally when you have things so hozed up you need to get back to a relatively clean, know state. They generally aren't for getting a fully functional phone. Your WiFi problem is likely the driver that matches your kernel not being installed.
FB is around from time to time.
In general, I wouldn't hold your breath on anyone updating software from a couple years ago. Older projects eventually get archived or deleted as each ROM build you are working on can take 50 GB or more.
---
Posted from whatever phone booted today
Phone was super hosed. Would not restore a Nandroid backup.
A VB one-click would have been fastest.
Would gladly try a newer ROM but my wife and I use wifi-calling every day - until and unless somebody with a newer ROM figures that out, we're on GB.
jeffsf said:
I'm not sure why you're looking for one-click installers for everything. The typical way to install is using a zip in recovery. You should be able to find a good selection of ROMs and kernels that you can flash from the recovery that it sounds like you already have installed.
The one-click installers are generally when you have things so hozed up you need to get back to a relatively clean, know state. They generally aren't for getting a fully functional phone. Your WiFi problem is likely the driver that matches your kernel not being installed.
FB is around from time to time.
In general, I wouldn't hold your breath on anyone updating software from a couple years ago. Older projects eventually get archived or deleted as each ROM build you are working on can take 50 GB or more.
---
Posted from whatever phone booted today
Click to expand...
Click to collapse
Gingerbread is cool, especially if you need the proprietary WiFi calling feature. Several of us have poked at those bits and they aren't very happy with anything but the ROM they were built for.
You'll typically have problems if you flash a kernel through download mode "over" an existing ROM. Download mode is partition-at-a-time so it can't, for example, update kernel modules on that are on the same partition as the rest of the ROM.
Lots to pick from once you have custom recovery going.
---
Posted from whatever phone booted today
Back to the original question though - did Eollie or anyone update the kernel in the Rooted/stock one-click so that Wifi works? Maybe it was just a fluke that it didn't work for me?
(I'm asking for the next guy...)
JaimeZX said:
Back to the original question though - did Eollie or anyone update the kernel in the Rooted/stock one-click so that Wifi works? Maybe it was just a fluke that it didn't work for me?
(I'm asking for the next guy...)
Click to expand...
Click to collapse
I think bhundven made a fixed version and put it in the....this thread
http://forum.xda-developers.com/showthread.php?t=1358498
Sent from my Nexus 5 using XDA Premium 4 mobile app
TwitchyEye said:
I think bhundven made a fixed version and put it in the....this thread
http://forum.xda-developers.com/sh...read.php?t=1822626"]AntonX's BwaT + Stock Rom[/COLOR][/SIZE]
Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2.5 kernel)
Click to expand...
Click to collapse
...downloaded 24 Feb '14, but wifi didn't work afterwards. Had to flash the BwaT kernel.
bhundven said:
And done. The second post has been updated with the new oneclick.
This fixes wifi and removes the csc update. Enjoy!
(note, after rebooting it does go to recovery, so you can flash after oneclicking)
Click to expand...
Click to collapse
I see. Maybe he just made it boot to recovery instead so you still have to reflash the kernel.
Sent from my Nexus 5 using XDA Premium 4 mobile app
just rooted with the new 2.20 exploit! ive had this phone since june and ive seen multiple accounts where people have flashed international one x roms on there att one x. I don't want that to happen to me. can someone please point me in the direction which some good att compatible one x roms are. id like to have sense 4.5 and some good theme capability, I know all about cm10 and aokp, and there ild for me now..(had a Samsung skyrocket)
THANKS! Kole
Kole_Ackerson said:
just rooted with the new 2.20 exploit! ive had this phone since june and ive seen multiple accounts where people have flashed international one x roms on there att one x. I don't want that to happen to me. can someone please point me in the direction which some good att compatible one x roms are. id like to have sense 4.5 and some good theme capability, I know all about cm10 and aokp, and there ild for me now..(had a Samsung skyrocket)
THANKS! Kole
Click to expand...
Click to collapse
Stay in the "AT&T, Rogers HTC One X, Telstra One XL" forum (look up top) and you'll be fine. ROMs are in the Development subforums.
Isn't it annoying how they hide all the ROMs from us? They really make you dig for them! (<----click there!)
_MetalHead_ said:
Isn't it annoying how they hide all the ROMs from us? They really make you dig for them! (<----click there!)
Click to expand...
Click to collapse
thanks guys I appreciate it! sorry that forum name always confuses me. so I can flash any of these in the dev section?
thanks, Kole
Kole_Ackerson said:
thanks guys I appreciate it! sorry that forum name always confuses me. so I can flash any of these in the dev section?
thanks, Kole
Click to expand...
Click to collapse
Yes, they are all for our phone.
Don't forget about the Original Dev forum! AOSP goodness
http://forum.xda-developers.com/forumdisplay.php?f=1726
I have a hard time not endorsing CM10. It's so dang fast and smooth.
Sent from my JellyBlueX
Try them all
Sent from my HTC One XL using Tapatalk 2
mmapcpro said:
I have a hard time not endorsing CM10. It's so dang fast and smooth.
Sent from my JellyBlueX
Click to expand...
Click to collapse
Im having a hard time trying to figure out what to do next. I downloaded the gapps and unzipped my CM10 file where i unzipped all the stuff to unlock it and now have no idea what to do. How do i put CM 10 on my phone?
manturia said:
Im having a hard time trying to figure out what to do next. I downloaded the gapps and unzipped my CM10 file where i unzipped all the stuff to unlock it and now have no idea what to do. How do i put CM 10 on my phone?
Click to expand...
Click to collapse
You are unzipping it to get boot.img correct? Now rezip.fastboot boot.img Boot into recovery wipe data, system, cache, and dalvik cache. Install cm10 zip, wipe cache install gapps for jb
Edit. This should help also
http://forum.xda-developers.com/showthread.php?t=1952076
Swagged out rooted jelly bean HOX
tae_254 said:
You are unzipping it to get boot.img correct? Now rezip. Boot into recovery wipe data, system, cache, and dalvik cache. Install cm10 zip, wipe cache install gapps for jb. After that fast boot boot.img file
Edit. This should help also
http://forum.xda-developers.com/showthread.php?t=1952076
Swagged out rooted jelly bean HOX
Click to expand...
Click to collapse
okay so I entered "fastboot flash boot boot.img" after I replaced the boot.img file. It went back to the bootloader screen and selected recovery. It stays black.
I tried resetting the phone, going back to recoverty, get sent to the TWRP app. When i look under install under the sdcard, I dont see any roms.
Retrying a second time, reentered "fastboot flash boot boot.img" and am now stuck on the HTC Screen with red text "this build is for development purposes... etc"
what am i doing wrong?
If I ever actually get my phone into recovery mode I'll let you know -.-
Edit: Alrighty. That was annoying but I got it done. Shoulda known not to bother with automatic things -.-
Ended up having to manually flash TWRP to finally get it to stick. I think I'm going Nocturnal for now. Seems to have alot of goodies in it that I might enjoy. Eventually I'll probably "step down" to the slickest, smoothest, fastest ROM I can find and manually add in everything I intend to use though.
Been a LOOOOOOONG time since I had a device you could even flash though so I'll probably end up flashing excessively for a while. Havn't had one since my Xperia X1 was ran over and rained on... HEYYYY... X1... One X (1X) ! It's destiny
Sorry you need to fast boot boot.img first
swagged out rooted jelly bean HOX
econoura beacause
tae_254 said:
Sorry you need to fast boot boot.img first
swagged out rooted jelly bean HOX
Click to expand...
Click to collapse
Yeah this is what i did, but i was unable to get it to recovery. In wiping the data i seemed to have wided the sd card clean. It shows as unmounted in the TWRP mount menu. I have no idea what to do from here.
I cannot find the rom anywhere, even after i fast boot boot.img
manturia said:
Yeah this is what i did, but i was unable to get it to recovery. In wiping the data i seemed to have wided the sd card clean. It shows as unmounted in the TWRP mount menu. I have no idea what to do from here.
I cannot find the rom anywhere, even after i fast boot boot.img
Click to expand...
Click to collapse
Download on your PC and either try to transfer to SD card that way by mounting or adb push the file to your phone once in recovery. If that doesn't work you will have to run back to 2.20 and reroot.
When you were wiping you didn't press wipe external storage because that's what wipes the data off your SD.
Sent from my Xoom using xda app-developers app
tae_254 said:
Download on your PC and either try to transfer to SD card that way by mounting or adb push the file to your phone once in recovery. If that doesn't work you will have to run back to 2.20 and reroot.
When you were wiping you didn't press wipe external storage because that's what wipes the data off your SD.
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
I think thats what I accidently did. I can no long mount my SD, and when i go to check it what inside there is only TWRP. I guess i bricked it
manturia said:
I think thats what I accidently did. I can no long mount my SD, and when i go to check it what inside there is only TWRP. I guess i bricked it
Click to expand...
Click to collapse
Nope ruu back to 2.20 and redo the process
swagged out rooted jelly bean HOX
I thought this would be appropriate..
Sent from my One X using xda premium
Speaking of flash all the things, I'm already considering getting rid of Nocturnal. Apparently it makes it difficult to access the menu button. Several of the programs I use offer no other method of accessing the menu.
Kole_Ackerson said:
can someone please point me in the direction which some good att compatible one x roms are.
Click to expand...
Click to collapse
Its quite simple, as others have mentioned just stick to the Development and Original Development subforums in this "AT&T, ROgers HTC One X, Telstra One XL" section and you will be fine.
Or just stick to my index thread, which is an organized list all the ROMs and other mods: http://forum.xda-developers.com/showthread.php?t=1671237
If you wander into the forum section simply labelled "HTC One X" with no mention of AT&T, you are in the wrong place (forum section for the international version).
---------- Post added at 09:14 AM ---------- Previous post was at 09:10 AM ----------
Poetique said:
Speaking of flash all the things, I'm already considering getting rid of Nocturnal. Apparently it makes it difficult to access the menu button. Several of the programs I use offer no other method of accessing the menu.
Click to expand...
Click to collapse
Which Nocturnal ROM, there are like 4 of them (or more)? If its a Sense based Nocturnal ROM, just remap the "recents" button as with stock 2.20 in Settings>Display, gestures & buttons>Buttons. But I don't think there is an option to bring back the horrid 3-bar menu button for apps that don't have one built-in (if that is what you are looking for).
Not sure about the AOSP Nocturnal ROM, haven't used that one myself. But the AOSP ROMs usually have a button remap in settings as well.
please help! I do NOT care about my root, I do NOT care about my data I just really want this to be fixed, I'm almost crying, I have no idea what to do, all i wanted was a custom battery so i downloaded one, loaded it into some app called metamorph and it said it was all good but when i restarted my phone the notification bar was gone. I cannot pull it down and this is my first android device, I have had it for 3 days and it cost me a lot of money! please help I will do anything whatsoever, I'm so worried, I'm only 16. I tried restoring my phone to factory settings, wiping my memory card as if that would do anything. please help it's all I ask!
Hi there, I have had this problem before. I am no dev so I can't explain the technical issue, but this usually happens when you flash a mod that's not compatible with your ROM... if its compatible and your ROM has updated, the mod sometimes needs to be updated to be compatible with the latest version of your ROM.
Reflashing your ROM will completely fix the issue. I hate to say it, but ALWAYS do backups before flashing anything through recovery!!!
Sent from my One X using xda premium
Sorry
franki_667 said:
Hi there, I have had this problem before. I am no dev so I can't explain the technical issue, but this usually happens when you flash a mod that's not compatible with your ROM... if its compatible and your ROM has updated, the mod sometimes needs to be updated to be compatible with the latest version of your ROM.
Reflashing your ROM will completely fix the issue. I hate to say it, but ALWAYS do backups before flashing anything through recovery!!!
Sent from my One X using xda premium
Click to expand...
Click to collapse
Sorry I'm such a noob, I have no idea what I am doing, I don't know what flashing is or anything could you please tell me how to flash a ROM? please??? I will love you forever man I have no idea what to do, im so desperate right now
franki_667 said:
Hi there, I have had this problem before. I am no dev so I can't explain the technical issue, but this usually happens when you flash a mod that's not compatible with your ROM... if its compatible and your ROM has updated, the mod sometimes needs to be updated to be compatible with the latest version of your ROM.
Reflashing your ROM will completely fix the issue. I hate to say it, but ALWAYS do backups before flashing anything through recovery!!!
Sent from my One X using xda premium
Click to expand...
Click to collapse
He's not rooted it seems. You first need to calm down. Then, go to settings -> About phone and see what build you have. If it's 2.20 then go here. If it's 1.73 or 1.82 go here. If it's 1.85 then go here. Once rooted, if you have anything but 2.20 you won't need to flash the boot.img seperately. In order to flash the boot.img go here.
Mister J said:
He's not rooted it seems. You first need to calm down. Then, go to settings -> About phone and see what build you have. If it's 2.20 then go here. If it's 1.73 or 1.82 go here. If it's 1.85 then go here. Once rooted, if you have anything but 2.20 you won't need to flash the boot.img seperately. In order to flash the boot.img go here.
Click to expand...
Click to collapse
i am rooted on software 1.85 please help me get this stupid notification bar back, it happened when I used Metamorph to change my battery
Is there possibly a way to revert to the original through "metamorph"? Most tweaks or apps like this only work on certain devices, so check the reviews or description more thoroughly if it doesn't say your device.
Sent from my HTC One X using Tapatalk 2
sorry
tyessen said:
Is there possibly a way to revert to the original through "metamorph"? Most tweaks or apps like this only work on certain devices, so check the reviews or description more thoroughly if it doesn't say your device.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
no there is no way to revert in metamorph and i already wiped my device and the notification bar is still not there, I have no idea what to do.
HtcOneXProblem said:
no there is no way to revert in metamorph and i already wiped my device and the notification bar is still not there, I have no idea what to do.
Click to expand...
Click to collapse
That happened to me on my old LG G2X. I tried to do something similar with a different program. It was messing with SystemUI.apk. I had created a backup before it did its work so I just replaced it, rebooted and it was fine. Might not be the same problem just because the symptoms are similar. If you had an unmodified SystemUI.apk file you could probably just overwrite it. Worst case, just flash a new ROM.
But yeah, in the future always take backups before you do anything like that. I learned that the hard way a few times.
HtcOneXProblem said:
i am rooted on software 1.85 please help me get this stupid notification bar back, it happened when I used Metamorph to change my battery
Click to expand...
Click to collapse
In that case just back everything up and reinstall the rom.
Thanks
Mister J said:
In that case just back everything up and reinstall the rom.
Click to expand...
Click to collapse
thanks for everyone's help, i figured out that I did not have bootloader installed so I got that (it was a ***** because I had to fake the CID which took forever) and I installed a new ROM, thanks for the help guys, really means a lot to me
Hi guys. Loving the forums - I've been a watcher for a while, but have only just joined.
I'm having trouble installing most ROMs. They all hang at the opening screen, or continually reboot depending on which one it is. I've tried flashing boot.img with no success. I've had luck with Stuart's ROM, but was really hoping to find a stable ROM with Jelly Bean.
I've read through the noob guides and FAQs, done a heap of searches but can't find the answer, yet I'm sure I'm not the first with this issue. It looks like this guy was having the same problems, but he posted in the wrong area and I can't find a follow up...
I've rooted and unlocked all ok, can access bootloader and TWRP without any issues.
Does anyone know what I could be doing wrong? Or know where this has been answered before? Thanks a mil.
http://forum.xda-developers.com/showthread.php?p=33303798
This is in the q&a stickies. See if this helps.
Sent from my One X using xda premium
itscoby said:
Hi guys. Loving the forums - I've been a watcher for a while, but have only just joined.
I'm having trouble installing most ROMs. They all hang at the opening screen, or continually reboot depending on which one it is. I've tried flashing boot.img with no success. I've had luck with Stuart's ROM, but was really hoping to find a stable ROM with Jelly Bean.
I've read through the noob guides and FAQs, done a heap of searches but can't find the answer, yet I'm sure I'm not the first with this issue. It looks like this guy was having the same problems, but he posted in the wrong area and I can't find a follow up...
I've rooted and unlocked all ok, can access bootloader and TWRP without any issues.
Does anyone know what I could be doing wrong? Or know where this has been answered before? Thanks a mil.
Click to expand...
Click to collapse
Give the members here more details. What exactly interests you in JB ROMS? What have you been trying to flash? What are you on right now?
If you wish to have a great Rom with no nonsense I'd suggest to you ViperXL. It's foolproof. I too asked questions after tons of research and tutorials. Asking questions is better than banging your head. And of course stick to this this forum for ROMS and you'll avoid a cool looking paperweight.
Jon
Sent from my HTC One XL using xda premium
subarudroid said:
http://forum.xda-developers.com/showthread.php?p=33303798
This is in the q&a stickies. See if this helps.
Click to expand...
Click to collapse
Thanks! I'd read through this one and had tried flashing the boot.img as it suggests for those experiencing my problem. Unfortunately it made no difference. It's a helpful guide though - unfortunately it came after I'd worked it all out for myself from other forums and posts!
ToxicWaste said:
What exactly interests you in JB ROMS? What have you been trying to flash? What are you on right now?
Click to expand...
Click to collapse
Thanks Jon. I'm after Jelly Bean primarily to check out Google Now. I head up digital customer experience for a big Aussie company and am interested to see how it might help our customers (READ: Really I want to know how it can help me!)
I was on a rooted stock Telstra ROM but couldn't get the OTA JB update to work. I tried ViperXL 3.0.0, CyanogenMOD 10 and Tachi91's v2.1 MOD. ViperXL is what I want to run ideally.
Currently on Scott's CleanROM 5.1. I'm running One XL with Firmware 2.20.502.7.
By all means download Viper and flash that bad boy. Firmware 2.20 and Viper are good friends. No need to flash .img separately. While you're at it, check out some kernels in the Venom Hub.
You came to the right place for help though. Never think you can't ask a quesrion hers if you think research hasn't answered it for you.
I've been trying Google Now but it's not doing much for me. Still playing with it.
ATT HOX Premium App--Stock is fine but modded is Creative
ToxicWaste said:
By all means download Viper and flash that bad boy. Firmware 2.20 and Viper are good friends. No need to flash .img separately. While you're at it, check out some kernels in the Venom Hub.
You came to the right place for help though. Never think you can't ask a quesrion hers if you think research hasn't answered it for you.
I've been trying Google Now but it's not doing much for me. Still playing with it.
ATT HOX Premium App--Stock is fine but modded is Creative
Click to expand...
Click to collapse
regarding Viper, I just downloaded 2.4.0 and honestly don't know what to do next. Do I just move the file to the phone while it's plugged in? I rooted and unlocked last night, and installed twrp. I didn't want to start a thread about this and am having trouble finding the answer. Any help is a big thanks.
In Flames said:
regarding Viper, I just downloaded 2.4.0 and honestly don't know what to do next. Do I just move the file to the phone while it's plugged in? I rooted and unlocked last night, and installed twrp. I didn't want to start a thread about this and am having trouble finding the answer. Any help is a big thanks.
Click to expand...
Click to collapse
First and foremost, go into recovery (twrp) and make a backup. The backup is just that, a backup in case something goes wrong.
Now that you have a backup, plug your phone into you pc (assuming that's what you have) and select your phone to be mounted as storage.
Next, open your file location for your phone.
Next, locate Viper Rom.
Now, copy Viper (just drag and drop) it into your phones sd card.
Ok. Now you should copy your backup you made in twrp previously. Now you have it backed up in two locations.
Let's get started:
Boot into recovery (twrp).
Select Wipe and do the next 4 steps INSIDE twrp!
Now wipe dalvick cache.
Now wipe cache.
Now wipe system.
Now do a factory reset.
Now Select Install in twrp.
Find your Viper folder zip.
Select it.
Swipe to flash!
Follow Aroma Installer options to your liking.
Please be patient as it takes a while. Also, when it first boots it takes a while.
Any more questions, just ask us
ATT HOX Premium App--Stock is fine but modded is Creative
Thanks a lot. Installing now.:good:
In Flames said:
Thanks a lot. Installing now.:good:
Click to expand...
Click to collapse
No prob, man. Let us know how it went.
ATT HOX Premium App--Stock is fine but modded is Creative
Install was flawless, only bad thing is I have to work and can't toy with it for 8 more hours Thanks again!
In Flames said:
Install was flawless, only bad thing is I have to work and can't toy with it for 8 more hours Thanks again!
Click to expand...
Click to collapse
That sucks but it will be fun to learn about all the tweaks and such. I would go back to the Venom thread and flash the 2.4.0-->::2.4.1 update. I did the ota reset file too. Same thing you did before by wiping but you don't do or need a factory reset. Just flash those files in twrp. All up to date then.
ATT HOX Premium App--Stock is fine but modded is Creative
ToxicWaste said:
By all means download Viper and flash that bad boy. Firmware 2.20 and Viper are good friends. No need to flash .img separately. While you're at it, check out some kernels in the Venom Hub.
Click to expand...
Click to collapse
Hmm. Viper 3.0.0 really did not work and I followed the instructions closely. Perhaps I will try Viper 2.4.0 and then, if successful, look at updating my kernel, and then updating to 3.0.0? Current kernel is 3.0.8-01558-g7f75e5b Could this be causing me problems?
itscoby said:
Hmm. Viper 3.0.0 really did not work and I followed the instructions closely. Perhaps I will try Viper 2.4.0 and then, if successful, look at updating my kernel, and then updating to 3.0.0? Current kernel is 3.0.8-01558-g7f75e5b Could this be causing me problems?
Click to expand...
Click to collapse
Before you started to install Viper 3.0.0, what we're you on?
Sure, if let's say you had-Viper 2.4.0 but wishing to go to 3.0.0, THEN you need to flash the boot img separate since its a JB Rom.
The directions I provided are fool proof and the other user had success. So I'm wondering what you started out on before you loaded the Rom.
--------------------
Also, Viper and CleanRom are identical in the fact you DON'T need to extract the boot.img from the Rom zip as long as its under 3.0.0 (if flashing Viper). It's basically pointing twrp to the Viper zip and swiping to goodness.
ATT HOX Premium App--Stock is fine but modded is Creative
ToxicWaste said:
Before you started to install Viper 3.0.0, what we're you on?
Sure, if let's say you had-Viper 2.4.0 but wishing to go to 3.0.0, THEN you need to flash the boot img separate since its a JB Rom.
The directions I provided are fool proof and the other user had success. So I'm wondering what you started out on before you loaded the Rom.
Click to expand...
Click to collapse
So I've finally had success! Installed both 3.0.0 and 2.4.1 - I realised that I was much better off on 2.4.1 with all the venom tweaks than on 3.0.0 for seemingly not much more OS-wise, especially since I want to bypass my corporate exchange security policy, and Google Now was available as a mod.
Turns out I was trying to install on top of ROMs that wouldn't boot, and when I was trying to install from working ROMs, I wouldn't think to go back in to make sure debugging was on and fast boot was off.
The key things I've learned (which I initially missed in my initial scan of pages and pages of forum posts):
You need to install from a stable ROM that will let you boot into it
...because having a stable ROM will allow you to make sure the fast boot setting in the Power settings is off and USB debugging is on in Developer tools
You may need to flash boot.img if you're running bootloader 1.13 or above - even if the ROM installer instructs you not to
boot.img must be flashed before the installation, not after
They might sound obvious now, but this might hopefully help anyone else in my situation.
Thanks for all your help guys!
PS - LOVING Viper.
itscoby said:
So I've finally had success! Installed both 3.0.0 and 2.4.1 - I realised that I was much better off on 2.4.1 with all the venom tweaks than on 3.0.0 for seemingly not much more OS-wise, especially since I want to bypass my corporate exchange security policy, and Google Now was available as a mod.
Turns out I was trying to install on top of ROMs that wouldn't boot, and when I was trying to install from working ROMs, I wouldn't think to go back in to make sure debugging was on and fast boot was off.
The key things I've learned (which I initially missed in my initial scan of pages and pages of forum posts):
You need to install from a stable ROM that will let you boot into it
...because having a stable ROM will allow you to make sure the fast boot setting in the Power settings is off and USB debugging is on in Developer tools
You may need to flash boot.img if you're running bootloader 1.13 or above - even if the ROM installer instructs you not to
boot.img must be flashed before the installation, not after
They might sound obvious now, but this might hopefully help anyone else in my situation.
Thanks for all your help guys!
PS - LOVING Viper.
Click to expand...
Click to collapse
Good to hear you got it up and running. Viper was recommended to me and man once I played with it and tweaked it I'm having a hard time wanting to flash anything else. If I do its going to be 3.0.0. The tweaks and ElementalX kernel are just unreal.
P.S. Hitting the Thanks button is a good way to show your appreciation.
Sent from my HTC One XL using xda premium
So I've been more of a stalker of the XDA community for a while, never really needed to ask a question because I usually find the answers on the boards pretty handily or by some fluke things work for me without the need to post anything. But now that time has come to an end.
I had Jellybam 4.1.2 on my device flashed with whatever kernel came with it, and when my battery died yesterday the phone was stuck in a boot loop. Keep in mind that prior to that 1) It had never done this on a reboot and 2) the correct kernel had been flashed via fastboot. My hboot is 1.14. The reason I'm not posting this question in the Jellybam post in android development is because 1) I'm a n00b to posting on here and 2) this is now happening with any other rom I install (most recent is MIUI which I flashed late last night, started up normally, then got caught in a boot loop on a reboot).
I follow the normal steps of going into TWRP, flashing cache/davlik, factory wipe, system wipe, then installing, doing the gapps if necessary, or following the instructions on any aroma installers, then rebooting into fastboot and flashing the kernel so i don't get boot loops on the initial start up. I'm also doing this on a mac, but the command lines in terminal are pretty straight forward and i'm just doing normal ADB / fastboot commands.
I'm perplexed now and I can't figure out what changed or what I did differently that's causing this. Any help would be most appreciated and I apologize if this is somehow a cross or repeat post, but I couldn't find much like it.
Do you have an Evita or Endeavour phone?
Sent from my HTC One XL using xda premium
It sounds like you are doing everything correct. Also seems like you have a good grasp of what to do. My thought is even if your initial install went though. Something in the bootimg may be corrupt. Perhaps try redownloading your preferred rom? And try again.
Sent from my One X using xda premium
ToxicWaste said:
Do you have an Evita or Endeavour phone?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Evita
subarudroid said:
It sounds like you are doing everything correct. Also seems like you have a good grasp of what to do. My thought is even if your initial install went though. Something in the bootimg may be corrupt. Perhaps try redownloading your preferred rom? And try again.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I've tried a couple times with the same result. I'll try again and see if anything different happens. Maybe just by some miracle I'll get it working again
I'm not sure how it works with safari for Mac. I do know that when I download ROMs with crome it some how downloads corrupt zips. On ei9 it works fine.
Sent from my One X using xda premium
uncledoobie said:
So I've been more of a stalker of the XDA community for a while, never really needed to ask a question because I usually find the answers on the boards pretty handily or by some fluke things work for me without the need to post anything. But now that time has come to an end.
I had Jellybam 4.1.2 on my device flashed with whatever kernel came with it, and when my battery died yesterday the phone was stuck in a boot loop. Keep in mind that prior to that 1) It had never done this on a reboot and 2) the correct kernel had been flashed via fastboot. My hboot is 1.14. The reason I'm not posting this question in the Jellybam post in android development is because 1) I'm a n00b to posting on here and 2) this is now happening with any other rom I install (most recent is MIUI which I flashed late last night, started up normally, then got caught in a boot loop on a reboot).
I follow the normal steps of going into TWRP, flashing cache/davlik, factory wipe, system wipe, then installing, doing the gapps if necessary, or following the instructions on any aroma installers, then rebooting into fastboot and flashing the kernel so i don't get boot loops on the initial start up. I'm also doing this on a mac, but the command lines in terminal are pretty straight forward and i'm just doing normal ADB / fastboot commands.
I'm perplexed now and I can't figure out what changed or what I did differently that's causing this. Any help would be most appreciated and I apologize if this is somehow a cross or repeat post, but I couldn't find much like it.
Click to expand...
Click to collapse
My phone did this once too. Never figured out why but the way I stopped it was to nandroid data, then wipe everything, reinstall the Rom and restore only data. After this it never bootlooped again.
Sent from my Venom1 XL using Xparent Red Tapatalk 2
ImagioX1 said:
My phone did this once too. Never figured out why but the way I stopped it was to nandroid data, then wipe everything, reinstall the Rom and restore only data. After this it never bootlooped again.
Sent from my Venom1 XL using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Ok, I'll give that a shot. I installed CleanRom 5.1 today, ran some reboots and that seemed to clear it up. It might be a Jellybean thing, but who knows. Thanks for all the suggestions and quick responses!
Oh yea there is some discussion about a Rev-a or rev-b that is on your box having issues with 4.2 jb not working. I think its rev-b that everyone is having issues with.
Sent from my One X using xda premium