yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] Naveen_S:
Hey! I recently made the switch over from a Note 3 to a Nexus 6 and I'm really enjoying it. Sadly, i'm having a pretty big issue. My Nexus 6 will not connect to my School's WiFi. I've tired resetting it and literally everything. The phone goes into the WiFi, but when I've to login, the phone won't connect. I've tired doing it through the browser, but chrome won't even let me go into the Login authentication page. I can connect to my home network, but yeah. School WiFi does not seem to work, is there any troubleshoot fix for this?

Thanks in advance!:)
[Nexus 6 Q&A, Help & Troubleshooting] jimmyjoebob:
http://xdaforums.com/nexus-6/help/broken-wifi-peap-android-m-marshmallow-t3221066
[Nexus 6 Q&A, Help & Troubleshooting] Naveen_S:
I'm on 5.1

Thank you
[Android Q&A, Help & Troubleshooting] Rtkhammer:
I rooted it with a method I found on XDA. Worked great! I saw I had an update and wanted to install it. So wanted to unroot with same method. There was an error I disconnected from the computer and this popped up " EFI Hard Drive has been blocked by the current security policy". I shut it off and try to restart it same warning. Try to reboot into recovery mode unsuccessful. Turned it off plugged it in to charge same warning sign comes up. Is there any way to fix this or am I getting a new tablet.

Thanks for reading

rtkhammer
[Android Q&A, Help & Troubleshooting] NoviceForever:
Same here

I am in the exact situation. The diference is that it is my mom's. So I had to buy her the same tablet and not let her know what I did. I don't wanna use it as spare parts for her tablet; I would like to bring it back to life. I have tried through Fastboot commands but always it says that access is blocked.

I need help!
[Android Q&A, Help & Troubleshooting] EviLSAJiB:
Me too bro ;(

It's my, and am still trying but...

Please if anyone know the solving of this problem, please help us
[Android Q&A, Help & Troubleshooting] profi_fahrer:
I know, the answer won't help you any more, because it's late but if anybody has the issue there is a workaround.

1. Turn off the Tablet (Hold the Power-Button 10 sec.)

2. Plug in a OTG-Adapter

3. Plug in a PC-Keyboard

4. Turn on the Tablet and hold the ESC-Kay on the Keyboard

5. Now you are in the BIOS (Yes, the A1-840 has a BIOS)

6. With the Coursors on the Keyboard, go to "Boot"

7. Set the Boot-Device to "EFI and Legacy"

8. Save the changes

9. Reboot

And it works :)

I had the same issue, when I installes CWM
[AT&T LG G3] CLKeenan:
Thought I had it backed up when I installed xposed when it first came out, but apparently I didn't. Using CloudyG3 2.5 + latest xposed3 alpha4 + v75 if it matters. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
So, yea, i bricked my S3... it happened when I was installing a custom ROM HOLD UPP!! It was a ROM that was for my device, and it wasn't caused by flashing the ROM. I formatted /system by accident (yea, I was using TWRP), but the strange thing was, it allowed me to boot once. before I actually went into the 'bricked' state. When I realized I formatted the /sdcard directory, where the custom ROM was stored (yea, call me an idiot), I rebooted so I can reboot to use the browser to download the ROM, but it stayed at this screen, except it didn't say "I9300"

d38v16rqg5mb6e.cloudfront (dot) net/wp-content/uploads/2015/07/Samsung-Galaxy-S31 (dot) jpg

Then I realized that TWRP had an MTP feature so I can transfer the ROM from my computer. So I transferred the ROM, flashed it, and yes, I did a full NANDroid backup, and stored it on my PC. After I clicked reboot, it got into the bricked state. the only signs of life, is when the LED turned red when I plug it in, but that only happens when I take the battery out first, and the phone gets warm when I plug it in.

So I need to know how to unbrick, without a 16 GB SD card. i only have a 2 GB SD. Is there a method to debrick using SD cards less than 16 GB? Is there a way to transfer the boot files to the phone? The phone, when I plug it in to the computer, the computer actually recognizes it, but as qhsusb_dload. what does that mean?

Yea I tried to be as specific as possible, but if you need any more info, ask. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Do you have an i9300? I ask because this forum is for the i747/i747m.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
no its a I747M rogers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
It sounds like you found the debrick thread so I won't go into that. To answer your questions though, aside from that debrick method, the only other option is a jtag repair. There may be a shop near you that can do this, but if not you'll have to send it somewhere.

As for the size of the SD card for the debrick.img, I think I remember hearing once or twice that an 8gb card worked, but I still question if that was true. The idea behind it is the SD card is supposed to be the same size as the devices internal storage, so nothing less than 16gb will work. Can't hurt it to try of course, but don't get your hopes up is all.

