Related
Hi all,
this is the 3rd time this is happening to me with different ROMs. The problem is:
The phone boots up normal, I can swipe to unlock, enter my PIN, but after pressing OK it won't unlock the SIM. If I lock the screen it won't come back on. It stays black whatever I do. After some time the phone reboots (soft reboot) and everything starts from the beginning.
The first time this happened I was using Modacos Ir9. I had the phone switched off over night and switched it on. Only thing that seemed to help was completely unrooting the phone and rerooting it again.
The second time I was using codeworkx CM9 Builds and tried to update. I restored my nandroid, but it kept happening. Flashing the XXKK1 Radio did the trick here.
Now it is happening again. This time I installed dropbox and the phone froze on the setup wizard...
I don't want to unroot the phone, it takes forever to restore the SD card.
Any advice on this one?
Update:
- Flashed the following radio images without any success: XXKL1, KRKL1, UGKL1 and XXKK1
- Used my older nandroids from CM9 and Modaco Ir10. NOT WORKING
- Wiped every nandroid. NOT WORKING AT ALL
- Reflashed CM9 and Ir10. Still NOT WORKING
I'm so lost I'm going to revert to stock and unroot... and try how far I can throw an 1 month old GNx from the fourth story.
I don't know much on the development part so I don't know why its doing that I can only suggest using odin and going back to stock.
Sent from my Galaxy Nexus using xda premium
I had similar problems with mine once. Only thing that helped me out wasn't unrooting though. A complete factory reset was enough to make me go on again.
I posted a thread here then to ask people if anyone experianced the same but got no reaction what so ever zo I guess "we" are a dark minority.
I don't know what it caused it or what the solution might be but a Factory reset did it for me.
Good Luck!
C-4Nati said:
I don't know much on the development part so I don't know why its doing that I can only suggest using odin and going back to stock.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Last time it was working again after reverting to stock. But I bought it to use Custom Roms
I would say go back to stock w/ odin, Wipe everything and start again.
Diger36 said:
I had similar problems with mine once. Only thing that helped me out wasn't unrooting though. A complete factory reset was enough to make me go on again.
Click to expand...
Click to collapse
Factory Reset wasn't helping unfortunatly.
Flashed the original factory image through fastboot. Now everything is working again. I'm restoring my SD backup now and will try to get CM9 working again.
If it would keep failing in stock I could return the phone. Now I'm left with "hopefully it isn't happening a fourth time" and "My phone doesn't work I need 4 hours to get ich working"
the_alien said:
Factory Reset wasn't helping unfortunatly.
Flashed the original factory image through fastboot. Now everything is working again. I'm restoring my SD backup now and will try to get CM9 working again.
If it would keep failing in stock I could return the phone. Now I'm left with "hopefully it isn't happening a fourth time" and "My phone doesn't work I need 4 hours to get ich working"
Click to expand...
Click to collapse
Fastboot flash stock google images. And your phone isn't bricked. Stop using the term wrong. It's most likely a software issue or you're doing the rom flash procedure incorrectly.
A bricked phone is a phone that is unaw to go into bootloader and recovery mode and cannot start android.
Sent from my Galaxy Nexus using xda premium
zephiK said:
Fastboot flash stock google images. And your phone isn't bricked. Stop using the term wrong. It's most likely a software issue or you're doing the rom flash procedure incorrectly.
A bricked phone is a phone that is unaw to go into bootloader and recovery mode and cannot start android.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sorry for using the term wrong, I thought it just referes to broken phones.
The ROM flash is correct and it runs for some time and the problem occours after a few days... the only thing that helped was reverting to factory images and after that restore the nandroid from the "broken" Rom.
So the Rom works... than keeps crashing, I do a nandroid backup and only a factory image stops the crashes. But the Rom keeps working after I restore it.
I can't see why this could be a hardware issue. And I can't see how I should explain it to the store "Yes, it is working but not with custom roms, and I bought the Nexus because of custom roms..."
the_alien said:
Sorry for using the term wrong, I thought it just referes to broken phones.
The ROM flash is correct and it runs for some time and the problem occours after a few days... the only thing that helped was reverting to factory images and after that restore the nandroid from the "broken" Rom.
So the Rom works... than keeps crashing, I do a nandroid backup and only a factory image stops the crashes. But the Rom keeps working after I restore it.
I can't see why this could be a hardware issue. And I can't see how I should explain it to the store "Yes, it is working but not with custom roms, and I bought the Nexus because of custom roms..."
Click to expand...
Click to collapse
I'm willing to bet an app is causing it.
Sent from my Galaxy Nexus using xda premium
One of my colleagues had this issue with an early CM9 build on his Nexus S - turned out it was an app that is incompatible with ICS. Every time it tried to launch a notification, poof. So I would have to side with Josh in the post above mine.
A way for you to verify / discredit this theory would be : When you say it works with the stock ROM, are you re-installing everything you have when you are on stock? My understanding from what you've written above is that you're only getting your full suite of apps back when you restore your (presumably custom ROM) nandroid backup...
Potterified said:
One of my colleagues had this issue with an early CM9 build on his Nexus S - turned out it was an app that is incompatible with ICS. Every time it tried to launch a notification, poof. So I would have to side with Josh in the post above mine.
A way for you to verify / discredit this theory would be : When you say it works with the stock ROM, are you re-installing everything you have when you are on stock? My understanding from what you've written above is that you're only getting your full suite of apps back when you restore your (presumably custom ROM) nandroid backup...
Click to expand...
Click to collapse
It can't be any app or ROM because IF it happens, it happens on all ROMs, regardless of wipe or not.
It just happened again and i wiped everything and tried using AOKP MS 3. Wasn't working... So I tried using the phone without the SIM card, because the hell only breaks loose after entering my PIN. And it worked. I could use the phone...
I put it back in and it worked...
I'm restoring my CM9 nandroid right now. I'm hoping it works...
edit: Nope, ripping out the SIM doesn't work. I'm reverting to stock and wait what happens. If it crashes again I'm trying to return it.
I was having a few issues with my phone. Primarily boot loops with AOKP b23 and franco #17.2 kernel. So I went into clockwork recovery as per usual, flashed a backup a had made a few months back.
However when it booted up, it was not the backup I had made, and was in fact a stock version of android. I know this as it even prompted me with the option to upgrade android over the air. Something I believe an unlocked phone will not do. So wtf happened? It is all working fine now as stock, but will no doubt be trying to flash CWM on sometime soon.
Sent from my Galaxy Nexus using xda premium
If u turn your phone off and power it back on and see a padlock in the bottom of the Google logo. Then your boot loader is still unlocked. U can use fast boot to flash cwm again and flash a new rom.
Sent from my Galaxy Nexus using xda premium
Yeah it is still unlocked. So I'll follow the normal procedure from there.
It seems a very strange occurrence though, something I haven't read about or experienced before. Had me very worried for a while. Any idea what could cause a recovery to do that?
Sent from my Galaxy Nexus using xda premium
I can't definitively speak to why things reverted in that way, but I'd suggest reading through this thread.
The discussion there was very informative to me as far as better understanding how a cocktail of stock/modded recoveries, bootloaders, kernels and ROMs all play together on the same phone. For one, your idea of what receiving an OTA notification indicates is a bit off (but I'll let you read through that for yourself instead of rehashing).
This is sort of a stab in the dark, and I don't know if a nandroid includes the recovery installed at the time, but you can run CWM without installing it over the stock recovery. Maybe you did this with your first nandroid and installed CWM afterwards, then forgot about what the nature of that nandroid was?
Anything qualified with "a few months ago" is a red flag to me to suggest limits of human memory accuracy
Hi everybody!
I figure we should have a thread dedicated to telling horror stories about flashes gone wrong. Whether it's because of power failures, bad USB cables, poorly labeled packages, or pure user error, we've all had that moment of worry: "Did I just turn my device into a paperweight?"
It's my hope that, by sharing these stories, we can help each other realize that we're all human, we all make mistakes, and most mistakes can be recovered from. Don't be afraid to share your stories; we can't learn from each other's mistakes if nobody talks about them!
_____________________________________________
My first story is from my Telus SGS3 (I747M, you'll see why that matters in a moment) and is definitely a user-error kind of story.
I've been playing around with CM10 and its derivatives for the past month or two (got my SGS3 on release day and it wasn't running Samsung software 3 hours later) and I'm not new to Android, having run XDAndroid on my HTC Diamond, and bouncing between CM7 and CM9 on my Milestone. The first thing I did when I got my SGS3 was a full block device backup using DD from the command line, which is the only reason I don't have a paperweight today.
I decided to try out Paranoid Android over a week ago and I've been loving it, so I haven't been flashing much lately. But, when I got back from vacation and saw that CM10 had gone into nightly builds, I couldn't resist the temptation to try a clean install. I've got folders on my SD card for ROMs, GApps, kernels, recoveries, and anything else flashable just to make my life easier. Apparently at some point I downloaded an AT&T (I747, no M) modem, stuck it in a "/modems/" folder with the rest of my flashables, but realized that it wouldn't work on my device, so I never used it. I then promptly forgot that I had put it on the SD card, and it had a fairly cryptic filename. Away I went, flashing CM10, GApps, a nice bootscreen, and... the modem.
Dammit. :crying:
At this point, I was running the newest CM10 build, but with a borked modem. I thought I had fallen victim to the IMEI bug that's been going around, but then I remembered something about that modem file not being usable on a Telus device... And had no idea how to get back to a working state. I already knew that none of my nandroid backups would have the modem in them, and the only "stock" flashables I could find were rooted kernels and a nearly-700MB "stock" package that wouldn't download any faster than 10 kb/s. I couldn't wait 20 hours for a download, I wanted my phone now! I tried using Odin with a few of the TAR packages I found, but that only made my situation worse to the point of failing to boot entirely, even restoring a nandroid wasn't helping anymore.
I started digging through the forums in the hope that someone had ripped the Telus modem into a CWM flashable zip, but had no luck. I tried both the Rogers and Bell modems with the same results. That's when I remembered that I had done a block backup, but I had no idea which block device was the modem, and my phone wouldn't even boot up to let me MTP the files over. I was left with CWM recovery as my only option, and had to ADB push 2.5 GB of .img files to the SD card, and DD them one at a time through the ADB shell.
Somehow, it all worked out, and I was back to running Stock Touchwiz with root, and was then able to restore a nandroid from yesterday and amazingly enough Paranoid Android booted up, happy as ever, and in came my emails and text messages. I know I'm lucky that my IMEI didn't get lost in that mess, but it just goes to show that there's no such thing as a backup being "too extensive". You never know when "mmcblk0p99" needs to be replaced with a known working copy.
I do believe im going to flash a stock/rooted ROM and then do a dd backup.
What options do you set for your backups?
Sent from my SGH-I747M using xda premium
I did as follows:
Code:
cd /dev/block/
ls
(get the list of mmcblk devices from here)
dd if=/dev/block/mmcblk0p1 of=/sdcard/dd/blk0p1 bs=4096
...
dd if=/dev/block/mmcblk0p99 of=/sdcard/dd/blk0p99 bs=4096
Obviously you shouldn't have 99 partitions... but you get the idea. I ran each line manually.
Then just move the /dd/ folder off your /sdcard/ and onto some safe storage.
I bought my device off someone from Craigslist 2 nights ago. Went home with device working great. Decided to update from ICS to JB, downloaded everything on the ol gaming machine, go to update using Kies, then BAM! Hung update, bricks phone immediately. Woo....great experience after dropping $400 on phone lol. Contacted Samsung support who told me my update wouldn't work until I registered? I told him it bricked my phone and it wasn't being picked up by computer anymore and I wanted to go back to ICS, he apparently thought waiting 24 hours would fix driver issues. Found JB official rom and learned about Odin. Worked at it until 2-ish am, never worked, woke up, did ICS instead same method, worked immediately, then update worked.
Moral of story? Don't trust Samsung apparently, go with 3rd party everything....
Can we share from other devices? Because I've had a serious one with my nitro HD lol.
Sent from my SGH-I747 using xda premium
After having my phone on stock rooted touch wiz since day one I was tempted to go jellybean... So months later I'd say Octoberish I finally said f**k it I'm going aokp... So I ran the task and k toonsen romantic for a while until they started porting the t mobile jelly bean stock tw rom... It made me miss tw and it's awesome camera app... So I flashed it after a week or so upon its release... First thing I noticed was the phone would get txts and phone calls rarely (keep in mind I'm in an lte area) and it became un bare able after about an hour. So I reverted back to my aokp nandroid and just figured I'd call it a day... But when I restored my nandroid my service was still messed up.. So after a bit of gooogling I checked my phone status to find my imei to be 0!!! I was beyond upset... So I tried re flashing stock in Odin and everything else I could find (unfortunately the imei restorer wasn't existent yet) and it came to the point where I left it stock and went to the att repair center down the road... The guy didn't know what was wrong with it and I just played dumb... After about 30 mins he came to the conclusion that my sim card slot was broken and I got a new phone...
After getting this one back home I instantly rooted it again
I've been staying away from those ported tmobile roms ever since
Sent from my SAMSUNG-SGH-I747
[/COLOR]
rani9990 said:
Can we share from other devices? Because I've had a serious one with my nitro HD lol.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I dont see why not. All stories are interesting lol
Sent from my SAMSUNG-SGH-I747 using xda premium
No bad flashes .... Yet?
Sent from my Nexus 7 using xda app-developers app
Alright then,
It was my first day with the LG Nitro HD. My first smartphone (don't comment xD) and I was prepared to root and flash the living crap out of it. Done with rooting, now to install CWM. Simple enough, right? WRONG. This was the one time where google was not my friend. I followed a horribly misleading guide, and ended up with a paperweight. Turns out I flashed the recovery image to the secondary bootloader partition, thereby bricking my phone completely and utterly, irreparably. Had to ship it off to LG, and they fixed it, no questions asked. Thank God for that...
I had an HTC Touch Pro on Sprint. You had to flash a stock ROM before flashing a new custom ROM or the phone would stop working properly after almost exactly an hour. The file system would become completely messed up but the OS would keep running from RAM. It would fail to reboot after that. It was such a pain that I updated my phone every ~3-4 months.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
This one actually just happened this weekend.
So I finally got bored of having stock ICS on my i747 (Rogers), and since I loved cm 7/9 on my SGS2, I figured I'd go with the latest (15 dec) CM10 nightly.
downloaded to phone, rebooted in recovery, wiped data and cache, and installed the new firmware.
booted up and I've got no (or inconsistant) cell service. Figure it's a bug that hasn't been fixed, so no biggie, I backed up a week ago, so I decided to revert back to stock for the time being.
go through the process, and discover I still only have EDGE data.... WTF?
So I do some reading *AFTER the fact, hur dur...* and discover the IMEI wipe issue, and surprise surprise, I didn't do an NV backup, since I didn't know it'd get wiped.
Spent a couple hours keeping the phone / computer away from the 13 month old while I replace the IMEI NV data.... Still stuck on EDGE.... at least my IMEI is showing up though.
Nick
Odin back to stock worked for me when that happened to me.... YMMV.
Sent from my SGH-I747 using xda premium
The night I got my phone, I rooted via odin and when it booted, I'd get a framework FC every 90 seconds or so. It took me almost two hours to get cwm recovery on my phone to flash AOKP. Not a brick, but since I hadn't even activated it, yet....not happy.
Sent from my SGH-I747 using xda app-developers app
Each Phone an Adventure
I can completely relate to all of you. Though I'm new as a member (thought I already had an account but apparently I didn't), I've been using the forum for a long time. I have rooted four phones to date, each with its' own disaster story and happy ending. My latest was the AT&T S3. While not a disaster entirely, the no flash counter guide ended up not working out for me. So I paved my own trail so to speak and I found all the root dependencies (Recovery, ROM, the works) by myself. The entire process took me about a day. I also used TriangleAway which threatened explosions if anything went wrong and thankfully nothing did. I'm glad I never had to send a phone back, I've always been very cautious about any type of flashing and always read the forum before doing it.
When I was on the captivate, I really wanted JB so I thought I could grab the Nexus S JB ROM cause the devices were so close to each other. Flashed it via Odin. Good God was that a mistake. I couldn't get back to download mode using the button combo since the button mapping was all switched up. I had this one cable that would give me bad connection, so I jiggled that around in the port for 35 minutes trying to get download mode. Finally, I got it and flashed the stock package. Learned my lesson, will never flash something from a different phone or anything that won't work 100%.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
goobs408 said:
When I was on the captivate, I really wanted JB so I thought I could grab the Nexus S JB ROM cause the devices were so close to each other. Flashed it via Odin. Good God was that a mistake. I couldn't get back to download mode using the button combo since the button mapping was all switched up. I had this one cable that would give me bad connection, so I jiggled that around in the port for 35 minutes trying to get download mode. Finally, I got it and flashed the stock package. Learned my lesson, will never flash something from a different phone or anything that won't work 100%.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
The thing about the Captivate was, no matter what ROM you flashed, the jig ALWAYS worked. It saved my ass quite a few times, until that is, the memory in the phone decided to die. I could flash through Odin as much as I wanted and it would pass everytime, but never go past the boot animation.
Dave the Knave said:
The thing about the Captivate was, no matter what ROM you flashed, the jig ALWAYS worked. It saved my ass quite a few times, until that is, the memory in the phone decided to die. I could flash through Odin as much as I wanted and it would pass everytime, but never go past the boot animation.
Click to expand...
Click to collapse
Flash stock GB with forgot name of kernel baked in. After that in cwm recovery partition external SD card.. then reflash in Odin then install whatever ROM u want
Sent from my SGH-I747 using xda premium
Trying to use Kies to flash anything. That's always a bad story for me
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Don't attempt to explain to a friend of little flashing knowledge how to root their phone. He hard bricked my phone. Odin is easy if you read but he turned it into rocket science and yeah.. Had to wait for another phone
Sent from my SGH-I747 using xda app-developers app
Well let me begin by saying I have a Galaxy Nexus and have been flashing roms, etc like it's going outta style. It's very simple to me and I am no newb. So with this logic in mind, I got a brand new GS3 the other day and proceeded to do the same. First, it took my a while to realize there are so many variants of our phone, then when I did a search I saw that there was a i9305 that is LTE....you already know where this is going. I figured that was the correct variant, spent like an hour trying to install a recovery because of the auto wipe feature and thus increasing the flash counter to 10+ (wtf!). Finally I download a rom, flash it. Freezes half way through (knew that wasn't good) and when I pull the battery, BAM, bricked phone.
After some more reading, not only did I find out the correct way of flashing to not increase the counter but also that the Canadian versions are the i747! Luckily it happened a day after I got it and I switched it out for a new one. Moral of the story: If you are flash happy and think all phones are like the Nexus, that's your biggest mistake! lol
I've been testing out various jelly bean ROMs and they all get stuck while booting up on Google logo, it takes a good 5 or so minutes to boot up. I have a Verizon Galaxy Nexus. If it helps, I use each ROM for a week to have things settle down before I decide to move on. Does anyone else have this problem?
Yeah, I have the same problem. I did some research and found that it might be the older ICS boot loader, so I loaded up the JB boot loader. This seemed to work at first, but after switching to CM10 nightlies, it still behaves as before.
Right, forgot to mention I too have tried JB Loader, same scenario as you.
Stupid question, but do you dirty flash or clean flash? Do you flash toro version or toroplus version?
I always do a clean flash of any new rom flavor. If I am doing nightlies, I dirty flash.
I always flash toro (VZW).
TonyDeez said:
I've been testing out various jelly bean ROMs and they all get stuck while booting up on Google logo, it takes a good 5 or so minutes to boot up. I have a Verizon Galaxy Nexus. If it helps, I use each ROM for a week to have things settle down before I decide to move on. Does anyone else have this problem?
Click to expand...
Click to collapse
Known issue and has been covered over and over again in numerous threads.
jpspyro said:
Yeah, I have the same problem. I did some research and found that it might be the older ICS boot loader, so I loaded up the JB boot loader. This seemed to work at first, but after switching to CM10 nightlies, it still behaves as before.
Click to expand...
Click to collapse
It has absolutely nothing to do with the bootloader.
If the phone believes it was not shut down correctly, it will initiate a scan of the ENTIRE file system to check for errors. This takes about 5 minutes, and is done at the Google logo screen.
Any way/ROM that avoids this?
I've been running BAMF for a few weeks (with the ics bootloader) and it's only happened to me once.
Ryands991 said:
If the phone believes it was not shut down correctly, it will initiate a scan of the ENTIRE file system to check for errors. This takes about 5 minutes, and is done at the Google logo screen.
Click to expand...
Click to collapse
That makes the most sense of anything I've seen. Noticed the issue after flashing the leaked VZW JB OTA, went back to a clean factory image and tried again, with no change. The only thing I've noticed is the slow boot appears once apps are installed, and only after a battery pull or being off for a few minutes or longer. Since I rarely pull a battery (only if switching to a spare because I can't plug in to charge) or actually turn the device off, it's really a non-issue.
Sent from my Xoom using xda premium
Will occasionally happen to me when rebooting which kind of makes sense as this wasn't initially designed into the build.
Sent from my Galaxy Nexus using Tapatalk 2
I was having this issue when I re-flashed su.zip after the OTA 4.1.1 update. I flashed my phone back to stock 4.0.4 and let it upgrade OTA to 4.1.1. It booted normally now. I added a half-a-dozen apps or so and everything was still fine. I rebooted many, many times. My /data folder was basically clean. Then I installed SuperSU using recovery-clockwork-6.0.1.0-toro.img. That's when the problem started to happen again. The Google screen would sit for just about 3 minutes. Now since then, I added about 12 gigs of media but the boot hasn't lengthened. It's still just about 3 minutes. It always takes that amount of time now no matter how many times I reboot. I sure would like to find out exactly why JB is doing this scan every boot since root. The rooting must prevent a normal shutdown to trigger this. I'm on the stock rom.
I'm just going to throw this out there for anyone who may know the answer, after searching for the last 3 days, I'm not finding anyone else having the same problem, so I'm thinking it may be something I did. Here's the issue.
I'm a confirmed flash-a-holic, and flash new roms or backups probably 2-3 times per week. I haven't tried any of the JB roms until recently, but dove in just before Nit's Viper Rom became available for ICS. I had installed the JB "global" rom, and had it working(ish), and then changed to the viper mod, then installed Aeroevan's "unofficial JB" when the 10/25 update on Goo.im came available. The install went smoothly and it worked great for about a day, then tanked big time when I tried to change the launcher from Trebuchet to Nova (I can't even guess why THAT had anything to do with it). It started lagging big time and then boot looping. Now, upon trying to wipe everything (factory reset/cache/dalvik/all partitions but sd), I get nothing but boot loops and NONE of the JB roms will install. From my reading, I know others get boot loops, but after a sequence, finally get into setup. Mine will too after 5-6 boot loops minimum, but the screen freezes on the initial setup screen and it's completely unusable (touch screen unresponsive). I don't get why that is when I HAD it installed the other day and it was very responsive (using Aeroevan's JB mod). I WAS using the 4EXT recovery when I started doing all of this, then switched recoveries to the most recent TWRP, and it allowed me to install Aeroevan's JB mod, and even start the setup, but very soon started lagging and then the boot loops again. At this point, I'm sortof at a loss, and the only thing I can think of is that maybe I should NOT have been wiping the sd partitions and SHOULD have only been wiping cache/dalvik/factory reset. At the moment, anyway all ICS mods are flashing/running just fine (currently on Nit's Vipermod and really liking it btw), but if anyone knows where I went astray, I'd appreciate any pointers. Thanks all, this is by far the best forum I have been a part of!
http://forum.xda-developers.com/showthread.php?t=1805773&page=117
Oh boy..... Be sure and post back if you find a solution, glad I'm not the only one! I thought I did this to myself... which I guess I sortof did if you get technical.
Sent from my Dinc2 using Tapatalk
I had the same problem but was told to flash new radio and it stopped bootlooping and everything went back to normal....
auberry05 said:
I had the same problem but was told to flash new radio and it stopped bootlooping and everything went back to normal....
Click to expand...
Click to collapse
Which radio did you flash?
Ok, I made headway by reverting TWRP recovery back to 4ext's newest recovery, restored my oldest original stock GB backup with ext3 partitions which was originally a CWM recovery. I let it run after install for about 10 minutes without updating anything, then 4Ext wiped data, cache/dalvik, system. I then reformatted all partitions back to 4ext and then wiped everything again even fixing permissions. Then I tried a fresh install to Aeroevan's unofficial CM10 from 10/25 and gapps from 10/11. Install went smoothly and booted first time with no boot loops. I'm using it right now and I'm back in the butter again..... for now at least. If I take a turn for the worst, I'll post back.
Ok, well, scratch that, I am having the same problems a couple of other guys are having in the cm10 dev thread. I'm only able to run sense roms, original stock, UKBII, etc, no ICS or JB roms work, incredibly laggy and bootlooping endlessly. I have never had this much trouble flashing roms, I do it all the time. Sadly, it started when I flashed the viper rom, and I don't even have a copy of it to re-flash now since I wiped my card and it wasn't backed up on my computer (I think I must've downloaded it from my phone). I have spent WAY too much time on this, so am now relegated to only lurking here until someone can find a solution that's not just "firing down the well" like I've been doing since this started.
bwpoersch said:
Ok, I made headway by reverting TWRP recovery back to 4ext's newest recovery, restored my oldest original stock GB backup with ext3 partitions which was originally a CWM recovery. I let it run after install for about 10 minutes without updating anything, then 4Ext wiped data, cache/dalvik, system. I then reformatted all partitions back to 4ext and then wiped everything again even fixing permissions. Then I tried a fresh install to Aeroevan's unofficial CM10 from 10/25 and gapps from 10/11. Install went smoothly and booted first time with no boot loops. I'm using it right now and I'm back in the butter again..... for now at least. If I take a turn for the worst, I'll post back.
Ok, well, scratch that, I am having the same problems a couple of other guys are having in the cm10 dev thread. I'm only able to run sense roms, original stock, UKBII, etc, no ICS or JB roms work, incredibly laggy and bootlooping endlessly. I have never had this much trouble flashing roms, I do it all the time. Sadly, it started when I flashed the viper rom, and I don't even have a copy of it to re-flash now since I wiped my card and it wasn't backed up on my computer (I think I must've downloaded it from my phone). I have spent WAY too much time on this, so am now relegated to only lurking here until someone can find a solution that's not just "firing down the well" like I've been doing since this started.
Click to expand...
Click to collapse
On follow-up, I read mixed opinions about the wisdom of using TiBu on restores, assuming I'm able to ever recover this my thinking is that one could use TiBu to restore apps ONLY and NO data and that would/should not cause a problem (assuming you're restoring a backup from within your installed ROM's file structure .i.e., JB/ICS/GB)? Also, I use My Backup Pro to restore call/MMS/texts only, that oughta be safe too shouldn't it?
I had a similar issue last night. never had problems flashing from viper to cm10 till yesterday. I've flashed back and forth about 3 times until I flashed the leaked 4.2 camera with sphere camera on aero cm10 Halloween build. I was playing around with the sphere camera and attempted to get it to actually finish loading the pics together by overclocking to 1.4mhz and I ended up pulling the battery. it boot looped very slow and laggy after. I did a full wipe, fresh install of aeros cm10 from twrp and got the same thing. So I recovered viper Rom from twrp , booted, then did a full wipe and install of cm10 and still boot loops laggy. I did not have the overclock settings "set at boot" ticked when I put it to 1.4mhz. odd indeed
sent by the viper
So... I was having no issues until today's huge headache. I was on cm10 10-25 and it worked great. Dirty flashed to 31 and it all went to hell. Slowed to a crawl so restarted to recovery to fix permission. Restarted and it kept restarting. I got some failure message when it would boot. Don't recall what it was.
I then tried 3 different recoveries and also full wipes and fresh flashes of 3 different roms. Same loop result basically. Finally an old recovery worked and I'm on a month old mrom version now. Soo... any thoughts on what the heck happened? I did nothing out of the ordinary. I was worried I somehow bricked but obviously not since I'm sending this on my phone. Kinda freaked to do anything right now... any thoughts or help/ideas?
PS... I just use the basic cwm and only cwm for my recoveries.
Sent from my Incredible 2 using xda app-developers app
Ukb wont boot here.
Sent from my HTC_Amaze_4G
so I got aeros 10/31 build to boot after taking 10 min to finish the start up set-up. it was extremely laggy, it would random restart a few times. I played around with over clocking then under clocking but the cpu was maxed out 24/7. I'm assuming this is what is causing the extreme lag. I changed the governor to on demand and it started to act normal and not lag out. so I used it for awhile then I decided to change the cpu governor back to smartassv2 and then I was back to lag and the cpu was maxxed again... can't recreate the scenario cuz it doesn't boot now...
my conclusion is it has to due with the kernel and cpu governors on JB. I've tried aeros jb 12, 13,14,and 15 kernel and also Evans kernel with no luck on getting the cpu not to b maxed out... hope this helps solve the issue
Sent by the viper
fen0m said:
so I got aeros 10/31 build to boot after taking 10 min to finish the start up set-up. it was extremely laggy, it would random restart a few times. I played around with over clocking then under clocking but the cpu was maxed out 24/7. I'm assuming this is what is causing the extreme lag. I changed the governor to on demand and it started to act normal and not lag out. so I used it for awhile then I decided to change the cpu governor back to smartassv2 and then I was back to lag and the cpu was maxxed again... can't recreate the scenario cuz it doesn't boot now...
my conclusion is it has to due with the kernel and cpu governors on JB. I've tried aeros jb 12, 13,14,and 15 kernel and also Evans kernel with no luck on getting the cpu not to b maxed out... hope this helps solve the issue
Sent by the viper
Click to expand...
Click to collapse
Someone just threw down on the info. Sounds like I will be flashing the latest mrom. Not gonna repeat the horror of my recent cm10 fiasco. Thanks for this.
Sent from my Incredible 2 using xda app-developers app
Unfortunately I too am finding it near impossible to flash any ICS/JB ROM. The closest I've gotten is the Google sign-in on Andromadus Mimicry, but that practically slows to a halt when signing in. As of now I'm on Condemned CM7 and I must say I REALLY miss Google Music.
Sent from my Incredible 2 using xda premium
jtsrtr13 said:
Unfortunately I too am finding it near impossible to flash any ICS/JB ROM. The closest I've gotten is the Google sign-in on Andromadus Mimicry, but that practically slows to a halt when signing in. As of now I'm on Condemned CM7 and I must say I REALLY miss Google Music.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Try installing 4ext recovery. Format system, data, cache to ext3 like 3 times. Flash tunnas global cm10 rom
Sent from my Incredible 2 using xda app-developers app
Baby mamas INC 2 has been having same issues. I have to believe it had something to do with her being on the ICS leak from back in September with the 320 radio. I went as far as to getting back to compete stock with s-off. Got back to 2.3.3, got CWM and root. Hopefully I can try getting her phone back on CM9-10 cuz she really misses it and we were having EXACT problems stated above. Boot loops, touch screen not responsive, wallpaper would change out of nowhere, lock screen would be black with nothing but hardware buttons lighting up. Thank GOD for these devs and their work to get back to stock or I would have thrown this POS out the window lol.
Sent from my MB865 using xda premium
A2Trip said:
Baby mamas INC 2 has been having same issues. I have to believe it had something to do with her being on the ICS leak from back in September with the 320 radio. I went as far as to getting back to compete stock with s-off. Got back to 2.3.3, got CWM and root. Hopefully I can try getting her phone back on CM9-10 cuz she really misses it and we were having EXACT problems stated above. Boot loops, touch screen not responsive, wallpaper would change out of nowhere, lock screen would be black with nothing but hardware buttons lighting up. Thank GOD for these devs and their work to get back to stock or I would have thrown this POS out the window lol.
Click to expand...
Click to collapse
I did the revert a while back for some other issues and didn't have any trouble getting aeroevan's CM10 up and running. I haven't had any issues with it other than the persistent bugs which are no problem for me. I don't think these issues have anything to do with the radio, but with the way the stuff is getting flashed. You might try a different recovery. I have had success with TWRP and CWM (as installed from ROM Manager, not touch) restored from a backup for me, but I didn't install using CWM.
ericsdeadinside said:
Try installing 4ext recovery. Format system, data, cache to ext3 like 3 times. Flash tunnas global cm10 rom
Click to expand...
Click to collapse
Did these things ....even Stunna's CM10 was laggy beyond belief. Back to gb.....again.
Sent from my Incredible 2 using xda premium
Don't know what to tell you. I switched to 4ext ran CDMA miui for a week and I was able to flash cm10 with no issues.
Sent from my Incredible 2 using xda app-developers app
jtsrtr13 said:
Did these things ....even Stunna's CM10 was laggy beyond belief. Back to gb.....again.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
+1... seems like only Sence ROMs have been working on my girls Inc. 2. Viper seems fine for now... But her phone must literately hate CM9 and 10...7 works fine too. Not quite sure why these issues have been going on to few of us but I'm almost certain it will not be solved... On the move...
Sent from my MB865 using xda premium
hey guys I fixed my Inc 2 with jb ics lag/ boot looping issues.
check it out
http://forum.xda-developers.com/showthread.php?t=1987051
Sent from an incredibly running JB inc2