Related
Green lens Defy, UK Unbranded. I've tried everything.
Tried these SBF:
JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_USAJORDANRTGB_P026_A007_HWp3_Service1FF
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P019_A010_HWp3_Service1FF.sbf
With these:
update-cm-7.1.0-11-Defy-signed
update-cm-7.1.0-jordan-signed
CM72-20120304-NIGHTLY-Defy
Done eveything in this link: http://forum.xda-developers.com/showpost.php?p=24119414&postcount=12
Whats going wrong? Been at it hours now, and this is not the 1st Defy I've done!
I did make a backup shortly after flashing the 1st SBF, and can still get back on to the standard ROM. But I want CM7.
All help appreciated.
Re flash this sbf
joey_t said:
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P019_A010_HWp3_Service1FF.sbf
With these:
update-cm-7.1.0-11-Defy-signed
update-cm-7.1.0-jordan-signed
CM72-20120304-NIGHTLY-Defy
Click to expand...
Click to collapse
Then follow your link with volume down battery in, wipe data / factory reset,
Then root it with super one click
Then reboot
Then install 2nd init via instructions
Then flash cm7.1 stable
But once you get back into the standard moto software take a while and read the beginners guides
teamwork makes the dream work
Thanks, I appreciate the help.
However, its basically what I already did, but did it again anyway, and same result.
Getting stuck on the blue cyanogen screen. It must be CM7 file, although these are all the same files I'm using from my first sucessful installation.
I remember being stuck at the same point, but not sure how I resolved it.
Do you know if it would be OK to make a backup of the CM7 from my working phone, and install it on this other Defy?
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Edit: OK, tried my last suggestion. Not good. Have a working CM7, but no signal, when I check the IMEI on the phone using *#06#, it shows as all zero's, which may explain the problem.
joey_t said:
Green lens Defy, UK Unbranded. I've tried everything.
Tried these SBF:
JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_USAJORDANRTGB_P026_A007_HWp3_Service1FF
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P019_A010_HWp3_Service1FF.sbf
With these:
update-cm-7.1.0-11-Defy-signed
update-cm-7.1.0-jordan-signed
CM72-20120304-NIGHTLY-Defy
Done eveything in this link: http://forum.xda-developers.com/showpost.php?p=24119414&postcount=12
Whats going wrong? Been at it hours now, and this is not the 1st Defy I've done!
I did make a backup shortly after flashing the 1st SBF, and can still get back on to the standard ROM. But I want CM7.
All help appreciated.
Click to expand...
Click to collapse
joey_t said:
Thanks, I appreciate the help.
However, its basically what I already did, but did it again anyway, and same result.
Getting stuck on the blue cyanogen screen. It must be CM7 file, although these are all the same files I'm using from my first sucessful installation.
I remember being stuck at the same point, but not sure how I resolved it.
Do you know if it would be OK to make a backup of the CM7 from my working phone, and install it on this other Defy?
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Edit: OK, tried my last suggestion. Not good. Have a working CM7, but no signal, when I check the IMEI on the phone using *#06#, it shows as all zero's, which may explain the problem.
Click to expand...
Click to collapse
Try baseband switcher app which is in CM itself and try switching to your region
Strictly follow these steps:
INSTRUCTIONS:
1. Flash froyo (SBF using RSD lite)
2. Copy *.zip to sdcard
3. Reboot your device in BootMenu/ClockWork
4. WIPE (wipe data/factory reset + wipe cache partition)
5. Install the *zip
6. reboot
Refer to the following article for more information:
http://forum.xda-developers.com/showthread.php?t=1033654
Hope this helps!
joey_t said:
Thanks, I appreciate the help.
However, its basically what I already did, but did it again anyway, and same result.
Getting stuck on the blue cyanogen screen. It must be CM7 file, although these are all the same files I'm using from my first sucessful installation.
I remember being stuck at the same point, but not sure how I resolved it.
Do you know if it would be OK to make a backup of the CM7 from my working phone, and install it on this other Defy?
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Edit: OK, tried my last suggestion. Not good. Have a working CM7, but no signal, when I check the IMEI on the phone using *#06#, it shows as all zero's, which may explain the problem.
Click to expand...
Click to collapse
Hold on the above post for a minute,
Enter boot menu,
Go stable recovery,
Wipe data,
Wipe cache,
Wipe dalvik(under advanced)
The rom should boot easy,
Then use baseband switcher (some cm have it installed) choose the frequency to work with your phone ie if the phone was for 850/2100 use a 850/2100 baseband
teamwork makes the dream work
adamo3957 said:
teamwork makes the dream work
Click to expand...
Click to collapse
Well said!!
Thanks for the replies guys. However, I just flashed the standard SBF again after the blank IMEI issue. So back to square one again.
Are you both suggesting I should use the backup ROM from my other phone, then use the baseband switcher to get the signal back?
If so that would be much easier, as I know my backup ROM works fine.
joey_t said:
Thanks for the replies guys. However, I just flashed the standard SBF again after the blank IMEI issue. So back to square one again.
Are you both suggesting I should use the backup ROM from my other phone, then use the baseband switcher to get the signal back?
If so that would be much easier, as I know my backup ROM works fine.
Click to expand...
Click to collapse
That would work fine as long as you are using froyo kernel for both, so my suggestion is this
Root
Install 2nd init
Go to recovery on you working cm defy and back up everything (cache data system boot recovery and only leave pds, )
Copy the images to your blank factory defy,
Restore all Tue images you just made - remember no pds,
Should boot 1st go
Then if your doing it for someone else re enter recovery and wipe data,
All this is done via the 2nd init recovery
teamwork makes the dream work
Thanks, once again I appreiciate your help, just a couple of things in your last set of instructions:
1. Whats pds? Can't see an option to leave that.
2. Tue images?
Edit:
Ok should have at least looked into PDs before I asked.
But Tue images? Still not sure on that.
1st backup off working phone, excluding pds hasn't changed. For some reason, it saying it cannot find system.img, andriod_secure.img and cache.img. But I only copied over the clockworkmod backup folder. I think I saw the android_secure folder elsewhere, so will go back on that.
OK contents of backup folder from working cm7 defy are:
.android_secure.vfat.tar
boot.img
cache.ext3.tar
data.ext3.tar
devtree.img
nadroid.md5
recovery.img
system.ext3.tar
There is no system.img, android_secure.img and cache.img on this folder, hence why the restore cannot find those files.
I'm checking versions of clockworkmod recovery are the same on both phones, thats the only thing I can think is making it different. Checked, same versions.
I seem to be having more sucess, trying my install of cm7, where it gets to the blue logo screen, then running the restore. However, still no signal. I don't seem to have the baseband switcher option in my version. Any direct links to the latest cm7 build, as the one on the link from Rajneeshgadge17, is down.
SUCCESS!
Thanks for your patience adamo3957 and Rajneeshgadge17.
I eventually went for a complete fresh install of everything, downloading the same version of cm7 I already had even, just to check that. Now up and running :thumb:
Now, I just need to sort the other Defy I killed when atempting the macguyver fix!
Download CM7.1.0 from below mentioned link:
http://download.cyanogenmod.com/?type=stable&device=umts_jordan
Follow the same steps as mentioned in the above article ans share the results.
INSTRUCTIONS:
1. Flash froyo
2. Copy *.zip to sdcard
3. Reboot your device in BootMenu/ClockWork
4. WIPE (wipe data/factory reset + wipe cache partition)
5. Install the *zip
6. reboot
Click to expand...
Click to collapse
joey_t said:
SUCCESS!
Thanks for your patience adamo3957 and Rajneeshgadge17.
I eventually went for a complete fresh install of everything, downloading the same version of cm7 I already had even, just to check that. Now up and running :thumb:
Now, I just need to sort the other Defy I killed when atempting the macguyver fix!
Click to expand...
Click to collapse
Just noticed your post now
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Did you wipe data and cache when you flashed the new rom?
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you
chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik
nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.
Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app
Hi there, I'm new to the forum but have been rooting for about a year. Here is my problem...
I was running stock firmware on my SGS3 and went through the standard cm10 root/rom install process. I flashed CMW with Odin, booted to recovery, installed cm10, jb gapps, cleared cache and delvik cache and rebooted. All the above processes worked fine and once it boots into JB, nothing seems to work. My home button does nothing, the top status bar is blank, no wifi, no keyboard (the process just crashes when I attempt to type).
I know this isn't an issue with CM10 on the SGS3 as this works for most people but does anyone have any ideas on how to remedy this? This may be a unique issue as I can't seem to find anyone else experiencing this.
Also...
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Coming from stock you need to fully wipe.
Sent from my SAMSUNG-SGH-I747 using xda premium
Machoscrawn said:
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Click to expand...
Click to collapse
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
dynamiclynk said:
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. This is what I did...
(Main cwm menu) -wipe cache partition
(Advanced) -wipe dalvik cache
+++go back+++
-reboot system now
Is there something additional I should clear?
Kweli87 said:
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
Click to expand...
Click to collapse
Thanks for the reply,
How do i update to the latest clockworkMod? Do you happen to have a URL? I think I found the latest 6.something, but they all seem to be in .iso format.
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
i386W7 said:
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
Click to expand...
Click to collapse
Sorry I may have missed mentioning that. The first thing I did was the -factory restore/reset
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
goodtimes50 said:
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
Click to expand...
Click to collapse
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
BAM1789 said:
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
Click to expand...
Click to collapse
Ok thanks! I'm going to give that a shot and see how it goes.
Machoscrawn said:
Ok thanks! I'm going to give that a shot and see how it goes.
Click to expand...
Click to collapse
Ok so I tried flashing a stock rooted ICS ROM and now I'm stuck on the Samsung logo boot screen. Here is the method I tried, using Odin. http://forum.xda-developers.com/showthread.php?t=1739426
I used the "Bell Image (This works with Canadian Virgin Mobile SGH-I747M) - Old Image I747MVLALH1 (ICS 4.0.4)"
After flashing I booted into the stock recovery and cleared the cache partition then rebooted. Still stuck on the Samsung boot screen.
UPDATE: I just let it sit on the Samsung logo boot screen and it eventually loaded into ICS.
Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
goodtimes50 said:
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
Click to expand...
Click to collapse
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Machoscrawn said:
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Click to expand...
Click to collapse
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
wally3614 said:
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
Click to expand...
Click to collapse
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Machoscrawn said:
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Click to expand...
Click to collapse
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
wally3614 said:
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
Click to expand...
Click to collapse
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Machoscrawn said:
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Click to expand...
Click to collapse
If youre looking to completely start over. Just grab an unrooted stock .tar from one of the links somewhere around here, put your phone in download mode and let it flash. Clean slate.
THIS IS FOR XT907
I decided to start this post for those who encounter issues while flashing. Whether you had trouble flashing your first custom ROM from stock, whether you even had issues trying to get root, whether you had trouble flashing the next custom ROM/update from an existing custom ROM, or whether you have had the Safestrap splashscreen but the softkeys weren't working (like me)..
It's a painful task to RSD everytime you want to make a small change, and it's an even more painful quest to search for every unique case we fall into.. so I would be hoping that everyone could give their input, and maybe help compile a How-to right here, from obtaining root, to installing safestrap and all the way up to flashing a custom ROM. Also following that up with more advanced troubleshooting ie my issues with the safestrap softkeys not working..
I'm going to post up what most other people have posted up, general instructions on how to install a custom ROM.. and also a few handy tips.. in case you ever get bricked.
STUFF YOU WILL NEED:
BACKUP OF JELLYBEAN 4.1.1 FIRMWARE FOR THE M
TO FLASH FIRMWARE INCASE YOU GET BRICKED: RSD LITE (google this and get the latest version of RSD LITE - it's late and I'm actually flashing an UPDATE for Eclipse the long way cuz my softkeys for Safestrap aren't working)
TO OBTAIN ROOT: MOTOFAIL2GO
TO FLASH ROMS: SAFESTRAP RECOVERY
and ROMs of your choice from any of the ROM threads
STEPS courtesy of AndroidJunkies' instructions:
You need to be rooted and have a custom recovery installed on your RAZR M to be able to install this ROM.
You can use this guide to Root your RAZR M and Install Safestrap Recovery
Get the latest version of THE ROM OF YOUR CHOICE from xda forums or other forums of your choice.
Connect your Droid RAZR M to the computer and transfer the downloaded ROM zip file from Step 2 to the SDcard on your device
Now disconnect your RAZR M We need to boot to Safestrap recovery now, To do that open the Safestrap app on your device and use the Reboot to recovery option
At the splash screen, choose recovery to boot into Safestrap. You need to select the option within 10 seconds, to avoid booting back in to the normal OS
The top of the screen should show “Safestrap System is: Disabled” (that is what we want right now and is also referred to as “Non-Safe mode”).
Make a back up of your existing ROM within recovery, Wait for the backup to complete, it might take a few minutes.
In the Safestrap recovery menu, navigate to and enter the Safe Boot Menu and Select Enable Safe System. Wait a few minutes for Safestrap to finish backing up the necessary system files.
Now from the recovery main menu, scroll to Wipe Data /Factory Reset and select it. Confirm wipe in the next step. This could take a few minutes, so don’t panic and be patient.
Once that’s done, select Wipe Cache from the main menu, and confirm it in the next step.
Next, select Mounts and Storage from the main menu and then select Format /system. Don’t worry. Your primary system partition will be untouched.
Once the format is complete go back to the main menu and select Advanced, and from the next screen select Wipe Dalvik Cache
Go back to the main menu and Select Install zip from SD card. Select the Eclipse RAZR M ROM zip file you had transferred to the SDcard in Step 3, and confirm the flash on the next screen
Wait for the ROM flash to complete. Once finished, reboot your device.
For best results, leave the device alone for at least 5-10 minutes after the first boot and let the new ROM settle in. While this may seem unnecessary, it usually prevents issues like inexplicable force closes later
AT ANY POINT IN TIME you get stuck - here are a few handy tips..
TO POWER DOWN: HOLD Power + Vol Up + Vol Down
TO ENTER BOOTLOADER (to choose boot in recovery, fastboot etc) : when phone is off, HOLD Power + Vol Up + Vol Down
TO RESET: HOLD Power + Vol Down
If you ever get bricked, try to enter bootloader, select recovery (THIS IS THE STOCK RECOVERY and when you see the dead android, with the red exclamation mark. The ONLY thing you can press to obtain a response is something like hold Vol Up + Vol Down (what I did was that and when it didn't work I just spammed..)
it's late and it'll take awhile for me to finish this up - but guys please feel free to contribute, I'll update the OP - I'm sure many will benefit from this. As for me I've one last question
honestly, was there an easy way/quick fix when my Safestrap was enabled and I couldn't press the softkeys? I read somewhere that I could disable safestrap.. did not know how to and ended up uninstalling recovery..
then got into a bootloop - so I RSD'd and RE FLASHED everything. painful yeah - this thread is dedicated to those who do not want to go through the trouble I did..
SPECIAL THANKS to
androidjunkies.com
madrao from androidevolved.com
thanks for putting this together. wondering if we have to put the ROM on the "/sdcard" vs. the "mnt/external1" folder. I believe the system (at least on my device) has the "/sdcard" actually stored in the phone's memory, and not the memory card. this is the problem I ran into when using safestrap last time (ran low on memory).
jco23 said:
thanks for putting this together. wondering if we have to put the ROM on the "/sdcard" vs. the "mnt/external1" folder. I believe the system (at least on my device) has the "/sdcard" actually stored in the phone's memory, and not the memory card. this is the problem I ran into when using safestrap last time (ran low on memory).
Click to expand...
Click to collapse
paste it on /sdcard which is the phone's memory, my ext sd is /sdcard1
Sent from my XT907 using xda premium
safestrap installed but not usable
I have a system version 98.12.4 on my razr m. I've used motofail2go to get root. Installed safestrap with es file explorer.
When opening app safestrap I have(recovery state: installed) and (safe system: not active). There are no boot options, just install or uninstall and the version 3.12
I power down as normal and boot holding vol+- getting to the boot selection menu 10.9b.
Pressing vol- to select BP TOOLS vol+ to enter and I end up with this unusually formatted form of safestrap which is unusable.
I've even flashed back to stock and gone through the process again to the same result.
Any ideas?
gdubb360 said:
I have a system version 98.12.4 on my razr m. I've used motofail2go to get root. Installed safestrap with es file explorer.
When opening app safestrap I have(recovery state: installed) and (safe system: not active). There are no boot options, just install or uninstall and the version 3.12
I power down as normal and boot holding vol+- getting to the boot selection menu 10.9b.
Pressing vol- to select BP TOOLS vol+ to enter and I end up with this unusually formatted form of safestrap which is unusable.
I've even flashed back to stock and gone through the process again to the same result.
Any ideas?
Click to expand...
Click to collapse
you dont have v3.12, thats the only one that worked for me, your SS is showing 3.11
jfletch86 said:
you dont have v3.12, thats the only one that worked for me, your SS is showing 3.11
Click to expand...
Click to collapse
Strange I know, inside the wrongly formatted recovery it says 3.11. Inside of the app it has a version # 3.12. I downloaded from the link at the top of this page.
---------- Post added at 12:51 PM ---------- Previous post was at 12:00 PM ----------
Alright so I found a new download specific to our device. The download in the original post was not working for me - not sure if it's because it was for the razr hd.
Inside safestrap it still gives v3.11 but everything seems to be normal so far for me.
safestrap razr m download:
(apparently not enough posts to put up a link) but if you visit the Hash-of-Codes website there is a download specific for the m.
Previously used this site to root and put CM10 on my old X2, which has since passed on to the next world due to one too many times being dropped....
Trying this process now, hoping it all works out. I'm going to try the energy ROM on for size.
Can't boot to Eclipse?
Thanks to the OP for providing his guide. It was very helpful, and has gotten my 99% of the way there....
I have a Razr M that I recently rooted. I installed the newest version of safestrap (3.12) from HOC's website. I'm successfully able to enter recovery, create a partition, format/wipe it, and install Eclipse.
Everything seems fine at first when I reboot; I get the safestrap screen showing that it's activated. Once I continue the boot process, though, the phone just seems to freeze on a blank screen, without ever displaying a splash screen. I've waited over 5 minutes with nothing happening (several times I've tried this). Using the PWR+VolUp+VolDown button combo I'm able to restart the phone and enter recovery. Stock ROM still works.
I've tried wiping caches, to no avail. Any ideas out there?
Good stuff
This is very helpful. I wish I had known all of this stuff before I started on my M. something I have done that I am not sure will work on all ROMs, so be careful.
For the Eclipse rom, I installed it on a new rom slot, then backed it up. I then restored the Eclipse backup over the stock slot. I would recommend backing up stock first.
P.S. I am not sure if this will work with every rom. Only tried with Eclipse!
AndroidAardvark said:
Thanks to the OP for providing his guide. It was very helpful, and has gotten my 99% of the way there....
I have a Razr M that I recently rooted. I installed the newest version of safestrap (3.12) from HOC's website. I'm successfully able to enter recovery, create a partition, format/wipe it, and install Eclipse.
Everything seems fine at first when I reboot; I get the safestrap screen showing that it's activated. Once I continue the boot process, though, the phone just seems to freeze on a blank screen, without ever displaying a splash screen. I've waited over 5 minutes with nothing happening (several times I've tried this). Using the PWR+VolUp+VolDown button combo I'm able to restart the phone and enter recovery. Stock ROM still works.
I've tried wiping caches, to no avail. Any ideas out there?
Click to expand...
Click to collapse
Sounds like a bad download and/or flash. I would wipe ROM slot 1, re-format and re-install a newly downloaded version of Eclipse.
So i finally got safestrap 3.11 for M and i was able to backup my Stock slot, then create one on slot 1. When i go to select a zip to install the zip will not show up. I downloaded eclipse twice and it wont install because the zip wont even show up. I cleared everything on stock partition like factory resetand cache, ect. How can i get the zip to show up to install? Thanks in advance guys
kpsullzz said:
So i finally got safestrap 3.11 for M and i was able to backup my Stock slot, then create one on slot 1. When i go to select a zip to install the zip will not show up. I downloaded eclipse twice and it wont install because the zip wont even show up. I cleared everything on stock partition like factory resetand cache, ect. How can i get the zip to show up to install? Thanks in advance guys
Click to expand...
Click to collapse
Hopefully, you didn't wipe system on your stock slot. If you did, you no longer have an OS installed. When you set up a ROM slot, you don't need to wipe stock. You only need to wipe your custom slot. If you wiped stock, you'll need to fast boot back to stock.
If everything is OK, then you can flash Eclipse on ROM slot 1. You have to choose external SD in SS. The zip won't just magically appear.
Sent from my Baked GT-P3113
No I made sure I didn't wipe stock system partition just factory reset and cleared cache and dalvick sorry. Then I activate slot 1 clear all of that and go to root of SD card and the zip doesn't show. Then I put it in TWRP folder to experiment and still no dice. No idea
Edit. Could it be the SD card? I navigate to device /storage/sdcard1 and it doesn't show anything no folders or anything but if I use es explorer I can navigate to the zip just fine so weird. I even just tried putting a .zip on the end but no go.
Sent from my XT907 using xda app-developers app
RikRong said:
Hopefully, you didn't wipe system on your stock slot. If you did, you no longer have an OS installed. When you set up a ROM slot, you don't need to wipe stock. You only need to wipe your custom slot. If you wiped stock, you'll need to fast boot back to stock.
If everything is OK, then you can flash Eclipse on ROM slot 1. You have to choose external SD in SS. The zip won't just magically appear.
Sent from my Baked GT-P3113
Click to expand...
Click to collapse
Solved. The two settings that say use internal SD or use external SD I used use internal SD card then went to device/ external SD. Odd but it worked and eclipse magically showed up. Thankyou
Sent from my XT907 using xda app-developers app
kpsullzz said:
Solved. The two settings that say use internal SD or use external SD I used use internal SD card then went to device/ external SD. Odd but it worked and eclipse magically showed up. Thankyou
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
It's good you figured it out. This was going to be my next suggestion.
kpsullzz said:
Solved. The two settings that say use internal SD or use external SD I used use internal SD card then went to device/ external SD. Odd but it worked and eclipse magically showed up. Thankyou
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Yep that's a ss3 known bug. Gotta select external-sd or storage/sdcard1
Sent from my XT907 using Tapatalk 2
Can you upload safestrap for droid razr m cuz when i click on the link it says system offline.
I have a question about safestrap:
I just flashed the new 4.1.2 OTA update through fastboot. I was running eclipse in rom slot 1. Now, it seems safestrap and that partition are gone. Is that so? Am I basically just left with the OTA'd stock rom on my entire phone?
That is what I would prefer, but I just want to make sure safestrap or the space it created aren't lurking anywhere
Dyelon said:
I have a question about safestrap:
I just flashed the new 4.1.2 OTA update through fastboot. I was running eclipse in rom slot 1. Now, it seems safestrap and that partition are gone. Is that so? Am I basically just left with the OTA'd stock rom on my entire phone?
That is what I would prefer, but I just want to make sure safestrap or the space it created aren't lurking anywhere
Click to expand...
Click to collapse
If you fastbooted to 4.1.2, then it should have eliminated SS, but there are probably still some folders in there. Just use a file explorer and find any "SS" or "SafeStrap" folders and eliminate them.
RikRong said:
If you fastbooted to 4.1.2, then it should have eliminated SS, but there are probably still some folders in there. Just use a file explorer and find any "SS" or "SafeStrap" folders and eliminate them.
Click to expand...
Click to collapse
Thanks a lot man
Sent from my XT907 using xda app-developers app
Last night I soft bricked my phone. At least from what i have read it is a soft brick. The phone will power up to the Samsung Galaxy s3 screen. I can also get into download mode and cwm. I am hoping this means that phone has been soft bricked.
As far as why my phone did this...I booted into cwm and i did a restore through the menu options. I'm not sure if i hit the wrong one, or what exactly happened at this point. Whatever it was loaded and i was unable to get past the gs3 screen.
I tried loading a .Tar file from a tutorial provided by "Theexcel". The tutorial was to flash the new tar onto the phone through Odin. However, in the tutorial, it says to make sure that the flash counter is set back at zero. How can i do this when my phone won't power on. I am not aware of how to reset the counter without getting an app from Playstore.
As you can see, I am new to the forum. I posted here because this seems to be a similar topic.I have ready many other instances of bricked phone. none of them seemed to match my exact scenerio. Please let me know if you have any ideas. I tried to address what i think my be wrong with the phone and some of the steps I have done to try and repair it already. I will gladly provide answers to more specific questions.
Just to clarify Tmobile Galaxy S3 (SGH-T999)
Flash counter not relevant in your case.
Factory reset through recovery should fix your issue.
Aerowinder said:
Flash counter not relevant in your case.
Factory reset through recovery should fix your issue.
Click to expand...
Click to collapse
I may have done this wrong. I think I have tried this though. home+volume up+power, this brings me to my cwm recovery. I did the full wipe and factory reset. after this it still didn't allow me past the gs3 screen. Should i somehow be using android recovery? if so, how do i get that to work again? Thanks
Weird. Try Odining a stock rom.
Aerowinder said:
Weird. Try Odining a stock rom.
Click to expand...
Click to collapse
Thanks Aero! I have tried this already as well. the file i used was T999UVALH2_T999TMBALH2_T999UVALH2_HOME.tar.md5 . I believe this is the stock 4.1.1. Also, I have just heard of md5 checked. I am not sure how to use that solely on my computer. I found a tutorial for doing it on the phone. As you know...not an option right now. I am keeping my hopes up that I don't need to send my phone off for Jtag. Like i said, i can still access cwm and download screen.
I have searched around the forum quite a bit. Do you know of any good instructions to walk me through flashing the stock rom that also includes links to the rom and gapp?
Hold on....you can get into recovery? Once in recovery you just do a factory reset? Do you have a micro SD card? Do you have a micro SD card adapter so that you can connect it to a computer?
Sent from my SGH-T999 using xda premium
Sounds like a boot loop, not a brick. Boot to recovery and wipe data then try to restart the phone.
Sent from my SGH-T999 using xda premium
707BeastMode707 said:
Hold on....you can get into recovery? Once in recovery you just do a factory reset? Do you have a micro SD card? Do you have a micro SD card adapter so that you can connect it to a computer?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I do have a card reader. Not exaclty sure where it is right now....what should I do once i have located it?
I have done the factory reset through recovery. Just to make sure i'm not misunderstanding this would be cwm? (sorry, i am still a noob!) haha
nickcross88 said:
I do have a card reader. Not exaclty sure where it is right now....what should I do once i have located it?
I have done the factory reset through recovery. Just to make sure i'm not misunderstanding this would be cwm? (sorry, i am still a noob!) haha
Click to expand...
Click to collapse
Don't worry about being a noob. Everyone on this forum is or has been a noob. You'll learn though.
Just follow these steps:
1.) Download this ROM on your computer (the latest from T-Mobile, stock rooted):
http://forum.xda-developers.com/showthread.php?t=2126679
2.) On your SD card create a designated folder for ROMs (just to make it easier to find the ROM when it comes time to flash it), then find the ROM you have just downloaded and put it in the folder you have created on the SD card
3.) Power on the phone, Boot into recovery which is also known as CWM by (volume up, home button and power button)
4.) Once in recovery do the following:
-wipe cache
-wipe dalvik cache
-wipe date/factory reset
-install zip from external SD card
-navigate to the folder where you placed the ROM in step 2 and select it and and select yes to flash it.
-when finished flashing go back to the main menu and select reboot device
(Device may take a few minutes to fully boot so let the phone sit and do its thing)
5.) When phone is booted up, go through the setup process with your email and what not.
6.) AFTER GOING THROUGH THE SETUP PROCESS, REBOOT DEVICE BACK INTO RECOVERY (CWM) AND SELECT RESTORE/BACKUP, THEN SELECT BACKUP, WHEN FINISHED REBOOT THE DEVICE
7.) AFTER YOU HAVE REBOOTED YOUR DEVICE GO TO THE PLAY STORE AND DOWNLOAD THIS APP:
https://play.google.com/store/apps/...tore/apps/details?id=com.j.y.daddy.customizer
8.) ONCE DOWNLOADED, OPEN THE APP (should ask for root permissions, hit accept) SELECT TOOLS, SELECT IMEI(S) BACKUP/RESTORE AND SELECT BACKUP.
You are now good to go, you may now flash and experiment with other ROMs. Stay away from the international s3 forum, just flash things that are meant for your S3 model, if you are not sure just ask the dev.
Sorry for the caps lock but steps 6, 7 and 8 will prevent you from major headaches. Especially 7 and 8. If you flash a ROM and your stuck on 2g/edge and your imei is zero, just download that app and open it and restore your imei. Step 6 is helpful just in case if you download a ROM and you run into your current problem you can just restore your backup and your phone will be fine.
Sent from my SGH-T999 using xda premium
If you have Odined a stock rom, how is it that you still have CWM? Did it fail? If you were able to successfully Odin a stock rom, then doing a factory reset should fix your problem.
UVALH2 is 4.0.4. http://www.sammobile.com/firmwares/1/?model=SGH-T999&pcode=TMB#firmware
Try using mrRobinson's root66 of UVDLJC. root66 is identical to the official firmware .tar file in every way except that root has been injected into the system image.
707BeastMode707 said:
Don't worry about being a noob. Everyone on this forum is or has been a noob. You'll learn though.
Just follow these steps:
1.) Download this ROM on your computer (the latest from T-Mobile, stock rooted):
http://forum.xda-developers.com/showthread.php?t=2126679
2.) On your SD card create a designated folder for ROMs (just to make it easier to find the ROM when it comes time to flash it), then find the ROM you have just downloaded and put it in the folder you have created on the SD card
3.) Power on the phone, Boot into recovery which is also known as CWM by (volume up, home button and power button)
4.) Once in recovery do the following:
-wipe cache
-wipe dalvik cache
-wipe date/factory reset
-install zip from external SD card
-navigate to the folder where you placed the ROM in step 2 and select it and and select yes to flash it.
-when finished flashing go back to the main menu and select reboot device
(Device may take a few minutes to fully boot so let the phone sit and do its thing)
5.) When phone is booted up, go through the setup process with your email and what not.
6.) AFTER GOING THROUGH THE SETUP PROCESS, REBOOT DEVICE BACK INTO RECOVERY (CWM) AND SELECT RESTORE/BACKUP, THEN SELECT BACKUP, WHEN FINISHED REBOOT THE DEVICE
7.) AFTER YOU HAVE REBOOTED YOUR DEVICE GO TO THE PLAY STORE AND DOWNLOAD THIS APP:
https://play.google.com/store/apps/...tore/apps/details?id=com.j.y.daddy.customizer
8.) ONCE DOWNLOADED, OPEN THE APP (should ask for root permissions, hit accept) SELECT TOOLS, SELECT IMEI(S) BACKUP/RESTORE AND SELECT BACKUP.
You are now good to go, you may now flash and experiment with other ROMs. Stay away from the international s3 forum, just flash things that are meant for your S3 model, if you are not sure just ask the dev.
Sorry for the caps lock but steps 6, 7 and 8 will prevent you from major headaches. Especially 7 and 8. If you flash a ROM and your stuck on 2g/edge and your imei is zero, just download that app and open it and restore your imei. Step 6 is helpful just in case if you download a ROM and you run into your current problem you can just restore your backup and your phone will be fine.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Finally got home. Ready to try this. My freaking phone is dead. I have plugged it in...It doesn't seem to be recharging while my phone is turned off? Do you have any ideas for what i should do here?
re: charging issue
nickcross88 said:
Finally got home. Ready to try this. My freaking phone is dead. I have plugged it in...It doesn't seem to be recharging while my phone is turned off? Do you have any ideas for what i should do here?
Click to expand...
Click to collapse
First thing I would do is to remove the battery and put it into the freezer for a couple hours,
then put the battery back in the phone to charge. (wipe the moisture off the battery first).
I know this sounds like a weird thing to do, but it's an old school trick which works most the time.
Once the phone starts to charge leave it alone until it has a full charge, don't play with it til then.
nickcross88 said:
Finally got home. Ready to try this. My freaking phone is dead. I have plugged it in...It doesn't seem to be recharging while my phone is turned off? Do you have any ideas for what i should do here?
Click to expand...
Click to collapse
Wait before you follow my post.....when you boot into recovery, what color is the background and what is the color of the text?
|When Emotion Goes up, Logic Goes Down|
707BeastMode707 said:
Wait before you follow my post.....when you boot into recovery, what color is the background and what is the color of the text?
|When Emotion Goes up, Logic Goes Down|
Click to expand...
Click to collapse
recovery mode is 5.5.0.4 CWM Black background with blue text. also has the top hat logo in the middle of the screen.
nickcross88 said:
recovery mode is 5.5.0.4 CWM Black background with blue text. also has the top hat logo in the middle of the screen.
Click to expand...
Click to collapse
Ok, i have loaded the provided .zip file to my sd card. however, it isn't showing up on my sd card when in recovery. It shows other files, but it won't show the new zip file or the new rom.
I see there is a setting under mount that says "mount external SD card" could this be the reason?
No. External SD mounting is broken on 5.5.0.4. Update it.
Aerowinder said:
No. External SD mounting is broken on 5.5.0.4. Update it.
Click to expand...
Click to collapse
I have fixed it. I was able to odin a stock .tar file on it 20 minutes ago. The only thing i am wondering about its that system info says i'm running 4.0.4. I am running the system update for it.
Thanks to everyone that helped me with my mistake. You guys are awesome!
Thank you sooo much!
707BeastMode707 said:
Don't worry about being a noob. Everyone on this forum is or has been a noob. You'll learn though.
Just follow these steps:
1.) Download this ROM on your computer (the latest from T-Mobile, stock rooted):
http://forum.xda-developers.com/showthread.php?t=2126679
2.) On your SD card create a designated folder for ROMs (just to make it easier to find the ROM when it comes time to flash it), then find the ROM you have just downloaded and put it in the folder you have created on the SD card
3.) Power on the phone, Boot into recovery which is also known as CWM by (volume up, home button and power button)
4.) Once in recovery do the following:
-wipe cache
-wipe dalvik cache
-wipe date/factory reset
-install zip from external SD card
-navigate to the folder where you placed the ROM in step 2 and select it and and select yes to flash it.
-when finished flashing go back to the main menu and select reboot device
(Device may take a few minutes to fully boot so let the phone sit and do its thing)
5.) When phone is booted up, go through the setup process with your email and what not.
6.) AFTER GOING THROUGH THE SETUP PROCESS, REBOOT DEVICE BACK INTO RECOVERY (CWM) AND SELECT RESTORE/BACKUP, THEN SELECT BACKUP, WHEN FINISHED REBOOT THE DEVICE
7.) AFTER YOU HAVE REBOOTED YOUR DEVICE GO TO THE PLAY STORE AND DOWNLOAD THIS APP:
https://play.google.com/store/apps/...tore/apps/details?id=com.j.y.daddy.customizer
8.) ONCE DOWNLOADED, OPEN THE APP (should ask for root permissions, hit accept) SELECT TOOLS, SELECT IMEI(S) BACKUP/RESTORE AND SELECT BACKUP.
You are now good to go, you may now flash and experiment with other ROMs. Stay away from the international s3 forum, just flash things that are meant for your S3 model, if you are not sure just ask the dev.
Sorry for the caps lock but steps 6, 7 and 8 will prevent you from major headaches. Especially 7 and 8. If you flash a ROM and your stuck on 2g/edge and your imei is zero, just download that app and open it and restore your imei. Step 6 is helpful just in case if you download a ROM and you run into your current problem you can just restore your backup and your phone will be fine.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thank you so much! this happened to me this morning, I've been looking for answers for 2 hours! I came upon yours and this helped me! I just wanna thank you so much, I thought I bricked my phone, and had to buy a new one. Thanks to you, I won't have too, just wanted to say this one more time, thank you! c:
Aerowinder said:
No. External SD mounting is broken on 5.5.0.4. Update it.
Click to expand...
Click to collapse
Could this be part of the reason i was unable to flash cm 10.1 onto the phone in the first place? Should i update to the touch version?
nickcross88 said:
Could this be part of the reason i was unable to flash cm 10.1 onto the phone in the first place? Should i update to the touch version?
Click to expand...
Click to collapse
What you have to do is go to the play store and download ROM manger, open ROM manager and install the updated version of cwm, then you shouldn't run into any more problem when flashing ROMs, just make sure the recovery is always up to date.
|When Emotion Goes up, Logic Goes Down|