This is as little long, but I wanted to be as thorough as possible. I have loaded custom ROMs successfully in the past and I beileve I followed all the directions in the FAQs. Nevertheless, I could have missed something.. so here you go.
I installed the cyanogen7 RC2 release today. I installed it on a freshly wiped phone. I updated the incredible to the latest official update from verizon, rooted it with Unrevoked3 and then did a nandroid backup.
I rebooted, opened recovery and wiped the cache and then the phone. I installed the rom update-cm-7.0.0-RC2-Inc-signed via SD card. It said it was successful. After I restarted, the phone worked.
Next, I went into the rom manager and downloaded gapps. it asked me to reboot I said yet but declined to backup prior (as I already had the fresh verizon backup). It said it installed successfully.
Upon rebooting I hit the cyanogen load screen which cycles ~4 times.. After that the "welcome to adr6300" screen pops up where it tells you to click the droid in the middle of the screen. The screen is almost unresponsive. If I can get it to click, i advance to the next screen where it becomes completely unresponsive. Regardless of where I get on the setup page, after ~3 seconds it takes me back to the cyanogen load screen and this continues in an endless loop.
I tried clearing the cache and wiping the drive in recovery and reinstalling the rom but I still get that screen (which leads me to believe its an issue with gapps??). So I went ahead and cleared the cache, dalvik cache, wipe, and then restored my original official vwz rom.
I downloaded gapps-hdpi-20101114-signed from the CM6 stick this time and put in on my sd card (root). I got the phone back into recovery mode, and cleared both cache's (realized I missed this the first time) as well as wiped the phone. The CM7RC2 rom installed successfully and once again I was able to get into the rom.
I restarted after that success, booted into recovery, and flashed the gapps-hdpi-20101114-signed.zip file. It said it was successful and I rebooted. However... the phone still will not get past the CM7RC2 screen...
Do you know what I'm missing? I've tried to be as thorough as possible. When I first boot up the CM7RC2 rom, do I need to do something else prior to installing GAPPS? Do i need to install GAPPS immediately after CM7RC2 prior to booting the phone up at all?
edit: With the fresh vwz rom install, I did install a few apps (about 10) prior to backup as well as remove about 15 bloatware apps so I wouldn't have to re download or delete them if I flash back to the regular rom (re installed beautiful widgets, astro, titanium backup, etc. Removed vm, vzwnav, etc). I didn't open or input preferences in any of them.. but could this be causing the conflict? Should I hard reset the phone, get the OTAs all over again, root etc w zero apps?
Just realized I had the wrong version of gapps and not to get the ones from the sticky under the Dinc rom section.
I got the latest (and correct one) here:
at goo-inside.me/google-apps/
Not sure how I missed this before but I now have the correct one and its working.
Thanks anyway!
Related
I have a G2. I decided to root it using the guides on Lifehacker and Cyanogens wiki. I got a temproot using Visionary, and permaroot using terminal. Everything went swimmingly. I only used download links that I found on Lifehacker and on Cyanogen's site (the same places I got the guides to root my phone) I attempted to root my phone and put CM7 on it. I backed up everything with Titanium Backup. I downloaded Rom Manager, flashed ClockworkMod Recovery to get the latest version, downloaded CM7 through Rom Manager, and attempted to install it as well as backup existing ROM and wiping data and cache. My G2 returns to the HTC startup screen and just stops.
I tried to do a factory reset, it just stops at the same area. I tried doing a factory reset from the startup options (power and down volume), nada. I tried reflashing ClockworkMod Recovery, zilch. I restored my backup from Titanium, nothing.
The phone works, I'm able to do everything I would normally do on it, but I just can't get this to work and I don't know where I went wrong or how to fix it. I have experience with UNIX based systems so I know how to work a command line to an extent and I know that part went off without a problem. I just can't figure out what's going on with it.
I have been on all the Root66 versions, and have had no problems ever...... till this UVDM5
I made a CWM backup (2 just to be sure) and proceeded to flash this new version that I have been waiting for so anxiously!
After it booted up, my desktop was the same, and all the apps showed, but talkback was already turned on, and I could no way get to the settings to turn that #$%%$ thing off. Heck, I could not even get to anything at all. It kept talking and reciting numbers everytime I tried to do anything. It was "Frozen" on the main homescreen, and could not do anything. I sometimes could get to the app drawer and that, too, would not scroll or do anything. I Re-flashed the thing after doing another download with the usual cache, dalvic blow out, and it acted the same way...
I decided to revert to the backup and tried to get to recovery (CWM).... That, too was gone! Stock recovery. I flashed the only version I had of CWM and it booted, and declared both of my backups were "corrupt" after it was almost done restoring?????? WTF!!!
I then reloaded UVDMD5 again, got the same results so did a factory restore and got to install my ROM manager, and re-flashed CWM to the version it uses, and tried the restore.....
It worked, and now after some pressure packed moments, I'm back to the UVLJA. I have to go on a trip tomorrow, (in a few hours) and need the phone working. PHEW! if anyone knows why the hiccup that I had occurred, please chime in and let me know. I still want the new OS and after my return, I plan to do the update again.... Hopefully....... Just gotta ccalm m my nnnneerves a bit before I attempt it again!
bobolinko said:
I have been on all the Root66 versions, and have had no problems ever...... till this UVDM5
I made a CWM backup (2 just to be sure) and proceeded to flash this new version that I have been waiting for so anxiously!
After it booted up, my desktop was the same, and all the apps showed, but talkback was already turned on, and I could no way get to the settings to turn that #$%%$ thing off. Heck, I could not even get to anything at all. It kept talking and reciting numbers everytime I tried to do anything. It was "Frozen" on the main homescreen, and could not do anything. I sometimes could get to the app drawer and that, too, would not scroll or do anything. I Re-flashed the thing after doing another download with the usual cache, dalvic blow out, and it acted the same way...
I decided to revert to the backup and tried to get to recovery (CWM).... That, too was gone! Stock recovery. I flashed the only version I had of CWM and it booted, and declared both of my backups were "corrupt" after it was almost done restoring?????? WTF!!!
I then reloaded UVDMD5 again, got the same results so did a factory restore and got to install my ROM manager, and re-flashed CWM to the version it uses, and tried the restore.....
It worked, and now after some pressure packed moments, I'm back to the UVLJA. I have to go on a trip tomorrow, (in a few hours) and need the phone working. PHEW! if anyone knows why the hiccup that I had occurred, please chime in and let me know. I still want the new OS and after my return, I plan to do the update again.... Hopefully....... Just gotta ccalm m my nnnneerves a bit before I attempt it again!
Click to expand...
Click to collapse
It seems to be an issue with the latest version of TalkBack on most roms. I had the issue already and from what I read in the forums, many other people have to. My advice, as soon as you flash a rom, uninstall or freeze talkback and DO NOT let it update to the latest version. Im not too sure what the issue is but hope Google fixes that soon.
I think also that I had a problem before when I installed the stock 4.1.2, it seemed to take my sdcard and renamed it to 0 on the sdcard. Took me a few hours to figure that out. I then copied everything that was in the folder 0 over everything in the root of the sdcard and it was back to normal.
Thanks! (Clicked it already)
I did notice a LOT of stuff was on the external card after the final recovery to the older version and had to clean up the external SD card.
You were right! I had no means to freeze the TalkBack, or do anything at all while within the OS itself, so no alternative was available to me at that time except a Factory Restore. The re-installation of my software was just going to take too long, so I did a recovery using the same version of CWM and was back where I was before the fiasco. Good thing I got it going.... Ida been really screwed! LOL. I'll try again maybe later, when I get home.
When I do try again, I'll remove the SD Card and then do the install using a spare one.
Have a great day!
So my phone is stuck in bootloop. and I cant get my phone to boot correctly.
To start, I was running 4.2.2 AOKP for about half a year and it started to not work as well. Force closing alot, freezing etc. So I decided it was time to update. While I was running AOKP, I experienced bootloop almost every time I turned off my phone. This became regular, but by pulling the battery and trying again (sometimes I had to do with a few times) it always got working again.
I went and found the new 4.3 Carbon ROM and decided that looked cool and would be a nice upgrade. So I downloaded it and the new 4.3 gapps. Put them on an external sd card, and put it into my phone. I then booted into CWM and did a factory reset. Then I went and installed the Carbon from the external sd, installed gapps, and rebooted immediately. I was then, and still am, stuck in a bootloop.
I can restart my phone go back into clockwork.
But I cant get the phone, despite all my efforts, to boot correctly. I have tried to wipe caches, wipe dalvik, format system. All of it. yet I cannot boot correctly.
I really need a working phone. Any help would be really great.
Thanks all
Also, I am using TWRP 2.6.3 to do the flash of the Carbon after it failed the first time
Moheemo said:
Also, I am using TWRP 2.6.3 to do the flash of the Carbon after it failed the first time
Click to expand...
Click to collapse
2.6.3.0 seems to be giving many people issues. You need to install 2.6.1.0.
And is your radio up to date? Only 2 work...the new T-Mobile and Telus radios.
After those 2 things are taken care of, you should be fine. Tho lots of things can cause boot loops, and there's many.. many posts about it. If my suggestions don't help.....Search and read up. Try some various fixes.
Maybe try a different rom too.
Sent from my cellular telephone
---------- Post added at 03:09 PM ---------- Previous post was at 03:06 PM ----------
Hope you did a nandroid backup in recovery? Restore it if so. If not, you may need to start from scratch and Odin flash stock rom, flash recovery and root again.
Sent from my cellular telephone
Moheemo said:
So my phone is stuck in bootloop. and I cant get my phone to boot correctly.
To start, I was running 4.2.2 AOKP for about half a year and it started to not work as well. Force closing alot, freezing etc. So I decided it was time to update. While I was running AOKP, I experienced bootloop almost every time I turned off my phone. This became regular, but by pulling the battery and trying again (sometimes I had to do with a few times) it always got working again.
I went and found the new 4.3 Carbon ROM and decided that looked cool and would be a nice upgrade. So I downloaded it and the new 4.3 gapps. Put them on an external sd card, and put it into my phone. I then booted into CWM and did a factory reset. Then I went and installed the Carbon from the external sd, installed gapps, and rebooted immediately. I was then, and still am, stuck in a bootloop.
I can restart my phone go back into clockwork.
But I cant get the phone, despite all my efforts, to boot correctly. I have tried to wipe caches, wipe dalvik, format system. All of it. yet I cannot boot correctly.
I really need a working phone. Any help would be really great.
Thanks all
Click to expand...
Click to collapse
flash stock rom zip via odin then you should be good to root and try to flash another custom rom again:good:
Thanks for taking the time to read and hopefully help me out.
First off I was rooted stock and updated to NF9 and have TWRP installed. This morning I went to flash my first rom on this device, effortless ROM. It did jot flash, it said that the zip couldn't be opened. So I downloaded dompop on my PC and transfered to my SD card. Dompop installed fine, but after waiting 30+ minutes to boot up I pulled the battery and reflashed. Same result. So now I am trying to restore my back up I made last night and it seems to be stuck at restoring modem (64%). Its been stuck here for 30 minutes. Any help would be appreciated.
Going on 45 minutes now.....anyone think its safe to pull the battery and try to restore my back up again? How long should a restore normally take with this phone?
Also I don't have access to PC for a few hours.
So I read flashed each partition individually and it seemed to work. No after is starts up a bunch of black boxes appear one after another stating that "unfortunately the process (insert process name) has stopped. And it appears to be every app I have on the phone. I wiped cache and delvik cache. Going to try wiping data next.
After restoring my back up one partition at a time I had to wipe data and cache for it to work properly. Any ideas on why I wasn't able to install a custom ROM?
Hello all!
This is my first foray into the world of custom Android systems, and I'm having a hell of a time with it... if somebody would be able to help me out, I would greatly appreciate it.
First off, the situation:
I am on Sprint, and I recently bought a Samsung Galaxy S3 (SPH-L710) from Sprint to use as a backup phone, I used it for a while on Stock, then deactivated it so I could give it to my wife. First though, I wanted to put a custom ROM on it, and experiment/play around a bit and see what this world of options could do for me. Long story short, I ended up flashing an AICP ROM, and everything seemed to go smoothly, but when I went to activate the phone on my account again and it would not work no matter what I tried (details below). I figured maybe I could activate on the stock setup then just restore my custom setup, so I tried to revert to my stock ROM backup and I couldn't do anything because I was constantly getting messages that various programs had closed... Then I tried to wipe and restore my custom ROM backup and I get stuck in a boot loop... so I tried to flash a stock recovery and I get stuck in a boot loop... I'm out of ideas here, and now I'm stuck with a phone I can't use or do anything with, and I can't activate.
Details:
The initial rooting/install process seemed to work ok, and was fairly straightforward. I followed various guides on http://galaxys3root.com/ to get my phone rooted and backed up (Don't recall which ones now, but I've read through so much by now I don't know if it matters...).
My phone:
Samsung Galaxy S3 (Sprint) SPH-L710
Modem: L710SPRDNJ2
My Desktop:
Debian Linux
Here's the steps I performed:
Rebooted phone in Odin mode
Downloaded CWM S3 Sprint Recovery from the http://galaxys3root.com/ website (can't find the link any more)
Flashed the CWM recovery using Heimdall then rebooted phone into CWM
Installed SuperSU through CWM, then rebooted
Checked that the phone was rooted successfully (it was), then ran Titanium Backup on the whole device to my SD card, then copied the backup files to my desktop computer
Rebooted into CWM, and performed a backup through CWM, then rebooted and copied the CWM backup to my desktop.
Downloaded AICP Rom for my phone from here: http://downloadandroidrom.com/file/GalaxyS3Sprint/roms/AICP/aicp_d2spr_lp-10.0-RELEASE-20150707.zip, put it on my SD card, then installed it through CWM and rebooted
At this point, I was happy with how everything was working, so I did some minor theme customizations then made another backup through CWM, and copied it to my computer, but I did NOT run Titanium this time...
After all of this, I tried to go ahead and activate it through the Sprint web service. This process failed continuously with an unhelpful error message of "Sorry, this device can't be activated right now". I then got on Chat to see if they could activate it manually, and then the problems began. They did their thing activating the phone, but when I booted up I got no data connectivity, and couldn't make calls, and the SIM was not changing over to the new number. I was on the chat with them for over an hour trying to get the situation resolved, but that finally ended when they started asking me to punch in ## codes, because I discovered that none of them worked on my custom ROM. Some quick research told me that this was non-trivial to get around so I had them switch everything back and I started researching the issue.
I found this thread: http://forum.xda-developers.com/showthread.php?t=1626638&highlight=sph-l710 that looked like it would let me do what I needed from the custom ROM, but I couldn't tell if it would fix my problem for sure, so I figured "I'll just restore my stock setup from that backup I took, activate it and update, then start over". This is when things got really frustrating...
First I rebooted into CWM, went to 'backup/restore', and restored my stock backup
Rebooted, and as soon as I got past the lock screen, I get inundated with messages of various apps being closed unexpectedly.
I researched a bit, discovered the issue may be caused by stale dalvik cache, so I rebooted into CWM, cleared the dalvik cache, formatted the /cache partition, then tried to restore the stock backup again, but this time I get stuck in a boot loop.
I then rebooted into CWM, tried to restore the backup of my AICP ROM, only to be stuck in a boot loop as well.
Trying to get into any usable system, I rebooted to CWM, cleared dalvik cache, then formatted /cache, /data, and /system just to be sure, and re-flashed the base AICP ROM I started with. This worked fine, and before long I had stock AICP back
Since I still couldn't get the phone to activate in the custom ROM, and my backups are apparently completely useless, I rebooted into CWM, wiped dalvik, /cache, /data, and /system again and tried to install a different stock ROM I found in the XDA forums (here: http://forum.xda-developers.com/galaxy-s3-sprint/development/stock-rom-4-4-2-t3010642) only to be greeted by another bootloop
At this point I've spent well over 24 man-hours trying to get this to work, reading, researching, flashing, etc all to no avail. Nothing I do seems to work, and it seems like every article, tutorial, or forum thread I read either has nothing to do with my device, is too old, or doesn't describe my problem.
I'm at wits end, and am so frustrated I'm ready to just give up and smash this device and buy a new one... My questions to the community are as follows:
I know I screwed up on a couple of things, but in my initial research of doing this there was no indication that these were even things I needed to watch out for... Is there any more organized sources of information for doing this sort of thing?
Does anybody else out there use Sprint on a custom ROM, and if so how you you pull this off
Where else have I screwed up, and how can I fix this situation? (My end goal is still to get the S3 onto Sprint with a custom ROM)
What can I do differently next time? I would like to figure this out and do it to other phones and devices I have, but if it's this much trouble every time, I just don't have the time to mess with it.
Thank you in advance, and I appreciate any information that the community can provide.
This sounds like a CWM problem to me. If I were you, I'd boot the phone into Odin Mode and flash TWRP ( www.twrp.me ) then try flashing the latest aicp nightly downloaded from the official site ( www.aicp-rom.com ). Check the md5sums on everything! Then maybe try flashing a touchwiz ROM and activating your phone. Remember that you need to wipe the internal storage when you go between KitKat and lollipop.
I'm fairly certain you have to do activation with the stock Touchwiz roms -- once the phone is activated you can flash a custom.
You should go into recovery and wipe everything (System/data/etc) EXCEPT for the External SD Card
Power off - pull the battery for a few - power on directly into download mode
Odin NJ2 back onto the phone and reboot and activate it (skip through most of the setup since you'll flash a custom after)
Once you know it's activated and working under the stock Touchwiz, then again power off and Odin TWRP recovery
Then you can go back into recovery, wipe everything except External SD, and flash the custom rom back on.
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
afarris01 said:
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
Click to expand...
Click to collapse
Get rid of them. TWRP can't restore CWM even if the backup is good