Note 3 [N9005] Screen Flickering Issues - Galaxy Note 3 Q&A, Help & Troubleshooting

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!!

Related

Phone messed up?

Try this I did and it worked to get mine booting after a bad update.
I messed around with it using several methods of getting it to boot into download mode until I finally got it to do it. I think I left it plugged into the USB, powered it down until I saw the charging screen, then I proceeded to play with the different ways to hold the buttons to get it to download mode. If you are persistent enough and read a little on booting methods to get bricked phone into download mode you will succed if not then your not for the world of trial and error... the main thing is do the first steps I said before until it works
1. Get into Download Mode (WITH THE PHONE PLUGGED IN) by following the steps below
*Turn off the phone until you get to the charging battery screen (keep in mind, your phone is currently PLUGGED IN)
*Press volume up and down, and power all at once.
*As soon as the screen turns black, release your power button.
2. Unplug phone from USB
or try
2. Remove everything from your phone (SD card, sim, battery).
3. Plug your phone into your computer WITHOUT the battery, as you have already taken it out in the last step.
4. Press and HOLD vol. up and vol. down.
5. As you are HOLDING these buttons, reattach your battery.
6. You should be in Download Mode.
7. Unplug phone from USB
any how try try try until it works
Once in download mode
Get your files together for your phone, and use Odin 1.85.
Plug into Odin and make sure it shows yellow and its added!
1. Now if your files have like 3 files and the exact .pit file for your phone
I found mine here
http://www.droidevelopers.com/showthread.php?11722-Download-OPS-amp-PIT-files
2. Click the PIT button and browse to your exact .pit file for your phone *It should now have added a check in the re-partition box under the options area of the Odin window. If not CHECK IT!
***If you don't have your .pit don't worry about this unless you suspect, or have a bad partition
3. If you have just 1 file just click the PDA button and load the file. If you have 3 then you will load the PDA file in PDA, the Modem file into PHONE, and the CSC file into CSC, there are way too many phones to link all the files so get you stuff together!
4. Now hit start.
5. When done and the phone shows the first sign of starting up IE Logo or whatever... immediately unplug the battery from the phone to shut it down.
6. Now put it back in and start it in Upload mode by pressing Vol Up, Home at the same time then the Power button.
7. As soon as the phone shows the first sign of starting up IE Logo or whatever let go of all buttons and using the Vol Up down Choose the Clear Cache option and go through and make sure you factory reset it if you can just for good measure.
8. Reboot
9. Now when the phone shows the first sign of starting up IE Logo or whatever take out battery again to power off
10. Now put it back in and start it in Download mode by pressing Vol Down, Home at the same time then the Power button.
11. Once in download mode Hook up to Odin again and flash it with a root kernel for your phone. Do not ask me just find it. I did it took time but I got all the files together over several days of reading and collecting the correct ones.
12. When done and the phone shows the first sign of starting up IE Logo or whatever... immediately unplug the battery from the phone to shut it down.
13. Now put it back in and start it in Upload mode by pressing Vol Up, Home at the same time then the Power button.
14. In most roots you will now have a advanced or mounting options and more options to use.
15. I cleared the Cache again, Cleared the Davilik Cache, Went into a option and actually mounted the cache formatted the Cache.
16. Use the option now to restart the phone...
And mine started up installed the apps and I am up and running, nice and smooth and no issues so far
I hope this helps out someone whos just about to go off the deep end, as I was there and patience and trial and error came up with this step by step way to recover mine. Thank me by hitting the little thumbs up THANKS button below this post.
And if your so happy your phone is up show your appreciation by buying me a Pepsi
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=E6M7UWKCZYSNE
scottsdesk
http://forum.xda-developers.com/showthread.php?t=1924233
Not sure why you created 2 threads.
Closed

My fix works for your messed up phone!!!

