Develop Bugs

[Q] Get out from APX Mode

lsusb:
Bus 002 Device 020: ID 0955:7820 NVidia Corp.
nvflash --sbk 0xF28F1E00 0x14A9C006 0xFBE02404 0x00022103 --sync --go:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)

ZapixAibulatov said:
lsusb:
Bus 002 Device 020: ID 0955:7820 NVidia Corp.
nvflash --sbk 0xF28F1E00 0x14A9C006 0xFBE02404 0x00022103 --sync --go:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Click to expand...
Click to collapse
Asking how to get out of apx mode or saying your trying to use nvflash?
To get out just hold power for like 30 seconds then power on normally. Then stop messing with nvflash unless you have your sbk, in which case I'd love to know how you got it.
Or its a brick and its been forced into apx mode, no way put of it other then turn it off and leave it that way.
Sent from my Galaxy Nexus using Tapatalk 2

pio_masaki said:
Asking how to get out of apx mode or saying your trying to use nvflash?
To get out just hold power for like 30 seconds then power on normally. Then stop messing with nvflash unless you have your sbk, in which case I'd love to know how you got it.
Or its a brick and its been forced into apx mode, no way put of it other then turn it off and leave it that way.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Sorry for digging this topic alive after a lot of time. Trying to go back stock my A100, after flashing the stok image by update.zip, its reset and dont turn on anymore. there's any way of make its back to life??
It's turn only on APX mode with the screen off. Any tool I tried to recover, it's just disconnect from pc and nothing can be done.

thiago.albertodesouza said:
Sorry for digging this topic alive after a lot of time. Trying to go back stock my A100, after flashing the stok image by update.zip, its reset and dont turn on anymore. there's any way of make its back to life??
It's turn only on APX mode with the screen off. Any tool I tried to recover, it's just disconnect from pc and nothing can be done.
Click to expand...
Click to collapse
What you Can do is, contact acer via there facebook page, tell them that your tablet will not boot past the boot logo and that based on your research
this is do to a known issue with the emmc/motherboard being faulty. Also tell them that although your warranty is expired you would expect a company such as acer to back there product in such a case warranty or no
They should Msg. you back and ask for your snid#, "on the back of your external micro sd card slot door" Then they should determine that you are out of warranty but grant you a repair ticket anyway
"All in the assumption that your warranty is indeed expired"
This is exactly what I did/said etc. when dealing with my acer a100-Brick
it Took only 1Wk to get it fixed and returned
All with no warranty and 0$ spent
You should get the same results as I if you follow the above directions.
Good Luck

What you can do (for Acer A100)
Phatboyj420 said:
What you Can do is, contact acer via there facebook page, tell them that your tablet will not boot past the boot logo and that based on your research
this is do to a known issue with the emmc/motherboard being faulty. Also tell them that although your warranty is expired you would expect a company such as acer to back there product in such a case warranty or no
They should Msg. you back and ask for your snid#, "on the back of your external micro sd card slot door" Then they should determine that you are out of warranty but grant you a repair ticket anyway
"All in the assumption that your warranty is indeed expired"
This is exactly what I did/said etc. when dealing with my acer a100-Brick
it Took only 1Wk to get it fixed and returned
All with no warranty and 0$ spent
You should get the same results as I if you follow the above directions.
Good Luck
Click to expand...
Click to collapse
It looks like I am going to have to try this method. Which facebook page should I post too (I think there is more than one)? Also, should I just post it on there wall (were, if so) or should I send them a message (the message button at the top of the facebook page)?
I have been using my tablet for about a 2 year and I love it, it makes me so sad to think that it might not ever work again.
Thanks for the info, and hopefully they will help me even though it is out of warranty

MMC Reset

