Related
I did quite a few searches about ROM's, Launchers, and other stuff. I have come to conclusion that I'll give CM7 a try. But currently I only know a few stuff, like, the CM7 will replace my stock ROM and I can choose AOSP to replace HTC Sense etc but I'm not sure if my GO Launcher will cross over to CM7. What about my apps? What about the apps placements on my home screens, would they be all reset or gone or what? I see a settings in GO Launcher that says it'll back up my GO Launcher configurations, would this restore my placements of apps on home screens? Also, I'm assuming the GO Launcher as the Desktop Dock apps for Windows and the CM7 as the OS of the computer. Am I assuming things right?
What's not working for HTC EVO 3D on CM7? I saw a video on youtube saying that the 3D video capturing doesn't work on CM7.
Regards
You're absolutely right. 4G and 3Ddo not work. But as development progresses, we're bound to be surprised.
Some widgets are ''Sense'' based so you might not see them cross over since cm removes sense. Apps should work.
I say dive in brother! Make sure to nandroid so that you can easily restore if you find its not your cup of tea.
kaphtc said:
I did quite a few searches about ROM's, Launchers, and other stuff. I have come to conclusion that I'll give CM7 a try. But currently I only know a few stuff, like, the CM7 will replace my stock ROM and I can choose AOSP to replace HTC Sense etc but I'm not sure if my GO Launcher will cross over to CM7. What about my apps? What about the apps placements on my home screens, would they be all reset or gone or what? I see a settings in GO Launcher that says it'll back up my GO Launcher configurations, would this restore my placements of apps on home screens? Also, I'm assuming the GO Launcher as the Desktop Dock apps for Windows and the CM7 as the OS of the computer. Am I assuming things right?
What's not working for HTC EVO 3D on CM7? I saw a video on youtube saying that the 3D video capturing doesn't work on CM7.
Regards
Click to expand...
Click to collapse
Essentially, when moving from any type of Sense based ROM to an type of AOSP based ROM, you will probably lose all your settings, including Wifi passwords, brightness preferences, google accounts sync'd to the device, etc.
On the spectrum of ROMs available, view Sense on one end and AOSP on the other. Some ROMs try to sit in the middle and have features of both, but they always have to pick either Sense or AOSP as the base.
Sometimes you can move between different sense based ROMs and keep your settings/3rd party applications and sometimes you can't. Same goes for AOSP based ROMs.
If you've ever used a google device, G1, Nexus One, or Nexus S, they run pure AOSP by default. CM7 will be fairly similar to that type of experience plus some CM7 "tweaks/goodies".
Making a nandroid, as suggested above, is probably the best way to backup everything currently on the device, in case you want to revert. It will also help provide confidence when testing out new ROMs knowing you'll be able to revert to a previous one if something goes wrong.
To save you some time and help provide information on the next step, once you've selected a ROM and kernel how to make sure they are loaded properly.
If you're using the HTC unlock method on your device, there are basically two ways to load the kernel:
I've answered this type of question a few times in other posts. I've edited my answer from earlier this morning to help answer your question. Feel free to post back if anything isn't clear!
http://forum.xda-developers.com/showpost.php?p=18807723&postcount=3
When booted into the custom recovery through the traditional methods, reboot recovery, bootloader -> recovery, etc., HTC unlock method does not unlock *kernel* write access but does unlock *system* write access.
The main issue around kernel write access is due to the HTC unlock method only allowing kernel write access in two modes:
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery.
Click to expand...
Click to collapse
Let us know if you have any other questions! Hope that helps!
Oh! So I have to choose a ROM (I chose, CM7), Sense or AOSP and ALSO a kernel? My main purpose of flashing a custom ROM is to improve my battery life, get more customization options and cooler effects, no lags.
My status right now is I have S-OFF with Revolutionary tool and only GO Launcher installed. Where do I go now? Install Sense or AOSP (which one do you recommend), I understand E3D comes with HTC Sense 3.0 if that's the same sense we're talking about in above posts. Then install CM7? Which one goes first?
PS: I'm going to follow this tutorial: http://www.phonedut.info/tutorial-install-cyanogenmod-7-cm7-on-htc-evo-3d/
Can you check for me if it's correctly written?
kaphtc said:
Oh! So I have to choose a ROM (I chose, CM7), Sense or AOSP and ALSO a kernel? My main purpose of flashing a custom ROM is to improve my battery life, get more customization options and cooler effects, no lags.
My status right now is I have S-OFF with Revolutionary tool and only GO Launcher installed. Where do I go now? Install Sense or AOSP (which one do you recommend), I understand E3D comes with HTC Sense 3.0 if that's the same sense we're talking about in above posts. Then install CM7? Which one goes first?
PS: I'm going to follow this tutorial: http://www.phonedut.info/tutorial-install-cyanogenmod-7-cm7-on-htc-evo-3d/
Can you check for me if it's correctly written?
Click to expand...
Click to collapse
since you have the revolutionary tool, you're all set. i read thru the guide and it seems good.
good luck! hopefully you enjoy cm7!
joeykrim said:
since you have the revolutionary tool, you're all set. i read thru the guide and it seems good.
good luck! hopefully you enjoy cm7!
Click to expand...
Click to collapse
One more thing, if you don't mind. In the tutorial, it says it's for CDMA. Mine is GSM. Is there a difference between the two? If you say, yes, I'll look for another tutorial.
kaphtc said:
One more thing, if you don't mind. In the tutorial, it says it's for CDMA. Mine is GSM. Is there a difference between the two? If you say, yes, I'll look for another tutorial.
Click to expand...
Click to collapse
Yea, that is a problem. As far as I've seen, there is no CM7 release for the GSM version.
A great location to look for GSM compatible EVO 3D ROMs will be on the EVO 3D GSM developer board.
I'm not bad with electronics. I've done a lot of tinkering with Android, so I'm not brand new to everything. I've flashed multiple ROMS before. I always backup (nandroid) and Titanium Backup, wipe cache and dalvik, and use superwipe in order to clear my phone before flashing a new ROM.
Recently I used Warm's ROM with Tiam's Kernel, with derp's green theme applied, although this problem persisted in other ROMS I have tried. I have overclocking things in the past, but on the current ROM I haven't even fully customized my phone yet by overclocking with The Configurator, etc. So I haven't gone crazy with my phone yet to do some crazy **** that would screw it up.
Basically, my question is: why are all my google framework, etc, force closing, and why doesn't my Wifi/4G work?
What could I do to fix that? I'm thinking of re-flashing the radio's by renaming them PG____ (whatever it was, forgot at the moment), and flashing it at hboot, but I don't think that would effect the google services force closing. So what do you think my problem is?
Thanks again in advance.
Diabetic said:
I'm not bad with electronics. I've done a lot of tinkering with Android, so I'm not brand new to everything. I've flashed multiple ROMS before. I always backup (nandroid) and Titanium Backup, wipe cache and dalvik, and use superwipe in order to clear my phone before flashing a new ROM.
Recently I used Warm's ROM with Tiam's Kernel, with derp's green theme applied, although this problem persisted in other ROMS I have tried. I have overclocking things in the past, but on the current ROM I haven't even fully customized my phone yet by overclocking with The Configurator, etc. So I haven't gone crazy with my phone yet to do some crazy **** that would screw it up.
Basically, my question is: why are all my google framework, etc, force closing, and why doesn't my Wifi/4G work?
What could I do to fix that? I'm thinking of re-flashing the radio's by renaming them PG____ (whatever it was, forgot at the moment), and flashing it at hboot, but I don't think that would effect the google services force closing. So what do you think my problem is?
Thanks again in advance.
Click to expand...
Click to collapse
I'm not 100% sure on the framework FC errors. You mentioned a lot of detail and based on all that detail, I would first guess it is related to the theme.
The next step I would take would be to wipe dalvik. If that doesn't fix, than wipe data. If that doesn't fix, than load a new ROM with wiped data and dalvik. My guess would be something to do with either the ROM or theme modifying framework files.
Framwork files can be correctly modified but if for some reason there is some type of previously cached version or setting relying on prior information, that *could* trigger a FC on the framework.
Regarding the WiFi error, this issue we've seen a lot of. Are you using hboot 1.5 and htc unlock method by chance? If so, I've wrote a fairly decent explanation in previous posts and I'll copy/paste here.
Let us know if you have any other questions!
The WiFi error is caused by a mismatch between the WiFi module and the currently loaded kernel. The WiFi module is stored in /system/lib/modules/bcm4329.ko . The kernel is stored in the boot partition.
When booted into the custom recovery through the traditional methods, reboot recovery, bootloader -> recovery, etc., HTC unlock method does not unlock *kernel* write access but does unlock *system* write access.
The result is the kernel module for WiFi is loaded but the kernel itself is not loaded. This creates a mismatch between a WiFi module loaded from the ROM and the matching kernel not being loaded as HTC does not allow it to be loaded from the traditional recovery boot method.
The main issue around kernel write access is due to the HTC unlock method only allowing kernel write access in two modes:
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery.
Hope that helps!
Edit: If you're curious and want to do some reading on previous WiFi error issues with the EVO 3D on this Q&A board where I replied, here are some similar posts:
http://forum.xda-developers.com/showthread.php?p=17681402
http://forum.xda-developers.com/showthread.php?p=16990247
http://forum.xda-developers.com/showthread.php?p=18624865
http://forum.xda-developers.com/showthread.php?t=1265467
http://forum.xda-developers.com/showthread.php?p=18807723
http://forum.xda-developers.com/showthread.php?t=1326892
Click to expand...
Click to collapse
Mods, I'd have liked to have posted this as a reply to Andybones' thread, but I'm under 10 posts, so please move as needed.
So, I got my Rezound from eBay and figured I'd root it and update it.
Went through the HTC Unlock Bootloader process.
Setup Perm Root
Installed Amon Ra Recovery 3.1.3
Allowed OTA to take place to get to 2.01.605.11.
Went into Amon Ra and had it install superuser and su.
Figured it was an eBay phone and should be wiped clean, so from bootloader did a Factory Reset
After it rebooted a few times, phone came up and "Wifi Error". Everything else working perfectly- 3g, 4g, voice, bluetooth... just no WiFi. Unable to stop or start it in settings GUI.
Hunted online for "WiFi Error" and Rezound and found a few posts asking about clearing cache and dalvik; another few were referencing Kernel and/or module installs.
Cleared cache and dalvik to no avail.
Searched for 2.01.605.11 Kernel and found Andybones post. Installed the Kernel and Wifi was working with everything else again.
So the question-- now that it is fixed and working-- what the heck happened to have broken my WiFi for that duration? Was it when I did the Factory Reset that I somehow screwed up my Wifi Kernel Module? If so, how? Did Factory Reset install some older module or Kernel? Or, was there something broken in my OTA? I saw mention of one other person whose WiFi was broken after OTA to 2.01.605.11-- he also resolved by using the Andybones post to install the Kernel.
Unfortunately, after seeing that the WiFi wasn't working, I didn't think to check what Settings showed for my Kernel, or to try checking mass storage for file dates or versions-- I know those could probably have helped in ascertaining what occurred.
Anybody else experience WiFi broken after OTA?
Thanks in advance!
After I got the OTA I restored my Ineffabilis GB nand and didn't have working wifi even though I flashed the original 1.x stock kernel with it. I didn't get it working until I flashed the dsb kernel, which I had been running when I made my nand. I suspect that is because installing that kernel is more than just flashing the boot.img, there's an install using other folders that happens before the boot.img flash so I guess it is altering something else.
(I didn't try flashing the modules for the new kernel since I wasn't trying to use the new kernel, at that point I was wondering why I couldn't get wifi with the same kernels others were getting it on the same ROM.)
However, even when I did a clean flash of Ineffabilis I had the same problem of not having wifi even with the stock rooted kernel posted with that ROM. I would think at that point I would not have had any traces of the dsb kernel but that was the only thing that got me wifi so I have to assume that had something to do with it.
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
So it would seem that both of us had broken wifi in instances when it would seem we should have had working wifi, albeit for possible different reasons. I too would like to know why. I like fixes but I prefer to know why they work and what is being fixed.
Are you willing to factory reset again? I'm thinking of going back to stock OTA again and starting over with my ROM and seeing about switching kernels. One of my concerns in my situation is am I going to be able to switch from the dsb kernel if that's the only one that got my wifi working now? Others had wifi working with other 1.x kernel using the same ROM so I know the others work, just not on my phone atm.
feralicious said:
After I got the OTA I restored my Ineffabilis GB nand and didn't have working wifi even though I flashed the original 1.x stock kernel with it. I didn't get it working until I flashed the dsb kernel, which I had been running when I made my nand. I suspect that is because installing that kernel is more than just flashing the boot.img, there's an install using other folders that happens before the boot.img flash so I guess it is altering something else.
(I didn't try flashing the modules for the new kernel since I wasn't trying to use the new kernel, at that point I was wondering why I couldn't get wifi with the same kernels others were getting it on the same ROM.)
However, even when I did a clean flash of Ineffabilis I had the same problem of not having wifi even with the stock rooted kernel posted with that ROM. I would think at that point I would not have had any traces of the dsb kernel but that was the only thing that got me wifi so I have to assume that had something to do with it.
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
So it would seem that both of us had broken wifi in instances when it would seem we should have had working wifi, albeit for possible different reasons. I too would like to know why. I like fixes but I prefer to know why they work and what is being fixed.
Are you willing to factory reset again? I'm thinking of going back to stock OTA again and starting over with my ROM and seeing about switching kernels. One of my concerns in my situation is am I going to be able to switch from the dsb kernel if that's the only one that got my wifi working now? Others had wifi working with other 1.x kernel using the same ROM so I know the others work, just not on my phone atm.
Click to expand...
Click to collapse
dsb's kernel installs wifi modules, so since u made the nand using that kernel, that is why u got an error, until u added original stock 1x kernel wifi modules ud get an error.. or flash dsb's kernel like u did.
also when u did a fresh install of ineffibiliss is does install wifi kernel modules, but no a kernel. so you would of still had dsb's kernel even after doing a full fresh instal of inefibiliss. flashing the stock 1x kernel would fix wifi as it has the stock 1x wifi modules.
this is why when people updated to the OTA, and had the new kernel and then did a nand, or a fresh install of ineffibiliss they had wifi error, they needed the new OTA wifi modules.
andybones said:
dsb's kernel installs wifi modules, so since u made the nand using that kernel, that is why u got an error, until u added original stock 1x kernel wifi modules ud get an error.. or flash dsb's kernel like u did.
also when u did a fresh install of ineffibiliss is does install wifi kernel modules, but no a kernel. so you would of still had dsb's kernel even after doing a full fresh instal of inefibiliss. flashing the stock 1x kernel would fix wifi as it has the stock 1x wifi modules.
this is why when people updated to the OTA, and had the new kernel and then did a nand, or a fresh install of ineffibiliss they had wifi error, they needed the new OTA wifi modules.
Click to expand...
Click to collapse
But the only way I could get wifi back was flashing dsb. That's why I'm wondering about what that extra stuff is in the dsb package. After going stock I flashed the original stock rooted kernel that was posted with the ROM before and after flashing Ineffabilis again and still no wifi. But others who did those same steps did have wifi. This makes me concerned about being able to switch from dsb. I want to go back to stock anyway and start fresh since my status bar is crashing and uninstalling the apps I installed right before that started hasn't fixed it. So I'll experiment some more.
Trust me, I get what you're saying and it makes sense, unfortunately that hasn't been the case which is what all my previous posts were about.
Also the OP was completely stock and didn't have wifi and that doesn't fit the equation either.
Sent from my ADR6425LVW using Tapatalk
feralicious said:
But the only way I could get wifi back was flashing dsb. That's why I'm wondering about what that extra stuff is in the dsb package. After going stock I flashed the original stock rooted kernel that was posted with the ROM before and after flashing Ineffabilis again and still no wifi. But others who did those same steps did have wifi. This makes me concerned about being able to switch from dsb. I want to go back to stock anyway and start fresh since my status bar is crashing and uninstalling the apps I installed right before that started hasn't fixed it. So I'll experiment some more.
Trust me, I get what you're saying and it makes sense, unfortunately that hasn't been the case which is what all my previous posts were about.
Also the OP was completely stock and didn't have wifi and that doesn't fit the equation either.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
i had this problem a few times...the last two times i think it was because i had wifi tether on then stupidly i turned on verizon tether app and so wifi and verizon mobile hotspot/wifi tether stopped working and kept giving an error message...i had to flash a version of incredikernel i had laying on my card and everything worked fine..kind of wierd but whatever lol and once i believed it just happened out of nowhere so i just reflashed everything..that time wiping and flashing the rom all over again worked but all other times i needed to flash a kernel. i believe i was running clean rom all those times and once happened on ICS i think..running the latest clean rom 1.6.5 and havent had those issues yet( knock on wood)
feralicious said:
I would think you would have had wifi working on stock OTA since you should have had the 2.x kernel and everything else.
Click to expand...
Click to collapse
That's what I'd have thought, too. I am/was completely stock and my update was OTA. Didn't touch any 3rd party kernels or ROMs. I want to make sure phone works as intended before considering messing with other ROMs/Kernels.
EDIT: Found this older thread which is very similar -- mods can probably close mine or migrate the posts over to the older one since my query resembles what SquireSCA experienced.
feralicious said:
Are you willing to factory reset again?
Click to expand...
Click to collapse
Yeah, tempted to give it a shot after doing an Amon Ra backup to see if it was the factory reset that did me in. I can head back to the Andybones kernel thread to recover again if needed. Probably not going to test it right away though. Still settling in with the phone.
One variable that I didn't consider-- when I did my OTA-- I did not re-lock the bootloader prior. Any possibility of correlation?
I would say that's very possible. I didn't relock the first time so I redid the update using con247's Stock OTA ROM with his update file.
I have a nand of my phone from right after I did my OTA without relocking. When I get around to doing my fresh installs I will restore that and check it to see if I have the same issue. I'll probably do it when I get back home later tonight. I'll post back afterwards to let you know.
So I just restored my nand from when I went back to stock recovery, ROM and kernel (all 1.x) and then accepted OTA. wifi was broken until I flashed the new 2.x stock kernel. That was from when I got the OTA without relocking the phone. I meant to check what the kernel said before I flashed the 2.x stock one but forgot. Argh... now I want to go back to Ineff and do this again to check it.
EDIT: Well, I went back to my stock OTA nand again and the kernel shows as dsb. So I can't replicate what I did earlier since I had flashed the stock kernel before getting the OTA and I guess the nand doesn't back up/restore the kernel.
I don't know what condition wifi was in when I made the nand since I didn't know to check and I just made that as a safety copy and went back to Ineffabilis right away.
I did flash the stock 2.x kernel to get wifi working on stock OTA, then restored my Ineffabilis nand and again, the only way to get my wifi back was to flash the dsb kernel. The stock rooted kernel that came with Ineffabilis didn't do it. Gonna go post on the dsb forum and see what they say. Also, tomorrow I'm going to run the RUU and factory reset and try to get this thing totally clean and see if I can use a different kernel than dsb. Ineff was just updated to 2.x so perhaps flashing the new ROM will break the chains.
feralicious said:
I would say that's very possible. I didn't relock the first time so I redid the update using con247's Stock OTA ROM with his update file.
Click to expand...
Click to collapse
Soooo... I was reading some of the ICS threads and getting really curious about installing. Saw a post by someone mentioning they're on baseband 0.95.00.1118r. Went to check mine, and I'm on 0.95.00.1017_2r . Checked the Verizon site and OTA 2.01.605.11 provides 0.95.00.1118r . Did some more digging to figure out how I got left behind using the official OTA and came upon this post:
Baseband does not update without a re-lock first.
EDIT: found plan of attack via http://forum.xda-developers.com/showthread.php?t=1467329 and will give it a shot this evening.
http://forum.xda-developers.com/showthread.php?t=1467329&highlight=ota+update
Read the last part of the first post.
EmerikL said:
http://forum.xda-developers.com/showthread.php?t=1467329&highlight=ota+update
Read the last part of the first post.
Click to expand...
Click to collapse
Thanks!
Off-topic: Any alternatives to using Filefactory or Dev-host to download the RUU? Has anyone done a sniff during the OTAs to see what URL is used to download the RUU? Does VZW restrict what IPs/MACs can download the updates? Or do they use a proprietary protocol? Or are the updates strictly via their CDMA/LTE, without WiFi?
Mission accomplished-- I now have radio 0.95.00.1118r on my 2.01.605.11.
I did follow the http://forum.xda-developers.com/showthread.php?t=1467329 directions, and I'm posting the commands used for future ref in case needed again:
1) downloaded vigorOTAStockRooted.zip after midnight pacific time (download didn't die) and then copied it to the sdcard.
2) {boot into Amon Ra} adb reboot recovery
a. backup everything
b. install vigorOTAStockRooted.zip
3) {install drops the ph98img.zip file on external sdcard-- but it won't install with unlocked bootloader. need to lock the bootloader} fastboot oem lock
4) {installation finished up, let phone boot up and prep it with devel setting} settings/applications/development/usb debugging
5) {go into bootloader} adb reboot bootloader
6) {get token to submit to htcdev.com; once displayed, plop in the token, and wait for email} fastboot oem get_identifier_token
7) {once email with token received, flash it} fastboot flash unlocktoken Unlock_code.bin
8) {let phone boot up and prep it with devel setting} settings/applications/development/usb debugging
9) {reboot into bootloader to install Amon Ra Recovery} adb reboot bootloader
10) {install Amon Ra} fastboot flash recovery recovery-ra-vigor-3.14-gnm.img
11) {enter recovery - from HTC bootloader, go to recovery} select menu item to go to recovery
12) {restore} from Amon Ra recovery, restore the backup from step 2a and then reboot
Just what the title states, I have just switched over from HTC sense based Operation Jelly Bean 3.15.651.16 to Official BlakCM. My EVo 4gLTE is s-off and rooted with latest TWRP 2.5 for recovery. I followed defection as how to install this particular ROM. What I am not sure on is the kernel. Do I need to install a custom kernel to run this Rom properly and which one if that is the case. I also have the latest base band 1.12.11.1210 installed without TP firmware upgrade. Thanks
You don't need to run custom kernel to run cm10 roms. You can if you want to and komodo is the only one I know of
Sent from my EVO using xda app-developers app
It's not necessary to flash a custom kernel (in this case Komodo), but it does make the ROM even better: battery life almost doubles (on the stock ROM I'm usually at about 18% by 10:00 while with Komodo at that time I'm still at 45% or so), it also helps boost the audio volume and you can use swipe functions on the capacitative keys to turn on the screen (swipe from the left to right), turn off (inverse of the turn on function), increase and decrease volume (swiping halfway) and other functions.
Oh forgot to mention: flash the ViperBoy voltage fix. When I first used to flash it I'd get all sorts of random reboots and such, but since I flashed it it's so much smoother and doesn't reboot randomly
LemonNinja said:
It's not necessary to flash a custom kernel (in this case Komodo), but it does make the ROM even better: battery life almost doubles (on the stock ROM I'm usually at about 18% by 10:00 while with Komodo at that time I'm still at 45% or so), it also helps boost the audio volume and you can use swipe functions on the capacitative keys to turn on the screen (swipe from the left to right), turn off (inverse of the turn on function), increase and decrease volume (swiping halfway) and other functions.
Oh forgot to mention: flash the ViperBoy voltage fix. When I first used to flash it I'd get all sorts of random reboots and such, but since I flashed it it's so much smoother and doesn't reboot randomly
Click to expand...
Click to collapse
To flash the custom kernel do I drop it on sd/root like a firmware upgrade or flash using recovery/zip method, also for the voltage fix.
cpt.kraker said:
To flash the custom kernel do I drop it on sd/root like a firmware upgrade or flash using recovery/zip method, also for the voltage fix.
Click to expand...
Click to collapse
Both have to be flashed in recovery, only if you are s-off... But thicklizard has s-on kernel installers...
Sent from my EVO
Komodo a no go.
Thanks for all the help. Currently i am running carbon ROM (I like it so far) I tried installing komodo kernel but I always get boot loop. I tried to instal rom first let it load. Reboot into recovery and install komodo, i get a boot loop tried reversing the process and same thing. I am s-off lazy panda. Hboot 1.12.1111 radio 1.12.11.1210 I dont know if i am doing somethin wrong some pointers needed. Thanks.
cpt.kraker said:
Thanks for all the help. Currently i am running carbon ROM (I like it so far) I tried installing komodo kernel but I always get boot loop. I tried to instal rom first let it load. Reboot into recovery and install komodo, i get a boot loop tried reversing the process and same thing. I am s-off lazy panda. Hboot 1.12.1111 radio 1.12.11.1210 I dont know if i am doing somethin wrong some pointers needed. Thanks.
Click to expand...
Click to collapse
Might want to hit Thick up and see if he can get you pointed in the right direction.
Sent from my EVO using xda premium
Which version of Komodo? I was reading the carbon thread a while back and remember Jamie saying a certain version for Carbon. Unfortunately I can't remember which version he said...probably have to search the thread again. I'm hopping back and forth between sense and aosps right now so I'm interested in trying this rom again with a different kernel as well.
talroot said:
Which version of Komodo? I was reading the carbon thread a while back and remember Jamie saying a certain version for Carbon. Unfortunately I can't remember which version he said...probably have to search the thread again. I'm hopping back and forth between sense and aosps right now so I'm interested in trying this rom again with a different kernel as well.
Click to expand...
Click to collapse
I was trying to instal the latest version of komodo rls31 capped at 1.7 both sweep gestures and standard versions and no luck. I was reading that tread and others have had same problems with boot loop after installs. Thread also mentioned that others had success installing rls31 capped at 1.998 with no gestures and rls31 capped at 1.5 with no gestures. I have not tried installing these versions yet.
Ah, I want to say rls29 was recommended somewhere back on that thread. I haven't tried any of them yet though.
cpt.kraker said:
I was trying to instal the latest version of komodo rls31 capped at 1.7 both sweep gestures and standard versions and no luck. I was reading that tread and others have had same problems with boot loop after installs. Thread also mentioned that others had success installing rls31 capped at 1.998 with no gestures and rls31 capped at 1.5 with no gestures. I have not tried installing these versions yet.
Click to expand...
Click to collapse
You might need to run the kernel stabilizer in thick's dev host forum... I got the same result as you until I flashed th stabilizer...
Sent from my EVO
Hey guys,
I just got a few questions with this,
Will i lose my apps, theme and such when installing only a ROOT?
Also what do you guys prefer as ROOT method goes, Chainfire and Odin?
I've seen a ROOT BAT program a while ago that realy did everything for you, i just can't remember the name at the moment...
With that i would also like to ask what happens if i update my device? Will i still be able to update it when Samsung pushes a new update ?
Would i need a custom flash recovery? I used to have a phone wich i did it on, But as this is more of my expensiver phone i aint looking to realy risk it. and due all my apps info etc, has well over 150 apps.
Thanks everybody
Bump,
Sorry if nagging but i'm kinda in a rush, if anyone could help me a little?
I basicly know how you most likely root and stuff, just wanna be sure about a few things and what program/apk is best to get into the S3 at 4.3 firmware
Dr.Luigi said:
Hey guys,
I just got a few questions with this,
Will i lose my apps, theme and such when installing only a ROOT?
Click to expand...
Click to collapse
You might lose data.
Few things can be saved, because you have an official (so unrooted) device.
Also what do you guys prefer as ROOT method goes, Chainfire and Odin?
Click to expand...
Click to collapse
Odin is needed, Chainfire root is the most famous method.
I've seen a ROOT BAT program a while ago that realy did everything for you, i just can't remember the name at the moment...
Click to expand...
Click to collapse
Personally I did root with an automatized software, called Unlock Flash.
The better one is Framaroot, but I don't know how it works.
With that i would also like to ask what happens if i update my device? Will i still be able to update it when Samsung pushes a new update ?
Click to expand...
Click to collapse
You'll lost Samsung warranty (no more assistance support, excluded mine and use for software problems [emoji6]), update check and the access to some proprietary apps (You shouldn't be able to download/update from Galaxy Apps).
Normally when you root the device, a CWM custom recovery is included, otherwise you can simply flash via Odin the excellent Philz Recovery, so you'll be able to flash a new Samsung-based rom (ARHD, ArchiPort, Omega, Imperium... aborting the limited stock) or try the greatful AOSP roms (CyanogenMod, Omnirom, PacRom, etc.).
Also custom kernels (BOEFFLA, Googy Max, ArchiKernel and some others, I prevent to cite you outdated ones) and mods (everything!).
Would i need a custom flash recovery? I used to have a phone wich i did it on, But as this is more of my expensiver phone i aint looking to realy risk it. and due all my apps info etc, has well over 150 apps.
Thanks everybody
Click to expand...
Click to collapse
Highly recommended, as I said you need this to install a new rom and any other zip file.
For the rest... I haven't understood you.
Can you explain better last things?
Simone98RC said:
You might lose data.
Few things can be saved, because you have an official (so unrooted) device.
Odin is needed, Chainfire root is the most famous method.
Personally I did root with an automatized software, called Unlock Flash.
The better one is Framaroot, but I don't know how it works.
You'll lost Samsung warranty (no more assistance support, excluded mine and use for software problems [emoji6]), update check and the access to some proprietary apps (You shouldn't be able to download/update from Galaxy Apps).
Normally when you root the device, a CWM custom recovery is included, otherwise you can simply flash via Odin the excellent Philz Recovery, so you'll be able to flash a new Samsung-based rom (ARHD, ArchiPort, Omega, Imperium... aborting the limited stock) or try the greatful AOSP roms (CyanogenMod, Omnirom, PacRom, etc.).
Also custom kernels (BOEFFLA, Googy Max, ArchiKernel and some others, I prevent to cite you outdated ones) and mods (everything!).
Highly recommended, as I said you need this to install a new rom and any other zip file.
For the rest... I haven't understood you.
Can you explain better last things?
Click to expand...
Click to collapse
Well i would only be intrested in ROOT if i can keep all of my files, apps, widgets and such,
I would have done a new ROM if i wouldnt have had so many apps, it would take hours if not days to get everything back as it used to be would be a rather pain in the ***.
Thanks for your help!
Been a while when i unlocked my old device and rommed it undervoltaged it etc etc.
Dr.Luigi said:
Well i would only be intrested in ROOT if i can keep all of my files, apps, widgets and such,
I would have done a new ROM if i wouldnt have had so many apps, it would take hours if not days to get everything back as it used to be would be a rather pain in the ***.
Thanks for your help!
Been a while when i unlocked my old device and rommed it undervoltaged it etc etc.
Click to expand...
Click to collapse
My same problem: too many apps to be restored.
With MyBackupsPRO, the only working without root permissions, you can only keep some settings, contacts, SMS and MMS, then all your apps and games... but without any relative data.
Because as I said you're on an unrooted/official system.
I think you are using an external SD for documents and multimedia files, when you run the first start of your custom rom (highly recommend for the updates, instead the limited stock), be sure that the "Restore data from Google" option is checked.
A discrete help for you, better than nothing.
You have to think that when you did root, backups will be complete, via the greatful Titanium Backup or via recovery with Nandroid backup (my words should be useless if you already have experience with an old device).
Good hacking
As Samsung-based roms I suggest you Android Revolution HD 4.3 or ArchiPort to get the new and officially unsupported 4.4 system.
Pro:
-Compatibility with other Samsung devices;
-Much better camera stabilization than AOSP roms.
Con:
-Touchwiz is heavy for RAM memory and CPU performance;
-Many AOSP functions are completely removed or altered.
As AOSP rom I suggest you CyanogenMod 11, the M builds to have a more stable system, the nightlies for daily updates and less (but always enough) stability.
Pro:
-Latest updates daily/monthly available;
-Many features, AOSP and Cyanogen specific;
-Fully configurable, launcher can be completely replaced, at opposite of Samsung-based roms;
-Greater performance than Samsung-based roms.
Con:
-Some little bug;
-Poor compatibility with Samsung devices and proprietary apps.
As custom kernel, no better one than BOEFFLA: obviously OC and UV support, then lots of functions such "Touch to Wake", a great audio engine, zRAM support, a rich choice of governors and schedulers... it's available for Samsung and many AOSP roms.
Simone98RC said:
My same problem: too many apps to be restored.
With MyBackupsPRO, the only working without root permissions, you can only keep some settings, contacts, SMS and MMS, then all your apps and games... but without any relative data.
Because as I said you're on an unrooted/official system.
I think you are using an external SD for documents and multimedia files, when you run the first start of your custom rom (highly recommend for the updates, instead the limited stock), be sure that the "Restore data from Google" option is checked.
A discrete help for you, better than nothing.
You have to think that when you did root, backups will be complete, via the greatful Titanium Backup or via recovery with Nandroid backup (my words should be useless if you already have experience with an old device).
Good hacking
As Samsung-based roms I suggest you Android Revolution HD 4.3 or ArchiPort to get the new and officially unsupported 4.4 system.
Pro:
-Compatibility with other Samsung devices;
-Much better camera stabilization than AOSP roms.
Con:
-Touchwiz is heavy for RAM memory and CPU performance;
-Many AOSP functions are completely removed or altered.
As AOSP rom I suggest you CyanogenMod 11, the M builds to have a more stable system, the nightlies for daily updates and less (but always enough) stability.
Pro:
-Latest updates daily/monthly available;
-Many features, AOSP and Cyanogen specific;
-Fully configurable, launcher can be completely replaced, at opposite of Samsung-based roms;
-Greater performance than Samsung-based roms.
Con:
-Some little bug;
-Poor compatibility with Samsung devices and proprietary apps.
As custom kernel, no better one than BOEFFLA: obviously OC and UV support, then lots of functions such "Touch to Wake", a great audio engine, zRAM support, a rich choice of governors and schedulers... it's available for Samsung and many AOSP roms.
Click to expand...
Click to collapse
Thanks for the great help,
I aint realy sure yet realy,
But isnt there a way you can simple backup almost everything with the PC?
I thought that was faster, then root it and get those back up on the phone with the PC?
Youve made me thinking realy as my phone was getting slower, Samsung OS isnt that great quiet slow indeed,
I might just drop a few games i dont play realy, so i can get my faster phone back as it used to be.
I used to love tweaking my phone realy, till it broke due rain, was a quiet cheap phone 150e or so.
Do you mind giving your SKYPE or Steam? so i could ask you there, Its been 2 years when i did this, some are kinda floating around in my head but i just cant remember it all anymore.
http://forum.xda-developers.com/gal...msung-galaxy-s3-unified-toolkit-v8-0-t1979290
This is what i meant, Its simple and all in 1, just aint sure if its still up to date?
Via ADT Development Tool, you can do the "adb backup" command, but I think it will include the bootloader, so you'll restore the official and unrooted device state.
But I'm not sure, I never used to backup via PC.
Games are almost innocue, except for notification services who consume a bit of resources.
Can you tell me the heavier apps you're using?
According to your words, having too many apps you're not very satisfied about your performance... or I'm wrong?
Simone98RC said:
Via ADT Development Tool, you can do the "adb backup" command, but I think it will include the bootloader, so you'll restore the official and unrooted device state.
But I'm not sure, I never used to backup via PC.
Games are almost innocue, except for notification services who consume a bit of resources.
Can you tell me the heavier apps you're using?
According to your words, having too many apps you're not very satisfied about your performance... or I'm wrong?
Click to expand...
Click to collapse
Ye it used to be quiet a bit faster, Might be Samsung OS i forgot the name of the OS but anyhow, wizard or something,
Oh well, i will just do it i guess and i will see on the road what apps i need, the rest clearly seems that i dont need em if i never use em.
I'm guessing that the best would be Clockwork recovery and the SUroot? together with cyanogen ROM and buffalo.
As apps goes its basicly my home screen wich has quiet some widgets and such, all diffrent apps, in some folders like 100 apps etc.
Dr.Luigi said:
Ye it used to be quiet a bit faster, Might be Samsung OS i forgot the name of the OS but anyhow, wizard or something,
Oh well, i will just do it i guess and i will see on the road what apps i need, the rest clearly seems that i dont need em if i never use em.
I'm guessing that the best would be Clockwork recovery and the SUroot? together with cyanogen ROM and buffalo.
As apps goes its basicly my home screen wich has quiet some widgets and such, all diffrent apps, in some folders like 100 apps etc.
Click to expand...
Click to collapse
SuperSU is included in CF-Root and so is the most known, but Superuser (from Clockworkmod, the other Superuser is obsolete!) is a great open source alternative.
The best recovery is Philz, always based on CWM, but with extra and TWRP functions.
CyanogenMod yes, is the better choicr and also the easiest choice for root newbies.
Ps Buffalo is a kernel? If it's true, try BOEFFLA, is considered absolutely the best.
Simone98RC said:
SuperSU is included in CF-Root and so is the most known, but Superuser (from Clockworkmod, the other Superuser is obsolete!) is a great open source alternative.
The best recovery is Philz, always based on CWM, but with extra and TWRP functions.
CyanogenMod yes, is the better choicr and also the easiest choice for root newbies.
Ps Buffalo is a kernel? If it's true, try BOEFFLA, is considered absolutely the best.
Click to expand...
Click to collapse
Well i meant boeffla of course, Well i cant get it to work, What are the keys to get into TWRP recovery?
As in download mode it tells me its custom, but i cant get into it..
tryed quiet a few combis already
Dr.Luigi said:
Well i meant boeffla of course, Well i cant get it to work, What are the keys to get into TWRP recovery?
As in download mode it tells me its custom, but i cant get into it..
tryed quiet a few combis already
Click to expand...
Click to collapse
Edit:
Tryed again, i cant reboot if i did it would get the old recovery back, so in a push method it worked,
Now SuperSU, i might get a ROM but aint sure yet, Do kernels work on the stock rom aswell?
Dr.Luigi said:
Edit:
Tryed again, i cant reboot if i did it would get the old recovery back, so in a push method it worked,
Now SuperSU, i might get a ROM but aint sure yet, Do kernels work on the stock rom aswell?
Click to expand...
Click to collapse
Yes, BOEFFLA works also on stock rom (make sure to flash the correct zip file)... but I haven't understood your problem: can't reboot, old recovery back... what?
Simone98RC said:
Yes, BOEFFLA works also on stock rom (make sure to flash the correct zip file)... but I haven't understood your problem: can't reboot, old recovery back... what?
Click to expand...
Click to collapse
Ye nevermind that,
The problem is when i flashed my recovery, that when i reboot it switched automaticly back to the orginal stock recovery,
Only way to repair this was to not reboot, but goto the Philz recovery directly and reinstall the recovery program,
Also rooted it now,
So i can simple install Boefflo on my S3 international, With stock rom and ROOT, philz recovery?
If so that would be sweet ^^
As it should be more sufficient as far as battery goes, and a small overclock to like 1.6Ghz is reasonable ive heard,
1.8 is to high if i can believe those on some forums.
Since the last stable release you can overclock up to 1704 Mhz... and no more 1.5 Ghz step, I don't know the reason.
As I said, BOEFFLA works almost on every rom, but you habe to flash a different zip file for Samsung and AOSP roms.
Why can't you get a custom recovery? Are you sure to flash them reproducing properly the reported Odin guide (what to check in app, where to write file, etc.)?
It's a strange problem, rom "might" be cause by replacing the new recovery with the stock one, I think, but I'm not absolutely sure.
Simone98RC said:
Since the last stable release you can overclock up to 1704 Mhz... and no more 1.5 Ghz step, I don't know the reason.
As I said, BOEFFLA works almost on every rom, but you habe to flash a different zip file for Samsung and AOSP roms.
Why can't you get a custom recovery? Are you sure to flash them reproducing properly the reported Odin guide (what to check in app, where to write file, etc.)?
It's a strange problem, rom "might" be cause by replacing the new recovery with the stock one, I think, but I'm not absolutely sure.
Click to expand...
Click to collapse
Well like i said i've fixed that,
The standard way to flash doesnt work, As once i get booted in Samsung ROM, It fixes it, So you have to goto your Recovery immeaditly when youve flashed it, and flash it again in the custom recovery, and then it does work.
Well i will see, aint sure yet if i will do it the kernel and romming.
Thanks for the help
Dr.Luigi said:
Well like i said i've fixed that,
The standard way to flash doesnt work, As once i get booted in Samsung ROM, It fixes it, So you have to goto your Recovery immeaditly when youve flashed it, and flash it again in the custom recovery, and then it does work.
Well i will see, aint sure yet if i will do it the kernel and romming.
Thanks for the help
Click to expand...
Click to collapse
Here is also a great kernel. Check this out http://forum.xda-developers.com/gal...04-googy-max2-kernel-2-3-1-cm-camera-t2517875