Related
Seen an alpha 3 ICS rom. Can I just download that and flash it over my current rom or does it habecto be done certain way. I've flashed before on my evo but this seems a little bit more complicated
Sent from my SPH-P100 using XDA App
I'd rather go the full procedure they describe within their thread - imho especially you have needs for clockworkmod. Found that to be a quite safe way for me.
I would I just don't have access to a pc. Does ICS run fine on your tablet. Is it worth it
Sent from my SPH-P100 using XDA App
Once you have CWM Recovery installed, getting the ICS Alpha on your tab is not difficult if it's listed as supported in the thread.
Only thing: This is an ALPHA build. That means many things are not functional. The build is aimed at developers/testers.
Having given a shot at it, this build is surely not a daily driver for someone who needs its tab to be functional and reliable. Many of those problems have work arounds however but since the tablet is not mostly used by myself, I did not take the risk of having it be unreliable...
In short: it should work and not eat your hamster... But it is not a fully functional rom yet, be prepared for some trouble... Be sure you know how to go back in case of trouble... and read instructions carefully
If you want a good ICS rom here ya go. FYI!!! THIS IS FOR CDMA TABS!!!
Get rooted and CWM'd via Rodderick's thread in our Development section.
From there do the following (all credit to JT from here on out)
Download http://k.22aaf3.com/jt1134/vzwtab/cwm-recovery-5.0.2.7.tar
Extract the contents. You will have two files zImage and recovery.bin
Odin these two files to your tab while your tab is plugged in to the PC and in Download mode. This will bring your clockworkmod up to 5.0.2.7 which is a must to install the rom I'm about to link.
Next go to this thread
http://rootzwiki.com/topic/11697-rom-cdma-aosp-ics-cm9-build-31-0104-x-2/
At the bottom of the first post download the 3.1 ROM the 3.1 Patch and the gapps files.
Once those are downloaded boot your tab up to normal operations and plug it into your PC again. Now transfer those three files to your tab.
Boot up into clockwork recovery wipe the cache, dalvik, and do a factory data reset. Then flash the 3.1 file first, then flash the 3.1 Patch, then flash the gapps files.
If everything says it installed correctly the only things that won't be working are camera (which it does work in panorama mode) and possibly 3G. (Never tested 3G as I only use wifi).
Can you please post pictures and how can I check which cwm I already have? If I already have 5.0 can I just go ahead and flash? One more thing is this a whole new ICS or the ones going around. Thank you much
So I checked and I got 4.0 cwm. With that said. I don't have access to a pc. Is there any other way to upgrade to 5.0 cwm? PLEASE someone reply with yes. I'm getting bored with this andcwpuld like to try ICS. Thanks
rjumawan said:
So I checked and I got 4.0 cwm. With that said. I don't have access to a pc. Is there any other way to upgrade to 5.0 cwm? PLEASE someone reply with yes. I'm getting bored with this andcwpuld like to try ICS. Thanks
Click to expand...
Click to collapse
Without access to a PC I think you are making life very difficult for yourself.
You do not state what Tab you have; below I linked to the install for the P1010 only...I did this for reference because you will see it required Odin to flash it i.e. access to a PC.
http://forum.xda-developers.com/showpost.php?p=20195348&postcount=1
Thank for the reply. Yeah I know it makes it, harder just seeing if there was a way around it. I'm playing with the sprint galaxy tab. Not much to play with out there for it.
How to install a custom rom (eg. CM9, Ice Cream Sandwich, Liberty, Maverick, SteelDroid) to a Bell XT860 without losing the ability to revert to stock later.
Why this guide?
I noticed over time that my phone has become slower and more frustrating to use. For example, long pauses when trying to open a program - sometimes it takes an easy 10 or more seconds to open the dialer and dial a number.
I wanted to try a custom rom, but was concerned about the ability to get back to stock, if something goes wrong, or to be able to take advantage of a Bell update if they release a new one. Thanks to the hard work of many on this board, I have discovered how to make this possible and wanted to share with others.
Big thanks to DoomLord, HashCode, Enderoid, Rick#2, Dasilva333, Willis111 and others. Please feel free to make corrections to these instructions.
Note: This has been tested with an XT860 on Bell 2.3.6 firmware. This will probably NOT work on v2.3.4 So if you have 2.3.4, upgrade to 2.3.6 and then these instructions should work. When I first got the phone, it was at 2.3.5 and later was updated OTA (Over the air) by Bell to 2.3.6. To check which firmware you have, Home Screen / Settings / About Phone
Needed:
1. Windows pc (someone else more knowledgeable could probably tell you how to make this work on a Mac)
2. USB cable for connecting your phone.
3. Rooting tool, I highly recommend zergRush method by DoomLord found here:
http://forum.xda-developers.com/showthread.php?t=1321582
4. Safestrap by hashcode
http://hash-of-codes.blogspot.com/p/android-downloads.html
5. Custom rom of your choice.
Step 1:
Root your phone using the DoomLord tool. I used version 3. It was really easy, just follow the instructions on the link above.
Step 2:
Backup existing user programs that you might want to restore on a new system. I used Titanium Backup Pro but there are others.
Step 3:
Please read this page carefully
http://hash-of-codes.blogspot.com/p/how-to-safestrap.html to download and install safestrap v1.08. Note, you should remove any other type of bootstrap (eg. ClockworkMod, ROM Manager) before installing Safestrap.
Step 4:
Now you should be ready to download and try a custom rom. Make sure to do a backup (“Nandroid” backup) of your working system before you try a custom rom so you have something to fall back on in case something goes wrong or you want to return to stock.
Find a rom, download it and save it to a location on your sdcard or ext-sdcard. There’s lots of good candidates for you to test and a good thread with some reviews here:
http://forum.xda-developers.com/showthread.php?t=1384676
To do this, power down your phone after you have run safestrap and clicked to make recovery active. If you did it right, when you turn it on again, you should see a different splash screen that gives you a few seconds to enter the recovery menu by pressing the “menu” button on you device.
You should see “Safestrap Recovery v1.08” and below that “Safe System is: DISABLED”
on a black screen with some green menu choices.
Use the volume keys to scroll up/down and select “backup and restore” by pressing the power button.
The screen should change to show the Nandroid backup menu. You need to make a Nandroid backup of your existing (working) system, which is simply a snapshot of the exact system with all programs, settings, sms’s, call logs, etc. It’s like a snapshot in time in case you need to revert. Select “backup”, then select Internal or External SD Card for the location (I’m not sure it it matters for the location).
Safestrap will backup your system to a Nandroid backup. It takes a few minutes.
After the backup is complete, you can enable the Safe System where you will install custom roms. Scroll down and select “safe boot menu”, then “Toggle Safe System”, then on the next screen confirm your selection. It will backup the original system to a safe area where it can’t be modified (unless you are an advanced user and install a different version of Safestrap but that’s beyond the scope of these instructions).
After Safe System is: ENABLED, scroll down to “Install zip from sdcard”, select your rom, install, reboot and enjoy.
To revert back to your original system, follow these steps:
1. Turn off your phone and reboot into SafeStrap recovery menu.
2. Turn off SafeSystem. (Safe boot menu -> Toggle Safe System)
3. Restore your nandroid backup and reboot.
If you wanted to go further back to stock you could uninstall Safestrap and even unroot using DoomLord’s zergRush tool, which would put you back to stock.
I think that’s it. Hopefully this guide will be helpful to others who want to try a new rom without losing the ability to revert back to stock Bell.
ncho2233 said:
How to install a custom rom (eg. CM9, Ice Cream Sandwich, Liberty, Maverick, SteelDroid) to a Bell XT860 without losing the ability to revert to stock later.
Why this guide?
I noticed over time that my phone has become slower and more frustrating to use. For example, long pauses when trying to open a program - sometimes it takes an easy 10 or more seconds to open the dialer and dial a number.
I wanted to try a custom rom, but was concerned about the ability to get back to stock, if something goes wrong, or to be able to take advantage of a Bell update if they release a new one. Thanks to the hard work of many on this board, I have discovered how to make this possible and wanted to share with others.
Big thanks to DoomLord, HashCode, Enderoid, Rick#2, Dasilva333, Willis111 and others. Please feel free to make corrections to these instructions.
Note: This has been tested with an XT860 on Bell 2.3.6 firmware. This will probably NOT work on v2.3.4 So if you have 2.3.4, upgrade to 2.3.6 and then these instructions should work. When I first got the phone, it was at 2.3.5 and later was updated OTA (Over the air) by Bell to 2.3.6. To check which firmware you have, Home Screen / Settings / About Phone
Needed:
1. Windows pc (someone else more knowledgeable could probably tell you how to make this work on a Mac)
2. USB cable for connecting your phone.
3. Rooting tool, I highly recommend zergRush method by DoomLord found here:
http://forum.xda-developers.com/showthread.php?t=1321582
4. Safestrap by hashcode
http://hash-of-codes.blogspot.com/p/android-downloads.html
5. Custom rom of your choice.
Step 1:
Root your phone using the DoomLord tool. I used version 3. It was really easy, just follow the instructions on the link above.
Step 2:
Backup existing user programs that you might want to restore on a new system. I used Titanium Backup Pro but there are others.
Step 3:
Please read this page carefully
http://hash-of-codes.blogspot.com/p/how-to-safestrap.html to download and install safestrap v1.08. Note, you should remove any other type of bootstrap (eg. ClockworkMod, ROM Manager) before installing Safestrap.
Step 4:
Now you should be ready to download and try a custom rom. Make sure to do a backup (“Nandroid” backup) of your working system before you try a custom rom so you have something to fall back on in case something goes wrong or you want to return to stock.
Find a rom, download it and save it to a location on your sdcard or ext-sdcard. There’s lots of good candidates for you to test and a good thread with some reviews here:
http://forum.xda-developers.com/showthread.php?t=1384676
To do this, power down your phone after you have run safestrap and clicked to make recovery active. If you did it right, when you turn it on again, you should see a different splash screen that gives you a few seconds to enter the recovery menu by pressing the “menu” button on you device.
You should see “Safestrap Recovery v1.08” and below that “Safe System is: DISABLED”
on a black screen with some green menu choices.
Use the volume keys to scroll up/down and select “backup and restore” by pressing the power button.
The screen should change to show the Nandroid backup menu. You need to make a Nandroid backup of your existing (working) system, which is simply a snapshot of the exact system with all programs, settings, sms’s, call logs, etc. It’s like a snapshot in time in case you need to revert. Select “backup”, then select Internal or External SD Card for the location (I’m not sure it it matters for the location).
Safestrap will backup your system to a Nandroid backup. It takes a few minutes.
After the backup is complete, you can enable the Safe System where you will install custom roms. Scroll down and select “safe boot menu”, then “Toggle Safe System”, then on the next screen confirm your selection. It will backup the original system to a safe area where it can’t be modified (unless you are an advanced user and install a different version of Safestrap but that’s beyond the scope of these instructions).
After Safe System is: ENABLED, scroll down to “Install zip from sdcard”, select your rom, install, reboot and enjoy.
To revert back to your original system, follow these steps:
1. Turn off your phone and reboot into SafeStrap recovery menu.
2. Turn off SafeSystem. (Safe boot menu -> Toggle Safe System)
3. Restore your nandroid backup and reboot.
If you wanted to go further back to stock you could uninstall Safestrap and even unroot using DoomLord’s zergRush tool, which would put you back to stock.
I think that’s it. Hopefully this guide will be helpful to others who want to try a new rom without losing the ability to revert back to stock Bell.
Click to expand...
Click to collapse
Good writeup. As a note when your switch back to nonsafe you don't need to restore a nandroid. Actually with safestrap you should rarely have to restore a nandroid as its next to impossible to screw up your device so bad that a restore is required. The stock bell /system stays nice and untouched
Sent from my XT860 using xda premium
Dont you just root, install safestrap and flash paritions to preinstall from stock(to avoid not being able to return to true stock) and not flash the og /system? Obviously works on 2.3.4, 2.3.6 etc any rootable rom capable of running safestrap. You should be able to even use my rom to return to stock deodexed by flashing to /system(non-safe) and removing any custom recovery. It should be very easy to convert that or the og dumps into a system.img for use with rsdlite and even the rest of the stock img files. I'll take a look at it this aft. Thanks for the write up, hope some of this info helps.
Maybe this is the wrong place to ask, but XT860 threads are few and far between in this droid 3 section. But I've got a few questions about this method.
First off, how safe is this from start to finish? I'm by no means new at the whole installing custom roms thing, but there have most definitely been times on all three of the devices I've installed roms on (Nook Color, Milestone, Transformer) where I've gotten a non-booting device that was fixed either because it was so easy to just go into CWM or RSDlite and flash a new rom or revert to stock. Doing anything (I'm not even rooted yet) on my XT860 kind of scares me, because we don't have an sbf or anything. This method seems like its the closest thing we've got, but new things are scary.
Secondly, I read somewhere that ICS uses a different kernel than GB. Would this method be able to deal with that or are we boned (i.e. stuck with the GB kernel and hackarounds) until Moto randomly decides to unlock the bootloader and we can rewrite everything?
And lastly, we can root on bell now? Last time I'd looked into it, I seem to remember flashing firmware from another country and without an easy way to get back to stock, that kind of killed it for me.
Once again, sorry that some of this is kind of off topic, its just kind of hard to know where to read while we're piggybacking on the droid 3 forum.
Tyfighter said:
Maybe this is the wrong place to ask, but XT860 threads are few and far between in this droid 3 section. But I've got a few questions about this method.
First off, how safe is this from start to finish? I'm by no means new at the whole installing custom roms thing, but there have most definitely been times on all three of the devices I've installed roms on (Nook Color, Milestone, Transformer) where I've gotten a non-booting device that was fixed either because it was so easy to just go into CWM or RSDlite and flash a new rom or revert to stock. Doing anything (I'm not even rooted yet) on my XT860 kind of scares me, because we don't have an sbf or anything. This method seems like its the closest thing we've got, but new things are scary.
Secondly, I read somewhere that ICS uses a different kernel than GB. Would this method be able to deal with that or are we boned (i.e. stuck with the GB kernel and hackarounds) until Moto randomly decides to unlock the bootloader and we can rewrite everything?
And lastly, we can root on bell now? Last time I'd looked into it, I seem to remember flashing firmware from another country and without an easy way to get back to stock, that kind of killed it for me.
Once again, sorry that some of this is kind of off topic, its just kind of hard to know where to read while we're piggybacking on the droid 3 forum.
Click to expand...
Click to collapse
Yes we can root, there is no need to flash any other countries fastboot files as long as you are on bell 2.3.6. While bell doesn't have a fastboot package yet(sbf) if you borked your device you can use motofastboot to flash just /system from the fastboot package of another country, and then restore a backup, thus everything stays bell stock.
The best advice is to use safestrap and only flash the safemode. You should always be able to get into CWR with safestrap
And yes we are stuck with the GB kernel for now, which is part of the reason developing ics roms has been so painful
Sent from my XT860 using xda premium
This process does not work for me...
When I load SafeStrap 1.08, I get Recovery State: Not Installed
I try and click the "Install Recovery" button and it goes through a process (preparing something, obtaining root, etc) but the Recovery State never changes
I have an XT860 from Bell (2.3.6) that is running on Rogers (unlocked).
Root works fine for TiBu and Root Explorer....The SuperUser entry for SafeStrap lists allowed and logs a whole bunch of "granted".
Any thoughts?
Caz666 said:
This process does not work for me...
When I load SafeStrap 1.08, I get Recovery State: Not Installed
I try and click the "Install Recovery" button and it goes through a process (preparing something, obtaining root, etc) but the Recovery State never changes
I have an XT860 from Bell (2.3.6) that is running on Rogers (unlocked).
Root works fine for TiBu and Root Explorer....The SuperUser entry for SafeStrap lists allowed and logs a whole bunch of "granted".
Any thoughts?
Click to expand...
Click to collapse
Perhaps you don't have su binary properly installed. I've had this happen with bootstrap. Check that you have su in both /system/bin and /system/xbin
Sent from my XT860 using xda premium
Close...it was busybox. It was present, but borked. Nuked and reloaded..problem fixed.
Many thanks to hashcode for the pointer to busybox being most likely.
Sent from my XT860 using xda premium
Caz666 said:
Close...it was busybox. It was present, but borked. Nuked and reloaded..problem fixed.
Many thanks to hashcode for the pointer to busybox being most likely.
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Now that you say that I remember someone else having the same issue and it turned out to be busybox. I had nearly the same problem with the bootstrap and it ended up being su missing from xbin
Sent from my XT860 using xda premium
OK I tried this and it works perfectly. Thanks man. This is what I needed.
Finally got around to trying this. I'd been in the middle of a move with my pc in a box, but now I've got ICS fully up and running (save for the whole camera thing). Panicked halfway through when I got into a bootloop, but then I wiped everything (forgot the cache the first time) and then everything worked.
I got wifi tether working with the app that was included in the rom, but have any of you had any luck with doing it natively through the settings? I only ask because being able to trigger it from the status bar would be pretty sweet.
edit: did some looking around and it looks like maybe its an issue with shoehorning GSM into a CDMA rom. At least that's the feel I've been getting, I'd love to be wrong.
Thanks for this thread! I hadn't realized there had been developments for the XT-860.
I had unlocked (for use on the Fido network)/rooted my phone and it was working great, then the OTA update from Bell came and I installed that. Now, I seem to have lost root privileges (I guess, obviously).
So, I guess I'm pretty much back to square one.
I would love some advice on how to proceed! I'm thinking of following your directions, and am interested in recommendations for which ROM to install.
What is the problem with the camera with ICS? I use the camera on our phone pretty often so I want a ROM that doesn't break it. Does anyone have some links to some good ROMs to try that work with the XT-860?
twitchcity said:
Thanks for this thread! I hadn't realized there had been developments for the XT-860.
I had unlocked (for use on the Fido network)/rooted my phone and it was working great, then the OTA update from Bell came and I installed that. Now, I seem to have lost root privileges (I guess, obviously).
So, I guess I'm pretty much back to square one.
I would love some advice on how to proceed! I'm thinking of following your directions, and am interested in recommendations for which ROM to install.
What is the problem with the camera with ICS? I use the camera on our phone pretty often so I want a ROM that doesn't break it. Does anyone have some links to some good ROMs to try that work with the XT-860?
Click to expand...
Click to collapse
Use zergrush to root 2.3.6. Picture camera works in ics but you can't record or view video. There's some good gb roms. Give me a few and il shoot you some links
Sent from my XT860 using xda premium
Starting the process now. Can someone please send me a link or two to a good ROM for the XT-860?
I would prefer ICS (I want Chrome on my phone), but if that causes to many problems, a GB recommendation would be fine.
Bell SBF available at the following URL:
http://sbf.droid-developers.org/umts_solana/list.php
ncho2233 said:
How to install a custom rom (eg. CM9, Ice Cream Sandwich, Liberty, Maverick, SteelDroid) to a Bell XT860 without losing the ability to revert to stock later.
Click to expand...
Click to collapse
If there was any interest at all I would have just made a 100% stock bell 2.3.6 that you flash with CWM and then remove the recovery to be 100% stock but the deodex version seems to be good enough, especially to get a phone with a physical problem past bell/motorola reps. I'm downloading and mirroring that bell sbf right now, very nice find pfak! I made a new thread since you didn't but just linked to your post.
twitchcity said:
Starting the process now. Can someone please send me a link or two to a good ROM for the XT-860?
I would prefer ICS (I want Chrome on my phone), but if that causes to many problems, a GB recommendation would be fine.
Click to expand...
Click to collapse
There are many roms on this part of the sub-forum, just look around or try a search with [ROM] as your query (might not work so hot in the d3 dev subforum )
I
twitchcity said:
Starting the process now. Can someone please send me a link or two to a good ROM for the XT-860?
I would prefer ICS (I want Chrome on my phone), but if that causes to many problems, a GB recommendation would be fine.
Click to expand...
Click to collapse
Willis111 said:
If there was any interest at all I would have just made a 100% stock bell 2.3.6 that you flash with CWM and then remove the recovery to be 100% stock but the deodex version seems to be good enough, especially to get a phone with a physical problem past bell/motorola reps. I'm downloading and mirroring that bell sbf right now, very nice find pfak! I made a new thread since you didn't but just linked to your post.
There are many roms on this part of the sub-forum, just look around or try a search with [ROM] as your query (might not work so hot in the d3 dev subforum )
I
Click to expand...
Click to collapse
I have a number of xt860 adapted roms on my computer. Give me a few days to contact the devs and such and I'll see if I can get a stickied thread with xt860 ready roms to make it easy for new comers. Also willis, ignore my other post to you, I'll include that info in aforementioned thread if I can get it going
Sent from my GT-P5113 using xda premium
Endoroid said:
I have a number of xt860 adapted roms on my computer. Give me a few days to contact the devs and such and I'll see if I can get a stickied thread with xt860 ready roms to make it easy for new comers. Also willis, ignore my other post to you, I'll include that info in aforementioned thread if I can get it going
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
You can just use one of the patches (small xt860 patches) to get any rom working on our phones as far as I know.
pfak said:
Bell SBF available at the following URL:
http://sbf.droid-developers.org/umts_solana/list.php
Click to expand...
Click to collapse
thank you for this it will help a ton of peeps
I used AdamOutler 's guide to root and put a custom ROM on Captivate 2.2 found here:
http://forum.xda-developers.com/showthread.php?t=1012769
And everything went swiftly. AT THIS POINT, I MADE A NANDROID BACKUP
I then wanted to step up to an Ice Cream Sandwich ROM, which was the main purpose of my rooting in the first place. So, I downloaded the ROM found in this forum, as it is the most popular amongst the forums, so to seem. I found it here:
http://forum.xda-developers.com/showthread.php?t=1363760
Well I downloaded the ROM straight from my phone on the browser, then put it on the Root of my internal memory.
I booted into recovery, Factory Reset/Wipe Cache Partition/Wipe Dalvik Cache.
Went to install .zip from SD card, then clicked on install the ICS ROM.
Began to seem as if it was updating, then the phone shut off, started bootlooping.
No big deal I thought, just boot into recovery, right? I booted into recovery. It went from the Red CWM that i had seen before, to a Blue one.
I selected my nandroid backup, and it gave me all sorts of errors.
Got to the point where CWM was acting as if it could even find where it was supposed to work from?
Now I have the Phone>!<Computer on the black screen when I try to turn on.
Anyone else ever had this problem, or could someone tell me what went wrong? Not in a huge rush as this is just my development phone, but do I need to go ahead and use the Odin3 One Click to do a full complete restore or is there any way of saving what I had?
Thanks guys, God Bless.
LOL OOPS thought i was in the dev section.... ignore..help below.
xCaptivateRx said:
I used AdamOutler 's guide to root and put a custom ROM on Captivate 2.2 found here:
http://forum.xda-developers.com/showthread.php?t=1012769
And everything went swiftly. AT THIS POINT, I MADE A NANDROID BACKUP
I then wanted to step up to an Ice Cream Sandwich ROM, which was the main purpose of my rooting in the first place. So, I downloaded the ROM found in this forum, as it is the most popular amongst the forums, so to seem. I found it here:
http://forum.xda-developers.com/showthread.php?t=1363760
Well I downloaded the ROM straight from my phone on the browser, then put it on the Root of my internal memory.
I booted into recovery, Factory Reset/Wipe Cache Partition/Wipe Dalvik Cache.
Went to install .zip from SD card, then clicked on install the ICS ROM.
Began to seem as if it was updating, then the phone shut off, started bootlooping.
No big deal I thought, just boot into recovery, right? I booted into recovery. It went from the Red CWM that i had seen before, to a Blue one.
I selected my nandroid backup, and it gave me all sorts of errors.
Got to the point where CWM was acting as if it could even find where it was supposed to work from?
Now I have the Phone>!<Computer on the black screen when I try to turn on.
Anyone else ever had this problem, or could someone tell me what went wrong? Not in a huge rush as this is just my development phone, but do I need to go ahead and use the Odin3 One Click to do a full complete restore or is there any way of saving what I had?
Thanks guys, God Bless.
Click to expand...
Click to collapse
Different kernels have different colour recoveries. kernels change with rom.
Different CWM version recoveries are incompatible.
Almost anyone that has flashed a samsung galaxy phone has seen that screen, and it is correctly written " Phone /!\ PC " (you can choose to underline the /!\ if you want to be fancy). it is called the "soft brick screen" hint hint.. go search.
yes
yes. restore with same kernel you used to back it up.
TRusselo said:
Different kernels have different colour recoveries. kernels change with rom.
Different CWM version recoveries are incompatible.
Almost anyone that has flashed a samsung galaxy phone has seen that screen, and it is correctly written " Phone /!\ PC " (you can choose to underline the /!\ if you want to be fancy). it is called the "soft brick screen" hint hint.. go search.
yes
yes. restore with same kernel you used to back it up.
Click to expand...
Click to collapse
Very good responce...however after odin3 one clicking back to stock 2.1 eclair, I lost my clockwork mod folder that was on the internal SD, of course. Rookie mistake, I should've definately copied it on to the external SD card. Thanks for informing me of proper terminology. Also, after downloading rom manager and flashing, booting recovery, I can only access cwm through the rom manager, the three button fix doesn't work.
Why was this moved? I posted in general..
because you have a question/problem
rom manager is only used with 2.1 (for captivate). doesnt work on 2.2 or 2.3.X or 4.0.X
in all newer versions of android we "bake" cwm into the custom kernels we package into the custom roms. so there is no stock recovery and you dont need the update.zip.
dunno why you would flash all the way back to 2.1... EWWW.
in the dev section there is a sticky called odin master collection. use a newer stock rom. the master collection also has stocks versions, pre-packcaged with a custom cwm kernel so you can skip a step of getting it after going back to stock.
Do we know why this happened in the first place? Incompatible kernel? Is there a guide somewhere for moving from GB to ICS?
Sent from my SGH-I897 using XDA App
I thought you had to have GB bootloaders before you flashed any ICS roms ? I know I've read that ,then again I've read 10,000 threats and sometimes it becomes mind numbing.
Do you not have to flash back to 2.1 after having these problems? Right now my phone is at the soft brick screen, no button combo working. Not recognized by the computer either. I'm heading out to radio shack and make a USB jig in a bit. I'd love to just flash straight up to a gingerbread ROM if I can possibly get this thing in download mode. Anybody help a brotha out!
Edit: the sim is not activated, I just run it off Wi-Fi because big red is my carrier. This is my development phone. So I can't just KIES update to whatever the newest is.
Sent from my DROID X2 using XDA App
Any firmware should work, no need to go all the way to eclair...just flash gingerbread.
Don't think its been mentioned yet but when going from 2.2 to ICS, you have to flash the rom twice to get out of the bootloops. Sounds like you were at that point but when you flashed your nandroid instead of the ICS rom again, your phone must not have liked it.
aww.W.T.F? said:
I thought you had to have GB bootloaders before you flashed any ICS roms ? I know I've read that ,then again I've read 10,000 threats and sometimes it becomes mind numbing.
Click to expand...
Click to collapse
Not all ICS ROM's require GB bootloaders. I ran THS, and am now on vibranturk's AOKP and I came straight from 2.1
I think the issue was you're supposed to flash them twice. Well that fixed it for me. I dkbhave the gingerbread boot loaders now though
Sent from my SGH-I897 using xda premium
I went from bone stock Froyo 2.2 straight to THS ICS with no problems whatsoever. So some ICS Roms doesn't need GB bootloaders.
Sent from my SGH-I897 using xda premium
I'm on the same situation as the original poster: I'm on andromeda3 and now I want to upgrade to ICS. Right now my captivate has cwm 2.5.1.2 can I flash any ICS mod from there or do I need to do something else?
See this.... TRusselo's "Guide..." that is a Stickied Thread in the Q & A Forum.
I believe u will need the Gingerbread Bootloaders...
Sent from my SAMSUNG-SGH-I777 using xda premium
I need a bit of urgent advice if possible. Having waited patiently for Samsung to release ICS for the P7310 which has never appeared in the UK, I'm trying to flash to JB (latest AOSP version) from the stock 3.2.
I've installed CWMOD 5.5.0.4 ok, and copied the update rom and gapps to the root of the tab. I've gone into CWMOD recover mode, wipe/reset and then selected the rom to install. It starts the install, then fails with the system error 7 message (seems to be fairly common). It obviously started the install but now I don't seem to be able to boot the tab into 3.2 anymore, it just sits at the boot logo and doesn't get any further. I'm happy to try another ROM (maybe CM10), but I need to transfer it to the device first, and ofcourse I can't do this within windows at the moment. Odin still runs and can talk to the tab, but I'm a bit lost at the moment.
I'm a bit new to all this, so could really do with some help.
Flash the stock Rom.with Odin. You can find it at sammobile.com. it'll bring you back to stock.and.you can start over again. You're soft bricked right now.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Cool. Thanks for that. I guess I just select the PDA option in Odin, and let it do its thing.
Any idea why this happens? I'd read a couple of threads about going from HC to ICS first, then to JB. Is this a requirement, or optional?
I'ver had similar problems finding a Rom that works on my i957. Never did find an ics that worked. I'm running jb from nrvate, but I think its specific to the i957. And, yes, flash just like you did the cm recovery.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Really appreciate the replies. I've managed to get the tab back working under 3.2 (stock rom downloaded from SamFirmware), so that's a start. I still want to upgrade to JB if possible (or ICS if not). Am I likely to experience the same problem again? Is it worth going to ICS first? I've downloaded the stock US ICS rom, which i can flash using Odin. I can't see why this wouldn't work on a UK spec 8.9 wifi, but can anyone confirm if it does?
So, I'm back at square one, but really want to try and get this sorted.
Did you do a clean install when you tried to flash the jb Rom? I.e. factory reset, format/clear system and data. If not that probably is the problem. There should not be any benefit of flashing ics before jb. The one difference between the two is you most likely will have to flash a gapps (Google apps) package after the the jb flash. Not sure where you got the Rom, but the developer should have the gapp they recommend and instruction on how to do the flash. Every jb to Rom I've flashed has the gapps package flashed after the Rom and before rebooting.
I'd stick with a Rom specific for your device. I hard bricked my phone with the wrong Rom once. The US Rom probably does not have the correct radio for.you in the UK. I only use WiFi so don't care too much if I have the right radio or.not.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Did you do a clean install when you tried to flash the jb Rom? I.e. factory reset, format/clear system and data. If not that probably is the problem. There should not be any benefit of flashing ics before jb. The one difference between the two is you most likely will have to flash a gapps (Google apps) package after the the jb flash. Not sure where you got the Rom, but the developer should have the gapp they recommend and instruction on how to do the flash. Every jb to Rom I've flashed has the gapps package flashed after the Rom and before rebooting.
I'd stick with a Rom specific for your device. I hard bricked my phone with the wrong Rom once. The US Rom probably does not have the correct radio for.you in the UK. I only use WiFi so don't care too much if I have the right radio or.not.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
I've just tried again, and have hit the same problem, and have tried the AOSP rom and the CM10 rom this time. I did a wipe/factory reset beforehand, but the installer starts then just aborts with 'symlink: some symlinks failed' E:Error in /sdcard/<rom file name> (Status 7). Obviously the tab 8.9 doesn't have an sd card slot, but I thought the rom must be aware of this.
Where am I going wrong?
You might try to flash a different version of cwm I don't remember now how I found this link, but here is a link for Overcome_CWM_Recovery_v5.1.2.6_P73xx.tar
http://www.sendspace.com/file/507gjv
just flash in Odin, like the ROM itself (in PDA section)
I use twrp but don't know where to find a version for your p7310.
Have you tried a different Rom
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
You have a /sdcard directory despite the fact you have no physical external sdcard.
I had the same problem. Found this solution:
http://forum.xda-developers.com/showthread.php?t=1973712
tman24 said:
I've just tried again, and have hit the same problem, and have tried the AOSP rom and the CM10 rom this time. I did a wipe/factory reset beforehand, but the installer starts then just aborts with 'symlink: some symlinks failed' E:Error in /sdcard/<rom file name> (Status 7). Obviously the tab 8.9 doesn't have an sd card slot, but I thought the rom must be aware of this.
Where am I going wrong?
Click to expand...
Click to collapse
harry_fine said:
You have a /sdcard directory despite the fact you have no physical external sdcard.
I had the same problem. Found this solution:
http://forum.xda-developers.com/showthread.php?t=1973712
Click to expand...
Click to collapse
If reading that reply right, one specific stock rom does what's necessary, trouble is, that's a US stock rom, and I'm in the UK. Already had it confirmed that it wouldn't be good to install a US rom on a UK tab. Loads of people has flashed their tabs, so it can't be that difficult! I've just tried Overcome CwM v5.2.1.6 with the same AOSP and CM10 roms, but same error
Ok, silly question time, but does the tab need to be rooted to install these new roms successfully?
You don't need to be rooted, just the recovery installed. Not sure why you're having problems now other than I had a hell of a time getting a Rom installed too. I'd try a different Rom. I tried some yesterday and didn't get any of them to work well. At least you've learned how to recover from a soft brick. I've learned that lesson too, to many times!
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
I'd try to download CM10 again. As i see in the error message there is a problem with the zip, maybe caused by error in downloading?
tman24 said:
If reading that reply right, one specific stock rom does what's necessary, trouble is, that's a US stock rom, and I'm in the UK. Already had it confirmed that it wouldn't be good to install a US rom on a UK tab. Loads of people has flashed their tabs, so it can't be that difficult! I've just tried Overcome CwM v5.2.1.6 with the same AOSP and CM10 roms, but same error
Click to expand...
Click to collapse
Hi, dont know if this will help, but I have flashed the US ICS rom on my Swiss Tab 8.9, with no problems. There should be no issue with worrying about the wrong radio as stated previously, as the 7310 is the WIFI only model, so there should be no issue with 3G. The only thing which causes some issues is the screen flicker issue. If you flash the US gingerbread first, then the ICS, it seems to solve the issue. For mor info check out this thread http://forum.xda-developers.com/showthread.php?t=1573548&page=50
Good luck!
Aaarrgggh! Frustrating, now I'm just getting 'hardware id not found' when I connect the tab to the PC!!! I can browse the device in Windows, but of course, Odin won't connect. How difficult can this really be!
I've already uninstalled and re-installed the Samsung USB drivers, tried a different USB port etc, but same result.
As it stands, the tab is working, but on that horrible v3.2.
I might be getting somewhere, but nothing's easy! I have moved everything over to a laptop we have, and have gone through the whole process again. I installed CwM ok using Odin, copied over the AOSP beta13 for the 7310, and this time when I installed the ZIP, it said completed ok. Good so far.
I then rebooted, and while I see the Samsung logo, the screen then goes black and stays that way. I've left it ages, but it doesn't seem to get anywhere. I can still reboot it and get into download/recovery, so that's ok. Am I doing anything wrong? I did the wipe/reset beforehand, so It's not obvious why this is not working.
Quick update. I can get ICS running (CM9 works), so that's good. It does look like any JB rom (AOSP/CM10) just cause a blank screen on reboot, which is wierd. I've re-downloaded the ROM's just in case, but no dice. Install completes ok, and gapps reports no problems.
I often don't get a boot animation, just the black screen. Every once in awhile the animation comes back. Seems totally random. I'm using nravates jb Rom on the i957. Other than that it runs great.
Sent from my SGH-I727 using xda app-developers app
Friends
I have few questions about i897
1. Is there any way to downgrade from CM10 to CM7 other than flashing stock and rooting?
2. If this is only the way, how can i find the bootloader version. I am now running slimbeen and i am purchased it from ebay with custom rom. Bootloader screen is at&t logo and world phone. I don't know is it 2.2 or 2.3
3. Back button is little laggy. I found a solution in xda about updating touch driver using secret code *#*#2663#*#*. But this code is not working in my captivate. Is this due to custom rom?
4. During taking photos temperature of cell increases and battery drains quickly. Is it normel?
Thanks
Sent from my MB525 using Tapatalk 2
If you want to go down to gingerbread just to use touch firmware update
Then you should not do it, this can brick your touch firmware and you may not be able to use your mobile without adb
And for downgrading purpose
Backup your sdcard (as it can get formatted in the process)
Then flash a cm7 rom
Without completing the installation it will reboot
Boot into recovery again and flash cm7 again
This time you will have working cm
dheeraj (dhlalit11) said:
If you want to go down to gingerbread just to use touch firmware update
Then you should not do it, this can brick your touch firmware and you may not be able to use your mobile with adb
This time you will have working cm
Click to expand...
Click to collapse
But users said that it is working for them. Not find this information. Thanks
Sent from my SGH-I897 using Tapatalk 2
Well do it and if something like that happens then share it with all of us, so no one else will do it