[GUIDE/FIX] {S4-MULTI} No Sound &/ WiFi &/ Bluetooth After Unbrick/Update? Read Me! - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

[GUIDE/FIX] {S4-MULTI} No Sound &/ WiFi &/ Bluetooth After Unbrick/Update? Read Me!
THIS GUIDE CAN APPLY TO ANY MODEL, PROVIDED YOU ENSURE TO GET THE PROPER FILES FOR YOUR VERSION!
I've had success myself flashing stock firmware from the M919V for Wind Mobile onto my I337M with no issue. This shouldn't be an issue. However, for the purpose of this guide, it is important that you get the firmware that was intended FOR YOUR DEVICE!
---
First head over here >> http://forum.xda-developers.com/showthread.php?t=2559693 >> and check out the original thread that helped me get to this resolution. Thank you to all the lovely people there!!
Before my softbrick occurred, I had flashed the NE1 modem through ODIN. I found that the same modem remained regarldess of the firmware I flashed. So I thought to match them up and give it another go. This worked great. This will work even if it was a regular S/W upgrade or install that caused the no sound and/or WiFi and/or Bluetooth issue.
Quick note before we begin: this guide assumes that you already went through a softbrick and have successfully come back from it, or went through a software update/firmware install which resulted in the same issue. Some of the steps in this guide may be able to be applied to some parts unbricking a phone, but this is NOT the intention. The intention is to help recover sound, WiFi and Bluetooth AFTER a successful unbrick or failed update/install otherwise.
DISCLAIMER: I am not responsible for your phone melting, imploding, turning into maple syrup or dying. Follow at your own will!
PRE-GAME CHECKLIST:
- Determine the ORIGINAL FIRMWARE that came on your device (this one was important for me, not sure how crucial it may be for others) - to be honest, I'm not 100% sure how to figure this out other than looking at the phone's box. It should notate which software version (SW-VER) it is. Before doing this, I was soft bricked, and had to use the very original 4.2.2 software for my carrier to recover from THAT. So maybe this part wasn't as important as I think, but I wanted to mention it anyway.
- The ORIGINAL USB cable for the phone - I suspect any high quality ones would work, but the one that came with the phone is a no-brainer
- ODIN 3.xx (I used 3.09)
- Samsung USB Drivers installed properly
- NO SD CARD (to be safe - this is optional as it should not be touched throughout the process)
- DO NOT, under any circumstance, use a USB hub for this procedure. Make sure it's direct into your computer with no extensions. I also recommend a cable that is 6ft or shorter if possible, but the quality of the cable is the most important
DO IT:
1) Download the ORIGINAL firmware that came with your phone (if you weren't able to determine this, I'd say the most recent one should be safe to flash, unless you softbricked while on 4.2.2 or 4.3 - in that case I would stick with the corresponding version, though I'm not sure how it would be affected since I didn't run into this)
2) Extract the file (I use 7Zip) and ensure there is one .tar.md5 file as a result - do not extract again
3) Boot up the phone into Download Mode (PWR off completely, then hold VOLDOWN + HOME + PWR together until the warning appears on the screen - click VOLUP to accept and proceed)
---PHONE WIPE---
This part is optional but I highly, highly recommend it.
4a) Flash Philz CWM (you can find the file and instructions on how to flash it through ODIN very easily)
4b) After flashing, it usually reboots into recovery. If it does not, do so manually: turn off the phone completely (hold the power button until the screen goes black) then quickly press the VOLUP + HOME + PWR buttons. When you feel a vibration, release the PWR button but KEEP HOLDING VOLUP + HOME. Keep holding those two until you see the phone turn off and come back on.
4c) Make sure you close ODIN once confirmed the flash is done
4d) Tap factory reset and confirm it
4e) Once done, choose the clean ROM install option and confirm that as well
4f) Reboot the phone and continue on with the steps
NOTE: if there is anything to backup, now would be a good time to do this.
---
5) Open ODIN (IMPORTANT: In Windows, right-click and choose "Run as administrator" - this helped avoid an error for me)
6) Connect your phone directly to a USB on your PC and confirm that ODIN recognized it (it should highlight the first box and have "COM#" listed)
7) Click the second section (AP / PDA) and choose the .tar.md5 file you got in Step 1
***NOTE: ODIN may look like it's freezing or hanging here - IT IS NOT, BE PATIENT - it is a large file and it will take a bit of time to verify the MD5 for it
8) Click Start and sit back - it should take 8-10 mins or so (8:55 for me) with KitKat, and 5-7 mins or so with JB.
9) Your phone should have rebooted into a fresh Firmware. If you hear the Samsung boot sound, GREAT! You should be good (test WiFi and Bluetooth if possible) and you're done. Assuming that's not the case, which is why you're here, proceed to the next step
***If it's stuck in a bootloop, you need to force Recovery mode and do a factory reset. To do this, turn off the phone completely (hold the power button until the screen goes black) then quickly press the VOLUP + HOME + PWR buttons. When you feel a vibration, release the PWR button but KEEP HOLDING VOLUP + HOME. Keep holding those two until you see the phone turn off and come back on. Use the VOL buttons to scroll to the factory reset option, and choose PWR to select. Then confirm on the next screen. Once that's done, wipe cache in the same way. Then, reboot, again in the same way. Now your phone should boot up
10) Go through setup and then go into Settings > More > About device. Observe the "Baseband version" section, and see if it matches the "Build number" section (starting from I337 and onwards). IF THEY MATCH, then repeat steps 5-10. IF THEY DO NOT MATCH, continue.
11) Download the matching modem file - ENSURE that the version of the modem you download MATCHES EXACTLY with the "Build number" in your phone's settings. Flash the file in ODIN in the AP / PDA section (if you need detailed instructions on this, it's a snap to find in XDA or Google)
12) Once done, reboot into the regular OS and verify that the "Baseband version" and "Build number" sections MATCH. If not, try to flash the modem again. After this has been verified, go ahead and follow steps 5-10 as many times as necessary until you hear that beautiful boot noise! It took me twice.
All the best and happy flashing guys! I'm not too much of an expert, just very good at explaining things, but I'll try to help as I can with any questions!
THANKS:
- All the great help thanks to input from around XDA in this thread (also listed in the beginning of this one): http://forum.xda-developers.com/showthread.php?t=2559693
- All the devs that work hard for us Canadian and AT&T guys over here

