Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283
jgardner said:
Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283
Click to expand...
Click to collapse
Why not do the nandroid with safestrap?
I didn't think safestrap was working with the D4?
jgardner said:
I didn't think safestrap was working with the D4?
Click to expand...
Click to collapse
I dont know whats going on lol.....everyone is coming with all these different stories. I used the root exploit that was out and used the safestrap for recovery. I dont think I did anything different than anyone else. And then i took a chance flashing a Razr rom
Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk
jgardner said:
Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I took it out until Hashcode brings it out for Droid 4. I've been corresponding with him and if the maker of Safestrap tells you it isn't safe to use on Droid 4 yet then you usually should listen.
All up to your risk though.
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.
mattlgroff said:
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.
Click to expand...
Click to collapse
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
---------- Post added at 02:27 AM ---------- Previous post was at 02:24 AM ----------
As far as the warnings i didnt see the warning to not use safestrap till i got on here and it was to late. I figured since i was able to boot into recovery and make a backup i would be ok
Briteyez83 said:
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
Click to expand...
Click to collapse
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.
Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Which FASTBOOT error are you seeing? It should be referencing one of the partitions.
Sent from my DROID4 using XDA App
greekchampion04 said:
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.
Click to expand...
Click to collapse
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.
Briteyez83 said:
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.
Click to expand...
Click to collapse
I cant help unless I know what your error message says when you turn on the phone. :/
Sent from my DROID4 using XDA App
Send me your email addy in a message and ill send you a pic of it
Briteyez83 said:
Send me your email addy in a message and ill send you a pic of it
Click to expand...
Click to collapse
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?
Hashcode said:
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?
Click to expand...
Click to collapse
No, i dont. Im new to root, just rooted in nov. If you give me something thst would fix it that would be awesome.
Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.
Hashcode said:
Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.
Click to expand...
Click to collapse
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.
Briteyez83 said:
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.
Click to expand...
Click to collapse
If it works, I'll create a new thread with the instructions as I believe there are a few in your situation.
Yes there is quite a few. Ill let you know as soon as i can
Related
Not sure if this has already been posted somewhere, but after my experience I figured it might be useful to someone. If it's been posted already ignore this and move on with your day/night
1. flash sbf
2. phone will go in the boot loop of death, thats fine lol.. when rsdlite says 100 percent pull the battery
3. put the battery back in, hold down the home button plus the power button till you see the moto logo followed by the triangle
4. hit search button, your now in recovery
5. do a factory restore
6. once complete reboot phone
7. thank god and swear you wont flash your phone ever again (ofcourse only to do it in a day or so after you have calmed down)
rsdlite and sbf can be found in this thread CLICK
If you made a nandroid backup of 2.1 couldn't you just restore that? I'm pretty sure you can. I remember doing it with the Moto Droid.
taypotts said:
If you made a nandroid backup of 2.1 couldn't you just restore that? I'm pretty sure you can. I remember doing it with the Moto Droid.
Click to expand...
Click to collapse
not sure if you can use bootstrap in froyo, and besides if you ever need to go back to a unrooted state this is the way to go :: cough warranty ::
taypotts said:
If you made a nandroid backup of 2.1 couldn't you just restore that? I'm pretty sure you can. I remember doing it with the Moto Droid.
Click to expand...
Click to collapse
Do not restore a 2. 1 nandroid in 2. 2. The update changes the bootloader and recovery versions which aren't part of the backup. The phone will just hang at the MOTO logo. I learned this the hard way. You have to use the sbf. You can then apply your nandroid to get everything back.
Sent from my DROIDX using XDA App
iB4STiD said:
Not sure if this has already been posted somewhere, but after my experience I figured it might be useful to someone.
Click to expand...
Click to collapse
Could you explain?
I am holding off on switching to 2.2, always do to let everyone else find the bugs.
What was your experience?
bad4u6669 said:
Could you explain?
I am holding off on switching to 2.2, always do to let everyone else find the bugs.
What was your experience?
Click to expand...
Click to collapse
what i meant by my experience was downgrading 2.2 to 2.1, My g/f has the droid x, and i am the one to root or mod her phone for her. She wanted to try out froyo and liked the rom alot. there are little bugs i noticed
1. odd little animation hiccup when scrolling home screens
2. lag in gallery
3. what seemed like market delay (but the market has been slow lately, same thing on my vibrant and g1)
but this is a test build not a "final rom"
Like i said downgrading the phone is a little different than other android phones Ive used and i thought this post may help someone out. Im the type of person who wont mod something unless i know i can get back to where i started and with this sbf and "how to" you wont have to worry about that.
pjsockett said:
Do not restore a 2. 1 nandroid in 2. 2. The update changes the bootloader and recovery versions which aren't part of the backup. The phone will just hang at the MOTO logo. I learned this the hard way. You have to use the sbf. You can then apply your nandroid to get everything back.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
also i believe it updates the radio and kernel.. thanks pj for explaining that
If I wanted to go to 2.1 ,don't see why...at the moment.
Before I do a SBF would it be ok to to do a data wipe and a partition wipe in recovery mode then do the SBF bootrecovery deal???
Thank You
after you upgrade to 2.2 koush has a new DroidXBootstrap.apk out
go back to his website and DL it and reinstall then rerun bootstrap.
after that rom manager can do backups or recoveries.
sucks you all get bootloop with sbf, ive done it twice now and has worked fine
keeps all my apps and stuff
goodluck
pjsockett said:
Do not restore a 2. 1 nandroid in 2. 2. The update changes the bootloader and recovery versions which aren't part of the backup. The phone will just hang at the MOTO logo. I learned this the hard way. You have to use the sbf. You can then apply your nandroid to get everything back.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I'm kinda confused what you mean? I did a nandroid backup of 2.1 with the latest bootstrap and clockworld.
I just remember using a nandroid on my girl's moto droid and I went from 2.2 all the way back to 2.0.1.
when trying to sbf on my Mac I get this -bash: ./sbf_flash: Permission denied? Any suggestions I have been asking for 2 days now hopefully someone can help. Thanks
taypotts said:
I'm kinda confused what you mean? I did a nandroid backup of 2.1 with the latest bootstrap and clockworld.
I just remember using a nandroid on my girl's moto droid and I went from 2.2 all the way back to 2.0.1.
Click to expand...
Click to collapse
I also did the same from my Eris. The major difference is that the recovery on those devices were completely replaced not just patched. When you restore a 2.1 nandroid from a 2.2 droid x the android 3e recovery is not replaced. When the system tries to boot it sees that as an invalid recovery image and won't boot, it just hangs at the moto logo forever. When you upgarde to 2.2 on a Droid or an Eris your still using clockwork recovery or amon ra's recovery and not upgrading to the android 3e system recovery. Maybe it was just a fluke that it didn't work for me but it makes sense as to why it would fail, otherwise we would be able to have a full custom recovery.
dscottjr81 said:
when trying to sbf on my Mac I get this -bash: ./sbf_flash: Permission denied? Any suggestions I have been asking for 2 days now hopefully someone can help. Thanks
Click to expand...
Click to collapse
From my understanding sbf_flash is for linux only. To flash on mac you need to use rsd lite with a virtual windows os.
http://www.droidforums.net/forum/droid-hacks/38671-flashing-sbf-mac.html
i cant get my phone to flash. i have done this 2 before with my droid x on 2.1 but now that i am on 2.2 every time i try to use RSDlite, i connect my phone and select my SBF but the START button will not light up so i cannot proceed. any thoughts.. im running windows 7 64 and i have all the drivers working for my phone.
failed sbf flash
Hey guys, i got an error in RSD that says "Failed flashing process. Failed flashing process. Phone[0000]: Phone is not compatible with muli-interface super-file. (0x703B); phone connected
Any ideas, i'm really new to android stuff, been using WM forever.
Thanks for the help
please ignore me as I can't read apparently
if anyone else sees this remeber to copy the pst_flash file to the Program Files/Motorola/RSDLite directory
tacticalmedicokc said:
please ignore me as I can't read apparently
if anyone else sees this remeber to copy the pst_flash file to the Program Files/Motorola/RSDLite directory
Click to expand...
Click to collapse
thanks. i had the same problem.
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
atquick said:
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
Click to expand...
Click to collapse
http://goo.gl/7NoAv
Androidsims said:
http://goo.gl/7NoAv
Click to expand...
Click to collapse
Tried that. It keeps failing saying something about size was not as expected or something like that.
Redownload?
Avelnan said:
Redownload?
Click to expand...
Click to collapse
I have. MD5 sums match up each time. Should I try removing the ext sd card?
I would redownload everything and try agian
littleneutrino said:
I would redownload everything and try agian
Click to expand...
Click to collapse
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
atquick said:
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
Click to expand...
Click to collapse
Downloading the sbf's again. Went over to check and see if the phone was still on, The charging led is on, however the screen is off..
Held power, nothing. Held M + Power. Still nothing... Any thoughts on whats going on now?
I didn't see if you have pulled the SD card but yeah it can't hurt.
Sent from my DROID3 using XDA App
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
wattnxt said:
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
It keeps failing.
Step 3 mbmloader.bin
Step 4 mbm.bin
Step 8 logo.bin
Step 9 'lbl'
I'm stuck.
Let me do some looking when I get home tonight. I remember there being a file for certain versions of XP that helped some people and they couldn't flash without it.
I never had it happen personally, but I know those that did were terribly frustrated.
I also hear the 959 version is easier to flash for some reason. Never flashed that version, so this is only hear-say. But I know it did flash easier according to posts.
I will try to dig up a link for you.
i am getting the same thing also getting the bad CG boot.. now this may be a fix but idk how this guy got it it.. i have been asking eveywhere maybe you guys could help me... here is the thread http://forum.xda-developers.com/showthread.php?t=1248721
I found this by Psouza. He is likely the foremost expert on making things easy as far as unbricking your D3. Rumor has it he has a set of unbrick tools floating around this forum somewhere, though I haven't found it yet. Try in the Development thread, for sure it has to be there somewhere.
Post number 84
psouza4 said:
For those of you having problems flashing this and/or are suspicious of flashing ebr, mbr, and parts of the bootloader, you can selectively just flash the rest of it.
See attachment.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=715510&d=1315657647
Hope this helps.
I also saw that flashing the pre-installs file alone first helped someone. That file borked on me once, but I was able to adb it over and then execute it via adb to get my phone unbricked.
Please let us know what works for you, as all of this is a work in progress right now.
Good luck!
i don't know to much about adb and are looking for help on pre-installed files. I don't understand what that means or how to go about it? i also cant get past the bootloader screen, "invalid CG version". i can not boot up at all.
How bricked are you? can you boot into CWM? Are you able to boot into tools, or how far can you get?
What version were you running? 5.959 (stock) or 6.890 OTA or Leaked OTA or Soak test (all the same as far as 6.890 goes).
i can get into boot tools and just tryed another flash got to step 6 till it failed instead of 3.. I'm running stock. Cannot get passed boot tools... scratch all that just tried to flash again just on the off chance it mnight work and i got it. Going to try and re-root and CWN recovery with sdteel froids rom... will keep you in the loop
Awesome!!
Here is the link about the adb commands for preinstall.sh
http://forum.xda-developers.com/showpost.php?p=17196391&postcount=88
It helped me when I borked my leaked update. I ran into the same problem as limaxray did with too many files in /system. So make sure you clean out any apps you made into system apps before trying the update via the standard update route, and that all stock system apps are in place and properly named.
I had to remove some that updated partially with the leaked update when mine borked. I used the posted system dump to push them to the phone and then the update ran properly and updated them anyhow.
If for some reason re-rooting doesn't work for you. Go to /system/bin and remove su, busybox. Do the same in /system/xbin. For some reason if you already have them in there when you run the process, it will say success but no root after reboot. My 2c as it happened to me. You do not need to remove superuser.apk, but you will have to update it in the market after you re-root.
Congrats!!
I see now too there is a fastboot and moto-fastboot. moto-fastboot has worked for some who had issues from what I've found.
Keep us posted, and smile knowing you've recovered from a bork; none of us got where we are without doing it at least once, so you're in good company.
re-rooted and installed bootstrap, just got steel droid all loaded up and all is good.... thanks for your speedy responses and detailed instructions and links. I realy think all that happened was i took everything aet it sone last time tried to flash and it went threw. All i used was RSD lite and flashed the 8.6.590 fast boot file and after a several retries it went threw. If anyone needs help on this i will post the file links if you need the ones i used
greetings,
I had the brilliant idea of flashing my droid 3, but now I'm stuck on a black screen:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.40
Battery OK
OK to Program
Connect USB
Data Cable
I used RSD Lite to flash, but it just shows
Failed flashing process. 1/18 (...) result FAIL
I'm trying to update with CW, but it stuck after the 'press menu' page
someone knows how to unbrick my phone?
http://forum.xda-developers.com/showthread.php?t=1336980
if youre trying to update through CW, you shouldnt need to use RSD. Since you have used RSD, you need to make sure you have the correct SBF. Im not sure if the Milestone 3/??Model# has an SBF! You will need to sbf (with RSD) and (probably) clear cache (through recovery m+power)
thank U vry much!
giving a try
as soon I get some results, I'll post here
and again: thank you
well... my droid is a
motorola Milestone 3 x850
Godmik said:
well... my droid is a
motorola Milestone 3 x850
Click to expand...
Click to collapse
oh..you have the XT860? In this topic http://forum.xda-developers.com/showthread.php?p=19784171 they're saying you can make nandroid backups now...I guess you didn't?
I'm not really up to date with XT860 news (there's still no subforum) but you could try flash the http://forum.xda-developers.com/showthread.php?t=1288823.
I don't know if there's an official SBF for XT860 yet
when i saw the flag in your profile, i figured you werent using our XT862. I did a couple searches but didnt come up with anything but a system dump
I did...
bot even the backup stuck....
when I boot with + and - volume buttons pressed, I can navigate to 'Normal Powerup'
then appears the CW window, where I made the backup, but when I try to restore and reboot, it keeps stucking....
http://forum.xda-developers.com/showpost.php?p=17419746&postcount=81
check out this thread, not just post 81. this guy said he tried flashing the xt862 rom to his xt860 and bricked like you. ive never had to fastboot the /preinstall partition (??), but you may find more information if you dig a little deeper. hope that helps
guys,
my greatest THANKS!
after this little time and this little help I can yell:
IT'S ALIVE!! \o/
I almost lost (another) mobile on flash (frist a Motorola v360, then a Palm Treo Pro 850)
on other hand.... it's on CHINESE!!!
but I think I can handle that..... or at least try to....
awesome. i was worried because motorola marketed two phones as the XT860, which is Bell Canada, and Vivo Brazil. everything ive checked out was for the Bell version (even though they could be the exact same base)
now, I'll try to root again, install CW and restore my backup...
wish me luck =P
thinking better....
this whole confusion started because my droid was too slow.... (I guess it's because motoblur) and restore the backup will only help to mess up with my head again
If you're on the me863 rom now thenone click root won't work, there is a link to a working root method in the me863 thread in the Droid 3 android dev forum
Rooted xt860, debloated and overclocked to 1.1
DoubleYouPee said:
oh..you have the XT860? In this topic http://forum.xda-developers.com/showthread.php?p=19784171 they're saying you can make nandroid backups now...I guess you didn't?
I'm not really up to date with XT860 news (there's still no subforum) but you could try flash the http://forum.xda-developers.com/showthread.php?t=1288823.
I don't know if there's an official SBF for XT860 yet
Click to expand...
Click to collapse
I've been making nanxroids through CWR since the d3 bootstrap first came out. Never had a problem. Its safestrap that doesn't work in xt860
Rooted xt860, debloated and overclocked to 1.1
there's only one problem: I can't instal gapps...
there's a method or a order?
Godmik said:
there's only one problem: I can't instal gapps...
there's a method or a order?
Click to expand...
Click to collapse
Yes flash with stock recovery http://www.gokuai.com/f/S2rh89s025kihzf6
Also install morelocale 2 to change language
now I got gapps working too
ty guys!
In an attempt to go from ICS 206 to 215, I followed the instructions step by step and using the utility, when I get to the step where it says instill zip file from SD card, I navigate to "D4.6.16.215.zip", apply it, and it says update aborted.
My phone will now no longer boot beyond the M Dual Core screen. It is simply blank. Does anyone have any ideas?
i was about 5mins away from doing the same thing you did before glad i saw this gonna, i'm gonna wait until you find a fix (im on .213)
icebear8 said:
i was about 5mins away from doing the same thing you did before glad i saw this gonna, i'm gonna wait until you find a fix (im on .213)
Click to expand...
Click to collapse
Well I'm back working again, but it's still on 206 even though I went through the flashing process to 215. I haven't even thought about updating my phone since installing 206 when it came out. I have read many threads that talk about "unsticking" to get from 206 to 208, but they're over a month old. I can't follow the instructions associated with unsticking because a) they're written for the razr and thus are ridiculously confusing, and b) the one thread that tries to explain how to use unstuckICS for D4 users makes even less sense.
I posted about where to get unstuckICS on another forum and someone directed me back to the Droid4withICSfix-rootLITE tool, which I already had. Step 16 seems to flash (with a TON of error that are supposedly to be expected) but then I can't apply any zip updates. All attempts abort.
This is all so maddening because nothing I try is working. At least my phone isn't a paper weigh. So I have that going for me... which is nice.
strakajagr said:
Well I'm back working again, but it's still on 206 even though I went through the flashing process to 215. I haven't even thought about updating my phone since installing 206 when it came out. I have read many threads that talk about "unsticking" to get from 206 to 208, but they're over a month old. I can't follow the instructions associated with unsticking because a) they're written for the razr and thus are ridiculously confusing, and b) the one thread that tries to explain how to use unstuckICS for D4 users makes even less sense.
I posted about where to get unstuckICS on another forum and someone directed me back to the Droid4withICSfix-rootLITE tool, which I already had. Step 16 seems to flash (with a TON of error that are supposedly to be expected) but then I can't apply any zip updates. All attempts abort.
This is all so maddening because nothing I try is working. At least my phone isn't a paper weigh. So I have that going for me... which is nice.
Click to expand...
Click to collapse
Literally the tool does nothing. I run it. Everything in step 16 essentially errors out. Ultimately the phone reboots having accomplished zero. I am "stuck" on 206.
strakajagr said:
Literally the tool does nothing. I run it. Everything in step 16 essentially errors out. Ultimately the phone reboots having accomplished zero. I am "stuck" on 206.
Click to expand...
Click to collapse
here is a boot.img i got from Droid forums https://www.dropbox.com/s/zwl0e6jx767aksb/boot-6-16-215.img try using this one and rename it to ICSFIX
icebear8 said:
here is a boot.img i got from Droid forums https://www.dropbox.com/s/zwl0e6jx767aksb/boot-6-16-215.img try using this one and rename it to ICSFIX
Click to expand...
Click to collapse
Tried that. Same result. I have to believe this has something to do with the 206 build that I'm on, though I don't know why that latest utility doesn't address this since the 206 sticking thing seems to be a problem that was addressed so long ago.
\how did you get back to normal when you soft bricked? so i know i can get back if i get the same problem. i might try this just to see if it works for me
---------- Post added at 12:34 AM ---------- Previous post was at 12:22 AM ----------
icebear8 said:
\how did you get back to normal when you soft bricked? so i know i can get back if i get the same problem. i might try this just to see if it works for me
Click to expand...
Click to collapse
VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01.xml.zip this is the fastboot GB 219 files correct? my files are all over the place lol
I just booted to recovery and did a data wipe/factory reset, and I was back to stock 206. I didn't use that xml file because I'm not upgrading from GB.
well i just bricked my self on the update lol
Not sure why you guys are having trouble. I used the tool yesterday to go from 213 to 215. Basically we are flashing the GB files, then the boot.img for 215, letting it reboot and attempt to update, it will stick at the moto boot logo, then flashing the update in stock recovery. The only thing that might be of issue is if you are running safestrap, menu 16 is designed to not over write your data. I haven't tried running safestrap and using menu 16 to update. You can try the old method of flashing the GB files, Flashing the boot.img and then recovery update flash.
jsnweitzel said:
Not sure why you guys are having trouble. I used the tool yesterday to go from 213 to 215. Basically we are flashing the GB files, then the boot.img for 215, letting it reboot and attempt to update, it will stick at the moto boot logo, then flashing the update in stock recovery. The only thing that might be of issue is if you are running safestrap, menu 16 is designed to not over write your data. I haven't tried running safestrap and using menu 16 to update. You can try the old method of flashing the GB files, Flashing the boot.img and then recovery update flash.
Click to expand...
Click to collapse
In terms of names - are you using boot.img or ICSFIX.img for the name of boot on .215?
Right, but you're not dealing with upgrading from 206, which is supposedly the pain in the ass build to upgrade from.
strakajagr said:
Right, but you're not dealing with upgrading from 206, which is supposedly the pain in the ass build to upgrade from.
Click to expand...
Click to collapse
I`m going to update from 213 to 215, and still need an anwer: ICFIX.img or boot.img?
Thanks in advance.
mrAdvo said:
I`m going to update from 213 to 215, and still need an anwer: ICFIX.img or boot.img?
Thanks in advance.
Click to expand...
Click to collapse
You should be able to rename to boot.img and upgrade from .213 to .215. As for the .206 upgrade you may have to follow the full upgrade process outlined in the ics upgrade thread in which you have to flash the gb fastboot before upgrading to the next build. It seems to have worked for most people going from leak to leak.
Sent from my DROID4 using xda app-developers app
If your using the modified D4 tool I made then you should name it ICSFIX. However I think we can shorten the process further and will try to work on that tonight.
Sent from my DROID4 using Tapatalk 2
azrael293 said:
You should be able to rename to boot.img and upgrade from .213 to .215. As for the .206 upgrade you may have to follow the full upgrade process outlined in the ics upgrade thread in which you have to flash the gb fastboot before upgrading to the next build. It seems to have worked for most people going from leak to leak.
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Wait, are you saying that you can just flash the boot.img without having to fastboot GB?! Cause if that is the case, I wasted a ton of time last night going from 213 --> 215
podspi said:
Wait, are you saying that you can just flash the boot.img without having to fastboot GB?! Cause if that is the case, I wasted a ton of time last night going from 213 --> 215
Click to expand...
Click to collapse
Going by the tool you would have to flash the fastboot of the GB files then proceed to flash the current leak. Same as with all the previous leaks. What I meant by flashing it as boot.img is that name format should work, tho jsnweitzel said that with his tool it should be named as icsfix.img instead. he replied right after I had posted and I'd go with his response since it is his code/tool. lol
azrael293 said:
Going by the tool you would have to flash the fastboot of the GB files then proceed to flash the current leak. Same as with all the previous leaks. What I meant by flashing it as boot.img is that name format should work, tho jsnweitzel said that with his tool it should be named as icsfix.img instead. he replied right after I had posted and I'd go with his response since it is his code/tool. lol
Click to expand...
Click to collapse
Ok, I was just afraid for a moment I had wasted a bunch of nail-biting time or something
I think a lot of people get tripped up at the boot.img --> ICSFIX.img step. Especially because the instructions tell you to rename it to ICSFIX, not ICSFIX.img (which Windows may or may not do for you automatically, depending on your settings).
That being said, it is still incredibly easy to move from one leak to the other with the utility, it is incredibly awesome.(Thanks jsnweitzel!)
Can't get into recovery or anything can someone help or point me into the right place to fix this just need to get the phone up and running the rest i can do root ect,,,,,
mobgod said:
Can't get into recovery or anything can someone help or point me into the right place to fix this just need to get the phone up and running the rest i can do root ect,,,,,
Click to expand...
Click to collapse
Does your phone turn on at all?
i can get into fastboot but thats about it
mobgod said:
i can get into fastboot but thats about it
Click to expand...
Click to collapse
maybe the correct files to flash or what i can do to just get the phone back to stock
mobgod said:
i can get into fastboot but thats about it
Click to expand...
Click to collapse
You will have to use RSD and fxz you phone back to stock. I was in you situation once tried using the bootstrap built for the razor. As long as you can access fast boot mode your alright. Here's the link where you can find the file you need. http://forum.xda-developers.com/showthread.php?t=132810
Get the. 902 fastboot file.
nobe1976 said:
You will have to use RSD and fxz you phone back to stock. I was in you situation once tried using the bootstrap built for the razor. As long as you can access fast boot mode your alright. Here's the link where you can find the file you need. http://forum.xda-developers.com/showthread.php?t=132810
Get the. 902 fastboot file.
Click to expand...
Click to collapse
I've tried that keeps failing with rsd step 6 I believe the first time I got to step 20 than all hell broke lose I believe it was something about web top. Should I just try 902 again is what your telling me ? Also big question is how can I charge the battery I'm getting low battery in fastboot ??
Sent From My Rooted 3D
mobgod said:
I've tried that keeps failing with rsd step 6 I believe the first time I got to step 20 than all hell broke lose I believe it was something about web top. Should I just try 902 again is what your telling me ? Also big question is how can I charge the battery I'm getting low battery in fastboot ??
Sent From My Rooted 3D
Click to expand...
Click to collapse
You might have bad partitions. That might be pretty hard to fix with only rsd light you might have to make your own fxz flashable zip to repartition your phone. That would take some good coding skills.
androidifyme said:
You might have bad partitions. That might be pretty hard to fix with only rsd light you might have to make your own fxz flashable zip to repartition your phone. That would take some good coding skills.
Click to expand...
Click to collapse
you RSDd over safestrap didnt you..
nitephlight said:
you RSDd over safestrap didnt you..
Click to expand...
Click to collapse
Not sure trying to fix my buddy's phone but I think the battery is to dead now how can I charge it ??
Sent From My Rooted 3D
mobgod said:
Not sure trying to fix my buddy's phone but I think the battery is to dead now how can I charge it ??
Sent From My Rooted 3D
Click to expand...
Click to collapse
goto radio shack and buy one of those chargers that works for most batteries like phones and cameras or you can try the usb cable hack.
once charged you will need to FXZ through RSDLite.
RSDLite 5.7
http://d-h.st/Wja
FXZ 905 - Please read the README.txt for more info
http://d-h.st/W6A
Motorola Device Manager (up-to-date USB drivers for Windows)
http://www.adrive.com/public/ABQ6M2/MotorolaDeviceManager_2.2.26.exe
mobgod said:
Can't get into recovery or anything can someone help or point me into the right place to fix this just need to get the phone up and running the rest i can do root ect,,,,,
Click to expand...
Click to collapse
mobgod said:
i can get into fastboot but thats about it
Click to expand...
Click to collapse
mobgod said:
I've tried that keeps failing with rsd step 6 I believe the first time I got to step 20 than all hell broke lose I believe it was something about web top. Should I just try 902 again is what your telling me ? Also big question is how can I charge the battery I'm getting low battery in fastboot ??
Sent From My Rooted 3D
Click to expand...
Click to collapse
twinkyz1979 said:
goto radio shack and buy one of those chargers that works for most batteries like phones and cameras or you can try the usb cable hack.
once charged you will need to FXZ through RSDLite.
There is a program that SamuraiHL has posted called House of Bionic. It's on the droidforums web site and you should be able to search for it there. Either that or google House of Bionic. It should bring up the thread where you can download this program. It's definitely a lifesaver. I would post the link myself but I haven't posted here enough yet to do that.
Hope this helps you out!
Cindy
Click to expand...
Click to collapse
cindylike24 said:
twinkyz1979 said:
goto radio shack and buy one of those chargers that works for most batteries like phones and cameras or you can try the usb cable hack.
once charged you will need to FXZ through RSDLite.
There is a program that SamuraiHL has posted called House of Bionic. It's on the droidforums web site and you should be able to search for it there. Either that or google House of Bionic. It should bring up the thread where you can download this program. It's definitely a lifesaver. I would post the link myself but I haven't posted here enough yet to do that.
Hope this helps you out!
Cindy
Click to expand...
Click to collapse
Link to usb hack http://www.droidforums.net/forum/dr...-code-corrupt-battery-low-cannot-program.html
Link to House of Bionic. http://www.droidforums.net/forum/mo...wngrade-902-no-app-data-loss.html#post2173723
Make sure you download the latest drivers and the right rsd to be used. Link to find both http://www.droidhive.com/forums/ind...nks-in-op-updated-dailyformerly-whats-in-dev/
The reason for it error in out is because the phone doesn't have enough juice to do the fxz process. Make sure that battery has over 50% charge before attempting or do the usb hack with a cord that you will no longer be using.
Click to expand...
Click to collapse
I had this same problem. I used my warranty and got a new bionic. I blame Verizon and Motorola for not giving us what we want with an unlocked bootloader. Personally, I feel they should support the rooting community and be able to reinstall the operating system when we mess up, similar to how we can reinstall windows on a computer. They can even charge $50 for the service and be able to do it in-store from a computer. Not only could they make more money, they wouldn't have to replace as many devices.
Sent from my DROID BIONIC using Tapatalk 2
smokedkill said:
I had this same problem. I used my warranty and got a new bionic. I blame Verizon and Motorola for not giving us what we want with an unlocked bootloader. Personally, I feel they should support the rooting community and be able to reinstall the operating system when we mess up, similar to how we can reinstall windows on a computer. They can even charge $50 for the service and be able to do it in-store from a computer. Not only could they make more money, they wouldn't have to replace as many devices.
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
You blame Verizon because you voided the warranty and ****ed up your own phone? Blame yourself for buying a phone that was known to have a locked bootloader to begin with.
smokedkill said:
I had this same problem. I used my warranty and got a new bionic. I blame Verizon and Motorola for not giving us what we want with an unlocked bootloader. Personally, I feel they should support the rooting community and be able to reinstall the operating system when we mess up, similar to how we can reinstall windows on a computer. They can even charge $50 for the service and be able to do it in-store from a computer. Not only could they make more money, they wouldn't have to replace as many devices.
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
I would have to say that this is the reason there will most likely never be an unlocked phone sold again for VZW. By doing this you are making everyone look bad! You break, void warranty, then you should have to buy another one. If you don't like my statement don't try something you apparently have no knowledge to do.
Relax guys don't jack the thread for people that need the info
Sent From My Rooted 3D
i hada bricked phone i installed ics 235 and tryed to reflash it after data failed from safestrap . first i used a script it failed bad to reflash stuck in fastflash. so i found house of bionic(hob) of course cell battery was dead before i found it. crap i found online u can stick usb cable after cuttinfg it open and use red(pos)+ n black(neg)- wires to battery sandwhich it in phone . and it work 15min later battery ok used hob to reflash 235 used update 235 on sd card bang its alive.
....this order is my back aka new rsd flash ....no worryes