Error when initiate backup in CWR - Motorola Droid Bionic

The error says something along the lines of "error preparing system image". Whatever it says I can't back up my current system. Any suggestions?
Sent from my DROID BIONIC using Tapatalk 2

Nero's said:
The error says something along the lines of "error preparing system image". Whatever it says I can't back up my current system. Any suggestions?
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
Do you have enough space on your SD Card?

linuxgator said:
Do you have enough space on your SD Card?
Click to expand...
Click to collapse
Over 13 Gs
Sent from my DROID BIONIC using Tapatalk 2

Nero's said:
Over 13 Gs
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
Hmm, maybe try reinstalling Bootstrap and trying again. Also, try wiping the dalvik cache. These are just kinda generic solutions, but I don't know of anything more concrete to try.

linuxgator said:
Hmm, maybe try reinstalling Bootstrap and trying again. Also, try wiping the dalvik cache. These are just kinda generic solutions, but I don't know of anything more concrete to try.
Click to expand...
Click to collapse
Preesh... From what I've read it a recovery issue. I tried un install re install. But I think I need a different version of bootstrap. Might give safe strap a try again.
Sent from my DROID BIONIC using Tapatalk 2

Related

[Q] SBF recovery = "passed" but bootloops [URGENT]

For unknown reasons, the SBF recovery in RSD lite 5.5 comes up with a "pass" result when the SBF itself actually fails. It runs like it worked, but on the final reboot, I get an endless bootloop.
Backstory:
I made a rom, flashed it, bootloop, go to SBF, SBF passes but bootloops.
*ps i've tried it 4 additional times and each time still bootloops even though it says "pass"
I've done this at least 4 times in the past 3 days trying to get my rom to flash. What the FUUUUUUUUUU*K is it doing this for now?
Wipe data/cache after you SBF.
Sent from my DROID3 using xda premium
kshen1 said:
Wipe data/cache after you SBF.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
I can't get into anything.
The SBF bootloops.
did you try a battery pull and booting into recovery
shane1 said:
did you try a battery pull and booting into recovery
Click to expand...
Click to collapse
battery pull over 20 times at least.
no more cwm, i sbf'd. everything is stock. 100% stock. but bootlooping.
Try to flash the chinese rom, see if it boot then flash back the verizon rom.
The Solutor said:
Try to flash the chinese rom, see if it boot then flash back the verizon rom.
Click to expand...
Click to collapse
What the f...No don't do this.
Did you download the correct SBF for your system version? I know there are both 959 and 890 SBFs out there.
Sent from my DROID3 using xda premium
You wont have CWM after doing the SBF but you can still boot into the stock moto recovery and wipe data/cache
kshen1 said:
What the f...No don't do this.
Click to expand...
Click to collapse
And why
The Solutor said:
And why
Click to expand...
Click to collapse
Different phone, different everything.
lordgodgeneral said:
You wont have CWM after doing the SBF but you can still boot into the stock moto recovery and wipe data/cache
Click to expand...
Click to collapse
I can still do that? I'll try that and give it a go when I get back home. I thought the stock recovery had no options though....
kshen1;18233443 said:
Did you download the correct SBF for your system version? I know there are both 959 and 890 SBFs out there.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Yep, been using the same one the whole time, 890.
Sent from my dad's DROIDX using XDA App
dpwhitty11 said:
Different phone, different /system.
Click to expand...
Click to collapse
And then ?
I suggested this way purposely, because the different organization will lead to a wiped phone.
The Solutor said:
And then ?
I suggested this way purposely, because the different organization will lead to a wiped phone.
Click to expand...
Click to collapse
Its a different model phone. It would be a brick, not a bootloop, if I did that.
Sent from my DROIDX using XDA App
The Solutor said:
And then ?
I suggested this way purposely, because the different organization will lead to a wiped phone.
Click to expand...
Click to collapse
Lmao...
Dpwhitty go into stock recovery after sbf and wipe data.
Sent from my DROID3 using xda premium
kshen1 said:
Lmao...
Dpwhitty go into stock recovery after sbf and wipe data.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
lol, that guy....
Kshen, I left my phone at home, i'll do that when I get back.
Sent from my DROIDX using XDA App
I go into recovery and I get the little android guy and that white triangle with the orange exclamation mark inside it. No options or menus in there.
dpwhitty11 said:
Its a different model phone. It would be a brick, not a bootloop, if I did that.
Click to expand...
Click to collapse
Is better to open the mouth having something useful to say, and not to spread urban legends.
(for the record I have the chinese rom installed on my phone, which is a verizon phone.)
Is a way better rom in many areas, but my purpose was not to suggest a different rom, but to solve a problem, with a safe solution, as I'm used to do in the last 30 years.
dpwhitty11 said:
I go into recovery and I get the little android guy and that white triangle with the orange exclamation mark inside it. No options or menus in there.
Click to expand...
Click to collapse
Press in both volume keys. That'll bring up some options. You'll see factory reset/wipe data there
Sent from my DROID3 using XDA App
erismaster said:
Press in both volume keys. That'll bring up some options. You'll see factory reset/wipe data there
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
That worked.
Thank you so much guys, thought I was a goner for a while.
The Solutor said:
Is better to open the mouth having something useful to say, and not to spread urban legends.
(for the record I have the chinese rom installed on my phone, which is a verizon phone.)
Is a way better rom in many areas, but my purpose was not to suggest a different rom, but to solve a problem, with a safe solution, as I'm used to do in the last 30 years.
Click to expand...
Click to collapse
Ok
Sent from my DROID3 using xda premium
dpwhitty11 said:
That worked.
Thank you so much guys, thought I was a goner for a while.
Click to expand...
Click to collapse
Yeah NP haha I knew wiping data would solve the issue
Sent from my DROID3 using xda premium

