hi last night (very late) i was trying out a miui rom i am trying to port, i used the wrong update-script and i seems as though its overwritten my unsafe partition even though i was in safe. i couldnt see the safeboot splash but could still get to it form tools in the bootloader menu, i now have the safeboot menu back but no touch buttons. i have done a restore but i only have 2 backups and this is making me think i haven't backed up when i got on the leak.
so dose any one have a backup they would let me try to see if this is the case, can i fastboot out of this (i dont really understand how fastboot works with this phone as its locked down), or is there anything else i can do to get it back working i would like to keep root if possible.
Are you still able to boot your phone when you try to boot your phone of you can then the best thing for you is that try to install fresh stock room of your phone repeat the whole process again that would be better.
If I or anyone else have helped you in any kind of way please press THANK YOU button.
what type of phone do you have.if you Samsung thing will go fast and smooth to go back to stock Rom
If I or anyone else have helped you in any kind of way please press THANK YOU button.
i have droid 4 this is the droid 4 sub forum, i can boot the safe rom, i used to be able to boot non-safe (had miui on it) but after trying a restore form backup its not booting. i am still new to safe boot i dont fully know how it works.
I think you should be able to use the process for going from one leak to another to to get back to a stock ICS leak system. Follow the instructions in the Droid 4 Utility Updated thread.
Sent from my Droid 4
been thinking that and hoping it to as i think there is root for ICS now, but you are ment to unfreeze apps and uninstall safeboot before you upgrade both of witch i cant do, there is no apps to unfreeze to as the partitions gone.
and safeboot is the only thing that is making this phone not bricked.
Unfreezing and uninstalling recovery shouldn't matter the way I understand it. Fastbooting .219 should wipe that stuff out allowing you to freshly install the ICS leak.
Sent from my Droid 4
Yea, I'd fastboot "back" to 219, which of course WILL brick you, but also allow you to flash the ICS leak, which should get you back to a working phone.
Luckily there are root methods for ICS now, so you don't need to have root on 219 to enjoy root on (ICS) 213 :laugh:
Don't worry man, I've done it a dozen times already.
Just flash the system.img and the preinstall.img .219 fastboot files and erase your data and cache partitions with moto-fastboot:
Code:
moto-fastboot erase userdata
moto-fastboot erase cache
moto-fastboot flash system system.img
moto-fastboot flash preinstall preinstall.img
moto-fastboot flash boot [boot.img for .208/.213 kernel]
(You can skip erasing your /data partition if you want but unless you really need something on there, it's usually best to just start fresh.)
You can find the moto-fastboot executables on xda here with a quick search.
Otherwise you can just do a normal fastboot flash through RSD Lite but the method above is a bit quicker since you only really need to re-flash your /system and /preinstall partitions. If you choose to use RSD Lite, then you have to delete the boot.img file in the .219 package and replace it with the .208/.213 boot.img that you can find here on xda.
Pop the corresponding leaked .208/.213 update .zip file onto your external sdcard and reboot your phone into recovery mode by pressing Vol-Up+Vol-Down+Power and choosing Recovery Menu from the screen with white text on a black background and follow the prompts to install the update from your external card and you're good to go.
thanks i will try this soon.
i have updated to 213 now and it boots in to the animated droid eye but dose nothing not even getting a logcat.
got it working just updated again then wiped catch and data then it booted thanks a lot.
Sweet, glad to hear it. Happy hacking!
Related
Standard disclaimer applies: if anything breaks down, it wasn't me.
Use this only on LG Thrive P506, not P505 or others.
Here's a flashable zip with the latest AT&T FOTA rom (thunderg-user 2.2.2 FRG83G LG-P506-V11h.19BA7112F9). Old, non-working mirror is here.
Changes from stock rom?
- rooted, deodexed, added a2sd support.
- updated Google apps (market, gmail, maps, voice search).
- added FM radio app (from P500) and AppWidgetPicker.
- RTL fix applied.
- AT&T apps moved from /system to /data, so they can be uninstalled.
- build.prop modified: debug.sf.hw=1 and wifi.supplicant_scan_interval=120.
How to flash?
- if you don't have a custom recovery, you first have to root, install Rom Manager and install CWM (use Optimus One (Old BB) version for now, it's imperfect but usable).
- use Rom Manager to boot to recovery (do nothing else from Rom Manager!), make a backup, and install the zip. The rom does not wipe your data, but do a factory reset before complaining about FCs.
Advanced topics
- a patched CWM recovery can be found here. It only solves the color issue, not others. A real solution may be pending.
- I usually delete DunServer.apk and IQAgent.apk from /system/app, as they seem to run automatically and do nothing. Perhaps WapService.apk is expendable too. YMMV.
- AT&T preset bookmarks/contacts can be removed by using SQL tools on the appropriate databases. I didn't bother with wifi/apn presets.
Saving a post for a rainy day.
Thank you so much for working on this, as soon as I get home from my trip I'll be trying this out, I can't wait.
Maybe you can share some screenshots?
It's a stock, non-themed firmware.
See the official page or any review of the Thrive for screenshots.
This Stock P506 Thrive ROM didn't Recovery my P506 Thrive - Why?
Had all the prerequisites setup to apply this Stock P506 Thrive ROM.
In a pinch I needed a ROM and I tried this ROM for my P506 Thrive.
Has anyone also had problems recovering to this ROM? And if so, how did you work around and make a good recovery using this ROM?
Would this work on a Phoenix (P505)?
I tried it and it has the color issue where everything is blue/green and poor resolution. Has anyone found a fix for this yet?
electech said:
Would this work on a Phoenix (P505)?
I tried it and it has the color issue where everything is blue/green and poor resolution. Has anyone found a fix for this yet?
Click to expand...
Click to collapse
One possible fix is not to install a P506 rom on a P505.
It is also written in boldface in the 2nd line of the original post.
Another fix is to restore the backup you did in CWM recovery.
brightstar2 said:
Had all the prerequisites setup to apply this Stock P506 Thrive ROM.
In a pinch I needed a ROM and I tried this ROM for my P506 Thrive.
Has anyone also had problems recovering to this ROM? And if so, how did you work around and make a good recovery using this ROM?
Click to expand...
Click to collapse
What kind of problems? bootloop or FC? did you try to wipe?
LG Thrive P506 2.2.2 ROM Recovery hasn't recovered
Hi,
The P506 phone boots into CMW recovery over and over. Or with key-press sequence phone will boot into fastboot.
Problem isn't limited to this tweaked 2.2.2 ROM, the backup when restored is equally stuck in the boot to CMW.
Wiped many times in my opinion, but what does "wiped" mean to you? Maybe I didn't do it precisely as you want/require before attempting 2.2.2 recovery.
I think you should reflash recovery from fastboot.
Wipe is relevant if you get FCs or standard boot bootloops, not so much for recovery bootloops.
LG P506 Thrive Failure to Recover in to 2.2.2 ROM Newbie
Will try ...
Would you consider sending me a PM, URL or post with tad bit more precision (on reflash recovery from fastboot). Only a few months with this. Still a Newbie
I wrote you a link in the thread you opened.
(As a last resort, I'd try to flash the P506 original stock recovery and see what happens, perhaps it'd do a factory reset.)
Fastboot cries on Update of LG P506 Thrive ROM
If you mean that I should give these fastboot commands...
>fastboot -w
>fastboot update /sdcard/p506_AT_T_v11h_deodexed_rooted.zip
... THEN my LG/Fastboot cries with the following errors/messages:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
errror: update package has not android-info.txt or android-product.txt
So close, so many URLs to consider for remedy and if someone would take a moment and type out the right fastboot command or share the pin-point URL how-to. THEN Thanks in ADVANCE!!
I haven't seen any tutorial around here that recommends the use of fastboot update.
- fastboot flash recovery cwm-recovery.img,
- fastboot boot cwm-recovery.img (keys not working now)
- adb shell
- reboot recovery (keys are working now)
- flash the rom itself from within CWM.
Thanks, Will try (2nd, 3rd) time to flash & recovery LG P506 Thrive
Thanks that is precise and super clear! I needed that. More than worth the few extra bytes of redundant data. Appreciate your time. Will try this again over the week.
And was there a significant typo (prior posting)
Thanks again ... not up to 100% speed with expert android lingo and acronyms, so spelling it out helps.
brightstar2 said:
And was there a significant typo (prior posting)
Click to expand...
Click to collapse
Nope, just missed a letter while typing (key->keys)
Must something obivious I'm doing wrong to Recovery LG P506 Thrive with 2.2.2
Tried, still boots into recovery (orange). Do you see something obvious?
fastboot flash recovery CWM3100-p506-recovery.img
-- OK
fastboot boot CWM3100-p506-recovery.img
-- OK
Then Original Blue-style CWM Recovery on phone
adb shell
-- OK
reboot recovery
-- OK
Now Orange-style CWM Recovery on phone
Apply update from .zip
Choose zip from sdcard
/sdcard/p506_AT-T_v11h_deodexed_rooted.zip --- selected and installed
-- OK
Power Down
Power Up
--> Back into Orange-style CWM Recovery
and here the LG P506 stays following recovery with 2.2.2 ROM
SOLVED - LG P506 Thrive Now 2.2.2 after unroot & AT&T OTA upgrade try to 2.2.2
Thanks to the XDA Forum and users. With it I stitched together a solution and have returned my LG P506 (AT&T Thrive) to good working order with 2.2.2
This was my first Android learner phone, since I would soon need to know Android +/- for work.
Started with a backed up (and backed up) Rooted LG Thrive running 2.2.1 with CWM Recovery. Tried to unroot and return to stock (unfreeze AT&T bloatware, unroot, etc). The AT&T 2.2.2 over-the-air (OTA) was successful, but after reboot the P506 was stuck in a CWM boot-to-recovery mode.
All the fastboot commands, all the CWM recovery commands worked fine. New Custom Stock ROM 2.2.2 re-flashed fine, but the phone would still either boot to CWM Recovery to Fastboot-mode depending on Keys/buttons pressed at boot.
So phone wasn't bricked, but was stuck.
From this XDA forum (this and other XDA forum posting here and there). The Solution was found.
From another LG P506 thread here I got 2 files boot.img and system.img for LG P506 (I did use these files, but perhaps a full custom CWM ROM recovery would be good to -- These are the facts, you can refine)
From the LG Fastboot command I
>fastboot flash boot boot.img
>fastboot flash system system.img
Tried to boot but still stuck at CWM Recovery
POST AFTER POST here says wipe phone more or less. I did wipes with CWM Recovery. I was never really sure how to do enough but NOT TOO MUCH of a WIPE. Too timid as a noob, never tried to fastboot to erase.
LEARNED POINT: fastboot erase is/must-be different than CWM Recovery wipes/formats etc.
The LG P506 was a starter Android phone to learn on, build skill and make mistakes without wrecking an $800 phone.
I had seen another XDA Forum posting about the structure of the phone's file system ... it showed 'system' 'cache' 'userdata' 'misc' 'FOTABIN' 'FOTA' ... plus a few more.
HINDSIGHT: I looked for but could not find a good here is how ANDROID boots for this phone. (1) this .. (2) that ... (3) etc .. kernel, GUI, etc. I suspect I would have learned that something I erased below like FOTA or FOTABIN was running and dying throwing me into CWM Recovery.
I felt I had nothing to loose at this point and no matter what I tried I was (up to that point) still always able to get into CWM Recovery. CWM Recovery ROCKS!
The BREAK THROUGH....
In fastboot mode again.
>flastboot erase FOTA
>flastboot erase FOTABIN
>fastboot erase misc
>fastboot erase cache
>fastboot erase userdata
>fastboot reboot
... there was the LG P506 running 2.2.2 sans the AT&T bloatware. Battery needed recharged, so I took my son to House of Air in the Presidio in San Francisco for trampoline dodgeball.
Nearly 24 hours later the LG P506 Thrive is still working fine.
I suspect that (1) either the boot & system img were needed and something needed erased/wiped.
-- OR --
(2) something like FOTA and/or FOTABIN need erased first and foremost.
As newbie, I was not sure quite what to do at each turn. Using google, I struggled to find insightful android documentation for my problem that was current and not about older versions of ANDROID. The Forum experts use acronyms and speak at an expert-level at times, but the gist of what they shared feels/felt sound. But kind of hard to hear Babe-Ruth explain how to hit a HOME RUN and all together different thing to step into the batter's box and hit a HOME RUN.
Anyhow, the XDA FORUM ROCKS. The experts are EXPERT, I'm unworthy. THANK YOU FOR THE HELP.
If anyone is having problems with this rom you're not doing something right. I wiped dalvik cache, cache, system, and battery stats. Then flashed the rom. Then reboot. It took a few minutes to start up. But its working great. Now im doing some experimenting. I have done several things to my phone as well. Internet speed tweak (which made my dl speeds increase dramatically) and other things. If anyone has things they want tested on a thrive, im willing to do it.
Sent from my LG-P506 using XDA App
This seems to be the only place I can post.
Basically the title.
Here is some info to avoid some easy questions:
Rooted D3 (obviously)
5.6.890 (I think those were the numbers, I am sure it wasn't 5.7 something)
Using the Droid 3 bootstrapper. NOT safestrap, though in Hashcode's post, he said he updated it to be compatible with boostrap.
Flashed Steel Droid v3 about 2 weeks ago, week later flashed to the Bionic Blue theme.
Ran the "Safe bloat removal script (50+ apps) [UPDATED 9/1/2011]" script.
Ran the script to get my bloat back.
No problems until....
Tried to flash to CM7.1 Alpha using Droid 3 Bootstrapper
Bootloop.
tl;dr: How do I correctly install CM7.1?
you may just need to boot into andriod recovery and clear cache. i dont use bootstrap anymore, but its essentially the same. boot into recovery, format /system (under mounts and storage) then install CM7, factory reset (wipe data/cache) then boot her up. Safestrap is the way to go though
So I tried again, wiping my cache and /system, this time I ended up with a soft brick (Only thing appearing is the Motorola Dual Core screen). Clockwork Recovery doesn't appear on startup anymore.
How do I:
a) Unbrick and
b) Correctly install CM7.1?
Thanks to anyone who responds in advance.
EDIT: I should have read more closely, the order I performed the actions was:
1. Install CM7.1
2. Install Gapps
3. Format cache
4. Format /system.
5. Factory reset
slayer621 said:
So I tried again, wiping my cache and /system, this time I ended up with a soft brick (Only thing appearing is the Motorola Dual Core screen). Clockwork Recovery doesn't appear on startup anymore.
How do I:
a) Unbrick and
b) Correctly install CM7.1?
Thanks to anyone who responds in advance.
EDIT: I should have read more closely, the order I performed the actions was:
1. Install CM7.1
2. Install Gapps
3. Format cache
4. Format /system.
5. Factory reset
Click to expand...
Click to collapse
Ya formatting /system after flashing removes the cm7 rom. Try
Format /system
Install cm7/gapps
Wipe data/cache
xt860, android 2.3.5, Monster rom
Endoroid said:
Ya formatting /system after flashing removes the cm7 rom. Try
Format /system
Install cm7/gapps
Wipe data/cache
xt860, android 2.3.5, Monster rom
Click to expand...
Click to collapse
Thanks for that. Any idea on how to unsoftbrick though?
Also, the link in this thread http://forum.xda-developers.com/showthread.php?t=1255198
is dead.
if you formated /system after installing the rom, then you need to SBF. start the phone with m+pwr, use vol down to reach AP Fastboot, then use vol up to select. download RSD 5.5 and the sbf file. check out the RSD thread in the dev section. and you are on verizon, correct?
edit: dang i see what youre referring to. the 5.6.890 download isnt working. i have it, but i dont know i dont have an account to upload to. And on my 5meg pipe itll still take a few min lol
2ndedit: i cant upload. sorry i dont have a professional account and its 455MB.. check this out it works http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/
MrJudylicious said:
if you formated /system after installing the rom, then you need to SBF. start the phone with m+pwr, use vol down to reach AP Fastboot, then use vol up to select. download RSD 5.5 and the sbf file. check out the RSD thread in the dev section. and you are on verizon, correct?
edit: dang i see what youre referring to. the 5.6.890 download isnt working. i have it, but i dont know i dont have an account to upload to. And on my 5meg pipe itll still take a few min lol
Click to expand...
Click to collapse
hxxp://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/
(replace xx with tt)
I'm following this guide, figured I'd just re root and install cwm again and restore my back up. Will that work?
lol yes youve got it. follow the instructions. also, do not freak out if after you SBF it still does not boot up. Even after the SBF (RSD will show rebooting) and you could bootloop on the animation. if that happens, boot into recovery using M+pwr, select android recovery, when you get the android with the !, use vol up and down and you'll get another menu, and clear cache. then you'll be ok
and also, dont use cwm, use hashcodes safestrap. read up on safestrap, and then you can flash without worrying about bricking
MrJudylicious said:
lol yes youve got it. follow the instructions. also, do not freak out if after you SBF it still does not boot up. Even after the SBF (RSD will show rebooting) and you could bootloop on the animation. if that happens, boot into recovery using M+pwr, select android recovery, when you get the android with the !, use vol up and down and you'll get another menu, and clear cache. then you'll be ok
and also, dont use cwm, use hashcodes safestrap. read up on safestrap, and then you can flash without worrying about bricking
Click to expand...
Click to collapse
Alright thanks man, after I get back up and running I'll be sure to switch to safestrap. Thanks for all the help.
glad i could help. ive been there lol
Hello guys.
I lost several hours and still no success.
I want to clone ICS leak into the safe system for rebuilding some files and have non-safe system as untouched for recovery if something will happen.
But I have no luck to launch moto ics leak in the safestrap. What I tried:
1. found that safe system's partition is the preinstall, it's /dev/block/mmcbl1p22
2. installed clean ICS leak, dumped rooted system.img using dd command.
3. installed safestrap into ICS leak.
4. in the safestrap I went to console, but since preinstall partition is 608MB only (normal system partition is about 640MB), I had no chance to use dd command to restore system.img to /dev/block/mmcbl1p22 by the sector method.
5. Mounted system.img, created .tar archive for saving all permissions for folders and files, then I did format preinstall partition and unpacked .tar files. All seems to be fine and ready to boot.
6. After trying to boot safe system, I stuck on the animation logo. It's not bootloop, it's something other.
7. I decided to restore my /data from normal non-safe system and I had success on booting ICS leak as safe system.
8. BUT no sound in the boot (droid), and no main sound. When I go to settings -> sound and trying to play something, I have freezing of settings.apk.
9. If I go to phone.apk and try to dial, sound from dial numbers are ok.
10. Camera is force closing.
Any suggestion where am I wrong?
Thanks:good:
olegfusion said:
Hello guys.
I lost several hours and still no success.
I want to clone ICS leak into the safe system for rebuilding some files and have non-safe system as untouched for recovery if something will happen.
But I have no luck to launch moto ics leak in the safestrap. What I tried:
1. found that safe system's partition is the preinstall, it's /dev/block/mmcbl1p22
2. installed clean ICS leak, dumped rooted system.img using dd command.
3. installed safestrap into ICS leak.
4. in the safestrap I went to console, but since preinstall partition is 608MB only (normal system partition is about 640MB), I had no chance to use dd command to restore system.img to /dev/block/mmcbl1p22 by the sector method.
5. Mounted system.img, created .tar archive for saving all permissions for folders and files, then I did format preinstall partition and unpacked .tar files. All seems to be fine and ready to boot.
6. After trying to boot safe system, I stuck on the animation logo. It's not bootloop, it's something other.
7. I decided to restore my /data from normal non-safe system and I had success on booting ICS leak as safe system.
8. BUT no sound in the boot (droid), and no main sound. When I go to settings -> sound and trying to play something, I have freezing of settings.apk.
9. If I go to phone.apk and try to dial, sound from dial numbers are ok.
10. Camera is force closing.
Any suggestion where am I wrong?
Thanks:good:
Click to expand...
Click to collapse
Couple of questions for you and I should be able to help you out.
Which leak are you currently running?
Did you install Safestrap v1 or v2?
You would need to follow jsnweitzel's thread on installing the leak, rooting and installing safestrap v2 (this is the ics safestrap).
Then you should be able to switch from the stock leak safe rom and go into safe mode which will create your backup and then go into a nonsafe version of your leak for modding, tweaking, etc.
Let me know if this helps/is easily understood and if you have questions. You can PM me as well.
EDIT::
http://forum.xda-developers.com/showthread.php?t=1779810 ,- D4 Tool for ICS w/ leak updating, root and safestrap.
Which leak are you currently running?
Click to expand...
Click to collapse
215 latest
Did you install Safestrap v1 or v2?
Click to expand...
Click to collapse
2.00a, with console ability
You would need to follow jsnweitzel's thread on installing the leak, rooting and installing safestrap v2 (this is the ics safestrap).
Click to expand...
Click to collapse
I installed, all fine.
Then you should be able to switch from the stock leak safe rom and go into safe mode which will create your backup and then go into a nonsafe version of your leak for modding, tweaking, etc.
Click to expand...
Click to collapse
I'm able to switch from stock leak to any other safe rom like cm9.
D4 Tool for ICS w/ leak updating, root and safestrap.
Click to expand...
Click to collapse
Thanks.
But I know all this already.
I need to run stock leak ICS 215 in the safe system and in non-safe system both in same time. In other words, clone non-safe system with safe system. That's all I need.
You dont need to install another rom then. All you need to do is switch into safe mode and reboot. No need to install another rom over it.
Hashcode created a .206 stock ROM that can be flashed to your safe system in safestrap. I don't know much about what goes into creating a ROM that can be flashed to the safe side but maybe you could use that as a reference in creating a flashable .215 ROM?
Here is the .206 stock ROM thread: http://forum.xda-developers.com/showthread.php?t=1716382
kwyrt said:
Hashcode created a .206 stock ROM that can be flashed to your safe system in safestrap. I don't know much about what goes into creating a ROM that can be flashed to the safe side but maybe you could use that as a reference in creating a flashable .215 ROM?
Here is the .206 stock ROM thread: http://forum.xda-developers.com/showthread.php?t=1716382
Click to expand...
Click to collapse
Thank you, I'll definitely look at it.
update.
but link is dead and it seems that file was deleted from the site.
There aren't up, when rombot crashed they neglected to reupload the ICS leak safe system builds. What are you trying to do in safe system? I developed and tested a deodexer (read lots and lots of "softbricking") on my "unsafe system" but my phone still works. As long as you make a safestrap backup you should be fine, especially if your using the altered version of safestrap with terminal, just make a backup of the files you change and if it doesnt boot copy them back!
Sent from my DROID4 using xda premium
moah909 said:
There aren't up, when rombot crashed they neglected to reupload the ICS leak safe system builds. What are you trying to do in safe system? I developed and tested a deodexer (read lots and lots of "softbricking") on my "unsafe system" but my phone still works. As long as you make a safestrap backup you should be fine, especially if your using the altered version of safestrap with terminal, just make a backup of the files you change and if it doesnt boot copy them back!
Sent from my DROID4 using xda premium
Click to expand...
Click to collapse
I'm actually started to use safestrap with terminal for restoring my state, but I thought that I will able to create easier process for testing - using safe system. And was crazy and mad when things happened (in first post) with stock ICS and safe system
fixed a problem, I stupidly forgot about symlinks.
Could you explain, either in this thread or a guide, how you accomplished that? I agree that it would be a lot simpler in a safe system, although testing does work in unsafe I tried doing it when the rombot build was down, but to no success :-/
Sent from my DROID4 using xda premium
moah909 said:
Could you explain, either in this thread or a guide, how you accomplished that? I agree that it would be a lot simpler in a safe system, although testing does work in unsafe I tried doing it when the rombot build was down, but to no success :-/
Sent from my DROID4 using xda premium
Click to expand...
Click to collapse
After all what I did, I found Arctic ICS rom in droidforums and found all "ready to go" update-script there. You can download it and use as example for creating safe system rom.
I was trying to upgrade safestrap from 3.73 to 3.75 so that I could install CM12. I did not remove 3.73 before installing 3.75, causing major boot problems. I was able to boot into Fastboot, and using the DROID 4 Utility XT894 Jellybean, I flashed the official jellybean firmware. Now my phone will get as far as the Droid Eye logo boot animation, but will not finish the boot. Are there any other utilities or methods that I can try to get the phone back up and running? I have access to another Droid 4, so if there's a way to copy the ROM from it to mine with adb, or some other method, I'd be open to that. Any help would be appreciated.
No idea about that utility. Without Safestrap or a working O/S, ADB is only available from stock recovery (I think), and stock recovery is almost completely useless on this phone.
If you still had access to SS, then you could restore a backup made on another phone, but in stock form the phone has no way to make/restore system backups.
At a guess, the DROID 4 Utility flashes one of the two newest XMLs depending on whether you want to keep data or not. If you chose 2, it could be that the boot process is getting hung up on something you have installed. Since you're using stock, did you try safe mode?
Failing that, or if you already chose a complete wipe in the Droid 4 Utility and got stuck anyway...for each of the several times I've managed to brick my phone, I've always used RSDLite and manually flashed the appropriate XML via Fastboot, have never had any problems.
RSDLite: http://rsdlite.com/rsd-lite-download/
Newest stock JB 4.1.2 XML (VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip): via Mega (probably fastest, in Firmwares), Motofirmware or AFH, links courtesy of @sd_shadow's big document of Droid 4 stuff
Note that the above XML will wipe data and internal storage (SD card is unaffected). If you need to keep those, use cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip instead (also in the Mega Firmwares folder, or get other links from the above document), it should keep everything. Probably. I hope you made a backup before trying to upgrade SS : \
Connect your phone via USB, get into Fastboot
Start up RSDLite
Click the "..." next to the Filename box, select the XML zip
Click "Decompress And Start Flashing"
Give it a while to complete
Hopefully, bootable ROM. Note that RSDLite will probably get "stuck" on the last reboot, waiting for the phone; it's safe to close once the flash is completely complete (e.g. you're at the boot animation)
I'd imagine that the Droid 4 Utility does much the same as RSDLite, just in a somewhat more automated fashion, but it never hurts to try something slightly different.
RSD Lite is more complex than the utility, slightly different methods, if one failed try the other.
Stock recovery is really only good for factory reset and wiping cache, if you haven't already done so, wipe them now.
Sent from my XT907 using Tapatalk
I was able to get it up and running with the Mfastboot method:
https://docs.google.com/document/d/102LcdnDXpSjOXWdR39Zl4wMikfWRw2KAj63PuoJyJz4/edit
So I decided to try out Ivan's Marshmallow ROM, knowing it would be a bad idea... I backed everything but the photos which were 2.5GBs and was too lazy to copy over. I wiped cache, but not user data, copied ROM to phone, rename to update.zip and updated through recovery(stock). Now it's stuck on booting and want to know if there is any way to recover my photos.
Keep in mind there is a functional MIUI ROM inside but it is named differently than update.zip so I don't know how to flash it. It turns on, boots on fastboot and recovery but can't do much... I could wipe it, but I need the photos....
Thanks in advance.
eXtrimist said:
So I decided to try out Ivan's Marshmallow ROM, knowing it would be a bad idea... I backed everything but the photos which were 2.5GBs and was too lazy to copy over. I wiped cache, but not user data, copied ROM to phone, rename to update.zip and updated through recovery(stock). Now it's stuck on booting and want to know if there is any way to recover my photos.
Keep in mind there is a functional MIUI ROM inside but it is named differently than update.zip so I don't know how to flash it. It turns on, boots on fastboot and recovery but can't do much... I could wipe it, but I need the photos....
Thanks in advance.
Click to expand...
Click to collapse
Assuming that you haven't yet extended partitions, stock phone has 2 system partitions. So if you're using system 1, boot using system 2 and vice versa. AFAIK, if you flash stock miui using MiTools, it wouldn't erase the storage on the phone.
The second partition seems unable to boot as well...
Anyway, if found out I could install twpr through fastboot, from where I could mount the sdcard.
As far as MiTools are concerned, last time I tried it, I think it erased everything.
The thread can be closed. Thanks!
eXtrimist said:
The second partition seems unable to boot as well...
Anyway, if found out I could install twpr through fastboot, from where I could mount the sdcard.
As far as MiTools are concerned, last time I tried it, I think it erased everything.
The thread can be closed. Thanks!
Click to expand...
Click to collapse
Glad you could work it out. Don't be lazy next time