I've been trying to do the OTA update and can't. I've uninstalled recovery, uninstalled safestrap, updated my SU, unfroze all apps, and downloaded voodoo. Well after I think 7 attempts of this I decided to switch methods and do it through fastboot. Well I can't get fastboot to actually stay open on my computer to accomplish this. I have tried to figure that problem out too no help there. I'm assuming I deleted something before I froze the apps that isn't allowing me to do the update. Is there any solution to all this? Especially getting fastboot to work. Also in safestrap the first time I flashed something to my safe system it worked fine. After that regardless of what I did I could never get another rom to work. Everything else just sent it into a black screen forever.
What are you using to try to fastboot? RSDlite or jsnweitzel's Droid 4 tool?
Droid 4 - AOKP FLATLINER-KRUSH
Rsdlite
Sent from my DROID4 using xda app-developers app
Wolverinepur said:
Rsdlite
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
I would try using the Droid 4 Utility. I successfully fastbooted GB a while back using it. Also, make sure you have the latest moto drivers installed.
Droid 4 - AOKP FLATLINER-KRUSH
Yeah I just did that. It worked took a couple minutes but I'm all updated now.
Sent from my DROID4
Related
Hey guys I haven't updated my.phone to 902 yet because of fact I accidentally deleted my stock 901 backup meaning I'll have to flash to update...my problem is last time I tried flashing, it alway it always failed, but it always got to different percentages everytime
Is there a total noob fail proof way of flashing so I don't brick?
Sent from my DROID BIONIC using xda premium
Notorious93 said:
Hey guys I haven't updated my.phone to 902 yet because of fact I accidentally deleted my stock 901 backup meaning I'll have to flash to update...my problem is last time I tried flashing, it alway it always failed, but it always got to different percentages everytime
Is there a total noob fail proof way of flashing so I don't brick?
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Flashing through CWR or RSDlite? I did it with RSDlite (this wipes everything) and it failed until I got RSDlite 5.6, then it worked great.
RSDlite but mines v5.5
Sent from my DROID BIONIC using xda premium
Notorious93 said:
RSDlite but mines v5.5
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Go grab 5.6 bro. And make sure you're using the right FXZ.
And there's definitely no failsafe to flashing. All I can say is plug the usb into a back usb port as front ones aren't as reliable. If it gets disconnected even for a second during the flash, you could have a very expensive paperweight... permanently
R3l3as3DRoot and For3v3r root can take you back to stock 886.
Sent from my DROID BIONIC using XDA
Ok soooo ive uninstalled safestrap and back on stock recovery and stock ics rooted. What else do i need to do to recieve ota when its pushed out?
Sent from my DROID4 using xda app-developers app
rruleford said:
Ok soooo ive uninstalled safestrap and back on stock recovery and stock ics rooted. What else do i need to do to recieve ota when its pushed out?
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
If it's like the last OTA to ICS, you're probably going to have to flash the ICS fastboot files before the new OTA will take. The problem before was safestrap changed something, somewhere (logwrapper maybe?), that did not get changed back after uninstalling the safestrap recovery and app. MAYBE this has been changed/fixed in the new versions of safestrap? Pretty sure we were on version 2.x at the time. You can always try without fastbooting and see what happens. Won't hurt anything. If you do need to fastboot, use jsnweitzel's utility. It has an option to fastboot without wiping data. That's what I'm planning on doing. It should still fix whatever safestrap changed.
Sent from my Droid 4 - LiquidSmooth
kwyrt said:
If it's like the last OTA to ICS, you're probably going to have to flash the ICS fastboot files before the new OTA will take. The problem before was safestrap changed something, somewhere (logwrapper maybe?), that did not get changed back after uninstalling the safestrap recovery and app. MAYBE this has been changed/fixed in the new versions of safestrap? Pretty sure we were on version 2.x at the time. You can always try without fastbooting and see what happens. Won't hurt anything. If you do need to fastboot, use jsnweitzel's utility. It has an option to fastboot without wiping data. That's what I'm planning on doing. It should still fix whatever safestrap changed.
Sent from my Droid 4 - LiquidSmooth
Click to expand...
Click to collapse
In doing that it froze on step 3 of 17 mbmloader. Over night. When disconnected and tried again the battery was to dead. Plugged into wall charger now. Should i try again when its fully charged??
Sent from my DROID4 using xda app-developers app
rruleford said:
In doing that it froze on step 3 of 17 mbmloader. Over night. When disconnected and tried again the battery was to dead. Plugged into wall charger now. Should i try again when its fully charged??
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Yes. Never try to flash a fastboot or sbf file without making sure you have PLENTY of charge. Same goes for backing up and ROM flashing. You never want your phone to die in the middle of a flash.
Sent from my Droid 4 - LiquidSmooth
I think the most important thing to do is grab the update file and post it on Mediafire or similar so that the rest of us can have it
Hi guys,
I installed JB on my droid 4. It was running the stock ICS from Motorola. I used this : http://forum.xda-developers.com/showthread.php?t=2199741
I installed it by wiping the normal slot and put the zip file on the first rom slot.
I was able to boot on it without any problems, and I unistalled some of the stock apps (such as Verizon stuff, Motorola... I don't quite remember all the names). Since this moment, I didn't reboot my phone and it was fine.
But today I went out of battery, and now my phone wont boot ! I have the "Dual Core Technology", the Safetrap screen, and then blackscreen. Even the Motorola recovery wont work. And the phone doesn't seem to charge for whatever reason.
Is there a way to make my phone boot ? I was thinking about reinstalling ICS and make the update OTA to JB, but since I don't have energy on my phone I don't have time to do this...
Help me !
Thank you.
I'm sure you could just use
http://forum.xda-developers.com/showthread.php?t=2207384
And go straight to jb ... But idk just a thought....
Sent from my XT894 using xda app-developers app
dbreezy187 said:
I'm sure you could just use
http://forum.xda-developers.com/showthread.php?t=2207384
And go straight to jb ... But idk just a thought....
Sent from my XT894 using xda app-developers app
Click to expand...
Click to collapse
The problem is that my phone wont charge at all ! I can let it plugged for hours it doesn't work.
you will need a tbh programming adapter, to by pass battery
so you can flash xml restore file with rsd lite or or droid 4 utility
links in my list
sd_shadow's [Collection] of Links for Droid 4
Sent from my Clear using xda premium
You could try to make one if you can't buy one...
http://forum.xda-developers.com/showthread.php?t=1077414 never tried to make or use it myself... I did make an otg cable mentioned in the post... Worked fine I'm sure this would to...
Sent from my XT894 using xda app-developers app
Well thank you for your answers, I have to buy this cable so...
while trying to get a recovery to work with no avail, i wiped cache and did a factory reset and now i am in a boot loop. wish i could remove the freaking battery. just got my phone today and the first thing i did was updated to sense 4.3. I then unlocked the bootloader successfully. I started having problems with flashing a recovery even though the bootloader said unlocked and tampered. twrp would not boot, but i got cwm to boot. the problem on cwm was i didnt have access to all the folders like the downloads folder that had the su zip. I did have avast already installed while i was trying to root(going to activate antitheft once rooted) i thought avast might be the problem so i uninstalled went back into recovery wiped cache and did a factory reset hoping cwm would access the folder i need nope. so i was calling it a night and booted up the phone and now it is STUCK. It was easier rooting my evo 3d with brick method. PLEASE HELP ASAP
Did the instructions I sent end up working?
Sent from my HTCONE using XDA Premium 4 mobile app
plegrand said:
Did the instructions I sent end up working?
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
adb wont work on either computer i did some more research and it looks like i have to get the stock RUU
none of the recoveries will mount to anything but thank you for your help hopefully the RUU works
There is no RUU for 4.3 yet.
Sent from my HTCONE using xda app-developers app
Konfuzion said:
There is no RUU for 4.3 yet.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
and i just found that out. i just have perfect timing
how long does it usually take for someone to come out with the RUU, because i dont have a phone until it does
twistedamnion said:
and i just found that out. i just have perfect timing
how long does it usually take for someone to come out with the RUU, because i dont have a phone until it does
Click to expand...
Click to collapse
See if this will work for you.
http://forum.xda-developers.com/showthread.php?p=44243635
My AT&T moto X was rooted via RockMyMoto, but I decided I didn't need root, so I allowed my device to update to 4.4. After it powered off to install the update, it immediately booted back up. And now after about 30 seconds or so after it boots up, the phone turns off and repeats the process. Any suggestions? It is a locked boot loader At&t Moto X.
Thanks
Sent from my Nexus 7 using xda app-developers app
And my phone was previously on 4.2
Sent from my Nexus 7 using xda app-developers app
Nckrk123 said:
My AT&T moto X was rooted via RockMyMoto, but I decided I didn't need root, so I allowed my device to update to 4.4. After it powered off to install the update, it immediately booted back up. And now after about 30 seconds or so after it boots up, the phone turns off and repeats the process. Any suggestions? It is a locked boot loader At&t Moto X.
Thanks
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You can not flash the ota while having any form of a hijacked or custom recovery, you need a 100 % stock rom with the stock recovery. This has been talked about several 100 times already not being or trying to be a prick but really getting sick of reposted and duplicate threads . theres a search function , please use it
Sent on my Moto X
Thanks for the reply. I do understand this concept, its just that my device symptoms didn't seem to match anyone else's. I appreciate it.
Sent from my Nexus 7 using xda app-developers app
Nckrk123 said:
Thanks for the reply. I do understand this concept, its just that my device symptoms didn't seem to match anyone else's. I appreciate it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes it does, the ota is found in the cache folder, so you need to delete it or move it, you can delete it with fastboot erase cache or you can try erasing cache in recovery
Sent on my Moto X
flashallthetime said:
Yes it does, the ota is found in the cache folder, so you need to delete it or move it, you can delete it with fastboot erase cache or you can try erasing cache in recovery
Sent on my Moto X
Click to expand...
Click to collapse
Thank you.
Sent from my Nexus 7 using xda app-developers app