Related
I have been using Rubix Focused 1.8.9 on my DX for a weeks or so and I was super happy with it. I have been getting a little ROM crazy though and had been reading up on Tranquility 3.5.1 and it seemed pretty cool so I decided to try it.
I think I messed something up in the install process because things were FCing left and right and it was just super laggy. So I decided to restore my nandroid backup that I had made right before installing Tranquility.
I was doing all this on a bus so I didn't realize that my batter was pretty low. Well halfway through my nandroid restore my batter died. Suffice it say that I was freaking out.
I got home and booted the phone and got the Tranqulity splash screen, followed by the Rubix splash screen. Then the phone booted up into Rubix exactly like it was in the backup.
I have no idea what is going on. I dont really mind the splash screens but I am afraid there may be some issues if there are files from both installs running at the same time.
Should I try restoring the backup again and let it go all the way through or do I have nothing to worry about?
Actually - and you can correct me if I am wrong - you got the tranquility boot logo and the rubix flash screen? If that is correct - you don't really need to worry about it. For whatever reason - the nandroid does not over write the boot logo.
I actually performed and sbf and when I rebooted my phone I still had my custom boot logo! It actually kind of bothered me. I thought the whole purpose of an sbf was to COMPLETELY restore your phone to its factory state.
So anyways - I wouldn't worry about it too much. I know it would drive me crazy to have the "wrong" boot logo. Here is a link to a thread with tons of boot logo's to choose from...
http://www.droidforums.net/forum/droid-x-hacks/91707-droid-x-custom-boot-logo-ill-create.html
good luck.
This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic
syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??
Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App
syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.
last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.
Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App
OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!
Self-dangerous noob here. NC 1.2, theoretically returned to stock
History:
Got NC 1.2
Rooted w/ManualNooter 4.5.25. Everything seemed to go great. So...
Downloaded, backed up, and flashed CM7 in ROM Manager
Wouldn't boot...hung on n COLOR screen
Same results w/ Phirerom (CM7 based - doh)
Able to restore MN4.5.25 from CWM - BUT noticed "Error formatting /data!" during nandroid restore. Didn't seem to matter...restore successful
Get "Error formatting /data!" no matter what
Able to boot into CM7 from SD, but it has "problems". For instance, there are no "back" or "return" softkeys. So there is no way to navigate around any app! Only the hard "n" home key works
Reflashed stock 1.2
Seemed to work, began to ask me to reregister. BUT, it won't display the keyboard, so I'm stuck at the "Login with your existing B&N...." screen! Keyboard flashes up and then immediately disappears!
As an noob, it occurs to me that all my problems are related to my inability to format the /data partition (if it's even called a partition).
Can any of you awesome people help me? And, if I'm in the wrong forum, any directions would also help. Thanks.
Same error here
If anyone can help with this it would be much appreciated.
have you tried removing CWR then do the 8-boot reset?
No, every time I've done it, it boots into CWR. Maybe REMOVING it will help. lol. Sorry to be so inept. I can flash the 1.2 stock that will remove CWR. Is that the way to do it?
Worked like a charm
Removing CWR and 8-boot-interrupts did the trick. I'm now back to a fully stock NC 1.2.0. Ready to roll up my sleeves and re-brick!
This is the most amazing community. The closest thing I have to any technical knowledge is speaking a little Klingon. VERY little. But, I have learned more here by reading these threads for a couple hours...OK, several hours... than my wife has learned in a dozen trips to the apple store. I feel more empowered every day. You are all great. Can't thank you enough.
Goldie, I wasted a bunch of time on this last night. I'm guessing you have a new nook. If you do, slap cwr on your SD (3.0.2.8 or something) and look for the thread that tells you how to repartition your nook. Follow instructions to set it to the old way. After that run manualroot zip through cwr. Reboot to cwr and wipe data, system, cache. Finally install your rom of choice from your SD card through cwr. That's what I did to finally get it to work.
Thanks. I'll give this a try. As you probably guessed, I DO have a new NC, and while I was able to get it back to 100% stock, and easily reregister it, I had the same results. The ONLY way I can get CM7 running is off the SD card. So, I'll try the partitioning trick. Why do I get the feeling this is going to work? Unfortunately, I'm not on dev's time... I'm at work by 7:30am EDT, but in bed pretty early. I REALLY appreciate the response. Later this week I'll install SDK, and all my tools at home so I'll be able to stay up all night with you awesome folks.
still looking for the thread on re-partitioning. I found the thread on restoring, but I get the error every time I try to reformat the /data.
No luck. I can restore to stock 1.2, reregister, and MN 4.5.25, all easily. BUT, once I flash CM7 (or Phiremod 6.3, etc.) it hangs at the "n C O L O R" screen (C O L O R flashing at various speeds just to fool you into thinking it's actually going to work). Here's what I've noticed...after flashing CM7, the ADOBE screen no longer flashes up at boot. Once it fails to boot the Adobe software, it won't boot at all. So, for now, I guess I'm running CM off my SD unless anyone can suggest anything.
Goldie u have to repartition to get it working. Ill go look for the thread. Also maybe you should try out the cm7 mod over the phiremod Tom. I'm on phiremod now and the lag is killing me
Wow that was painful to find. Needs a sticky.
http://forum.xda-developers.com/showthread.php?t=1094371
Edit: I take that back about the lag, set your cpu to 1200 in the ROM and change yourgovernator to interactive for an amazingly smooth experience
I've been going nuts trying to figure this out. I too ran into the "error format /data" message but I powered through it only to end up at at the Android logo--nothing. Out of frustration, I returned to CWR and wiped everything--like on my Evo (did not go through to mounts option). That seemed to go through /data but I don't know the difference between a wipe and a format (I'm looking...). Still got bootloops. I tried to return to stock but the 8 interrupts wouldn't work.
Pressing START and N worked though and that got through to CM7 and it's working great now but I'm afraid to do anything else because I still get the "error formatting /data" message.
I've heard horror stories (bricking beyond repair--if that's possible) of users repartitioning their drives though so... I hope there's another solution out there.
I love this community!!
Sys:
Thanks a million!! Everything perfect!! I just can't say enough about this awesome community, all the amazing devs.
heh you're more than welcome . i hope this helps anyone else that stumbles on your thread as well. Ive been having fun with my nook but i think its time to trade it out for something a little bigger. Maybe ill just wait till att gets its flavor of gs2 idk. So many choices out there!
thanks guys!
i just had the same problem and falshes all kinds
of zips until i found this post.now i've launched cm with status bar
really really thanks
this worked great for me too! i had a nookcolor bought in december and it had a messed up chargerand 6 really bright white spots that were really noticiable. went to b&n store and the guy just gave me a new one. it came with 1.2 and i had the cwm sd from the old one. so tried restoring my cm7 backup from the old one and error formatting data came up. flashed this zip, and im wondering, since these are too different nookcolors, should i restore the cm7 backup or flash it brand new. because i had a ton of stuff on the old one and i dont want to lose it. so can i ust do advanced restore and restore data, or can i restore the whole thing or just flash and slowly get my stuff back?
update cwm
ok not sure if you fixed it or not yet, but i had the same problem for awhile too until i found a post
your probably using cwm 3.0.0.28 just updated it to 3.2.0.1
bl3achcrazy said:
ok not sure if you fixed it or not yet, but i had the same problem for awhile too until i found a post
your probably using cwm 3.0.0.28 just updated it to 3.2.0.1
Click to expand...
Click to collapse
i have tried 3.2.0.1 but get same error message
3.2.0.1 on the bootable card or already on the eMMC? It has to be on the bootable card.
Thanks
It works after getting my nook color around 2pm today and taking it home. I was working on this thing all day I tried several ways and this one worked!!! Having issues with wifi that's all
So I was trying to go from comrom to OMFGB nightlies, and didn't know you have to go to OMBG first. When I tried to do that. I odined the ED05 modem, then flashed OMFGB, then the GAPPS. It wouldn't work, and then I read I had to flash a new kernel, so I flashed the Glitch high leakage. Then it started to work, but after it went to the boot screen, it went to a new CMW, blue, and tried to install GAPPS? I think that's what it was doing, but it went really quickly, and said something like it couldn't mount the sd card, which is weird. So I took out the sd card, and it said waiting for mount, or something similar. I put it back in, but it wouldn't work. So then, I flashed back to UKB with the pb&j kernel, to see if I could get things going from there. It booted fine, but when I tried to just flash OMFGB, it would go to the boot screen, and then go back to CWM. So I tried to go back to UKB, and then it did the same thing, didn't change the boot screen at all (so now it's stuck with Galaxy S Cyanogen mod boot screen). I tried to flash OMBG then, but it was still going back to CWM. I'm thinking about odining the eclair package, and then trying from there. What do you think. Oh and usually I go to android central, but they don't have OMFGB nightlies there, so here I am.
TL;DR: I flashed a bunch of GB stuff in what I assume to be in the wrong order, now I'm stuff. Help me?
EDIT:After flashing a bunch of stuff, I don't remeber what or what order, just that the Glitch was last, I managed to get it to boot, first with a glitch boot screen, then the android boot screen. I'm not sure what I'm on, I think it is OMGB, at least that is what the widget says when I booted it up. I'm really confused. Anyways, I think I got it.
EDIT2:Nope, stuck at the boot to CWM loop. I'm going to try to go back to UKB (froyo) through that sticky in dev
EDIT3:Well I'm waiting for it to download, so what I did that worked was flash OFGB in red CWM, weird, but it worked. I'm leaving it at that for now, cause nobody is replying.
While I'm glad you got things to work, you should probably start from scratch if things start to get weird again. I highly recommend this thread as the proper way to go from CM7/MIUI/OMFGB back to stock, and from there back to whatever you want: http://forum.xda-developers.com/showthread.php?t=1124391
Remember that when you flash stock DL09 or EB01 or ED05, you also have to have the atlas 2.2 pit file and "repartition" checked in ODIN.
Finally, while you still have things working, I recommend you do a nandroid backup. If you need to go all the way back to stock before coming back to gingerbread, you can do an Advanced Restore > Data Restore in order to get your apps and such back pretty painlessly.
Yeah thanks, that's the sticky I was talking about. I didn't know about the re-partition button having to be checked, thanks for that And the Data restore is through CWM? I assume so. And for that, I just need a regular nandroid backup?
Yes, in CWM you can choose backup and restore, and then do a system backup.
When you want to go back to a given setup (i.e. your apps, widgets, etc.) you can do an advanced restore where you choose to restore just data, and not the whole nandroid system backup.
That's pretty cool, I never new about that. So I tried the *228 1 and 2 thing, cause I couldn't download the beta swype, and I thought it I needed too, but it said my phone couldn't be activated, and to try again, then the I lost all signal. I rebooted, and it came back, but I couldn't activate it again. It's being weird still, and in the morning, I'm starting over like you suggested. I'm still receiving calls though, and I get good connection. For the morning, I was wondering if I could just check to see if I have everything I need. I have:
CI500_VZW_ED05_FROYO_REL.tar.md5 from the thread you posted for odin
OMGB 1.2.0
OMFGB nightly build 7/21
Glitch High leakage v11.1
The CWM for all roms (red)
lithid gapps (unless you think the other gapps is good)
and I think that is it. I don't have the atlas 2.2 pit file, can I just search here for that? Thanks for all the help
EDIT:Found the atlas 2.2, and I use that at the same time as the md5 file, right?
EDIT2:Okay, I tried to do a nandroid backup, but with the CWM recovery 4.0.1.0 (I think that's what it is), it didn't show anything, like it said backing up system, then it didn't show what part it was backing up, and the status bar stayed blank, then it moved on to data after a while, and that. It said it failed to back up sd-ext, which I'm guessing is why it wasn't working properly. I'm doing the odin restore to froyo, and if someone could tell me the correct order to install/flash/odin stuff to get to the OMFGB nightlies, that would be amazing!
EDIT3:I think I did it right. Odined to froyo, Odined the ED05 modem, Odined the CWM for CM7, flashed CM7, Rebooted, Flashed Glitch Kernel, then Flashed OMFGB nightly build 7/23. I still need to do gapps though.
EDIT4:I did gapps, and almost everything looks good. I can't activate my phone through *228 1, and when I try to set up my google account, it says it couldn't establish a reliable connection to the servers. And After I call to activate my phone, my service goes dead. I can still text and receive calls though
EDIT5:man, a lot of editing. I flashed OMGB 1.2.0 on top, and now I can set up my google account. Still not activating though :/
Unrelated question, how come sometimes my wifi and signal bars are grey, sometimes blue (I'm using cyanbread)? I think when they are grey, I'm not using signal? How do I make them blue?
Alrigt, I randomly get reboots and I just rooted using Revolutionary last night. I'm using TWRP as my recovery and I want feedback as to if this is a normal issue or if it's just my handset. I hate sense and want rid of this garbage. >=( I appreciate all feedback, just don't be a jerk about it. I'm not new, and this isn't a noob question. I'm asking specifically about Revolutionary root with twrp then flashing CM7 as the rom and if it has bootlooping issues coming from stock.
I haven't tried TWRP, but you might want to try the usual recoveries, and try wiping everything once and and a fresh install. Just a thought. I have never had issues with any cyanogenmod. Oh another thing, might want to partition your SD card.
It's stuck in a bootloop right now. I actually already tried CWM and just did Amon_ra's recovery...it seems to be a CM7 issue with my phone? I'll try MIUI and then switch to CM7
So, you're afraid to ask for getting shot down.
I'm afraid to post an idea for getting shot down. But, I'll venture forth and probably be wrong. Do you still have PC136.img on your SD? If so, I think you're supposed to remove it. I could be wrong and probably am. I'm 70% sure I'll hear about it if so.
MIUI was bootlooping as well. I think this might be an issue with me flashing my splash screen after acquiring root?
Common issue: make sure you are wiping the SYSTEM partition. The "factory reset" wipe option does not do this. Or find one of those automated "super wipe" scripts to flash in recovery that does it all for you.
Others had bootloops and such and later posted back that it was a wipe issue.
Also, provide a logcat if you can.
Actually, I found that I had to wipe the boot partition for some reason. It worked and I hope this thread helps people get past boot loops. I also need to restore my Wimax keys now lol.