Related
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.
Ok, so here is what I have done: I have already rooted my phone, etc, and have flashed some different roms on my phone, and have not had any problems until now. I recently tried the miui rom, but didn't like it.I just flashed the newest miui rom, and it was acting really weird, so I decided to go back to the virtuous rom which I had used before. For whatever reason, I am getting this error: E: can't mount /dev/block/mmcblk0p1 (file exists), and the installation aborts. I did the wipe data deal, and I also tried to reinstall the miui rom. It says that installs fine, but it won't get past the htc incredible screen. Any suggestions? Also, I didn't want to try this and mess things up further, but can I restore a backup I had done when I had the virtuous rom installed, or do I have to have the rom already working properly? Kind of a noob question, I know.
calamari85 said:
Ok, so here is what I have done: I have already rooted my phone, etc, and have flashed some different roms on my phone, and have not had any problems until now. I recently tried the miui rom, but didn't like it.I just flashed the newest miui rom, and it was acting really weird, so I decided to go back to the virtuous rom which I had used before. For whatever reason, I am getting this error: E: can't mount /dev/block/mmcblk0p1 (file exists), and the installation aborts. I did the wipe data deal, and I also tried to reinstall the miui rom. It says that installs fine, but it won't get past the htc incredible screen. Any suggestions?
Click to expand...
Click to collapse
Hmmm... Do you have any Nandroids from earlier roms? That'd be the easiest route.
If not, since you can't even get to a homescreen, you might try an RUU reset, but let's hope it won't come to that for now.
I get that too, but only when going into the menu for Dalvik Cache wiping, and it never actually gets in my way, it just pops up and then I can keep going on about my business.
1. yes you can restore the backup whether a rom is currently working or not
2. post questions in the correct forum
If you can't get a nandroid backup to work, you may have to RUU back to stock.
Here's the older one that will still let you use unrevoked after. Just rename this PB31IMG.zip, load up H-boot, follow the prompts, and be patient. Then run unrevoked when it finishes and install rom manager to restore your backup. If the backup still won't work, try a fresh install of virtuous.
Sorry
g00s3y said:
1. yes you can restore the backup whether a rom is currently working or not
2. post questions in the correct forum
Click to expand...
Click to collapse
My apologies, where should I have posted? And can I move the thread so it is in the correct place?
calamari85 said:
My apologies, where should I have posted? And can I move the thread so it is in the correct place?
Click to expand...
Click to collapse
Probably in the Q & A General Forum, but don't worry about it this time, just as long as it doesn't end up being a frequent thing.
But I don't know about being able to move the thread, I think that's a Moderator power.
Regarding your issue though, either use the RUU link posted above, or try Nandroid-ing back.
No go
I tried restoring a backup, and got cannot mount /data, along with the previous error... It changed my boot animation, but has not restored my phone. should I do this RUU back to stock? Sorry for not being very good at this, and I definitely appreciate the help.
calamari85 said:
I tried restoring a backup, and got cannot mount /data, along with the previous error... It changed my boot animation, but has not restored my phone. should I do this RUU back to stock? Sorry for not being very good at this, and I definitely appreciate the help.
Click to expand...
Click to collapse
It's cool.
Yes, you'll need it on the root of your SD-card (not in any folders), run it through hboot, and then you'll have to re-run the unrEVOked tool from your PC. I would also suggest running the S-Off tool afterwards, just to be safe. That has saved me once before.
Make sure you have at least 50% battery before you do the hboot flash. VERY IMPORTANT. If your phone dies or loses power while updating the radio files from the RUU, your phone is as good as bricked.
If you get stuck with the unrEVOked tool at waiting for root for more than fifteen minutes, post back here again and we'll continue from there.
EDIT: Actually, run the unrEVOked Forever S-Off tool through CWM recovery before doing this, as a pure precautionary measure.
I'm an idiot apparently
Well, I am really sorry guys, I won't ask any more questions on here. Apparently I am super stupid. I figured it out, I left out some info because it didn't even register as relevant, but it was the key apparently. So I just go a new sd card, and I formated it on my computer, and just dropped the zip files on there, and was trying to flash like that, and apparently the phone didn't like the new sd card, or it needed info off the old one, because once I put it back in and tried flashing from it, it works fine now. Sorry for bothering everyone, I am going to go sit in the corner in shame now.
calamari85 said:
Well, I am really sorry guys, I won't ask any more questions on here. Apparently I am super stupid. I figured it out, I left out some info because it didn't even register as relevant, but it was the key apparently. So I just go a new sd card, and I formated it on my computer, and just dropped the zip files on there, and was trying to flash like that, and apparently the phone didn't like the new sd card, or it needed info off the old one, because once I put it back in and tried flashing from it, it works fine now. Sorry for bothering everyone, I am going to go sit in the corner in shame now.
Click to expand...
Click to collapse
Hahaha! No worries, we all have our moments!
Glad you figured it out. Be sure to make a backup of your current rom on your new SD card right away haha.
help with flashing myns 2.2
Hey guys I've been reading the threads for a while and finally decided to root my evo last night using unrevoked..I made a nandroid as well ad a ti backup. I download myns last night and I think I put it into the root if my SD card according to directions I found using astro. I keep on trying to flash the Rom from my recovery and it goes about 3/4 of the way then aborts and states E:can't symlink/system/bin/ then e: failures at line 15. Then finally symlink busybox system : xbin.. I have not partitioned my SD card yet since I have read places there is no need to.. if anyone could shed some light on this is really appreciate it..BTW I'm on stock froyo atm
Hey guys I've been reading the threads for a while and finally decided to root my evo last night using unrevoked..I made a nandroid as well ad a ti backup. I download myns last night on my phone and I think I put it into the root if my SD card according to directions I found using astro. I keep on trying to flash the Rom from my recovery and it goes about 3/4 of the way then aborts and states E:can't symlink/system/bin/ then e: failures at line 15. Then finally symlink busybox system : xbin.. I have not partitioned my SD card yet since I have read places there is no need to.. if anyone could shed some light on this is really appreciate it..BTW I'm on stock froyo atm
are you s-off, what recovery?
Could be a corrupt download so I would try to redownload the rom and then reinstall. But what hardware version and hboot do you have?
Yes s is on..and the recovery is clockwork..
Wrong section bud, don't post questions in here especially since you already posted in Q&A. But you need your S-OFF thats why your having problems.
definitely need s-off, but have you tried to DL it again?
yea i thought it might be on the wrong forum so i reposted it there after, i apologize. how do i get the s off. Im not very good at this.. im interested in alt his stuff but not very good yet..i thought when i rooted it would turn s off..and yea ive tried installing it several time with no luck and same error
in another thread someone told me that its not working bc im still s-on..how do i turn that off.. hardware version 0003
First, you need to verify whether s is on or off. To do this, power down your phone, and hold the volume down button while you power it back on. It will boot into a white screen with 3 Androids on skateboards at the bottom. The very first line at the top of the screen will indicate if s is off or on.
If you rooted with Unrevoked, s should be off. However, I believe that before you can flash custom roms, you need to unlock NAND by flashing the engineering SPL onto your phone. On the same screen where you see if s is on or off, it needs to say Hboot: 0.76.2000 on the second line. If it has any other version of the hboot, you will not be able to flash custom roms.
This is what I did 1 week ago when I rooted my girl's Evo (also a 0003):
1) Ran Unrevoked for root.
2) Installed ROM Manager to flash recoveries & TI for back-ups.
3) Put Myn's RLS 4 on root of SD, and tried to flash via recovery; got errors similar to yours.
4) Downloaded engineering spl and placed on root of SD
5) Went back into recovery and flashed the eng. spl (at this point, I tried to boot it and the phone had no rom and would loop at the white HTC EVO 4G screen).
6) Got the phone back in recovery by doing a battery pull, powering on while holding volume down, and selected recovery.
7) From the recovery, I flashed Myn's RLS 4, my favorite kernel, a custom boot screen, and then rebooted.
8) Opened a beer and relaxed.
Don't forget to wipe everything twice! Also, before you flash the eng. spl, make sure you go into ROM manager and use the option to "flash an alternate recovery" so you do everything with Amon recovery which does a better job wiping. However, with Amon you cannot navigate through all the folders on your SD card to find what you want to flash. All flashable files MUST be placed in a .zip format in the root of your SD card (meaning out in the open and NOT inside any folders)
I hate using ADB, and if you follow these steps precisely, you will not need it.
Good luck!
i will try what you say to do..im just nervous bc that sounds complicated with my limited computer skills..i just dont understand why s-on is still there..isnt that the point of rooting.. can i unroot and run unrevoked forever?..is there any difference ?
firmbiz94 said:
i will try what you say to do..im just nervous bc that sounds complicated with my limited computer skills..i just dont understand why s-on is still there..isnt that the point of rooting.. can i unroot and run unrevoked forever?..is there any difference ?
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Check your hboot version, and see what it is. If it is hboot 2.02, that is your problem. Unrevoked doesn't work (yet)with that hboot version. Currently, the only way to root that hboot version is the "boss" method. Can be found in the development section. You can check by doing the same thing the guy before mentioned, hold vol down, and power button together. Then you will see the version, at the bottom I think. When did you get your Evo? What hardware version are you? ( settings, about phone, hardware info) software info the same way, see if your build 3.29 or 3.30.
Edit: looks like the thread is now "like a pinecone" rather than "like a boss"
OP: Rooting does not turn s off. Root allows you to run programs that require root access. With root, you can run wireless tether, ROM Manager, Titanium back up, Shootme app for screen shots, etc.
However, to flash custom roms, you need to have NAND access and that is done by flashing the engineering hboot. You can find the engineering hboot here:
http://forum.xda-developers.com/attachment.php?attachmentid=342668&d=1276481802
Like k2buckley, if you have the 2.02 hboot, you need to follow this root guide:
http://forum.xda-developers.com/showthread.php?t=829045
It requires lots of ADB and this is for more advanced users. If you are going to try it, make sure your battery is completely charged before you start messing with it. I HIGHLY recommend you search YouTube for video tutorias on the root method you need to use and watch it from beginning to end (twice if you need to) to make sure this is something you feel you can do before you dive in.
Merged 2 threads.
I finaLly figured it out..I got frustrated and figured I'd flash unrevoked forever..I downloaded to SD card and flashed it..that turned nand off..then I flashed myns..and it worked..i couldn't believe it..thanks for your help guys..
I downloaded shootme to take a shot of my software to so you guys. But when I try to attach a file it doesn't do anything when I press search..anyways so far I really like the Rom and netarchy kernel..I think I'm gonna be addicted and flash often although I nandroid backed this one since I like it..any other suggestions for sense roms..I just want to have a blazing fast Evo..not sure if I wanna go aosp though..
Hey people!
I read a few posts dealing with same error below, but the descriptions of the problem was a bit different so I wanted to be sure.
I'm quite new to this so bear with me. I got an EVO last month (dec 24) and have since wanted to root. I've been reading up on it, and finally decided to root using Unrevoked earlier today. The root process worked perfectly, so I proceeded to create a nand backup and flashed the CM6 Mod using Clockworkmod rom manager app.
I was a bit excited played around with it a bit, and decided to flash the Miui ROM. I placed it on the root of my SD card, and this is where I lost control. I tried to flash using the ROM manager and it never completed, citing an error. I tried to reboot phone but I didnt get past the white HTC EVO 4G screen. I entered bootloader, and I tried to restore my original Nand backup but I keep getting this error, "Error while flashing boot image."
What would be the appropriate (or least risky) course of action? I can mount my SD card on computer through ClockworkMod recovery, should I try placing stock ROM zip or cm6 zip file and try to flash?
I do not think this is a battery issue, I had my phone plugged to charger while trying to flash nand.
I appreciate the help, I know I probably sound like a noob, but for almost a month I was reading, learning and trying to be careful (obviously not enough), once I rooted I got overzealous.
MOD Version is 2.5.0.1
Thanks for all your help,
DJ
I flashed a the recovery, after a few issues...my phone is back up and running...DISREGARD. Sorry for the noob ?.
I apologiz if this has been answered, or beat into hte ground, or what. I cant really find an answer, and not sure what to search for either.
I recently noticed that my hboot is "s-on". I still have root, and su and everything. ?I want to update hboot from .76.2000 to the latest, which is 2.16.00.
I see I can go to this revolutionary website and generate a key which allows me to get s-off, but it looks like thats for rooting a brand new ohone. mine is already rooted, just has S-ON.
can I flash hboot 2.16.00, then flash that revolutionary patch/s-off and be in good shape, or would that mess something up? I'm trying to flash the anthrax kernel, and I need something higher than .76
Interestingly I had a very similar issue yesterday. If you have some qxdm files on the root of your sdcard, and can't mount the sdcard, this may work for you. I had to execute a couple of commands in fastboot mode. I am assuming with these steps that you have a computer, win/lin/mac whatever with adb already configured, etc.
Power off phone
Remove sdcard
Power on holding vol down
Select Fastboot
Connect USB to computer
Open cmd prompt/terminal on computer
Execute
Code:
fastboot oem enableqxdm 0
Execute
Code:
fastboot oem eraseconfig
Power off phone
Insert sdcard
Rejoice!
I really hope this works for you, I wasted a couple of hours digging around google to find this.
Flash the unrevoked forever zip through recovery, not sure if it's compatible with your hboot or radio, but it's worth a shot.
You can always RUU to like 3.70 and run unrevoked. I'd prefer that over updating to the latest and running revolutionary since unrevoked doesn't use a different hboot and is easier to unroot, but you can do either if you don't find a different way.
Happy New Year!
Supersonic Evo 4G | MIUI | Tapatalk
jasongthang said:
I apologiz if this has been answered, or beat into hte ground, or what. I cant really find an answer, and not sure what to search for either.
I recently noticed that my hboot is "s-on". I still have root, and su and everything. ?I want to update hboot from .76.2000 to the latest, which is 2.16.00.
I see I can go to this revolutionary website and generate a key which allows me to get s-off, but it looks like thats for rooting a brand new ohone. mine is already rooted, just has S-ON.
can I flash hboot 2.16.00, then flash that revolutionary patch/s-off and be in good shape, or would that mess something up? I'm trying to flash the anthrax kernel, and I need something higher than .76
Click to expand...
Click to collapse
What recovery where you using? And what did you wipe before this happened? You seem to have hit the sake thing as me, but my recovery was gone, as well as my Rom.
Sent from my PC36100 using xda premium
I'm using Amon Ra
I was following this guide [Guide][31 Dec] Rooting and Sense Guide! to try and flash everything decently and how it should be. I flash the newest radios/nv/wimax the way it shows. I got to the kernel, he recommended Anthrax, so I downloaded it and flashed it. The phone wouldnt boot past the splash screen.
So I pull the battery, and pwr+vol down because I want to get into recovery. Well it boots normally into the white hboot screen, and I happen to look at the security, it says S-ON. Huh, thats weird, but everything is working normally (i think) so I just go into recovery, and flash ChopSuey's kernel. THAT doesnt let me boot past the splash screen.
So looking more at Anthrax thread, I notice that you need to have a higher hboot int order to flash the Anthrax kernel successfully, i have .76.2000. Someone has a link for a .93 hboot, so I download and flash it. I flash the Anthrax kernel from recovery, but now the phone wont boot, it just keeps going back to the white hboot screen. I have the phone working now by just re-flashing the rom (evo classic), but I want to get the S-ON situation fixed, I want to have the proper hboot that I need, and I would LIKE to get the Anthrax kernel working, although I could go to another one if its just not going to work.
Is there a good write-up on just what exactly the hboot is and what it does? I never read up on it because it never seemed to be something I needed.
Thanks for your replies.
plainjane said:
Flash the unrevoked forever zip through recovery, not sure if it's compatible with your hboot or radio, but it's worth a shot.
You can always RUU to like 3.70 and run unrevoked. I'd prefer that over updating to the latest and running revolutionary since unrevoked doesn't use a different hboot and is easier to unroot, but you can do either if you don't find a different way.
Happy New Year!
Supersonic Evo 4G | MIUI | Tapatalk
Click to expand...
Click to collapse
Are you pretty much saying to just completely flash back to stock un-rooted, and start all over again? That would be fine with me, would that straighten out any hboot problems as well, as far as putting the hboot back to the way it should be, or was?
It's not a bad idea. RUU back to stock, accept the updates, then root using whatever the most current version is.
Ok, messed around and updated with a back-to-stock pc36img, the hboot version was still .93... So now I've successfully rooted with unrevoked. s-off, super user, everything is fine, but i'm still at the .93 hboot.
What exactly is hboot, and can I update it to 2.16.0001? How do i know which hboot i should be on?
Also, I apologize again but its been a while. My phone is running clockwork recovery. Can I just flash the amon ra recovery zip through clockwork?
jasongthang said:
Ok, messed around and updated with a back-to-stock pc36img, the hboot version was still .93... So now I've successfully rooted with unrevoked. s-off, super user, everything is fine, but i'm still at the .93 hboot.
What exactly is hboot, and can I update it to 2.16.0001? How do i know which hboot i should be on?
Also, I apologize again but its been a while. My phone is running clockwork recovery. Can I just flash the amon ra recovery zip through clockwork?
Click to expand...
Click to collapse
No reason the upgrade your HBoot. Latest doesn't necessarily mean best. I wouldn't go any higher than 0.97, personally, since that's the last version that's downgradable.
You'll be fine with what you have.
Captain_Throwback said:
No reason the upgrade your HBoot. Latest doesn't necessarily mean best. I wouldn't go any higher than 0.97, personally, since that's the last version that's downgradable.
You'll be fine with what you have.
Click to expand...
Click to collapse
Captain, any idea why some of us seem to be having trouble restoring back, while others aren't?
I'm almost at my wits end here. The hours I've put into this makes me feel like I'm close, but the honest truth is that I've yet to so much as get my device to stop showing up as a Qualcomm Diag Mgr, when I first turn the phone on, & haven't even gotten root or S-Off yet.
I've got a HW0004 evo, which I'd previously rooted with unrevoked & 2 - 3 months ago had rooted with unrevoked forever. I was running Decks, with a 32 gb sd card, which I was constantly having to run parted on b/c my sd-ext was losing it's filesystem, and my last attempt to fix this without going back to a 16 gb card was to switch from amonRA to TWRP 2.0, then repartition with a ext4 partition this time. It had been running smoothly for a week, if not longer, so I decided that I could go ahead & flash firerat's mod again, this time with a more accurate (and smaller) system partition. When I rebooted I started having this issue.
I'm somehow back to S-ON, 2.10.0001, 2.15.00.11.19 radio, with no access to adb. When I tried to flash the RUU that you posted over on MikMIk, to go back to stock 3.70, i had a ton of problems getting it to actually complete (everything from stopping in the middle of it, to going to a black screen, as if it had stopped, then coming back on & looking like it was going to finish, to stopping when I got to the reboot screen, but I'm pretty sure that it did finally flash. The only problem is that it still won't recognize my phone when I run unrevoked3, and it won't stay on long enough to let me figure out why.
ncadden said:
Captain, any idea why some of us seem to be having trouble restoring back, while others aren't?
I'm almost at my wits end here. The hours I've put into this makes me feel like I'm close, but the honest truth is that I've yet to so much as get my device to stop showing up as a Qualcomm Diag Mgr, when I first turn the phone on, & haven't even gotten root or S-Off yet.
I've got a HW0004 evo, which I'd previously rooted with unrevoked & 2 - 3 months ago had rooted with unrevoked forever. I was running Decks, with a 32 gb sd card, which I was constantly having to run parted on b/c my sd-ext was losing it's filesystem, and my last attempt to fix this without going back to a 16 gb card was to switch from amonRA to TWRP 2.0, then repartition with a ext4 partition this time. It had been running smoothly for a week, if not longer, so I decided that I could go ahead & flash firerat's mod again, this time with a more accurate (and smaller) system partition. When I rebooted I started having this issue.
I'm somehow back to S-ON, 2.10.0001, 2.15.00.11.19 radio, with no access to adb. When I tried to flash the RUU that you posted over on MikMIk, to go back to stock 3.70, i had a ton of problems getting it to actually complete (everything from stopping in the middle of it, to going to a black screen, as if it had stopped, then coming back on & looking like it was going to finish, to stopping when I got to the reboot screen, but I'm pretty sure that it did finally flash. The only problem is that it still won't recognize my phone when I run unrevoked3, and it won't stay on long enough to let me figure out why.
Click to expand...
Click to collapse
Well I know quite a few people that used TWRP had similar issues (sd card issues aside). But it could be firerat's that was the last straw. Let's say that you have bad blocks on your system partition, but then you use the mod to reduce the size if the partition to a size that *should* be big enough to accomodate everything, but due to your bad blocks, actually isn't. That would likely lead to corruption of your system partition, and everything would go downhill from there. Personally, I've tried to reproduce most of these issues on my device with TWRP and haven't had any success. My phone always works fine. I think it just comes down to everyone's devices being different, and the bad blocks causing device corruption one way or another with the ones that fail.
jasongthang said:
I apologiz if this has been answered, or beat into hte ground, or what. I cant really find an answer, and not sure what to search for either.
I recently noticed that my hboot is "s-on". I still have root, and su and everything. ?I want to update hboot from .76.2000 to the latest, which is 2.16.00.
I see I can go to this revolutionary website and generate a key which allows me to get s-off, but it looks like thats for rooting a brand new ohone. mine is already rooted, just has S-ON.
can I flash hboot 2.16.00, then flash that revolutionary patch/s-off and be in good shape, or would that mess something up? I'm trying to flash the anthrax kernel, and I need something higher than .76
Click to expand...
Click to collapse
I know how to fix this had the same problem a few months back
1 : Download the stock RUU executable for your PC
2 : Make sure you have the htc sync drivers installed on your PC
3 : Enable USB debugging in your phone's settings menu
4 : Hook your phone up to PC and run the RUU (This will return it 100% to stock)
5 : You will know need to root again. (this is the only way I got through this problem)
6 : After you root s will be off (delete or rename any PC36IMG.zip after you have used them from your SD card)
Here is the RUU that got me out of the same problem they won't let me post links yet just google this....
RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15.00.0808_NV_2.15_release_209995_signed
My phone is back to....somewhat normal now, i think lol.
I may just be having issues with the particular rom I'm on. But everything seems fine.
I have reverted back to hboot eng .76.2 because I wasnt able to fastboot with .93, and I wanted to flash a custom boot image. When I flashed the .76 hboot, I wasnt able to boot my phone, i could only bounce between recovery and hboot. What seemed to fix this is reflashing the rom. I only wiped dalvik and cache, nothing else. This allowed me to boot right up normally, and I have fastboot commands. But I'm back to square one in that I don't have that anthrax kernel running anymore. I'm thinking of jumping back on the MIUI train though.