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.
Hi there, long time reader, first post here
I've been running Myn's RLS4 with Clockwork 2.6 for a while, and have had no problems installing (flashing) zip files. Recently, I upgraded to RLS5 (still with Clockwork 2.6) and everything was still good to go (in reference to the Gingerbread keyboard, and Dark Coconut font zips in particular).
Well, I updated CWMod to 3.0 yesterday (after basically starting over with the phone... long story) and for some reason, the GB keyboard and Coconut fonts give an 'installation aborted' error now. The only thing that has changed was CWMod, but it just isn't making any sense. Before the abort, the recovery says something about the scripting being deprecated, and switching to Edify scripting (which it showed in the past when the flashing would work), but for some reason, with CW 3.0, it aborts the installation.
I've tried toggling script asserts and signature validation, to no avail. Is there something really simple I am missing, or I am going to have to find another zip to accommodate CW 3?
Thanks in advance for any insight!
I've been having that problem too, there are still a few things I can't flash, but it's the cw mod you're using. I haven't found the right one yet, but I've been flashing them from ROM manager... if anything goes through i'll let you know
vwgtiturbo said:
Hi there, long time reader, first post here
I've been running Myn's RLS4 with Clockwork 2.6 for a while, and have had no problems installing (flashing) zip files. Recently, I upgraded to RLS5 (still with Clockwork 2.6) and everything was still good to go (in reference to the Gingerbread keyboard, and Dark Coconut font zips in particular).
Well, I updated CWMod to 3.0 yesterday (after basically starting over with the phone... long story) and for some reason, the GB keyboard and Coconut fonts give an 'installation aborted' error now. The only thing that has changed was CWMod, but it just isn't making any sense. Before the abort, the recovery says something about the scripting being deprecated, and switching to Edify scripting (which it showed in the past when the flashing would work), but for some reason, with CW 3.0, it aborts the installation.
I've tried toggling script asserts and signature validation, to no avail. Is there something really simple I am missing, or I am going to have to find another zip to accommodate CW 3?
Thanks in advance for any insight!
Click to expand...
Click to collapse
Go back to CW 2.6. Everything will be back to normal. There were changes with the 3.0 update to CW. Anyway 2.6 works and this is the answer to your problem. Also the 2.6 version backs up Wimax.
I reverted back to 2.5.x from within ROM Manager, and all seems well. I think my nandroids were done with 2.6 (I remember seeing the system back up WIMAX during the process), so I should probably find a way to upgrade it 2.5.x to 2.6, right? I assume, if I did in fact have 2.6 before the update to 3.0, that my nandroid backups are worthless??
I switched to Amon Ra and haven't regretted it
ghost1227 said:
I switched to Amon Ra and haven't regretted it
Click to expand...
Click to collapse
I suppose now is as good of a time as any... I was avoiding it, because it's different (and CWM is pretty easy with ROM Manager) but I've had issues in the past with corrupt backups every now and then, so maybe this is the time to move. I don't think I've ever heard of issues with Amon Ra...
Well, I flashed Amon from ROM Manager, and upon reboot... well, it never rebooted. The screen just stayed black. It was completely dead until pulling the battery (which sucks, pulling the phone from this Ballistic case) but after reinstalling the battery, all is well. I just wish there was some sort of progress indicator during the backup (besides a seemingly endless line of dots).
So I tried installing Both Lou's Kernel #6 and 7. As well as Ziggy's latest beta. I cleared the Dalvik Cache as well. I still cannot seem to figure out what the issue is.
I'm running Myn's Warm 2.2 the latest release.
I have the newer Incredible with the SLCD screen but I didn't think the touch sensor would have changed at all...
I hope somebody can help me clear this up.
Thanks in advance.
What version of CWM do you have? It requires a certain version. I think it's 2.5.0.5, and it has to be unmodded (no fast scrolling, etc.).
I recently upgraded to 3.0.0.5. I hadn't had any problems with 3.0.0.5. I'll try downgrading and trying again.
Chad has a modded clockwork out that supposedly fixes it. I've never tried it personally.
So I couldn't get chads version of Rom manager to download clockwork 2.5.0.5 and I can't seem to find a 2.5.0.5 version of clockwork anywhere. I tried flashing via amon ra 1.81 for incredible but that didn't seem to work either. What exactly is the issue here? I'm not understanding how the clockwork version would interfere with installing a kernel.
Thanks a ton guys.
So I finally found a 2.5.0.5 version of clockwork, however it doesn't support SLCD screens (Just get the black screen and white lines). On top of that I booted up the phone and the touch screen wouldn't respond at all. Couldn't even unlock the phone. I had to install the SD card in my old enV 2 and rename and move the Amon Ra Recovery back to the root of the SD card and reinstall.
I'm gonna try to figure out where I can find Chad's modded version of clockwork, but this is getting very frustrating.
This has turned into an ordeal. AmonRa didn't fix my touch screen. I tried restoring an AmonRa backup but it errored and told me to restore using adb commands. I am currently at my parents house in and don't have access to ADB here. This computer is terrible. I won't be back to my house until Monday.
I reflashed Clockwork 3.0.0.5 and now am currently restoring a backup. I hope this fixes the issue...
So I found a version of clockwork 2.5.0.5 that was modified to work with SLCD, (Doug Piston's Website) and still no dice. Only 2 touches registering. I have no idea what else to try...
Bump. Im really stumped here guys. Thanks for the help.
Sent from my ADR6300 using XDA App
I use clockwork 3.7 & get 5 on chads & 10 on tiamat. Amoled tho
sent from dinc
Try opening term emulator: and type su, then cat /sys/android_touch/vendor and put the output here:
If it's AMTEL_x004F_x0016, then 2 touch is likely the limit. During all the testing that went on by Chad, I don't think anyone with SLCD or AMOLED that had the x004f_x0016 panel got more than 2. I guess they figured 2 was enough for that panel. It made no difference what version of cwm or which kernel was used. They all got 2.
If it's not what was mentioned ^^ then you can probably keep messing around with cwm versions and kernels until you find some magic combo that works.
Thanks hamchacha. I do have that panel, that's unfortunate. Not the end of the world though...
Thanks again.
LakesideWiseman said:
Thanks hamchacha. I do have that panel, that's unfortunate. Not the end of the world though...
Thanks again.
Click to expand...
Click to collapse
Sure thing. I've got it as well. I went to the Amtel website and tried to look it up, but they don't use those numbers on the site or if they do they're in some other format I can't figure out. They do , however, talk about 5-10 touch panels, and 2-touch and 1-touch panels all in the 'cellphone' (or so it appears) section, and those panel pictures all resemble the ones on our phones.
I know you can buy another one from some reseller if this is a big deal for some reason, but I'm not sure if that reseller (I could find them again) will tell you which you're getting. I think they were 30-40 bucks. I'll see if I can dig up the link. Getting it all apart might not be too simple as well.
It was for a MIDI controller. Which someone wrote an app that turns your phone into a wireless one. If you're unfamiliar, a MIDI controller allows you to program and change values in music production software with faders or different input methods on my phone.
However it is a fairly small workspace for sure a use. Because of this a plan on getting a tablet very soon. So i think it would be a waste to buy a new panel.
Thanks for all the hard work on this. Can never learn enough about my phone.
Okay this is really getting on my nerves and I've never had this much problem from a phone. I've been modding and helping develop for years, but I've never had this issue. So for five days now, I've been playing around with my old DINC that my daughter messed up somehow, and I can't install a ROM and make it work to save my life. I've run countless ROM's on this thing in the past with no issues. The problem now is, no matter what recovery I use or what I wipe, all of the old apps keep showing up on boot and crashes the phone. Meaning while it says "Android is upgrading" it shows every app that has ever been installed on this phone, even though I wipe and format every partition, and I haven't installed a single app. Heck... I can't even get into the system to install an app. The furthest I've gotten on a clean install is to pick a launcher in Carbon, but then it reboots.
Someone please help with a solution if you know one. I would hate to make a mess on the concrete outside with this phone, but I'm almost to that point. Thank you in advance!
ludeawakening said:
Someone please help with a solution if you know one. I would hate to make a mess on the concrete outside with this phone, but I'm almost to that point. Thank you in advance!
Click to expand...
Click to collapse
What recovery are you running?
I've been using CWM 5.0.2.0 since 2011 and haven't had an issue, and I still flash things on it. I found an active mediafire link with it from a post on Rootzwiki that is flashable through HBOOT. Just put it on the root/top level of an SD card formatted FAT32 and it will load the recovery image, press volume up to flash it, then you should be on an up to date recovery and you can try wiping from there. I had issues with some of the older ones and TWRPs earlier versions.
I'd also recommend CyanogenMod 7.2 stable, but that's just what I've ran the last few years. Never had an issue with it and it is stable as can be. Always a good start. In fact, it's more stable than stock on my phone, plus I over clock a bit.
It's a good device to have around when you have to send in your current device for exchange or damage it etc. I used it full time not long ago while exchanging my M8.
BrettApple said:
What recovery are you running?
I've been using CWM 5.0.2.0 since 2011 and haven't had an issue, and I still flash things on it. I found an active mediafire link with it from a post on Rootzwiki that is flashable through HBOOT. Just put it on the root/top level of an SD card formatted FAT32 and it will load the recovery image, press volume up to flash it, then you should be on an up to date recovery and you can try wiping from there. I had issues with some of the older ones and TWRPs earlier versions.
I'd also recommend CyanogenMod 7.2 stable, but that's just what I've ran the last few years. Never had an issue with it and it is stable as can be. Always a good start. In fact, it's more stable than stock on my phone, plus I over clock a bit.
It's a good device to have around when you have to send in your current device for exchange or damage it etc. I used it full time not long ago while exchanging my M8.
Click to expand...
Click to collapse
I've tried every recovery you can think of for this device. All versions of the CWM and TWRP touch and non-touch, including CWM 5.0.2.0. And I use HBOOT to flash all of the recoveries. It doesn't matter what ROM or recovery I flash, I still get the same results. And the ROM I used the most on this phone was Condemned CM7.2, but like I said, it won't matter how stable a ROM is, I can't get it to boot to even use it now. For some reason there is a partition somewhere that will not wipe. I've used VR Superwipe, which was recommended on some ROM's in the past, but it doesn't help at all either. No matter what, while booting for the first time, it still shows every app that has ever been installed to this device over the years, which causes everything to crash or just immediately reboot. All of the apps crash even if I go back completely stock by flashing a PB31IMG of stock firmware with HBOOT. That includes trying it with S-ON and S-OFF. As you can tell, this isn't my first rodeo at all. Lol
I've been doing this for years and have helped develop ROM's on a couple of sites, but I've never seen or heard of anything like this. Thanks for the input though.
I guess I'll risk completely bricking it, and manually re-partition the device and push the bootloader and everything else to it with ADB Shell. I've got nothing to lose, it's already a paperweight that just lights up. Haha
ludeawakening said:
No matter what, while booting for the first time, it still shows every app that has ever been installed to this device over the years, which causes everything to crash or just immediately reboot.
Click to expand...
Click to collapse
Sounds like a bad NAND to me (like one partition is fried and is now read-only). Good luck with the repartitioning. If you're feeling adventurous, you could try this. If you're feeling really adventurous, I seem to remember reading a post from someone who had actually unsoldered the NAND chip and got the phone to boot using only an sdcard. I can't find the post right now though.