[Q] Bricked?

I was attempting to work through applying the .218 update to my droid 4. It was giving me a system validation error while when it was running in recovery. I found a thread that stated I needed to replace the apks and odex's as well as the build.prop. I didn't read it carefully enough as it said to replace *THE* problem ones. My validation error was on the build.prop file, I think.
In any case, I was using root explorer to copy *ALL* the files from a base zip file's app folder into the /system/app folder. Things were going along fine, until the phone app forced closed, then the phone rebooted.
Now I'm boot looping.
What can I do? I don't have any safe straps.
Can't access safestrap? Stock recovery? Adb services?
Sent from my DROID4 using Carrier Pigeons
The Magician Type 0 said:
Can't access safestrap? Stock recovery? Adb services?
Sent from my DROID4 using Carrier Pigeons
Click to expand...
Click to collapse
thanks for the reply...
I don't have safestrap installed on the device, and I've never used it. I don't think that's an option, unless you have something up your sleeve there
As for Stock recovery, I'd love to give it a try, but I don't know how that would work. I can't get to ADB because I can't boot the phone.
I *CAN* get into the bootloader. From there, I can get into recovery, AP Fastboot, BP SBF Flash BP boot... and others.
So, I'm hoping there's some kind of way to push to the device from one of the boot loader options. I've had a Droid 1, and a number of other android devices, but I've never gotten this far into a hole before.
again... thanks for whatever you got
It doesn't look good my friend, not without a SBF to flash. The only thing I can think of off the top of my head would be to try flashing the update again and cross your fingers that you got things in place before the bootloop. However I'm 99.9% sure that won't work. If I find anything else I'll let you now, but at this point you might be a sitting duck.
Sent from my DROID4 using Carrier Pigeons
The Magician Type 0 said:
It doesn't look good my friend, not without a SBF to flash. The only thing I can think of off the top of my head would be to try flashing the update again and cross your fingers that you got things in place before the bootloop. However I'm 99.9% sure that won't work. If I find anything else I'll let you now, but at this point you might be a sitting duck.
Sent from my DROID4 using Carrier Pigeons
Click to expand...
Click to collapse
I have the update on the SD Card, and nope, flashing it results in the same system validation error, and a bootloop.
thanks. Do you think that flashing the RAZR sbf's would get me a booting device? I only got the thing 14 days ago. Maybe I can exchange it
jbeazell said:
I have the update on the SD Card, and nope, flashing it results in the same system validation error, and a bootloop.
thanks. Do you think that flashing the RAZR sbf's would get me a booting device? I only got the thing 14 days ago. Maybe I can exchange it
Click to expand...
Click to collapse
If you're still in the 14 day return window I would try to return it. If it can't get past the bootloader than they won't know you rooted it. Just tell them you tried to do the update and it bootlooped. That's probably you're safest bet.
kwyrt said:
If you're still in the 14 day return window I would try to return it. If it can't get past the bootloader than they won't know you rooted it. Just tell them you tried to do the update and it bootlooped. That's probably you're safest bet.
Click to expand...
Click to collapse
I'm heading down there in a few minutes. Thanks for the help all ! I think I'm getting the razr maxx. My wife has one and the screen on that thing is incredible. I think it's worth losing the keyboard to get that screen... and the battery life. That part is also incredible.
again.. thanks.
BTW, you guys absolutely rock. You've helped me out of some serious holes with my OG Droid and other devices more often than I can count.
Sent from my DROID4 using Tapatalk 2
You can use bp tools to push over a clean system. I believe theres a tutorial somewhere that written for bionic. Just replace that with the droid 4 system. I would extract it from one of the stock roms available and push it thru bp tools.
Sent from my DROID4 using Tapatalk 2
Can you link that tutorial? I'm also trying to figure out how to use adb via stock recovery. Thanks!
Sent from my DROID4 using Carrier Pigeons
http://forum.xda-developers.com/showthread.php?t=1236465
Sent from my Galaxy Nexus using Tapatalk 2
Thanks!
Sent from my DROID4 using Carrier Pigeons
Let me know
Sent from my Galaxy Nexus using Tapatalk 2
It sounds like OP is going to exchange their phone, but could you really just replace the entire /system folder and have it work? (Nothing special with permissions, etc?)
If so, that is definitely something worth knowing...
Yes i believe so.
Sent from my DROID4 using Tapatalk 2