The eMMC module "crashed" in my Nexus 7, and it got into write-locked mode as much as I can tell.
Actually I get -110 on init, I can't reach the block devices in adb, as it says it's busy.
What I can do:
Get into bootloader mode
Get into recovery mode (The screen stays at TWRP logo, but I can adb shell in it, but I can't read or write the mmc blocks)
Now this is not much help in write locked mode of course, but then I ran into this thread.
I could try the same with my Nexus 7, but I need some help:
Reset command (if there is any) for H26M64003DQR (I guess that's what is inside the 32GB version)
A dump from the boot and some other neccesary partitions.
As an alternative if someone knows the pinouts of eMMC chip I can use to solder to an sd card reader, it would help a lot.
As a second alternative, if anyone knows a way to boot right from usb, it would help too.
If anyone could help me with this, I would be really grateful.

Having the same issue and need help
I'm also having the exact same issue. No access to the eMMC at all -- all attempts to mount or read from it results in I/O error (-110 error when checking via dmesg).
It all happened randomly and I thought it was just a random restart. But after it was stuck for 30 minutes on the Google logo, I found out something was not right.
Does someone have any ideas? I would be **very** interested and grateful if I can get this fixed. The warranty just expired two months ago... :crying:

leoetlino said:
I'm also having the exact same issue. No access to the eMMC at all -- all attempts to mount or read from it results in I/O error (-110 error when checking via dmesg).
It all happened randomly and I thought it was just a random restart. But after it was stuck for 30 minutes on the Google logo, I found out something was not right.
Does someone have any ideas? I would be **very** interested and grateful if I can get this fixed. The warranty just expired two months ago... :crying:
Click to expand...
Click to collapse
I've tried everything, and as far as I can tell, you have 2 options:
Solder a microsd card to the proper pins on the motherboard. (When I looked, nobody knew those pins, maybe there is some development since then)
Buy a new motherboard. - That's what I did, it was about 75$ from eBay. It's working beautifully since.

Xmister said:
I've tried everything, and as far as I can tell, you have 2 options:
Solder a microsd card to the proper pins on the motherboard. (When I looked, nobody knew those pins, maybe there is some development since then)
Buy a new motherboard. - That's what I did, it was about 75$ from eBay. It's working beautifully since.
Click to expand...
Click to collapse
I think I'll buy a new motherboard: is this one [1] okay?
Also, would you mind writing up a quick guide as to how to change the motherboard? I've found a video on YouTube for disassembling but unsure on how to change the motherboard safely. Thanks!
L i n k s (sorry, but there's a restriction; you know what to do with the l i n k s):
[1] www-ebay-fr_itm/ASUS-Google-Nexus-7-tablet-Gen-2-2013-16gb-motherboard-logic-board-100-working-/271623781886
[2] www-youtube-com_watch?v=uv3u78YNUHk

Yes, it's okay.
I've done the disassembling from a youtube video too. Just be careful, the case can be easily cracked on the corners. Memorize(or take photo from) every cable's place. There is a few hidden screws holding parts of the MB you should be aware of, but you'll find them if you search.
It's not that hard, just be patient and gentle.
Good luck!

Thank you! I'll try this and hope I can revive my Nexus 7.

Did you also try booting from a USB flash driver through an OTG cable before replacing the motherboard? I'm just curious what you did end up trying when you say you tried everything.

I'm not the OP, but as I've had the same issue, I can definitely say it wouldn't have helped, since it was a hardware failure.

Hard bricked Xperia M - Help!

Hello all, I have been a lurker for quite a while here. I own an Xperia M (Rooted, Unlocked BL running CM11). I was feeling adventurous and started messing with the partition table hoping to resize the system and data partitions using parted. I was unaware that the bootloader detects such modifications and ended up with a brick.
Just to clarify, this is a hard brick, since the Flashtool and fastboot modes do not work. I do not see the blue LED while trying to start the device in the fastboot mode using the volume rockers. My PC only detects a "QHSUSB_DLOAD" device for which I've installed the drivers and it is now "Qualcomm HS-UDB QDLoader 9008".
However, before I started to work with the partition table, I took a raw backup of the emmc i.e. mmcblk0. This should include the correct partition table and all the partitions (TA, userdata, system etc.). Theoretically (I believe so), if this is reflashed onto the device, an unbrick could be possible. However, so far, I haven't been able to figure out a way to push this image back to the device. I came across QPST and some linux bash scripts but haven't been able to use them successfully.
Has anyone come across such a scenario before? I looked for solutions in other threads but didn't find anything conclusive for Xperia devices. Can someone help me with this? thanks.

randallstevens said:
I was feeling adventurous and started messing with the partition table
Click to expand...
Click to collapse
Hi,
On other forum one user followed suggested by me same theory of remapping paritions as described here to shrink so large /system and increase /userdata
He gotta same brick because deleted 3 partitions and then they was cannot created by any commands, so seems this method not applicable to our phone.
Next he very early quited from recovery without restoring partition table from backup.
Surprisingly, in un-offical service center phone was quickly fixed, seems with JTAG-device.
QHSUSB_DLOAD – this is fall-back low-level mode of CPU that allow access to all partitions just like fastboot
Needed to repair / writing stock ROM at factory.
Can be enabled manually by connecting to PC with holding both volume buttons. How to exit – don't know.
QPST utility not useful because we not have dump in it's proper format. So only Linux our hope.
That user tried to manage with Ubuntu but phone was not recognized. Very likely he went into something wrong.
That's very great that you created backup of whole NAND.
Maybe will be enough restore GPT (partition table), I have one and own per-partitions dump too.
So plan very easy: connecting phone to PC with Ubuntu and restore dump via dd utility.
Partially follow this instruction with modifications because you have full dump.
Connect phone, find where it "attached" (whole nand, not partitions), restore file there.
Be careful with disk naming, you can damage data on HDD.

Bonoboo said:
So plan very easy: connecting phone to PC with Ubuntu and restore dump via dd utility.
Partially follow this instruction with modifications because you have full dump.
Connect phone, find where it "attached" (whole nand, not partitions), restore file there.
Be careful with disk naming, you can damage data on HDD.
Click to expand...
Click to collapse
Hi Bonoboo, thank you for replying.
Unfortunately, Ubuntu isn't able to detect the emmc and therefore, I'm unable to find the "/dev/sdX" node for the device. The phone is being detected only as "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)".
I've seen some threads wherein QPST is first used to enable the partitions detection of emmc. However, as you mentioned, we do not have the necessary MSM8227 HEX file for this.
A windows app called "s1tool.exe" can be used to flash the bootloader files from the FTF, Link to thread. However, a testpoint combination is needed to access the emergency mode. I was unable to find a testpoint for Xperia M.
Is JTAG the only way forward here? Thanks again for the help.
EDIT: Looks like the s1tool I mentioned is device specific, may not work with XM.

randallstevens said:
I'm unable to find the "/dev/sdX" node for the device.
The phone is being detected only as "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)".
Click to expand...
Click to collapse
Yeah, this is not good, same as was with that guy. 1, 2
But here under spoiler I found Perl-script that may open access to eMMC.
Here more info.
Maybe it device-specific too, but anyway try.
UPD: post
just connect your phone to PC (at this time your /var/log/kern.log should update and ttyUSB0 should be added), in terminal, cd to your download folder and run './qd.pl --check', or run 'perl ./qd.pl --check'.
Click to expand...
Click to collapse

Bonoboo said:
Yeah, this is not good, same as was with that guy. 1, 2
But here under spoiler I found Perl-script that may open access to eMMC.
Here more info.
Maybe it device-specific too, but anyway try.
UPD: post
Click to expand...
Click to collapse
Hello Bonoboo,
I've tried using the qd.pl script but I'm not sure which file needs to be sent to the device when using the "qd.pl --pfile X" and the other parameters. The script detects the Qualcomm modem. I've tried uploading the first 256 kilobytes of the dump which should include the partition table but this results in an "Invalid Response" error from the script. Tried uploading the TA and some other partitions, but received the same error. No eMMC access yet. What file do you think the script requires?

randallstevens said:
What file do you think the script requires?
Click to expand...
Click to collapse
Was mentioned some *.hex, that maybe relates with same from QPST.
In threads more info.
Very likely script just not compatible with M.
UPD: it's sounds weird, but try to connect phone in fastboot / flashmode with long holding volume key.
In some cases this really helpful due second "bootloader" (alt_s1sbl2 partition and other).

Bonoboo said:
UPD: it's sounds weird, but try to connect phone in fastboot / flashmode with long holding volume key.
In some cases this really helpful due second "bootloader" (alt_s1sbl2 partition and other).
Click to expand...
Click to collapse
Hi, I tried long-pressing the volume key, it does not seem to work. Thanks for the confirmation about the hex file. It looks like I'll need the right files for the handset, as using hex files of similar chipsets did not help. I'll keep working on it and write back with an update if I'm able to fix it.

I've got the same problem., but unfortunately I didn't make a dump of mmcblk0. There is a way I can get yours? Or a part of it with the interesting data with which I can try figuring out how the qdload.pl script works (maybe leave out userdata cause of its size and the private data).

fakier said:
I've got the same problem., but unfortunately I didn't make a dump of mmcblk0. There is a way I can get yours? Or a part of it with the interesting data with which I can try figuring out how the qdload.pl script works (maybe leave out userdata cause of its size and the private data).
Click to expand...
Click to collapse
Hi fakier, sorry to know you have the same problem. I've sent you a PM with a link to a compressed copy of the first 140 MBs of the raw eMMC dump I made earlier. This should contain all the important partitions besides system and userdata. Note that this also includes my TA partition which probably shouldn't be written to your device.

randallstevens said:
Hi fakier, sorry to know you have the same problem. I've sent you a PM with a link to a compressed copy of the first 140 MBs of the raw eMMC dump I made earlier. This should contain all the important partitions besides system and userdata. Note that this also includes my TA partition which probably shouldn't be written to your device.
Click to expand...
Click to collapse
Thanks, a backup of my TA partition I do have...

Update
Hello folks, after spending a lot of time trying to fix my device with qdloader and QPST, I gave up. Before getting it JTAGed, I wanted to try my luck (again) and approached Sony to claim warranty, since there was a month remaining before its expiry.
My warranty claim was accepted and they replaced the mainboard, though the bootloader was unlocked!! My Xperia is alive and kicking again! Will unlock it soon.
Trying to fix the phone was not a pleasant experience, but I think I learned much along the way. Hope nobody else screws-up the way I did.
Thanks XDA, see ya around! :good:

randallstevens said:
Hello folks, after spending a lot of time trying to fix my device with qdloader and QPST, I gave up. Before getting it JTAGed, I wanted to try my luck (again) and approached Sony to claim warranty, since there was a month remaining before its expiry.
My warranty claim was accepted and they replaced the mainboard, though the bootloader was unlocked!! My Xperia is alive and kicking again! Will unlock it soon.
Trying to fix the phone was not a pleasant experience, but I think I learned much along the way. Hope nobody else screws-up the way I did.
Thanks XDA, see ya around! :good:
Click to expand...
Click to collapse
Dude what was the point of this thread and when you tried to fix your phone did you re flash stock ROM?

Reply to Piravinthb's comment
Piravinthb said:
Dude what was the point of this thread..
Click to expand...
Click to collapse
The point of this thread, dude, was to see if the device could somehow be taken out of the "Qualcomm HS-USB QDLoader 9008" mode, a (very) low-level interface meant for vendors to flash bootloaders and system images on their devices.
..and when you tried to fix your phone did you re flash stock ROM?
Click to expand...
Click to collapse
Had you googled this, you'd know that this mode isn't the same as the Flashtool flash mode or fastboot. No rom, stock or CM, can be flashed before fixing the bootloader itself, which is needed to start the device.
Not much progress could be made here since the bootloader hex files for Qualcomm's OEM tools (QPST) would be needed to fix such a hard brick. Also, the QDloader scripts mentioned earlier were written for a different chipset from the one used in Xperia M.
Cheers, RS.

randallstevens said:
Hello all, I have been a lurker for quite a while here. I own an Xperia M (Rooted, Unlocked BL running CM11). I was feeling adventurous and started messing with the partition table hoping to resize the system and data partitions using parted. I was unaware that the bootloader detects such modifications and ended up with a brick.
Just to clarify, this is a hard brick, since the Flashtool and fastboot modes do not work. I do not see the blue LED while trying to start the device in the fastboot mode using the volume rockers. My PC only detects a "QHSUSB_DLOAD" device for which I've installed the drivers and it is now "Qualcomm HS-UDB QDLoader 9008".
However, before I started to work with the partition table, I took a raw backup of the emmc i.e. mmcblk0. This should include the correct partition table and all the partitions (TA, userdata, system etc.). Theoretically (I believe so), if this is reflashed onto the device, an unbrick could be possible. However, so far, I haven't been able to figure out a way to push this image back to the device. I came across QPST and some linux bash scripts but haven't been able to use them successfully.
Has anyone come across such a scenario before? I looked for solutions in other threads but didn't find anything conclusive for Xperia devices. Can someone help me with this? thanks.
Click to expand...
Click to collapse
hi i have same problem with same adventure , but i was using stock rom with customized kernel with cwm.
i think the solutions are 2
repair hard brick with JTAG or test point and s1tool what is not implemented for xperia m
see http://forum.xda-developers.com/showthread.php?t=2646405 for Z1

my handset will be in trash no free or paid solution or sony service . i'll buy another one
thx

rafik23 said:
my handset will be in trash no free or paid solution or sony service . i'll buy another one
thx
Click to expand...
Click to collapse
Buy a nexus 4 off amazon for 140€
It only takes 2 taps to thank somebody here.

[Q] How do I restore system partitions?

Basically, I accidentally deleted the first 5 system partitions which bricked my phone. I found a system dump which is the same version as the ROM I was using on my phone. I haven't downloaded it yet, but, I believe, system dumps contain all the system partitions which are in img file format (not sure on this). My phone does get detected on my computer as QHSUSB_BULK but not with adb, so if I could get my phone into fastboot mode and hopefully my computer detects my phone in fastboot mode, will it be possible to flash the system partition imgs and restore my phone?
nb: my phone won't turn on; I don't know if it charges as there's no charging Led but sometimes if I plug it in to charge it flashes on then stays off; can't get into recovery; phone doesn't seem to respond to combination presses but I have yet to try this method
When you plug it into the computer does the computer make a ding sound that it's connected? If so, then press power and volume up until the disconnect ding sound which indicates it's rebooting and then immediately press volume down and see if you can get into fastboot. The timing is tricky so I've found using audio cues from computer can help if the phone is messed up.
Click to expand...
Click to collapse
.

Quick answer, you can't AFAIK. Not without a JTAG box

BLUuuE83 said:
Basically, I accidentally deleted the first 5 system partitions which bricked my phone. I found a system dump which is the same version as the ROM I was using on my phone. I haven't downloaded it yet, but, I believe, system dumps contain all the system partitions which are in img file format (not sure on this).
Click to expand...
Click to collapse
I think by "system partition" you mean "partition". There is the actual /system partition, and deleting that will only have wiped the ROM. I think you actually deleted other partitions; in particular if you wiped hboot or radio, the phone is screwed and you need JTAG.
QHSUSB_BULK (or similar) message when connecting to computer, and screen not coming on at all, reinforces that notion.

redpoint73 said:
I think by "system partition" you mean "partition". There is the actual /system partition, and deleting that will only have wiped the ROM. I think you actually deleted other partitions; in particular if you wiped hboot or radio, the phone is screwed and you need JTAG.
QHSUSB_BULK (or similar) message when connecting to computer, and screen not coming on at all, reinforces that notion.
Click to expand...
Click to collapse
Yeah. I think I only deleted the first 5 partitions mmcblk0p1 to mmcblk0p5.
Partition List

EddyOS said:
Quick answer, you can't AFAIK. Not without a JTAG box
Click to expand...
Click to collapse
So my best bet is it send it to a HTC certified repair centre and get them to fix it? If that's the case, how long does it usually take and what's the average cost?

BLUuuE83 said:
Yeah. I think I only deleted the first 5 partitions mmcblk0p1 to mmcblk0p5.
Partition List
Click to expand...
Click to collapse
According to the list you linked, you deleted a bootloader module (sbl1). So its a real brick.
---------- Post added at 09:21 AM ---------- Previous post was at 09:18 AM ----------
BLUuuE83 said:
So my best bet is it send it to a HTC certified repair centre and get them to fix it? If that's the case, how long does it usually take and what's the average cost?
Click to expand...
Click to collapse
That would certainly work. HTC will probably replace the motherboard, which if memory serves me (based on reports by others here) is something like $300 US.
But it may be cheaper to find a repair shop that can JTAG the phone. I think that price is around $100-150. But you need to find a shop that can do it, and on the M8 specifically.

Urgent Help Needed!

Hello....I bricked my I927 when I accidently formatted my efs partition when using EFS professional .....my phone boots in download mode.....but only boots till samsung logo screen.....I tried various things like installing stock GB and ICS through odin and installing custom firmware but phone boots onle till samsung logo and then lights up with sone stange colored thin lines and screen goes off.....In TRWP I get a "unable to mount preload" error whenever I try to install somethiing.....I suspect that the EFS partiton is corrupted and needs to be repartioned....I had backupped the efs folder when my phone was working before.....its in a tar format.....I read somwhere that someone made a recovery.zip out of his backedup EFS.IMG and flashed it with CWM solved his problems which were exactly similar to mine.....can somebody on the forum make a recovery.zip for I927 with update binary and script so that I can add the backedup EFS image to it and flash it with CWM? Please.....this would also help many others who are facing similar issues.....and also what do I do regarding the "unable to mount preload" error? I need to repartition and tried to install hemdall.....but get the common .dll error even after following all the instructions and installing C++ 2010.....

Hi, k one thing after the other.
Do you have repartitioned anything?
Do you have adb in place and does adb works when in TWRP?
The easiest thing would be to connect by adb then mount /efs and then restore the efs backup. The good is that you will have a good chance to recover your device. Maybe you need to reformat /efs but that depends.
Which timezone do you live? Maybe a Teamviewer session would be helpful?
.

Thank you for your reply sir...
THANKS FOR THE REPLY SIR....YES I WAS ABLE TO GO INTO CWM RECOVERY AND CONNECT THE PHONE WITH MINIMAL ADB FASTBOOT.....AND AFTER SPENDING ALMOST 2 DAYS CONTINUOUSLY TRYING TO FIND THE PROBLEM USING GOOGLE, I TRIED DIFFERENT COMMANDS ON ADB TO GET EFS BACK OJ THE PHONE....BUT WITH NO SUCCESS...... MY EFS BACKUP IS IN TAR FORMAT......IT WAS MADE USING GALAXYSIMUNLOCK BY SPOCKY.....I LATER TYPED IN 'ADB MESG'.....OR SOMETHING SIMILAR TO THAT COMMAND, AND FOUND OUT THAT ALL THE PARTITIONS ON mmcblk0 were mangled up with strange letters.....for eg, p1, p2, p3 and so on had strange characters written next to them.....SO I TRIED TO RE-PARTITION THE WHOLE THING WITH SDPARTED......AND IT RE-PARTIONED THE SYSTEM (AROUND 7000MB).....MMCBLK01 (AROUND 500MB).....AND ANOTHER THING I CANT REMEMBER NOW.....BUT WHEN IT FINISHED THE JOB, IT GAVE ME A mmcblk02 ERROR.....AND WHEN WHEN I CHECKED MY PHONE ON CWM SCREEN, IT GAVE ME A LIST OF CACHE ERRORS.....AND WHEN I SWITCHED OFF THE PHONE AFTER THAT IT REFUSED TO POWER ON.....IT WAS NOT EVEN GOING INTO DOWNLOAD OR RECOVERY MODE.....BATTERY HAD ENOUGH POWER....SO ITS NOT BATTERY FAULT......I SUPPOSE THAT SINCE THE PARTITIONS WERE FORMATTED THE PHONE BECAME COMPLETELY DEAD......CAN YOU TELL ME IF THERE IS ANY WAY WHERE I COULD GET THE COMPUTER TO RECOGNIZE MY PHONE USING A 'DEAD PHONE USB FLASH' OR SOMETHING.....AND THEN FLASH A BLANK BOOTLOADER AND THEN WRITE CWM?
I LIVE IN INDIA SIR.....+5.30 GMT.....I DO NOT KNOW ANYTHING ABOUT TEAMVIEWER.....IS IT AN ANDROID APP? CAN YOU EXPLAIN MORE IN DETAIL SIR?
PLEASE LET ME KNOW HOW TO GET THE COMPUTER TO RECOGNIZE THE PHONE AGAIN......

Well.. that sounds not that good...
Teamviewer (www.teamviewer.com) is an easy to use and free remote control software for your PC (it runs on both Linux and Windows). We could do a remote control session if you like. I can try to help but cannot promise anything.
I live in Germany: GMT +1. Send me a PM if you want to give that a try. Next Monday. Tuesday or Thursday would be possible on my site. At least for getting a short overview.
.

Thank you sir,
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....

alvcross said:
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....
Click to expand...
Click to collapse
Ok I have made one. It want to say it was VERY hard to find the correct instructions to do so and therefore I'm absolutely not sure if that will work for you!
Test it if you like but again: I have no idea if that would damage anything more than it is now!
See --> http://forum.xda-developers.com/cap...od-unbrick-debrick-hard-bricked-i927-t3285505
If it worked for you (would be like a miracle) then please report back!
If it does NOT work for you please report back, too!
thanks
xdajog
.
UPDATE:
Besides the link I posted --> Could you please also try the following:
1) Power on your device and directly after that:
2) Press and hold down Vol Up + Vol Down (both the same time)
3) You should see a warning message like the attached one which is the APX mode
4) you need to release the vol buttons immediately after you see the APX mode otherwise it will continue to the non working download mode.

