Related
Hello! I am sorry for my translation. I'm just out of Russia. I have a problem - I beg your Oppo FIND 7а wrong firmware and it does not react to the power button. When connected to a computer is determined by the device - Qualcomm HS-USB QDLoader 9008, and the flash drive is not seen. Esteemed the on the forums that it is possible restore through the program - GPST, but at me there are no files necessary for programm required for programming via this program. Necessary files from the same machine - mprg8974.hex 8974_msimage.mbn sahara.xml, maybe someone you have these files?
vovan0983 said:
Hello! I am sorry for my translation. I'm just out of Russia. I have a problem - I beg your Oppo FIND 7а wrong firmware and it does not react to the power button. When connected to a computer is determined by the device - Qualcomm HS-USB QDLoader 9008, and the flash drive is not seen. Esteemed the on the forums that it is possible restore through the program - GPST, but at me there are no files necessary for programm required for programming via this program. Maybe someone you have these files?
Click to expand...
Click to collapse
Contact Oppo. Their support staff have given people QPST recovery files in the past... The only OEM I'm aware of to ever have done this.
Entropy512 said:
Contact Oppo. Their support staff have given people QPST recovery files in the past... The only OEM I'm aware of to ever have done this.
Click to expand...
Click to collapse
Official forum written request, but so far received no response. Can anyone here downloaded these files?
up
vovan0983 said:
Official forum written request, but so far received no response. Can anyone here downloaded these files?
Click to expand...
Click to collapse
up
Found A Solution ?
vovan0983 said:
Hello! I am sorry for my translation. I'm just out of Russia. I have a problem - I beg your Oppo FIND 7а wrong firmware and it does not react to the power button. When connected to a computer is determined by the device - Qualcomm HS-USB QDLoader 9008, and the flash drive is not seen. Esteemed the on the forums that it is possible restore through the program - GPST, but at me there are no files necessary for programm required for programming via this program. Necessary files from the same machine - mprg8974.hex 8974_msimage.mbn sahara.xml, maybe someone you have these files?
Click to expand...
Click to collapse
Hi Guy !
Did you find a solution ?
Thanks
Leny
I have the same problem... if you have the files, can you send them to me ? (I'm using google translate so my English could be wrong...)
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.
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.
Hi everyone ,
(first sorry for my bad english)
i got a g8 rio-l01 with a few problem ( no imei , no sn , no wifi and bt mac adresse) all this problem was solved using the hcu tool
but the biggest problem is the phone boot in a factory mode ,i can see this in the projectmenu>veneer informaton>other info>run mode: factory
so in this mode :
1-i have no shortcut panel and notification panel when i slide from up to down nothing come
2-no signial or network conection
3-in the first home page in the phone i have MMIs app/software upgrade/MMI/projectmenu/MMIa,
in the second one i have runningtest3
in the last one basic android app
4-i can't use keyboard
so i have trayed i think all huawei g8 firmware and nothing change
trayed with DC phoenix methode (the two methode) and same problem
trayed with the original soft (RIO-L01_M105_Board Software_general_Android 5.1_EMUI 3.1_05021TJY) and no change
trayed with l02 ,l03 ,tl00 ,slim6 and cm13 and the problem persist
bootloader and frp are unlocked ,sim too with hcu and phone rooted
if i remove appfac from user data and reboot the keyboard Appears and other app Appears but the phone stay in factory mode with no upper pannel and no network signial
i can use wifi and bt
in fastboot getvar pruduct give msm8916 (it's normal??? the phone is an msm8936)
i think there is a currupted or a missing file or partition
i have all factory flash file
bootloaderimage: huawei_msimage.mbn, MPRG8936.mbn (i don't know how tu use this two files)
fastbootimage: boot.img, ,cache.img ,cust.img ,emmc_appsboot.mbn ,erecovery.img ,frp.img ,fs_image.tar.gz.mbn.img ,gpt_both0.bin ,hyp.mbn ,log.img ,misc.mbn ,modem_st1.mbn ,modem_st2.mbn ,NON-HLOS.bin ,oeminfo.mbn , persist.img ,recovery.img ,rpm.mbn ,sbl1.mbn ,system.img ,tz.mbn,userdata.img ( and all crc file )
any idea are welcome
thank you
Hi again
So after many test ( and break and unbreak the soft many times) by editing prop and conf files, i noticed that the ro.runmode is the command controling the boot mode.
But i don't know were is this command and if it's possibol:
- To force ro.runmode=normal?
- Or any solution to by pass runningtest3 app or to fake the result?
Thank you (any help are welcome i don't worry about bteaking the phone)
Finally the phone is fully dead ?
After many flash factory, stock and custom i decided to find the way to enter to hs-usb 9008 mode and i find,by flashing the phone with cherry honor 4 rom. And the phone rebooted in 9008 mode, than flashed the ddr and the msm8936 file with zte tool. The msm will not finish and the phone reboot in fastboot (with red, green,blue screen) than reflashed factory rom with dc unlocker the phone rebooted normal but with the same problem that i have in the first.
Second try, flashed with cherry, entred 9008 mode,reflashed with zte tool (by error used a bad msm8936 file from lenovo)
And the phone stop working not detected and black screen
Third try, desassemled the phone, removed battery find test point after many risky test,the phone boot again in 9008 mode.
Reflashed with zte tool, enter red green blue fastboot, and decided to reflash all the factory with fastboot flashall méthode to unbrick an msm8916. Fastboot finish with many failed.
The phone rebooted but black screen and blinking led with continus (red,blue, green), not detected in pc, trayed with test point and nothing
I think it's fully dead now
Sorry for all this long text but just to share expérience
Thank you
And no it's not dead ðŸ˜, find the way to boot it again in 9008 mode with shorting two test point
Here we go for other test
السلام عليكم
hello friend
have you tried to flash the OEMINFO partition (if not be careful because the unlocked code of the bootloader will be changed and you need to read the new one with hcu client)
if you dont know how to do, tell me
sorry for bad english I'm not english man
xzanium said:
السلام عليكم
hello friend
have you tried to flash the OEMINFO partition (if not be careful because the unlocked code of the bootloader will be changed and you need to read the new one with hcu client)
if you dont know how to do, tell me
sorry for bad english I'm not english man
Click to expand...
Click to collapse
allrady solved my problem with an oeminfo but it work only single sim i need an other oeminfo with dual sim
thank you
How To Get Oeminfo
makabress said:
allrady solved my problem with an oeminfo but it work only single sim i need an other oeminfo with dual sim
thank you
Click to expand...
Click to collapse
makabress Please clear here how to get oem info and write it.. i m alredy face same problem..
hellowbd said:
makabress Please clear here how to get oem info and write it.. i m alredy face same problem..
Click to expand...
Click to collapse
Hi , i found the oeminfo searching in google. I will try to find it again
hello
i a have the same prolem but i cant find "the service rom" too, my phone is stuck in mode 9008 i tried to do the rom by myself but witouth any succes.... i read in a post that i cant try to put the "Huawei_Honor_Cherry_L04_V100R001C900B150_India_4.4.4_EMUI_3.0_05021SLQ" who has the same structure but cannot flash phone said "bootloaderimage" fail
please anyone can help me? i am 2 months witout phone... sorry about my bad english im a spanish guy
rio-l01 test point
hi, please i can't found rio-l01 test point can you help me
rmili25 said:
hi, please i can't found rio-l01 test point can you help me
Click to expand...
Click to collapse
test point are in the left/right side of the display connector, you can use a small wire to short it
JoseBankai said:
test point are in the left/right side of the display connector, you can use a small wire to short it
Click to expand...
Click to collapse
thank you brother
please i have the same problem ( rio-l01 no service no call ) can you help me please by oeminfo file or other things
excuse me i'am bad in english
still having the same problem, no solution, try to resoldering emmc, processor, voltage are ok, everything works in other board, so the problem is still the **** mode 9800 and the vanished "service rom" (not trully vanished but every service that i call to fix this ask me for a lot of money just to fix 1 phone... not worth it..) hope somebody can explain this at least, and why is happening, maybe one day can recovery my data on thtat phone....
Hey everybody. I am looking for mbn or firehose files so i can try to revive my hard bricked Nokia XL. I dont know the history of the device, because i have bought it online in hope of fixing it. My best guess is that somebody flashed V2 files on this device. The device shows as QDLoader 9008. I have read some tutorials and the problem is, dont have money, nor do i know where to buy a jtag box in order to flash boot files that way. QPST is my only hope but as you can guess from the title, i cannot find proper boot files for my device that will work on QPST. Thank you in advance for help