download-droid-4-jelly-bean-update-98-72-18

Yesterday, Verizon approved Jelly Bean for the DROID 4 as build 98.72.18, but as is typical, Motorola sent the first wave of updates out to members of their feedback network (soak testers) this morning. And since that happened, the file has been pulled and made available to everyone with the device.
We have instructions for you below, so if you do not feel like waiting for the update to be pushed to your device, feel free to jump below.
The official changelog can be found here. here
Instructions:
*These are the instructions from the RAZR HD update, but they should work for the DROID 4 as well.
*You have to be running the official Ice Cream Sandwich (Android 4.0.4) update of build 6.16.217. You also have to be completely stock.
1. Download the update file here: here
2. Drop that file on your SD card, not internal storage.
3. Turn phone off, and reboot into recovery.
*Hold both Volume Up and Down along with Power until you see the boot menu. Use Volume Down to hover over “Recovery.” Press Volume Up to select it.
*Once you see the Android and Exclamation point, press both Volume Up and Down at the same time.
4. Select “apply update from external storage.”
*Use Volume keys to highlight, Power button to select.
5. Then select the file you downloaded from above. It should already be on your SD card.
6. Watch as the update applies.
7. Once finished, choose the “reboot” option and enjoy!
DON'T FORGET TO SAY THANKS!
got this from droid-life
FYI, you will lose root if you do this without Voodoo unrooting first, as I just mistakenly did
rorytmeadows said:
FYI, you will lose root if you do this without Voodoo unrooting first, as I just mistakenly did
Click to expand...
Click to collapse
yes ots's will cause you to loose root
So do I need to De-root and remove safestrap before installing this, or can I just install and then root this?
bluri said:
So do I need to De-root and remove safestrap before installing this, or can I just install and then root this?
Click to expand...
Click to collapse
Safeboot and restore complete stock ICS. Don't worry about losing root. RAZR blade method is confirmed to work. Unless u have no access to PC then yes backup root with voodoo only if u are using super user latest binary. Restore root after jb update.
Sent from my DROID4 using xda app-developers app
does anyone know if this changes the kernel as with gingerbread to ics? curious to know if my ics custom rom will work in safestrap still or if its a done deal
Sorry for spamming on this topic, but just tried to install this after disabling safestrap and done factory reset.
got to recovery and chose the file, it started install but then gave error
"Assert failed: apply_patch_check("/system/bin/logwrapper", "aHASHCODE" ,"ANOTHER HASHCODE")
E:Error in /tmp/sideload/package.zip
Status 7
Installation aborted."
EDIT: OK I have to flash it completely stock with RSDlite and clean package, just downloading it..
EDIT2: Just installing this update, clean ICS with RSDlite helped
rorytmeadows said:
FYI, you will lose root if you do this without Voodoo unrooting first, as I just mistakenly did
Click to expand...
Click to collapse
azrael293 said:
does anyone know if this changes the kernel as with gingerbread to ics? curious to know if my ics custom rom will work in safestrap still or if its a done deal
Click to expand...
Click to collapse
i have not upgraded yet as i allways wait for some type of working sbf..sence this will upgrade your device to jellybean i am sure it will include new kernels
Is it possible to revert to the OEM 4.0.4 (6.16.217) firmware via the existing SBF?
Just curious, I haven't made the jump to JB yet.
rruleford said:
Safeboot and restore complete stock ICS. Don't worry about losing root. RAZR blade method is confirmed to work. Unless u have no access to PC then yes backup root with voodoo only if u are using super user latest binary. Restore root after jb update.
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Do you have a link? I
I did something wrong in the process and vodoo wouldn't restore root for me
bdbraaten said:
Do you have a link? I
I did something wrong in the process and vodoo wouldn't restore root for me
Click to expand...
Click to collapse
It'll be on the RAZR forum
Sent from my DROID4 using xda app-developers app
---------- Post added at 07:25 PM ---------- Previous post was at 07:23 PM ----------
Or here. http://vulnfactory.org/public/razr_blade.zip
Sent from my DROID4 using xda app-developers app
does anyone know how to reflash after update? i mean to reflash the entire phone, not just do a factory rest/wipe. or is that my only option?
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
jmagi said:
does anyone know how to reflash after update? i mean to reflash the entire phone, not just do a factory rest/wipe. or is that my only option?
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Wait for the jb xml
Sent from my DROID4 using xda app-developers app
jmagi said:
does anyone know how to reflash after update? i mean to reflash the entire phone, not just do a factory rest/wipe. or is that my only option?
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Like rruleford said the only way to totally wipe/flash the entire phone would be to wait for the xml fastboot files. What you COULD try is placing the JB OTA update on your external sd card, then booting into stock recovery, wiping data and cache, and then re-flashing the update manually. It should be able to flash over top of itself just fine. Not sure if it would fix anything but might be worth a shot.
Sent from my Droid 4 - Eclipse JB
ok thanks you all, i guess i can wait for the fastboot files then.. it hasnt rebooted on me all day so far. might have been a glitch with apps i installed that no longer work well on jb as they did on ics
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
aah dang sussed it. seems u can now reboot the fone by holding power button for 3-4 seconds. mine gets stuck once in a while so thats what i think was causing the reboots. any chance there's a way to turn that off?
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
jmagi said:
does anyone know how to reflash after update? i mean to reflash the entire phone, not just do a factory rest/wipe. or is that my only option?
Sent from my DROID4 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2207384
ovelayer said:
http://forum.xda-developers.com/showthread.php?t=2207384
Click to expand...
Click to collapse
Thanks for the link, this method is not working for me and I have stock ICS installed, removed safestrap and all, but I get a code 7 validation error of the current version that is installed.. maybe because im dutch and have an adjusted build.prop and apnsconf for data
komani86 said:
Thanks for the link, this method is not working for me and I have stock ICS installed, removed safestrap and all, but I get a code 7 validation error of the current version that is installed.. maybe because im dutch and have an adjusted build.prop and apnsconf for data
Click to expand...
Click to collapse
yes i believe that is what is going on

