Related
I did a couple searches but could not find a guide to updating my CyanogenMod version. I followed an old ninja tutorial on rooting which linked to v3.4.6. But I don't think I have to do a wipe and all that stuff do I? Do I just have to copy the ROM to SD, rename as update.zip and do the reboot thing? Will I lose my data? Settings? (I know it's a good idea to backup anyway)
Do I have to upgrade incrementally from 3.5-->3.6-->3.7-->etc.. or can I jump to latest version? Do I need to use an updated recovery image, or is cm-recovery-1.2.img okay?
On a side note, I just noticed that there is an update showing up under System Updates. Is that the official Google update? What would happen if I applied that update?
Thanks
just download cm 4.0.1 and flash it. you do not have to wipe unless things start to terribly mess up. i would recommend get the 1.4 recovery image as you can flash any .zip file with it. also you can restore a nandroid backup from it. if something does mess up try running fix_permissions in the recovery console before wiping.
if you applied an official google update you would lose root access but that wouldn't be terribly hard to get back with the one-click root in the market aka recovery flasher.
Thanks david1171.
Does either flashing the ROM or the Recovery Image wipe my settings, apps? Sorry for the noob q's.
Also, someone in a previous thread said to update radio? Is that a separate procedure? Where do I find the latest radio version?
just flashing the rom or radio or recovery image will not wipe anything. the newest radio is 2.22.19.26I. you can check in setting>about phone> under baseband version the part past the U_ is the radio version. if you do not have the latest radio you can get in cyanogen's thread in the first post. and you just flash the radio like a normal rom. the only thing that will wipe your data when you flash it is haykuro's spl.
what do you mean just flash the radio like any normal rom?
do I rename the radio zip file to update.zip, put in root directory, reboot, hold HOME, then ALT+S? Is that what you mean?
I tried to follow the HTC guide for updating radio, but it sounds like you need a developer machine to run those commands.
Thanks
meanderingthemaze said:
what do you mean just flash the radio like any normal rom?
do I rename the radio zip file to update.zip, put in root directory, reboot, hold HOME, then ALT+S? Is that what you mean?
I tried to follow the HTC guide for updating radio, but it sounds like you need a developer machine to run those commands.
Thanks
Click to expand...
Click to collapse
yeah thats how you do it.
Alright, I'm up and running:
recovery 1.4
newest radio
cyanogenmod 4.0.1
Here's a guide for noobs that I found useful:
http://androidandme.com/2009/05/gui...r-rooting-your-android-g1-to-install-cupcake/
It's going to be outdated but at least it shows how to update radio. I didn't realize that all updates were treated the same. Now with Cyanogen's Recovery 1.4, we don't have to rename the files to update.zip.
I also didn't realize that when you do updates it doesn't delete your data folder which houses all of your custom settings, apps, google account info. It just flashes the system files.
I still don't know a lot and don't completely feel comfortable doing everything. Hopefully soon enough, someone will put together a guide to explain all the particulars that are not obvious to the noob. People have already started.
Thanks so much to everyone who has worked on these projects. It's so awesome!
do you have the Hard SPL. if not go to the guide in my sig and you can install it noob friendly from there
Hello! Please help me!
I bought HTC Dream G1 on ebay with
installed Android 1.6 (DONUT) on it.
I heard that now there are android versions 2.x and i need to have so versions to install most of apps.
Please, write my some instructions what should i do to update my device, or give me some links.
I have seen a lots of modifications of Roms in your forum but i don't understand nothing about this. /please recommend me/
Also I should add : I live in eastern europe (bulgaria) /because i heard that there re some US roms or.../??
P.S. Sorry for my stupid questinos, but i'm migrating from 186mhz windows 6.0. smartphone)) and i'm new to android...
its a lot of work I just did it now :/
Have a friend do it.
I did this, I stopped at this step "Now you have root!"
http://forum.xda-developers.com/showthread.php?t=442480
then I did this
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
using this:
http://dev-host.org/uxpmh3p0c2z6/recovery-RA-dream-v1.7.0-cyan.img
then I followed some of this for the radio/spl
http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
***probably best to follow this one instead***
http://forum.xda-developers.com/showthread.php?t=983834
and finally I installed this:
http://forum.xda-developers.com/showthread.php?t=929678
it's a lot to absorb at once and theres a lot of room for error... I'm still having issues as we speak
you found all the guides except for mine lol... which is basically all of that on one place...
http://forum.xda-developers.com/showthread.php?t=1098899
Hey i was reading up about rooting for 2 weeks before i plunged in and took the step. Let's say on your first try, don't do anything that needs you to change radio etc.
Just use the superoneclick method to root it, then download rom manager (free from android market) and install clockworkmod recovery. This should be easy, as from rom manager all you need to do is click flash clockworkmod recovery, and it will do it for you.
Next find the rom you want, and download 3 files. One is the rom itself, the other is a kernel (example ezterry's) and finally gapps and put them on your sd card. Next reboot into recovery.
First you'll want to create a backup, go to backup and restore click backup, and let it do it's thing. Once it says backup complete, you'll need to wipe cache, and wipe date/factory reset.
Once you've done that, do install zip from sd card, and install the files in this order:
ROM first: (find where you put the zip file on your sd, and select it)
Then do install zip from sd card again & select the Kernel (if you need to flash a seperate kernel)
Then finally do install zip from sd card again and select the gapps, zip (this is basically the android market, and a few other google apps).
Next press reboot into recovery, and it should load into your new rom, if all has been done correctly. I just recently rooted and put a custom rom on my phone, and this is the way i did it, so it should work for you. Make sure you research rooting and flashing roms onto your phone, before you take the plunge though.
Fellow androiders,
I believe I am in a really rare brick situation that no matter how I try, it still does not show any turn around.
[Introduction]
I bought a Korean version Milestone(Moto Qrty, as they put], and I took it to China. Because the original phone did not support sending Chinese text message, plus, too much telco provided apps are making the phone sluggish, I decided to follow my friend advice, to switch to widely available open-sourced Froyo (I wanted the CM).
[Problem]
I thought that the flashing process would not be too difficult and I could handle it by myself. But, it turns out that I have become a victim of an overly simplified version of flashing guide. I don't know what exactly have done wrong, after successfully rooted the phone, I vaguely remember that I have used CM ROM for Droid, instead of CM ROM for Milestone.
And that made my phone a brick. My phone will turn on, but will restart again and again after M logo(So-called M boot loop).
[Background information of the Phone and my PC environment]
Phone Model: A853
Original Bootloader version: A0.20
Original Android System: Froyo
RSD lite version: 5.3.1. (later switched to 4.6 due to the suspicion of RSD bug)
Operating System: Windows 7 64 bit, English
[What I have tried so far]
I have tried to follow many tips on the internet. Tips from Korean websites, from Chinese websites, and from English websites. Basically, these tips will let you flash back to the original ROM by using RSD lite.
But, no matter what I try, it will not fix the boot loop problem.
I've tried to
1) Bring the phone to the original status [did not work.]
- flash the bootloader into A0.20 (the original bootloader) with RSD lite;
(bl_a020_umts_sholesumts_skt_consumer_replacer.sbf)
- flash with original Froyo sbf (following the advice from Korean websites, flashed Clair first, and then flashed Froyo) with RSD lite.
(A853_2.1(Eclair).SBF / A853_2.2.1(Proyo).SBF)
* According to what Koreans say, it would make your phone into the original status, will even remove signs of root.
2) Used many combination of following bootloader and ROMs
- flash the bootloader into 90.78ch
(BL_9078_umts_sholes_GC_HS_Consumer_replacer.sbf)
- flash the bootloader into 90.78
(BL_9078_umts_sholes_HS_Consumer_replacer.sbf)
- GOT221 ROM
(GOT_RTEU_2_2_1FULL.sbf)
- And some other un-name-able ROMs
SGC_U2_03.04.0_USASHLSGCB1B2B5008.0R_PDS06A_HWp2a_1FF.sbf
3) Used many different OpenRecovery Variations
OpenRecovery v1.46
OpenRecovery 3.3
OpenRecovery GOT mod v2.1
4) Restore Nandroid backup which I made right before I made my phone brick.
5) Cleaned data/cache/dalvic as I do every flash, and tried boot without SIM card and SDCard.
[Some discoveries and successes]
- With 90.78ch + GOT2.2.1, it will show "Android" screen, but it will reboot as soon as the phone OS interface show up.
- According to my friend, when he flashed back to the original bootloader A0.20 + original froyo Rom, it showed TelCo Symbol "T" once (which is the booting screen right after M).
[Final Comment]
What I really want to know is that is it the time I give up on it? or is there any value of pursuing other knowledge on bring this phone back?
I really need this phone, and it will take some times to save money to buy another smartphone, I would really really appreciate if you can help me bring this phone back to normal.
Thank you.
some users reported problems with sdcard. try to boot without sdcard, and wipe everything after or before the flash process.
and i don think it's hard bricked...
Sir, I have tried so, somehow, I did not have lucks other had.
roofghost said:
Sir, I have tried so, somehow, I did not have lucks other had.
Click to expand...
Click to collapse
So you've tried flashing different bootloaders, with no success? I always thought flashing another bootloader version different from your own was risky.
If not, you can just try flashing the SBF from here: http://android.doshaska.net/rootable , then installing OpenRecovery, rooting the phone, flashing a custom ROM, etc.
..... my bad
I have the same issue,
in recovery there is message when wiping data/factory reset:
E:Error in CACHE:fota/log
(no space left on device)
I am wondering, if I move CACHE to SD would it help??
Yesterday I have installed original Rom (shols~) and phone booted once to android and when I have rebooted it, there is M bootloop again.
Please help me
skadude66 said:
So you've tried flashing different bootloaders, with no success? I always thought flashing another bootloader version different from your own was risky.
If not, you can just try flashing the SBF from here: android.doshaska.net/rootable , then installing OpenRecovery, rooting the phone, flashing a custom ROM, etc.
Click to expand...
Click to collapse
Thanks, did not work.
I have a feeling that the "doshaska" will know how to solve this. Anyone know how to contact or PM him?
Thanks.
By the way,
in this case, is there anyway can fix the brick via "console" in the OpenRecovery?
Thanks.
So... you have open recovery and can get to the console...
What happens if you copy CM to the updates folder and flash CM?
zeppelinrox said:
So... you have open recovery and can get to the console...
What happens if you copy CM to the updates folder and flash CM?
Click to expand...
Click to collapse
Yes, I can enter OpenRecovery and can get to the console.
And,
sorry about the CM, I think I will have to try that again and let you know then.
Is there any CM ROM you want me to try? (Hopefully with a reliable instruction. If you are busy, you can just leave this part, I will look for myself about the instruction.)
Truly thank you and glad to see new reply under this topic.
Well, use OR's mount as usb function and plug into your computer.
Copy the latest CM7 (I think that's what you want - or any ROM really) to the updates folder.
Wipe all caches
Then apply the update
It should "just work"
I mean, the hardest part is getting into OR lol
I'm surprised that your battery hasn't died yet
zeppelinrox said:
Well, use OR's mount as usb function and plug into your computer.
Copy the latest CM7 (I think that's what you want - or any ROM really) to the updates folder.
Wipe all caches
Then apply the update
It should "just work"
I mean, the hardest part is getting into OR lol
I'm surprised that your battery hasn't died yet
Click to expand...
Click to collapse
Can I install CM7 on Froyo? I thought that was for the Android 2.3.
I have just flashed back to the original bootloader of A0.20 (it was 90.78 as I play around with it.), and flashed the original korean .sbf froyo. Just to follow your suggestion.
I will try to install vulnerable recovery. I think in this way, I can use OpenRecovery again.
About my batter, I purchased a separate battery charger.
I will keep my status updated as soon as I try this out.
Thanks.
same problem and flash so many rom My milestone can't acess sdcard on recovery mode and android os.
Sent from my Milestone using XDA App
guys same problem here, help us
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
Dear Experts
I am first time android user, have rooted Droid 3 XT883 & installed Safestrap 1.08.
Later I came to know that it wont's work due to some partition issues.
Now safestrap 1.09 is available for droid 4, will it work on my device?
Also please tell me how shall I uninstall safestrap 1.08 without damaging my phone.
Thanx in advance
Still Unanswered, please help
Please suggest, I am noob in this matter & can't try any dangerous stuff.
use this one!
all the explanations are there also.
if you decide to uninstall safe strap, you go to the main ROM. and nothing bad happens. you just choose disable SAFESYSTEM from recovery, and open SAFESTRAP in phone menu, uninstall recovery...and thats it.
Thanx but still unclear
your link directs to how to safestarp page which I have already gone through several time while downloading 1.08 & installing .
My question is that 1.08 doesn't support XT883 due to some issue with partition size, so shall I try 1.09 releases recently. On site it says it's for Droid 4 so I dont know if it will support droid 3 or not. I am afraid to try without any confirmation as I may brick it & I don't have any backup of ROM till now.
If 1.09 supports XT833 then please tell shall i just install the apk over 1.08 or shall i uninstall 1.08 first then install 1.09?
Droid 4 is a completely different phone. I wouldn't. I would tweet Hash if no one knows why here.
Sent from my XT862 using XDA
Thanx Mr. Obivious
I have posted on his blog & will wait.
Thanx for your advise.
I have a working build of Safestrap 1.06 for ME863 that should also work for the other non-Verizon variants too.
Instructions are at http://forum.xda-developers.com/showpost.php?p=20976390&postcount=294 and the download's attached a little earlier in the thread, with more instructions.
Thanx
TBBle said:
I have a working build of Safestrap 1.06 for ME863 that should also work for the other non-Verizon variants too.
Instructions are at http://forum.xda-developers.com/showpost.php?p=20976390&postcount=294 and the download's attached a little earlier in the thread, with more instructions.
Click to expand...
Click to collapse
So I have 1.08 installed on my 883, what I understood is that i need to unzip your file which contains two files (recovery & fixM3android.diff. Then I go to etc/safestrap & copy the 2nd-init.zip to my laptop. Extract it & replace the recovery file with yours & zip it again & replace the new 2nd-init.zip in phone /etc/safestrp folder & reboot. It will take the backup.
Few doubts :
1. Is there any chance that I may brick my phone by doing this?
2. Once backup is successful do I need to replace the original 2nd-init.zip for flashing another rom.
3. If i need to restore my original rom do i need to put back your's version of 2nd-init.zip
And many thanks to you for your help. All international droid 3 users shall get benefit if it works out well.
Edit : While zipping your version do I need to specify any specific compression method. As i faced while creating custom bootanimation for droid 3 that if you do a normal zip it doesn't work, it has to be selected store method in compression type.
That sounds right.
I guess it's possible to brick your phone doing this, but I think if it goes wrong you can just battery-pull to bypass 2nd-init for the next boot, and reinstall safestrap normally.
I don't know the answers to the other questions as I don't know what changed between 1.06 and 1.08, and I don't know if restoring works with my code, let alone with stock 1.08.
Sorry, I only threw it together quickly, so it's not massively user-friendly at the moment. I was hoping hashcode or rick#2 would integrate it or something similar, and my version could quietly fade into the mists.
TBBle said:
That sounds right.
I guess it's possible to brick your phone doing this, but I think if it goes wrong you can just battery-pull to bypass 2nd-init for the next boot, and reinstall safestrap normally.
I don't know the answers to the other questions as I don't know what changed between 1.06 and 1.08, and I don't know if restoring works with my code, let alone with stock 1.08.
Sorry, I only threw it together quickly, so it's not massively user-friendly at the moment. I was hoping hashcode or rick#2 would integrate it or something similar, and my version could quietly fade into the mists.
Click to expand...
Click to collapse
Hii, It didn't brick my phone, I am able to do backup & restore, enable safe system & install another ROM but the new ROM always boots to Black Screen. I have tried CM7.2 & Maverick 4.5. Going to try 1 or 2 more ROMs mean while to make sure it's not ROM problem. Could you suggest something what could be the reason or any workaround.
Thanx
We have same issue. I think we have to install Verizon ROM with .906 then we can install any other ROM.
NIGHTMARE- said:
We have same issue. I think we have to install Verizon ROM with .906 then we can install any other ROM.
Click to expand...
Click to collapse
Today I am gonna try few more ROMs with my tweaked safestrap, if it doesn't workout then I think we need to SBF with .906 & install safe strap then do it. But as I have heard on forums some features of XT883 ROM is comparatively good than others.
Please share if you find some other working solution.
Sure one of my friend having same problem, he well aware of android as compare to me. My primary device is iPhone, So I don't have such knowledge as compare to you also. We are looking into Gummy ROM let's see. And XT883 more stable than these ROM.
TBBle said:
That sounds right.
I guess it's possible to brick your phone doing this, but I think if it goes wrong you can just battery-pull to bypass 2nd-init for the next boot, and reinstall safestrap normally.
I don't know the answers to the other questions as I don't know what changed between 1.06 and 1.08, and I don't know if restoring works with my code, let alone with stock 1.08.
Sorry, I only threw it together quickly, so it's not massively user-friendly at the moment. I was hoping hashcode or rick#2 would integrate it or something similar, and my version could quietly fade into the mists.
Click to expand...
Click to collapse
Hey, I've been reading through everything I can find about the ME863. I've got Saestrap installed but I can't seem to get it to backup anything or to run any ROMs in safeboot after they've been installed. I have read your solution and done exactly what you say to. I copy over your recovery file then in ES File Explorer I copy over the 2nd-init to a new folder extract it delete the old recovery, put the new one in, compress it and then put it back in the original directory, (I leave the original renamed 2nd-init_original ) however when I go to boot to safestrap it just loads a black screen. Then I have yank out the battery reboot to the bastardization that is Chinese Android and put everything back and then safestrap goes back to sort of working (except not at all really). What am I doing wrong?
daniel0524 said:
Hey, I've been reading through everything I can find about the ME863. I've got Saestrap installed but I can't seem to get it to backup anything or to run any ROMs in safeboot after they've been installed. I have read your solution and done exactly what you say to. I copy over your recovery file then in ES File Explorer I copy over the 2nd-init to a new folder extract it delete the old recovery, put the new one in, compress it and then put it back in the original directory, (I leave the original renamed 2nd-init_original ) however when I go to boot to safestrap it just loads a black screen. Then I have yank out the battery reboot to the bastardization that is Chinese Android and put everything back and then safestrap goes back to sort of working (except not at all really). What am I doing wrong?
Click to expand...
Click to collapse
Probably the problem is your in zip, I also went through the same. Do as below
1. Install safestrap 1.08 on your phone
2. Copy /etc/safstrap/2nd init.zip to your PC. (file size 1.13 mb)
3. Extract it with winrar to some folder
4. delete the recovery file
5. copy TBBie recovery in folder
6. select all files & zip it to 2nd-init.zip (don't ZIP the folder, that's what mistake i had made & had same problem)
7. verify that zip size is 1.19 mb & when you open it in browser you see files not any folder.
8. replace the tweaked zip with original in etc/safestrap
9. set permission & ownership as original
10. Reboot & you shall be good.