Hi--I am a generally technically adept Evo owner who would like to root to a Froyo custom ROM, but I've never had to root anything before. I've read threads meant to act as guides (like those linked in the sticky thread), but there seems like so much I don't understand. I know these are simple questions, but my searching didn't really help. I'd be really grateful if anyone had any helpful answers.
Question 1: Does anyone have any recommendations for the best custom ROM that will have these features?:
Froyo (of course)
SenseUI (I prefer it, but have nothing against stock Android)
Ability to restore my apps (via Titanium Backup, I assume)
Unlocked wifi tethering (via app or Froyo's in-built capability)
Unlocked FPS (I have a Novatec panel)
Same or better camera/video capabilities as stock SenseUI (i.e., nothing broken at least)
My current software: Stock Evo, no OTA updates applied, with Superuser Unrevoked permissions.
(That is, I have not applied any OTA updates since I bought it, June 11th. I'm running 2.1-update1, version 1.32.651.6. I did the Unrevoked 1-click "root" that in fact only gave me Superuser permissions (the Unrevoked that was first released, not the Unrevoked2 or 3 updates). I.e., I can use the wifi tether and Titanium Backup, and I've backed up my apps/settings with it.)
Question 2: Can anyone tell me in a simplest method to safely root and install the custom ROM, considering I have no OTA updates and unrevoked superuser permissions?
Specifically, I've read guides that list 3 steps (gaining root permissions, unlocking NAND, gaining "full" root), but I still have a lot of questions:
What does it mean to "flash a recovery"?
[*]When do I have to manually install radio updates, and how do I know which ones I need?
[*]If I decide I'd rather go back to stock, ever, can I do that?
[*]What is the likelihood of a brick, and can I repair a brick?
[*]Can Titanium Backup really restore all my apps after I do a full wipe and root? (just to calm my anxiety, please...)
The best guide I've seen is the "IDIOT-PROOF" root guide, at thread 701004 (sorry, new user restriction, can't post links), but I don't know if it's still current. That also seems more complex than SimpleRoot (also don't know if it's current).
I think I'm looking for the simplest root method with the least possibility of screwing everything up. (It pains me to say it, but a brainless iPhone-like "slide-to-jailbreak" method would be great.)
Sorry for the newbie questions. If anyone has any advice/answers, I'd be glad to hear them!
Well best bet for you is probably going to be either the one click simpleroot, you can go to simpleroot.com its there for download. Of course it depends on exactly what software version you are on. As far as your rom choice there is no rom that offers all of those things, probably closest will be stock rooted 2.2, then you can either live with the 30fps restriction or flash a custome kernel and live with 3mp camera .... you're choice. the recovery is a program that the phone boots into that has nothing to do with the rom at all, with this you can select several operation to make on the rom. You need recovery because you cant modify the rom when you are booted in the rom. Anyway this is all a very basic explanation. My recommendation would be to follow toasts part 1 then part 2 to root and unlock nand. (unlocking nand allows writing and writing to the system area of the rom while booted into the rom) then you will be all set to flash any rom you like. feel free to pm if you need more info As far as knowing what you need I would recommend starting with netarchy's stock rooted 2.2 odexed version. In his post he will tell you flash rom then radio then wimax, all of these files are included there in the post. Then as you learn you can switch between roms to explore what each one can do for you and decide which you like best. Yes Titanium backuop will work with this.
For me and I have flashed every rom lol. Daily driver would have to be the fastest and stabliest rom which is in my opinion Caulkins v1.02 froyo. Use simple root for 1.32. Then use the flash recovery and pick ra recovery.
ifly4vamerica said:
As far as your rom choice there is no rom that offers all of those things, probably closest will be stock rooted 2.2, then you can either live with the 30fps restriction or flash a custome kernel and live with 3mp camera .... you're choice.
Click to expand...
Click to collapse
Really? How about a ROM with, say, just 2.2 + SenseUI, with all the standard features, and wifi tether enabled?
Thanks for the advice, by the way, both of you.
ScaryBugThing said:
Hi--I am a generally technically adept Evo owner who would like to root to a Froyo custom ROM, but I've never had to root anything before. I've read threads meant to act as guides (like those linked in the sticky thread), but there seems like so much I don't understand. I know these are simple questions, but my searching didn't really help. I'd be really grateful if anyone had any helpful answers.
Question 1: Does anyone have any recommendations for the best custom ROM that will have these features?:
Froyo (of course)
SenseUI (I prefer it, but have nothing against stock Android)
Ability to restore my apps (via Titanium Backup, I assume)
Unlocked wifi tethering (via app or Froyo's in-built capability)
Unlocked FPS (I have a Novatec panel)
Same or better camera/video capabilities as stock SenseUI (i.e., nothing broken at least)
My current software: Stock Evo, no OTA updates applied, with Superuser Unrevoked permissions.
(That is, I have not applied any OTA updates since I bought it, June 11th. I'm running 2.1-update1, version 1.32.651.6. I did the Unrevoked 1-click "root" that in fact only gave me Superuser permissions (the Unrevoked that was first released, not the Unrevoked2 or 3 updates). I.e., I can use the wifi tether and Titanium Backup, and I've backed up my apps/settings with it.)
Question 2: Can anyone tell me in a simplest method to safely root and install the custom ROM, considering I have no OTA updates and unrevoked superuser permissions?
Specifically, I've read guides that list 3 steps (gaining root permissions, unlocking NAND, gaining "full" root), but I still have a lot of questions:
What does it mean to "flash a recovery"?
[*]When do I have to manually install radio updates, and how do I know which ones I need?
[*]If I decide I'd rather go back to stock, ever, can I do that?
[*]What is the likelihood of a brick, and can I repair a brick?
[*]Can Titanium Backup really restore all my apps after I do a full wipe and root? (just to calm my anxiety, please...)
The best guide I've seen is the "IDIOT-PROOF" root guide, at thread 701004 (sorry, new user restriction, can't post links), but I don't know if it's still current. That also seems more complex than SimpleRoot (also don't know if it's current).
I think I'm looking for the simplest root method with the least possibility of screwing everything up. (It pains me to say it, but a brainless iPhone-like "slide-to-jailbreak" method would be great.)
Sorry for the newbie questions. If anyone has any advice/answers, I'd be glad to hear them!
Click to expand...
Click to collapse
I'd like to suggest something before you actually move forward. I usually back up with MyBackup and with Titanium backup. I am completely rooted and nand unlocked but something i've seen Titanium for some reason after i grant it superuser tell me my phone isn't rooted on different roms, also i have seen Mybackup crash the sense and try to reboot it over and over in a loop. Luckily I did a Nandroid restore to a more stable setup. Some of the other forum members here are more likely than not less new to the process than myself, but I thought i had covered everything and when i did simple root, I was on 1.47, with the factory reset and everything lost my data... luckily it wasn't a lot or important. I just thought i'd let you know that it is not a bad thing to have a zipped backup of all of your apks+data, and your contacts with both programs before you go ahead. Hope that possibly can steer you out of trouble if one of them fails to perform as it should. Best of luck.
Exohart said:
I'd like to suggest something before you actually move forward. I usually back up with MyBackup and with Titanium backup. ... Hope that possibly can steer you out of trouble if one of them fails to perform as it should. Best of luck.
Click to expand...
Click to collapse
Cool, thanks for the tip.
You can get a rooted stock 2.2 ROM, odexed or deodexed. Then you can install a wifi tether app. Personally, I use Fresh 3.1.0.1, I don't notice any differences in general to stock, but you should probably just try different ROMs out and see which one you like. It's easy to switch around.
See this for ROMs.
As for rooting, You can use Simple Root, but I highly suggest doing it yourself using toast's or TheBiles' guides. You learn a lot and it's the same thing as using Simple Root, but you can deal with problems better (although I didn't have any issues when I did mine).
See here for guides.
There is a lot of info on how to get around any issues you have, so be sure to search if you do run into trouble.
And if you need the files for rooting, check here.
Awesome response, SilverZero, thanks! I'm starting to feel comfortable with the rooting procedure.
I think the difficulty I have in choosing a ROM is that many ROM threads don't list conclusively whether a feature works or not. So, for instance, I presume that the Fresh ROM has a fully working camera (8MP/720P with all settings), but I've read other ROM threads that talk about downgraded camera bugs, so I am not sure if I should assume things work fine. Conversely, I think wifi tethering doesn't work, since it *seems* to suggest it isn't working, but doesn't flat-out say so...
I don't suppose some source exists somewhere that lists/compares all of these ROMs' features in a table format, listing whether they work or not, or are downgraded? Having something like that in a central, often-updated location would be incredibly useful...
I used toast's method for rooting, and havent had any problems whatsoever. All I had to do after that, was install the new RA recovery image ( was more current ).
Is this the simplest way? probably not. But, i perfer doing the method with the most manual work. Automated processes tend to scare me, 'oh, our mod does steps 1 through 19 all at once'... well, thats fine, but what happens when it fails half way through? Toast's method, while a bit involved, is pretty simple, and if something happens, you can go "hey, when i do this command <whatever>, it does this, helps?!".
as for your 'questions 2s'
1: Are you sure you dont mean, flash from recovery? recovery is where you do all of your flashing, do your nandroid backups, and wiping. theres 3 ways to get there ( once your rooted/nand unlocked ).. volume -, and power while the phone is off, hold it til you get the menu. use quickboot ( a feature of damagecontrol mod ), or use adb using a command prompt on windows ( adb reboot recovery ).
2: Most people install radio updates when they go to change to new roms. The reason being, 2.2 'code' is based around having a certain radio version, and for things like 4g, and good 3g signal, you need to match.
personally, every time i go to install a new rom, i verify what the most recent radio version is out there, and install it ( same with wimax )
3: Once you are fully rooted, there are walktrhoughs for 'starting over / going back to stock'.. but I would just use one of the rooted stock images, as it gives you the ability to change your mind. for instance, right now 2.2 isnt rootable, so if you changed your mind after switching back to it, your kind of screwed. I'm not sure if the engineering image you install for root would go away if you reverted to stock/root though, as have never tried.
4: as long as you have the phone rooted, any 'bricking' that i have caused ( boot loops, power turning off on boot, etc ), were easily recoverable by just booting into recovery and reflashing. the only way I could see bricking in a totally bad way, would be if you somehow messed up the rooting process and corrupted the bootloader in such a way it couldnt recover. Otherwise, i have yet to see a rom that will flash / change your bootloader or recovery image, so it shouldnt be an issue.
5: It can, but i've seen issues where backing up stuff from a 2.1 rom, and installing a 2.2, causes weird issues. its safer to just redownload them if you are using a 2.2 rom. Another benefit of 2.2, is now google backs up your app selection you had installed, so when you wipe / flash a new rom, it auto-reinstalls all your apps you had from before ( it doesnt backup your settings though, just the applications themselves ).
ScaryBugThing said:
Awesome response, SilverZero, thanks! I'm starting to feel comfortable with the rooting procedure.
I think the difficulty I have in choosing a ROM is that many ROM threads don't list conclusively whether a feature works or not. So, for instance, I presume that the Fresh ROM has a fully working camera (8MP/720P with all settings), but I've read other ROM threads that talk about downgraded camera bugs, so I am not sure if I should assume things work fine. Conversely, I think wifi tethering doesn't work, since it *seems* to suggest it isn't working, but doesn't flat-out say so...
I don't suppose some source exists somewhere that lists/compares all of these ROMs' features in a table format, listing whether they work or not, or are downgraded? Having something like that in a central, often-updated location would be incredibly useful...
Click to expand...
Click to collapse
Here's a project that one user is putting together comparing different ROMs.
https://spreadsheets.google.com/ccc?key=0Aguc0npJCrWxdEFyU2NRNG1jNnRkY2trdXBsYlJLdWc&hl=en#gid=0
imiddlet said:
I used toast's method for rooting, ...
Click to expand...
Click to collapse
Wow, thank you for taking the time--you really answered all of my questions.
SilverZero said:
Here's a project that one user is putting together comparing different ROMs.
Click to expand...
Click to collapse
Greeeeat. Exactly what I was looking for.
You guys are awesome--I think I know what I need to know now, and in the next few days I will probably try rooting and installing Fresh Evo or BakedSnack. I'll update once I know how it went!
Urg...Well, I did the manual root method. Everything went fine through the initial root (using the classic method by toastcfh), and through the manual recovery mode where I made a nandroid backup.
Then, in recovery mode, I attempted to flash the latest Fresh Evo 3.1.0.1. It gave me no error messages, and I rebooted.
Now, it is stuck on an infinite reboot at the Fresh Evo ("FRESH!!!") bootup animation. It just keeps running that animation, never loading up. I've let that animation run about 15 times before I had to pull the battery to make it stop. Any time I try to boot the phone, I am stuck at that infinite reboot/load sequence.
The only thing I could do was hold Vol- while powering up to get into the bootloader and redo my stock root. I redid the Fresh Evo install, and it still just keeps rebooting for 10 minutes, before I pull the battery. I'll try Baked Snack next, but I don't want to press my luck with too many flashes... Any ideas anyone?
ScaryBugThing said:
Urg...Well, I did the manual root method. Everything went fine through the initial root (using the classic method by toastcfh), and through the manual recovery mode where I made a nandroid backup.
Then, in recovery mode, I attempted to flash the latest Fresh Evo 3.1.0.1. It gave me no error messages, and I rebooted.
Now, it is stuck on an infinite reboot at the Fresh Evo ("FRESH!!!") bootup animation. It just keeps running that animation, never loading up. I've let that animation run about 15 times before I had to pull the battery to make it stop. Any time I try to boot the phone, I am stuck at that infinite reboot/load sequence.
Anyone have any advice? Am I screwed?
The only thing I think I can do is hold Vol- while powering up to get into the bootloader and have it check PC36IMG, after which it gives me the same normal root Step 1 option to "Start Update" (Vol+ for yes, Vol- for no). Will this just restore to "stock" root? I'd like to get FreshEvo working somehow...
Click to expand...
Click to collapse
Try doing a full wipe, Data, Dalvik Cache, everything except the SD card. Then try reflashing the ROM. That was how I had to fix mine when it did the same thing.
Also don't forget to update your Radio, WiMax and Recovery if you havent already.
http://forum.xda-developers.com/showthread.php?t=715485
http://forum.xda-developers.com/showpost.php?p=6877247&postcount=98
As far as the best ROM is concerned I've been using SteelH's deodexed stock ROM with the netarchy-toastmod kernel and it's been running great. FPS are unlocked, its quick as hell and my battery life is excellent.
http://forum.xda-developers.com/showthread.php?t=743781
http://forum.xda-developers.com/showthread.php?t=719763
xHausx said:
Try doing a full wipe, Data, Dalvik Cache, everything except the SD card. Then try reflashing the ROM. That was how I had to fix mine when it did the same thing.
Click to expand...
Click to collapse
Thanks for the suggestions. Unfortunately, I did a double-wipe (cache, dalvik cache, and data/factory reset x2) before each of the 3 times I tried to install Fresh Evo. Same infinite reboot loop always.
Then I installed Baked Snack just now. I was able to actually boot (54 fps looks great!) but ROM Manager was giving me an error message about flashing the Recovery replacement, Wifi Tether force closed every time I opened it, and every time I plugged in the USB cable, it would disconnect about 2 seconds later, rendering the phone essentially useless since it wouldn't recharge or accept files in that two seconds.
So now I'm flashing back the stock root image, PC36IMG.zip.
I guess this isn't going very well. If anyone has any advice about these problems I'm having, I'm still in the depths of rooting hell. I appreciate the SteelH suggestions. Maybe I'll try that next. But it's definitely worrying me that every ROM I try has some major problems.
ScaryBugThing said:
Thanks for the suggestions. Unfortunately, I did a double-wipe (cache, dalvik cache, and data/factory reset x2) before each of the 3 times I tried to install Fresh Evo. Same infinite reboot loop always.
Then I installed Baked Snack just now. I was able to actually boot (54 fps looks great!) but ROM Manager was giving me an error message about flashing the Recovery replacement, Wifi Tether forced close every time I opened it, and every time I plugged in the USB cable, it would disconnect about 2 seconds later, rendering the phone essentially useless since it wouldn't recharge or accept files in that two seconds.
So now I'm flashing back the stock root image, PC36IMG.zip.
I guess this isn't going very well. If anyone has any advice about these problems I'm having, I'm still in the depths of rooting hell. I appreciate the SteelH suggestions. Maybe I'll try that next. But it's definitely worrying me that every ROM I try has some major problems.
Click to expand...
Click to collapse
if you're using clockwork try switching to Amon-RA. That may be whats doing it
xHausx said:
if you're using clockwork try switching to Amon-RA. That may be whats doing it
Click to expand...
Click to collapse
Thanks for the suggestion and the very fast responses. I'll give Amon-RA a shot, if I can install it. (note: I didn't use Rom Manager to install any actual ROMs here--it was just what I was about to begin using.)
Sorry if I have so many questions, but: What is the best method to flash Amon-RA recovery? Rom Manager seemed easy because you could simply download the program, run it, and choose an option in the settings menu to replace the stock Recovery.
For Amon-RA, there are two options--fastboot, and adb. I only have a vague idea of what these are and how to make them work.
As an UPDATE: I installed SteelH's ROM, and it booted, but it definitely didn't have 54 fps on mine (clearly 30 fps, Novatec panel FWIW), and I had the same problem with the USB cable disconnecting 2 seconds after plugging it in. I of course wiped everything before installing.
So I'm trying to figure out if I did something wrong in my original root--though it seemed to work fine. Could a locked NAND be causing these problems?
ScaryBugThing said:
Thanks for the suggestion and the very fast responses. I'll give Amon-RA a shot, if I can install it. (note: I didn't use Rom Manager to install any actual ROMs here--it was just what I was about to begin using.)
Sorry if I have so many questions, but: What is the best method to flash Amon-RA recovery? Rom Manager seemed easy because you could simply download the program, run it, and choose an option in the settings menu to replace the stock Recovery.
For Amon-RA, there are two options--fastboot, and adb. I only have a vague idea of what these are and how to make them work.
As an UPDATE: I installed SteelH's ROM, and it booted, but it definitely didn't have 54 fps on mine (clearly 30 fps, Novatec panel FWIW), and I had the same problem with the USB cable disconnecting 2 seconds after plugging it in. I of course wiped everything before installing.
So I'm trying to figure out if I did something wrong in my original root--though it seemed to work fine. Could a locked NAND be causing these problems?
Click to expand...
Click to collapse
I used the fastboot method earlier and it was a piece of cake. Just move the recovery to the Tools folder for the SDK, put your phone in fastboot mode and copy paste the two lines in a cmd prompt to install it. I was bored reading through the recovery thread I linked to earlier and apparently clockwork is not wiping properly, others were also having problems with Fresh because of it.
For the FPS fix that is done in the kernel so you would need to flash a custom one.
xHausx said:
I used the fastboot method earlier and it was a piece of cake. Just move the recovery to the Tools folder for the SDK, put your phone in fastboot mode and copy paste the two lines in a cmd prompt to install it. I was bored reading through the recovery thread I linked to earlier and apparently clockwork is not wiping properly, others were also having problems with Fresh because of it.
For the FPS fix that is done in the kernel so you would need to flash a custom one.
Click to expand...
Click to collapse
I tried to do as instructed. I rebooted into Fastboot mode on my phone, verified the device was seen by fastboot on my PC, then entered:
C:\android-sdk-windows\tools>fastboot flash recovery recovery-RA-evo-v1.7.0.1.img
sending 'recovery' (5032 KB)... OKAY [ 1.406s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.094s
I tried to redownload the file, but the same result occurred.
EDIT: I was able to flash the Amon-RA recovery, going back to toast's instructions. I don't know why it wasn't flashed before...
I'm also not sure that my wiping the data is the problem--I wiped factory settings/cache/dalvik cache each time using only the stock recovery. I think my mentioning Rom Manager might have suggested I used that program to wipe my data, but I haven't done so...
Anyway, I appreciate the help. This is tough for me--I can't seem to get anything to work.
EDIT2: Problems solved! Indeed, I had not properly unlocked NAND. I redid the toast NAND unlock steps, and Fresh Evo installed on the first try!
My only remaining question: how do I flash a kernel? I simply flash a ROM and then the kernel? I think Fresh Evo is great, but fps2d is still showing me locked at 30 fps.
EDIT3: I think I found the answer. Flash it like any other ROM from zip. (Doing it with Netarchy's Kernel 4.0.3: http://forum.xda-developers.com/showthread.php?t=719763 )
(Probably looks silly reading me answer my own questions, but I thought it was better to look stupid if it might help a future beginner like me.)
Just my oppinion simpleroot never really worked for me and ive read bad things about unrevoked so just follow toasts method to rooting it is very simple and straight forward, as for rom i prefer baked snack themed version it is by far the most sexy rom i have seen it uses manups theme and u can enhance it even more, its very stable and has no fps cap on it, as well as both cameras work and video recording works, im not sure if blue tooth has been fixed yet and am not sure if 4g works because i dont have it where i live try it out and tell me what u think.
So...Everything works! A couple of final notes in case it ever helps anyone in the future:
Note 1: The call part of the phone was not working well at all. I could send and receive calls, and hear the other party, but the audio was very noisy and the other party didn't hear my voice when I talk.
I tried to update PRL and Profile, but I got an error code 1012: "The profile update could not be completed. Please try again later. If the problem persists, you may need to contact customer service. Error code:1012"
I thought the problem might be me overwriting some system files with Titanium Backup (though I was careful). But when I tried wiping factory settings/cache/dalvik cache, and rebooted, still the same problems. Ultimately, it turned out simply that Sprint's servers were down, so I couldn't update my profile/PRL. I finally was able to update the Profile and PRL (now 60669) when they came back up, and everything seems to be working.
Note 2: I realized too late that I lost all of my visual voicemails. I don't think there's a way to restore them, and I don't know if there's any way to back them up. But something to think about if you've racked up a fair amount of downloaded visual voicemails.
Thanks everyone for your help.
I'm sorry if this has been covered before, but I couldn't find anything exactly like the issue. My friend has an EVO and asked me to help him with getting custom roms onto it, so we set out to root it last night. We used unrEVOked as it seems the most idiot-proof, and the last thing I wanted to do was brick his phone. The whole root process ran without a hitch, and afterwards we were booting into recovery, and when booting back into the main OS, the superuser app was on the phone. But, when I downloaded wireless tether, the computer would connect to the app, but no bandwidth was allowed.
The only issue I could think of was that we rooted with the sd card removed, as he was afraid of it being wiped for some reason. When the phone was booted into recovery, it seems like something error-ed out due to the sd card not being there. Any help would be GREATLY appreciated.
Are you using "Wireless Tether for Root Users"
http://www.appbrain.com/app/wireless-tether-for-root-users/android.tether
This app has many, many isuues. If you just downloaded it from the Market or AppBrain you likely got the generic, older build.
Go here...
http://code.google.com/p/android-wifi-tether/downloads/list?q=label:Experimental
for the various different versions and find one that works for you.
Thank you, I had no idea. When I get ahold of his phone next, I'll try one of those builds.
jrp07f said:
Thank you, I had no idea. When I get ahold of his phone next, I'll try one of those builds.
Click to expand...
Click to collapse
I could never get more than about .3kbs and .1 up and I tried em all. now finally with pre 15 it's working. I get about the same between my laptop tethered and what the phone gets by itself.
jrp07f said:
I'm sorry if this has been covered before, but I couldn't find anything exactly like the issue. My friend has an EVO and asked me to help him with getting custom roms onto it, so we set out to root it last night. We used unrEVOked as it seems the most idiot-proof, and the last thing I wanted to do was brick his phone. The whole root process ran without a hitch, and afterwards we were booting into recovery, and when booting back into the main OS, the superuser app was on the phone. But, when I downloaded wireless tether, the computer would connect to the app, but no bandwidth was allowed.
The only issue I could think of was that we rooted with the sd card removed, as he was afraid of it being wiped for some reason. When the phone was booted into recovery, it seems like something error-ed out due to the sd card not being there. Any help would be GREATLY appreciated.
Click to expand...
Click to collapse
I tried using Wireless Tether for Root as well and I had the same issue wihich forced me to search out a ROM that already had HotSpot unlocked, I am currently using Frost and it comes with the Sprint Wifi Hotspot unlocked and it works great. I know there are several other ROMs out there that also have this feature... If he isnt too hooked on the stock ROM, maybe you could suggest him finding a new ROM...
All right, I've confirmed root on the Evo and flashed clockwork recovery, and now trying to flash a rom. On the page for installing CyanogenMod, it mentioned installing an Engineering SPL, and I was wondering what the purpose of this is and if it is necessary. We are trying to install Warm if that makes any difference.
Last Thursday, I installed Incubus's cleaned up and rooted 4.06.605.2 ROM: http://forum.xda-developers.com/showthread.php?t=1219407. First ROM I've installed. Not sure how I missed Stangs 4.06.605.3 ROM here: http://forum.xda-developers.com/showthread.php?t=1247253 but I did.
Now I'm trying to figured out if I want to get to 4.06.605.3, what's the best course of action? Can I update to Stangs, without a factory reset? Or can I update using the patch at the bottom of the first page of this thread: http://forum.xda-developers.com/showthread.php?t=1257679?
I'm trying to avoid a factory reset just for that patch and it seems like I should be able to do that, but it's not entirely clear.
I'm rooted with S-OFF. I have CWM recovery 5.0.2.0, so maybe I need to revert to the stock recovery first.
Will the .3 patch get me up to the new radio too (currently on 2.15.00.07.28)?
Thanks
fredmanwalking said:
Last Thursday, I installed Incubus's cleaned up and rooted 4.06.605.2 ROM: http://forum.xda-developers.com/showthread.php?t=1219407. First ROM I've installed. Not sure how I missed Stangs 4.06.605.3 ROM here: http://forum.xda-developers.com/showthread.php?t=1247253 but I did.
Now I'm trying to figured out if I want to get to 4.06.605.3, what's the best course of action? Can I update to Stangs, without a factory reset? Or can I update using the patch at the bottom of the first page of this thread: http://forum.xda-developers.com/showthread.php?t=1257679?
I'm trying to avoid a factory reset just for that patch and it seems like I should be able to do that, but it's not entirely clear.
I'm rooted with S-OFF. I have CWM recovery 5.0.2.0, so maybe I need to revert to the stock recovery first.
Will the .3 patch get me up to the new radio too (currently on 2.15.00.07.28)?
Thanks
Click to expand...
Click to collapse
You can flash stangs over .2 without factory reset, although you should still wipe cache and dalvik cache. You couldnt use the .2 to .3 patch in your current state as you need to be conpleet stock for it to install. Neither of these options will install the new radio it needs to be installed seperatly. Remember to make a nandroid first just in case.
Thanks much for the quick reply cmlusco!
So if I flash stangs over the .2 without the factory reset will it wipe my data?
I just want to know if I need to be prepared to reconfigure things (I have TB Pro for most things I can backup)
I dont believe it would wipe data, but i'd ask stang on the rom thread. You can always restore your nandroid if it does and be right back where you were on .2
That's true about the nandroid. I'll just give it a try. I don't have the ability to post in the ROM forum because I'm now, otherwise I'd ask stang.
Thanks again
Awesome. Took nandroid backup, wiped cache and dalvik, then flashed to .3 using stang's ROM. Booted up fine and no issues so far. I guess that's a good mental note to make. So long as the ROM isn't a major upgrade, I may be able to incrementally flash without a factory reset, correct?
I noticed a few things that I'm wondering if you observed since it looks like you're running the same ROM, cmlusco:
-Hardware version still shows 003. It showed that when I was running incubus's .2 ROM. My Dinc is a AMOLED. Does your's show the correct HW version?
-WiFi hardware still shows b/g only. .2 showed the same. Are you seeing the same yourself?
fredmanwalking said:
Awesome. Took nandroid backup, wiped cache and dalvik, then flashed to .3 using stang's ROM. Booted up fine and no issues so far. I guess that's a good mental note to make. So long as the ROM isn't a major upgrade, I may be able to incrementally flash without a factory reset, correct?
I noticed a few things that I'm wondering if you observed since it looks like you're running the same ROM, cmlusco:
-Hardware version still shows 003. It showed that when I was running incubus's .2 ROM. My Dinc is a AMOLED. Does your's show the correct HW version?
-WiFi hardware still shows b/g only. .2 showed the same. Are you seeing the same yourself?
Click to expand...
Click to collapse
Yes as long as its not a major update you should be able ti keep flashing over the old one.
All those issues have to do with the build.prop file in /system. Verizon actually sent the ota out this way. It is from a sprint phone. I will post a fixed one in awile. As for wifi this is correct we only get b/g no n with this update.
That wireless-n removal is uncalled for. I don't understand why HTC would do that. Is it correct that a custom kernel could reimplement that. Or maybe it was an oversight by HTC and Verizon.
fredmanwalking said:
That wireless-n removal is uncalled for. I don't understand why HTC would do that. Is it correct that a custom kernel could reimplement that. Or maybe it was an oversight by HTC and Verizon.
Click to expand...
Click to collapse
What do you mean removed, as far as i know we have never had n because our hardware dosent support it. I could be wrong, i dont think i've ever had it.
Oh and here is the fixed build.prop just download and unzip. Use root explorer go to /system and rename the build.prop already there build.prop.orig then copy the unziped file you downloaded and paste it in /system change permisions to rw-r--r-- and change owner and group to root (0) i will try to make a flashable one tomorrow im tired and need to go to bed.
http://dinc.does-it.net/build.prop.zip
Yeah, we had wireless N on 2.2. I could usually get about 65-72 Mbps on a wireless access point at work. I didn't realize it was missing, hadn't noticed.
iowabowtech said:
Yeah, we had wireless N on 2.2. I could usually get about 65-72 Mbps on a wireless access point at work. I didn't realize it was missing, hadn't noticed.
Click to expand...
Click to collapse
Mabey its not missing mabey i just dont realize i have it ill have to check it might just be another error in build.prop run a test and see if you guys have it.
cmlusco said:
Mabey its not missing mabey i just dont realize i have it ill have to check it might just be another error in build.prop run a test and see if you guys have it.
Click to expand...
Click to collapse
Ok, I'll check it out tomorrow eve at work and post back.
I tried wireless-n at work today and it is still working, just not reported properly on the phone. I didn't really pay attention to the speed before, but I guess it really is quite slower than what I'd expect from N. I was getting 65 Mbps.
On a related note, we use 802.1x and that presented a problem because secure credentials needs to be on in order to store my password. Secure credentials gets turned off if the phone is rebooted. It also gets turned off if the phone is powered down with fast boot off. With fast boot on, a power down leaves it untouched. The solution isn't too bad (re-check the Use Secure Credentials check box and re-enter the my credential pass) but it's one more irritating bug to that I don't get made into the OTA release.
---------- Post added at 07:34 PM ---------- Previous post was at 06:39 PM ----------
cmlusco said:
Oh and here is the fixed build.prop just download and unzip. Use root explorer go to /system and rename the build.prop already there build.prop.orig then copy the unziped file you downloaded and paste it in /system change permisions to rw-r--r-- and change owner and group to root (0) i will try to make a flashable one tomorrow im tired and need to go to bed.
http://dinc.does-it.net/build.prop.zip
Click to expand...
Click to collapse
Thanks, but I replaced my build.prop with this and the HW version is still 003. Can't figure out where that is the in the file. I did change WiFi to show b/g/n . What else is changed in the fixed build.prop?
Same here with the wireless n. 72 Mbps.
How do I fix unable to mount /usbstorage?
Happens whenever I wipe something in recovery or install a ROM...
Also is there a way of fixing "UnregisterIRListener is called()", which is spammed ALL THE TIME in CatLog? It's not ROM related, as a developer told me it also happens in unedited stock?
My battery life sucks after flashing multiple ROMs and kernels, in relative to the STOCK unrooted ROM with same governors and schedulers or better like ondemandx!
EDIT (Jan 31, 2014):
I am brainstorming possible causes of unregisterIRListener / unable to mount usb storage problem / bad battery:
- Unable to mount /usbstorage messed up the ROMs I install or broke root, as I keep getting errors whenever I wipe something -> therefore, maybe I am unable to clean-flash and this is causing all of my problems
- I messed up on rooting therefore some part of root is broken
- SE Linux or internal storage not being write-able is a cause
- Samsung messed up on infrared-red coding including it with Knox and when it broke, causes phone to go ballistics in logcat
- When I went ballistics in late December and early January flashing a bunch of kernels without clean-flashing, I think I broke something
Possible solutions?
- Fix root, SELinux, usbstorage error, and/or internal storage somehow
- Unroot, go back to stock and then re-root using a safer method hoping it fixes it, along with flashing an "ultimate wipe" script for the Note 3
- Find where the code is stemming from and take away the unregisterIRListener call
Mystery? said:
How do I fix unable to mount /usbstorage?
Happens whenever I wipe something in recovery or install a ROM...
Also is there a way of fixing "UnregisterIRListener is called()", which is spammed ALL THE TIME in CatLog? It's not ROM related, as a developer told me it also happens in unedited stock?
Click to expand...
Click to collapse
Fwiw - I'm not a developer
But it's true, they were in a logcat from an odexed (but rooted, otherwise unedited) stock build.
dwitherell said:
Fwiw - I'm not a developer
But it's true, they were in a logcat from an odexed (but rooted, otherwise unedited) stock build.
Click to expand...
Click to collapse
wait aren't those who make ROMs developers?
Anyways is it referring to the infrared thing on the phone?
Mystery? said:
wait aren't those who make ROMs developers?
Anyways is it referring to the infrared thing on the phone?
Click to expand...
Click to collapse
lol yeah that's one definition, I just don't feel like I make anything really, more mess w/ other peoples stuff
And yeah that's what I was thinking when I first saw it.
dwitherell said:
lol yeah that's one definition, I just don't feel like I make anything really, more mess w/ other peoples stuff
And yeah that's what I was thinking when I first saw it.
Click to expand...
Click to collapse
I uninstalled WatchOn and same thing persists... hmm. Could it be that when root broke Knox, it also affected one of the infrared functions?
Also does the same thing happen to you with the function?
Mystery? said:
I uninstalled WatchOn and same thing persists... hmm. Could it be that when root broke Knox, it also affected one of the infrared functions?
Also does the same thing happen to you with the function?
Click to expand...
Click to collapse
Tbh this stuff is a bit above my paygrade - I didn't try to mess w/ it very long though as I wrote it off as "normal" and that was it. I have an app to do the remote thing (not WatchON) and those are still in the logcat, though I never tried to look for differences when using vs. not using if that's what you are asking.
dwitherell said:
Tbh this stuff is a bit above my paygrade - I didn't try to mess w/ it very long though as I wrote it off as "normal" and that was it. I have an app to do the remote thing (not WatchON) and those are still in the logcat, though I never tried to look for differences when using vs. not using if that's what you are asking.
Click to expand...
Click to collapse
hmmm I seriously think the error unregisterIRListener is a problem Samsung screwed up on... I was searching in other threads and someone else mentioned it and idk if its related to the problem but soon afterwards they started talking about SELinux or internal storage not being write-able. Could the error be related the unregisterIRListener? Idk why but my battery life sucks on multiple roms even after flashing different kernels in the past few weeks in relative to the STOCK unrooted ROM with same governors and schedulers or better like ondemandx
I am brainstorming possible causes of unregisterIRListener (I know @dwitherell, you may not know much about this, but this is for others):
- Unable to mount /usbstorage messed up the ROMs I install or broke root, as I keep getting errors whenever I wipe something -> therefore, maybe I am unable to clean-flash and this is causing all of my problems
- I messed up on rooting therefore some part of root is broken
- SE Linux or internal storage not being write-able is a cause
- Samsung messed up on infrared-red coding including it with Knox and when it broke, causes phone to go ballistics in logcat
- When I went ballistics in late December and early January flashing a bunch of kernels without clean-flashing, I think I broke something
Possible solutions?
- Fix root, SELinux, usbstorage error, and/or internal storage somehow
- Unroot, go back to stock and then re-root using a safer method hoping it fixes it, along with flashing an "ultimate wipe" script for the Note 3
- Find where the code is stemming from and take away the unregisterIRListener call
Mystery? said:
...
- Unable to mount /usbstorage messed up the ROMs I install or broke root, as I keep getting errors whenever I wipe something -> therefore, maybe I am unable to clean-flash and this is causing all of my problems
...
Click to expand...
Click to collapse
If this is a message you are seeing while flashing things in twrp - it is completely normal and of no concern. That's all I got
I searched and couldn't find an answer to my specific situation but apoligize in advance if this is addressed. I really am new to this so don't want to screw something up.
Basically, if I am rooted with the current stock 4.3, can I take an OTA update? I don't mind losing root.
Background info:
I rooted a while ago, can't specifically but I recall it being a "one-click" method. I checked with root checker from the play store and it says I have root access. If I open SuperSU it tells me KNOX is detected and I know I never removed them so I think it's right. I am running L900VPUBMK4.
I hope 4.4 is released soon, so I'm really just preparing for that day. I need to do a factory reset in the next day or two anyways because my phone is acting up and I have a ton of junk on it anyways so I want a fresh start. I originally rooted to get wifi tethering working but that never worked out for me and I really don't need root at all.
Thanks in advance.
This should be asked under q&a but to answer your question yes you can but you will need the stock recovery installed and not CWM/Philz/TWRP
Sent from my SPH-L900 using Tapatalk
Elw00d said:
This should be asked under q&a but to answer your question yes you can but you will need the stock recovery installed and not CWM/Philz/TWRP
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Can this be moved to QA then?
So did I install a custom recovery to root? Is there a way to check? I've tried several varieties of volume +/- and power to try to boot into recovery but nothing happens.
I'm in the same boat as you, but I'm still running 4.1.2. I installed "CF Auto Root" so I could run "WiFi Tether - TrevE Mod". From what I remember it installed a different recovery as well. I'm trying to avoid completely erasing everything on my phone, I just wanna remove the root and nothing else, goto Setting, System Update, Update Firmware to whatever is the recent one available, then run CF Auto Root again. Is that not possible?
I've got MobileODIN installed on my phone, but I swear that over the years that the "standard" skill level has jumped 10 fold since my days of rooting Palm Treo's, my Samsung Epic, etc...there are so many [xxxx][xxxx][xx] box things that I'm COMPLETELY at a loss here.
m5james said:
I'm in the same boat as you, but I'm still running 4.1.2. I installed "CF Auto Root" so I could run "WiFi Tether - TrevE Mod". From what I remember it installed a different recovery as well. I'm trying to avoid completely erasing everything on my phone, I just wanna remove the root and nothing else, goto Setting, System Update, Update Firmware to whatever is the recent one available, then run CF Auto Root again. Is that not possible?
I've got MobileODIN installed on my phone, but I swear that over the years that the "standard" skill level has jumped 10 fold since my days of rooting Palm Treo's, my Samsung Epic, etc...there are so many [xxxx][xxxx][xx] box things that I'm COMPLETELY at a loss here.
Click to expand...
Click to collapse
I looked on my laptop and remember what I used. I used Kingo Android Root to do it. It didn't appear to work because I never got a "success" popup. But when I did a root check it says I have it.
How do I check if I have a custom recovery?
I'm with you M5James - very confusing. Even the "one-click" idiot proof method I used confused me. Different boxes to check that I have no idea as to what they mean.
I've rooted, installed ROM's and kernals, OC'd, custom baked my own ROM's using 7Zip, I tweaked my GF's phone so that she could use it here in the States and then while we were in Dubai as well, etc. Nowadays, when it comes to things like pushing through ADB (I have no clue what that even means, I've just heard it enough that it sticks lol), all the [xxx] before the title of the ROM, kernal, etc and I just become a dear in headlights. Lastnight I tried Googling random things on how to remove root easily and one mentioned using Superuser and just clicking the Unroot Complete icon, which I did. Running random apps says I've removed root, Market doesn't work anymore (I'd upgraded to the Lucky Patcher Market is where I'm guessing the problem is), yet even though I don't have root, I still can't get the OTA to push 4.3 to my phone. I don't even really care about having 4.3 because I'm fine w/ using 4.1.2 at the moment, I'm just sick of the random pushes to my phone asking me to update.
In regards to my Note II with just installing things like custom ROM's, I haven't wanted to do anything wild to it for fear of being like the days of when I had a custom Samsung Epic...worked great OC'd, but could never get battery stats to work right, then the phone would freak out and become laggy, I'd reboot and then suddenly the battery was dead. I just want a simple root, add root-only apps as needed like WiFi Tether, then continue on being a texting whore lol.
If you have rooted your epic and installed custom recovery all this should be pretty simple. All the info is here. Its to the point where rooting and unroofing can be down in probably under 10 mins. You have to read.
Sent from my SPH-L900 using XDA Free mobile app
I read it all, but it's gotten to the point where it's overly technical sometimes. I get lost in jargon, acronyms, I liked it better when there were 5 REALLY good guys making ROM's that worked, not 30 people making their own variations in their basement, then it turns into a pissing match of who's got the latest, fastest, most battery efficient, you've gotta do this to do that, but don't do this if you want that (assuming I know WTF "that" is in the first place) otherwise you'll brick your phone (but you can maybe unbrick it this way), if you swallow this pill you'll get rid of one symptom but you'll get 15 other problems in it's place, etc...then I just say F'it and leave my phone the way it is lol
My wife has the note2, I have the s3 (both rooted, I'm running a custom rom). I think I'm gonna take her back to stock so so she can get the update, then I'll just flash a custom recovery and su zip. It'll give me a chance to clean up her phone.
Edit: thinking of using this
http://forum.xda-developers.com/showthread.php?t=2086769
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2