Does teamviewer require internet connection with a lot of data?
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....

alvcross said:
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....
Click to expand...
Click to collapse
Uhm do you have read my above post??
.

1927 wouldn't boot.....Help.
Ohhhh Thank you.....thank you.....thank you for your kind reply Sir.....how good of you to take all your precious time to help me.....I greatly appreciate all your hard work Sir.....wonderful...*.I wanted to download your img file to try it out and when I read the reply of brother Bubor, that the I927 woudnt boot from the SD card when the bootloader is bricked, I was very disappointed. Like I said before, I have a very very slow internet connection with very less data left....and according to brother bubor's reply I doubt this will work....It looked like he was sure that it wont work....I tried to get into APX mode as the link that brother bubor posted had mentioned, but no luck, as the phone is not going into APX mode.....I remember that when I was trying to get to the APX mode the first time, the computer flashed a notification that the APX driver was not successfully installed.....but after that I tried the method more than a dozen times, but the computer was not recognizing the phone to go into APX mode.....Does the phone go into APX mode when the full internal phone system is formatted? I tried your second method on trying to get to APX mode, but nothing happens.....the computer is not recognizing the phone.....The battery had about 30% power in it when the phone got bricked 2 weeks ago.....Dont know if the battery drained all these days of not using the phone.....And even if I get to the APX mode, I have no idea how to proceed from there to repartition the internal phone system and get back download mode.....In the link that brother bubor posted the person who made the thread has made some files to be used when one gets into APX mode.....The PIT and emmc files which are necessary for repartitioning the system and getting the bootloader work are found in that zip file.....But that zip file is for the I9103 Galaxy R.....there isnt something like that available for the I927 yet.....And is brother bubor sure that the unbrick.img file wont work on the I927?