QHSUSB_DLOAD = Qualcomm Hi Speed USB Download

It's a definite indicator that a device is hard bricked.

For future reference, I recommend NEVER wiping /system. When you flash a rom that's the first thing that happens anyway, so doing so manually has zero benefit, but all the risk of ending up with a device that has no O/S to boot into.

Sorry to hear that happened. Good luck with it though!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] placroix74:
Debricked mine just yesterday.

The procedure recommends to use a class 10 16GB micro-SD card only, but I managed with a class 4. I really think you ought to try with your 2GB card, as the debrick image is only 80MB. The worst that could happen is that it simply won't boot off the SD card.

In all my browsing on XDA I couldn't make sure to find a certified I747M debrick image, so I made one from my wife's rooted S3 (I747MVLUFNE6) following instructions from this post, and used it to boot mine (I747MVLUFNK2). I used Win32DiskImager (link to it is in the post) to get the image on my SD card. After I got it to boot, I downloaded the stock firmware for my device and used Odin to flash it. It worked just as they said.

I recommend you use Win32DiskImager to backup your SD before writing the debrick image : this will save you 1) copying the files manually and 2) looking for some tool (e.g. SD Formatter) to restore it to its former size (after writing the image, Windows will think the capacity of the SD card is 80MB!).

If you need a I747MVLUFNE6 or I747MVLUFNK2 debrick image, PM me.

Best of luck :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andoridone:
Hello,

First you will need to download correct ATT ROM, and when you install that ROM, you will need to select correct option in ODIN.

To me its look like, you get stuck in boot...

Are you ATT customer?

Let me know, I will post link for Original ATT ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
I flashed the image through my firends phone instead of a sd card reader

so my friend has a kyrocera rise, so i inserted my sd inside, and it showed up the sd card in my pc, and flashed the img, but it didnt work. yea i think the theory about the sd card having to be the same size as the internal storage is true. im going to try writing the img using the reader instead. yea i already backed up the few files i had so that wasnt an issue!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
Not to be rude or anything, but i know what to do about soft bricks. I'm not in that situation. and i have a i747M. that means its Canadian. i also stated earlier it is from rogers. what does having to be a at&t customer have to do with anything, if this is a 2012 phone? The warranty is gone already.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
Yea i wiped /system by accident. but, it allowed me to reboot AFTER i wiped /system, which was weird, and i thought you were supposed to wipe /system. I wonder why the option to wipe /system is there anyway? Also, i flashed the rom already, so wouldnt the /system be written to the parition already? i thought there was a /boot partition..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
I can get my hands on a 16 gb sd cad by sunday, but i was just looking for a unbrick method for a 2 gb sd card. Even if it means i have to keep the (2gb)sd in my pone in order for it to boot, i was looking for a temporary method to unbrick my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
It's a very common mistake. I see it happen way too often. I don't know where or why it got started, but some folks always recommend wiping /system. (Maybe it was required on a specific older device and they carried over to others).

tbh, I can't think of any situation where it's beneficial, so I don't know why is still included in recovery options.

Not sure why it would've booted that one time. I've seen that happen before, but only when flashing the firmware, not just a rom.

If the flash was successful after transferring the new rom via twrp, then you are correct that that the /system partition wouldn't be empty anymore. Maybe the rom was corrupted during the download or transfer?

The boot partition is actually where the kernel is located.

Like I mentioned before, don't get your hopes up using the 2gb card. But by all means give it a shot! Can't hurt anything to try.

Someone mentioned the class of the SD is important. It is recommended to use a class 10, brand name card, but it's not required. I've seen class 4 cards work where class 10 cards failed. I believe it has to do with the transfer speed if the individual SD card. Some class 4/6 cards can actually read/write much faster. Just like some class 10 cards just don't perform as advertised.

Still, the most successful ones have been class 10's, which is why I think many consider it a requirement. Many lower class ones do often fail, but not all. Just something to keep in mind...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
ok thanks. Did anyone report success using a 2 gb card?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Not that I've ever heard. But I doubt many have even tried. I've only seen a couple of reports that it worked with an 8gb card, but as I think I mentioned before, I'm not quite convinced that it was even true.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] placroix74:
Flashing stock firmware to my phone after booting off the SD card into download mode restored the phone's bootloader, but I knew that it was the bootloader I'd messed up.

The posts I've read about debricking this way seemed to mention that the phone would use the bootloader from the SD card, but would finish the booting process from the phone's storage.

