Related
Well new company gave me 20% Sprint discount and have become sick of my Tmobiles poor coverage. However I fear wimax might be sucky too here in Seattle. Anyway, long time member here and have been involved in the HTC Sensation and One forums. Both with very very stable roms and kernals.
I was excited to pick up a couple Sprint Galaxy epics and the guy at Sprint had his all rooted and claimed it was smoking fast.
However I came to this forum and see all kinds of complaints of loss of stability just from simple Root of the Epic? Also have not read any stable ICS roms and I have read all of the threads. Plus read this phone is very easy to brick under clockwork. With sensation we use Aroma and it rocks!
So before I move on, I am not looking to break rules on asking ROM questions. I simply would like some input on what ICS rom is stable and supported still as I see many devs have moved on the the sg3 here.
What kernal and radio or what you call modem is stable and how do you find what is for your phone match?
Lastly, what is safest way to ROOT and flash ROMS for this phone?
I did read the stickies but am still confused.
I may be just happy at first to simply ROOT and install the fix for Hot Spot Wi fi and go from there.
Thanks so much.
Not even sure if phones will arrive with stock ICS tomorrow or GB...
Ice
The SAFEST way to flash stock ROMs in case of emergency is using Odin.I've found both stock ROMs (GB & ICS) very stable, however I reboot my phone everyother day (windows habit).
This thread http://forum.xda-developers.com/showthread.php?t=1525495 was my starting point.
rovar said:
The SAFEST way to flash stock ROMs in case of emergency is using Odin.I've found both stock ROMs (GB & ICS) very stable, however I reboot my phone everyother day (windows habit).
This thread http://forum.xda-developers.com/showthread.php?t=1525495 was my starting point.
Click to expand...
Click to collapse
First off thank you for your reply. Interesting, I have read ODIn maybe responsible for bricking many of these phones is that incorrect? Lots of what I found seeing the people are very unstable with the custom roms so far for ICS for this phone of course stock ICS will be here soon.is there the ability to just root the phone and leave the stock ics ROM and just run the sprint hot spot mod.
Sent from my Sensation 4G using xda premium
iceshark said:
First off thank you for your reply. Interesting, I have read ODIn maybe responsible for bricking many of these phones is that incorrect? Lots of what I found seeing the people are very unstable with the custom roms so far for ICS for this phone of course stock ICS will be here soon.is there the ability to just root the phone and leave the stock ics ROM and just run the sprint hot spot mod.
Sent from my Sensation 4G using xda premium
Click to expand...
Click to collapse
Odin never causes any bricks as long as the process is not interrupted. Most of the instability is caused by user error. From my experience, all fresh (by fresh I mean wipe data/cache and format system) custom ROM installs have been rock solid stable. Also, most network issues are fixed by updating profile/prl. Official ICS is already out, it is build FF18. Stock ICS will not normally have the hotspot mod. You will have to use a hack to install it yourself. If you want a stock ICS experience, use this odin package (reset user data) to odin your phone to pre-rooted FF18:
http://forum.xda-developers.com/showthread.php?t=1721229
And here is your hotspot hack:
http://forum.xda-developers.com/showthread.php?t=1760712
Nonetheless, I see no reason why you wouldn't just save yourself the time and flash a custom ICS ROM.
Imho, there isn't any ics custom rom as of yet that is 100% stable, glitch-free, and reliable. I would wait it out until more polished versions come out. If there is a pretty good one to try, i'd say the blu kuban.
revamper said:
Odin never causes any bricks as long as the process is not interrupted. Most of the instability is caused by user error. From my experience, all fresh (by fresh I mean wipe data/cache and format system) custom ROM installs have been rock solid stable. Also, most network issues are fixed by updating profile/prl. Official ICS is already out, it is build FF18. Stock ICS will not normally have the hotspot mod. You will have to use a hack to install it yourself. If you want a stock ICS experience, use this odin package (reset user data) to odin your phone to pre-rooted FF18:
http://forum.xda-developers.com/showthread.php?t=1721229
And here is your hotspot hack:
http://forum.xda-developers.com/showthread.php?t=1760712
Nonetheless, I see no reason why you wouldn't just save yourself the time and flash a custom ICS ROM.
Click to expand...
Click to collapse
Thanks, I think we are on the same page with this!
So I just loaded the FF18 Full Restore and Samsung drivers as indicated in this thread,
http://forum.xda-developers.com/showthread.php?t=1670110
I also tested after unzipping to a folder and the ODEN program comes up waiting for me to hook up phone I dont have yet till tomorrow.
I also watched this video and it seems very easy to do if this is correct process,
http://www.youtube.com/watch?v=_IL21F8Gfbs
Still some clarifying questions,
1. If my new phone comes with ICS already pushed to it. Do I simply still install FF18 to get root for the ICS rom?
2. If phone does not come with ICS will this install ICS and Root?
3. Do I need to use this or Caulkins to wipe data first before I do this process on phone out of the box new?
http://forum.xda-developers.com/showthread.php?t=1670110
Also I am little nervous reading this post from SFHUB<, Is he saying not to do the above process thru the built in Odin recovery in the phone if it comes with stock ICS in it? What does this mean???
The Epic 4g Touch has a bug in it's emmc controller that can cause the /data partition to become inaccessible/unrecoverable sometimes thanks to the wipe process when flashing from ICS recoveries... DO NOT FLASH FROM ICS RECOVERIES!!!!
7/11/12 edit: In the FF18 source Garwynn has confirmed the presence of the offending code that triggers the emmc bug (http://forum.xda-developers.com/show...1&postcount=32) meaning that it will eventually be safe to flash from ICS as long as the offending code is removed by the dev of the kernel/rom...
- Please see this (http://forum.xda-developers.com/show....php?t=1525495) thread by xST4T1K which details how NOT to brick your device... It is slightly out of date but still very relevant... if you want a more technical understanding of what this emmc bug is and why this is happening you can see Sfhub's thread in general related to it (http://forum.xda-developers.com/show....php?t=1644364 ). The OP contains all of the information that our users have been able to figure out about this bug... Be sure to thank these people, as their hard work has made it exponentially safer for all of us to flash ICS roms on our phones...
-Every ICS rom will have a flashing guide in it's dev thread, its HIGHLY suggested you read and reread the guide for the rom you want to flash and follow it EXACTLY, taking the extra time upfront to fully understand what you're about to do will save you alot of trouble going forward.
-Put simply though you will always want to ODIN or Mobile ODIN (mobile Odin is an app made by the dev chainfire, available in the play store, that allows you to preform Odin flashes from your phone without using a PC) the el26 Gingerbread kernel/recovery and flash any ICS roms from that. NEVER FLASH FROM AN ICS RECOVERY, THAT IS HOW BRICKS ARE MADE!!!! Also do NOT use Rom Manager or Touch recovery!!!!
- Currently there are some ICS recoveries that are thought to be safe to flash from thanks to the work done on the emmc bug. If one of these is included in your rom it will be noted by the dev in the rom thread, however the safest way is still just to Odin back to el26 in order to avoid any chance of bricking!
Next, once I do this FF!8 and have root and ICS. If I want to dabble in custom roms. I am guessing they are installed by CWM from file downloaded to root of SD card like normal. I do not find CWM touch for this phone anywhere. I am sure I am missing it. It seems from reading the exploit in ICS kernal is causing the bricks. So I am guessing to use SF hubs or Claukins data wipe before loading custom roms. Are we beating to the same drum here?
Will correct radio or modem be installed automtic with FF18 or custom roms? I see many threads just on modems.
Thanks and thanks for the hot spot mod.
optimummind said:
Imho, there isn't any ics custom rom as of yet that is 100% stable, glitch-free, and reliable. I would wait it out until more polished versions come out. If there is a pretty good one to try, i'd say the blu kuban.
Click to expand...
Click to collapse
Thats what it seems from hours reading each ROM thread. Reminds me of the Sensation when GB and or ICS first leaked. Will most likely just root stock and go from there.
CWM is in the kernel. Current kernels such as chris41g's or AGAT's kernels have patched up recoveries that avoid the emmc bug, so they are completely safe. You should use calkulins format all before flashing a rom in CWM.
For odin, it wouldn't hurt to odin sfhubs wipe data/cache, but it's not necessary. As long as you use the reset user data odin package for FF18, it will take you to stock rooted FF18. Regardless of what rom your phone comes with, run that odin package. You don't need to worry about the modem either because it will install the latest one. Be sure to update your profile/prl in settings>about>system updates after.
If you want to try a custom rom, use odin to flash a kernel with cwm (agat's or chris41g's). Once you have a recovery, flash calkulins format all, and then the ROM of your choice. Modems are not installed through CWM rom zips. You'll have to flash a modem zip in recovery or odin a modem tar.
revamper said:
CWM is in the kernel. Current kernels such as chris41g's or AGAT's kernels have patched up recoveries that avoid the emmc bug, so they are completely safe. You should use calkulins format all before flashing a rom in CWM.
For odin, it wouldn't hurt to odin sfhubs wipe data/cache, but it's not necessary. As long as you use the reset user data odin package for FF18, it will take you to stock rooted FF18. Regardless of what rom your phone comes with, run that odin package. You don't need to worry about the modem either because it will install the latest one. Be sure to update your profile/prl in settings>about>system updates after.
If you want to try a custom rom, use odin to flash a kernel with cwm (agat's or chris41g's). Once you have a recovery, flash calkulins format all, and then the ROM of your choice. Modems are not installed through CWM rom zips. You'll have to flash a modem zip in recovery or odin a modem tar.
Click to expand...
Click to collapse
I was studying Sfhugs FF18 thread and it says I can do the one click root and then install option D and that puts in the FF18, with agats CWM. So is this more simple then flashing FF18 and then doing a flash for either chris or agat kernal with cwm?
Should I use Calkulins format before flashing FF18 from stock?
So when you guys flash new custom roms you have to flash current modem each time? or only if you want to have a more current one? Coming from HTC you only have to flash radio when its required to match a new base leaked. So little confused there too.
Thanks your help has been great!
iceshark said:
I was studying Sfhugs FF18 thread and it says I can do the one click root and then install option D and that puts in the FF18, with agats CWM. So is this more simple then flashing FF18 and then doing a flash for either chris or agat kernal with cwm?
Should I use Calkulins format before flashing FF18 from stock?
So when you guys flash new custom roms you have to flash current modem each time? or only if you want to have a more current one? Coming from HTC you only have to flash radio when its required to match a new base leaked. So little confused there too.
Thanks your help has been great!
Click to expand...
Click to collapse
I know I personally use Mijjahz's "GOODNESS" ROM and it runs smooth. Many mods and add ons with more added daily. I flashed agat's 2.2 kernel because I don't like the 2.3 that version 16.6.1 comes with.
I also flashed FF18 over my EL26 modem. Modems don't change between flashing I believe. Those you update yourself. A lot of folks stay on EL29 or find something that works perfectly in their area.
Sent from Konnor the E4GT.
optimummind said:
Imho, there isn't any ics custom rom as of yet that is 100% stable, glitch-free, and reliable. I would wait it out until more polished versions come out. If there is a pretty good one to try, i'd say the blu kuban.
Click to expand...
Click to collapse
not sure what you expect from a mobile os but I couldn't disagree more.... my experance on mijjahs goodness has been better and more stable than stock in every way, hell even cm9 and aokp are extremely reliable as well if you can live without dialer codes and prl/profile updates.... no software is ever going to be 100%.... I say flash away, you won't be dissapointed
Sent from my SPH-D710 using xda app-developers app
cp320703 said:
not sure what you expect from a mobile os but I couldn't disagree more.... my experance on mijjahs goodness has been better and more stable than stock in every way, hell even cm9 and aokp are extremely reliable as well if you can live without dialer codes and prl/profile updates.... no software is ever going to be 100%.... I say flash away, you won't be dissapointed
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
QFT.
ICS ROMs are very stable at this point.
iceshark said:
Thanks, I think we are on the same page with this!
So I just loaded the FF18 Full Restore and Samsung drivers as indicated in this thread,
http://forum.xda-developers.com/showthread.php?t=1670110
I also tested after unzipping to a folder and the ODEN program comes up waiting for me to hook up phone I dont have yet till tomorrow.
I also watched this video and it seems very easy to do if this is correct process,
http://www.youtube.com/watch?v=_IL21F8Gfbs
Still some clarifying questions,
1. If my new phone comes with ICS already pushed to it. Do I simply still install FF18 to get root for the ICS rom?
2. If phone does not come with ICS will this install ICS and Root?
3. Do I need to use this or Caulkins to wipe data first before I do this process on phone out of the box new?
http://forum.xda-developers.com/showthread.php?t=1670110
Also I am little nervous reading this post from SFHUB<, Is he saying not to do the above process thru the built in Odin recovery in the phone if it comes with stock ICS in it? What does this mean???
The Epic 4g Touch has a bug in it's emmc controller that can cause the /data partition to become inaccessible/unrecoverable sometimes thanks to the wipe process when flashing from ICS recoveries... DO NOT FLASH FROM ICS RECOVERIES!!!!
7/11/12 edit: In the FF18 source Garwynn has confirmed the presence of the offending code that triggers the emmc bug (http://forum.xda-developers.com/show...1&postcount=32) meaning that it will eventually be safe to flash from ICS as long as the offending code is removed by the dev of the kernel/rom...
- Please see this (http://forum.xda-developers.com/show....php?t=1525495) thread by xST4T1K which details how NOT to brick your device... It is slightly out of date but still very relevant... if you want a more technical understanding of what this emmc bug is and why this is happening you can see Sfhub's thread in general related to it (http://forum.xda-developers.com/show....php?t=1644364 ). The OP contains all of the information that our users have been able to figure out about this bug... Be sure to thank these people, as their hard work has made it exponentially safer for all of us to flash ICS roms on our phones...
-Every ICS rom will have a flashing guide in it's dev thread, its HIGHLY suggested you read and reread the guide for the rom you want to flash and follow it EXACTLY, taking the extra time upfront to fully understand what you're about to do will save you alot of trouble going forward.
-Put simply though you will always want to ODIN or Mobile ODIN (mobile Odin is an app made by the dev chainfire, available in the play store, that allows you to preform Odin flashes from your phone without using a PC) the el26 Gingerbread kernel/recovery and flash any ICS roms from that. NEVER FLASH FROM AN ICS RECOVERY, THAT IS HOW BRICKS ARE MADE!!!! Also do NOT use Rom Manager or Touch recovery!!!!
- Currently there are some ICS recoveries that are thought to be safe to flash from thanks to the work done on the emmc bug. If one of these is included in your rom it will be noted by the dev in the rom thread, however the safest way is still just to Odin back to el26 in order to avoid any chance of bricking!
Next, once I do this FF!8 and have root and ICS. If I want to dabble in custom roms. I am guessing they are installed by CWM from file downloaded to root of SD card like normal. I do not find CWM touch for this phone anywhere. I am sure I am missing it. It seems from reading the exploit in ICS kernal is causing the bricks. So I am guessing to use SF hubs or Claukins data wipe before loading custom roms. Are we beating to the same drum here?
Will correct radio or modem be installed automtic with FF18 or custom roms? I see many threads just on modems.
Thanks and thanks for the hot spot mod.
Click to expand...
Click to collapse
you're quoting some of my new user guide here, and i haven't updated it since the OTA came out so it somewhat overstates the danger of bricking (not a bad thing really, made you read, didn't it!?) which was much easir to do before we got kernel source, since then agat63 and chris41g have been killin it in kernel development since they got ICS source... their ICS kernels are safe to flash from and can be found in the dev section, if you're on the stock FF18 rooted with stock kernel i would personally ODIN (mobile or desktop) back to EL26, and from there flash whatever custom ICS rom you like, as far as I'm aware all of the roms come with a safe kernel these days but do be sure to double check and flash one if it does not... at that point going forward should you wish to flash something else you can just do it via cwm as per usual without having to odin back to gingerbread....do note however that you can't use touchwiz kernels with AOSP roms, there asr safe AOSP kernels as well however...
edit: oops, just noticed revamper addressed most of this on the last page, to answer another one of your questions though you can try as many modems as you like and decide which one works best for you, its varies phone to phone and area to area... the modem is not at all required to match the build number of the rom, (example: may people still use the el29 modem with ICS) you can use ANY modem with ANY rom
Ive flashed this phone hundreds of times. Put your rom and any other zips you have on external card. Then to do a full clean wipe go to privacy. then factory data reset then check usb storage. You can skip this step, but this is how to get it factory fresh. Download the el26 cwm kenal. Its posted everywhere. Next open Odin go to pda and select EL26 cwm kernal. Uncheck auto reboot. Have battery cover off! Flash kernal pop battery out when it starts to boot. or says pass. then use the vol up and power combo hold them down until boot screen pops up then let off. Next flash calkulins wipe all or wipe no data. . Never brick never fail. Then flash your rom and tweaks and be happy. Ive done this driving down the road its that easy. Laptop sitting in passenger seat with odin up lol. Plus i drive a 5sp full size truck. Flashing is easy. Follow directions. There is nothing wrong with this phone just read directions if your a noob. I,ll be making multi scenario flashing youtube movies soon. Like mobile tech videos does.
Flashing is easy. Follow directions. There is nothing wrong with this phone just read directions if your a noob.
Click to expand...
Click to collapse
That's all there is to say.
I really wanna use this kernel/custom kernels, but I give up! Constant force closing and crashes for me Now I'm wondering, did I do something wrong during the root process? I rooted my device a couple weeks ago using this link: http://forum.xda-developers.com/show....php?t=1771687 (Root without tripping flash counter), followed by flashing Team Sonic's TouchWiz Rom, and then now, recently as of a little over a week ago I started using Cyanogen Mod 10. Did I miss a step in between which is causing so many problems with installing a custom kernel on my phone? Lean kernel worked earlier around the 8/20-25 nightlies, but now everything's pretty much a bust
It's a T-Mobile GSIII
No you didn't do anything wrong. A lot of the kernels aren't updated as fast as kernel changes in CM. Have you tried the latest nightly with the latest LK?
Sent from my SGH-T999
joshnichols189 said:
No you didn't do anything wrong. A lot of the kernels aren't updated as fast as kernel changes in CM. Have you tried the latest nightly with the latest LK?
Sent from my SGH-T999
Click to expand...
Click to collapse
I've tried all the latest kernels. Every kernel I've tried is compatible with the ROM I've tried it on.
isikh said:
I really wanna use this kernel/custom kernels, but I give up! Constant force closing and crashes for me Now I'm wondering, did I do something wrong during the root process? I rooted my device a couple weeks ago using this link: http://forum.xda-developers.com/show....php?t=1771687 (Root without tripping flash counter), followed by flashing Team Sonic's TouchWiz Rom, and then now, recently as of a little over a week ago I started using Cyanogen Mod 10. Did I miss a step in between which is causing so many problems with installing a custom kernel on my phone? Lean kernel worked earlier around the 8/20-25 nightlies, but now everything's pretty much a bust
It's a T-Mobile GSIII
Click to expand...
Click to collapse
if it was me, which btw am running CM10/LeanKernel, I would use odin to flash back to a rooted stock app, then install NEWEST CWM, and try again, I have had no issues EVER using the combo's that you are using. Also, I NEVER flash a kernel on a new rom until the rom has booted correctly, then reboot and flash whatever compatible kernel.
Good Luck.
TheAxman said:
if it was me, which btw am running CM10/LeanKernel, I would use odin to flash back to a rooted stock app, then install NEWEST CWM, and try again, I have had no issues EVER using the combo's that you are using. Also, I NEVER flash a kernel on a new rom until the rom has booted correctly, then reboot and flash whatever compatible kernel.
Good Luck.
Click to expand...
Click to collapse
Okay I'll do that, but tell me this. How did you come to CM10 exactly? What steps did you do? I want to see if you did something different from me and I may have sent wrong somewhere.
I simply rooted installed freegs3, wiped data and caches and all, then I flashed cm10. Was that the wrong way? Should I go back to stock and restart the process? Because right now for one, custom kernels are giving me strange issues. Also, a ktoonz kernel dev told me my log cat pointed towards corrupt partition or Rom, but I'm using cm10
How do I go back to stock basically? Can you link me to some guides and/or videos? I'm on the T-Mobile galaxy s3. The reason I ask is because I'm mobile and can't search for some reason but I'd like to read up on it before I do it
isikh said:
Okay I'll do that, but tell me this. How did you come to CM10 exactly? What steps did you do? I want to see if you did something different from me and I may have sent wrong somewhere.
I simply rooted installed freegs3, wiped data and caches and all, then I flashed cm10. Was that the wrong way? Should I go back to stock and restart the process? Because right now for one, custom kernels are giving me strange issues. Also, a ktoonz kernel dev told me my log cat pointed towards corrupt partition or Rom, but I'm using cm10
How do I go back to stock basically? Can you link me to some guides and/or videos? I'm on the T-Mobile galaxy s3. The reason I ask is because I'm mobile and can't search for some reason but I'd like to read up on it before I do it
Click to expand...
Click to collapse
I started here, READ EVERY LINE in a separate window, so you can reference back in forth between the windows. And do it STEP BY STEP. Once you are rooted and using the stock rom, back that up, so you can revert back to if you crash, once you have those 2 done, get the newest copy of Clockwork, install it. (by the way, the flash counter will tick you using Odin) so make sure you wipe the tick counter before installing any custom roms. Now get CM10 from the thread, install, do not flash the kernel until you have booted the first time, then reboot to recovery and flash kernel of choice. then your set. Now these are MY DIRECTIONS ONLY! and worked for me. So anyone want to add, feel free, or if I missed something, but do NOT slam me for trying to help, again this worked for me, may not for others, but it has been flawless for me. Hope this helps good luck.
Start here>>>http://forum.xda-developers.com/showthread.php?t=1746682
TheAxman said:
I started here, READ EVERY LINE in a separate window, so you can reference back in forth between the windows. And do it STEP BY STEP. Once you are rooted and using the stock rom, back that up, so you can revert back to if you crash, once you have those 2 done, get the newest copy of Clockwork, install it. (by the way, the flash counter will tick you using Odin) so make sure you wipe the tick counter before installing any custom roms. Now get CM10 from the thread, install, do not flash the kernel until you have booted the first time, then reboot to recovery and flash kernel of choice. then your set. Now these are MY DIRECTIONS ONLY! and worked for me. So anyone want to add, feel free, or if I missed something, but do NOT slam me for trying to help, again this worked for me, may not for others, but it has been flawless for me. Hope this helps good luck.
Start here>>>http://forum.xda-developers.com/showthread.php?t=1746682
Click to expand...
Click to collapse
Thanks for the input! I just wiped everything properly, other than odining back to stock again because that wasn't really necessary I thought since I did everything right, maybe? Well, I don't know lol. I don't have time to go back to stock atm, so I wiped all things including external/internal sd, used superwipe and just flashed a touchwiz rom, by xquizit: http://forum.xda-developers.com/showthread.php?t=1843409 UVALH2 and flashed the kernel for touchwiz by ktoonz and it is running smooth and solid. So, now, I'm going to go back and flash CM from scratch superwiping and all because I have now confirmed ktoonz's kernels work, and for some odd reason it wasn't working with my CM setup, so I'm going try it again from start and see if it works on CM, and go from there. I'll report back either ways in case anyone is having this problem. If I still have the same issue back on CM, I'll live with it or come back to touchwiz. I kinda like it Weird. Haha, but either ways, I'll keep yall updated! I'm wondering if I need to/should flash the UVALH2 radio/baseband since I"m on a UVALH2 ROM though.
Use this kernel it works perfectly on CM10
http://forum.xda-developers.com/showthread.php?t=1845836
EDIT: nvm use this one http://forum.xda-developers.com/showpost.php?p=31025930&postcount=1152
isikh said:
Thanks for the input! I just wiped everything properly, other than odining back to stock again because that wasn't really necessary I thought since I did everything right, maybe? Well, I don't know lol. I don't have time to go back to stock atm, so I wiped all things including external/internal sd, used superwipe and just flashed a touchwiz rom, by xquizit: http://forum.xda-developers.com/showthread.php?t=1843409 UVALH2 and flashed the kernel for touchwiz by ktoonz and it is running smooth and solid. So, now, I'm going to go back and flash CM from scratch superwiping and all because I have now confirmed ktoonz's kernels work, and for some odd reason it wasn't working with my CM setup, so I'm going try it again from start and see if it works on CM, and go from there. I'll report back either ways in case anyone is having this problem. If I still have the same issue back on CM, I'll live with it or come back to touchwiz. I kinda like it Weird. Haha, but either ways, I'll keep yall updated! I'm wondering if I need to/should flash the UVALH2 radio/baseband since I"m on a UVALH2 ROM though.
Click to expand...
Click to collapse
Now I am a tad confused, you have UVALH2 on the phone already, and you want to flash UVALH2? or did you typo? I am no dev, but from what I have been seeing, the radio should not matter at the moment, if I am wrong, someone please set me straight, also, I will be on the web all night and tomorrow, so I will help where ever I can, I will check here for your progress. Good luck my friend.
BTW, I do not like stock roms, so to me CM10 is for sure better. Faster also.
There is no wrong way to root. I bought my phone, didn't even set it up. Downloaded the toolkit, rooted and flashed a custom recovery, then flashed CM10. You didn't miss any steps, and you didn't do anything in the wrong order.
Your radio and ROM do NOT have to match.
joshnichols189 said:
There is no wrong way to root. I bought my phone, didn't even set it up. Downloaded the toolkit, rooted and flashed a custom recovery, then flashed CM10. You didn't miss any steps, and you didn't do anything in the wrong order.
Your radio and ROM do NOT have to match.
Click to expand...
Click to collapse
Yeah, I know all this, but I wanted to ask in case I may have missed something. Even when you're pretty Android savvy when it comes to rooting and whatnot, you do miss things on occasion. In this instant I didn't, but I was hoping I did because a bunch of custom kernels won't work on my phone with CM10! Trinity worked well, so I'm waiting for those. It must be some specific chip related issue because I'm not the only one. Anyways, thanks everyone!
Any resolution to this problem? This has been reported in several threads (link 1, link 2, link 3, need I give more?)
I'm also experiencing the same problem. I installed Paranoid Android (per instructions here) and am now experiencing the same problem. After flashing, the phone continuously reboots. I am using an HTC One V (CDMA) from the US. I also flashed the JB 4.1.2 gapps with the ROM flash process.
When it boots, I receive two errors: "Unfortunately, android.process.acore has stopped working" and "Unfortunately, Contacts has stopped working". When I lock the screen, it reboots. When I try using it, it reboots after 30 seconds. If I just leave it alone, it reboots.
I have also tried several kernels with this same ROM (kernel that comes with the ROM, SuperSick [found here], and stock CM10) and they all just produced the same behavior.
I've looked all around. Some possibilities are: bad kernel, memory (RAM or otherwise) running out, bad install of ROM, or something no one has yet to define. I don't think its a bad kernel because this happens in 3 different ones. I don't think it's a memory issue because I lowered the CPU clockspeed and the phone has plenty of storage memory, and I've also flashed AOKP with the same results which rules out a bad ROM install.
I've wiped cache, system, data, and dalvik and followed all instructions as given to get a completely fresh installation. No avail. I realize that the One V isn't very popular, and there is only a limited amount of support for it but could anyone shed some light as to what the problem could be?? Perhaps some of the original devs who made the ROMs can help out us lowly fools who can't get it to work? I thank anyone in advance for being awesome and at least trying to help.
You may have to flash the old RUU. Look in the General subforum for a thread about phone rebooting after one minute.
sounds like you did the OTA update and have the new radio version, you need to RUU back to stock and dont get the OTA.
I'll try.
Thanks both of you! I will try flashing the RUU and I'll make sure to not install the OTA update. I'll post later with my results.
...
So... I flashed the RUU on the phone again. I again carefully followed instructions on how to flash ROMs (AOKP and Paranoid) and it simply doesn't boot. AOKP's ROM only starts up to a black screen. Paranoid boots to the boot screen animation and just hangs... I've used stock kernels, and tried the SuperSick kernel with both. No progress. Any other ideas?
Try the latest version of cm10 with the latest version super sick kennel. That's what I'm running. AOKP has a few versions that boot to a black screen. If you want AOKP use the latest stable version.
Awesome!
riggerman0421 said:
Try the latest version of cm10 with the latest version super sick kennel. That's what I'm running. AOKP has a few versions that boot to a black screen. If you want AOKP use the latest stable version.
Click to expand...
Click to collapse
Riggerman0421, thanks a ton for the suggestion!! It worked! Despite not being able to use the other roms, I think I can settle with using CM10.
htc one v
filoxo said:
Riggerman0421, thanks a ton for the suggestion!! It worked! Despite not being able to use the other roms, I think I can settle with using CM10.
Click to expand...
Click to collapse
Hey I am having the same problem as you with my htc one v. What did you do exactly to fix this?
lytesson said:
Hey I am having the same problem as you with my htc one v. What did you do exactly to fix this?
Click to expand...
Click to collapse
You have to RUU your device back to the original radio version; it was changed when you accepted the OTA update. That means that you're going to have to flash it to complete stock (no recovery, HTC Sense, booloader relocked, etc.) using the RUU. The forum I found that had all of the different RUUs was deleted unfortunately. You'll have to do careful research for the RUU for your specific device. I only know that Virgin Mobile in the U.S. uses the Sprint towers, so the RUU I used was titled "RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed". Just a quick search on XDA and found this forum that has a download link to the RUU you would need for VM [CDMA] phone (read the comments); you can also look around yourself to make sure you have the right one.
You can find specific instructions on how to RUU your device at this awesome forum. It should only take, literally, 15-20 minutes.
After that is done, you will need to unlock your bootloader again and then you're ready to move on to bigger and better ROMs.
filoxo said:
You have to RUU your device back to the original radio version; it was changed when you accepted the OTA update. That means that you're going to have to flash it to complete stock (no recovery, HTC Sense, booloader relocked, etc.) using the RUU. The forum I found that had all of the different RUUs was deleted unfortunately. You'll have to do careful research for the RUU for your specific device. I only know that Virgin Mobile in the U.S. uses the Sprint towers, so the RUU I used was titled "RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed". Just a quick search on XDA and found this forum that has a download link to the RUU you would need for VM [CDMA] phone (read the comments); you can also look around yourself to make sure you have the right one.
You can find specific instructions on how to RUU your device at this awesome forum. It should only take, literally, 15-20 minutes.
After that is done, you will need to unlock your bootloader again and then you're ready to move on to bigger and better ROMs.
Click to expand...
Click to collapse
So, this happend to my htc and I ruu'ed back to stock, after continunously trying to install roms with constant bootloops. I did the ota update again. So if I want to install a custom rom your saying DONT do the ota after ruu'ing then install one after rooting?
I've got a similar issue (virgin mobile HTC One V)
I currently have TWRP recovery installed, and I attempted to flash the jellybean CM10 as well as the AOKP rom, and I got as far as the unicorn and I actually manged to get the phone to boot to the main screen with all the icons, but it would constantly reboot after being on for maybe a minute
I tried flashing everything back to stock including restoring a backup I had previously taken with TWRP, but no luck
I also tried flashing the stock rom downloaded somewhere here on XDA and I even flashed the stock recovery, but all I got was constant rebooting.
it would get as far as the startup animation and then reboot indefinitely
I'm at a total loss here. I've seen a few links with some resources that look like they might have been helpful (like on this thread) but the links are dead, and I also read somewhere that HTC was putting the kibosh on a site that had some stock roms.
I'd prefer to get jellybean working on my phone, but ultimately, I just want a working phone.
I've followed the process of installing the rom - some instructions said to flash the boot img before flashing the rom, some say after
I've tried both methods
I went into recovery, mounted the usbmsd and copied the rom, and used recovery to install the rom after having cleared the cache, davlik cache and wiping the data (factory reset)
I also installed the gapps package after the rom, but I don't think that's critical to getting it to just boot.
The OTA update reboots were fixed in the latest 4.2 SickleKernels.
Sent from my One V using Tapatalk 2
bheadrick said:
I currently have TWRP recovery installed, and I attempted to flash the jellybean CM10 as well as the AOKP rom, and I got as far as the unicorn and I actually manged to get the phone to boot to the main screen with all the icons, but it would constantly reboot after being on for maybe a minute
I tried flashing everything back to stock including restoring a backup I had previously taken with TWRP, but no luck
I also tried flashing the stock rom downloaded somewhere here on XDA and I even flashed the stock recovery, but all I got was constant rebooting.
it would get as far as the startup animation and then reboot indefinitely
I'm at a total loss here. I've seen a few links with some resources that look like they might have been helpful (like on this thread) but the links are dead, and I also read somewhere that HTC was putting the kibosh on a site that had some stock roms.
I'd prefer to get jellybean working on my phone, but ultimately, I just want a working phone.
I've followed the process of installing the rom - some instructions said to flash the boot img before flashing the rom, some say after
I've tried both methods
I went into recovery, mounted the usbmsd and copied the rom, and used recovery to install the rom after having cleared the cache, davlik cache and wiping the data (factory reset)
I also installed the gapps package after the rom, but I don't think that's critical to getting it to just boot.
Click to expand...
Click to collapse
I think I'm having the same problem. The phone boots, gets as far as the "this build is for development purposes..." and then hangs for a few minutes and restarts, over and over. The flash with fastboot seemed to work fine and reported no errors.
EpicLordPhone said:
So, this happend to my htc and I ruu'ed back to stock, after continunously trying to install roms with constant bootloops. I did the ota update again. So if I want to install a custom rom your saying DONT do the ota after ruu'ing then install one after rooting?
Click to expand...
Click to collapse
Yes. Do NOT install the update if you want to flash another ROM onto your device. Use the RUU to get the device back to factory; this will restore the original radio version. Then go through the steps to unlock the bootloader, root, and flash your ROM as desired. There are other forums which explain the mentioned processes better.
BeyondExistence says that this is fixed with a "4.2 SickleKernel", but as far as I'm aware there are no JB 4.2 ROMs for the HTC One V. Maybe a little more information would be in order?
Bheadrick:
I'm not quite sure what you mean when you say you flashed the stock recovery. The One V doesn't have a recovery when everything is stock.
You will have to RUU your device back (have you read any of the posts in this and other forums??). The process will reinstall the stock rom, relock your bootloader, remove the recovery, etc.
I recommend that you use Paranoid android's rom with the latest SuperSick kernel. Its been my favorite and most stable build I've used.
Sent from my Nexus 7 using xda app-developers app
So I found what BeyondExistence might have been talking about (for those of you who care/are currently having the bootloop problem and would rather go with this route). Its called RhythmicRom. This is a 4.2.2 ROM and it has some cool things for users switching from Sense to a more-pure Android [Link here]. Its based off of CM10.1 for the One V and it includes the BeatsAudio app (which most ROMs don't, as far as I know).
The reason I think that this is worth mentioning is because whoever runs into this bootlooping problem can simply SKIP the RUU process and just move onto this ROM. Hit thanks if this helped!
Newest OTA update.
As some of you may have seen, there's an even newer OTA Update available through the stock ROM. As always, this will cause problems when you try to flash a different kernel, resulting in bootlooping (can anyone who has done the newest update confirm?). Anyway, I've also read that this update also updates your hboot (which, since I haven't and will not apply the update, don't know why it would impede you from flashing any other ROM/kernel but it does) and radio version.
I've looked for additional ROMs who try and make their builds compatible, but so far only RhythmicRom has done anything worthwhile (in my opinion). His latest v 1.3 build will be out soon, and I highly recommend it.
If you flashed both OTA updates, then please be sure to include that when making any post.
filoxo said:
As some of you may have seen, there's an even newer OTA Update available through the stock ROM. As always, this will cause problems when you try to flash a different kernel, resulting in bootlooping (can anyone who has done the newest update confirm?). Anyway, I've also read that this update also updates your hboot (which, since I haven't and will not apply the update, don't know why it would impede you from flashing any other ROM/kernel but it does) and radio version.
I've looked for additional ROMs who try and make their builds compatible, but so far only RhythmicRom has done anything worthwhile (in my opinion). His latest v 1.3 build will be out soon, and I highly recommend it.
If you flashed both OTA updates, then please be sure to include that when making any post.
Click to expand...
Click to collapse
I got my One V at the end of December and did the OTA update at the beginning of April. Last week, I decided to try messing with loading some different ROMs and have encountered all of the problems you've mentioned (e.g., boot-looping, inability to RUU back to stock). I have successfully gotten RhythmicRom to load using this OTA_support.zip (which has been incorporated into the regular release since I flashed it). I have also gotten the most recent version of PACman v22.1 to run (using the same kernel as RhythmicRom) without boot-looping, but the performance hasn't been great (browser crashes frequently and it seems like the launcher has to restart a lot). User demi_fiend has said that the PACman ROM will work using the CodefireX kernel from user BeyondExistence.
I had also tried to revert back to my stock CWM recovery, but it had the boot-loop problem too. However, demi_fiend has also informed me that you can revert to a stock backup by using the boot.img file that is located in the backup folder. I haven't had the chance to verify this, but I wouldn't be surprised if it were true.
It's a bit of a pickle being unable to revert back to previous radio versions, but there is hope that some of the devs will incorporate this issue into their new builds.
tallnproud said:
I got my One V at the end of December and did the OTA update at the beginning of April. Last week, I decided to try messing with loading some different ROMs and have encountered all of the problems you've mentioned (e.g., boot-looping, inability to RUU back to stock). I have successfully gotten RhythmicRom to load using this OTA_support.zip (which has been incorporated into the regular release since I flashed it). I have also gotten the most recent version of PACman v22.1 to run (using the same kernel as RhythmicRom) without boot-looping, but the performance hasn't been great (browser crashes frequently and it seems like the launcher has to restart a lot). User demi_fiend has said that the PACman ROM will work using the CodefireX kernel from user BeyondExistence.
I had also tried to revert back to my stock CWM recovery, but it had the boot-loop problem too. However, demi_fiend has also informed me that you can revert to a stock backup by using the boot.img file that is located in the backup folder. I haven't had the chance to verify this, but I wouldn't be surprised if it were true.
It's a bit of a pickle being unable to revert back to previous radio versions, but there is hope that some of the devs will incorporate this issue into their new builds.
Click to expand...
Click to collapse
Did you flash stock recovery and lock bootloader before running RUU?
Lsesp said:
Did you flash stock recovery and lock bootloader before running RUU?
Click to expand...
Click to collapse
I had flashed my stock recovery (although it was still boot-looping), and I did re-lock the bootloader before running the RUU.
I used the instructions found here.
Hey guys, just got my E4GT yesterday. I installed the rooted GB27 via the one click method. Then installed kernel/recovery through mobile Odin and the tar from here http://forum.xda-developers.com/showthread.php?p=40549220
I am coming the Nexus S 4G (got the epic via a warranty swap) and a Nexus 7, so things here are WAY more complicated. I have been reading like crazy to get a grasp of the flow of how to do things with this device, but I keep getting what seems like either conflicting information or gaps in knowledge.
So what I want to do is switch to an AOSP ROM like PAC or CM, as TW UX is so not jiving with my nexus sensibilities. So since I am currently on all JB partition images I am to understand that I need to switch to a ICS modem. Now this might be a seemingly stupid question, but is there a perfered version of it? I see quite a few ICS modem and don't know to choose and nothing seems to give advice in this regard (at least that I can find). My only guess would be the largest number would be final ICS modem and thus should be the most stable/best available. Thoughts?
Then recovery, I see that the recovery I have installed is for only TW jellybean Roms. So I would have to flash another kernel/recovery prior to flashing my aosp ROM of choice. The GB - EL26 seems to be recommend from many sources, and I want to avoid the whole emmc brick mess. So is that the preferred recovery to flash from? And just so I understand, once I flash a ROM it will then inject its own kernel/recovery images correct?
So every time I want to flash a new ROM, I would start with installing that gingerbread recovery, then reboot recovery into that recovery, full wipe (factory reset,wipe cache/dalvik cache), flash ROM+gapps, and reboot. What about nandroid? Since I am switching recoveries so often are nandroid good across different recoveries? Or not? I am used to being able to have a few backups handy to always be able to get back to a working ROM.
Anyway, thanks in advance for any advice you have to offer. I hated having to ask these questions, but better to ask than end up with a paperwieght.
Your reading has paid off, looks like you got it down. FL24 is the newest ICS modem. EL29 directboot kernel is pretty easy to use, only problem is that it can't flash modems. But you can do that after you get AOSP booted up.
Nandroids are only good on the recovery that they are made on, but all the AOSP ROMs use the same recovery. If you use garwynn's v0.4.1 GB27 kernel it uses that same recovery as well, that's how I go about it. You'll catch on quick don't worry.
Search for Mobile Odin it will save you a lot of time.
bilgerryan said:
Your reading has paid off, looks like you got it down. FL24 is the newest ICS modem. EL29 directboot kernel is pretty easy to use, only problem is that it can't flash modems. But you can do that after you get AOSP booted up.
Nandroids are only good on the recovery that they are made on, but all the AOSP ROMs use the same recovery. If you use garwynn's v0.4.1 GB27 kernel it uses that same recovery as well, that's how I go about it. You'll catch on quick don't worry.
Search for Mobile Odin it will save you a lot of time.
Click to expand...
Click to collapse
I got it working, and am running rootbox. Being back on aosp feels like home, I hate TW!!
Sent from my Nexus 7 using Tapatalk 2
hlxanthus said:
I got it working, and am running rootbox. Being back on aosp feels like home, I hate TW!!
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I like things about both, mostly just the music on TW. But yeah, I usually stick with AOSP. I've got 8 AOSP ROMs in the Android Development section when you get around to it. Welcome to the madhouse btw.
First off, a little background info:
Rom: CM 10.1 (5/22)
Kernel: stock cm
Recovery: twrp 2.5.5.0
Anyway.. I've noticed this issue for probably two months now. Whenever I try to flash ANY kernel on my device, I don't get past the initial boot screen. I do make sure that I'm flashing the correct kernel (that is, one that's compatible with the rom that I'm using) and no matter what, I can't get past the startup screen. Even if I flash the stock kernel, it won't boot.
Conclusion (that will help troubleshoot):
-It can't be recovery, unless an update caused a fluke. I've flashed kernels using twrp before.
-I would suggest that it's the rom, but even if I go back to the roms (RootBox to be more specific) that were over clocked, it won't get past the boot screen with third party kernel. It will boot with just rom however.
-it can't be incorrect flashing methods.. I've done this for years without (many) issues.
I'm beginning to think ill have to Odin stock 4.x.x, but I would like to take another route if at all possible. Any suggestions?
Gfrt94yn said:
First off, a little background info:
Rom: CM 10.1 (5/22)
Kernel: stock cm
Recovery: twrp 2.5.5.0
Anyway.. I've noticed this issue for probably two months now. Whenever I try to flash ANY kernel on my device, I don't get past the initial boot screen. I do make sure that I'm flashing the correct kernel (that is, one that's compatible with the rom that I'm using) and no matter what, I can't get past the startup screen. Even if I flash the stock kernel, it won't boot.
Conclusion (that will help troubleshoot):
-It can't be recovery, unless an update caused a fluke. I've flashed kernels using twrp before.
-I would suggest that it's the rom, but even if I go back to the roms (RootBox to be more specific) that were over clocked, it won't get past the boot screen with third party kernel. It will boot with just rom however.
-it can't be incorrect flashing methods.. I've done this for years without (many) issues.
I'm beginning to think ill have to Odin stock 4.x.x, but I would like to take another route if at all possible. Any suggestions?
Click to expand...
Click to collapse
What kernel are you trying to flash?
ROOTBOXED!
roughneckboren said:
What kernel are you trying to flash?
ROOTBOXED!
Click to expand...
Click to collapse
I've tried many kernels (again, with various ROMs)
Kernels:
King Kanger's
SOAP
some AOSP kernel (don't think there was a specific name)
And something else by ManelScout
I've tried using ROMs:
PA
PACMAN
RootBox
CM 10.1
LiquidSmooth (with its 2.16ghz kernel, still unsuccessful)
Jedi
And DevientXone
.. Mixing and matching, but using the correct kernel with its base; no luck whatsoever. If you haven't noticed, I stay away from stock-based roms, as I like the more streamlined, slicker software that AOSP has to offer. I can't say that I've tried reverting to stock I317 TW based roms. Though, I wouldn't see that AOSP is the issue.. It's almost like a piece is missing since it just happened out-of-the-blue and I can't seem to remedy the problem no matter how many different combinations I try and how many times I download it.
You may have a corrupted device...
I suggest a full wipe...then a fresh install of a rooted stock rom via odin...
then push a fresh recovery via odin...use the UCAMA4 build from mr. Robinson's thread...(development section)
Then attempt the rom of choice..
but first verify the stock build will boot properly...
many devices get corruption within the partitions...especially with the large amount of flashing you have done...
my .02....g
I was afraid of that.. Oh well, it was worth asking. Can I use mobile Odin to flash all of these things or would you suggest using a computer? I've never used Mobile Odin, but I'm familiar with how all of that stuff works (on pc), so I assume it's similar.
PC....
Mobile Odin is a fine program ...but why risk flashing the device, with a possible corruption issue ??
Eliminate the risk ...IMHO ...g