Related
UPDATE: To fix 3.0.2.4 from not formatting /system
Open rom manager and select settings, and check erase recovery. hit menu again and select clear cache, then flash 3.0.2.4 again.
now if your in recovery and you cant boot back up to use rom manager, use the file below. It will allow you to restore your backup then once booted back up use the method above to fix 3.0.2.4.
The reason im leaving custom over 3.0.2.4 is bc i know fastboot flash with this one will allow you to restore without wiping recovery or clear cache or anything else.
http://www.mediafire.com/file/b8ejhqbf3tgnsoe/recovery.img - this is CMW 3.0.1.4 just altered for installing zips. linking for people needing a recover img to boot up
To install:
1. If in recovery, open ur terminal on ur pc and type adb reboot boatloader
2. Once in bootloader it will load fast boot and say fastboot usb in red
3. cd to the folder with fastboot.exe and also place recover.img in that folder
4. then enter fastboot flash recovery recovery.img
5. adb reboot recovery
6. restore your backup and boot up
RafficaX said:
Little FYI for all, cwm recovery wont format system on a restore. made a backup, tried a flash and went to restore and it fails formatting system.
So be careful with flashing and all bc yo may not be able to restore currently with cwm.
UPDATE: format system in menu also fails! be careful bc you pretty much cant restore or flash atm!
Click to expand...
Click to collapse
Oh how I miss Amon_Ra
jlevy73 said:
Oh how I miss Amon_Ra
Click to expand...
Click to collapse
im really hoping Amon_Ra does do his recovery on T-Bolt. I like Rom Manager and its features but would rather loose features for stability and reliability on each use.
RafficaX said:
im really hoping Amon_Ra does do his recovery on T-Bolt. I like Rom Manager and its features but would rather loose features for stability and reliability on each use.
Click to expand...
Click to collapse
QFT
can't wait for amon-ra
raffica, what version of CWM worked for you?
MYxdaUSERNAME said:
raffica, what version of CWM worked for you?
Click to expand...
Click to collapse
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Thanks for the heads up I agree I always loved CWM on my N1 but it started giving me all kinds of grief for several different reasons so I finally went to Amon Ra.
RafficaX said:
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Click to expand...
Click to collapse
Can you help me out and provide it because right now i cant even boot
RafficaX said:
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Click to expand...
Click to collapse
isnt UD banned on these forums?
just curious dont flame me or anything! cuz when a Ud rom hit the inc the thread was deleted in minutes
superchilpil said:
isnt UD banned on these forums?
just curious dont flame me or anything! cuz when a Ud rom hit the inc the thread was deleted in minutes
Click to expand...
Click to collapse
yeah, if you go on their forums all they do is flame XDA left and right. But I find it funny since their roms take advancements from XDA developers and then they incorporate it into their roms...
nosympathy said:
yeah, if you go on their forums all they do is flame XDA left and right. But I find it funny since their roms take advancements from XDA developers and then they incorporate it into their roms...
Click to expand...
Click to collapse
See that's what I thought, but wasn't sure
Sent from my ADR6300 using XDA Premium App
Yes Clockwork 3.0.2.4 is borked on Thunderbolt. I've been helping people on AndIRC's thunderbolt channel all day. Install 3.0.2.2, it's given me no problems.
jgrimberg1979 said:
Can you help me out and provide it because right now i cant even boot
Click to expand...
Click to collapse
I ran into the same problem. I tried to do a restore and got stuck. I used an sd card reader and put the 3rd file from the root thread PG05IMG.zip on the root of my sd card. I then put the card back in. Rebooted into recovery holding the volume down and the power button. It reflashed the file automatically and I followed the steps from 7 on to regain root. Worked for me, but now I have to start over. Hopefully they will get CWM working again. I will be much more careful about what I delete from now on. I think I will freeze it in TiBackup first to make sure everything is still working correctly. Hope this helps.
lynseyw said:
I ran into the same problem. I tried to do a restore and got stuck. I used an sd card reader and put the 3rd file from the root thread PG05IMG.zip on the root of my sd card. I then put the card back in. Rebooted into recovery holding the volume down and the power button. It reflashed the file automatically
Click to expand...
Click to collapse
This is the exact procedure I used when the same thing happened on my N1
i added the recovery.img i used to OP with instructions for those stuck in recovery or bootloader.
jeffnucci said:
Yes Clockwork 3.0.2.4 is borked on Thunderbolt. I've been helping people on AndIRC's thunderbolt channel all day. Install 3.0.2.2, it's given me no problems.
Click to expand...
Click to collapse
Latest Rom manager is 3.0.1.3 sorry if I am missing something I am a bit of a clockwork noob.
Sent from my ADR6400L using XDA App
miketoasty said:
Latest Rom manager is 3.0.1.3 sorry if I am missing something I am a bit of a clockwork noob.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Newest Rom Manager is 3.0.1.3 but the newest ClockworkMod Recovery for the tbolt is 3.0.2.4
Under flash clockworkmod recovery it stats the current and latest recovery.
My battery died and am in the same position. Got an expensive paperweight at the moment. I'll try to get another battery today and give this a try. After fooling around with it last night, the computer wouldn't even recognize the phone. Ughh!
RafficaX said:
Newest Rom Manager is 3.0.1.3 but the newest ClockworkMod Recovery for the tbolt is 3.0.2.4
Under flash clockworkmod recovery it stats the current and latest recovery.
Click to expand...
Click to collapse
Good call just checked and 3.2 does wipe date and cache properly.
Sent from my ADR6400L using XDA App
miketoasty said:
Good call just checked and 3.2 does wipe date and cache properly.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Where did you get 3.2? 3.0.2 you mean?
My computer is down and TWRP seems stuck in recovery mode? possibly. Every time I try to flash a ROM TWRP just reboots itself. I'm able to backup and restore fine but cannot flash. I'm running dualboot bootloader if that matters.
Is there a way to check what mode it is in via terminal and also change it?
Any help would be greatly appreciated.
http://m.youtube.com/#/watch?desktop_uri=/watch?v=2u5Dav9beuk&v=2u5Dav9beuk&gl=US
Sent from my Amazon Kindle Fire using XDA
freefaling said:
http://m.youtube.com/#/watch?desktop_uri=/watch?v=2u5Dav9beuk&v=2u5Dav9beuk&gl=US
Sent from my Amazon Kindle Fire using XDA
Click to expand...
Click to collapse
I know how to flash via terminal. I need to know of you can change boot mode via terminal. I already tried flashing the recovery over top of it but I still cannot flash a new ROM. (The tablet boots up fine, fyi)
Sent from my Nexus One using xda premium
uoY_redruM said:
I know how to flash via terminal. I need to know of you can change boot mode via terminal. I already tried flashing the recovery over top of it but I still cannot flash a new ROM. (The tablet boots up fine, fyi)
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
If you can flash twrp 2.1.1, then you can boot into your rom from twrp. It used to have a bug where it would not change bootmode. I believe it is now fixed with v2.1.1.
Hope it helps.
Sent from my Amazon Kindle Fire using XDA
freefaling said:
If you can flash twrp 2.1.1, then you can boot into your rom from twrp. It used to have a bug where it would not change bootmode. I believe it is now fixed with v2.1.1.
Hope it helps.
Sent from my Amazon Kindle Fire using XDA
Click to expand...
Click to collapse
I flashed 2.1.1 with success but still was unable to flash a ROM. To top it off, I clicked the "reset boot loader" option and now my Kindle is stuck on the dual-boot boot loader screen and will not respond or go further....
Sent from my Nexus One using xda premium
uoY_redruM said:
I flashed 2.1.1 with success but still was unable to flash a ROM. To top it off, I clicked the "reset boot loader" option and now my Kindle is stuck on the dual-boot boot loader screen and will not respond or go further....
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=943772&d=1331571368
Someone (user:b63) over at the firefirefire thread posted this handy file explaining how to change bootmodes via command line. Try it.
Sent from my Amazon Kindle Fire using XDA
freefaling said:
http://forum.xda-developers.com/attachment.php?attachmentid=943772&d=1331571368
Someone (user:b63) over at the firefirefire thread posted this handy file explaining how to change bootmodes via command line. Try it.
Sent from my Amazon Kindle Fire using XDA
Click to expand...
Click to collapse
Would love to but now I'm stuck and cannot even boot.
Sent from my Nexus One using xda premium
uoY_redruM said:
Would love to but now I'm stuck and cannot even boot.
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
your in fastboot. who reboots to bootloader not knowing what it does?
u need a PC now for sure.
why it won't flash, is beyond me tho.
Sent from my HTC Glacier using xda premium
smirkis said:
your in fastboot. who reboots to bootloader not knowing what it does?
u need a PC now for sure.
why it won't flash, is beyond me tho.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Yeah it was a stupid move, I was just getting frustrated with it not flashing ROMs all of a sudden and I just started trying random ****. Waiting for my friend and his laptop now.
Sent from my Nexus One using xda premium
Maybe this can help?
http://forum.xda-developers.com/showpost.php?p=22619437&postcount=5
Type this in terminal emulator:
Su
Oem idme bootmode 4000
FINALLY! Damn, his laptop was being defiant and didn't want to install the fastboot drivers. Was starting to piss me off, but an hour later and I got it going!
I had to run
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
I haven't tried to flash a new ROM yet, I don't even care at this point, happy the Kindle is back up. Now time to try and get ROMs to flash...
OK so I reset my partition to stock, flashed the latest FFF (replacing the dual-boot bootloader) and flashed the latest TWRP 2.1.1 and it still failed to flash ANY ROM. I reverted to TWRP 2.0 again and tried and it didn't fail...yet. It started the flashing process but I'm not sure it'll complete (been flashing for about 5 minutes now and has not completed). Really not sure what the deal is with flash failing. This never happened before.
EDIT-
Nope, goes...
Formatting /cache...
Formatting /cache...
Formatting /cache...
E:Unable to open zip file.
hi,getting trouble booting to recovery,it worked first time to install PA but now im trying to install franco kernel but im just getting blank screen,ive tried teamwin now im trying on rom manager with no luck,any ideas
Terminal emulator - reboot recovery.
Adb - adb reboot recovery
You may need to install your recovery again. Sounds like something is borked.
ROM manager doesnt use TWRP.
TWRP uses goo manager.
zephiK said:
ROM manager doesnt use TWRP.
TWRP uses goo manager.
Click to expand...
Click to collapse
Absolutely. I think he is just trying to boot to recovery, though.
estallings15 said:
Terminal emulator - reboot recovery.
Adb - adb reboot recovery
You may need to install your recovery again. Sounds like something is borked.
Click to expand...
Click to collapse
cheers,i will go back to toolkit
estallings15 said:
Absolutely. I think he is just trying to boot to recovery, though.
Click to expand...
Click to collapse
well I'm not sure if ROM manager can boot to recovery (i know its the same command, but it may respond weirdly as ROM Manager is CWR) and generally speaking. you shouldnt be using ROM Manager with TWRP, it can lead to bad things. Not saying that it would, but I'd proceed with caution.
tonybhoy said:
cheers,i will go back to toolkit
Click to expand...
Click to collapse
Using toolkits will get you out of a jam here and there, but you won't learn anything. Get rid of the toolkit and use adb and fastboot. You'll be glad you did.
estallings15 said:
Using toolkits will get you out of a jam here and there, but you won't learn anything. Get rid of the toolkit and use adb and fastboot. You'll be glad you did.
Click to expand...
Click to collapse
+1 especially when you're having troubles in the first place. just figure it out, it's not very difficult so you will know how to resolve issues in the near future and not have to rely on the XDA forums to fix a simple problem.
I have a Nexus 7 wifi, It is stuck at the Google screen boot looping. It is unlocked and has TWRP 2.5 which I can access. I have tried every tool kit to no avail. Need some help please!
dont use a toolkit
get to a command line and figure out whats wrong by trying to flash a factory image, or run factory reset in recovery and see if it fixes it.
Pirateghost said:
dont use a toolkit
get to a command line and figure out whats wrong by trying to flash a factory image, or run factory reset in recovery and see if it fixes it.
Click to expand...
Click to collapse
I tried factory reset but it fails. I tried to flash a factory image through side load but it fails.
If I go to advanced wipe and do them one at a time they all work except data.
It appears to have nothing on intrenal or external storage.
One other thing is when I try to mount the system in twrp it asks for a password?
I have never setup a password so I don't understand this.
Thanks
Did you encrypt your device?
Sent from my Galaxy Nexus
No, not at all that's what's so strange.
I purchased it new and it started locking up and after an attempted factory reset here we are.
Sent from my SCH-I605 using xda app-developers app
Factory reset would wipe data partition leaving nothing in data. Makes sense that it wouldnt let you wipe that when there is nothing there.
Try flashing a factory image from fast boot. Not from recovery.
Sent from my Galaxy Nexus
Would it not have to be loaded on the device? I tried it with a tool kit and it gets to the end and fails on verification.
I don't remember what version it was so that doesn't help. I think it was 4.1.2
But not positive.
Sent from my SCH-I605 using xda app-developers app
Pirateghost said:
Factory reset would wipe data partition leaving nothing in data. Makes sense that it wouldnt let you wipe that when there is nothing there.
Try flashing a factory image from fast boot. Not from recovery.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Okay seems to be a problem with twrp 2.5 as far as the password I'm downloading 2.6 now.
Use fastboot to flash new recovery and system partition. You run fastboot commands from your computer not from recovery and your device needs to be in bootloader not recovery. It does not require you to load it onto the device prior
Sent from my Galaxy Nexus
Pirateghost said:
Use fastboot to flash new recovery and system partition. You run fastboot commands from your computer not from recovery and your device needs to be in bootloader not recovery. It does not require you to load it onto the device prior
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
After reading more I decided to go with CWM for the recovery. I flashed it in fast boot and it works fine but what now?
Thanks for your time!
ugadawg67 said:
After reading more I decided to go with CWM for the recovery. I flashed it in fast boot and it works fine but what now?
Thanks for your time!
Click to expand...
Click to collapse
personally i would flash a stock system image in fastboot, root it, and use it....or pick from the hundreds of ROMs available around here.
Pirateghost said:
personally i would flash a stock system image in fastboot, root it, and use it....or pick from the hundreds of ROMs available around here.
Click to expand...
Click to collapse
What would I use to flash the stock image in fast boot? a toolkit? I have the stock img downloaded already.
ugadawg67 said:
What would I use to flash the stock image in fast boot? a toolkit? I have the stock img downloaded already.
Click to expand...
Click to collapse
you dont need a toolkit
you use fastboot command to flash.....
Pirateghost said:
you dont need a toolkit
you use fastboot command to flash.....
Click to expand...
Click to collapse
Sorry I need a little more help with that. Are you talking about from a command prompt?
Sent from my SCH-I605 using xda app-developers app
you need to do some reading
http://forum.xda-developers.com/showthread.php?t=1907796
Pirateghost said:
you need to do some reading
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
thanks!
okay I removed my sdk folder and started over. I followed the instructions on the link and it says failed cannot load bootloader. It performs all commands until that one.
Any ideas what I'm doing wrong?
Sent from my Galaxy Note 2 using xda app-developers app
Pirateghost said:
you need to do some reading
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
okay I removed my sdk folder and started over. I followed the instructions on the link and it says failed cannot load bootloader. It performs all commands until that one.
Any ideas what I'm doing wrong?
Sent from my SCH-I605 using xda app-developers app
So a while back I went through the process to root my phone and went with safestrap. Now it appears the new roms aren't compatible with safestrap (is it because of 4.3 gapps?).
How would I go about switching over to CWM? Is there anything fancy? Is there a guide? Any help appreciated.
Thank You.
Is your boot loader unlocked?
If so, flash CWM through fastboot (there are a few guides on XDA of how to do so). Flashing a new ROM through CWM will remove safestrap.
Sent from my XT907 using xda premium
Leraeniesh said:
Is your boot loader unlocked?
If so, flash CWM through fastboot (there are a few guides on XDA of how to do so). Flashing a new ROM through CWM will remove safestrap.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
Yes unlocked. I will look it up. Thanks.
I believe you can also use backups made in Safestrap in TWRP (/data/ only)
Sent from my XT907 using xda premium
You'll need to uninstall recovery through the actual SafeStrap app. Then, you'll need to delete the app and all the SS folders.
So I am getting the "cannot load cwm.img" on the command prompt.
cwm.img is in the same folder as fastboot and adb.
not sure what is up. Currently searching for solution....
EDIT: Typed full path. Seems to have worked....
RikRong said:
You'll need to uninstall recovery through the actual SafeStrap app. Then, you'll need to delete the app and all the SS folders.
Click to expand...
Click to collapse
Booted back into safestrap. I'm assuming this is why?
jagsfan82 said:
Booted back into safestrap. I'm assuming this is why?
Click to expand...
Click to collapse
Yep that's why. SafeStrap works seperate from your recovery. If you actually boot into recovery do you get CWM? If not, you'll probably need to re-flash it. When you re-flash, boot back into recovery prior to booting into OS. This will assure that the install script is complete. Otherwise, your stock recovery will override CWM.
RikRong said:
Yep that's why. SafeStrap works seperate from your recovery. If you actually boot into recovery do you get CWM? If not, you'll probably need to re-flash it. When you re-flash, boot back into recovery prior to booting into OS. This will assure that the install script is complete. Otherwise, your stock recovery will override CWM.
Click to expand...
Click to collapse
Gotcha. Well I can uninstall it via a recovered system that still has safestrap on it. I did something weird trying to boot into CWM and when i start my phone it goes into the bootloader due to flash failure. I can override this with "fastboot continue", but i don't want to do something really bad... am I going to run into any issues if I get to CWM and flash a new rom?
Thanks for the help fellas
EDIT: Flash failure problem went away. Reflashed CWM, wouldn't boot via fastboot boot cwm.img, managed to get to recovery before system loaded... but still went to safestrap.. trying old fashioned SS uninstall now, then reflash, then boot into recovery.
EDIT 2: Uninstalled safestrap.. doesn't boot to bootloader now?
EDIT 3: Brought up safestrap on my eclipse rom, uninstalled safestrap. Went to bootloader. Flashed CWM supposedly successfully. Tried to run "fastboot boot cwm.img" only to get cannot load. Tried to go from bootloader to recovery manually (power button --> key press) but just loads up the OS.
Clueless now
jagsfan82 said:
Gotcha. Well I can uninstall it via a recovered system that still has safestrap on it. I did something weird trying to boot into CWM and when i start my phone it goes into the bootloader due to flash failure. I can override this with "fastboot continue", but i don't want to do something really bad... am I going to run into any issues if I get to CWM and flash a new rom?
Thanks for the help fellas
EDIT: Flash failure problem went away. Reflashed CWM, wouldn't boot via fastboot boot cwm.img, managed to get to recovery before system loaded... but still went to safestrap.. trying old fashioned SS uninstall now, then reflash, then boot into recovery.
EDIT 2: Uninstalled safestrap.. doesn't boot to bootloader now?
EDIT 3: Brought up safestrap on my eclipse rom, uninstalled safestrap. Went to bootloader. Flashed CWM supposedly successfully. Tried to run "fastboot boot cwm.img" only to get cannot load. Tried to go from bootloader to recovery manually (power button --> key press) but just loads up the OS.
Clueless now
Click to expand...
Click to collapse
Just saw your last post... too tired. You mentioned deleting the app and folders. Is this most likely the issue?
jagsfan82 said:
Just saw your last post... too tired. You mentioned deleting the app and folders. Is this most likely the issue?
Click to expand...
Click to collapse
I don't think that's the issue. Deleting the app and folders just frees up some space. I'll have re-read your other post and then I'll get back to you on it.
jagsfan82 said:
Gotcha. Well I can uninstall it via a recovered system that still has safestrap on it. I did something weird trying to boot into CWM and when i start my phone it goes into the bootloader due to flash failure. I can override this with "fastboot continue", but i don't want to do something really bad... am I going to run into any issues if I get to CWM and flash a new rom?
Thanks for the help fellas
EDIT: Flash failure problem went away. Reflashed CWM, wouldn't boot via fastboot boot cwm.img, managed to get to recovery before system loaded... but still went to safestrap.. trying old fashioned SS uninstall now, then reflash, then boot into recovery.
EDIT 2: Uninstalled safestrap.. doesn't boot to bootloader now?
EDIT 3: Brought up safestrap on my eclipse rom, uninstalled safestrap. Went to bootloader. Flashed CWM supposedly successfully. Tried to run "fastboot boot cwm.img" only to get cannot load. Tried to go from bootloader to recovery manually (power button --> key press) but just loads up the OS.
Clueless now
Click to expand...
Click to collapse
Do "fastboot flash recovery cwm.img" and open up the power menu via three button press, then select recovery.
Sent from my XT907 using xda premium
Leraeniesh said:
Do "fastboot flash recovery cwm.img" and open up the power menu via three button press, then select recovery.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
This is more or less what I did except the only difference is I hit power first, phone went off, then quickly did keypress. Went strait to OS.
Seriously appreciate help btw
RikRong said:
I don't think that's the issue. Deleting the app and folders just frees up some space. I'll have re-read your other post and then I'll get back to you on it.
Click to expand...
Click to collapse
My first thought is I need to strip down the system.. maybe i didn't wipe something properly or what have you.
jagsfan82 said:
This is more or less what I did except the only difference is I hit power first, phone went off, then quickly did keypress. Went strait to OS.
Seriously appreciate help btw
Click to expand...
Click to collapse
Yeah unfortunately there's no command to boot recovery from fastboot.
You can try running "fastboot reboot" while holding the volume buttons right after flashing cwm. That should do the trick. It should boot to the boot selection menu, then you can choose to boot to recovery.
Also, thought you killed yourself when I read your other post...
fastboot boot cwm.img is one argument away from a very, very bad day... If you put "flash" before boot, you'd be in trouble... Lol
Maybe I should write up a root app that will rename install-recovery.sh... That's not a bad idea...
Sent from my XT907 using Tapatalk
I always just power down the phone after flashing recovery and then manually reboot into recovery.
And done. Here's a link...
ftp://kd8rho.net/RecoveryFlasherDisabler-public-test.apk
I forgot to declare superuser in the manifest... I know, shoot me. Needs root access and all that jazz. Run the app before flashing recovery
Oh and rikrong, stole your avatar for the app icon
Sent from my XT907 using Tapatalk
sloosecannon said:
And done. Here's a link...
ftp://kd8rho.net/RecoveryFlasherDisabler-public-test.apk
I forgot to declare superuser in the manifest... I know, shoot me. Needs root access and all that jazz. Run the app before flashing recovery
Oh and rikrong, stole your avatar for the app icon
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Haha, nice.
RikRong said:
Haha, nice.
Click to expand...
Click to collapse
Thankee
So, if someone on stock who wants to flash custom recovery could test this, that would be great. It should work, but as I have no stock RAZR Ms, I can't confirm it will work
Sent from my XT907 using Tapatalk
sloosecannon said:
Thankee
So, if someone on stock who wants to flash custom recovery could test this, that would be great. It should work, but as I have no stock RAZR Ms, I can't confirm it will work
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Installed on phone. Says found but disabled. Tried flashing cwm.img and rebooting into recovery. Still goes straight to OS...
Enable install-recovery doesn't work
this all seems very straightforward of a process that should be working...
Do I need to try wiping everything down as bare as possible?
Is this the process that works for others? Take safestrapped, rooted, bootloader unlock device on an old pre-bootloader-unlocked rom. Uninstall safestrap. Flash cwm.img using fastboot comand. Boot into recovery. Then you should be in CWM?