I've been having a few issues with the root and rom as time has went on. First my fingerprint reader went, then I would have random crashing and shutdowns. Those errors began to get more frequent, and now the internal memory card decided it will wipe itself clean. So I'm done with what ever I had installed. According to the phone that was on April 4th.
I've read some confusing stuff on here about rooting and unrooting, and none of the information is the same. I imagine thats because of all the updates the phone has gone through.
I would like to install cm7 or cm9 since it seems much more stable.
Any help at all to even simply unroot the phone would be appreciated. I need full functionality back.
Atrix 4g
android ver. is 2.2.1
kernel ver is 2.6.32.9
Build number is 1.5.7
Rom: GingerBlur
Just wipe data,cache and dalivk from recovery and install which ever rom u want if u have a unlocked bootloader for completely erasing the previous rom u can use fastboot wit these commands.
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
And if u have not unlocked the bootloader check this link first
THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs
terminator1983 said:
Just wipe data,cache and dalivk from recovery and install which ever rom u want if u have a unlocked bootloader for completely erasing the previous rom u can use fastboot wit these commands.
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
And if u have not unlocked the bootloader check this link first
THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs
Click to expand...
Click to collapse
Actually, if you want the cleanest and least likely to cause problems method, you should do a full fastboot wipe prior to installing any new ROM. Just wiping data, cache, and dalvik does not give you a completely clean wipe and prep properly for the new ROM.
If you are updating a ROM from a previous release, you are usually OK with just wiping Dalvik and cache. The dev will normally state what to do in their thread.
Thanks for the replies. How would I be able to check if I've unlocked the boot loader? I did this almost a year ago so I don't remember if I also did that.
21q said:
Thanks for the replies. How would I be able to check if I've unlocked the boot loader? I did this almost a year ago so I don't remember if I also did that.
Click to expand...
Click to collapse
We couldn't unlock the bootloader a year ago. Was around end of June we had this ability.
If ur phone bootloader is unlocked u can see unlocked written on top corner of boot screen logo.
terminator1983 said:
If ur phone bootloader is unlocked u can see unlocked written on top corner of boot screen logo.
Click to expand...
Click to collapse
Not necessarily. If a SBF has been flashed after unlock, the word "unlocked" is not there.
So going off of what you two have said and another thread I looked at. I have time to do this sunday.
First I will unlock the bootloader
then run through these steps
boot to recovery
Wipe Dalvik
wipe cache
factory reset/data
boot into fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
From here I can then load cm7 rom onto my sd card and install it via recovery?
Also, reading further into cm7, it doesnt support he fingerprint reader or web/lap-top huh. Are there any nightly releases that have it? I've seen ONE, but I've been out of this scene too long to really know what good right now.
21q said:
So going off of what you two have said and another thread I looked at. I have time to do this sunday.
First I will unlock the bootloader
then run through these steps
boot to recovery
Wipe Dalvik
wipe cache
boot into fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
From here I can then load cm7 rom onto my sd card and install it via recovery?
Also, reading further into cm7, it doesnt support he fingerprint reader or web/lap-top huh. Are there any nightly releases that have it? I've seen ONE, but I've been out of this scene too long to really know what good right now.
Click to expand...
Click to collapse
Download CM7.2 RC1 > http://forum.xda-developers.com/showthread.php?t=1556246. It has full FP reader support, both security and navigation. (No webtop though).
After unlocking the bootloader (assuming you will be following these instructions > http://forum.xda-developers.com/showthread.php?t=1136261) You will need root again (instructions also in the previously linked thread), and then you will want to flash Romracers recovery through fastboot before flashing any ROM >
http://forum.xda-developers.com/showthread.php?t=1204500
After this you will be able to get into recovery and flash whatever you want. There is an automated script here for unlocking the bootloader also located here > http://forum.xda-developers.com/showthread.php?t=1182871.
Been a while since I did all this myself, but I think I covered everything!
Good luck.
***Ignore this post***
So I don't need to run any of those fastboot commands??
And should I update my phone to 2.3.4?
I just updated it to 1.8.3 by flashing the sbf so I've lost root and everything.
I ended up flashing using this method
http://forum.xda-developers.com/showthread.php?t=1138204
I used the sbf that was supposed to already have the bootloader unlocked and the do some things for root.
When I went to install romracers though I was getting the error (180002)
From what I have read that means the boot loader wasnt actually unlocked?
So I'm guess I should flash the regular 2.3.4sbf. Then manually unlocked the bootloader myself and then root?
Or could I still manage with whats currently installed some how?
Again thanks in advance for any advice.
CaelanT said:
Not necessarily. If a SBF has been flashed after unlock, the word "unlocked" is not there.
Click to expand...
Click to collapse
Does it mean u have relocked the bootloader or it is still unlocked ?
Sent from my MB860 using xda premium
Does doing a full fastboot wipe delete the cwm recovery?
arpit85 said:
Does it mean u have relocked the bootloader or it is still unlocked ?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I don't believe it was ever unlocked
When I flashed the sbf via rdslite it would go to 100% but would be stuck saying "in process"
I made a new thread though since my problem is completely different now
http://forum.xda-developers.com/showthread.php?t=1568347
21q said:
I ended up flashing using this method
http://forum.xda-developers.com/showthread.php?t=1138204
I used the sbf that was supposed to already have the bootloader unlocked and the do some things for root.
When I went to install romracers though I was getting the error (180002)
From what I have read that means the boot loader wasnt actually unlocked?
So I'm guess I should flash the regular 2.3.4sbf. Then manually unlocked the bootloader myself and then root?
Or could I still manage with whats currently installed some how?
Again thanks in advance for any advice.
Click to expand...
Click to collapse
If you flashed sbf with rsdlite and text unlocked is gone, thats mean that you have relocked BL.
You can unlock again by flashing via RSDLite this:
ATT ONLY(It works for 4.5.91 and 4.5.141- Tested myself yesterday) - http://diamantephoto.com/pudding.rar
It is from post:
http://forum.xda-developers.com/showthread.php?t=1136261
Related
Hello Friends,
I have Moto Atrix 4G with Alien#4 Android version installed on it with following details.
System Version: 4.5.91.MB860.ATT.en.US
Android version: 2.3.4
Kernel version: [email protected]#2
Build number: Alien#4
Click to expand...
Click to collapse
I tried flashing CM7 but it does not work
http://forum.xda-developers.com/showthread.php?t=1463386
http://forum.xda-developers.com/showthread.php?t=1398819
Phone gets stuck on boot screen
When i again install Alien#4 from recovery it works fine.
kindly help to sort out this problem.
thanks in advance
Pull your battery out on boot logo stuck just for 1-2 sec and put it in.
always works for me
Also,
1. Are you using the latest Romracer's recovery?
2. Did you wipe properly before and after the installation?
How long are you letting your phone sit and reboot for after flashing CM7?
You may just be not letting it sit long enough. It can take a while on first boot.
LOCKDOC_UA said:
Pull your battery out on boot logo stuck just for 1-2 sec and put it in.
always works for me
Click to expand...
Click to collapse
Tried It Does Not Work
xploited said:
Also,
1. Are you using the latest Romracer's recovery?
2. Did you wipe properly before and after the installation?
Click to expand...
Click to collapse
Yes Using Romracers Recovery
Yep Wiped All Factory, Cache & Dalvlink Still No Go
CaelanT said:
How long are you letting your phone sit and reboot for after flashing CM7?
You may just be not letting it sit long enough. It can take a while on first boot.
Click to expand...
Click to collapse
Must Be More Than 15 Minutes.... Will Try Flasing Agin Tomm And Post back
Try a full fastboot wipe:
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
Helping?
yes as said above try pulling battery i had the same problem with mine and that helped also i have read on the dev forums about this and it may help be sure you have the newest rom racers and recovery, try waiting for a while after first boot it is a long one much longer than other roms i have tried, be sure to factory reset, wipe cache, go to advanced and delete the cache in there, and do a battery stat wipe (for the heck of it). Install the rom and let it load if it does get stuck just pull battery and try again it usually loads on the 2nd try on mine with some other roms as well.
Also you should try the aura roms and cm9 (although cm9 currently isnt playing music on my phone) it is based off of Ice Cream Sandwich)
CaelanT said:
Try a full fastboot wipe:
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
Click to expand...
Click to collapse
Is It necessary to erase webtop too?,
What If In Case I Want To Go Back To The Previous Rom Or The Stock Rom
CaelanT said:
Try a full fastboot wipe:
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
Click to expand...
Click to collapse
Tried Your Method Still Stuck At Start Screen..
Any Idea?
Wipe everything again, then try installing the ROM a few times in a row. I had the same problem with the joker's CM9 ROM.
Inspiredwire said:
Wipe everything again, then try installing the ROM a few times in a row. I had the same problem with the joker's CM9 ROM.
Click to expand...
Click to collapse
is your bootloader unlocked?
pienne said:
is your bootloader unlocked?
Click to expand...
Click to collapse
Yep, I'm not having any problems.
I was just explaining to the OP that they may need to flash the ROM twice in a row for it to take. I had to do it with jokers CM9 ROM in order for it to work. Joker just posted about it last night.
Though, if you're asking the OP, Ken's Alien ROM didn't require an unlocked bootloader so that may be the problem.
my phone wasnt restoring my backups in twrp recovery and now i have no os and i can only get to bootloader, i relocked my bootloader so i could run ruu but my phone is on the latest version so nothings working, i need help as soon as possible please
kjrehrer said:
my phone wasnt restoring my backups in twrp recovery and now i have no os and i can only get to bootloader, i relocked my bootloader so i could run ruu but my phone is on the latest version so nothings working, i need help as soon as possible please
Click to expand...
Click to collapse
Put TWRP back on. Go into recovery. Keep connected to PC. Transfer a sense ROM and flash it. Assuming you're S-ON: flash MeanBean. Or flash a different sense ROM that has an S-ON installer. Or fastboot flash boot boot.img when you install.
Delakit said:
Put TWRP back on. Go into recovery. Keep connected to PC. Transfer a sense ROM and flash it. Assuming you're S-ON: flash MeanBean. Or flash a different sense ROM that has an S-ON installer. Or fastboot flash boot boot.img when you install.
Click to expand...
Click to collapse
how do i unlock the bootloader again because i relocked it
kjrehrer said:
how do i unlock the bootloader again because i relocked it
Click to expand...
Click to collapse
If you've unlocked the bootloader before then you know how to unlock the bootloader.
Delakit said:
If you've unlocked the bootloader before then you know how to unlock the bootloader.
Click to expand...
Click to collapse
yeah i got it but im putting the mean bean rom on my phone then do i wipe and just flash it?
Delakit said:
If you've unlocked the bootloader before then you know how to unlock the bootloader.
Click to expand...
Click to collapse
when i try to flash it i get "error executing updater binary in zip '/sdcard/meanrom...... error flashing zip" what do i do? every rom i try flashing gives me this error
Unlock the bootloader again, first of all.
Delete your current recovery.img.
Re-download your recovery.
fastboot erase cache
install your recovery again
fastboot erase cache
boot into recovery
when connected you should be able to transfer files from PC to phone.
Otherwise you might need to use USB-OTG I think.
wipe data, cache, delvik/cache, system
Install the ROM.
reboot to bootloader
pull boot.img out of your ROM download
fastboot flash boot boot.img
reboot to system.
Delakit said:
Unlock the bootloader again, first of all.
Delete your current recovery.img.
Re-download your recovery.
fastboot erase cache
install your recovery again
fastboot erase cache
boot into recovery
when connected you should be able to transfer files from PC to phone.
Otherwise you might need to use USB-OTG I think.
wipe data, cache, delvik/cache, system
Install the ROM.
reboot to bootloader
pull boot.img out of your ROM download
fastboot flash boot boot.img
reboot to system.
Click to expand...
Click to collapse
i get an error when i try to flash roms
kjrehrer said:
i get an error when i try to flash roms
Click to expand...
Click to collapse
Lol. I understand that. Not much I can do to help you if you don't try what I already suggested.
Delakit said:
Lol. I understand that. Not much I can do to help you if you don't try what I already suggested.
Click to expand...
Click to collapse
i sent you a direct message about this
Uncheck all options in twrp.
Sent from my EVO using Xparent Skyblue Tapatalk 2
Okay, so I was trying to unlock my bootloader. Completed ALL the steps up to were I had to flash Radio.zip to get my signal back. Stupid me accidently hit to install the rom I had choosen to install after unlocking my bootloader. I didn't notice untilit was already installing. So it rebooted and I just get the non animated LG logo and it says security error under it. I am able to get to the s/w upgrade screen by holding volume up and plugging usb in. I searched Everywhere and can't solve the issue. I tried re-flashing my kdz file and it only goes to 15% then says my phone is not connected, tried reinstalling the drivers and got the same message. Then I proceeded to the online method. While doing this it found my phone and proceeded to the second part where it begins downloading. It went to 13 seconds time lapsed the stopped. No bar moving across and no more counting with the time lapse. I had read were it froze on others and they let it proceed and it did its thing. So I left it for about 4 hours and nothing changed. I then checked my traffic meter on my router and nothing had even began downloading. I reinstalled and tried again. It would go threw the checking for other software part fine then when it gets to the downloading part its at the 13 second time lapse freeze again. This time it didnt count up to it. It was just instantly where I had left off. I then went to my brothers and tried to his computer. Completely reinstalled it and it did the same thing! Didnt even count up to 13 seconds was just instantly there! I then read where someone had the same issues as me and installed fastboot and flashed xloader and uboot and then the offline method reconized them. Im thinking this is my key to fixing, however when i install the driver as instructed it says install failed because lack of electronic signature. So im lost and ran out of search methods to try. Has anyone else had this issue when installing fastboot? Also I was a little confused on which fastboot file to use so I tried a few and all had the same result. Does someone have a link to the one I need or any other advice? This stinks I just bought this phone but the stock rom was driving me crazy because im use to custom! Thanks so much and please help!!!
SOLVED! flashed ics xloader and uboot and it finally found my phone on the offline method. Now I just have the wonky TS to solve. Should be fun since I lost root and cwm. I was able to get show touches and usb debugging on so that makes lofe easier. You guys have no idea how relieved I feel! I thought I pretty much threw 200 bucks away!
Okay little update. I got fastboot loaded on my phone and flashed a recovery.img but still not having any luck. Both programs are doing the same exact thing as before. I feel like im getting there since I now have fastboot. What other options do I have that I can try?
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase boot
Flash the ICS u and x and then use upgrade mode to flash the kdz with offline method.
Sent from my LG-P769 using XDA Premium 4 mobile app
LaDY Vengeance said:
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase boot
Flash the ICS u and x and then use upgrade mode to flash the kdz with offline method.
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay I got it all up and running. However when I used your commands none of them would respond and do anything except flashing the ICS u and x. Once I did this I was able to get the offline method to work. I then rooted and installed Cwm to run the ts fix because I had the wonky touchscreen. I then flashed kumas rom . I forgot to use CWM to clear my cache and such before flashing to kumas ROM. Will this effect anything? Should I go to cwn and delete it all and reflash kumas ROM? Thanks!
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase boot
I using that and i have S/W Upgrade ;(. My phone does not have logos lg and automatically turns on when you insert the batteries into the s / w upgrade
SlideShowPl said:
fastboot erase userdata
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase boot
I using that and i have S/W Upgrade ;(. My phone does not have logos lg and automatically turns on when you insert the batteries into the s / w upgrade
Click to expand...
Click to collapse
So the only this you can access is sw upgrade mode? what lead up to this? did you install fastboot drivers twice?
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.
I downloaded some twrp backups and I tried to flash twrp using flashify but I keep getting bootlooped. Idk why it's doing this but in order to get S-OFF I need to get back to stock and the back up is my only chance. My phone bootloops when I've flashed twrp using flashify and I reboot into recovery. Any thoughts on maybe why twrp is making my phone bootloop? Is anyone else having these problems?
That's happened to me a few times as well. What worked for me was to flash twrp through adb or fastboot. You may have to try some older versions of twrp if the current release doesn't work. If I'm remembering correctly I think 2.7.0.1 and 2.8.3.0 worked for me. I believe it depends on what version of android you're currently running. Look here http://teamw.in/project/twrp2/225
To add a bit to what was mentioned above, do fastboot erase cache, and flash TWRP using fastboot.
This solves most issues with TWRP not flashing or booting properly.
Also, make sure you bootloader is UNLOCKED.
iTzz_KAMIKAZE said:
Idk why it's doing this but in order to get S-OFF I need to get back to stock and the back up is my only chance.
Click to expand...
Click to collapse
No, it isn't. You can also relock the bootloader and RUU back to stock.
redpoint73 said:
To add a bit to what was mentioned above, do fastboot erase cache, and flash TWRP using fastboot.
This solves most issues with TWRP not flashing or booting properly.
Also, make sure you bootloader is UNLOCKED.
No, it isn't. You can also relock the bootloader and RUU back to stock.
Click to expand...
Click to collapse
So I just tried to flash the recovery using fastboot with no luck. I followed the directions off of TWRP's thread and even tried it a second time running the "fastboot erase cache" first, still with no luck. Now you mentioned me relocking my bootloader and then RUU back to stock, is there a thread I can go to to try that?
iTzz_KAMIKAZE said:
So I just tried to flash the recovery using fastboot with no luck. I followed the directions off of TWRP's thread and even tried it a second time running the "fastboot erase cache" first, still with no luck. Now you mentioned me relocking my bootloader and then RUU back to stock, is there a thread I can go to to try that?
Click to expand...
Click to collapse
Try a couple older TWRP builds, to see if that helps (as recommended in previous post by johnnyutah22).
You can try RUU, you don't need a thread for that. Relocking the bootloader is a single command:
fastboot oem lock
After that, just run the RUU, its a Windows executable, and very self explanatory. You can find the RUUs linked in my Index thread:
http://forum.xda-developers.com/showthread.php?t=2751432