yashsingh1/xdaforums huggingface dataset:
[G2 Q&A, Help & Troubleshooting] phatmanxxl:
Look for Autorec, read carefully.
[G2 Q&A, Help & Troubleshooting] roobns:
I installed it but that's only for installing a recovery right?
[G2 Q&A, Help & Troubleshooting] Qverse:
look for ioroot to root then autoRec . And always say then to developers for there HARD work. :cool:
[G2 Q&A, Help & Troubleshooting] roobns:
thnks man, i already have rooted and TWRP then flash philz and stuff. Problem is i can't baclkup my EFS because it always give me no files not even the flashable zip, or the cmds so i guess it's the lg security it's messing up. So i wondered if the bootloader can be unlocked to get rid of that security
[G2 Q&A, Help & Troubleshooting] simon_lefisch:
This has been answered many times. You CANNOT unlock the bootloader. Loki is only a work around that will allow custom recovery/ROMs/kernels to work. We will most likely never get an unlocked bootloader.
[G2 Q&A, Help & Troubleshooting] simon_lefisch:
http://www.androidpolice.com/2013/0...d-bootloader-on-att-and-verizon-lg-g2-models/
[Galaxy S 4 Q&A, Help & Troubleshooting] maisterbackel:
Hi guys, not sure if this is the right place to post this, but I've tried everything and am getting desperate.

I was using my phone last night and all of a sudden I lost service. I can not get it back whatever I try, I can see other network operators just not mine.

Here is my setup:

Phone: Galaxy S4 (SGH-I337M)

Carrier: Wind

CM: 11