Failed flashing process 6/21 flash "cdt.bin" phone returned fail ; phone connected

Failed flashing process 6/21 flash "cdt.bin" phone returned fail ; phone connected
Ok I updated to JB, but lost root - so I've tried to flash back to ICS and now get this ****:
Failed flashing process 6/21 flash "cdt.bin" phone returned fail ; phone connected
Any solution? I gather that others are stuck like this too.
TechnoHippie said:
Ok I updated to JB, but lost root - so I've tried to flash back to GB and now get this ****:
Failed flashing process 6/21 flash "cdt.bin" phone returned fail ; phone connected
Any solution? I gather that others are stuck like this too.
Click to expand...
Click to collapse
already try to flash stock ICS .246 FXZ?
renonakal said:
already try to flash stock ICS .246 FXZ?
Click to expand...
Click to collapse
My mistake - that is what I'm really trying to do - FXZ to ICS.
I don't think it's possible to fxz and downgrade the Android version. I got a similar error when I tried to fxz and accidentally chose the old 5.9.905 zip file.
Sent from my Nexus 7 using xda premium
It's been discussed at length that you can't flash back to ICS because of securities. Likely brick risk.
metaljr81 said:
It's been discussed at length that you can't flash back to ICS because of securities. Likely brick risk.
Click to expand...
Click to collapse
Well this sucks - there is no way around this problem? I guess perhaps a JB FXZ might do it when it becomes avail.
If it makes you feel better I blew it too. Didn't even think twice as I was doing it. I'm better than that too. I'll be patiently waiting for the FXZ...
Sent from my SCH-I510 using Tapatalk 2
I did the same thing did the update lost root so I tried to go back I got the same error but now im booting into fastboot flash mode every time I turn my phone on. do you guys have any idea why?
TechnoHippie said:
Well this sucks - there is no way around this problem? I guess perhaps a JB FXZ might do it when it becomes avail.
Click to expand...
Click to collapse
siggers said:
If it makes you feel better I blew it too. Didn't even think twice as I was doing it. I'm better than that too. I'll be patiently waiting for the FXZ...
Sent from my SCH-I510 using Tapatalk 2
Click to expand...
Click to collapse
Won't have to wait much longer. It's just been posted in development
Sent from my skz_tenderloin using Tapatalk HD
obsidianfirefly said:
Won't have to wait much longer. It's just been posted in development
Sent from my skz_tenderloin using Tapatalk HD
Click to expand...
Click to collapse
Link?
chicagows said:
Link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2240725
Back up and running. Thanks for the heads up on the FXZ. I expected at least a week.
Sent from my DROID BIONIC using Tapatalk 2
what if i flash ICS without cdt.bin? Mabye it help back to ICS?
You will brick. The security doesn't allow any of the secure partitions to be downgraded. Not just cdt.
Sent from my Xoom using Tapatalk HD
siggers said:
Back up and running. Thanks for the heads up on the FXZ. I expected at least a week.
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
what version of RSDlite did you use?
stupeds said:
what version of RSDlite did you use?
Click to expand...
Click to collapse
RSD Lite v6.1.5
Sent from my Nexus 7 using Tapatalk HD
Maksim_ka said:
what if i flash ICS without cdt.bin? Mabye it help back to ICS?
Click to expand...
Click to collapse
no... it won't boot,
but, it will let the bionic boot into recovery mode (manually), then you can install the OTA update
tada...
siggers said:
Back up and running. Thanks for the heads up on the FXZ. I expected at least a week.
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
How did you solve this?
What firmware should i use? i dont what is FXZ
can you please help
i am using razr xt912 and fails on flash 1/24 cdt.bin
what should i do?
You are in a bionic thread instead of xt912 one. If you look through the threads for your device, you should be able to find what you need. Good luck!