If it's really /system you wiped, I wonder what your phone could finish booting from. :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
i think it was because it was given a direct command to be booted into recovery, instead of being booted into system. :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
Im worried when i use the 16gb sd card, THAT wont debrick my phone! All i did was formal /system by accident, and it booted again AFTER i deleted system.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
Also. I'm a noob at Ubuntu and all the "of=/dev/block/mmblk1". I thought it was as simple as

1. insert 16gb SD card and open Win32DiskImager

2. select the debrick.img and flash it

3. insert the SD in the phone and attempt to start it in download mode

BTW i heard that the CPU varient (exynos, quallcom) matters when u debrick the device. i have a SGH-I747M rogers so what CPU variant do i have?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
You have a dual core Qualcomm processor. As long as you are using the correct debrick image, or correct bootloader, modem, or ROM when flashing the processor worries take care of themselves.

You could use either method to flash the img to the sdcard. Win32diskImager could be used on Windows PCs. dd is a command line tool used in Linux to do the same. Brasero would be a GUI tool used in Linux if using the command line concerns you. Using the GUI tools you need to be sure you are 'burning' the image to the media instead of copying the image file. The same would apply to making a bootable usb thumb drive to create a live Linux drive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Unfortunately, it sometimes does not work. More unfortunate, there is no way to know if it will without trying it.

Earlier though, you described a classic hard brick. Red light, QHSUSB_DLOAD.... this method has fixed bricks just like yours plenty of times. More have succeeded than failed. But as I said, it doesn't always work. I think it's definitely worth trying though.

I am convinced that 90% of the failures were due to two things: the sdcard and/or user error. (Mostly the SD though.)

When you do try this method, keep in mind that many people don't get it to work the first few tries. So if it doesn't work, don't give up right away. Try at least 3 or 4 times. This actually happened to me twice! I did everything exactly the same way but it failed until my 3rd or 4th try! No idea why, but I have experienced this firsthand.

Let us know if you have any other questions!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] placroix74:
The SD card won't debrick your phone on its own : it will only allow you to boot into download mode. Successfully flashing stock firmware (which contains a bootloader) from download mode will.

Yeah, I saw those warnings, too. Maybe I was just lucky it worked on the 1st try...

BTW, where did you find a I747M debrick image to flash on your 2GB SD? The only ones I could find were for I747 (US)...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
Yea thats what i mean. So, i need to take out the sd when its in download mode to avoid everything going to the sd.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
The i747 and the i747m are the same model, exept the modems are different. it even sais SGH-I747 on the back of the housing, behind the back cover.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
Also, when i connect the phone to the pc, i press buttons to go to download mode, and it keeps disconnecting and reconnecting. If i leve it alone, that doesnt happen. only when i press buttons.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Hardware - wise, this is pretty much correct, but there may be some very subtle differences that are hard to find.

The T999 also has I747 on its housing, and though the two are very close to identical, they are not. I.e. there are little metal tabs that are built into the plastic housing which connect to pins on the motherboard. some of these are different.

The primary difference between the I747, T999 and their variants is in the firmware though.

How about if you boot download mode first and then connect to the computer?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
If you do as DocHoliday suggests and it continues to disconnecting and reconnecting, you might should check and see if your power button is sticking.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Easy way to check for power button sticking is to remove and reinsert battery. If it tries to turn on by itself the power button is failing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
No the power button isnt sticking. The disconnecting and reconnecting only happens when i press the buttons, not on its own.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
No they are the exact same model, exept some are locked to att, and some are locked to canadian carriers. the T999 is for UTMS (Videotron, wind, mobilicity). I use sgh-i747 ROMS, recoverys, and kernals all the time. also, thats why the sgh i747 and the i747m are in the same forum section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Just don't mix and match their bootloaders and modems. Otherwise, yes, kernels, roms, and recoveries can usually be swapped between the i747 and i747M. I have seen where some devs haven't included the i747M in the updater script. This causes the rom not to flash w/o modifying the script.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
Yea, i modify it myself
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
So we're you able to boot download mode and then plug in?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
Ok, can someone grab some debrick images for the I747M? also, what bootloader do i have? i have 4.4.2 OB1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
might be some here.

http://xdaforums.com/showthread.php?t=2549068

"all i can really do is stay out of my own way and let the will of heaven be done"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
can you create one for me? i have 4.4.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
no. its completely dead
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
How did that happen? Last I recall you could get download mode but it would disconnect if you pressed a button.

When you plug in now, what does the computer say it is?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
no, when i press the button combo to get to download mode, it will reconnect. it never went to download mode
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
I tried flashing about 7 different debrick images on a new 16 gb card. none will work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
i read on a forum that if you flash a custom ROM with a bootloader in it, it will require jtag. i flashed the glamour S5 ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I haven't seen any truly custom ROMs with built in bootloaders and modems, that is not to say it doesn't happen. The only "custom" ROMs I have seen with bootloaders and modems were dumps of stock ROMs. The only thing custom was that they were rooted and had Knox deactivated.