I tried everything, factory reset, I tried installing CM 11, 10. 2. 1, 10. 2. 0 10. 1. 3 (stable jfltecan's) same problem on all of them. The strange thing is it worked fine, I was in the middle of installing a new game and everything went to hell.

I did some research and saw that a simple solution is to change your CDMA subscription from NV to RUIM/SIM. Tried that, the only problem is it seems to be stuck on NV, I switch to the other one but when I go back to the menu it's still on NV.

This is driving me nuts, I've tried everything I could find. Please help guys, you're my only hope :(
[Galaxy S 4 Q&A, Help & Troubleshooting] maisterbackel:
Bump, anybody? :(
[Sony Xperia M2] comax70:
Hello i buy this phone is very fast..but camera is very wrong [emoji35]

View attachment 2851485
[Sony Xperia M2] darknesseff:
Now camera is better with Kit Kat!
[Sony Xperia M2] starterz:
Can someone post samples from JB and KitKat? My experiance witgh JB camera is also a yellow-ish glare on the photos using flash. Has this been repaired in KitKat? All best.
[Huawei Ascend P6, Mate] advisernet:
Hi all

Any solution to unlock the CDMA slot ?

I can only work with the GSM Slot! So only the 2G network!

To work with 3G i have to use the CDMA Slot! but it is locked with China Telecom!

It is a very big problem! Any solution?

Whenever I put the cdma sim I got no service.

Thanks a lot!
[Nexus 4 Accessories] Mademos:
Anyone got any suggestions? External batteries attached on phone with duct-tape don't count.

Sent from my Nexus 4
[Nexus 4 Accessories] fahadsul3man:
http://xdaforums.com/nexus-4/general/4200mah-nexus-4-internal-battery-t2239829
[Nexus 4 Accessories] Abby Oddie:
Keeping your Phone in a battery case while traveling may provide an extra benefit, since almost all such cases rely on Micro-USB cables for charging—you may well have other devices that can share the same charging cable, and replacement Micro-USB cables are far cheaper than Lightning cables.
[Nexus 4 Accessories] prasanth21:
I remember one for the nexus 4. But it was real ugly and made your phone gigantic. I really dont think there are really many more options.

Nevertheless, if you're that desperate heres the link.

http://www.androidcentral.com/review-zerolemon-nexus-4-juicer-removable-battery-case

Hope this helps!
[Nexus 4 Accessories] Planterz:
Good luck finding one.

There's the Mugen Power Extended 4500mAh. You can find them on eBay and Amazon. But it's rather expensive ($90-95) and freaking huge. Nice big battery though.
[Nexus 4 Accessories] Colinp123:
Mugen Power 4500mah

I have a MugenPower battery case that i don't use. Works great, PM me if interested.
[Nexus 4 Accessories] blentavi:
have you an link?
[Nexus 4 Accessories] Colinp123:
http://www.mugenbattery.com/mugen-power-extended-4500mah-battery-case-for-lg-nexus-4/
[Nexus 4 Accessories] blentavi:
Thanks for the link.
[Galaxy S I9000 Q&A, Help & Troubleshooting] reatman:
Hello everybody,

I'm trying to get a new microSD card (8 GB class 10 microSD HC from Kingston) to work with my GT-I9000 (Custom ROM Mackay CM9 2014 1.7; freshly installed from stock GB). The card doesn't seem to get recognized and is not usable.

In storage settings there's an option to mount an SD card. When I press it, it says 'preparing SD card', after which nothing happens. In WRTP the card is also not recognized. Another SD card (2GB class 4), however, works flawlessly with the current setup.

When connected with my PC via a USB adapter, the 8GB card is recognized and usable without any problems.

I already repartitioned and formatted (FAT32) the card multiple times using Minitool Partition Wizard and Windows 7's formatting tool, as well as SDFormatter.

Does anybody know what might cause this problem? What else can I try to get this card to work??

Thanks in advance.
[Galaxy S I9000 Q&A, Help & Troubleshooting] pryerlee:
Simple Fix for this. Keep in mind that smart phones are

computers and the SD cards are physical memmory and

like hard drives, they require regular maintenance.

First take the SD cad out of the phone.

You will then need to insert it into a PC of some sort. I

had to go out and buy an adapter to insert it in the SD

slot on my laptop. You can usually find a cheap adapter

in any store that sells digital camera supplies. I found

one at Walgreens for $8 with a 2MB micro SD.

Third step (Optional). Copy all the data from the card

into a folder on the PC in order to back up your data.

Fourth Step run a scandisck on the card. In windows

Right click the drive then choose "Properties". Click the

"Tools" Tab and you will find an Error correction section.

Run the error correct and make sure you choose the

"Automatically fix file system errors". This should take

just a couple momments to run. DO NOT CHOOSE THE

BAD SECTOR OPTIONS AS THIS WILL TAKE FOREVER TO

RUN.

Once this is complete. Remove the card from your PC

insert back into the phone and boot up. You should be

all fixed.
[Galaxy S I9000 Q&A, Help & Troubleshooting] reatman:
Thank you for your reply.

I did what you told (plugged the card into my pc with an adapter and ran scandisk, which ran successfully without finding any errors), but the card is still not used by my phone.

Any other suggestions?
[Galaxy S I9000 Q&A, Help & Troubleshooting] pryerlee:
Found this thread http://xdaforums.com/showthread.php?t=601340
[Galaxy S I9000 Q&A, Help & Troubleshooting] reatman:
Thanks for the suggestion. I deleted fsck_msdos, rebooted and tried to mount the card a couple of times, but sadly the problem persists.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Hello everyone, I desperately need help. Like many people I've read about around other forums, I decided to update my Telus Galaxy S3 to KitKat, and used Mobile ODIN, just because I am lazy and I didn't want a locked bootloader(who knows what Samsung might do these days, better be safe than sorry). The phone loaded up, but it told me that there's no SIM card plugged in. So just like all of the horror stories I've read after this terrible mistake, I decided to reboot the phone and possibly install back the 4.3 modem. Well, the shutdown worked perfectly. The restarting part, not so much. The moment I turn the phone off, I realized that I was holding a paperweight which doesn't respond to anything with a single exception being the red LED light going on if I plug it in without the battery inside. Sadly this fits in the every single story I've read AFTER this stupid mistake. Apparently the NE6 modem hard-bricks phones without the appropriate bootloader, and Mobile ODIN refuses to install bootloaders(it just skips them for safety reasons, how ironic that the safety measure bricked my precious?) After around 24 hours of not sleeping and googling every solution I can possibly foresee, I bought an external Micro SD card reader and tried to flash the debrick image files found around the forums(I'm a new user, so I can't link to any of them). Unfortunately, all the debricking files I've found were for the 4.3 software and I've flashed 3 debricking files I found to my card, at least 15-20 times for each image, followed the instructions perfectly, with no sign of life from the phone. What I am wondering is, because I've also read success stories from other carrier forums with a 4.4.2 debricking file and the fact that I couldn't even get my hands on one, maybe that's what people are missing at the moment? So my question is, can someone PLEASE upload a 4.4.2 debricking image for the Canadian Galaxy S3?(SGH-i747M, Telus would be awesome but I'm willing to try anything)

As a side note, I have another idea which may or may not work. I have downloaded the entire stock firmware from SamMobile, and was considering flashing the general 4.3 debrick image, plug the card in a linux box, and dd the bootloader mbn files located in the tar file downloaded in the appropriate partitions inside the memory card. I am currently giving it a try, and will report on the results. If either of the methods work, we can save dozens of S3's falling to the wrong hands of Samsung, without a JTAG! I could've paid for a JTAG because I can't afford a new phone due to the fact that I'm heading to college next year and my family is in serious bank debt, but here in Turkey, barely anyone knows how to JTAG and every phone repair shop would try to rip you off majorly(I was an exchange student, that's why I have the Canadian phone).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Failure

I have wrote the debrick_v4.3_SGH-I747M-UEMK5.img file I've found on this forum in a Micro SD card, extracted the I747MVLUFNE6_I747MOYBFNE6_I747MVLUFNE6_HOME.tar.md5 file I've downloaded from SamMobile and copied out the aboot, sbl2, sbl3, tz, rpm, and NON-HLOS (the modem file). Booted up my OS X partition and used dd to flash all the files in the appropriate partition on the memory card using this partition table I found on another forum:

Mount Point Start End Size File-System Name

__________________________________________________ ___

/dev/block/mmcblk0p1 4194kB 67.1MB 62.9MB modem

/dev/block/mmcblk0p2 67.1MB 67.2MB 131kB sbl1

/dev/block/mmcblk0p3 67.2MB 67.5MB 262kB sbl2

/dev/block/mmcblk0p4 67.5MB 68.0MB 524kB sbl3

/dev/block/mmcblk0p5 68.0MB 70.1MB 2097kB aboot

/dev/block/mmcblk0p6 70.1MB 70.6MB 524kB rpm

/dev/block/mmcblk0p7 70.6MB 81.1MB 10.5MB boot

/dev/block/mmcblk0p8 81.1MB 81.7MB 524kB tz

/dev/block/mmcblk0p9 81.7MB 82.2MB 524kB pad

/dev/block/mmcblk0p10 82.2MB 92.7MB 10.5MB param

/dev/block/mmcblk0p11 92.7MB 107MB 14.3MB ext4 efs

/dev/block/mmcblk0p12 107MB 110MB 3146kB modemst1

/dev/block/mmcblk0p13 110MB 113MB 3146kB modemst2

/dev/block/mmcblk0p14 113MB 1686MB 1573MB ext4 system

/dev/block/mmcblk0p15 1686MB 14.8GB 13.1GB ext4 userdata

/dev/block/mmcblk0p16 14.8GB 14.8GB 8389kB ext4 persist

/dev/block/mmcblk0p17 14.8GB 15.7GB 881MB ext4 cache

/dev/block/mmcblk0p18 15.7GB 15.7GB 10.5MB recovery

/dev/block/mmcblk0p19 15.7GB 15.7GB 10.5MB fota

/dev/block/mmcblk0p20 15.7GB 15.7GB 21.0MB ext4 carrier

/dev/block/mmcblk0p21 15.7GB 15.7GB 6291kB backup

/dev/block/mmcblk0p22 15.7GB 15.7GB 3146kB fsg

/dev/block/mmcblk0p23 15.7GB 15.7GB 8192B ssd

/dev/block/mmcblk0p24 15.7GB 15.8GB 5243kB grow

Unfortunately, there is still no sign of life on the phone with the card in place, and nothing has changed. I'm still desperately waiting for ideas, or a debrick image for the 4.4.2 software. In my opinion, Chainfire should've added a check on Mobile ODIN to see if the person is flashing 4.4.2 with the 4.3 bootloader, since it's so widely known that the combination certainly causes an irreversible hard brick. Not to mention there almost certainly is Samsung's mockery with the modem/bootloader software which more than likely caused the brick intentionally.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
No ones been able to fix this kind of brick yet. Just keep watching the debrick thread and hopefully we'll figure out something soon. There are 4.4 2 and 4 3 images in the thread. You just have to search them out.

You won't be able to use adb to dd those partitions while its bricked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I wasn't trying to dd the partitions in the phone while it's bricked. I thought about a clever idea of using a 4.3 debrick image and to dd the individual files from the stock firmware inside the appropriate partitions of the SD CARD, not the phone, so that the debrick card contains the 4.4.2 bootloader/modem/everything. Unfortunately, it didn't do anything major. And I have been searching everywhere for the past two days, and the only 4.4.2 debrick image I've found was for the SGH-i747, not the SGH-i747M, and if you have found something else, can you please share it with me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Sorry. Missed that you had the I747M. But if you can get the phone to boot from the debrick sdcard, its probably much easier and safer to just flash the firmware via odin or flash twrp then use it to flash one of the recovery firmware packages. Using dd should only be necessary if needing to fix a partition not included in the firmware. This is never really needed unless someone flashes something like another devices kernel or modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
That's the problem right there. I can't get the phone to boot literally anything. I don't have a debrick image for my phone, so I was going to use a 4.3 image and make it boot. You know, the debrick image is like a mirrored copy of the S3's whole eMMC, with most of the useless parts omitted, and it just includes the bootloader to boot from. The S3's CPU is designed to boot from the SD card if the eMMC fails to boot, so it works perfectly just to load the bootloader, which leads to an ODIN flash. What I was trying to do was to use a debrick image, and use the dd to copy the 4.4 bootloader and modem inside the needed partitions in the SD card, again, it's not the phone I'm dd'ing to, it's the SD card. Unfortunately, that also didn't work. Now I just need more ideas, and/or a 4.4 debrick image.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Unfortunately we have not found a way to debrick a device that hard bricked by flashing the 4.4.2 modem on 4.3. No idea why its not working....

But we have also not been able to get an I747M image. So I'd like to see some one make one for you guys just to see if it might work.

Like I said before, keep watch on the debrick thread. And if you know anyone with the same model ask them to create the img.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I understand. Just a question out of nowhere, if I was able to find someone to JTAG the phone, even though it's extremely hard given my circumstances, would it still not load up? I can't afford a new phone and I'm studying abroad so being phoneless is like a death sentence to me :crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I have found a zip file which will create a debrick.img on your internal device storage when flashed, it was located in http://xdaforums.com/showthread.php?t=2625332 I realize that it's for a different phone, but it doesn't really matter because what it does is device independent, it doesn't actually 'flash' anything to the phone. I have checked the updater-script and it's completely safe.

So, if anyone has a SGH-i747M running the latest software, practically any Canadian Galaxy S3 with KitKat installed, PLEASE flash this file and post the debrick.img located in your internal storage! It will not actually flash anything to the phone, it will just copy a small portion of the entire eMMC and save it as a file. This can save mine and many other people's phones from the KitKat's wrath, and it's a very short process!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Ive posted a script in the debrick thread a couple weeks ago. Its one I made to use for the T999 several months ago so it might be a better option since its more closely related. Ill take a look at this one too though in case anything is done differently that can give me any ideas.

Note that it has not worked on the I747 yet though. I am working with KAsp3rd on a script that will create the image a bit differently though, so hopefully we will figure this out before too long!

I still recommend trying the one available on the I747M though. You never know!

---------- Post added at 01:58 PM ---------- Previous post was at 01:54 PM ----------

Lol! Shoulda read the op of the link you posted first! The script they are using looks to be the one I originally made! Nice to see its getting around! It probably won't be giving me any new ideas though...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I've read some success stories on the debricking thread, and the fact that the i747 has a locked bootloader after 4.3 while Canadian phones have more mercy to their users, I'd say that there's a good chance of it working. I have a couple of questions to you though, one is why did the phone boot up to a perfectly usable state when I first flashed the modem(entire firmware minus the bootloader), while telling me that no SIM cards were inserted, and a hard brick happened after a reboot? Did the modem firmware overwrite the bootloader or something while the phone is running? And my other question is, if I actually found someone who could JTAG the phone(these people can't even pronounciate JTAG, I don't know what my chances are) would this fix the phone? Or did Samsung encrypt or hash the bootloader after the 4.4 update? I've read somewhere that the bootloaders are hashed with the IMEI number, and that JTAG is even useless now, but I'm not sure about the credibility of the place I've read it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
The I747 bootloader isn't locked. People confuse the changes made for knox with locking it. A locked bootloader prevents you from flashing any recovery or kernel. The only thing we are now "locked" out of is firmware downgrades. But this is true for all S3's after 4.3. So while the Canadian carriers may be a bit more lenient with what they want restricted, it won't have any bearing on this because its directly due to Samsung's Knox.

As for why it boots the first time and bricks on reboot, I dont think anyone knows. My best guess is some issue with knox seeing it modified after its fully booted. It might then try to adjust some value or resolve some sort of incompatibility and in doing so inadvertently causes a brick when the system tries to read/use this during boot. It probably was not designed to do this intentionally, but was also not tested with this scenario.

For jtag, I cant say positively yet. One person reported there were major issues and it couldn't be fully recovered. Another said theirs worked fine, but im not sure they bricked due to the modem. If you do try this, just make sure they guarantee their work and will refund your money if its not 100% fixed.

They do use hashes to check the IMEI and NV Data, and I believe they've done so since the S3 was first released, maybe earlier. If jtag doesn't work, I dont believe this would be the cause.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I can swear I've read quite a few things involving LOKI patches for the i747, and that Canadians are spared from it. That's why I thought there are some sort of restrictions on it. Anyway, I'll get my phone JTAG'ed in a few days and will surely report back on both this and the debrick thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I have really bad news to anyone hoping to get out of this mess with a simple JTAG. I have contacted a phone repair shop today(don't get me wrong, they can barely say the word JTAG, so it would be nice to have someone else trying to get a JTAG done), left my phone for an hour for them to complete the operation, and they told me that the eMMC is toast and has to be replaced. Apparently the JTAG program tells them that the eMMC is shown as zero bytes, making them unable to flash anything. I have flashed quite a bit, but have never done anything potentially dangerous to the chip besides installing the 4.4.2 firmware using Mobile ODIN, which is causing the brick as it doesn't flash the bootloader. Samsung seems to have really messed something up with the KNOX crap they're pushing at our phones, and I do not appreciate this happening. I cannot live without a phone since I'm studying abroad and I am taking a bank loan to be able to pay for a new phone(phone prices are absolutely ridiculous where I live). I am even considering legal action at this point because the brick is not accidental, there has to be some sort of intention to write something potentially dangerous to the phone's bootloader from a simple modem, not to mention the eMMC chip becoming toast right after the flashing, and many people's phones are becoming toast because Samsung's clumsiness. Sadly enough Samsung doesn't even fix the i9300's with SDS here, regardless if you're under warranty or not. My apologies for the rant, but can someone please report if they ever resort to JTAG?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danchise77:
Wow...Same issue here. I have tried every option in the debrick thread with no luck. Good to see that there are still people attempting to address this issue. Even though I have a new device I will continue to try and fix this as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I have also bought a new device, but I'm considering an eMMC change on the old device to gift if to my mother. Shame on Samsung for such a messed up software, JTAG didn't even fix it so this has to be somehow intentional. No software can 'accidentally' fry an eMMC chip.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danchise77:
WOW evern with the JTAG huh? I was just about to send mine out..Thank God you said something. I am going to look into getting a new chip as well. Thanks for the heads up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
No worries, I actually mentioned about it on a previous post in this thread. But again as I mentioned there, the phone repair shops around where I live don't even know how to pronounciate JTAG, so I'd strongly suggest you send it off anyway, given the service has a money back guarantee. It might be helpful to tell your repair service that the JTAG operation on my phone reported that there was 0 bytes available in the eMMC chip.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PaulRoe:
Wondering

I was wondering if this method would work for my sgh i747? I softbricked mine last night but can still force it into download mode(plug into computer take battery out hold vol down and home then put battery back in while still holding buttons) and have had no luck at all with trying to use odin(the methods that i have tried all ended in failing). Im totally new to all this, including this site so im im posting something that has already been answered i apologize, but like i said ive been searching a lot and this actually sounds somewhat promising, just wanted to double check before i screw the phone up more.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
That is for hard bricks only. If itll boot download mode on its own it wont even try to use the sdcard.

When you try flashing in odin, what does it say in its message box?