Give it a try with my unbrick image.
we all don't know.
.

xdajog said:
Give it a try with my unbrick image.
we all don't know.
.
Click to expand...
Click to collapse
Hi @alvcross: any update on this?
have you tried the SD card unbrick?
You said you cannot open the APX mode but what happens when you press the buttons for accessing the APX mode?
Try it even if you see a blank screen and then connect your Cappy with USB to your computer --> you should get a message about a missing driver or similar.
If that works I tell you how to proceed.

xdajog said:
hi @alvcross: Any update on this?
Have you tried the sd card unbrick?
You said you cannot open the apx mode but what happens when you press the buttons for accessing the apx mode?
Try it even if you see a blank screen and then connect your cappy with usb to your computer --> you should get a message about a missing driver or similar.
If that works i tell you how to proceed.
Click to expand...
Click to collapse
im so sorry that i was missing in this thread for a long time now sir.....i have had some issues at home and they have been sorted out lately.....yes sir.....i tried the sd card unbrick image....but my nothing happens.....when i try to hold volume up+power+home buttons and insert usb cable into my computer it says installing drivers and then says drivers failed to install....and nothing happens further.....can you help sir?

alvcross said:
im so sorry that i was missing in this thread for a long time now sir.....i have had some issues at home and they have been sorted out lately.....yes sir.....i tried the sd card unbrick image....but my nothing happens.....when i try to hold volume up+power+home buttons and insert usb cable into my computer it says installing drivers and then says drivers failed to install....and nothing happens further.....can you help sir?
Click to expand...
Click to collapse
Ok so you may try to install the special apx drivers now. Unfortunately I'm on vacation right now so I cannot upload them elsewhere. I come back to you next week.
Sent from my LG-H815 using XDA-Developers mobile app

