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.
So, i rooted my EVO a long time ago with unrevoked 2, i believe, and i decided i didn't want to bother with roms and all that crap, so i decided to update to 2.2, but unfortunately after i download it and start the install, it stops about a third the way through of the install of froyo and gives me a error(triangle with a ! in it, little android guy next to it on the bottom right). I'm not exactly sure why this is happening, but i thought something was screwed up, so i decided to do a factory refresh after backing up all my stuff. Did so, and got same results, think i read it has something to do with the custom recovery added on with unrevoked? Well, can anyone help me get to straight up 2.2(new OTA for 30 fps fix as well), then root? I really just don't want to bother with ROM's right now. Thanks in advance for any help!
Oh and, after i get the error, it reboots fine after i pull out the battery.
It's a sticky in the development thread 3.28.651.5 I believe. Just flashed it, stock rooted Rom. To me seems a lot faster (I'm very picky haha) was running a stock rooted rom prior. Did NOT lose root. Must be fully rooted though (s-off) with unrevoked forever. Hope that helps. BTW do a search next time or someone will flame u
Sent from my PC36100 using XDA App
Hey folks,
Thanks for taking the time to read/assist. I don't typically do these kinds of posts and am at my wit's end!
Phone's Previous Setup - MIUI Gingerbread, Rooted (but with S-ON after the fact).
What happened:
My HTC Incredible finally got to the point of being practically unuseable with laggy behavior and random restarts and the like, so I decided to complete a reset to factory settings or wipe.
I completed my backups using Titanium (apps) and ClockworkMod Recovery (full backup). After this, I went ahead and opened up Settings and directed the phone to complete a Reset to Factory Settings. It ran through the process, rebooted, and came up jelly. While no custom apps were installed (expected), my folder settings on my main home page were saved, along with some previous text messages. I was pleasantly surprised.
From here, I wished to wipe the SD Card so as to make sure it was clean of any residual folders/files that might cause conflict down the road (based on advice from others). So, headed to the SD card part of the settings. Had to unmount the SD card to format, proceeded to do so.
Here's where things went wonky: Despite receiving a confirmation that the SD card format had proceeded, nothing else ever happened. I attempted to mount the card again w/o luck (kept getting a msg that it was now unmounted). Eventually, I decided to go ahead and restart the phone and see if that helps. Big mistake.
From this point forward, the phone refuses to fully start up into any Android ROM. Initially, it hung on the white HTC Incredible splash screen (yes, even w/ giving it an hour+ of time). I tried wiping and reflashing different ROMS over the period of the day yesterday to no avail.
Doing a full recovery via ClockworkMod (from my backup that I made before and copied back onto the SD card via USB) leaves me stuck on the HTC Incredible white splash screen.
MIUI - 2.2.10
Hangs on white splash screen
No go w/ or w/o SD card installed
MIUI - 2.2.17
Loads past white and MIUI splash screens
Instead of loading into Android homescreen, immediately loads up "Encryption" error and directs to "reset phone."
Repeated restart and attempts of resetting phone don't work
No go w/ or w/o SD card installed.
MIUI - 1.12.9
Hangs on white splash screen.
No go w/ or w/o SD card installed.
CM - 7.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
CM - 6.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
I looked into HBOOT options, getting PB31IMG.ZIP and PG86IMG.ZIP.img thinking maybe I could try reverting to stock at a friend's suggestion. HBOOT sees the files and "checks" them, even briefly showing a small vertical blue loading bar at the top-right corner, but never attempts to run/update them as I am lead to expect from all the instructions/encounters I've found on the net suggest. The screen info flashes by so quickly, I can barely read it, but I confirmed that it said "checking" and not updating or such. x.x
I considered trying to flash an updated copy of ClockworkMod Recovery, but I cannot do that w/o being able to load up the phone into Android.
I cannot run anything desktop-side, like ADB, as they all require the phone started up and put into USB-debugging mode.
I've looked into and tried all this and more, but nothing seems to be working.
My next idea is to try to forcibly downgrade the phone. Reasoning being that I read that the HBOOT will not try to update if it senses that the ROM is newer than its default settings(?). So, I need a good choice of "old" ROM that I can attempt to install via the HBOOT or CWM Recovery, and verify I have the correct files for HBOOT to try updating/running.
Again, this is a speculative attempt, but I'm willing to try whatever might work! Otherwise, I've got a fancy brick and my well-being on the line w/ no $$ to replace the phone. x.x
Thanks again for reading and hopefully offering some wonderful assistance! Sorry it's so long!
Feel free to ask Qs if you need clarification on stuff.
wigmuke said:
Hey folks,
Thanks for taking the time to read/assist. I don't typically do these kinds of posts and am at my wit's end!
Phone's Previous Setup - MIUI Gingerbread, Rooted (but with S-ON after the fact).
What happened:
My HTC Incredible finally got to the point of being practically unuseable with laggy behavior and random restarts and the like, so I decided to complete a reset to factory settings or wipe.
I completed my backups using Titanium (apps) and ClockworkMod Recovery (full backup). After this, I went ahead and opened up Settings and directed the phone to complete a Reset to Factory Settings. It ran through the process, rebooted, and came up jelly. While no custom apps were installed (expected), my folder settings on my main home page were saved, along with some previous text messages. I was pleasantly surprised.
From here, I wished to wipe the SD Card so as to make sure it was clean of any residual folders/files that might cause conflict down the road (based on advice from others). So, headed to the SD card part of the settings. Had to unmount the SD card to format, proceeded to do so.
Here's where things went wonky: Despite receiving a confirmation that the SD card format had proceeded, nothing else ever happened. I attempted to mount the card again w/o luck (kept getting a msg that it was now unmounted). Eventually, I decided to go ahead and restart the phone and see if that helps. Big mistake.
From this point forward, the phone refuses to fully start up into any Android ROM. Initially, it hung on the white HTC Incredible splash screen (yes, even w/ giving it an hour+ of time). I tried wiping and reflashing different ROMS over the period of the day yesterday to no avail.
Doing a full recovery via ClockworkMod (from my backup that I made before and copied back onto the SD card via USB) leaves me stuck on the HTC Incredible white splash screen.
MIUI - 2.2.10
Hangs on white splash screen
No go w/ or w/o SD card installed
MIUI - 2.2.17
Loads past white and MIUI splash screens
Instead of loading into Android homescreen, immediately loads up "Encryption" error and directs to "reset phone."
Repeated restart and attempts of resetting phone don't work
No go w/ or w/o SD card installed.
MIUI - 1.12.9
Hangs on white splash screen.
No go w/ or w/o SD card installed.
CM - 7.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
CM - 6.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
I looked into HBOOT options, getting PB31IMG.ZIP and PG86IMG.ZIP.img thinking maybe I could try reverting to stock at a friend's suggestion. HBOOT sees the files and "checks" them, even briefly showing a small vertical blue loading bar at the top-right corner, but never attempts to run/update them as I am lead to expect from all the instructions/encounters I've found on the net suggest. The screen info flashes by so quickly, I can barely read it, but I confirmed that it said "checking" and not updating or such. x.x
I considered trying to flash an updated copy of ClockworkMod Recovery, but I cannot do that w/o being able to load up the phone into Android.
I cannot run anything desktop-side, like ADB, as they all require the phone started up and put into USB-debugging mode.
I've looked into and tried all this and more, but nothing seems to be working.
My next idea is to try to forcibly downgrade the phone. Reasoning being that I read that the HBOOT will not try to update if it senses that the ROM is newer than its default settings(?). So, I need a good choice of "old" ROM that I can attempt to install via the HBOOT or CWM Recovery, and verify I have the correct files for HBOOT to try updating/running.
Again, this is a speculative attempt, but I'm willing to try whatever might work! Otherwise, I've got a fancy brick and my well-being on the line w/ no $$ to replace it. x.x
Thanks again for reading and hopefully offering some wonderful assistance! Sorry it's so long!
Feel free to ask Qs if you need clarification on stuff.
Click to expand...
Click to collapse
You need to gain s-off again before flashing with clockwork. How come you turned it back on?
"In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag."
edit:
gain s=off boot into CMW wipe data, and factory reset. Flash a new rom of your choice and then boot. should get you back to a working phone.
synisterwolf said:
You need to gain s-off again before flashing with clockwork. How come you turned it back on?
"In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag."
edit:
gain s=off boot into CMW wipe data, and factory reset. Flash a new rom of your choice and then boot. should get you back to a working phone.
Click to expand...
Click to collapse
The first time my phone was rooted/flashed, my bf did it for me. He used Unrevoked to root it and install CWM Recovery (v2.5.1.2 presently). I recall conversation being that having S-On would be better security with regards to the cell carrier (e.g., good to leave on, bad if off as they can see you rooted). So I agreed to having it put back to S-On, which I understood he then took care of.
Fast-forward a year and he now tells me he didn't actually end up running the other Unrevoked (Forever) tool to put S-On back in place, but that it simply *was*, so he left it that way. o.o;
Keep in mind, I've flashed 3 different ROMs since he originally rooted and flashed, w/o issues.
I pulled up everything to try re-rooting it again (to gain S-Off), but the instructions required having the phone loaded up and in debugging mode, which I cannot do as I cannot start up the phone past recovery in the first place.
Did I miss something that allows it via recovery? Going to check again in the meantime.
wigmuke said:
The first time my phone was rooted/flashed, my bf did it for me. He used Unrevoked to root it and install CWM Recovery (v2.5.1.2 presently). I recall conversation being that having S-On would be better security with regards to the cell carrier (e.g., good to leave on, bad if off as they can see you rooted). So I agreed to having it put back to S-On, which I understood he then took care of.
Fast-forward a year and he now tells me he didn't actually end up running the other Unrevoked (Forever) tool to put S-On back in place, but that it simply *was*, so he left it that way. o.o;
Keep in mind, I've flashed 3 different ROMs since he originally rooted and flashed, w/o issues.
I pulled up everything to try re-rooting it again (to gain S-Off), but the instructions required having the phone loaded up and in debugging mode, which I cannot do as I cannot start up the phone past recovery in the first place.
Did I miss something that allows it via recovery? Going to check again in the meantime.
Click to expand...
Click to collapse
actually its better to keep it s=off so this type of situation wont happen. Your carrier cant see your hboot from my understanding on how this phone works. They dont care if you have root or not, unless you are trying to exchange the phone for another one from them or for insurance reasons. With root you only void your warranty on the phone and not your contract or anything to do with VZW. S=off is just a NAND lock, meaning you cant add your own custom recover to the phone, and you are limited to builds that come from VZW themselves (ie the security signature check).
If you ever want to take the phone back to them because its defective or call insurance then you need to remove root and S=on. but thats the only time you need to toggle the NAND lock.
ok so you will need to ruu to stock, downgrade then gain s=off over again:
for the ruu for GB:
http://forum.xda-developers.com/showthread.php?t=1227279
a guide to do this all after you ruu:
http://forum.xda-developers.com/showthread.php?t=1306400
OMG I may've gotten it!
So I decided to give things another go with attempting to revert to stock again, as at this point, nothing is going to work other than via HBOOT.
I completed another reformat of the SD Card (Fat32) to be on the overcautious side and copied over ONLY the PB32IMG.zip file and restarted into HBOOT.
(Ah.. new user, so not allowed to post the link of where I got it.)
This time, much like before, it scanned, found the file, and did a parsing/loading. However, THIS TIME it actually prompted me to update! I chose yes (Vol+) and let it do its thing.
At this time, I am happy to announce that it actually is back up stock!
Wooohoo! Now to get it back to how I like it again. XD
If nothing else, hope this information helps someone else later on.
wigmuke said:
OMG I may've gotten it!
So I decided to give things another go with attempting to revert to stock again, as at this point, nothing is going to work other than via HBOOT.
I completed another reformat of the SD Card (Fat32) to be on the overcautious side and copied over ONLY the PB32IMG.zip file and restarted into HBOOT.
(Ah.. new user, so not allowed to post the link of where I got it.)
This time, much like before, it scanned, found the file, and did a parsing/loading. However, THIS TIME it actually prompted me to update! I chose yes (Vol+) and let it do its thing.
At this time, I am happy to announce that it actually is back up stock!
Wooohoo! Now to get it back to how I like it again. XD
If nothing else, hope this information helps someone else later on.
Click to expand...
Click to collapse
You might have lost root if you did the ruu from hboot. to check download the app "super user" from market that will tell you if you still have root or not.
Alright, now that I'm back to stock and runnin' smoothly, I need to figure out what route to take for rooting and flashing. Everyone talks about Unrevoked3, but I've heard there're other newer tools, too.
What would you recommend?
....also, sorry for the weird delay/disjointed/incomplete responses. I keep forgetting that XDA severely limits my posting capabilities. I wanted to say super thanks wolf, for all your help and sticking with me! Your input is appreciated. And yes, I'm pretty sure I lost all root, etc. It is back to "out-of-the-box" stock as far as I can tell.
wigmuke said:
Alright, now that I'm back to stock and runnin' smoothly, I need to figure out what route to take for rooting and flashing. Everyone talks about Unrevoked3, but I've heard there're other newer tools, too.
What would you all recommend?
Click to expand...
Click to collapse
unrevoked3 is the easiest way. but you will need to downgrade to android 2.2 for the security exploit.
http://forum.xda-developers.com/showthread.php?t=1306400
Edit: fixed link
---------- Post added at 10:44 AM ---------- Previous post was at 10:35 AM ----------
wigmuke said:
....also, sorry for the weird delay/disjointed/incomplete responses. I keep forgetting that XDA severely limits my posting capabilities. I wanted to say super thanks wolf, for all your help and sticking with me! Your input is appreciated. And yes, I'm pretty sure I lost all root, etc. It is back to "out-of-the-box" stock as far as I can tell.
Click to expand...
Click to collapse
lol now worries. easiest way to get to the 10 limit is just pad the count in here. ie just say something 10 times and you are good to go.
synisterwolf said:
unrevoked3 is the easiest way. but you will need to downgrade to android 2.2 for the security exploit.
http://forum.xda-developers.com/showthread.php?t=1306400
Edit: fixed link
Click to expand...
Click to collapse
Good news, I'm on 2.2 stock right now (just checked to confirm). So should be able to just go ahead and run Unrevoked3 then.
Also, the most popular recovery I'm aware of is ClockworkMod Recovery. I found that it's up to version 5.0.2.0. Would you recommend anything else or know of a newer version?
Figure if I'm going to do this, might as well do it right.
wigmuke said:
Good news, I'm on 2.2 stock right now (just checked to confirm). So should be able to just go ahead and run Unrevoked3 then.
Also, the most popular recovery I'm aware of is ClockworkMod Recovery. I found that it's up to version 5.0.2.0. Would you recommend anything else or know of a newer version?
Figure if I'm going to do this, might as well do it right.
Click to expand...
Click to collapse
Nope I'm RunNing that one and it works well.
Sent from my sexy assistant. (AMOLED HTC Incredible)
I have looked around and am still not sure which way would be best to un-root my Evo 4g. Can I just use ( wipe data/factory reset ) then update my contacts thru asurion ? and reload the apps i want from the market ? right now i am in ClockworkMod Recovery v3.0.05 ( it was originally rooted with unrevoked ) not unrevoked forever. I thought i would like to try the latest official build for a while. ( not looking forward to the sprint bloatware ) or would the easiest thing be to try and update to the latest ClockworkMod or some other build. Thanks for any info you might have.
Best way to unroot is to grab the unrevoked s-on tool. Flash that and run a ruu or grab a stock non rooted rom.
Sent from my PC36100 using xda premium
so i guess wipe data is really no good ?
Can I just use ( wipe data/factory reset ) then update my contacts thru asurion ?
Click to expand...
Click to collapse
Not really sure what you are asking here. A factory reset will NOT unroot you, it will just reset whatever rom you are on. And updating contacts through Asurion? Asurion is your insurance provider, they have nothing to do with contacts....
I thought i would like to try the latest official build for a while.
Click to expand...
Click to collapse
You don't have to unroot to do this, just flash a rooted stock rom. This way you stay rooted. If you unroot, and then update to the latest stock rom, it will be VERY difficult to re-root.
or would the easiest thing be to try and update to the latest ClockworkMod or some other build.
Click to expand...
Click to collapse
I think you need to read a LOT more about rooting before you proceed to do any more, you don't really seem to know what's going on. ClockworkMod is your recovery, which has nothing to do with your rom. Updating Clockwork will not update your rom, or unroot you.
LOL I guess you are right. A LOT more reading in my future.. Thanks though.
I guess I will go ahead with the idea to update to the newest rom. I thought because ClockworkMod gave me the option to " wipe data/factory reset. " it would set it to factory default, which I thought might be un-rooted.
Side note: Asurion also syncs my phone contacts. I had to use it once when my phone was lost. to update / sync the new phone. It worked very well. Google sync stopped working long ago. I get an error message every time.
But thanks again. that post was very helpful to point me in the right direction. and make me feel a little foolish LOL BE WELL
DGXYZ said:
Google sync stopped working long ago. I get an error message every time.
Click to expand...
Click to collapse
did you try setting up a new gmail account? or maybe jsut delete it on your phone and re-set it up.
not yet. but i will soon. ill let you know how it goes. I've read that it works for some and not for others. haven't found a lot of info directly from Google though. it seems they don't acknowledge the issue. but I am sure i'm not the only one experiencing the error message.
If you really like the new sprint os but hate the bloatware, why not use a rooted sprint rom that one of the devs has made, kind of exactly what sprint/htc gives you but minus the bloat!
Thanks I will. i'm very new to this, how do i go about getting the correct one ? as you can see from above. I have Alot more reading to do.
just did a search on the rom you are running. How do you like that one.
The Rom I am running is great! Just can't post the link to it in this forum due to forum rules. But the Rom I am running is similar to a stock rom, just not a stock rom of an evo 4g. It's ics os which stands for (ice cream sandwich) the new HTC os. Its the stock upgrade for most of their new phones such as the Samsung Galaxy SII. Evo 4g was left out, but due to the devs on this site and others the evo 4g will be just fine!
Edit: Well there is alot of reading and research involved. But for me the best kind of research is trial and error. I read up on certain roms that interest me that have key perks. Such as ICS (newer roms), or wimax enabled (4g enabled and typically on the older roms). Then I read up on peoples response to the roms, what issues they have had, how they have fixed them, how the developer has fixed them. And then after that I'll flash the roms and see how they run. Usually a day or two of use can tell you if you like it or not. Its like a car test drive!
That's Great. I will look around a little more. and get a new rom, I'll probably try the one you mentioned, ( found the link ) Hey, I really appreciate the info, I just need the time to screw around a little more. LOL. Be Well. I'll let ya know how it goes. It is pretty interesting.
Yes on the site you are currently on, there should be a few helpful tips on how to flash the roms and kernels properly. Good luck, also a bunch of great tips on the CM7 Wiki
Sorry for putting this here, but do not have enough posts to reply to the official thread over in development forum.
I did a clean install of TOB after rerooting, getting S-off and downgrading to froyo then upgrading it back to gingerbread while retaining S-off. Seems I had to get S-off for custom roms to work correctly when verizon sent me a new phone due to the 2am loop boot happening every night for a week even doing a full wipe/factory reset.(they know it is a known issue and sent me a new phone as mine wouldnt stop looping. I installed the last RUU available to take it back to stock and it still did it.
Walked in the bedroom this morning and the softkeys lights were on, figured I had gotten a notification or update or something. Watched it for a few, when it went to the TOB boot animation. would get loaded to home screen, then the loading animation would start again, happened continuously over a 30 minute time frame before I finally pulled the battery to get it to stop. tried to use the phone as it loaded and it started to do it again. Going to attempt to get into recovery and fix permissions, format data/cache, and see if that fixes it.
Anyone else having that problem?
Also are there any mods like the older stock+ that wont show the darned nag screen about there being an update available?
Thank you in advance for any advice/help.
devnulled
Also wanted to ask if the verizaon backup assistant is/can be fixed? it FC's whenever I try to load it. When I try to sync contacts on the VZW website I get a few texts with junk characters but no more contacts. Already did a fix permissions in CWM recovery, and through CWM itself. Thanks again for your help. Will update if anything Ive done fixes the problems.
Devnulled
devnulled said:
Sorry for putting this here, but do not have enough posts to reply to the official thread over in development forum.
I did a clean install of TOB after rerooting, getting S-off and downgrading to froyo then upgrading it back to gingerbread while retaining S-off. Seems I had to get S-off for custom roms to work correctly when verizon sent me a new phone due to the 2am loop boot happening every night for a week even doing a full wipe/factory reset.(they know it is a known issue and sent me a new phone as mine wouldnt stop looping. I installed the last RUU available to take it back to stock and it still did it.
Walked in the bedroom this morning and the softkeys lights were on, figured I had gotten a notification or update or something. Watched it for a few, when it went to the TOB boot animation. would get loaded to home screen, then the loading animation would start again, happened continuously over a 30 minute time frame before I finally pulled the battery to get it to stop. tried to use the phone as it loaded and it started to do it again. Going to attempt to get into recovery and fix permissions, format data/cache, and see if that fixes it.
Anyone else having that problem?
Also are there any mods like the older stock+ that wont show the darned nag screen about there being an update available?
Thank you in advance for any advice/help.
devnulled
Click to expand...
Click to collapse
The 2am reboots are not a phone issue, it is a known issue with the latest ota. I cant believe they would rather give you a new phone than to admit they sent out a messed up ota.
Try fixing permissions and wiping data as you said.
If 2.2 is installed you should not get a nag to update, as its based on the latest ota.
devnulled said:
Also wanted to ask if the verizaon backup assistant is/can be fixed? it FC's whenever I try to load it. When I try to sync contacts on the VZW website I get a few texts with junk characters but no more contacts. Already did a fix permissions in CWM recovery, and through CWM itself. Thanks again for your help. Will update if anything Ive done fixes the problems.
Devnulled
Click to expand...
Click to collapse
Vzw backup was removed from the rom as most people dont use it. If you want it back, flash this http://dinc.does-it.net/APKs/VZW_Backup.zip, thru recovery.
Thank you cmlusco,
clearing cache and fixing permissions has fixed it, sorry for saying there was a problem. Verizon almost got back 3 phones (an eris that i was given, my old palm pre plus, and my incredible) at the same time with a certified letter having me cancel my contract 6 months early when the phone started rebooting back around the 4th of july. They replaced it last summer/fall when they rolled out gingerbread and my phone got half of it installed when it locked up and would not finish the update but was enough there to lock it from being fixed by ruu even.
I agree that it was not the phone, I told tech support I had it rooted for different skins and roms and to fix buggy software and they suddenly wanted to send out a new phone under warranty. I think they just wanted to get out a phone that was a little harder to root and get s-off rather than fix what was obviously a software bug issue. the new phone was supposed to be fully updated, but it wasnt installed, was still on the prior OTA and had a helluva time getting it to accept a custom recovery to begin with. Would goto the white HTC screen, then flash once or twice and go black with white bars down each side. took 3x to get it to accept it and ended up having to flash an older version first .92 i think (was 3 weeks ago now).
I will flash the backup software this time as my contacts were all edited on the website. Thank you again for the best rom Ive played with in a long time.
(forgot to add when I asked about the mods, I meant in a stock rooted rom that was similar to the old stock+ in use/appearance, but didnt get a nag screen, not that touch of blue did not have it. sorry for the confusion)
devnulled
Apologies for resurrecting an old thread, but I'm experiencing this issue too.
Getting overnight boot loops on Touch Of Blue 2.2.
I can temporarily fix it by booting to recovery, then wiping cache and dalvik cache.
Unfortunately, this is a daily ritual since updating from Stock+
I wiped our phones per rom install instructions ("Wipe dalvik-cache and format everything in the mounts and storage menu except emmc and sdcard before flashing."), so I'm not sure what's going on.
Seems to correlate with any 'pushed' updates from the Google Play store, but that's just my personal observation...
Any new developments (or permanent resolutions) on this issue since it was reported before?
dibmem said:
Apologies for resurrecting an old thread, but I'm experiencing this issue too.
Getting overnight boot loops on Touch Of Blue 2.2.
I can temporarily fix it by booting to recovery, then wiping cache and dalvik cache.
Unfortunately, this is a daily ritual since updating from Stock+
I wiped our phones per rom install instructions ("Wipe dalvik-cache and format everything in the mounts and storage menu except emmc and sdcard before flashing."), so I'm not sure what's going on.
Seems to correlate with any 'pushed' updates from the Google Play store, but that's just my personal observation...
Any new developments (or permanent resolutions) on this issue since it was reported before?
Click to expand...
Click to collapse
No i looked into it, but couldnt figure out what was causing it. Tob is my daily driver and for some reason i have never gotten these reboots. It must have to do with a stock app that i have removed or something. Mabey gmail, i always remove that as i use maildroid. Wish i could be more help, i will install fresh and not remove anythimg and see if i get the reboots. Then it will be easier for me to trouble shoot.
cmlusco said:
No i looked into it, but couldnt figure out what was causing it. Tob is my daily driver and for some reason i have never gotten these reboots. It must have to do with a stock app that i have removed or something. Mabey gmail, i always remove that as i use maildroid. Wish i could be more help, i will install fresh and not remove anythimg and see if i get the reboots. Then it will be easier for me to trouble shoot.
Click to expand...
Click to collapse
Thanks for the reply... I wonder what's doing the damage - The dedicated Gmail isn't on my phone. My wife is running TOB as well with the same symptoms. She runs a lot more apps than I do and we were looking for the ext4 fix when I found TOB.
Maybe it's another app? Let me know if you want a list...
Planning to load your rooted stock this weekend and see how things go.
If, in the meantime, you need a guinea pig for any possible fixes, let me know - I don't mind installing stuff via recovery. I'm a little rusty on adb, but I could do that as well.
dibmem said:
Thanks for the reply! I saw your rooted stock build - Most likely will go with that.
I wonder what's doing the damage - I could pull Gmail off for the evening and see if mine is stable. My wife is running TOB as well with the same symptoms. We were looking for the ext4 fix when I found TOB.
If pulling Gmail doesn't work - I'll load your rooted stock and see how things go.
If you need a guinea pig for any possible fixes, let me know - I don't mind installing stuff via recovery. I'm a little rusty on adb, but I could do that as well.
Click to expand...
Click to collapse
You can just flash back to tob 1.3. Same thing just not based on 4.08.605.15. Still has all the same features and look.
cmlusco said:
You can just flash back to tob 1.3. Same thing just not based on 4.08.605.15. Still has all the same features and look.
Click to expand...
Click to collapse
Can I flash that build directly over 2.2 or do I need to do a full wipe beforehand?
dibmem said:
Can I flash that build directly over 2.2 or do I need to do a full wipe beforehand?
Click to expand...
Click to collapse
Just wipe dalvik-cache and the cache partition and flash over. I have done it before and had no issues. That being said, if stuff starts acting goofy you may need to wipe and flash from scratch.
cmlusco said:
Just wipe dalvik-cache and the cache partition and flash over. I have done it before and had no issues. That being said, if stuff starts acting goofy you may need to wipe and flash from scratch.
Click to expand...
Click to collapse
Loaded 1.3 per your instructions. Also flashed the stop OTA and stock unlock patches. All is well this morning. No symptoms of a reboot present.
Observations: I noticed when I updated my phone, upon reboot, it wanted to immediately update various software in Google Play.
Perhaps the whole lockup / reboot issue is directly related to how the market pulls down updates(?)... On 2.2, I was doing a morning ritual: I would install market app updates, boot to recovery and do the following: Wipe cache, then dalvik cache. (Last couple of days, I ran 'fix permissions' as well). The process, albeit slightly tedious, worked with varying success - yesterday, it took a few TOB boot screen boots before the phones were stable (wife and mine).
Today, all seems to be fine. After installing 1.3, I did all my updates last night - nothing new pulled down in the market for me.
My wife's phone had one pending update that I left to see if the phone was stable overnight - Still there this morning. So, no 2 am reboot.
Hope this helps with development in some way.
Thanks much for your help and input - I'll keep an eye out for a future build of TOB for problem child phones.
---------- Post added at 05:03 AM ---------- Previous post was at 04:48 AM ----------
cmlusco said:
Just wipe dalvik-cache and the cache partition and flash over. I have done it before and had no issues. That being said, if stuff starts acting goofy you may need to wipe and flash from scratch.
Click to expand...
Click to collapse
Any pointers on upgrading the radio? Currently on 2.15.00.07.28
(Not in a rush - I see there's a few warnings on bricking your phone - unfounded or true?)
dibmem said:
Loaded 1.3 per your instructions. Also flashed the stop OTA and stock unlock patches. All is well this morning. No symptoms of a reboot present.
Observations: I noticed when I updated my phone, upon reboot, it wanted to immediately update various software in Google Play.
Perhaps the whole lockup / reboot issue is directly related to how the market pulls down updates(?)... On 2.2, I was doing a morning ritual: I would install market app updates, boot to recovery and do the following: Wipe cache, then dalvik cache. (Last couple of days, I ran 'fix permissions' as well). The process, albeit slightly tedious, worked with varying success - yesterday, it took a few TOB boot screen boots before the phones were stable (wife and mine).
Today, all seems to be fine. After installing 1.3, I did all my updates last night - nothing new pulled down in the market for me.
My wife's phone had one pending update that I left to see if the phone was stable overnight - Still there this morning. So, no 2 am reboot.
Hope this helps with development in some way.
Thanks much for your help and input - I'll keep an eye out for a future build of TOB for problem child phones.
---------- Post added at 05:03 AM ---------- Previous post was at 04:48 AM ----------
Any pointers on upgrading the radio? Currently on 2.15.00.07.28
(Not in a rush - I see there's a few warnings on bricking your phone - unfounded or true?)
Click to expand...
Click to collapse
If your s-off you can flash just the radio thru hboot. If s-on you would have to do a whole ruu in order to upgrade it. A bad radio flash can brick a phone. That being said, i have done it many many times with no issues. Just make sure to verrify the md5 sum, and never interrupt or run out of juice while flashing.
cmlusco said:
If your s-off you can flash just the radio thru hboot. If s-on you would have to do a whole ruu in order to upgrade it. A bad radio flash can brick a phone. That being said, i have done it many many times with no issues. Just make sure to verrify the md5 sum, and never interrupt or run out of juice while flashing.
Click to expand...
Click to collapse
Results post: Ended up flashing TOB 1.3, radio 2.15.10.12.20, and CMW 5.0.2.0. Updating the radio via hboot ended up being very easy (as long as I verified md5 beforehand.) Our phones are stable overnight - no reboots. Signal sucks here at home, but seems to be slightly better - hopefully will be better around town. If not, there's plenty of other radio versions to try out.