Related

[GUIDE] A detailed step-by-step "Dummies Guide" to installing CM7 on your ATRIX MB860

[GUIDE] A detailed step-by-step "Dummies Guide" to installing CM7 on your ATRIX MB860
After reading several threads of where to go and how to do it, and being able to successfully install CM7 after going through all those threads, I took it upon myself that if I was ever successful in getting it on my device (Motorola Atrix MB860, locked to T-Mobile UK), I'd share my experience and hopefully create a how-to in the process. I am hoping this guide will be useful to many others.
Please be advised that this is the completed version of this simple guide, the actual process involved me having to back track and read several threads, then re-read some more other threads just to make sure I did the proper thing.
A big thank you to all those who took the time to make the guides I based this "all in one" guide for T-Mobile Atrix users. Some of them had an instruction or two missing (like when do you plug in the phone to the computer?) that would have been obvious to many but to some would have had trouble figuring out.
The phone in question: Motorola Atrix MB860. My phone was running Android 2.2.2. I updated the phone using a Windows 7 Home Premium 64-bit machine.
Since I got it as a free phone on a new contract, I'd like to assume that the phone itself was network locked. I haven't tried any other SIM with it so far. Please be advised, YOU DO NOT NEED TO UNLOCK YOUR PHONE TO GET CM7. Unlocking the BOOTLOADER, is not the same as unlocking the phone. This maybe obvious to some people, but again, not to everyone (saw a guy respond in one forum who had to pay to get his phone network-unlocked, in hoping that would make it easier to install CM7 for him).
Also, this guide is not meant to be the official way of loading it up, I just hope that it makes it easier for someone else to load up the excellent CM7 on to a Motorola Atrix. Add it to the list of many threads you'll need to read! But I hope this thread is all you need to read.
So here goes, the step by step guide (I took) in getting the latest CM7 on it. Before I start, a few necessary words:
WARNING #1 - Ensure that whenever you plugin your phone, or install something, or run a command, please let the event finish before going on to the next step. In my experience, there were several times that I had to plug in the phone, and wait for the driver installation to continue, and on one instance I got a bit impatient unplugged the phone before realizing that it was still installing. It set me back another 10 minutes just because of that.
WARNING #2 - Please make sure that you back up any data that you have just to be sure. After the end of the entire process, your phone will be back to factory settings and you will need to re-setup any customisations, and put back any media files you use, AND install any apps you use.
WARNING #3 - Just to be safe, and to make sure that your battery stats isn't messed up, make sure that you fully charge your phone first before continuing with this guide.
DISCLAIMER - As with anything regarding XDA and tinkering with your phone, you may void your warranty doing this. I cannot be 100% sure that your phone will not be bricked by this (I've been using the guides by XDA'ers over the years and have yet to brick a phone. Well I did brick my Samsung Galaxy S i9000 once, but I was able to recover it!). Proceed at your own discretion.
THE GUIDE
1. Download all the necessary files. I have taken the liberty of gathering all the files you will need in one archive. Click on any of the following download links to grab it.
* Deposit Files Main
* MediaFire Mirror
* Filesonic Mirror
* Megaupload Mirror​
2. UnRAR the archive to "C:". A warning may show up based on your security settings, just say "Yes" to this.
3. Install the necessary drivers and programs. Start with "MotorolaEndUserDrivers_5.1.0x64.msi". Then install "RSDLite5.3.1.msi".
4. Unlocking the Bootloader.
a. Turn off your phone.
b. Remove your SIM, and MicroSD card if you have one.
c. Put the battery back in, then press and hold "Power Button + Volume Up" until it acknowledges RSD.
d. The phone will say “Starting RSD protocol support”.
e. On your computer, open "RSD Lite".
f. Press the “...” button.
g. Locate the "intl-fix-try1.sbf" file. This should be located in "C:\MotorolaMB860toCM7\". Select that. For USA AT&T users please refer to this link to download the correct SBF file.
h. Connect your phone to the computer. Ensure that all the drivers are installed before proceeding.
i. RSD Lite should recognize your phone and say something similar to “Model: SE Flash Olympus” and the status should read as “Connected…”
j. Press the “Start” button. This may take a few moments. My phone rebooted and completed starting up before the timer in RSD Lite reached 100%! But I did not disconnect the phone just to be sure.
k. Press "Windows Key + R". Type "cmd" then press "Enter".
l. In the command prompt window, enter in "C:" first to make sure you're in the right drive, then execute "cd C:\MotorolaMB860toCM7\fastboot\" to go to the right folder. This will change your working folder to that of where the files are (well, a subfolder of the main folder, you should be at the fastboot working folder, I won't say folder again... D'OH!).
m. Turn off your phone. After making sure it's turned off, press "Power Button + Volume Down" until you see "Fastboot" on the phone's screen.
n. Press "Volume Up" and you should see “Starting Fastboot protocol support”.
o. Connect your phone back to the computer via USB. Again, ensure that any driver installation prompts are finished before proceeding.
p. Back at the command prompt, type "fastboot oem unlock".
q. A warning will appear, along with a "Unique Device ID".
r. Type "fastboot oem unlock *****". Where ***** will be your "Unique Device ID".
s. Type "fastboot reboot".
t. Your phone will now reboot. Now, your phone has an unlocked bootloader!​
5. Flashing CWM Recovery using FASTBOOT.
a. Turn off your phone. Then boot into "fastboot". This is done by pressing "Power Button + Volume Down" when turning on your phone.
b. When you see "Fastboot" on the phone's screen, press "Volume Up" to select it.
c. Connect your phone to your computer. Again ensure any prompts are finished before proceeding.
d. Your command prompt should still be open, and your working directory should still be "C:\MotorolaMB860toCM7\fastboot\". Now type "fastboot flash recovery recovery.img".
e. After the process, type in "fastboot reboot".
f. Your phone will now reboot, and you have successfully installed CWM Recovery.​
6. Installing Cyanogen Mod 7!
a. Turn the phone off then put back your SIM, and your MicroSD card.
b. Turn on your phone, and after the phone completely boots up, connect it to your computer. You should use Mass Storage as the connection option in the phone.
c. Copy the files "Ba2tF.zip" and "gapps-gb-20110828-signed.zip" into the phone's internal memory.
d. Disconnect the phone properly from the computer, then turn off the phone.
e. On the phone, press "Power Button + Volume Down" until you see "Fastboot".
f. Press "Volume Down" several times until you see "Android Recovery". Then press "Volume Up". Your phone should say "Entering Android Recovery Mode".
g. Using the volume keys for movement (Up & Down) and the power button for selection, choose "install zip from sdcard".
h. Then select "choose zip from internal sdcard".
i. You might see a lot of folders and files here. You will need to select "Ba2tF.zip".
j. After which, it will ask you to confirm. Select "Yes - Install Ba2tF.zip".
k. After it completes the installation, you will need to run the "wipe data/factory reset" command in CWM Recovery. Follow the prompts to complete this.
l. After that, you will need to run the "wipe cache partition" command in CWM Recovery. Again, follow the prompts to complete this.
m. When it completes, choose "reboot system now".
n. Be enchanted by the excellent Cyanogen Mod 7 loading screen!​
7. Due to an arrangement (more like a request) from Google, the Cyanogen Mod 7 release does not contain any Google Apps. To install the necessary Google Apps:
a. Turn off the phone.
b. On the phone, press "Power Button + Volume Down" until you see "Fastboot".
c. Press "Volume Down" several times until you see "Android Recovery". Then press "Volume Up". Your phone should say "Entering Android Recovery Mode".
d. Using the volume keys for movement (Up & Down) and the power button for selection, choose "install zip from sdcard".
e. Then select "choose zip from internal sdcard".
f. You might see a lot of folders and files here. You will need to select "gapps-gb-20110828-signed.zip".
g. After which, it will ask you to confirm. Select "Yes - Install gapps-gb-20110828-signed.zip".
h. When it completes, choose "reboot system now".​
8. That is it! That's the whole process I believe. Can easily be done in 30 minutes, but I would recommend alotting an hour to this project just to be safe.
I have found that once going on to Cyanogen Mod 7, it would be very hard, nay, would be insane for me to go back to the Stock ROM (or any other ROM for that matter!). I personally think that all this hard work is worth it. Bottom line, I appreciate what my phone is and has to offer thanks to the Cyanogen Mod team (specifically the Atrix-Dev-Team!).
Most importantly, donations to the Atrix-Dev-Team (http://code.google.com/p/atrix-dev-team/) will be most appreciated (I'm not a part of them but I support what they do, hey). They do a fantastic job and giving them some beer money is the least we can do to show our appreciation.
Last and not the least, this guide is a combination of all the other guides that I have had to read and peruse in order for me to get my phone on to CM7. All I did was get the necessary important information that was useful to me, but the credit of the actual content and the guides go to the following:
1. Motorola Atrix 4G Forums
2. * Official CM7 for Atrix Stable only (No Nightly )* Atrix CM Ba2tF RELEASED!!
3. CM7 Q&A
3. [Updated 10-30-2011] THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs
4. [PUDDING] International House of Pudding! BL Unlock/root thread (Updated 07/23/2011)
5. BriefMobile - How To: Unlock the Atrix 4G Bootloader
6. Atrix-Dev-Team Backup/Restore​
* In case you were wondering what "preinstall.img" is, well according to this thread, it should help with ROOTing your phone. I haven't done so, haven't used it, but I've attached it for your convenience should you feel extra adventurous.
I wish you success in the installation of CM7 on to your Motorola Atrix!
Good job figuring it out and writing an in detail guide, I am sure many people will find it useful ....
...
BUT
.... the procedures of installing CM7 on network locked and network unlocked phones are exactly the same.
So, existing guides would do the job just fine, disregarding if the phone is sim locked or not.
Thanks for pointing that out, I will update the thread to indicate this.
The.Opethian said:
NOTE: This guide can also work on unlocked phones.
After reading several threads of where to go and how to do it, and being able to successfully install CM7 after going through all those threads, I took it upon myself that if I was ever successful in getting it on my device (Motorola Atrix MB860, locked to T-Mobile UK), I'd share my experience and hopefully create a how-to in the process that I am hoping will be useful to others.
Please be advised that this is the completed version of this simple guide, my actual process involved me having to back track and read several threads, then re-read some more other threads just to make sure I did the proper thing.
A big thank you to all those who took the time to make the guides I based this "all in one" guide for T-Mobile Atrix users. Some of them had an instruction or two missing (like when do you plug in the phone to the computer?) that would have been obvious to many but to some would have had trouble figuring out.
The phone in question: Motorola Atrix MB860. My phone was running Android 2.2.2. I updated the phone using a Windows 7 Home Premium 64-bit machine.
Since I got it as a free phone on a new contract, I'd like to assume that the phone itself was network locked. I haven't tried any other SIM with it so far. Please be advised, YOU DO NOT NEED TO UNLOCK YOUR PHONE TO GET CM7. Unlocking the BOOTLOADER, is not the same as unlocking the phone. This maybe obvious to some people, but again, not to everyone (saw a guy respond in one forum who had to pay to get his phone network-unlocked, in hoping that would make it easier to install CM7 for him).
Also, this guide is not meant to be the official way of loading it up, I just hope that it makes it easier for someone else to load up the excellent CM7 on to a Motorola Atrix. Add it to the list of many threads you'll need to read! But I hope this thread is all you need to read.
So here goes, the step by step guide (I took) in getting the latest CM7 on it. Before I start, a few necessary words:
WARNING #1 - Ensure that whenever you plugin your phone, or install something, or run a command, please let the event finish before going on to the next step. In my experience, there were several times that I had to plug in the phone, and wait for the driver installation to continue, and on one instance I got a bit impatient unplugged the phone before realizing that it was still installing. It set me back another 10 minutes just because of that.
WARNING #2 - Please make sure that you back up any data that you have just to be sure. After the end of the entire process, your phone will be back to factory settings and you will need to re-setup any customisations, and put back any media files you use, AND install any apps you use.
WARNING #3 - Just to be safe, and to make sure that your battery stats isn't messed up, make sure that you fully charge your phone first before continuing with this guide.
DISCLAIMER - As with anything regarding XDA and tinkering with your phone, you may void your warranty doing this. I cannot be 100% sure that your phone will not be bricked by this (I've been using the guides by XDA'ers over the years and have yet to brick a phone. Well I did brick my Samsung Galaxy S i9000 once, but I was able to recover it!). Proceed at your own discretion.
THE GUIDE
1. Download all the necessary files. I have taken the liberty of gathering all the files you will need in one archive. Click on any of the following download links to grab it.
* Deposit Files Main
* MediaFire Mirror
* Filesonic Mirror
* Megaupload Mirror​
2. UnRAR the archive to "C:". A warning may show up based on your security settings, just say "Yes" to this.
3. Install the necessary drivers and programs. Start with "MotorolaEndUserDrivers_5.1.0x64.msi". Then install "RSDLite5.3.1.msi".
4. Unlocking the Bootloader.
a. Turn off your phone.
b. Remove your SIM, and MicroSD card if you have one.
c. Put the battery back in, then press and hold "Power Button + Volume Up" until it acknowledges RSD.
d. The phone will say “Starting RSD protocol support”.
e. On your computer, open "RSD Lite".
f. Press the “...” button.
g. Locate the "intl-fix-try1.sbf" file. This should be located in "C:\MotorolaMB860toCM7\". Select that.
h. Connect your phone to the computer. Ensure that all the drivers are installed before proceeding.
i. RSD Lite should recognize your phone and say something similar to “Model: SE Flash Olympus” and the status should read as “Connected…”
j. Press the “Start” button. This may take a few moments. My phone rebooted and completed starting up before the timer in RSD Lite reached 100%! But I did not disconnect the phone just to be sure.
k. Press "Windows Key + R". Type "cmd" then press "Enter".
l. In the command prompt window, type in "cd\MotorolaMB860toCM7". This will change your working folder to that of where the files are.
m. Turn off your phone. After making sure it's turned off, press "Power Button + Volume Down" until you see "Fastboot" on the phone's screen.
n. Press "Volume Up" and you should see “Starting Fastboot protocol support”.
o. Connect your phone back to the computer via USB. Again, ensure that any driver installation prompts are finished before proceeding.
p. Back at the command prompt, type "fastboot oem unlock".
q. A warning will appear, along with a "Unique Device ID".
r. Type "fastboot oem unlock *****". Where ***** will be your "Unique Device ID".
s. Type "fastboot reboot".
t. Your phone will now reboot. Now, your phone has an unlocked bootloader!​
5. Flashing CWM Recovery using FASTBOOT.
a. Turn off your phone. Then boot into "fastboot". This is done by pressing "Power Button + Volume Down" when turning on your phone.
b. When you see "Fastboot" on the phone's screen, press "Volume Up" to select it.
c. Connect your phone to your computer. Again ensure any prompts are finished before proceeding.
d. Your command prompt should still be open, and your working directory should still be "C:\MotorolaMB860toCM7\". Now type "fastboot flash recovery recovery.img".
e. After the process, type in "fastboot reboot".
f. Your phone will now reboot, and you have successfully installed CWM Recovery.​
6. Installing Cyanogen Mod 7!
a. Turn the phone off then put back your SIM, and your MicroSD card.
b. Turn on your phone, and after the phone completely boots up, connect it to your computer. You should use Mass Storage as the connection option in the phone.
c. Copy the files "Ba2tF.zip" and "gapps-gb-20110828-signed.zip" into the phone's internal memory.
d. Disconnect the phone properly from the computer, then turn off the phone.
e. On the phone, press "Power Button + Volume Down" until you see "Fastboot".
f. Press "Volume Down" several times until you see "Android Recovery". Then press "Volume Up". Your phone should say "Entering Android Recovery Mode".
g. Using the volume keys for movement (Up & Down) and the power button for selection, choose "install zip from sdcard".
h. Then select "choose zip from internal sdcard".
i. You might see a lot of folders and files here. You will need to select "Ba2tF.zip".
j. After which, it will ask you to confirm. Select "Yes - Install Ba2tF.zip".
k. After it completes the installation, you will need to run the "wipe data/factory reset" command in CWM Recovery. Follow the prompts to complete this.
l. After that, you will need to run the "wipe cache partition" command in CWM Recovery. Again, follow the prompts to complete this.
m. When it completes, choose "reboot system now".
n. Be enchanted by the excellent Cyanogen Mod 7 loading screen!​
7. Due to an arrangement (more like a request) from Google, the Cyanogen Mod 7 release does not contain any Google Apps. To install the necessary Google Apps:
a. Turn off the phone.
b. On the phone, press "Power Button + Volume Down" until you see "Fastboot".
c. Press "Volume Down" several times until you see "Android Recovery". Then press "Volume Up". Your phone should say "Entering Android Recovery Mode".
d. Using the volume keys for movement (Up & Down) and the power button for selection, choose "install zip from sdcard".
e. Then select "choose zip from internal sdcard".
f. You might see a lot of folders and files here. You will need to select "gapps-gb-20110828-signed.zip".
g. After which, it will ask you to confirm. Select "Yes - Install gapps-gb-20110828-signed.zip".
h. When it completes, choose "reboot system now".​
8. That is it! That's the whole process I believe. Can easily be done in 30 minutes, but I would recommend alotting an hour to this project just to be safe.
I have found that once going on to Cyanogen Mod 7, it would be very hard, nay, would be insane for me to go back to the Stock ROM (or any other ROM for that matter!). I personally think that all this hard work is worth it. Bottom line, I appreciate what my phone is and has to offer thanks to the Cyanogen Mod team (specifically the Atrix-Dev-Team!).
Most importantly, donations to the Atrix-Dev-Team (http://code.google.com/p/atrix-dev-team/) will be most appreciated (I'm not a part of them but I support what they do, hey). They do a fantastic job and giving them some beer money is the least we can do to show our appreciation.
Last and not the least, this guide is a combination of all the other guides that I have had to read and peruse in order for me to get my phone on to CM7. All I did was get the necessary important information that was useful to me, but the credit of the actual content and the guides go to the following:
1. Motorola Atrix 4G Forums
2. * Official CM7 for Atrix Stable only (No Nightly )* Atrix CM Ba2tF RELEASED!!
3. CM7 Q&A
3. [Updated 10-30-2011] THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs
4. [PUDDING] International House of Pudding! BL Unlock/root thread (Updated 07/23/2011)
5. BriefMobile - How To: Unlock the Atrix 4G Bootloader
6. Atrix-Dev-Team Backup/Restore​
* In case you were wondering what "preinstall.img" is, well according to this thread, it should help with ROOTing your phone. I haven't done so, haven't used it, but I've attached it for your convenience should you feel extra adventurous.
I wish you success in the installation of CM7 on to your Motorola Atrix!
Click to expand...
Click to collapse
I needed to be in the fastboot directory to execute the fastboot commands using moto-fastboot [command].
Also needed to copy the recovery image to the fastboot directory.
Otherwise, easy to complete in around 30 minutes as you say.
Thanks very much,
Jim
Awesome guide!
But one question, "cd\MotorolaMB860toCM7" would that work? Wouldn't you need to wright "cd C:\MotorolaMB860toCM7" (assuming everything is extracted to C
Thank you lovfors and yey365 for the tips! Have updated the thread now.
Gonna throw this guide in the General section. It's not development, so it doesn't belong here.
Just a quick note so nobody bricks by mistake, remember to use the correct pudding for your kind of phone (international or AT&T)!
turl1 said:
Just a quick note so nobody bricks by mistake, remember to use the correct pudding for your kind of phone (international or AT&T)!
Click to expand...
Click to collapse
Thank you sir, I have amended the step with additional details. Cheers!
Awesome walkthrough, signed up just to say thanks. The only thing wrong was the recovery image didn't work for me, tried a few times then got one from http://forum.xda-developers.com/showthread.php?t=1204500 and it worked great.
Guys,
Is this ROM is 100% compatible with MB860?
Example: Fingerprint / DockStation
Thks!
gunbolt said:
Guys,
Is this ROM is 100% compatible with MB860?
Example: Fingerprint / DockStation
Thks!
Click to expand...
Click to collapse
The answer to your question can be found here.
Do some research before asking basic questions!
What Doesn’t Work:
•Fingerprint sensor - Work in progress (not native to CM)
•Webtop - Work in progress (not native to CM)
OK I see now.
Thks
If its any consolation, the lockscreens for CM7 are more than capable. Having big fingers, the fingerprint scanner only worked 60% of the time for me. Still, here's to hoping it gets fully implemented.
Sent from my MB860 using Tapatalk
The fingerprint scanner isn't about finger size, it's more about positioning and timing. I went from unlocking at a 70% rate to a 100% by just knowing how to position my fingers and sliding slowly, but not too slow. Unlocking in 1-1.5 second(s) sure beats typing the pin or having a unsecured phone.
I flashed to a GB ROM until CM7 gets it. CM7 has some sensitivity problems for me (http://forum.xda-developers.com/showthread.php?t=1331631) and it also cannot play HD flash yet. Don't get me wrong, I love what the devs are doing for CM7 and I support them all the way, but I just can't find myself to use it as my daily ROM until the small things (big for me) are patched out. Other than the problems mentioned, it is the best, it gives AMAZING battery life. About double what the GB ROMs give us, which is great. But I am willing to sacrifice charging every 1.5 days instead of 3 for Fingerprint and HD Flash.
Thanks for this guide, Will make my wife very happy.
She got the Atrix from t-mobile uk yesterday and hated it.
Her galaxy s cm7 was faster and my defy cm7 kept with up with it.
lets hope cm7 does it normal job and matches amazing hardware with amazing software.
Hey I need some help! I rooted my phone, unlocked bootloader and installed CWM as per in instructions in the noobs guide sticky and now have been trying to install CM7.
When it goes into the recovery screen I tried to install the cm7 zip file from the internal storage and it keeps giving me a installation aborted error:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Does anyone know how to get around this or what I am doing wrong??
I know you guys hate noobs and everything but this is starting to piss me off and I could use some help
i cant get to this step:
6
b. Turn on your phone, and after the phone completely boots up, connect it to your computer. You should use Mass Storage as the connection option in the phone.
my computer cannot detect my atrix having storage space.
so the only way i can install the cm7 rom is to "install from external sd card"
although it was successful, i got the error message during the installation, "error mounting /emmc"
i dont know if this error related to the following issue. i can only detect 1.97gb internal storage in the setting and the rest of the storage is missing!!
someone got the same problem and figured out the solution?
CMD problem D:
5. Flashing CWM Recovery using FASTBOOT.
a. Turn off your phone. Then boot into "fastboot". This is done by pressing "Power Button + Volume Down" when turning on your phone.
b. When you see "Fastboot" on the phone's screen, press "Volume Up" to select it.
c. Connect your phone to your computer. Again ensure any prompts are finished before proceeding.
d. Your command prompt should still be open, and your working directory should still be "C:\MotorolaMB860toCM7\fastboot\". Now type "fastboot flash recovery recovery.img".
e. After the process, type in "fastboot reboot".
f. Your phone will now reboot, and you have successfully installed CWM Recovery.
For part d i got into C:\motorolamb860\fastboot but when i try to enter fastboot flash recovery recovery.img it says "Fastboot" is not recognized as an internal or external command, operable program or batch file. Im pretty sure i followed the instructions dead on >.> i don't know why i cant flash recovery ~_~ help please
zx6rexx said:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
Try redownloading it is failing md5 verification
Sent from my MB860 using Tapatalk

[TUT][i9001] HOW TO UNBRICK YOUR SOFTBRICKED I9001

Soft bricking often happens in when you try to install a ROM which is not optimized for your phone e.g:Installing i9100 SII ROM on your i9001.
Here is a basic tutorial on how to unbrick a i9001.
Requirements:
For unbricking your phone you are going to need these:
1.An official Samsung firmware
2.ODIN downloader
3.AriesVE.ops for ODIN usage.
4.USB cable
5.Samsung KIES drivers installed
6.Patience!!!
OK.first of all you need to check things above and make sure you have them all.
Fortunately when your phone is soft bricked(when soft bricked your phone doesn't boot into the OS And instead of that you'll see picture of a phone connected to a computer and on the connection line there's a warning sign) can get yo the download mode. So first get your phone in download mode by pressing this button combination: volume down+ home key+ power button
So then get set to use ODIN.
Connect your phone to the PC and make sure you have installed drivers and also killed every KIES process.(If you have done well till now you can see one black gets yellow and in Terminal you'll see 2 lines "detected","added") So start ODIN and place AriesVE.ops as the ops file then use your official firmware (extension should be like this |..... .tar.md5|).To get your firmware working tick "one package" and place you "MD5" file in "one package" location. Then after MD5 checking start the process and go grab a beer.
Wait about 7 to 10 minutes to see PASS on the block.
Then your phone would automatically reboot into your android OS. Then you can start rooting, Tweaking and other stuff again.
At least one you have your phone and your warranty back.
FAQs:
1.my phone gets stuck at setup connection. what should I do?
Chill out! Don't panic! Simply remove your battery for 10 seconds then do these things all again and proceed!
2.my phone boot loops what do I do?
Simply reboot your phone in the Recovery mode "volume down+ power" and wipe cache/dalvik cache if you can.
(Once I installed FOTA from stock recovery and that worked for me)(I suggest you install the official TWRP recovery from SDcard to have more options)
3.you tell me your questions!I'll edit the topic later!
At last feel free to ask any dumb question. Dumb questions are muck more valuable than dumb mistakes!
Please hit thanks button if I helped you out!
Sent from my GT-I9001 using xda premium

How to unlock your galaxy S3 III on 4.1.2 for free without rooting your phone ! GUIDE

*It should work on pretty much any android phone on 4.1.2*
*it wont root your phone, so it wont break your warranty and its completely free*
*if you have 4.1.1, do step 8 only and your good to go*
You will need to downgrade your phone back to 4.1.1, unlock it using a simple method, factory reset, restore your data, upgrade back to 4.1.2
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
STEP 1: Find and download your 4.1.1 firmware on Sammobile (make sure you put the right model and country, etc)
STEP 2: Download Odin 3.07
STEP 3: Backup your data, I'm not gonna make a guide for this, there already a ton on google, as for me, I didn't really needed my apps so I just backed my contacts on my gmail and that's it
STEP 4: Turn off your phone, open it back up on download mode (Hold volume down + home button + power button)
STEP 5: Open Odin, click on the PDA button, then go get the firmware you downloaded on Sammobile
STEP 6: Plug your phone in your computer via USB, you should see COM something appear on one of the top left square in Odin, wait for it to load until it seems ready, make sure Auto reboot is checked.
STEP 7: Click on Start on Odin, the firmware will now install on your phone and then the phone will reboot, it took 5-10min for me, be patient and make sure to not unplug your USB cable.
STEP 8: After this, your phone is back to 4.1.1, it may be lagging a bit with some apps problems, but you still can do this unlocking method: Dial the following keys *#197328640#
Main Menu
[1] UMTS
[1] Debug Screen
[8] Phone Control
[6] Network Lock
Options [3]Perso SHA256 OFF
(after choosing this option, wait about 30 seconds, then go back one step by pressing the Menu button then select Back, now you are in
[6] Network Lock then choose
[4] NW Lock NV Data INITIALLIZ ..... wait for a minute then reboot your phone
*I am not the author of this method*
STEP 9: Factory reset your phone (should be in settings in backup and reset) make sure you backed up all the data you want to keep
STEP 10: upgrade back to 4.1.2, recover your data and you're done ! The phone is now factory unlocked entirely for free and still under warranty !
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
if its not clear or you have a better method for a specific step or you are stuck, feel free to make a reply, ill try to edit my post and help if I can, I am no professional though and learned how to do this in a few hours, just thought I would share to everyone since it saved myself 60$.
-PopJe
i have the SGH-I747M locked to Telus
This did work for me but after i completed step 7 the phone was lagging and app crashing so bad the dialer app would not open and it was very unstable!!!
At this point i did a factory reset with the following method
lets call it, optional STEP 7B..
After Odin is complete and the phone has rebooted, power the phone off again and do a factory wipe (YOU WILL LOOSE ALL INFO ON YOUR PHONE) using this method........
hold in the volume up, home, and power buttons until the samsung logo appears then release the power button only, once the android appears release the remaining buttons.
using the volume rocker, move the cursor to "wipe data/factory reset" and use the power button to select (AGAIN YOU WILL LOOSE ALL DATA ON YOUR PHONE!!!) then move cursor to "yes" and select to continue
Once complete move cursor down to "reboot system now"
you phone will now be stable and as if you just pulled it out of the box with 4.1.1
now move to step 8
wildbillers said:
i have the SGH-I747M locked to Telus
This did work for me but after i completed step 7 the phone was lagging and app crashing so bad the dialer app would not open and it was very unstable!!!
At this point i did a factory reset with the following method
lets call it, optional STEP 7B..
After Odin is complete and the phone has rebooted, power the phone off again and do a factory wipe (YOU WILL LOOSE ALL INFO ON YOUR PHONE) using this method........
hold in the volume up, home, and power buttons until the samsung logo appears then release the power button only, once the android appears release the remaining buttons.
using the volume rocker, move the cursor to "wipe data/factory reset" and use the power button to select (AGAIN YOU WILL LOOSE ALL DATA ON YOUR PHONE!!!) then move cursor to "yes" and select to continue
Once complete move cursor down to "reboot system now"
you phone will now be stable and as if you just pulled it out of the box with 4.1.1
now move to step 8
Click to expand...
Click to collapse
What happens after u do this and then upgrade back to 4.3? Does it stay? Do OTA updates still work or stop it? I'm trying to do a ATT S3 to T-Mobile. Any help would be appreciated. Thabks.
Fifth313ment said:
What happens after u do this and then upgrade back to 4.3? Does it stay? Do OTA updates still work or stop it? I'm trying to do a ATT S3 to T-Mobile. Any help would be appreciated. Thabks.
Click to expand...
Click to collapse
i continued on with steps 8 thru 10 above.
once the phone was tested as "unlocked" (placed a Rogers SIM in the device and tested) i then installed the OTA updates as normal.
as of today, this device has now received OTA updates to 4.3 and is still unlocked running on Rogers!
Hope this helps
Getting harder to find the firmware.
tbpopje said:
*It should work on pretty much any android phone on 4.1.2*
...
if its not clear or you have a better method for a specific step or you are stuck, feel free to make a reply, ill try to edit my post and help if I can, I am no professional though and learned how to do this in a few hours, just thought I would share to everyone since it saved myself 60$.
-PopJe
Click to expand...
Click to collapse
After a poor experience with ODIN sometime back I had my doubts about this procedure working... but it worked a treat. It did seem to get stuck rebooting after the procedure but a further factory reset/reboot sorted it out. The most difficult bit was finding the firmware but eventually found the same UK firmware at androidfilehost (no need to register with any file-hosting companies).
Thanks to everyone for taking the time to post these instructions for the benefit of people like me.
Will this work on a Alcatel phone?
Sent from my Nexus 7 using Tapatalk
Good info, thanks

Note 3 [N9005] Screen Flickering Issues

Hey guys,
I have recently rooted my device N3 (N9005) with CF-Auto-Root by Chainfire. (It trigged Knox to 0x1, it’s fine as its an overseas unit)
Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
It took me less than 10 seconds to get it done, all perfectly rooted.
But unfortunately, now my screen is flickering like crazy. I can’t even use the N3 right now.
When I boot it to Download Mode, screen is perfectly fine, but when I boot it to Recovery mode or the OS, it flickers like mad.
I’ve tried reflashing the stock ROM (downloaded from sammobile) but it doesn’t seem to work. What seems to be the problem?
I’ve googled “android screen flickering issue” but it seems that I am the only N3 user that is facing this problem.
The other problems are from HTC/Nexus,SGT10.1, tried the options suggested (eg auto brightness, developer option settings), some even said it’s the kernel issue.
I’ve only been using the N3 for a week and now its not working! HELP!!

[TUTORIAL][CM11][4.4.2] CyanogenMod Tutorial for Sony Xperia Tablet Z (pollux)

I went through a lot of searching and trouble to install CM11 on my Xperia Tablet Z, and I'd like to share a tutorial I made for anyone who is also wanting to accomplish this.
All links are in Dark Green because I cannot post links yet.
1. Download and extract the ADB+Fastboot+Drivers zip (alexpja.com/sony/adb-fastboot-win.zip)
2. Now we’ll unlock the bootloader.
a. If you do not have a Phone app (like I don’t on the SGP351), you can either get the IMEI from About -> Status in the settings OR you can find the IMEI right after the IC code, nearby the barcode on the bottom of the tablet.
b. If you do have a Phone app, enter *#06# to retrieve the IMEI.
c. Save this for later use.​3. Place the tablet into fastboot mode and connect it to the computer.
a. Power off the device
b. Connect USB to computer
c. While plugging in the other side of the USB cable into the tablet, hold down the Vol + button.
d. If your speakers are on, you should a sound.
e. We have to install the drivers for fastboot. Open devmgmt.msc via the Run window or in the Start menu and in Other Devices section, you should see S1 Service or S1 Fastboot (anything containing S1).
i. If it is showing a yellow exclamation mark: Follow 3.e.i.1. If it is not, continue to 3.f.
1. We need to download Flashtool and use the driver setup. Download Flashtool (unrestrict.li/flashtool) and install it.
2. Find cmd.exe, right click it, and select Run as administrator.
a. Type in
Code:
bcdedit /set testsigning on
and press enter.
b. Reboot your computer.​3. Once you have rebooted the computer, open the folder where you installed Flashtool (default: C:\Flashtool).
4. Open up the drivers folder and open Flashtool-drivers.exe.
5. Select the first two driver choices (Flashmode and Fastboot) and select “Xperia Tablet Z Drivers” and continue.
6. A new window will appear, continue on with that.
7. A window like this may appear a few times, just press Install this driver software anyway.
8. Run 3.e.2. again and run
Code:
bcdedit /set testsigning off
. Reboot your PC now or after the tutorial.​f. The LED pulse light above it should be emitting a blue-ish color. The screen will be dark.​4. Now we’ll verify if you have fastboot running.
a. Open the tools folder that was extracted from the ADB ZIP and double-click on START.cmd to open Command Prompt in the current directory (all it does is literally open cmd.exe, you can edit the script to verify).
b. Run the command
Code:
fastboot -i 0x0fce getvar version
. If you get
Code:
<waiting for device>
, then you did something wrong. Retrace your steps! (For example, I get
Code:
version: 0.5
)​5. Go to (unlockbootloader.sonymobile.com) and continue until you reach the screen where you put type in the IMEI and an email address. Type in the first 14 digits of the IMEI (remove the last one) and your email address (not sure if name is required). You should get an email instantly with the key.
6. In the Command Prompt, run
Code:
fastboot -i 0x0fce oem unlock 0xKEY
where KEY is the key you received in the email from Sony.
7. Download whatever release you would like to use on the tablet (I’m using CM 11 nightly) from (download.cyanogenmod.org/?device=pollux)
a. Optional: Also download gapps for Google apps such as Gmail, Google Play Services, etc. (wiki.cyanogenmod.org/w/Google_Apps)​8. Extract the ZIP file (but don’t delete it either) and copy boot.img to the tools folder.
9. If your device is still turned off, turn it on and enable USB storage mode. Copy the CM zip to either the internal storage (sdcard) or, if one is inserted, the microSD card (sdcard1).
10. Place it into fastboot mode again (#3).
11. Go back into the Command Prompt and enter:
a.
Code:
fastboot -i 0xfce flash boot boot.img
b.
Code:
fastboot -i 0xfce reboot
c. Enter recovery.
1. Once it shuts down, rapidly tap the Vol + button in order to get into the recovery.
2. Grep_The_Truth's tip: Look at the LED. It will turn orange and afterwards it'll turn purple. You want to press Vol+ as soon as it changes colors.​12. Select “wipe data/factory reset” and wipe it. Afterwards, go back to main menu.
13. Select “Install zip” and either select “Choose zip from /sdcard” (internal storage) or “Choose zip from /storage/sdcard1” (microSD card).
I’ve had varying experience with installing from the /sdcard because sometimes it doesn’t want to mount /data while wiping (/data/media which is /sdcard is safe in wipe) the tablet, so if you were to install the zip from /sdcard with the error present, it would screw things up. I prefer the microSD card route (/storage/sdcard1), and you don’t even need a big one. 512MB works just fine. The actual path would be /sdcard/0/ when looking for the cm.zip in the internal storage.
14. When you have chosen to install from either /sdcard or /storage/sdcard1, select the cm.zip and install it.
a. If you downloaded gapps.zip, install it the same way as you did with the cm.zip.​15. Go back to the main menu now and select “reboot system now”
a. Once, I had the option to install root access before rebooting, I declined (was planning on rooting after tutorial) but it gave me root anyway.​
That’s it! You can now use CyanogenMod with the Sony Xperia Tablet Z.
Getting in to recopvery
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
c. Once it shuts down, rapidly tap the
Code:
Vol +
button in order to get into the recovery.
Click to expand...
Click to collapse
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.
Grep_The_Truth said:
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.
Click to expand...
Click to collapse
I'll add it along with mine, because I can do it with no problem.
alexpja said:
I'll add it along with mine, because I can do it with no problem.
Click to expand...
Click to collapse
alexpja Thanks for your tutorial, this is very detailed and easy to follow.
my Xperia is SGP321.
I put it into practice and the results it gives me the "oem unlock" is:
FAILED: (remote: Command nor allowed).
I guess you should treat my tablet has the bootloader locked and not allowed (for now??) the unlocked.
I hope someone gives us the opportunity to unlock the devices and in the future can be unlocked.
I had the same experience where at times the steps were a little confusing, especially for a beginner. Each set of instructions would either leave something out or skim over it as if everyone already knew it. That's understandable since they were probably written for that audience. I soft-bricked my SGP311 at least 10 times.
I was even going to write something like this but I got lazy.
One suggestion I would offer is to request the bootloader unlock key first since it sometimes takes a little while and a person can reduce the possibility of having to stop and wait just when they are making progress.
And for anyone going this route for the first time, don't make my mistake - flash exactly what the instructions say to flash, particularly boot.img. Once you have that recovery flashed you have a lot more control over your device. If something goes wrong in a following step like getting boot loops you can still fix it. But if you get annoyed and start poking at it then you can mess up the recovery. Then you have to reset everything to stock and just about start over.
While I don't want to say something stupid like claiming the tablet is indestructible, I found that whether I got stuck in a boot loop I couldn't get out of or screwed it up so bad that all I could get from the tablet was an occasional LED flash, I could always restore it using Emma. It's annoying to have to start all over but it's a huge relief when it boots normally.
for me flashing was fine and without any error but my Tab doesn't boot up with CM flashed...any idea?
Hanging at reboot
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.
Guess my bootloader won't be unlocked. This is A lot of work. Good job on the write up though maybe one day I'll tackle it.
BOOT LOOP Step 9
All was going well, but step 9 powering on device, now its looping.....Ill use flash tools to put jelly bean on and try again, since i was trying with kitkat...why i suspect kitkat is the issue, before i used to be able to unlock and lock boot-loader with jelly bean but with kitkat it didn't work, which i then forced it via cmd
No GPS
I used the tutorial for my Pollux Windy (WiFi Only) and used the latest nightly. everything went well but my GPS is now broken. Is this a known issue?
kevinsickles said:
Is this a known issue?
Click to expand...
Click to collapse
yep! use search to find out more.
mulebreath said:
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.
Click to expand...
Click to collapse
Hi,
I've been trying with my Xperia Tablet Z Wi-Fi SGP311. Ran into the same problem. On reboot command the LED was stuck on red for 10 minutes and the cmd window was still open. I unplugged the USB and the LED would not turn off. Tried some things, I don't remember specifically what, but it got the LED to turn off. Now my device can't be detected. I've downloaded Emma and it is not recognising my tablet. I've tried to plug the USB in while hold Vol +, Vol -, and the Power button. No detection for any. All I can do with my tablet is make the LED flash white, purple and red in rapid succession by holding Vol + and Power for 5 seconds.
Anyone know what's happened? I suspect I've completely bricked it :L
EDIT: Apparently there are different modes which you can cycle through. If you hold down Vol + and Power for 5 seconds, the LED will flash according to which mode the tablet is in. The different modes give these flashes:
- 1 White flash
- 3 Rapid which flashes
- A white, purple and red flash in quick succession
To switch between the modes, I hold down Vol+ and Power, and after 5 seconds it will take around 3 more seconds to change modes. One of these modes will not appear unless plugged into a PC. What do these mean and can I do anything with it? Tablet is still bricked.
EDIT2: I've managed to get Emma to recognise my tablet. Turns out the modes do have different purposes. I should be fine now, problem solved. I will just leave the solution here in case anyone runs into the same problem.
Unplug your device and hold Vol + and Power for 10 seconds. At the 5 second mark your LED should flash white ONCE. Keep both buttons held and within 5 more seconds, your LED will flash white THREE times consecutively. This will allow you to enter Flashmode (plug in USB while holding Vol -) and Fastboot (plug in USB while holding Vol +). For Emma to recognise your device, enter Flashmode and you can restore and try again.
Bootloop
I've tried many times to flash cyanogenmod onto my Xperia Tablet Z (SGP311). This is a Wi-Fi only tablet and I have downloaded the versions of CM from (download.cyanogenmod.org/?device=pollux_windy) I've followed all of the steps and tried all of the versions of CM down to 10.2 (I used GApps10.2 for CM10.2). Each version gets stuck in bootloop. I've cleared all data (in CWM - wipe data/factory reset, wipe cache partition, wipe delvik cache) before flashing CM and GApps; however, when I try to clear data I get an error. This is what the tablet says:
-- Wiping Data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cacha
Formatting /sd-ext...
Formatting /sdcard/.android_secure!
Skiiping format...
Data wipe complete.
Click to expand...
Click to collapse
I'm thinking the "Error mounting /data" is the problem, but I'm not entirely sure, nor am I sure of how to fix it.
Any suggestions?
EDIT: Turns out I'm just really bad with Android stuff. I ended up flashing the original Xperia software, unlocking the bootloader (according to this tutorial's instructions), then I downgraded to 4.1.2, rooted my tablet (forum.xda-developers.com/showpost.php?p=53063218&postcount=14) and installed the PhilZ and TWRP custom recoveries. I didn't get to use them in the end. For some reason CWM kept coming up no matter what combination of buttons I pressed while rebooting. After downgrading and rebooting, I followed the rest of the instructions on this tutorial (from step 7). This time I got no errors while cleaning the disk, cache and delvik cache. Flashed the zip files, rebooted the device and voila, Cyanogenmod11!
Again, I'll leave this edit here in case someone runs into a similar problem. I couldn't get any version of CM until I rooted first.
I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
tp_88 said:
I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
Click to expand...
Click to collapse
download a proper stock (not bricked) firmware for your device and flash with flashtool.
Rootk1t said:
download a proper stock (not bricked) firmware for your device and flash with flashtool.
Click to expand...
Click to collapse
What makes you think that the stock firmwares I've tried are bricked? I've since my post tried one which I downloaded through Flashtool - same result.

Categories

Resources