"There's an internal problem with your device"

Unlocked last week like everyone else using Sunshine. Flashed TWRP, made a backup etc. and all seems well.
However, something is off because when I flash RR it boots but I get everything and its mother force closing, then tried CF's ROM and a warning comes up saying "android system there's an internal problem with your device, and it may be unstable until you factory data reset"
I've tried wiping data as well as factory reset in TWRP, but no luck. I am able to restore my backup, so I'm not in a panic or anything but I can't figure out where I went wrong.
Any help/advice is appreciated. Thanks
When you did a wipe in twrp did you do cache, data, system and dalvik?
Sent from my XT1254 using Tapatalk
tecsironman said:
When you did a wipe in twrp did you do cache, data, system and dalvik?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I only did a factory reset with RR, but with CF's ROM I wiped everything except internal storage in advanced.
Also, is everyone getting not a directory errors in twrp?
Sent from my XT1254 using Tapatalk
cenobite138 said:
Also, is everyone getting not a directory errors in twrp?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Yes.
Sent from my DROID Turbo using XDA Free mobile app
Well I get failed to mount storage. All I do is remount it.
I would honestly wipe your whole device from twrp (including internal storage) and start fresh.
Sent from my XT1254 using Tapatalk
tecsironman said:
Well I get failed to mount storage. All I do is remount it.
I would honestly wipe your whole device from twrp (including internal storage) and start fresh.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Alright, I wiped all contents of the phone and adb sideloaded CF's 1.2.3a rom. Still getting all the force closes and same warning "there's an internal problem with your device".
I also tried both using flashify and fastboot flashing TWRP, but same thing.
Anyone with any ideas? Thanks
What version of Android were you on before you unlocked your device?
Sent from my XT1254 using Tapatalk
tecsironman said:
What version of Android were you on before you unlocked your device?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I rooted with mofo on 4.4.4 when it first came out, but I was running CF's turbopop 1.6, which is 5.1 when I unlocked.
I did try updating the bootloader to the newest, in case that had anything to do with it, but still having errors.
Alright, so get this...
When I asked about the TWRP errors, I was getting error opening /data/data/com.google.android.gms/app_webview
So in android I created a folder called app_webview in /data/data/com.google.android.gms from root explorer, now all is well.
Thanks for your help, and hopefully if anyone else has issues this fix might work for them.
cenobite138 said:
Alright, so get this...
When I asked about the TWRP errors, I was getting error opening /data/data/com.google.android.gms/app_webview
So in android I created a folder called app_webview in /data/data/com.google.android.gms from root explorer, now all is well.
Thanks for your help, and hopefully if anyone else has issues this fix might work for them.
Click to expand...
Click to collapse
Ahh that webview app..
Sent from my XT1254 using Tapatalk
cenobite138 said:
Alright, so get this...
When I asked about the TWRP errors, I was getting error opening /data/data/com.google.android.gms/app_webview
So in android I created a folder called app_webview in /data/data/com.google.android.gms from root explorer, now all is well.
Thanks for your help, and hopefully if anyone else has issues this fix might work for them.
Click to expand...
Click to collapse
I've had the same problem as you, but my problem was inside the /data/data/com.android.chrome/cache/Cache with like 30 cache files missing. Since I was unable to recreate those files I searched for another solution. Flashing your stock rom using Fastboot fixes the problem too, but its resets all your data. Hope this helps anyone with the same problem.

Categories

Resources