Try this I did and it worked to get mine booting after a bad
update.
I messed around with it using several methods of getting it to
boot into download mode until I finally got it to do it. I think
I left it plugged into the USB, powered it down until I saw the
charging screen, then I proceeded to play with the different ways
to hold the buttons to get it to download mode. If you are
persistent enough and read a little on booting methods to get
bricked phone into download mode you will succed if not then your
not for the world of trial and error... the main thing is do the
first steps I said before until it works
1. Get into Download Mode (WITH THE PHONE PLUGGED IN) by
following the steps below
*Turn off the phone until you get to the charging battery screen
(keep in mind, your phone is currently PLUGGED IN)
*Press volume up and down, and power all at once.
*As soon as the screen turns black, release your power button.
2. Unplug phone from USB
or try
2. Remove everything from your phone (SD card, sim, battery).
3. Plug your phone into your computer WITHOUT the battery, as you
have already taken it out in the last step.
4. Press and HOLD vol. up and vol. down.
5. As you are HOLDING these buttons, reattach your battery.
6. You should be in Download Mode.
7. Unplug phone from USB
any how try try try until it works
Once in download mode
Get your files together for your phone, and use Odin 1.85.
Plug into Odin and make sure it shows yellow and its added!
1. Now if your files have like 3 files and the exact .pit file
for your phone
I found mine here
http://www.droidevelopers.com/showthread.php?
11722-Download-OPS-amp-PIT-files
2. Click the PIT button and browse to your exact .pit file for
your phone *It should now have added a check in the re-partition
box under the options area of the Odin window. If not CHECK IT!
***If you don't have your .pit don't worry about this unless you
suspect, or have a bad partition
3. If you have just 1 file just click the PDA button and load the
file. If you have 3 then you will load the PDA file in PDA, the
Modem file into PHONE, and the CSC file into CSC, there are way
too many phones to link all the files so get you stuff together!
4. Now hit start.
5. When done and the phone shows the first sign of starting up IE
Logo or whatever... immediately unplug the battery from the phone
to shut it down.
6. Now put it back in and start it in Upload mode by pressing Vol
Up, Home at the same time then the Power button.
7. As soon as the phone shows the first sign of starting up IE
Logo or whatever let go of all buttons and using the Vol Up down
Choose the Clear Cache option and go through and make sure you
factory reset it if you can just for good measure.
8. Reboot
9. Now when the phone shows the first sign of starting up IE Logo
or whatever take out battery again to power off
10. Now put it back in and start it in Download mode by pressing
Vol Down, Home at the same time then the Power button.
11. Once in download mode Hook up to Odin again and flash it with
a root kernel for your phone. Do not ask me just find it. I did
it took time but I got all the files together over several days
of reading and collecting the correct ones.
12. When done and the phone shows the first sign of starting up
IE Logo or whatever... immediately unplug the battery from the
phone to shut it down.
13. Now put it back in and start it in Upload mode by pressing
Vol Up, Home at the same time then the Power button.
14. In most roots you will now have a advanced or mounting
options and more options to use.
15. I cleared the Cache again, Cleared the Davilik Cache, Went
into a option and actually mounted the cache formatted the Cache.
16. Use the option now to restart the phone...
And mine started up installed the apps and I am up and running,
nice and smooth and no issues so far
I hope this helps out someone whos just about to go off the deep
end, as I was there and patience and trial and error came up with
this step by step way to recover mine. Thank me by hitting the
little thumbs up THANKS button below this post.
And if your so happy your phone is up show your appreciation by
buying me a Pepsi
https://www.paypal.com/cgi-bin/webscr?cm
d=_s-xclick&hosted_button_id=E6M7UWKCZYSNE
scottsdesk
Lots of good advices. I Got to Save them some where and hope that i don't Need them.
... slaycio
Button issue or startup bugs in ICS 4.0.4 ROOTED CWM
Try this
I am running ICS 4.0.4 and Rooted w/CWM just so you know...
Make sure and add this to the end of my guide above as I was having a small issue and this cleared it up
1. Go into recovery mode, wipe cache partition
2. Under mounts and storage, unmount all and format cache
3. Under the advanced, wipe dalvik cache, and battery and fix permissions
4. Reboot
hope this works it fixed mine...
And if your so happy your phone is up show your appreciation by buying me a Pepsi
https://www.paypal.com/cgi-bin/websc...=E6M7UWKCZYSNE
scottsdesk

[ROOT] I can't root my GN3