That said, flashing a custom rom from another device even without bootloader and modem could cause serious problems that may require a jtag. Devices have different partition layouts. You may have resized critical partitions with that S5 ROM.

What didn't work with you flashing the debrick images? Would they not burn to the micro sdcard? Would the phone not boot from the debrick image? What exactly happened when starting the phone with the debrick image on the micro sdcard? Did any leds flash? Did anything show up on the screen? Were there any error messages? You tried 7 debrick images, but were they all with the same sdcard?

[MENTION=4081205]DocHoliday77[/MENTION] what do you think, jtag?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
OK, sorry I misunderstood before. I get what you are saying now!

Were any created for a build that was the same as or newer than what you had on the device? I've got two from [MENTION=7040443]placroix74[/MENTION] (hope I got the name right!) He was running 4.4.2 and used a 4.1.1 debrick.img to fix his. Be aware that is the only time I've ever heard of that happening, but I've got copies of the images if you want to try them. The rule for everyone else since 4.3 has been that you MUST use the same or newer build as you had on your device. So don't get over hopeful until we can get a 4.4.2 debrick.img.

You probably already said, but what 4.4.2 build were you on before it bricked?

This is very highly possible. It just depends on what was flashed. I'm not familiar with the S5 setup and partition layout, but it would surprise me to hear they flash more than the system and kernel in a rom. More than likely it flashed the S5 kernel and system to some other partitions on your device.

for example, it could've flashed the system over the param partition and the kernel over efs or sbl1.

If you are lucky, it will be a partition we flash when we update our firmware. If it is not, then it's very likely jtag will be the only possible solution.

If you have a copy of the rom, open and look in the meta-inf folder for the updater-script. Open in Notepad and tell us what mmcblk it flashed the system and kernel to. Only with that information can I say if there's a chance this will work. :fingers-crossed:

Hope that all made sense!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
if luck holds and it is a partition issue you have a PIT for the i747 [MENTION=4081205]DocHoliday77[/MENTION] if needed , yes ? if its gotten lost i have it bookmarked still.:good:

"all i can really do is stay out of my own way and let the will of heaven be done"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
If necessary, I have a pit saved from my i747, let me know if I should attach it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
I've got a repo of .pit files for all the Qualcomm S3's. (Might be missing one or two, but pretty sure I've got the one that'd be needed.)

We will still need to know exactly what partition was flashed though. If it was one that is included with our firmware updates, it'll be much easier to fix. If it's not, well it depends....

For example, if it flashed sbl1, that is not included in the firmware updates. But, it being part of the secondary bootloader we can pull one from another identical device and write it back to the bricked one.

However, if it is something like the efs partition, that cannot be done as it contains data that is specific to each individual device. In a case like that, I believe a jtag service would be the only hope.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rns416:
How to make phone boot without SDCARD (help me plz. )

I debrick everything went well now phone boots into MJB but not without SDCARD. I flash with odin MJB so it should write bootloaders on internal memory but still phone does not boot on its own . I read somewhere, customer recovery flash it with odin then MJB bootloaders flash from recovery then MJB modem. If anyone has any link toshare please about how can i make phone boot on its own without Debrick image on sd card
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
If I follow what you are saying:

1) You can boot the phone when the micro sdcard with MJB debrick image is installed.

2) You tried to flash an MJB rom with Odin, but the phone will not boot without micro sdcard installed.

AT&T never released an official full ROM for MJB, it was an OTA install only. This is why sites like sammobile do not have a download available. Did you find an Odin flashable MJB stock rom on this forum, or maybe elsewhere?

AT this point I would say use Odin to flash a custom recovery (as you stated), the latest from TWRP should work. Try this one : twrp-2.8.7.0-d2att.img.tar 8.5M

From the custom recovery flash the MJB bootloader and modem. enewman17 has the file available on androidfilehost. After that you should be able to boot without the micro sdcard installed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
I was using build OB1 the latest one and i got it OTA

i have the copy of the rom

here is what it says

mount("ext4", "EMMC", "/dev/block/mmcblk0p12", "/data");

if you want the whole script,its at the bottom. i cant copypaste it because its too long

but i think the rom only overwrites some files in /system. i wiped the whole partition. so the essential files got wiped and caused the brick.

also, can you post any imgs that you think will work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MhikeiMPC12:
the /data, /system were flashed. there is also a boot.img in the rom .zip.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rns416:
After Debrick how to boot from internal storage without sdcard

http://xdaforums.com/galaxy-s3-att/help/i747att-signals-t-mobile-cm12-flashed-t3237063/page2