My son rooted my bionic, installed Safestrap and Eclipse launcher. The phone was working great. I changed phones and wanted to give the Bionic to a friend but wanted to wipe it clean before doing so. I decided to do a factory reset from the system settings. (I've done this before with no problem but that was before the phone was rooted.) Now when I start up the phone, all I get is the screen that says SAFESTRAP: DISABLED. Starting in 10 seconds. Then I get the red circle with the white M but nothing happens. It just cycles between the red circle and the safestrap disabled screen. I've messed around with the menu on the safestrap disabled screen but can't figure out how to get the phone started again. I don't know what version of anything I had because I can't access settings. I've spent hours searching the forums and have tried various unbrick methods with RSD Lite but nothing has worked. I honestly don't know what I'm doing and am unfamiliar with some of the lingo. Can anyone point me in the right direction and give me step by step instructions on how to restore the phone back to factory settings. Thanks in advance!
It sounds like your son installed eclipse which is a custom ROM on slot 1. The safestrap menu once opened under boot options has a button that says stock ROM. Hit that and then hit activate and then boot. You will then be back on your stock ROM. It sounds like you erased the custom one when you factory reset which is why it won't boot in slot 1, its BC there's nothing there. Once you get back on your stock ROM just uninstall the superuser app, and as far as most people would know it would be just as before. No need to rsd lite back to completely original unless you are giving it back to the carrier. If you still want to do that I would need to know specifics about what android version you are on etc to further assist you. However I recommend just switching to stock and uninstalling superuser and safe strap.
Sent from my XT875 using xda premium
DanRyan85 said:
It sounds like your son installed eclipse which is a custom ROM on slot 1. The safestrap menu once opened under boot options has a button that says stock ROM. Hit that and then hit activate and then boot. You will then be back on your stock ROM. It sounds like you erased the custom one when you factory reset which is why it won't boot in slot 1, its BC there's nothing there. Once you get back on your stock ROM just uninstall the superuser app, and as far as most people would know it would be just as before. No need to rsd lite back to completely original unless you are giving it back to the carrier. If you still want to do that I would need to know specifics about what android version you are on etc to further assist you. However I recommend just switching to stock and uninstalling superuser and safe strap.
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
Thanks for the quick reply.
When I go into Stock ROM from the Boot Options menu, it tells me it's Currently Active. If that's the case, how do I reboot the phone so I can get to the point where I can uninstall superuser and safe strap? Thanks.
If its already active and you have already tried rebooting then we may have a more serious problem. If you haven't hit reboot system then try that. If that doesn't work and year you've already done a factory data reset then I would say hit the restore button and see if your son made a backup. If there isn't one there then I would say you will have no choice but to learn to use RSd lite.
Sent from my XT875 using xda premium
That's because it flashed the stock boot image, the rooted settings stayed. You need to flash a diffrent boot image unroot then do factory reset. First time you did it you didn't do factory reset! Next time just reformat your sd card and you'll be fine! Good luck !
Sent from my HTC6435LVW using xda app-developers app
DanRyan85 said:
If its already active and you have already tried rebooting then we may have a more serious problem. If you haven't hit reboot system then try that. If that doesn't work and year you've already done a factory data reset then I would say hit the restore button and see if your son made a backup. If there isn't one there then I would say you will have no choice but to learn to use RSd lite.
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
I tried rebooting the system through Safestrap menu. It rebooted back to the SAFESTRAP: DISABLED screen.
I found the backup file, hit restore and it said restore was successful. However, I'm still stuck at the SAFESTRAP: DISABLED screen. I did more research on the internet and this is what I did with RSd lite based on a youtube video I found on how to restore the bionic:
I downloaded the motorola drivers, file name: Motorola_End_User_Driver_Installation_5.9.0_32bit.msi
I downloaded RSd lite 5.7 (also tried RSd lite 6.4.1)
I downloaded cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip
I tried installing the motorola drivers but got the error message that the drivers couldn't load successfully because a newer version was installed. (I searched the internet for a later version of the motorola drivers to see what version I might have but couldn't find a version newer than 5.9.0).
So I moved to RSd light. I located the cdma_targa zip file, hit decompress only. Once done I hit Start and there are 24 steps. I get a fail at step 5 with the message: Failed flashing process. 5/24 oem fb_mode_set -> Phone returned FAIL. I tried with RSd lite 5.7 as well as 6.4.1 and it always failed at step 5. Not sure what to try next or why this is so difficult. The YouTube video seemed so straghtforward. Thanks.
Okay, just breathe. This is not unfixable but it is probably going to require more than a little patience and some research. There is a wealth of knowledge in the forums here at xda and the answer is almost certainly there there to find. Once you open the forums use the search all forums tab to search key words like you error message. I found this: http://forum.xda-developers.com/showthread.php?t=2242075
Like the member who chimed in on our convo said the answer seems to be with the boot image. However I've never had this specific problem before. So I'll look a bit later and check back in. Maybe another member will weigh in and maybe you'll find a piece of gold in the forum!
Sent from my XT875 using xda premium
You need to edit the .xml file and remove all of the getvar lines and then it will flash properly in RSD Lite.
You can also use fastboot to flash the partitions separately but given your level of understanding, I would recommend using RSD Lite with the edited .xml and avoiding the need for command line and multiple operations.
The full xml.zip will restore your device completely and you can start fresh and re root and try SafeStrap again.
Related
i rooted my droid 3 and changed the battery icon and notification panel backround installed mavrom it was giving me lots of errors so i did a factory reset i think it failed now the phone starts but if i open any apps except the phone app or the stock messaging app the phone restarts and any apps i have are gone but the changes to the notification bar are still there i have tried every recovery method i can find and nothing can fix it can nayone help?
Did you do a wipe of data ?
Sent from my XT862 using Tapatalk
If u have tried everything u can think of the last step is .Sbf
Sent from my DROID3 using XDA App
Here is a link to a thread that will get you back to stock:
http://forum.xda-developers.com/showthread.php?t=1255198
Sent from my XT862 using XDA App
did a whipe and what was on the link dident fix it when i use rsd lite it gets to 3/18 and fails
What recovery are you using?
stock recovery cant get any other ones to work
Try this. Follow the directions in the OP. It'll take about 5 mins to get back to a box stock D3.
http://forum.xda-developers.com/showthread.php?t=1339816
went to the link downloaded it, flashed it everything went good then phone restarts and everything is back to stock except the things i changed with rom manager and still resets everytime my phone turns off
htimes said:
went to the link downloaded it, flashed it everything went good then phone restarts and everything is back to stock except the things i changed with rom manager and still resets everytime my phone turns off
Click to expand...
Click to collapse
Then ROM Manager is clearly the issue. That link gets you to box stock software. I'm not a fan of RM because I feel that unless 110% understood, it can cause way more headaches than it fixes. What do you use it for? What changes did you make after flashing to stock?
used rom manager to change battery icon 3g icon signal icon and the notification bar backround
I don't think that MavROM is compatible with Rom Manager tweaks. I believe that they only work with CM based ROMs. Try reflashing to stock, rerooting, and reROMing it. Don't make the changes and see if the issues persist.
i tried reflashing to stock like 10 times and it never fully goes back to stock
How about going to cwm through odin and deleting your catch data and your delv catch. I had the same issue when reverting back to stock ( it wasnt fully there) but when i erased all the data and delv catch it reverted to the stock rom properly. Just a thought
Sent from my GT-I5500M using xda premium
i cant get into cwm not sure how to do it
htimes said:
i cant get into cwm not sure how to do it
Click to expand...
Click to collapse
Well, the previous is strange, because I've used that to recover from all different causes of bricks and bootloops and reboots and etc. All took me back to box stock software...
Anyways, I would flash back to stock-ish with it, re-root, install CWM, boot into recovery, and then wipe /system /data /cache /dalvik cache.
Using X + Power then VOL Up + Down, you can get into stock recovery and wipe data and cache. This puzzles me though, because that quick SBF wipes data, system, and cache.
Just for my curiosity, what ISN'T stock after the quick unbrick method?
htimes said:
i tried reflashing to stock like 10 times and it never fully goes back to stock
Click to expand...
Click to collapse
Oops, bumped Thanks trying to quote this. When the DOS-looking window prompts you to press any key to exit, and I'm assuming you do, do you let the phone go through it's process where the yellow bar inches across the screen and completes the reset?
tried odin said it isent compatible with my device
htimes said:
tried odin said it isent compatible with my device
Click to expand...
Click to collapse
Odin is for samsung devices
Sent from my XT860 using xda premium
redsox985 said:
Well, the previous is strange, because I've used that to recover from all different causes of bricks and bootloops and reboots and etc. All took me back to box stock software...
Anyways, I would flash back to stock-ish with it, re-root, install CWM, boot into recovery, and then wipe /system /data /cache /dalvik cache.
Using X + Power then VOL Up + Down, you can get into stock recovery and wipe data and cache. This puzzles me though, because that quick SBF wipes data, system, and cache.
Just for my curiosity, what ISN'T stock after the quick unbrick method?
Oops, bumped Thanks trying to quote this. When the DOS-looking window prompts you to press any key to exit, and I'm assuming you do, do you let the phone go through it's process where the yellow bar inches across the screen and completes the reset?
Click to expand...
Click to collapse
the phone doesent go through the yellow bar process it just restarts to the first part of recovery menu all that is on my screen is the triangle and droid
htimes said:
the phone doesent go through the yellow bar process it just restarts to the first part of recovery menu all that is on my screen is the triangle and droid
Click to expand...
Click to collapse
Are you sure you have the latest drivers installed? Head over to that thread one more time, re-download the quick unbrick, boot up with M + Power, select AP Fastboot, open the shortcut for "CLICK HERE - Something something something", allow it to go through it's 20 or so lines of actions, and when it says to press any key to exit, do so. Now just let the phone sit there while still plugged in (IIRC, this is what I did last time). If this all fails to return you to stock settings... 1. I'll be surprised 2. I'll nand backup mine and make a video for you of quick unbricking mine and everything it does.
If it does work, please don't change things in ROM Manager, IIRC, those tweaks are only for CM based ROMs, and not Mav.
I need some help please. I seem to be in a pickle, though I’m not bricked. (At least, not yet.) So I rooted my phone last night, using [GUIDE][NOOB]Step-By-Step Instructions for New Stock Bionic Owners. Everything went great, and I got root. I followed the guide to get the .901 update, which went fine. Tried the ROM suggested, and liked it. Thought I would try Eclipse v2.1. I installed it, but I like Visual Voicemail, so I decided to use my Nandroid that I did right after root and revert back. Here is where problems started.
After the restore, it wouldn’t boot. Passed the Moto Dual Core logo and hung up. Allowed 10 minutes and after nothing, I flashed back to the backup I made after installing Eclipse. It booted fine. So I decided to go back to stock rom, debloat it how I like it and just run the debloated stock. Here is where problems started. I can’t find a flashable copy of the stock. Just a couple of guides on using RSD Lite. This is for Bricked Bionic’s, but I decided to try it, since one of the guides said it works to get back to OTA.
Downloaded the RSD Lite and the full system file to flash. I put my phone into the mode to flash (Power + Volume Down), unpacked the file with RSD Lite and tried to flash. Got an error.
Failed flashing process. Failed flashing process. 1/15 flash cdt.bin"cdt.bin"-> Phone returned FAIL.; phone connected.
Now, when I reboot my phone, it goes back to the Fasboot Flash Mode screen saing (Failed). I can boot into recover (Volume Up + Volume Down + Power) and do a Normal Boot, and it boots fine.
I tried a Factory Reset, and it just reset’s on Eclipse v2.1.
I want to simply get back to stock. Rooted or unrooted, I don’t care. I’ll reroot if I need to.
I also tried to download the STOCK Deodexed files. The links are dead. Figured if I went back to one of those stock images, I could unroot and see if everything was ok.
Suggestions?
Hmm..I think your mistake was in safeboot when you tried to go back to original back up you were suppose to toggle safe system so that it would be disabled. From there you would've been able to restore your original system and boot up just fine. It was mentioned in the guide through some posts.
Sent from my DROID BIONIC using Tapatalk
ms0chez said:
Hmm..I think your mistake was in safeboot when you tried to go back to original back up you were suppose to toggle safe system so that it would be disabled. From there you would've been able to restore your original system and boot up just fine. It was mentioned in the guide through some posts.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
So I need to turn Safe Mode off in SafeStrap and flash? I had thought about that, but I was worried about totally bricking the phone. I'm pulling SafeBoot now, and will try the flash.
EDIT...
SafeMode is off, and rebooted. I'm back to .875 Stock Rooted. So far, so good.
I can either flash from here (haven't tried yet) or stay here. When I boot, I'm still booting into Fastbook with (Flash Failure). Any way to get that off, other than flashing back to stock and locked through RSD Lite?
Your mistake was trying to restore from the un safe system. You can toggle safe system and you'll be ok. Or, reinstall a ROM to your safe system.
To clarify: don't flash a ROM with safe system disabled. toggle back to safe mode, and then pickup my directions from the format /system step. You can try another ROM no problem then.
I bet you can find the visual voicemail APK and add it whichever ROM. Copy paste into system/app directory.
Thanks. I'm used to flashing with the Thunderbolt and the XOOM. Not used to safestrap, just normal CWM.
Any idea how to stop the phone from booting into Fastboot? Having to do it the long way still. I'd be happy staying this way, if I can get that resolved.
Actually the problem was you tried to restore to a backup of a pre .901 system which has different radios which flashing doesn't like.
As for the flash failure, get the fxz files and put them in a folder with adb and fastboot. Then run this command in a prompt:
fastboot flash device_tree.bin
When you get a flash failure you just need to flash something to fix it; flashing device_tree.bin won't affect anything.
Its one solid file with a weird extension. Is there a way to unpack it? I am out right now and don't know the extension by heart.
Its a zip, just extract it
Sent from my DROID BIONIC using XDA App
Now, I'm scratching my head. (Again) I've worked with ADB with my Xoom, so I'm not a noob at that part. ADB doesn't see my phone. My computer does, and the phone know's it's plugged in. However when I try to flash the file, it can't find the device. I checked "adb devices" and it's not on the list.
So I decided to go ahead and flash completely back to stock with RSD Lite. Still get's the same error message. (I did check the MD5 SUM on the file. It's correct.) Safe Mode is off in Safestrap. Here is what the Fastboot screen looks like on my phone.
AP Fastboot Flash Mode (S)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
Since I've not seen the Fastboot screen on this phone until this started, I don't know if the (S) has meaning. Like, it thinks the phone's still in SafeMode?
I noticed one of the options in safestrap is to disable safestrap. Thought about trying that, but.... Unsure.
Ok so I have an Atrix HD that I rooted then went to install paranoid android on here. I made the mistake to try and install using Factory Recovery. So it threw an error in Fastboot. I used Myth Tools to get it back to stock. Then used Myth to install CWM Root it and unlock bootloader. Then went to install paranoid android again... Everything seemed to be going well but it just stayed on the Glowing X for 10-15 minutes. Knew something was up with it not loading into OS by then. So I tried to reinstall it again. No luck. Tried to use Myth Tools to go back to factory. Would just stay at Dual Core logo and do nothing. I went back in and installed CWM and tried to install Pacman Rom and it just stays at Pac is loading.
Fastboot still shows Bootloader as unlocked as it should, but is this the reason why Myth could not get me back to factory? I just want to get it back to factory at this point and worry about Rooting and installing Rom later. I have been searching and trying anything I can find on here, and droid razr forum. As well as various other sites and artices i find from google. I am at a lose. Have I bricked it enough to not come back from this or am I just missing something simple? I am looking for insight or help to get me in the right direction. I am on day 3 now off trying to get it running again.
I have tried in CWM formating Cache and re mounting it in Advance, Also have tried formating system, cache, davik cache... I did receive the can not mount errors but having formatting cache and remounting i did not get the error again.
Just take it a step at a time. Get it booted into stock first.
Sent from my MB886 using xda premium
darknessrise1234 said:
Just take it a step at a time. Get it booted into stock first.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
but where to begin? Trying to get it back to stock is not working even though Myth Tools. It states it finished I do not get any errors through Fastboot yet it stays on Dual Core never moves as if it is bricked.
DeVoe41 said:
but where to begin? Trying to get it back to stock is not working even though Myth Tools. It states it finished I do not get any errors through Fastboot yet it stays on Dual Core never moves as if it is bricked.
Click to expand...
Click to collapse
read this
http://forum.xda-developers.com/showthread.php?t=2226527
Make sure you have the adb drivers installed on your computer and I've noticed this phone is weird about chargers find one that works for data too. U will know cause if you have adb installed through myth tools and you reboot into fastboot mode then your computer will recognize it. Make sure the only thing in the firmware folder in myth tools is your .zip whatever stock att firmware you want. Then in myth tools install stock and make sure you type in the response 2 when it asks if you are in fastboot mode or normal. Fastboot is choice 2. I'm a flashaholic I've tried every rom in our development forum lol. I have bricked my AHD more times then anyone should this always worked for me. Try these things see if they help
Sent from my MB886 using xda app-developers app
Clean Flash
DeVoe41 said:
Ok so I have an Atrix HD that I rooted then went to install paranoid android on here. I made the mistake to try and install using Factory Recovery. So it threw an error in Fastboot. I used Myth Tools to get it back to stock. Then used Myth to install CWM Root it and unlock bootloader. Then went to install paranoid android again... Everything seemed to be going well but it just stayed on the Glowing X for 10-15 minutes. Knew something was up with it not loading into OS by then. So I tried to reinstall it again. No luck. Tried to use Myth Tools to go back to factory. Would just stay at Dual Core logo and do nothing. I went back in and installed CWM and tried to install Pacman Rom and it just stays at Pac is loading.
Fastboot still shows Bootloader as unlocked as it should, but is this the reason why Myth could not get me back to factory? I just want to get it back to factory at this point and worry about Rooting and installing Rom later. I have been searching and trying anything I can find on here, and droid razr forum. As well as various other sites and artices i find from google. I am at a lose. Have I bricked it enough to not come back from this or am I just missing something simple? I am looking for insight or help to get me in the right direction. I am on day 3 now off trying to get it running again.
I have tried in CWM formating Cache and re mounting it in Advance, Also have tried formating system, cache, davik cache... I did receive the can not mount errors but having formatting cache and remounting i did not get the error again.
Click to expand...
Click to collapse
I have a suspicion that for some odd reason, as Mythtools probably should have taken care of this, that there are some lingering files and caches that would cause any rom to fail upon install. I just posted something about this earlier today.
Read my post on this thread:
http://forum.xda-developers.com/showthread.php?t=2394238
PM me with any questions or problems and click the Thanks button if I helped.
I'm sorry I forgot to update I was able to get the phone working just had to do it through command prompt forcing you to file . The issue I had was using safestrap to install a ROM which somehow killed root access and the bootloader was not unlocked so and pretty much bricked the phone.
Sent from my MB886 using xda app-developers app
For recent custom roms, you must use a CWM with an unlocked bootloader.
I apologize first that I am completely confused after reading posts for hours trying to fix my problem. Second, I know enough to get myself into trouble & I've succeeded. I'd been running Icarus 183 on my previous Bionic for months, so after shutting the truck lid on it, I set out to install the same on my replacement. Not realizing that JB had been released is where my ^$&#& happened. Here's the order of what I did which has lead me to a phone that boots to AP mode when you turn it on, or to the menu when holding both volume keys and powering on. If I go thru the power keys and select normal boot, I get the red dot and the screen will stay backlit.... nothing else.
1] New replacement phone: I used the Virtual Machine program to root.... This worked perfectly.
2] Goomanager had reinstalled from my google account, but I don't think I had ever used it.
3] I had installed Icarus thru the safe strap (3.05, I think) on my old phone. I went ahead and installed this again (no problems so far)
4] I started to install Icarus thru safestrap again, but I didn't like partitioning, so I figured I would download and install a rom using GooMgr
5] I believe I chose a rom named "Carbon" from those roms GooMgr stated was compatible... When I ran GooMgr nothing appeared to happen, so I rebooted the phone thinking I would just go ahead and install Icarus using safestrap.
6] When I pressed the button to boot into safestrap, the Carbon rom I had started to load began to run.. (apparently GooMgr could not reboot due to having safestrap installed??)
7] Naturally, the installed failed, giving me the dead android symbol... I removed the battery to reboot, but only AP mode comes up.
8] I am still at this point, having tried RSD Lite 5.7, updated Motorola drivers, and have now tried as who knows how many fxz files to restore it..
9] RSD Lite continues to fail at step 5 , where the phone reports "FAIL"
All I want is the stock JB back, so I can be up an running again.
WOW! Sorry for the problems. I wish I can help but I'm not too familiar with returning your phone back to stock. I do have one piece of advice. Go to YouTube and look up Tomsgt123. His website is rootjunky.com. Really great guy. He responds very quickly. Good luck.
Sent from my XT875 using xda app-developers app
If fxz fails why not try recovery mode flash using sd card?
Just follow the directions for 'manual JB' flash.
http://www.android.gs/update-motorola-droid-bionic-official-android-4-1-2-jelly-bean/
[/COLOR]Use a more recent version of RSD Lite for the latest JB FXZ files. 6.1.5 is the current RSD Lite release version.
https://db.tt/Tya2balw
You don't need to install the MTK patch included with this release.
UPDATE.. Since I need this phone for my business, I couldn't take the extra time this week to sort it out... Ended up going into a Verizon store & told them what I did (honestly)... They were surprised I was telling the truth & made arrangements for a warranty exchange.. Got the new phone today and up & running on stock rom... I'll be more careful and thanks for the advice above.. I'll make sure I am using the correct software next time.
Thanks for the responses.
hello, i recently bought used droid 4, found it to be with some leftover data (sms, and such) so first thing i did was a factory reset only to
find it after a while in extact same state. weird thing is that when i factory reset it after removing some apps or changing anything at all it acts
as if i restored some backup instead of wiping device. it spams me with errors every few seconds too which is quite troublesome to say the least.
i searched the internet for an answer (still looking) to this problem but so far got nothing. i mean there are lots of ppl with similiar issue
but no real answer anywhere i looked. i thought maybe flashing some stock rom (dont wanna try anything custom yet since i got lapdock
too and havent checked if webtop works with custom roms yet). is it the right direction in my case or is there some simplier answer to my problem?
thanks in advance
update: cant root it, cant install official update through rsdlite, cant update through other unofficial ways,
it acts as if everything went fine and each time im back to square 1. it aint my first or second journey with rooting,
changing rom but im not really sure what else can i do. also rsdlite cant detect any information about device (imei,
os version, flex drm boot etc are all filled with N/A
install from sdcard also failed - signature verification failed. keeps gettin better. downloading another rom from
official moto website... not expecting anything though
wyklocnik said:
hello, i recently bought used droid 4, found it to be with some leftover data (sms, and such) so first thing i did was a factory reset only to
find it after a while in extact same state. weird thing is that when i factory reset it after removing some apps or changing anything at all it acts
as if i restored some backup instead of wiping device. it spams me with errors every few seconds too which is quite troublesome to say the least.
i searched the internet for an answer (still looking) to this problem but so far got nothing. i mean there are lots of ppl with similiar issue
but no real answer anywhere i looked. i thought maybe flashing some stock rom (dont wanna try anything custom yet since i got lapdock
too and havent checked if webtop works with custom roms yet). is it the right direction in my case or is there some simplier answer to my problem?
thanks in advance
Click to expand...
Click to collapse
uncheck restore data Hard Reset - DROID 4 by MOTOROLA - Verizon Wireless Support
update: cant root it, cant install official update through rsdlite,
Click to expand...
Click to collapse
updates.zips are not installed with rsdlite, XML/firmware is install with rsd lite, but adroid version can not be downgraded
cant update through other unofficial ways,
it acts as if everything went fine and each time im back to square 1. it aint my first or second journey with rooting,
changing rom but im not really sure what else can i do. also rsdlite cant detect any information about device (imei,
os version, flex drm boot etc are all filled with N/A
install from sdcard also failed - signature verification failed. keeps gettin better. downloading another rom from
official moto website... not expecting anything though
Click to expand...
Click to collapse
what official site? use files from my page How to Use RSD Lite to flash a .XML Stock Rom (firmware)
thanks for taking interest
tried factory reset with options You mentioned unchecked, same thing as before.
i did use xml with rsdlite and zip through built in recovery.
tried to find this page i downloaded files but theres too much in yesterdays history, trying those from Your link now.
also tried to update rom ota, but of course theres an error. oh my droid runs 4.0.4, i havent mentioned it before.
also, found in the net schematics for factory cable, was thinking if its worth a shot this way:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable-4.html
Factory cable only allows you to power device with low battery/no battery
Sent from my Amazon OtterX using Tapatalk
---------- Post added at 10:33 AM ---------- Previous post was at 10:31 AM ----------
Update zips only update specific system versions, you have to use correct one, and must be complete stock.
Sent from my Amazon OtterX using Tapatalk
from what i read in this post about factory cable it says it boots phone different way than normal thats why i thought maybe
itll be able to successfully update with it. also after every reset of this droid its not a simple matter of apps coming back thru wifi.
wifi is disabled and theyre there right from the start. i can remove some widgets or apps from home screen, i can delete texts,
and after reset theyre all back where they were. its as if every change i made havent been saved. i dont even have to reset phone,
i just need to reboot it to have it all back
phone needs to be in AP Fastboot mode when flashing with rsd lite.
verify md5 checksum for xml file before flashing.
yes, it was in ap fatboot mode, didnt verify the md5 tho.
more importantly, file i downloaded from site You linked passed verification! guess what i found wasnt official updates after all...
i hope this works
wyklocnik said:
from what i read in this post about factory cable it says it boots phone different way than normal thats why i thought maybe
Click to expand...
Click to collapse
Factory/Fastboot cable only uses the alt power (4) pin to power device, there are several pre-made ones
itll be able to successfully update with it. also after every reset of this droid its not a simple matter of apps coming back thru wifi.
wifi is disabled and theyre there right from the start. i can remove some widgets or apps from home screen, i can delete texts,
and after reset theyre all back where they were. its as if every change i made havent been saved. i dont even have to reset phone,
i just need to reboot it to have it all back
Click to expand...
Click to collapse
try reformatting internal sd card, before wiping
---------- Post added at 10:58 AM ---------- Previous post was at 10:53 AM ----------
wyklocnik said:
yes, it was in ap fatboot mode, didnt verify the md5 tho.
more importantly, file i downloaded from site You linked passed verification! guess what i found wasnt official updates after all...
i hope this works
Click to expand...
Click to collapse
there are no official moto download sites, all moto firmware is pulled by people with special access, and reuploaded
try reformatting internal sd card, before wiping
Click to expand...
Click to collapse
is it any different than checking "erase internal storage" when reseting phone?
anyways did it but atm have to recharge battery before trying to wipe it again.
also rom was succesfully updated thru recovery with no errors and after reboot im... back to square 1...
wyklocnik said:
is it any different than checking "erase internal storage" when reseting phone?
Click to expand...
Click to collapse
formatting is different than wiping data, in menu>settings>storage>unmount>format
anyways did it but atm have to recharge battery before trying to wipe it again.
also rom was succesfully updated thru recovery with no errors and after reboot im... back to square 1...
Click to expand...
Click to collapse
did system version change?
same story after formating internal memory.
no changes whatsoever. same homescreen, same widgets/apps present. same system version.
and of course new error every 5 seconds. guess the phone is messed up good.
talk about luck. its second droid 4 i bought. first i bought over a month ago on auction site, it was new. i paid, guy never sent it.
now this one. its like a curse
formatting internal won't wipe, user data, but will wipe backup data.
tried xml with rsdlite now.
after first reboot its supposed to go into the recovery mode right?
it went back in to ap fastboot... and after rsd transfered all the files then it went to bootloader... and now program says reboot is in process while phone sits in recovery mode...
wyklocnik said:
tried xml with rsdlite now.
after first reboot its supposed to go into the recovery mode right?
Click to expand...
Click to collapse
it happens sometimes
it went back in to ap fastboot... and after rsd transfered all the files then it went to bootloader... and now program says reboot is in process while phone sits in recovery mode...
Click to expand...
Click to collapse
select wipe data, then select reboot
done, nothing changed.
also, when rsd works it acts as if it doesnt wait for the phone with operations.
it writes reboot, phone starts to reboot, and long time before it boots back either in ap fastboot mode or into recovery
rsd says its already transfering files, it says reboot again (before phone even gets into fastboot or recovery after 1st reboot) and so on.
wyklocnik said:
done, nothing changed.
also, when rsd works it acts as if it doesnt wait for the phone with operations.
it writes reboot, phone starts to reboot, and long time before it boots back either in ap fastboot mode or into recovery
rsd says its already transfering files, it says reboot again (before phone even gets into fastboot or recovery after 1st reboot) and so on.
Click to expand...
Click to collapse
which fastboot version? 0A.74 , 0A.77?
which xml file?
0A.74
cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml
looks like you have a failure to write data, don't think there is a fix.
could try my Unbrick Moto device with moto-fastboot.exe
but unlikely that it will work