Hi
For the beginning i want to say thx to the people who will try help me.
Samsung Note 3 SM-9005
Rom: NB3 4.4.2 (kitkat)
I should post it as a reply to the chainfire's post on cf auto root but i can't cause i am a new on xda (and he didn't allow me )
So what is my problem ?
When i tried root with CF all is ok but when odin say 'PASS' there is no recovery boot (the install process, the red android logo)
What i have ? > After my flash my phone try to boot (with Se Enforcing + 2 other stuff blue red and yellow i guess) but my phone can't boot (yes even boot) he only reset and try re-booting.
chainfire's say
*NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.*
Click to expand...
Click to collapse
So i tried it, i unchecked the auto-boot, flash my phone pull the battery and press the button (without the battery), and after my phone turn off.
When i turn on >> same issue boot loop all time
And to have access on the phone i must go on the downlaod mode and click restard phone...
Well if u could help me .... 90% of my app require root x) :laugh:
Is this the file you used? There's 2 files, one for 4.4 and the other for 4.3. Try flashing the file again.
Yes i used this file
i forgot to say that kingo root is so buged i mean i try also to root with him (on 1s)
He put my phone on download, install the recovery ect
Result: a fake root, in fact even if i have SuperSU (he installed) He said me that i have no binnary installed
I also checked on "Root Checked" no root here
BUT on download mode: custom os + custom binnary
And his chinese recovery work
1 hour ago i used my GN2 to see if maybe it's my computed who have issue with kingo root
Result: Root perfectly my phone
I also forgot to say that i used different odin (1.85,3.09 ect) on admin
And i tried the NA6's rom (maybe was the rom ^^' but nop still no root)
French's user said:
Hi
So i tried it, i unchecked the auto-boot, flash my phone pull the battery and press the button (without the battery), and after my phone turn off.
When i turn on >> same issue boot loop all time
And to have access on the phone i must go on the downlaod mode and click restard phone...
Well if u could help me .... 90% of my app require root x) :laugh:
Click to expand...
Click to collapse
I re-read your reply and I'm a little confused. Did you pressed all buttons after removing the battery? Also, there is no restart phone in download mode, you can only get out of download mode by pressing power button for a few seconds or remove the battery.
Lastly, maybe check you have the correct samsung usb drivers and reactivation lock is off.
hey_joe said:
I re-read your reply and I'm a little confused. Did you pressed all buttons after removing the battery? Also, there is no restart phone in download mode, you can only get out of download mode by pressing power button for a few seconds or remove the battery.
Lastly, maybe check you have the correct samsung usb drivers and reactivation lock is off.
Click to expand...
Click to collapse
Well i know but i didn't even really understand the process to manually boot the recovery (the chainfire's quote)
what i did ? i flash my phone when odin say "reset" i just pull the battery on the table and next press buttons (Volup+home+power)
My phone turn off i replace the battery and i get the booting loop
Maybe my way to process is wrong, i don't even know chainfire don't really explain in details the way to do it....
For the driver i deleted all and re-installed by kingo but in fact all time my device is detected (in all mode) and COM if alway here (also the flash is correct)
I think maybe my process is badly done (maybe i can't understand cause im french)
Here's how I would normally do it.
- download the file and extract to a folder/location of choice
- put phone in download mode by pressing power + vol down + home button all at the same time until something comes up on the screen then let go of the buttons then press vol up then connect to usb on pc
- go to where you extracted the downloaded file, open odin and put the tar.md5 file in the PDA slot and click start
Odin will flash file and automatically restart to apply root ( red android with red letters ) then restart again to android.
OMG dude that work thx to you :laugh::laugh::laugh::laugh::laugh::laugh:
Ok the last post i mean i didn't understand the process of the boot recovery manually (with autoboot unchecked)
But i least this time i used a different thing- what ?- A nokia usb cable
And this time that work and im sure before i did all u said to me.
I worked on 2 night x)x)
Anyway dude thx to help me
No problem.
Enjoy your phone :good:

[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.

[GUIDE/FIX] {S4-MULTI} No Sound &/ WiFi &/ Bluetooth After Unbrick/Update? Read Me!

[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

Categories

Resources