Related
I'm sorry if someone already asked this question but I was not able find an answer. I am running a custom ROM now, do I have to go back to stock before flashing another ROM?
It is usually not necessarily to do it but it a very good idea to return to stock and master clear with the odin-1-click
Sent from my GT-I9000 using XDA App
No you don't need to go back to stock. Nor is is necessary to master clear. Most if not all the roms on here will do a full wipe of your SD card during the install. Flashing back to stock just adds another chance to mess up your phone. This was advised, several months back but it's not necessary now. This doesn't apply if you want to flash to CM7. They have their own install procedure that is different than anyone elses.
Just to add to what the others said. Make sure u flash a 2.2 based rom over ur curent (if thats what u are.using atm). Also you cant restore system app, it will screw up with ur new rom!
Sent from my SAMSUNG-SGH-I897 using XDA App
BWolf56 said:
Just to add to what the others said. Make sure u flash a 2.2 based rom over ur curent (if thats what u are.using atm). Also you cant restore system app, it will screw up with ur new rom!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The 2.2 stock will not let you flash a rom over it. Go back to 2.1 stock
Sent from my SAMSUNG-SGH-I897 using XDA App
crystalhand said:
The 2.2 stock will not let you flash a rom over it. Go back to 2.1 stock
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Not what I meant.
If he flashed, lets say, FireFly (which is 2.2 based) then he can't flash over with, lets say, CM7 (which is 2.3 based). Just simple logic
@ OP - You can look on the ROM's thread to see what it is based on.
Thank you for all your help. I'm using Phoenix Ultimate now and want to try out the other ROM.
It takes like ten minutes to odin back to stock. I do it every time, just feels like a cleaner install. Plus all the devs put that in their instructions. I trust the devs.
If you download the CWM update.zip before you Odin to stock and leave it on your phones internal SD card, you don't have to root or get ROM manager. Place your new ROM on the internal card too. Just Odin to stock, allow to boot, and restart into recovery (3 button combo), install updates (twice) then use CWM to install zip from card (ROM you downloaded).
Sent from my SAMSUNG-SGH-I897 using XDA App
quarlow said:
It takes like ten minutes to odin back to stock. I do it every time, just feels like a cleaner install.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
One less time touching Odin is one less time tempting fate. But that's just me. I'm pretty sure every rom dev in here has bricked a phone at least once...
much agreed. less odin. less potential for problems.
roms do a wipe now. doesnt matter what you had on it 2.1 or 2.2
2.3 is the only rom version that has a different partition table.
there is no issue flashing a 2.2 rom over 2.1 or vice versa. how CAN you upgrade from 2.1 to 2.2?? CWM anyone? oh **** right!
the only issue with flashing over 2.2 is the 3e recovery... and thers a fix for that. you dont need to go back to 2.1 to avoid the signature verification error... @crystalhand...
quarlow said:
It takes like ten minutes to odin back to stock. I do it every time, just feels like a cleaner install. Plus all the devs put that in their instructions. I trust the devs.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Not all devs put it in their op. Some devs say flash first thru clockwork and only use odin when there are problems. Odin could be better used as a recovery tool only, not the first thing you do whenever you want to flash a new rom. Just my opinion.
Sent from my SAMSUNG-SGH-I897
1tontomato said:
Odin could be better used as a recovery tool only, not the first thing you do whenever you want to flash a new rom. Just my opinion.
Click to expand...
Click to collapse
EXACTLY as it should be.....
No, odin is potentially more dangerous than any standard rom flash. as has been mentioned, use in case your in some s
I've always flashed back to stock using Odin whenever I flash a new rom. Like someone else on this thread said, it just feels cleaner doing it that way. While I don't doubt you guys when you say it's dangerous, would anyone like to offer a brief explanation as to why that is? And would anyone be willing to guess at what the odds of a permanent brick might be? Are we talking something like 1 in every 10 flashes or more like 1 in 1000?
If it's closer to the first one then we really are playing with fire here but if the odds are more like the second one then I don't consider that much of a risk.
Juanmail15 said:
I've always flashed back to stock using Odin whenever I flash a new rom. Like someone else on this thread said, it just feels cleaner doing it that way. While I don't doubt you guys when you say it's dangerous, would anyone like to offer a brief explanation as to why that is? And would anyone be willing to guess at what the odds of a permanent brick might be? Are we talking something like 1 in every 10 flashes or more like 1 in 1000?
If it's closer to the first one then we really are playing with fire here but if the odds are more like the second one then I don't consider that much of a risk.
Click to expand...
Click to collapse
I highly doubt someone is going to give you a "odds" answer. Phones can be finicky and they often do weird things. The less you're "changing" things, the better. Odining back to stock then flashing again to the ROM of choice just adds another chance for something to go wrong. Not just cable falling out or battery falling out, just weird coincidence. When there's absoutely no reason to go back to stock, why take the chance? Just because you're programed to THINK it's cleaner doesn't mean it is. As has been said several times already, most roms do a complete wipe of the sd card so there's really no reason to odin or masterclear.
axis01 said:
I highly doubt someone is going to give you a "odds" answer. Phones can be finicky and they often do weird things. The less you're "changing" things, the better. Odining back to stock then flashing again to the ROM of choice just adds another chance for something to go wrong. Not just cable falling out or battery falling out, just weird coincidence. When there's absoutely no reason to go back to stock, why take the chance? Just because you're programed to THINK it's cleaner doesn't mean it is. As has been said several times already, most roms do a complete wipe of the sd card so there's really no reason to odin or masterclear.
Click to expand...
Click to collapse
+1
Odin should only be used as a "Oh S**T I bricked my phone" program. But then again, if you read and know what you're doing than it should never be "needed"
axis01 said:
I highly doubt someone is going to give you a "odds" answer. Phones can be finicky and they often do weird things. The less you're "changing" things, the better. Odining back to stock then flashing again to the ROM of choice just adds another chance for something to go wrong. Not just cable falling out or battery falling out, just weird coincidence. When there's absoutely no reason to go back to stock, why take the chance? Just because you're programed to THINK it's cleaner doesn't mean it is. As has been said several times already, most roms do a complete wipe of the sd card so there's really no reason to odin or masterclear.
Click to expand...
Click to collapse
Completely agree just want to clarify 1 thing. The roms don't do a complete wipe of the sdcard. The wipe the /data /cache and /system partitions, leaving the /sdcard completely intact, just like flashing to stock would. Master clear just reformats /sdcard partition and is not really needed as the os doesn't use this to function and including this in a rom would be catastrophic if the zip is in fact on the /sdcard partition you are wiping with it.
The most I do is clear cache, data and disable lagfix.
quarlow said:
If you download the CWM update.zip before you Odin to stock and leave it on your phones internal SD card, you don't have to root or get ROM manager. Place your new ROM on the internal card too. Just Odin to stock, allow to boot, and restart into recovery (3 button combo), install updates (twice) then use CWM to install zip from card (ROM you downloaded).
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
So you'd just drop the update.zip on your internal drive, drop the ROM in as well, boot into recovery and flash it that way?
Lancered said:
So you'd just drop the update.zip on your internal drive, drop the ROM in as well, boot into recovery and flash it that way?
Click to expand...
Click to collapse
Yup. That's how u do it, if you have no need to root before hand and back up, I'm assuming you've done that if I remember right you are the girl I told to brick her phone yesterday to return, is the replacement on eclair or froyo? Ig it on froyo you will have to get past the 3e recovery that's why I ask.
So i got cm7 on my phone last week and ever since i got it when i leave the phone on for more that 2 min the phone will just turn itself off and restart and show the cyanogenmod logo with the little android guy on the skateboard (same as once you turn on the device) and all the apps and everything is shut off. What is happening, is this normal?
Still looking for a solution
Flash back to stock to see if it does it there. Then reflash CM7.
Eyeronik said:
Still looking for a solution
Click to expand...
Click to collapse
Maybe you restored system data from a different ROM and it broke something. Flash back to stock and then follow the direction to a T on flashing CM7. Do not restore anything and see if you have the issue.
I used cm7 for 2 weeks to see what all the fuss is about. I had the problem you where describing. in my case it was caused by restoring too much stuff from titanium back up. follow the instructions and you shuld be fine.
After getting it working I did not like cm7 so I uninstalled it and went to the i9000 gingerbread based ROMs(I am using continuum) and dident look back.
Us cappy owners are fortunate to have such a rich developer community with so much to choose from.
Sent from my GT-I9000 using XDA Premium App
Yea this is the first rom i have put on it. I just got it a couple weeks ago. Im going to attempt to figure out how to flash back to stock. Thanks guys.
Move some apps to external and see if it still happens.
Sent from my SGH-I897 using XDA Premium App
People have been asking in the dev forum alot about how to have two roms on the same device. So i thought I would make a how to.
You do this at your own risk.
Things Needed:
external SD
Get CWM for droid3
SafeStrap for droid3
stable rom to use as nonsafe [put on external SD]
rom to use as safe [put on external SD]
TiBu
1. (make sure you are in nonsafe, if you don't know what this means then dont worry). Do a backup of everything you will want to keep with TiBu.
2. Put the backup on external SD or on dropbox.
3. Uninstall any existing recoveries.
4. Reboot device.
5. Install cwm.
6. Reboot into CWM Recovery and install stable rom.
7. Reboot device.
8. Uninstall CWM and Then install safestrap.
9. Reboot into safestrap recovery.
10. Use volume rockers to go to safe boot menu.
11. Toggle safesystem.
12. select install a zip
13. choose safe rom
14. DONE "]
The nonsafe system will now contain your stable rom. and the safe system will contain your 'experimental' or second rom. I recommend not putting any new or buggy roms as your nonsafe. And this is already considered a dangerous thing to do. And give a huge thanks to hashcode for providing us with safestrap and koush for cwm :]
I currently use MavRom as a nonsafe. Its extremely stable and has not caused any issues at all.
Also if you want to transfer the safe to the nonsafe, use tibu to entirely back up the rom, system and user apps, you can then restore it after flashing it to nonsafe. Make a new backup folder to put it in so you don't mix it up with other backups from different roms
Sent from my XT860 using xda premium
I can't seem to get this to work with Cm7 as Safe rom and Cm9 as my experimental. I got Steel Droid to boot up and stock but I'm starting to think any rom that isn't blur based (which is really only cyanogen) isn't able to be dual booted. I just get a black screen after the splash screen I've been trying for a week now. If anybody is willing to give it a shot just to see if its me then please let me know of your findings but Mavrom Liberty SD all of those I can boot its cm7.1 or Cm9 that won't...
Sent from my DROID3 using Tapatalk
Thwe blur based thing may be right. Im unsure, but cm7 to me personally shuld not be used as stable
Sent from my XT862 using Tapatalk
can somebody unite thiese 2 topics?
http://forum.xda-developers.com/showthread.php?t=1436380
Dri94 said:
Thwe blur based thing may be right. Im unsure, but cm7 to me personally shuld not be used as stable
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
Damnit man I would rather not have to run cm7 as my stable rom seeing how I have no front facing camera support but the other features that the blur based roms lack just make it impossible to use as a daily driver. I need control over which buttons are in the notification widget and a few of the other features cm provides and none of the blurless roms give me that unfortunately... I'm determined to get this to work if its the last thing I do lol
Sent from my DROID3 using Tapatalk
Whats not working about it ?
Sent from my XT862 using Tapatalk
Dri94 said:
Whats not working about it ?
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
I can't get cm7 to boot up past the safestrap splash screen.... I start out with bootstrap boot cm7 up and then remove bootstrap and install safestrap thus making cm7 my non safe or main rom but upon rebooting the phone I just get the black screen after the splash screen... I can get into safestrap and switch to safe mode and run whatever rom I last had there or flash any nandroids I had in non safe mode but whatever rom I had on prior to installing safestrap (cm7 or cm9) they won't actually reboot. I thought cm9 would work which would really be a hastle keeping that as my non safe rom and cm7 as my main one on the safe side thus leaving me to redo the entire process everytime a new cm9 is released but cm9 wouldn't boot up past the initializing apps screen that first pops up... It counts up to all the apps I have then just stays stuck on starting applications or whatever it says, cm7 doesn't even boot up beyond the splash screen...
Edit: And I know that I'm doing it right because I have got Steel Droid to dual boot before I just can't understand y blurfree roms can't boot in non safe mode
Sent from my DROID3 using Tapatalk
ill test it when i get home.
Sent from my XT862 using Tapatalk
Dri94 said:
ill test it when i get home.
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
Appreciate it *fingers crossed*
Sent from my DROID3 using Tapatalk
Im sorry. I got behind on some work, when i catch up ill get back to you.
Sent from my XT862 using Tapatalk
Dri94 said:
Im sorry. I got behind on some work, when i catch up ill get back to you.
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
No pressure man I do appreciate the response tho lol
Sent from my DROID3 using Tapatalk
Ill do it tonight when i install the new ics :]
Sent from my XT862 using Tapatalk
Dri94 said:
Ill do it tonight when i install the new ics :]
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
I was gonna do the same lol hilarious
Sent from my DROID3 using Tapatalk
Lol cool :] lets see if we can both get it
Sent from my XT862 using Tapatalk
Ok im gonna give this another shot tonight..... haven't had the time or patience especially since I think its gonna fail again but ill update with my progress.... gonna try cm7 as the non safe and aokp as the safe one...
Sent from my DROID3 using Tapatalk
Ok, time to feel like a total noob.
So, my idea was to use safestrap to install aokp on the safe partition and leave my stock (+root) rom on the unsafe one.
I had bootstrap installed, just to back up my stuff and whatnot, so, I uninstalled it, installed safestrap, put all the stuff needed for AOKP ( rom, gsm patch and gapps ) and rebooted the phone. I enabled the safe system, and flashed rom, patch and gapps. then I rebooted, and I got into a loop where I would see the motorola logo ( the still one, which says "dual core technology" or something like that), then I got the safestrap splashscreen and if I pressed search, or left the phone idle so it would boot on it's own, it would get me to the motorola logo again, and repeat the loop.
I had to go back to the unsafe system and luckily it's all still there, but, since that point I tried every combination that I could think off, with wipes and I've flashed even just the rom, between wipes, and still, nothing.
I'm thinking that safestrap is not being able to write on the partition, or something like that, but I don't know how to solve it.
Any Ideas?
EDIT: I checked with a root explorer on /preinstall ( which I understand is the /system folder for the safe system ) and all the data seems to be there, but it's just not booting. Which makes me even more confused
FLASHING ROMS WILL VOID YOUR WARRANTY AND COULD POTENTIALLY DAMAGE YOUR PHONE -- WHILE I MAKE EVERY ATTEMPT NOT TO LET THIS HAPPEN, IT'S STILL A RISK THAT YOU'RE TAKING. IF SOMETHING BAD SHOULD HAPPEN TO YOUR PHONE, PLEASE DON'T BLAME ME -- HENCE THIS WARNING.
This isn't so much a ROM announcement as it is a direction to find the unofficial nightly builds of CM9 for the Droid 4 (based on Motorola ICS leaks)
Download Here from ROMbot
Download GApps Here (04/29 Goo-Inside GApps Link).
FLASH THE GAPPS.ZIP FILE AFTER YOU FLASH THE ICS.ZIP
WHAT do I need to run this ROM?
- Rooted
- Running a Motorola ICS leak (.206, .208, .211, etc)
- I recommend that you run Safestrap v2.00 to install this. Here's how to use Safestrap
And you can download Safestrap for the Droid 4 (v2.x for ICS-leak users) here:
Safestrap « Hash-of-Codes
WHAT can I expect to work right now?
- 4G and basic phone function
- All sensors
- Camera, Panorama and Face-unlock
- Video Recording
- HD YouTube
- Netflix
Current Known Issues?
- Data connection is a work in progress. It's MUCH better than it used to be in the old ICS builds, however there is always room for improvement. Due to the "global" data connection style of stock Motorola ICS, this problem will probably continue to be worked on. Feedback is always appreciated, but if you see it posted already then there's a good chance I know about specific issues.
- Currently, there is a bug in the rotation display of the phone. What I mean is, that when you take the phone and rotate it, the display will squeeze in on itself and then pop back out. This is a *known* issue and I'm working very hard to fix it.
- The CM9 built-in Wifi Tether won't work. You need to use the "Wifi Tether" app that's bundled into the ROM. Once you open it, hit [menu] and "Settings". Select "Change Device-Profile" to "Generic ICS".
- I'm sure there's more, I'll update this list here in a bit.
WHO works on this?
Myself and @DHacker29 work as a team to build AOSP-based ROMs (and device setups) for several Motorola phones. Typically, I do the coding work in C, C++ or Java while DHacker maintains the blobs, runs merges with CM/AOKP sources, and solves device issues which require less coding.
WHAT is a "nightly"?
It's an automated build ran from a script. It basically: deletes the current set of output files, sync's with github, and then attempts to do a brand new build. It can break at times, in which case we'll fix it (usually this happens when there are framework changes which didn't get merged).
WHY would I want this?
- Since we work on several devices, this is how we decided to start keeping builds up-to-date. Rather than spend several hours a week on builds and uploading. This happens automatically every night around 2am PST.
- It's up to you the community to identify good "stable" builds.
Feel free to follow me on Twitter as I do sometimes make announcements there before I do forum postings:
Hashcode (@Hashcode0f) on Twitter
We maintain all of our code at github:
https://github.com/o...ns/STS-Dev-Team
Screenshots:
[ COMING SOON ]
Reserved for future use
Looking great Hash! Thanks for your work.
my excitement is robust
Just tried installing using safestrap and bootlooped. Had to hard reboot to get back to safestrap recovery and back in to stock ROM. Anyone else tried this yet? Might try again tonight when I get home and let the battery charge up a bit.
Sent from my DROID4 using XDA
kwyrt said:
Just tried installing using safestrap and bootlooped. Had to hard reboot to get back to safestrap recovery and back in to stock ROM. Anyone else tried this yet? Might try again tonight when I get home and let the battery charge up a bit.
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
I was able to get it installed and working just fine under safestrap. Did you wipe data, cache, and dalvick?
jgardner said:
I was able to get it installed and working just fine under safestrap. Did you wipe data, cache, and dalvick?
Click to expand...
Click to collapse
That was it. First time I've used safestrap. I figured since I did not have a previous ROM installed in Safemode that I did not need to wipe. Went back in, wiped data and cache and now I am in business. Looking good Hash!
One question though, I tried to wipe dalvik and it said it could not find sd-ext. Any idea what that is about?
Edit: Feels so good to be flashing ROMs again!!!
kwyrt said:
That was it. First time I've used safestrap. I figured since I did not have a previous ROM installed in Safemode that I did not need to wipe. Went back in, wiped data and cache and now I am in business. Looking good Hash!
One question though, I tried to wipe dalvik and it said it could not find sd-ext. Any idea what that is about?
Edit: Feels so good to be flashing ROMs again!!!
Click to expand...
Click to collapse
I did the exact same thing (not wiping on a fresh safestrap). I believe that message about the sd-ext is normal when wiping dalvik.
kwyrt said:
That was it. First time I've used safestrap. I figured since I did not have a previous ROM installed in Safemode that I did not need to wipe. Went back in, wiped data and cache and now I am in business. Looking good Hash!
One question though, I tried to wipe dalvik and it said it could not find sd-ext. Any idea what that is about?
Edit: Feels so good to be flashing ROMs again!!!
Click to expand...
Click to collapse
I believe the reason behind that message is that the Dalvik cache is not stored on the sd-ext, but rather the sd, which is internal. Since theres technically 2 SD cards on our device, it looks for the dalvik on the first one. A dev would probably have better advice on it though,....I may be wrong.
kwyrt said:
That was it. First time I've used safestrap. I figured since I did not have a previous ROM installed in Safemode that I did not need to wipe. Went back in, wiped data and cache and now I am in business. Looking good Hash!
One question though, I tried to wipe dalvik and it said it could not find sd-ext. Any idea what that is about?
Edit: Feels so good to be flashing ROMs again!!!
Click to expand...
Click to collapse
Safestrap checks for a dalvik cache under a theoretical /sd-ext partition on the external SD. It's almost never there tho. So you can safely ignore that message.
So one thing I have noticed switching between stock and the ICS ROM is the battery level is not consistent. Reads 60% on stock. Reads 26% on ICS. Anybody know what's up with that?
Sent from my DROID4 using XDA
kwyrt said:
So one thing I have noticed switching between stock and the ICS ROM is the battery level is not consistent. Reads 60% on stock. Reads 26% on ICS. Anybody know what's up with that?
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
I havent flashed this one just yet but i know on my droid 3 i let the battery charge all the way up and then wiped battery stats and all was fine after that.
Sent from my DROID4 using XDA
thanks hashcode! you're the man!
Appreciate the Rom.. Runs very nicely on Droid 4. Easy install.
I know HW video is being worked on. Will that fix or update allow Movie Studio to work?
Very interested and excited about Ice Cream Sandwich and future updates to this Rom
Installed and loving it so far.
The one thing I've noticed, the phone gets really hot, and the battery usage is pretty poor. I actually watched my battery percentage drop while doing my installs of all the apps that I had to download.
I lost about 3% during that process, even when plugged into the wall charger.
I'll keep an eye on it, as I'm close to a charger at all times, so bad battery life doesn't affect me too much.
Can't wait for BT to work, as that would be the last piece in a daily driver for me.
EDIT - just discovered I'm having issues with Chrome Beta. I've never used it before, but it won't load any websites. I'll DL Dolphin for the time being, but would love to try out Chrome. Just wondering if anyone else is running into this.
Im fully installed and Chrome Browser works great along with all other functions on my end.
As for battery percentage Im not sure if im having your problem with excess heat....
doubleokneegro said:
Im fully installed and Chrome Browser works great along with all other functions on my end.
As for battery percentage Im not sure if im having your problem with excess heat....
Click to expand...
Click to collapse
Ok found out it was my charger. For some reason it wasn't actually charging and was just causing heat. Plugged it into a different charger and all is well now.
still no love with Chrome though.
kwyrt said:
Just tried installing using safestrap and bootlooped. Had to hard reboot to get back to safestrap recovery and back in to stock ROM. Anyone else tried this yet? Might try again tonight when I get home and let the battery charge up a bit.
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
Im in this same predicament.. Uh.. How do i hard reset? Hold power? That doesnt seem to be working for me....
---------- Post added at 10:16 PM ---------- Previous post was at 10:07 PM ----------
gangrif said:
Im in this same predicament.. Uh.. How do i hard reset? Hold power? That doesnt seem to be working for me....
Click to expand...
Click to collapse
Nevermind, google has solved my despair.
http://www.technipages.com/how-to-reset-frozen-droid-4.html
Thanks.
Absolutely love this ROM!!!!! One request though, what do I need to install to get webtop working? Just got the lapdock 500 a couple hours ago and love this ROM to much to give it up
Sent from my DROID4 on ICS
Everything seems to be working perfectly for me, even the camera is working properly. I haven't tried bluetooth yet, but I'm not too worried about it, I barely use it. Wifi connects and works, no problem there. I noticed a slight lag after installing setCPU but now it seems fine. I'll check tomorrow to see how the battery life is but for now every things pretty smooth. Thanks!
Hi all, I have looked all over the place, I need help.
Here are my Current "About Device"
Hardware Version: I800.0.3
Model Number: SCH-I800
Firmware: 2.3.5
Baseband Version S:I800.0.3V.E104
Kernel Version: 2.6.35.7-dsb9938.VZW.GTab.E104.1.1.2
I have looked at the "back to stock" threads, multiple DL links are no longer available.
I had rooted, and Flashed a "Cube" ROM quite some time ago. A while after that I messed something up with the built in "overclocking" type app. Set it to the side and kind of forgot about it. Fast forward to know, I would like to get it working for my son to use, but there are a few issues that keep us from using it. I kept getting all sorts of random force closes, so I was able to get in recovery, and tried to wipe everything. This somewhat worked for a while, but now I am getting a force close from Facebook (which isn't installed, and I have narrowed it down to a contact synching issue) and I keep getting a popup for an OTA system update. I have tried to do the update, but I think the recovery is keeping it from completing.
Long story short, I know this device is a bit older, but where should I start from? I am ok with a fresh, wipe everything start. Not looking for a crazy ROM, but just a everything works ROM. I am ok with GB, ICS, etc, I just want it to be fully functioning. I plan on adding the tablet on my account so I can stop tethering for my son to use it. This has been the only device I have ever needed to ask for help, I am just not so used to the ODIN type stuff.
Thanks in advance.
I tried to do a reset, and wipe from CW recovery. Then restore, it has been stuck on the black with white Samsung screen for about 10 minutes. Don't know what else to do right now.
Sent from my SCH-I605 using xda premium
http://forum.xda-developers.com/showthread.php?p=42913151
Sent from my GT-N7100 using xda app-developers app
priyana said:
http://forum.xda-developers.com/showthread.php?p=42913151
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Much appreciated, long/slow download, but hope it works.
Wish I could get into recovery, I would just flash from the card.
Sent from my SCH-I605 using xda premium
There's a very new thread that should help you get back to stock. http://forum.xda-developers.com/showthread.php?t=2383201
As far as what to put on it, I highly recommend this CM10.1 ROM. It runs very smoothly, but if you want to activate data, I think you have to go back a bit for a working kernel. http://forum.xda-developers.com/showthread.php?t=2043421 The CDMA version is the p1c.
I don't know if you have come across this yet, but unlike any device I had flashed before, the GTab recovery has to be flashed with a corresponding kernel. You can't just flash the recovery to get into recovery.