I was an idiot. I should've read the instructions and the new software released, but after successfully flashing my phone a few times, I got cocky. I was running greyblur but wanted to update it to the latest official gingerbread FW. I flashed it using CW, but now it's stuck on the load Motorola screen. It'll turn on, show the motorola icon, show GREYBLUR, then just get stuck in an infinite cycle.
I tried leaving it on for a while, about half an hour and nothing worked.
Tried to fastboot, and give it a hard reset but that didn't lead to anything.
Anyways, I've downloaded the FW 4.1.83, tried renaming it to update.zip and running that but it doesn't work..
Can anyone help me out?
IronicUniqueUsername said:
I was an idiot. I should've read the instructions and the new software released, but after successfully flashing my phone a few times, I got cocky. I was running greyblur but wanted to update it to the latest official gingerbread FW. I flashed it using CW, but now it's stuck on the load Motorola screen. It'll turn on, show the motorola icon, show GREYBLUR, then just get stuck in an infinite cycle.
I tried leaving it on for a while, about half an hour and nothing worked.
Tried to fastboot, and give it a hard reset but that didn't lead to anything.
Anyways, I've downloaded the FW 4.1.83, tried renaming it to update.zip and running that but it doesn't work..
Can anyone help me out?
Click to expand...
Click to collapse
Flash a stock 2.3.4 via moto-fastboot
http://bandbinnovations.com/xda/ging...ead-4.5.91.zip
extract boot.img, system.img from the archive and flash via moto-fastboot.
Download moto-fastboot for your OS here:
http://forum.xda-developers.com/showthread.php?t=1138092
Then do the following commands:
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fastboot -w
moto-fastboot reboot
This one should boot up without problems
You can upload files to flash i get error in the link to download the 2.3.4 stock
Tavo_an said:
You can upload files to flash i get error in the link to download the 2.3.4 stock
Click to expand...
Click to collapse
http://bandbinnovations.com/xda/gingerbread/Gingerbread-4.5.91.zip
Related
regardless of what i try the command prompt says "sending..." and goes nowhere from that. i cant flash anything. any ideas?
US Dell Streak for att (not from att) rooted with first leaked 2.1 rom
It would be easier to diagnose if you would be more specific.
Please copy-paste the command you gave and response you got.
smokku said:
It would be easier to diagnose if you would be more specific.
Please copy-paste the command you gave and response you got.
Click to expand...
Click to collapse
smokku's right, does it say 'fastboot' on the streak screen?
Is the device in fast boot mode?
Sent from my Dell Streak using XDA App
phone is in fastboot mode and says as much on the phone screen. what i am currently trying to do is flash back to 1.6 and the guide i was following said flash stock dell recovery. i downloaded the stock recovery file and in cmd i typed
fastboot flash recovery recovery.img
i was in the correct directory and the recovery.img file was there
the cmd then says sending recovery.img... and sits there. it doesnt fail it just does nothing. ive tried flashing several different recoveries including the clockworkmod recovery and i still get nothing but sending...
Try this worked for me
http://www.streaksmart.com/2010/08/...d-16-on-dell-streak-after-21-update.html#more
lufc said:
Try this worked for me
http://www.streaksmart.com/2010/08/...d-16-on-dell-streak-after-21-update.html#more
Click to expand...
Click to collapse
still getting no response from fastboot. i had this problem before and i just kept unlplugging the usb and reinstalling drivers. but its not working for me this time
Right the way to do it is download the recovery image from the last link download the stock recovery from here
http://android.modaco.com/content/d...1-6-downloads-how-tos-rom-superboot-recovery/
open them both up
in the r1-4399-streak-recovery delete the RECOVERY and copy over the recovery from the other file and rename it recovery
put device in fastmode and start the windows batch and the recovery will install
If i ever need to install a stock recovery just install it into the r1-4399-streak-recovery rename it recovery and it will install every time
lufc said:
Right the way to do it is download the recovery image from the last link download the stock recovery from here
http://android.modaco.com/content/d...1-6-downloads-how-tos-rom-superboot-recovery/
open them both up
in the r1-4399-streak-recovery delete the RECOVERY and copy over the recovery from the other file and rename it recovery
put device in fastmode and start the windows batch and the recovery will install
If i ever need to install a stock recovery just install it into the r1-4399-streak-recovery rename it recovery and it will install every time
Click to expand...
Click to collapse
i'll give it a try. thanks
well i finally was able to flash recovery, boot, and system after a reboot of my pc and phone and reinstaling drivers before each flash. now im stuck at the dell logo. ugh...
update: was able to flash to stock 02 1.6 rom. via the link lufc provided (thank you) i guess i'll have to retry flashing back to stock att 1.6 after a few more people have tweaked it and make an update.pkg for it.
punkrckriot said:
well i finally was able to flash recovery, boot, and system after a reboot of my pc and phone and reinstaling drivers before each flash. now im stuck at the dell logo. ugh...
update: was able to flash to stock 02 1.6 rom. via the link lufc provided (thank you) i guess i'll have to retry flashing back to stock att 1.6 after a few more people have tweaked it and make an update.pkg for it.
Click to expand...
Click to collapse
Yeah i got stuck at the dell log a couple times before it successfully flashed. I think something is up with fastboot not properly writing the files because i'll flash the clockworkmod recovery 3 or 4 times in a row with no result. give up on it and flash stock recovery then when i go into recovery mode, its the clockworkmod one :/
fone_fanatic said:
Yeah i got stuck at the dell log a couple times before it successfully flashed. I think something is up with fastboot not properly writing the files because i'll flash the clockworkmod recovery 3 or 4 times in a row with no result. give up on it and flash stock recovery then when i go into recovery mode, its the clockworkmod one :/
Click to expand...
Click to collapse
i just think my PC and fastboot dont agree with eachother. before i can flash anything i have to uninstall the drivers, restart my pc, reboot phone into fastboot again, reinstall drivers, and then flash what im trying to flash one at a time, then restart the whole process to get any results on what i try to flash next. I have no idea whats up with the recoveries because i ran into the same issue of flashing clockworkmod and having it work fine till next reboot and its back to stock.
lufc said:
Try this worked for me
http://www.streaksmart.com/2010/08/...d-16-on-dell-streak-after-21-update.html#more
Click to expand...
Click to collapse
Used this yesterday to go back to 1.6 so my streak gould go off for repair, worked a treat.
spences10 said:
Used this yesterday to go back to 1.6 so my streak gould go off for repair, worked a treat.
Click to expand...
Click to collapse
yeah im on an att streak though so i needed to get back to the US stock rom. its good to go now. thanks though
I decided to update to 2.3.4 after using froyo with the latest gingerblur. I read that i can update straight from gingerblur to 2.3.4, I wish I didn't lol. I followed this guide and got up to step 2 with no problem. Then I got kind of confused, since I already had cwm on my phone I just put this on my sd card and booted into tenfars cwm recovery using the system recovery app. I then selected the gingerbread update and it seemed like it installed just fine but when I rebooted I got up to the green motorola gingerblur screen and it would turn off and turn back on. So I then tried to flash back to 1.2.6 using rsd lite which failed.It still only gets up to the green motorola gingerblur screen. Any help would be greatly appreciated.
Does anyone know how I can get my phone back into working order and properly install kens 2.3.4 rom? The bootloader is still unlocked.
Do you have the new cwm? If so you can flash the 2.3.4 from kennethpenn . If you don't have the lastest it wont work. Fyi the lastest is install with fastboot did you do this? Let me know .
Sent from my MB860 using XDA Premium App
Fastest fix is to fastboot htkw build of gingerbread then flash to the one from kenneth.
have you ever used fastboot? if not i will walk you though it.
1st go download the htkw build http://www.megaupload.com/?d=VLAKXBB3
Fastboot files for u http://forum.xda-developers.com/showthread.php?t=1138092 choose if u have
32 or 64 bit
2st make sure the moto-fastboot or fastboot (they both work i have tested )file is in your c:\
you have to cd the drive first so make sure its in c:\ .FYI make sure all the files are in one folder not the root drive
so name a folder (whatever) then cd that folder from cmd.
Dont use " " just showing you commands
one at a time and wait for them
Then go to cmd
"cd c:\moto-fastboot"
click enter
then type
moto-fastboot flash boot atrix-2.3.4-hktw-boot.img
then
moto-fastboot flash system atrix-2.3.4-hktw-system.img
then
moto-fastboot -w
click enter
Should say writing\sending
Once your done and it completes
type moto-fastboot reboot
enter
Sent from my MB860 using XDA Premium App
It says "moto-fastboot is not recognized as an internal or external command, operable program or batch file"
edit: nvm downloaded the wrong one lol
Lol I think everyone does that first time ,after you get it back where you can use it. Flash cwm. Then we will go over how to install the good gingerbread.
Sent from my MB860 using XDA Premium App
Got everything working flashed cwm installed kens 2.3.4 rom and rooted it aswell. Thanks for all your help I would of been lost without you lol
Np buddy hope you enjoy your phone.
Sent from my MB860 using XDA Premium App
i actually am stuck in a boot loop as well. i unlocked the boot loader on 2.2, then rooted, then flashed tenfars CWM. all went well. tried to flash ken's 2.3.4, installed fine, but upon reboot went into a boot loop.
so i tried the directions in this thread. but the system image is too large. fastboot worked fine with the boot image, but not system image. any advice? thanks!
RogerPodacter said:
i actually am stuck in a boot loop as well. i unlocked the boot loader on 2.2, then rooted, then flashed tenfars CWM. all went well. tried to flash ken's 2.3.4, installed fine, but upon reboot went into a boot loop.
so i tried the directions in this thread. but the system image is too large. fastboot worked fine with the boot image, but not system image. any advice? thanks!
Click to expand...
Click to collapse
lol I believe the reason for that is because the images in the zip weren't made for CWM, but for fastboot. If your fastboot isn't working, make sure you're using the new, updated fastboot from Motorola. Here is a link to it. The files included are for Gingerbread, but I would stick with the Safe update from Kenneth Penn. If anything, just use the Automated Upgrade from here. To use this, try downgrading to 1.8.3 using Fruit cake (don't risk using the SBF on your unlocked bootloader. Might end up with a fancy brick.)
Oh, and before you do anything, BACK UP. =] Friendly reminder =D
Happy upgrading!
~jojojohnson7410~
This happened to me too. Please help.
This same problem happened to me. I'm brand new to this device. Just got it a few days ago. I think I managed to get the bl unlocked and got it rooted. Then I flashed gingerblur and everything was still okay. But when I tried to flash the latest alien build I got that same bootloop as described in the first post. Then I tried the solution in post #4. And it failed. I saved all the commands I entered and their output if that helps. Right now Im stuck at a screen that says "failed to boot 4" followed by "starting rsd mode". Any help would be greatly appreciated. Im a little scared
Hi Moto guys
I bought this RAZR. It is a GSM one without operator customizing.
I rooted it normally and tried to update to ICS leak (this one if I remember well).
It didn't work.
Anyway I downgrade back to Gingerbread and tried to flash in recovery the MIUI V4 zip.
It bootlooped.
So I wanted by the same way to downgrade to 2.3.6 again.
It was a fail.
From this, I had the flash failure screen at the beginning and lost the recovery.
Because of a "Battery Low" I made a factory cable and I can access again to the "flash failure" screen.
I found a tuto relating to the same problem than me and tried to apply it.
I downloaded this rom (SPDREM_U_01.6.5.1-167_SPU-15-M2-1-DE_1C.91P_0A.6C_TMDE_CFC_HWp2b_SIGNED.xml.zip) as explained and tried to flash it in RSD lite.
The problem is:
I have no error message, it just stays stuck on "6/11 flash system "system_signed".
I let it several hours, it never passed away this step.
With "Eternityprj_Fla**** script it's the same, it's blocked at "system writing..."
I don't really know if I'm considered to be on ICS or GB. My bootloader version is 0A.75 so I guess ICS one.
Any idea to reanimate this XT910?
Thanks for the help you could bring to me
P.S: I tried these roms since the first fail
-SPDREM_U_01.6.5.1-167_SPU-15-M2-1-DE_1C.91P_0A.6C_TMDE_CFC_HWp2b_SIGNED.zip
-SPDREM_U_01.6.5.1-167_SPU-15-M2-1-FR_SIGNEuropeAustraliaEMEA_USASPDRRTFR_HWp2b_Service1FF_fastboot.xml.zip
-SPDREM_U_01.6.5.1-73_SPU-11-PASS-10_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml.zip
-SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml.zip
Since I use XP in a VIRTUALBOX machine, I have an icon with activity on device.
During this operation, the activity on the phone is important
C:\Program Files\Android\android-sdk\platform-tools>fastboot.exe flash system sy
stem.img
sending 'system' (793344 KB)...
OKAY [ 28.541s]
Click to expand...
Click to collapse
As it is to this step, no activity...
writing 'system'...
Click to expand...
Click to collapse
I tried with normal fastboot executable from SDK and erpj-fastboot.exe, no difference.
Is it possible I make something wrong with my factory cable?
I don't think so because it makes my phone booting as I plug it and it writes normally boot.img for example with fastboot.
Your help would be appreciated very much guys ^^
Thanks!
Solved!
I can't explain why but I managed to access recovery even if system flash with fastboot never ended.
I flashed ICS rom and it booted well.
So it's solved even if I can't give explanations.
Thanks anyway.
flash fails...repeatedly
This has been covered extensively, but mine is still screwed up, i rooted the phone with clockwork mod. When the official ICS cam eout, i tried to manually download it. I have unrooted the phone and tried to install ics, it failed. So i tried flashing back to factory because clockwork was still popping up on boot. The flash continues to fail. I have tried using moto-fastboot in command prompt, i ha tried rsd lite with the flash(4 different ones). It keeps failing and i end up in the ap fastboot mode. it takes 2 tries to get the phone to boot normally and occasionally the clockwork boot menu pops up on reboot. Any ideas how to just start from scratch. As seen by the problems i have caused myself, i am a complete amateur here.
A little info, the phone is about 8 months old, rooted it once successfully, it is currently unrooted(i tried to reroot but got hung up in ap fastboot), updated drivers twice, moved the flash files all arounf my computer, using windows 7 64 bit. thanks to anyone who may help
Ok ok ok...
if i have an advice, before flashing, read read & read again.
So now.
Give me more info about your phone(xt910 / xt912 / europe / asia / latam /usa ) ??
Can you rsd to system_signed, or flash it manually through fastboot ?
When you installed ics manually which error did you have?
If you can, try to flash system_signed then reflash the OTA package with official recovery & wipe data. But i guess it wont work. For now i can't help you more without more info.
So tell me all you can and write it clear.
Or try this through rsd lite or fla**** http://forum.xda-developers.com/showthread.php?p=28199183
Sent from my XT910 using xda premium
yes, now ics fastboot file is out, you can easily fastboot to get back.
it is usa...i am downloading the ics fastboot now. I have tried the fastboot method with the latest gingerbread build, and also using the command prompt and flash commands....will let you know
thanks
Flash failed right away....how do i know i have the correct drivers? any other ideas?
I had the same issue when attempting to flash. Make sure you switch to a usb 2.0 port.
After that find the moto-fastboot package and then flash all the files manually using moto-fastboot instead of regular fastboot.
You have to do that for every single file. The file names are in the xml in the fastboot file.
first let me say I do not have a RAZR and have searched. I have a friend who was rooted, tried to unroot and install the OTA JB update. He is now stuck in fastboot. His PC will recognize his phone but doesn't show as available like it should. (I have the Note 2 and mine shows under "computer" when connected). he's tried running the razr utility and it fails then says he's back on original version. He can get into bootloader but not into recovery. He says it back the to AP Fastboot screen and then it says boot failed. He was rooted but on stock. he tried to install the JB update both OTA and through his external SD card. can anyone help? does the razr not use odin?
I don't understand exactly your problem. Would you like to flash stock ROM with fastboot recovery? Then you have to
1) install latest Motorola driver package
2) install RSD lite tool
3) boot phone to fastboot recovery
4) connect USB to computer
5) download fastboot package of you choice, exctract it and choose included xml-file in RSD lite
6) start flash and wait until it's finished
he's stuck in a repeat boot. he told me it was a fastboot but I didn't clarify if that meant it was a regular repeat boot screen or if it was the fastboot recovery screen. I didn't realize how different the razr was from my samsung phones. sorry if I am not making sense. He's in SC and I'm in AR so I am only going on what he is telling me.
I assume that he stucks in fastboot recovery.
The only chance to get the device working again is to flash ICS stock ROM with RSD lite.
AcidAngel21 said:
I assume that he stucks in fastboot recovery.
The only chance to get the device working again is to flash ICS stock ROM with RSD lite.
Click to expand...
Click to collapse
can you point me to where I can tell him how to do this? and with links to install please too thank you!
Try this: http://www.droidrzr.com/index.php/t...inux-all-in-one/page__pid__227369#entry227369
http://forum.xda-developers.com/showthread.php?t=2155576
Check out 2nd video.
I would also post links to fastboot files, motorola driver package and RSD-Lite, but unfortunately I'm not allowed to do with <10 posts
By the way, are you XT910 (GSM) or XT912 (CDMA) user?
Would you like to flash ICS or JB?
Note that for JB no fastboot files exits up to now. JB can not be flashed with RSD-Lite.
I am new to cell phone mods. My goal was to gain some experience by rooting and replacing the os image on my Atrix 4G. I use it for my alarm clock which uses an application that won't run on newer version of android than v2.x.x. I successfully rooted and installed super use. I then installed Titanium Backup and did a full backup to sdcard. I installed Rom Manager, chose ClockworkMod Recovery and then the correct image, and told it to flash the recovery partition. Rebooted. Got an error with the android logo and a circle with a triangle. Went back to all the how to's and attempted to install unlockable_bootloader. It now comes up to rsd, seems to fail, then goes into fastboot. Fastboot devices sees it and I can reboot from fastboot but it goes back to the same place. HELP.
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Try this guide. http://forum.xda-developers.com/showthread.php?t=2262869
ravilov said:
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Click to expand...
Click to collapse
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
flash recovery failed
andresrivas said:
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I previously found a thread that described that process and tried it. Fastboot reported it failed flashing recovery.
That usually happens if the BL is not unlocked (properly).
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
reflash the pudding sbf to unlock the bl, then go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
flash boot failed
palmbeach05 said:
reflash the pudding sbf to unlock the bl, th
en go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
Click to expand...
Click to collapse
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Phatdaddy said:
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Click to expand...
Click to collapse
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
palmbeach05 said:
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
Click to expand...
Click to collapse
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Phatdaddy said:
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Click to expand...
Click to collapse
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
palmbeach05 said:
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
Click to expand...
Click to collapse
ls of /system/etc/install-recovery.sh says the file does not exist.
When I bricked my atrix i used the xatrix tool to unbrick it. works really well and once unbricked was fully unlocked so was easy to flash new roms
xatrix (dot) webs (dot) com
once on there website click to download tab to get the downloads
This tool will remove everything from phone root, unlock and install cwm. What you do after that is upto you. sometimes its easier to start over then figure out what went wrong when installing a mod.
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
And thats the part that confuses me. It says 141, but the recovery issue is acting like its a 145. I'm stumped, but i do believe there is an install-recovery.sh script or something thats preventing this thing from sticking after flashing. I'm really baffled by this b/c i ran 141 for the longest time, i did all my rooting, unlocking, and recovery flashing on 141, and got no issues. I could advise that you download and flash the ICS leak (the true leak, not the ROMs we have available) via fastboot and see if that changes the situation, but i don't want to advise you to do something and then a bigger mess appears.
Sent from my MB886 using xda app-developers app
Phatdaddy said:
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
Click to expand...
Click to collapse
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
overboard1978 said:
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
Click to expand...
Click to collapse
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
palmbeach05 said:
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
Click to expand...
Click to collapse
That should do it. If for some reason it doesnt the xatrix tool will wipe everything off the phone and start it over with 141 unlocked bootloader, with cwm. Only automated tool i found that will unbrick phone with rsd lite. Make sure phone is fully charged before starting xatrix tool as it wipes battery fast and if it dies you will need to start over.
Erase cashe was successful, erase data failed. Found reference to additional file to delete but it did not exist either. If I conttinue, I will repost. Thanks for everyone's effort trying to get this working.