Related
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
Current phone information should be attached. Short form is, I'm using the Gummi 1.2.0 rom, put onto my phone after using safestrap (and following the instructions to make a backup before doing so). Safesystem is enabled.
Two backups: located on my external SD card
nonsafe-2012-05-26.07.52.54/
safe-2012-05-27.08.06.28/
Safestrap recovery v1.09 (afraid to update to 2.0 without breaking more stuff)
What I'm looking to do is return my phone to working stock, which I believe was Gingerbread 2.3.6. That said, every time I've touched this thing trying to go back, I've black screened it. I don't live in an area with 4g (screw the mountains, and their 1x service), so any attempts to connect to the 4g network for any part of the process will require me driving into Pennsylvania, 30 minutes away. I've heard before that you can't return from the ICS leak to the Stock for the Droid 4, for various reasons (but i believe the important one was it was a later firmware and it isn't a process designed to go backwards)
I'd like to know if thats still the case currently, or if something has changed. I'm getting shaky wifi/data/cell reception up here, and its flawless back on stock. Hell, I've got an old razor as an emergency phone that's flawless up here. Next time I'll do more research for this stuff I was a proud OG droid owner, and ran cyanogenmod on it before the vid card fried one evening. Thought the droid 4 would be a good deal, but I've had nothing but trouble with the roms on it.
All that said, I can simply smash and return this droid if its the only way to get a stock one back, but I don't like destroying useful and good technology when I can help it. Besides, I like fixing the problems I create.
Thanks for the help XDA, either way.
-- TheChaoticDoctor
Did you flash the leak ICS from Motorola or did you use Safestrap and flash Gummy ICS?
If you flashed the leaked ICS, there is no going back. You will need to find get the files to flash the partial .219 system back so you can run the .206 leak update again.
If you just used safestrap to flash Gummy 1.2.0 then you can use the .219 flash files to completely re-do your phone.
Currently there are no ROMs to flash if you are on the leak, Hashcode just released his Safestrap 2.0 to do so but still nothing to flash. All the current ICS ROM builds are for the stock phone running the Gingerbread Kernel.
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
TheChaoticDoctor said:
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
Click to expand...
Click to collapse
You should probably go up to .208, that's the latest leak. Make sure to use rootkeeper, and follow all the instructions. So far I haven't lost root, but be aware I'm stuck on .206 because I don't want to lose root....
Look here for more info:
http://forum.xda-developers.com/showthread.php?p=26311439
Sent from my XT894 running ICS
First of all, it sounds to me like you've just flashed a ROM, not flashed the leak. If that is the case, you can just toggle the safe mode in safestrap to get back to stock. Safestrap lets you toggle between stock and the ROM. It is pretty awesome because you can play with the ROM and then go back to stock whenever you need to.
If you HAVE flashed the Motorola leak (as opposed to just a ROM) you are SOL.
If you haven't flashed the Motorola leak and just want to get back to factory conditions, you'll have to flash via RSDLite. That info you should be able to find here:
http://forum.xda-developers.com/showthread.php?t=1622256
Honestly I WOULD NOT flash the leak at this time. IMHO, it doesn't really offer enough to risk getting off the upgrade path forever, and losing the ability to flash back via RSDLite.
Hello everyone,
Before I describe the issue I have been experiencing, I would like to say thanks in advanced for providing me assistance.
Okay currently, I am running.905 base band, and have followed the method for flashing back to .902(FXZ) in order to receive the .905(OTA), and have rooted my device using the moto-fail exploit. The issue I have been experiencing is persistent boot loops when flashing any ICS ROM(I am using CWM 4.0.1.5) via Bionic Bootstrap.
The procedure I have been using(assuming I am rooted and on .905),
Boot the device into recovery(CWM via Bionic Bootstrap)
Wipe Data/Factory Reset.
Wipe Dalvik, and System.
Apply update from SD-CARD(Initial ROM).
Apply update from SD-CARD(correct GAPPS for build).
Reboot ----->> Then the device boot loops.(I restore the device using the FASTBOOT Method).
I am aware of safestrap(but I do not want to "pseudo dual boot", ROMS, I prefer to flash over existing installs.
Is there anyone else experiencing this issue? or does anyone have a recommended solution(other than using safestrap)?
Thanks again!
Most, but not all, ROMs require GApps. Make sure the one you are installing does.
There is now a .905 FXZ that you can use to shorten the waiting time.
Make sure you are NOT using Bootstrap for ICS .
Most ROMs already wipe /system as a party of the install procedure.
*** MAKE SURE YOU ARE USING A ROM DESIGNED TO BE INSTALLED IN BOOTSTRAP AND ONE THAT IS NOT DESIGNED TO RUN ON THE ICS LEAKS.
HTH
Sent from my rooted BIONIC running ICS 6.7.235 via Tapatalk 2
johnlgalt said:
There is now a .905 FXZ that you can use to shorten the waiting time.
Click to expand...
Click to collapse
Where?
The one that has been available for download is not a true zip.
It fails in RSD and no zip utility can decompress it.
I've tried downloading from 3 different sources.
-s
Atheistnofaith said:
Hello everyone,
Before I describe the issue I have been experiencing, I would like to say thanks in advanced for providing me assistance.
Okay currently, I am running.905 base band, and have followed the method for flashing back to .902(FXZ) in order to receive the .905(OTA), and have rooted my device using the moto-fail exploit. The issue I have been experiencing is persistent boot loops when flashing any ICS ROM(I am using CWM 4.0.1.5) via Bionic Bootstrap.
Thanks again!
Click to expand...
Click to collapse
Are you installing one of the ICS releases like AOKP or CM9 or are you trying to install an ICS Leak?
If you're trying to install one of the official ICS Leaks, they will only flash in Stock Recovery.
suprsidr said:
Where?
The one that has been available for download is not a true zip.
It fails in RSD and no zip utility can decompress it.
I've tried downloading from 3 different sources.
-s
Click to expand...
Click to collapse
It's there, it's not an OTA, it is a true FXZ, given to us one week ago.
If the file you are downloading is less than 300MB it is definitely not the right one. The file name is the same as the .902 FXZ except .902 is replaced by .905.
I don't have the link on my phone, but PM me and i can link you to it back here tomorrow.
Sent from my rooted BIONIC running ICS 6.7.235 via Tapatalk 2
johnlgalt said:
It's there, it's not an OTA, it is a true FXZ, given to us one week ago.
If the file you are downloading is less than 300MB it is definitely not the right one. The file name is the same as the .902 FXZ except .902 is replaced by .905.
I don't have the link on my phone, but PM me and i can link you to it back here tomorrow.
Sent from my rooted BIONIC running ICS 6.7.235 via Tapatalk 2
Click to expand...
Click to collapse
I just tried again w/ the one listed http://forum.xda-developers.com/showthread.php?t=1328100
VRZ_XT875_5.9.905.XT875.Verizon.en.US_CFC.xml.zip ~488MB
and you cannot use it in RSD as it will fail and you cannot unzip it
7zip:"Can not open file 'VRZ_XT875_5.9.905.XT875.Verizon.en.US_CFC.xml.zip' as an archive"
I found it listed 3 different places and DL'd all each w/ same result.
I spent all day last Thursday flashing different ROMs and each time I had to use the OTA to get to .905 if this VRZ_XT875_5.9.905.XT875.Verizon.en.US_CFC.xml.zip had worked it would have saved me hours.
If you know where I can find a working version you would get my vote for president.
-s
suprsidr said:
I just tried again w/ the one listed http://forum.xda-developers.com/showthread.php?t=1328100
VRZ_XT875_5.9.905.XT875.Verizon.en.US_CFC.xml.zip ~488MB
and you cannot use it in RSD as it will fail and you cannot unzip it
7zip:"Can not open file 'VRZ_XT875_5.9.905.XT875.Verizon.en.US_CFC.xml.zip' as an archive"
I found it listed 3 different places and DL'd all each w/ same result.
I spent all day last Thursday flashing different ROMs and each time I had to use the OTA to get to .905 if this VRZ_XT875_5.9.905.XT875.Verizon.en.US_CFC.xml.zip had worked it would have saved me hours.
If you know where I can find a working version you would get my vote for president.
-s
Click to expand...
Click to collapse
Though I haven't tried it, this one might be the correct one, it's about 512 MB in size.
http://rombot.droidhive.com/ROMs/targa/fastboot/VRZ_XT875_5.9.905.XT875.Verizon.en.US_CFC.xml.zip
**Disregard, it is only listed as being 512 MB, it is actually the same as above.
Hey,
This is a pretty long post, so if all you're interested in is the 905 FXZ file, scroll down to the "FXZ to 905" section, it's bolded.
Problems with flashing ICS ROMs ( in regards to OP, by Atheistnofaith ) :
You may already know this, but each custom ROM is "built off" of one of the stock roms, flashing from a different starting point will often cause your phone to not boot correctly ( boot loop, or freeze at the Motorola logo ), or will boot, but not work correctly ( i.e. something like data will not work ). This, combined with the fact that many new ICS ROMs are built on the ICS leaks, could account for the problem ( Are you sure you're not trying to flash a ROM built on an ICS leak? That would definitely not work! ).
Another possible issue is that you are using the Bionic Bootstrap program to flash CWM. The version of CWM flashed by that program is rather old ( 4.x.x.x vs current: 5.x.x.x ). You may not like this, but Safestrap is the way to go. Before you defer me to the OP, "I am aware of safestrap(but I do not want to "pseudo dual boot", ROMS, I prefer to flash over existing installs." I want to point out that Safestrap is not for the purpose of Dual-booting ROMs, or at least, that's not how many people use it. Safestrap has many features that will: prevent being stuck at bootloops ( and needing to re-Flash 902/905 every single time ), allow you to always have a backup system ( i.e. I've soft-bricked the side that I flashed ROMs on, and since I needed to use my phone, I just opened safestrap ( battery pull, start booting phone, and hit the menu button at the Safestrap prompt ), and toggled safe system in the safeboot menu. This brings up another advantage of Safestrap: you don't need to be able to boot the phone to access CWM, installing safestrap adds a new bootup prompt that either lets you open safestrap or boot normally. Again safestrap is based on a much newer version of CWM, so if you don't want to install it for any other reason, install it for that one...
Setting up for, and using Safestrap:
So if I've convinced you that you want to use Safestrap ( I really recommend you do ), follow the instructions given here: http://forum.xda-developers.com/showthread.php?t=1771993 until step 10. Then root with motofail, and install Safestrap 2.0 ( download it here:
Code:
http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1328100&v=1&libid=1343056993296&out=http%3A%2F%2Frombot.droidhive.com%2FROMs%2Ftarga%2FBionicSafestrap-ICS-2.00.apk&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D1006&title=%5BLIST%202012-07-18%5DOne%20Stop%20Shop%2C%20ROMS%2C%20MODS%2C%20SCRIPTS%2C%20TOOLS%2C%20ROOT%2C%20BOOTSTRAP%20-%20xda-developers&txt=2012-06-22%20Safestrap%20v2.0&jsonp=vglnk_jsonp_13430595105542
). The file should be an apk, just install it on your phone, open it, and select the option to flash it.
If I haven't convinced you to use Safestrap, go to the section titled, "Picking a compatible ICS ROM". ( Then reconsider, and come back, lol ).
When you're ready to flash a ROM, power off the phone, turn it back on, while booting, a new screen will pop up, saying something like "Safe system: Disabled", while that screen is shown, hit the menu button. The screen will temporarily go blank ( Don't panic ), then it should enter a CWM-like setup ( it looks very similar and functions the same ). Now's a good time to do a full backup ( Same as CWM ). From there, go to safeboot menu, then go to toggle safe system ( Don't do quick toggle ). This will take a few minutes. Next flash the zip like you normally would with CWM. If All goes well, you can exit that ( same as CWM ) and the ROM should boot. If it doesn't ( give it at least 5 minutes though ), do a battery pull, and power on the phone again, going into the Safestrap menu like before ( hit the menu key at the screen ), and then go to the safeboot menu and toggle safe mode ( DO NOT QUICK TOGGLE NOW!!! Doing this will require you to re-FXZ ). After that finishes, reboot and your phone should be back to stock, ready to load a working ROM on it.
Picking a compatible ICS ROM:
As mentioned before, each ROM is built on a certain OTA release, like 905 or 902, or even the leaked ICS OTAs. Any ROM that say "ICS" and "LEAK" in its name is not for 905, or anything prior. For a list of 905 based ICS ROMs, check this out: http://rombot.droidhive.com/ROMs/targa/ ( Make sure you don't install anything from the "ics-leak-builds" folder ). CM9, AOKP, and AOKP AXIOM should all contain 905-based ICS builds. Try flashing something from there.
If you have a specific ROM in mind, read the forum post about it, making sure it doesn't say that you need to be on an ICS leak build. Make sure it's 905 based.
FXZ to 905:
I found two links to the new 905 FXZ. While I can't guarentee that either will flash ( I don't want to flash right now, I like where I am... lol ), I have tested and found that RSD Lite is willing to extract them, so they should flash. If one doesn't work, you can always try the other:
https://docs.google.com/open?id=0B26Hj6_2TMNTZ256eV9QbWpBSTQ from: http://forum.xda-developers.com/showthread.php?t=1771993
http://www.mediafire.com/download.php?71oyq7h8eskax6d from: http://androidforums.com/motorola-d...u-ics-back-updated-7-21-12-a.html#post4664922
Keep in mind that flashing these will essentially perform a factory reset on your phone, remove root, remove CWM and Safestrap, and possibly wipe all internal storage ( i.e. /sdcard and /mnt/sdcard ).
Conclusion:
Hopefully you found what you're looking for here. I would suggest trying out an ICS leak, they're all much more stable than the 905-based ICS builds. Also, there's a good amount of development going on that's based on them. ( For ICS builds based on the ICS leaks, See here: http://rombot.droidhive.com/ROMs/targa/ics-leak-builds/ ).
So if you want to try out an ICS leak, here's a link to a how-to ( but first a disclaimer ):
WARNING: DO NOT FLASH THE 235 ICS LEAK. YOU WILL NOT BE ABLE TO FXZ BACK TO 905. YOUR BEST BET IS 232
http://forum.xda-developers.com/showthread.php?t=1771993
If you use the 905 FXZ linked to above, make sure to give crobs808 ( The OP of that above thread ), a good thumbs up, he's the one that posted the FXZ.
Sorry this got so long. I hope this helps you get things working again. Good luck,
jedi453
projektorboy said:
Are you installing one of the ICS releases like AOKP or CM9 or are you trying to install an ICS Leak?
If you're trying to install one of the official ICS Leaks, they will only flash in Stock Recovery.
Click to expand...
Click to collapse
To further explain, I am not flash any of the ICS leaks, I am flash aokp, other etc etc. Also other posts stat to flash directly via FXZ file(the 905 firmware). I have attempted to flash the .905 on two bionics on both coming from 905 already, and will most defiantly wipe your web-top files, and corrupt your phones firmware(not brick it but Fasboot will end up failing to boot "A.6 error"), this is well documented not to flash directly to the fxz(.905) if you already have it installed it will corrupt your web-top files soft bricking your phone. The process requires you restore back to .902 and then apply .905 update(not fxz). Anyways thanks for the help, I have not flashed any of the leaks, only attempt were AOSP based roms. Maybe it is time to test out safestrap?
jedi453 said:
Hey,
This is a pretty long post, so if all you're interested in is the 905 FXZ file, scroll down to the "FXZ to 905" section, it's bolded.
Problems with flashing ICS ROMs ( in regards to OP, by Atheistnofaith ) :
You may already know this, but each custom ROM is "built off" of one of the stock roms, flashing from a different starting point will often cause your phone to not boot correctly ( boot loop, or freeze at the Motorola logo ), or will boot, but not work correctly ( i.e. something like data will not work ). This, combined with the fact that many new ICS ROMs are built on the ICS leaks, could account for the problem ( Are you sure you're not trying to flash a ROM built on an ICS leak? That would definitely not work! ).
Another possible issue is that you are using the Bionic Bootstrap program to flash CWM. The version of CWM flashed by that program is rather old ( 4.x.x.x vs current: 5.x.x.x ). You may not like this, but Safestrap is the way to go. Before you defer me to the OP, "I am aware of safestrap(but I do not want to "pseudo dual boot", ROMS, I prefer to flash over existing installs." I want to point out that Safestrap is not for the purpose of Dual-booting ROMs, or at least, that's not how many people use it. Safestrap has many features that will: prevent being stuck at bootloops ( and needing to re-Flash 902/905 every single time ), allow you to always have a backup system ( i.e. I've soft-bricked the side that I flashed ROMs on, and since I needed to use my phone, I just opened safestrap ( battery pull, start booting phone, and hit the menu button at the Safestrap prompt ), and toggled safe system in the safeboot menu. This brings up another advantage of Safestrap: you don't need to be able to boot the phone to access CWM, installing safestrap adds a new bootup prompt that either lets you open safestrap or boot normally. Again safestrap is based on a much newer version of CWM, so if you don't want to install it for any other reason, install it for that one...
Setting up for, and using Safestrap:
So if I've convinced you that you want to use Safestrap ( I really recommend you do ), follow the instructions given here: http://forum.xda-developers.com/showthread.php?t=1771993 until step 10. Then root with motofail, and install Safestrap 2.0 ( download it here:
Code:
http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1328100&v=1&libid=1343056993296&out=http%3A%2F%2Frombot.droidhive.com%2FROMs%2Ftarga%2FBionicSafestrap-ICS-2.00.apk&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D1006&title=%5BLIST%202012-07-18%5DOne%20Stop%20Shop%2C%20ROMS%2C%20MODS%2C%20SCRIPTS%2C%20TOOLS%2C%20ROOT%2C%20BOOTSTRAP%20-%20xda-developers&txt=2012-06-22%20Safestrap%20v2.0&jsonp=vglnk_jsonp_13430595105542
). The file should be an apk, just install it on your phone, open it, and select the option to flash it.
If I haven't convinced you to use Safestrap, go to the section titled, "Picking a compatible ICS ROM". ( Then reconsider, and come back, lol ).
When you're ready to flash a ROM, power off the phone, turn it back on, while booting, a new screen will pop up, saying something like "Safe system: Disabled", while that screen is shown, hit the menu button. The screen will temporarily go blank ( Don't panic ), then it should enter a CWM-like setup ( it looks very similar and functions the same ). Now's a good time to do a full backup ( Same as CWM ). From there, go to safeboot menu, then go to toggle safe system ( Don't do quick toggle ). This will take a few minutes. Next flash the zip like you normally would with CWM. If All goes well, you can exit that ( same as CWM ) and the ROM should boot. If it doesn't ( give it at least 5 minutes though ), do a battery pull, and power on the phone again, going into the Safestrap menu like before ( hit the menu key at the screen ), and then go to the safeboot menu and toggle safe mode ( DO NOT QUICK TOGGLE NOW!!! Doing this will require you to re-FXZ ). After that finishes, reboot and your phone should be back to stock, ready to load a working ROM on it.
Picking a compatible ICS ROM:
As mentioned before, each ROM is built on a certain OTA release, like 905 or 902, or even the leaked ICS OTAs. Any ROM that say "ICS" and "LEAK" in its name is not for 905, or anything prior. For a list of 905 based ICS ROMs, check this out: http://rombot.droidhive.com/ROMs/targa/ ( Make sure you don't install anything from the "ics-leak-builds" folder ). CM9, AOKP, and AOKP AXIOM should all contain 905-based ICS builds. Try flashing something from there.
If you have a specific ROM in mind, read the forum post about it, making sure it doesn't say that you need to be on an ICS leak build. Make sure it's 905 based.
FXZ to 905:
I found two links to the new 905 FXZ. While I can't guarentee that either will flash ( I don't want to flash right now, I like where I am... lol ), I have tested and found that RSD Lite is willing to extract them, so they should flash. If one doesn't work, you can always try the other:
https://docs.google.com/open?id=0B26Hj6_2TMNTZ256eV9QbWpBSTQ from: http://forum.xda-developers.com/showthread.php?t=1771993
http://www.mediafire.com/download.php?71oyq7h8eskax6d from: http://androidforums.com/motorola-d...u-ics-back-updated-7-21-12-a.html#post4664922
Keep in mind that flashing these will essentially perform a factory reset on your phone, remove root, remove CWM and Safestrap, and possibly wipe all internal storage ( i.e. /sdcard and /mnt/sdcard ).
Conclusion:
Hopefully you found what you're looking for here. I would suggest trying out an ICS leak, they're all much more stable than the 905-based ICS builds. Also, there's a good amount of development going on that's based on them. ( For ICS builds based on the ICS leaks, See here: http://rombot.droidhive.com/ROMs/targa/ics-leak-builds/ ).
So if you want to try out an ICS leak, here's a link to a how-to ( but first a disclaimer ):
WARNING: DO NOT FLASH THE 235 ICS LEAK. YOU WILL NOT BE ABLE TO FXZ BACK TO 905. YOUR BEST BET IS 232
http://forum.xda-developers.com/showthread.php?t=1771993
If you use the 905 FXZ linked to above, make sure to give crobs808 ( The OP of that above thread ), a good thumbs up, he's the one that posted the FXZ.
Sorry this got so long. I hope this helps you get things working again. Good luck,
jedi453
Click to expand...
Click to collapse
Thank you for the advice, but I have tested the method of flashing .905 directly via fxz on two bionic's, and can/will soft brick your phone. This has been documented not to because the webtop files are not included in the .905 fxz files, and if you flash an existing systems running 905 you will corrupt your firmware(the good old AP Fasboot failing to boot with an A.6 error I have tested this on two bionics with the same results both running .905. The solution is to flash back to .902, and then apply the OTA update(or dump the update to the cache directory) to .905. That is just a warning.
jedi453 said:
Hey,
This is a pretty long post, so if all you're interested in is the 905 FXZ file, scroll down to the "FXZ to 905" section, it's bolded.
Problems with flashing ICS ROMs ( in regards to OP, by Atheistnofaith ) :
You may already know this, but each custom ROM is "built off" of one of the stock roms, flashing from a different starting point will often cause your phone to not boot correctly ( boot loop, or freeze at the Motorola logo ), or will boot, but not work correctly ( i.e. something like data will not work ). This, combined with the fact that many new ICS ROMs are built on the ICS leaks, could account for the problem ( Are you sure you're not trying to flash a ROM built on an ICS leak? That would definitely not work! ).
Another possible issue is that you are using the Bionic Bootstrap program to flash CWM. The version of CWM flashed by that program is rather old ( 4.x.x.x vs current: 5.x.x.x ). You may not like this, but Safestrap is the way to go. Before you defer me to the OP, "I am aware of safestrap(but I do not want to "pseudo dual boot", ROMS, I prefer to flash over existing installs." I want to point out that Safestrap is not for the purpose of Dual-booting ROMs, or at least, that's not how many people use it. Safestrap has many features that will: prevent being stuck at bootloops ( and needing to re-Flash 902/905 every single time ), allow you to always have a backup system ( i.e. I've soft-bricked the side that I flashed ROMs on, and since I needed to use my phone, I just opened safestrap ( battery pull, start booting phone, and hit the menu button at the Safestrap prompt ), and toggled safe system in the safeboot menu. This brings up another advantage of Safestrap: you don't need to be able to boot the phone to access CWM, installing safestrap adds a new bootup prompt that either lets you open safestrap or boot normally. Again safestrap is based on a much newer version of CWM, so if you don't want to install it for any other reason, install it for that one...
Setting up for, and using Safestrap:
So if I've convinced you that you want to use Safestrap ( I really recommend you do ), follow the instructions given here: http://forum.xda-developers.com/showthread.php?t=1771993 until step 10. Then root with motofail, and install Safestrap 2.0 ( download it here:
Code:
http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1328100&v=1&libid=1343056993296&out=http%3A%2F%2Frombot.droidhive.com%2FROMs%2Ftarga%2FBionicSafestrap-ICS-2.00.apk&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D1006&title=%5BLIST%202012-07-18%5DOne%20Stop%20Shop%2C%20ROMS%2C%20MODS%2C%20SCRIPTS%2C%20TOOLS%2C%20ROOT%2C%20BOOTSTRAP%20-%20xda-developers&txt=2012-06-22%20Safestrap%20v2.0&jsonp=vglnk_jsonp_13430595105542
). The file should be an apk, just install it on your phone, open it, and select the option to flash it.
If I haven't convinced you to use Safestrap, go to the section titled, "Picking a compatible ICS ROM". ( Then reconsider, and come back, lol ).
When you're ready to flash a ROM, power off the phone, turn it back on, while booting, a new screen will pop up, saying something like "Safe system: Disabled", while that screen is shown, hit the menu button. The screen will temporarily go blank ( Don't panic ), then it should enter a CWM-like setup ( it looks very similar and functions the same ). Now's a good time to do a full backup ( Same as CWM ). From there, go to safeboot menu, then go to toggle safe system ( Don't do quick toggle ). This will take a few minutes. Next flash the zip like you normally would with CWM. If All goes well, you can exit that ( same as CWM ) and the ROM should boot. If it doesn't ( give it at least 5 minutes though ), do a battery pull, and power on the phone again, going into the Safestrap menu like before ( hit the menu key at the screen ), and then go to the safeboot menu and toggle safe mode ( DO NOT QUICK TOGGLE NOW!!! Doing this will require you to re-FXZ ). After that finishes, reboot and your phone should be back to stock, ready to load a working ROM on it.
Picking a compatible ICS ROM:
As mentioned before, each ROM is built on a certain OTA release, like 905 or 902, or even the leaked ICS OTAs. Any ROM that say "ICS" and "LEAK" in its name is not for 905, or anything prior. For a list of 905 based ICS ROMs, check this out: http://rombot.droidhive.com/ROMs/targa/ ( Make sure you don't install anything from the "ics-leak-builds" folder ). CM9, AOKP, and AOKP AXIOM should all contain 905-based ICS builds. Try flashing something from there.
If you have a specific ROM in mind, read the forum post about it, making sure it doesn't say that you need to be on an ICS leak build. Make sure it's 905 based.
FXZ to 905:
I found two links to the new 905 FXZ. While I can't guarentee that either will flash ( I don't want to flash right now, I like where I am... lol ), I have tested and found that RSD Lite is willing to extract them, so they should flash. If one doesn't work, you can always try the other:
https://docs.google.com/open?id=0B26Hj6_2TMNTZ256eV9QbWpBSTQ from: http://forum.xda-developers.com/showthread.php?t=1771993
http://www.mediafire.com/download.php?71oyq7h8eskax6d from: http://androidforums.com/motorola-d...u-ics-back-updated-7-21-12-a.html#post4664922
Keep in mind that flashing these will essentially perform a factory reset on your phone, remove root, remove CWM and Safestrap, and possibly wipe all internal storage ( i.e. /sdcard and /mnt/sdcard ).
Conclusion:
Hopefully you found what you're looking for here. I would suggest trying out an ICS leak, they're all much more stable than the 905-based ICS builds. Also, there's a good amount of development going on that's based on them. ( For ICS builds based on the ICS leaks, See here: http://rombot.droidhive.com/ROMs/targa/ics-leak-builds/ ).
So if you want to try out an ICS leak, here's a link to a how-to ( but first a disclaimer ):
WARNING: DO NOT FLASH THE 235 ICS LEAK. YOU WILL NOT BE ABLE TO FXZ BACK TO 905. YOUR BEST BET IS 232
http://forum.xda-developers.com/showthread.php?t=1771993
If you use the 905 FXZ linked to above, make sure to give crobs808 ( The OP of that above thread ), a good thumbs up, he's the one that posted the FXZ.
Sorry this got so long. I hope this helps you get things working again. Good luck,
jedi453
Click to expand...
Click to collapse
Thank you for the advice, I have already tried safestrap, but I do not want to dual boot,(safe strap will not allow you to flash over any currently installed ROMS, it appears to "sandbox" and new installs). To answer your question, I am not using the ICS leaks straigh AOKP, AOSP, and CM9(none flash without bootloops in CWM), and I understand the only way to install them is via stock recovery. lol I do not want a "sandboxed rom", because it simply is wasteful in regards to diskspace. Although, I do have a question are the ICS leaks still using motoblur as a the default launcher? Thank you again!!!
I have my Droid 3 working with the Stock rom and the safetrap using MiniMoto. Right now with all the changes I have made to it it works good, now I want to move it from safetrap to the phone as the default rom, I haven't found much info of going from safetrap to flash into the phone, any ideas?
As far as I know, I see that I would have to use the rsd, but I see that it flashes img files, I just have the zip file from the latest minimoto so... I am lost here.
XDADoog said:
I have my Droid 3 working with the Stock rom and the safetrap using MiniMoto. Right now with all the changes I have made to it it works good, now I want to move it from safetrap to the phone as the default rom, I haven't found much info of going from safetrap to flash into the phone, any ideas?
As far as I know, I see that I would have to use the rsd, but I see that it flashes img files, I just have the zip file from the latest minimoto so... I am lost here.
Click to expand...
Click to collapse
AFAIK there is no way to transfer a rom from safestrap to the stock system.
As a thought, and I have no idea if this would work, if you're using safestrap 3+ it saves custom roms as image files on the sd and mounts then for use. Logically you could try flashing this image file using motofastboot but I'm just talking out my ass, so...
If you're on an older safestrap, I had an idea about this once, I'll see if I can find the post I wrote when I get off work. I never tried it but it made sense to me
Sent from my XT860 using xda premium
I see...
So, just to be clear, to flash over stock it has to be an img file. The rom developer must have this option instead of zip? I'm looking to replace the stock rom with something less bloated like MiniMoto but as far as I see most of the Droid 3 roms apparently only run on Safestrap (I have the latest version 3.5) Damn I was looking to move all to the phone system so it would run a little bit faster
P.D.: Are there roms that could be flashed to replace the stock one then?
XDADoog said:
I see...
So, just to be clear, to flash over stock it has to be an img file. The rom developer must have this option instead of zip? I'm looking to replace the stock rom with something less bloated like MiniMoto but as far as I see most of the Droid 3 roms apparently only run on Safestrap (I have the latest version 3.5) Damn I was looking to move all to the phone system so it would run a little bit faster
P.D.: Are there roms that could be flashed to replace the stock one then?
Click to expand...
Click to collapse
Any rom can be flashed over stock, just not worth safestrap. You need plain old bootstrap app. However that doesn't help you move an existing rom install(which is what I thought you were asking)
I don't use safestrap on my phone and have minimoto installed as my stock rom. Just be aware brick recovery can be more difficult as I've had issues getting back into cwm after flashing a rom. Rsdlite will still get you back to stock no problem though so not that big a deal
Here is a http://db.tt/rNhVQCsclink for bootstrap. You'll need to boot into stock system and completely remove safestrap before you install this. I like to rsdlite or fastboot to complete stock personally, but not strictly necessary. Safestrap backups are not compatible with cwm. I can't fully guarantee this bootstrap works. I use a milestone version(since I have the XT860).
Sent from my XT860 using xda premium
So, to understand, I could flash minimoto over stock, but not use safestrap later? I had the idea to have flashed minimoto over stock and then a safestrap with other minimoto, if one fails I can go over the other and make changes accordingly. Bad or good idea?
XDADoog said:
So, to understand, I could flash minimoto over stock, but not use safestrap later? I had the idea to have flashed minimoto over stock and then a safestrap with other minimoto, if one fails I can go over the other and make changes accordingly. Bad or good idea?
Click to expand...
Click to collapse
Once you've flashed minimoto to stock you can remove the bootstrap and reinstall safestrap, yes. It seems redundant to have 2 versions of the same rom flashed to the phone, seems like less effort to just make sure to backup before making any changes, but it's your phone to do with as you will.
I don't use safestrap because I don't care about being able to reflash my phone. I hate this thing and am just waiting for it to die so I can replace it.
Sent from my XT860 using xda premium
:cyclops::cyclops: is not such a bad phone, if it just had more ram it would be fine. But 512Mb is just not enough (never ever )
XDADoog said:
:cyclops::cyclops: is not such a bad phone, if it just had more ram it would be fine. But 512Mb is just not enough (never ever )
Click to expand...
Click to collapse
And it's stuck on gb. I can't listen to music and have my running app open. One of them will close due to lack of ram. Keyboard sucks ass on mine. Button presses only register half the time. Same for the capacitive keys. Apps often take up to 10 seconds to Open(probably because it needs to clear ram)
Sent from my XT860 using xda premium
So, just to be sure (sorry for the delay, on monday I am officially on vacation so I was doing all the make up work that I had to do :fingers-crossed: )
I can flash minimoto over stock
Then install safe trap and install minimoto on the rom slot
Why?
Because I like minimoto and I have found that for this phone and my lifestyle it fits really well, the problem is that on safestrap mode I believe the lag is because he's reading some stuff from the sdcard and the internal memory (both I think and believe (I could be wrong, I am just an advanced user ) are slower than the reserved space for the rom itself), so I will start from scratch again install only the programs I really need on the phone rom and leave the safestrap rom for those scenarios where the phone is stuck on something.
Is that all virtually correct and possible, right?
XDADoog said:
So, just to be sure (sorry for the delay, on monday I am officially on vacation so I was doing all the make up work that I had to do :fingers-crossed: )
I can flash minimoto over stock
Then install safe trap and install minimoto on the rom slot
Why?
Because I like minimoto and I have found that for this phone and my lifestyle it fits really well, the problem is that on safestrap mode I believe the lag is because he's reading some stuff from the sdcard and the internal memory (both I think and believe (I could be wrong, I am just an advanced user ) are slower than the reserved space for the rom itself), so I will start from scratch again install only the programs I really need on the phone rom and leave the safestrap rom for those scenarios where the phone is stuck on something.
Is that all virtually correct and possible, right?
Click to expand...
Click to collapse
I get lag using it on stock rom too. You may find some improvement by flashing it over stock. Safestrap mounts an image file as a loop device, which I have heard is slower, although I couldn't confirm that through googling. Android seems to start to lag over time, I find flashing fresh often gives improvements, then it slows down again, then flash again etc
Sent from my XT860 using xda premium
ive had the phone since at&t had it on display. rooted it and had various roms for the last couple years and never had any serious issues. last night i flashed jellycream v2 and then did a factory reset inside the rom. the phone prompted that it would reboot twice and that it was normal. it rebooted into twrp and did nothing afterwards. i rebooted it from the recovery and all it did was reboot back into recovery. i decided to flash a different version of twrp and still the same. then flashed clockwork and still got the same result. i wiped the bootloader and basically went through the rooting process again. flashed the latest version of twrp and the phone is still only booting into recovery.
i am at a loss because this is as far as my knowledge goes. its like the phone is stuck still trying to wait for that factory reset from the jellycream rom or something and it wont do anything else but load TWRP.
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
drastic00 said:
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
Click to expand...
Click to collapse
so far i get the grey LG screen with 'booti mmc_read xxxx' at the upper left with the hard reset. it only takes 2 seconds to show up but the phone shuts off if i continue to hold the power and volume buttons. ill read up on that link here.
I missed that you wiped bootloader. You need that . So you could maybe just install the wkpark bootloader in recovery. You would do 1 and 3 here (1.25a file is down the page)
http://forum.xda-developers.com/showthread.php?p=39130435
I think Jellycream actually requires you have it, if I remember correctly.
Not sure why factory reset would cause that issue, but it will definitely not start without bootloader.
Flashing firmware will also write the (stock) bootloader if that does not do it. It will also reinstall the OS if system is corrupt or missing.
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
drastic00 said:
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
Click to expand...
Click to collapse
ok basic rundown of what i did in the last year;
when first played around with rooted it about a year ago i used all-in-one to do it. i had already upgraded to ics using the lg mobile support tool prior to rooting. rooting went off fine until i installed a Beats Audio app from the play store. when the phone rebooted after it would be stuck at the grey LG logo. i didnt know what to do so i used twrp and wiped the whole phone. then i used all-in-one and flashed the ICS bootloader and did the flash kernel 4 fix or something its one of the last options to do. then using twrp i flashed ICS_V20_P20, Stock_V20P_Rooted, and a Thrill Update, the phone rebooted fine in an ICS rom but it ran like complete ****, so i tried various roms and the one i settled with was called OptimusRS V1. i used that up until 2 days ago when i flashed the jellycream rom.
after i factory reset that i tried to flash the different wkpark bootloader and twrp that came with the megatron tool hoping that would fix the issue. but it did so i reflashed the original twrp and ics bootloader from all-in-one.
failed to mention this before but i tried 3 different recovery files in between each attempt and it would flash and reboot fine but the phone would still do the same thing and just load recovery.
ill find links when i get off work today. thats the basic history of the phone though.
Hmm. Stil not sure then . Maybe a corrupt zip or you wiped something important. Flashing with LG Flashtool should recover it. And always make a Nandroid backup before installing anything from recovery.
http://forum.xda-developers.com/showthread.php?t=2392309
thats the jellycream rom.
im downloading the files for your xbsa rom at the moment. i do remember yesterday when i used the megatron tool i saw an option to flash the stock bootloader and recovery. i tried it but all i got was the pink LG logo then a security error message below it and the phone shut off.
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
drastic00 said:
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
Click to expand...
Click to collapse
well that breaks down that a bit better. my progress at the moment is step f6. when i connect the phone nothing installs though. it just reconnects and disconnects every second or so. im guessing its because i already have those files. dunno though. i cant get my pc to install the adb drivers for the life of me when the phone is connected in recovery mode.it sees the new hardware just cant find the files.
actually i got it. for some reason the phone wouldnt install anything until i put the battery back in at that step. i continued successfully to step M. the phone is setting up my google account at the moment.
will flashing the baseband be necessary if my apn and sim work like the phone is now? my provider is h20(canadian i heard) but im the usa.
HUGE thanks regardless
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
drastic00 said:
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
Click to expand...
Click to collapse
im only getting E for data. i tried to flash a baseband meant for at&t but it says failed after about 90 seconds. still no 4g though. i did flash the xbsav8 before i set my apn up. i might just go with an optimusRS rom again though. i was happy with it. probably not jellycream this time.
Baseband fail after 80 or so sec is normal. It means it worked. Check your baseband in android settings/about phone.
You might try speed test app to compare actual speed. ATT 4G icon is a lie on this phone IMO.
Now that your pc is set up you can flash any P925/920 bin. Kdz files (combo of bin and fls, there is another tool for flashing those files) can be extracted into separate bin and fls, but I have not done it. The advantage is you can flash baseband separately.
Xbsalls vX3D (see his page) with the P925G fls file gives me 4G icon on Straight Talk in the US, but I like his vR3D better, and I can't tell a speed difference, honestly.
I have not actually measured the speed in either, however.
And for either of those ROMs, you must flash his large partition version of v28B first...very important.
oh its definitely like 2g speeds. its pretty slow. i tried using my providers app and website and its saying the phone i have isnt registered to them anymore so it might be just that. if thats the case ill just bring it in so they can do that for me. when i rooted it the first time i wasnt getting any data and they had to re-register the phone to get it to work right.
my baseband says OMAPP4430/XMM6260. for comparison and/or confirm differences. i have no idea lol.
side question though; my sdcard still has recovery files for the optimusRS v1 rom i had on it. i really liked the setup i had when i made the recovery for it. Im tempted to reinstall it but im really not too sure if itll work or worse harm my phone again.
Lots of variables, but you must remember that xbsall's P940 recovery app he he uses has recovery in system partition. The recovery you had before was probably in recovery partition. They write restores from two different places. Probably you would get an error, but not positive. Understanding that may take some Googling...
If you try it, back up before trying to restore the old backup. Then you could hopefully restore if the restore fails, know what I mean?
Probably the safest thing is to use the all in one tool to install recovery in recovery partition and use that one to restore backup.
I do know when I have restored backups, I have wiped Dalvik, Cache, and Factory Reset (in recovery) and then restore. Then it works. Some people wipe system too.
You can usually flash to recover from a problem, but then you have to set your phone up again
Well I recovered everything. All settings and personalized stuff. Just everything. Everything is running normal again. Just now my data is saying im using an h20 microcell instead of just H20 with a 4g connection. This 2g stuff is for the birds. I'm almost thinking the firmware we flashed has something to do with it. The phone is functional though. Just slow and no mms. I haven't been able to find much on the forums about it. I'll poke around more tomorrow.
Sent from my LG-P920 using xda app-developers app
I'd try another baseband.