xdajog said:
Ok so you may try to install the special apx drivers now. Unfortunately I'm on vacation right now so I cannot upload them elsewhere. I come back to you next week.
Sent from my LG-H815 using XDA-Developers mobile app
Click to expand...
Click to collapse
Oh yes Sir....Ill be waiting for the special apx driver package from you....Thank you so very much Sir.....God bless you.....

alvcross said:
Oh yes Sir....Ill be waiting for the special apx driver package from you....Thank you so very much Sir.....God bless you.....
Click to expand...
Click to collapse
No guarantee ! [emoji121]
Sent from my LG-H815 using XDA-Developers mobile app

xdajog said:
No guarantee ! [emoji121]
Sent from my LG-H815 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes Sir....I understand....

alvcross said:
Yes Sir....I understand....
Click to expand...
Click to collapse
Ok could you please try these driver package here: http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875
Follow the instructions there for installing
The next step (if the driver would work for you) will be to flash a working PIT to your device to make sure you are using the correct partitions.
Afterwards we will flash the bootloader (may absolutely brick your device if not done correctly) and then --> if all goes fine --> you should be able to flash in download mode whatever you want to.
So it is still a long way to go and I need to check all the steps first before actually we can proceed.
That may take longer so do not expect that this will be something in the next days.. sorry.
Update:
If the above universal driver do NOT work for you: Test these one here View attachment apx_driver_samsung.zip
.

Thanks for the speedy reply Sir......Ill do as you said and let you know Sir......thank you.....thank you.....thank you Sir....

wooowwww......windows installed the drivers for the phone and it shows up as "NVIDIA usb boot-recovery for mobile devices." But when I open minimal adb and fastboot and type 'adb devices' the phone doesn't show up in the 'list of devices attached'....the line after 'list of devices attached' is just empty.....Also the phone doesnt show up in odin....what should I do next Sir?

alvcross said:
wooowwww......windows installed the drivers for the phone and it shows up as "NVIDIA usb boot-recovery for mobile devices." But when I open minimal adb and fastboot and type 'adb devices' the phone doesn't show up in the 'list of devices attached'....the line after 'list of devices attached' is just empty.....Also the phone doesnt show up in odin....what should I do next Sir?
Click to expand...
Click to collapse
nvidia apx isnt fastboot/adb device. You can found tool on nvidia site ( more info https://ac100.grandou.net/nvflash ), this tool can read and write whole flash.
Before you could use nvidia's tool, you must send an uniq blob to your phone. APX mode is useless without this blob.
This blob is uniq for every phone.