Related
Hey, question. Every single CM from 6.0 I have downloaded I have had issues with. I love the rom, but every time I get the same issue. When I install the rom all worked fine. I wipe all data, clear cache, and have to reinstall of course everything, my issue is that my phone will randomly freeze. Sometimes I get an error message saying the process process.android has failed, other times it just freezes. Does anybody have any ideas?
I loved CM 6.1 best Rom I've had yet. But after a week it started acting up and having problematic auto shutdowns like 8 times a day. I then searched for another stock Rom and tried skyraider vanilla, I hate it. It's basically skinned sense. That's it. I enjoy sense but it eats battery. My favorite roms so far are the desire Hd Rom and
CM but without the shutdowns is be perfect.
Sent from my ADR6300 using XDA App
only people
So this is the only other person I have run into with this problem. Everybody else I have talked to over other forums or IRC has never heard of these issues at all.
The only time I've ever had those shut down issues is when I start screwing with themes or when I start screwing with kernels or overclocking. I'm not sure what you've got going on there though
Well...
Well I have done some of that however I have reverted to "stock" several times. I have Hboot .92 installed also, i saw something online. The latest radio is also installed. I guess has anybody else seen any issues like this?
Try formatting the system in addition to wiping. CM does not format anything when you flash it. In CWM its under mount sd section.
Sent from my Htc Incredible using XDA App
This happened to me today, I am 99% sure it was the kernel I had installed though. I put back invisiblek's #18 and had no problems before or after.
okay I can mess around with that and see what happens then.
justinmburrous said:
okay I can mess around with that and see what happens then.
Click to expand...
Click to collapse
Let us know please.
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
You need to be a little more specific but do this.
1. Click on the Cyanogen link in my signature and download it.
2. Download google apps
3. Reboot into recovery
4. Wipe Data/Factory Reset
5. Wipe Cache Partition
6. Wipe Dalvik Cache
7. Select install zip from SD card and choose the cyanogen ROM, let it install
8. Select install zip from SD card again and choose the google apps.
9. Reboot your phone and sign into your google account and let everything sync
This is the best way to do it. Not through ROM Manager.
If this doesn't work then I have absolutely no idea. That is the 100% correct way to flash a ROM.
neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
I had to revert back to #18 kernel working fine now!
neur0tk said:
I had to revert back to #18 kernel working fine now!
Click to expand...
Click to collapse
Yeah I mentioned it earlier in this thread. For some reason #21 and #22 do not like cyanogen.
I'm running #21 on my phone and I haven't had any issues yet.
Yeah IDK either... I had to revert now it's running like a champ! love the Inexus theme!
ok an update, I have everything working. I an using cm6.1, latest radio (on cm site), kernel 27, hoot .92, and the very latest clockwork that just came out. I know those last two should not matter, just letting you know. As of right now my phone is not freezing and everything works fine, even faster than before. When I first turned it on the phone did freezer and after that yet took a long time for 3g to start working. On reinstall I did a total revert to stock then did a factory reset and cleared all caches and everything on the phone there is to clear. It has been afew hours. I will update this if there are any more problems
Sent from my ADR6300 using Tapatalk
Keeps rebooting more and more time to switch roms
Justinmburrous
Justinmburrous.com
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!
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.
I have tried to install, following instruction on this site to install ROM's. I have tried Starburst and Task650. I currently have the OTA Touchwiz installed from Samsung, and Pershoot kernel 2.6.34-4-cyanogenmod installed. Every time I try it goes through the process and successfully I reboot, it boots to the Samsung Logo (Start) and I wait like 20 minutes and it does nothing, just stay at the start Samsung logo. I have done this several times on each ROM, always having to go back to a backup I did. What am I doing wrong? Why can’t I install any ROMs? I would greatly appreciate some expert advice, because I hear so many great things about Task650 I really want to give it a shot. I am an ex-iPad owner, gave to daughter as a friend had one and let me use it; feel in love with it the moment I picked it up. I have also searched the forums, but I am doing everything to the T as outlined in instructions. Had my tab for a week, it isn’t a 10.1v or I/O series. Thanks everyone in advance for helping a complete noob when it comes to android.
Sounds like a case of missing to clear the cache.
Did you wipe the cache partition and dalvic cache in the recovery menu?
After making major changes like switching between roms or kernels thats recommended and if not done might cause such an issue.
I did
I did do those steps, did the factory wipe/reset, wiped cache, wiped dalvic. Once I did those 3 steps, installed from zip, goes through the steps successfully, but when I reboot it just stay on logo. I read, it could take 5-10 min, but I have waited up to 20 and it doesn't move past that. Just see what I am doing wrong, as the 2 roms have both done that, and I have tried several times with both. Just have the stock rom with Touchwiz OTA upgrade from Samsung, and pershoots latest kernel. Thanks in advance.
bad zip file?
Is it possible the zip files are getting corrupt? Are you downloading them on your tab or on computer and transferring them over? I would also check to see if there are any errors when you flash.
Download from computer and transfer over. How can I if there are errors as once I install a ROM it just stays at the logo. After it starts to install it end with, i cant recall exactly, but it says success. Thanks in advance
In cwm when you flash there is some text readout. That is where some error messages could be seen. That text will be there before you choose reboot on the menu.
sounds like you've had some issues bro. if you do get fed up and need some help, just let me know and we can video chat through gmail or skype to get you through it and get you a custom rom.
slice2011 said:
I have tried to install, following instruction on this site to install ROM's. I have tried Starburst and Task650. I currently have the OTA Touchwiz installed from Samsung, and Pershoot kernel 2.6.34-4-cyanogenmod installed. Every time I try it goes through the process and successfully I reboot, it boots to the Samsung Logo (Start) and I wait like 20 minutes and it does nothing, just stay at the start Samsung logo. I have done this several times on each ROM, always having to go back to a backup I did. What am I doing wrong? Why can’t I install any ROMs? I would greatly appreciate some expert advice, because I hear so many great things about Task650 I really want to give it a shot. I am an ex-iPad owner, gave to daughter as a friend had one and let me use it; feel in love with it the moment I picked it up. I have also searched the forums, but I am doing everything to the T as outlined in instructions. Had my tab for a week, it isn’t a 10.1v or I/O series. Thanks everyone in advance for helping a complete noob when it comes to android.
Click to expand...
Click to collapse
Well first...are you rooted? Do you have Clockworkmod, Superuser, and Busybox?
Oh and congrats on your switch from Apple to Android
slice2011 said:
I have tried to install, following instruction on this site to install ROM's. I have tried Starburst and Task650. I currently have the OTA Touchwiz installed from Samsung, and Pershoot kernel 2.6.34-4-cyanogenmod installed. Every time I try it goes through the process and successfully I reboot, it boots to the Samsung Logo (Start) and I wait like 20 minutes and it does nothing, just stay at the start Samsung logo. I have done this several times on each ROM, always having to go back to a backup I did. What am I doing wrong? Why can’t I install any ROMs? I would greatly appreciate some expert advice, because I hear so many great things about Task650 I really want to give it a shot. I am an ex-iPad owner, gave to daughter as a friend had one and let me use it; feel in love with it the moment I picked it up. I have also searched the forums, but I am doing everything to the T as outlined in instructions. Had my tab for a week, it isn’t a 10.1v or I/O series. Thanks everyone in advance for helping a complete noob when it comes to android.
Click to expand...
Click to collapse
Maybe try in "reverse" order
Flash kernel back to stock - flash the rom you want - if that works then flash pershoots kernel
Just a thought
hy
i installed the overcome rom on my 7500, and i'm so entusiast!
Try it it's very easy!
---------- Post added at 07:21 PM ---------- Previous post was at 07:16 PM ----------
i did it in recovery, do wipe data
Yes its is rooted, cmw, superuser, and busybox all installed. Installed both roms in recovery, hold volume down and power method. Just can't figure it out, I will do the reverse suggestion and report back later tonight or tomorrow.thanks everyone for the advice/help.
no erreor s after install, think task's says success or something to that effect.
Well it finally stuck, I knew it was going right as when it was installing system files, it took like 5 minutes, the other time I did it took like 30 seconds. As per Stinky73 went back to stock Kernel, and wipe data, clear cache partition, and wipe Dalvik Cache, Thanks a million Stinky73 u da man! HELL YEAH this Rock, it is so responsive, seems a hell of a lot smoother, and apps just snap open. Task you did one outstanding job. This is coming from a noob who has no idea how much work goes into these, I am sure a lot. So from a noob to an expert EXCELLENT JOB, love my Tab that much more!!!!! Thanks everyone for the help, I am one happy camper! Now another dilemma, I saw new versions: How do I install these now that I have Tasks650 installed and working? Do I have to do the same steps above, wipe data, cache, and Dalvik? And if so what do I do next, do I do the same: Also is the BOB_WOW_Fix installed using the same method as i read flashable, sorry for the noob question, just want to get it right.
1. install zip from sdcard.
2. choose zip from sdcard.
NEW!!!- Task650's V7.1
Once again... I forgot to add "Desktop UAstring to V7.1 so flash this update after you boot up V7.1 if you want it.
Can someone please give me the proper ateps on installing the bob_wow_fix, and the 2 7.1 updates? Thanks
slice2011 said:
Can someone please give me the proper ateps on installing the bob_wow_fix, and the 2 7.1 updates? Thanks
Click to expand...
Click to collapse
There's no complete fix for BoB and WoW, its a continuous work in progress.
bob wow fix
Are you taking about the fix task posted?
What I had to do was wipe cache first then flash the zip just like you did on the rom. And bobs your uncle.
Edit:
Oh ya I would reboot after each flash just to be sure.
So as you probably read had a hell of a time getting a rom installed, followed stink'ys advice and it worked. Installed 6.0, finally, than installed the 6.1 theme update, no issues. Than downloaded the 7.1, followed op. wiped dalvik, wiped cache, and wipe data/factory restore. No errors, but when I rebooted it got stuck once again on the Samsung logo with the Galaxy Tab 10.1 print. So i do not know what the heck I am doing wrong. I got 6.0 than 6.1 updated and now I am back to my initial problem with 7.1, no I didn't use the 7.1 update one. tried 3 times, and even downloaded the fiel again, and followed the same steps task outlined, and no go. Had to restore the 6.1 from back up.
slice2011 said:
So as you probably read had a hell of a time getting a rom installed, followed stink'ys advice and it worked. Installed 6.0, finally, than installed the 6.1 theme update, no issues. Than downloaded the 7.1, followed op. wiped dalvik, wiped cache, and wipe data/factory restore. No errors, but when I rebooted it got stuck once again on the Samsung logo with the Galaxy Tab 10.1 print. So i do not know what the heck I am doing wrong. I got 6.0 than 6.1 updated and now I am back to my initial problem with 7.1, no I didn't use the 7.1 update one. tried 3 times, and even downloaded the fiel again, and followed the same steps task outlined, and no go. Had to restore the 6.1 from back up.
Click to expand...
Click to collapse
All sounds very strange...is it definitely stuck on the boot screen? These things can take anything from 5-20 minutes on initial boot, there is no definite rule for that, seems to be device related in some strange way...how long have you left it?
I am really an OCD when it comes to upgrading and always backup (nandroid or whatever) then go back to the very start before trying something new...years of PC and Mac have taught me that even tho the manufacturers say you just apply upgrades on top of previous upgrades, sooner or later they will f**k up....
I wonder why you are passing thro all the steps you are...(going thro 6.0, 6.1 etc)
I would be inclined to try going back to stock....stock whatever it was rom when you got the tab (notice you've never stated what model you have), stock kernel, nothing installed....then go direct to Tasks 7.1 (everything needed in 6.x is incorporated in 7.1) .... then, if it boots and runs, add pershoots kernel...
What do you reckon Task?? Can you chip in on this one?
Cheers, Stinky
@ slice2011.....any news?
Drpbody said:
And bobs your uncle..
Click to expand...
Click to collapse
How'd you know Bob was my uncle?
Oh wait..everybody has an uncle bob somewhere
okay so yes...im a noob, or atleast i consider myself one. heres my problem, i jumped into rooting and flashing head first, without researching EVERYTHING, ENTIRELY, so im at fault, i know this guys.
so heres the just of it, i have the mt4g aka htc glacier. i wanted to root, and flash a custom rom. i have a thing for sense 3.0 so i flashed virtuous fusion, now i never checked or learned how to figure out if i have a bad emmc? i through caution to the wind and here i am with no phone.
okay so its installed everythings good no glitches running smooth. my girl downloads mad bull**** into the phone and it starts running SLOW, real slow. i think hmm, factory data reset? earse everything yes i know this is unrevesable. phone goes black. remove battery reinstall, turn on, myotuch 4g then htc sense boot screen, then boot loop, then boot loop, then blakc screen unresponsive until battery pull.
cleared cached partition, wiped dalvik cache tried reinstalling viruous fusion from zip, same problem, not sure where i saved my nadroid backup unable to find it
so basicly guys, without gettin chewed out, am i a total ****ing moron? and is there hope....
also i saw a simalr thread unanswered there was a suggerstion to instal some file with a random jumble of letters and numbers as the name, however idk how to do so without being able to access my sd card with the phone i dont have a spare phone or way to put sd card in laptop please help me someone
SOLVED, not sure how i fixed it but i think its because, i first deleted everything i could form clockwork, then went to advanced deleted cache system and something else reflashed now its working...no complaints, however i read on another forum that virtuous fusion is known for brick devices upon factory data resets
Virtuous Fusion is a very outdated ROM.
Use Virtuous Unity.
joeyydaprofitt said:
okay so yes...im a noob, or atleast i consider myself one. heres my problem, i jumped into rooting and flashing head first, without researching EVERYTHING, ENTIRELY, so im at fault, i know this guys.
so heres the just of it, i have the mt4g aka htc glacier. i wanted to root, and flash a custom rom. i have a thing for sense 3.0 so i flashed virtuous fusion, now i never checked or learned how to figure out if i have a bad emmc? i through caution to the wind and here i am with no phone.
okay so its installed everythings good no glitches running smooth. my girl downloads mad bull**** into the phone and it starts running SLOW, real slow. i think hmm, factory data reset? earse everything yes i know this is unrevesable. phone goes black. remove battery reinstall, turn on, myotuch 4g then htc sense boot screen, then boot loop, then boot loop, then blakc screen unresponsive until battery pull.
cleared cached partition, wiped dalvik cache tried reinstalling viruous fusion from zip, same problem, not sure where i saved my nadroid backup unable to find it
so basicly guys, without gettin chewed out, am i a total ****ing moron? and is there hope....
also i saw a simalr thread unanswered there was a suggerstion to instal some file with a random jumble of letters and numbers as the name, however idk how to do so without being able to access my sd card with the phone i dont have a spare phone or way to put sd card in laptop please help me someone
Click to expand...
Click to collapse
well there's a lesson learned...
never EVER do a factory reset within a ROM... lol
btw, when you went to recovery, did it show any errors?
like "E:/ Can't find ..."?