Related
I castrated one of my aftvs; through an incredibly bone-headed series of events I disabled adbd AND left myself without an alternate entryway for repairs (terminal or ssh). Now I have an aftv that Amazon would love -- no sideloading at all, device only usable for Amazon content. It's stuck on 51107.
I was hoping that the new software update would make it whole (if unrootable), but when I check for new software update I get nada.
jocala said:
I castrated one of my aftvs; through an incredibly bone-headed series of events I disabled adbd AND left myself without an alternate entryway for repairs (terminal or ssh). Now I have an aftv that Amazon would love -- no sideloading at all, device only usable for Amazon content. It's stuck on 51107.
I was hoping that the new software update would make it whole (if unrootable), but when I check for new software update I get nada.
Click to expand...
Click to collapse
If you can play content why can't you go into settings and re-enable ADB?
kairnage said:
If you can play content why can't you go into settings and re-enable ADB?
Click to expand...
Click to collapse
It's not that simple. The problem involves a script running adbd as root after boot. Running adbd as root lets you do some cool stuff you can't do otherwise. Worked pre-boot, failed post-boot, leaving the box w/o adbd. Sucks to be me
Anyway, if you're going to play with internals, have a back door enabled. Lesson learned here, thought I'd pass it on. Locked bootloaders stink.
what about booting to recovery menu, clearing cache, restoring to factory defaults from there? Surely that would un**** your system?
jocala said:
I castrated one of my aftvs;
Click to expand...
Click to collapse
ROFL...sorry, I feel your pain, but I love the subject line...can't stop laughing.
:laugh::laugh::laugh::laugh::laugh:
roligov said:
what about booting to recovery menu, clearing cache, restoring to factory defaults from there? Surely that would un**** your system?
Click to expand...
Click to collapse
Nope
The problem lies in the install-recovery-2.sh script. Restoring to factory default doesn't seem to touch /system/etc.
jocala said:
Nope
The problem lies in the install-recovery-2.sh script. Restoring to factory default doesn't seem to touch /system/etc.
Click to expand...
Click to collapse
Unfortunately, if there is a problem in /system and you can't get a root shell, there really isn't anything that can be done. There is no way to force recovery to use an update.zip because there is no way to get it on there, and that's the only way to get recovery to write to /system. The only solution I know is to mount the emmc chip in linux and fix the /system partition: http://forum.xda-developers.com/showpost.php?p=55280958&postcount=254
rbox said:
Unfortunately, if there is a problem in /system and you can't get a root shell, there really isn't anything that can be done. There is no way to force recovery to use an update.zip because there is no way to get it on there, and that's the only way to get recovery to write to /system. The only solution I know is to mount the emmc chip in linux and fix the /system partition: http://forum.xda-developers.com/showpost.php?p=55280958&postcount=254
Click to expand...
Click to collapse
Yep. Thanks for the link to gtvhacker. I wasn't aware of that method.
Hi i was trying to restore my lg & i deleted the boot.img & now the phone is not recognized by the computer a lot
of disks show up can someone please help me thanks :crying::crying::crying:
tribi said:
Hi i was trying to restore my lg & i deleted the boot.img & now the phone is not recognized by the computer a lot
of disks show up can someone please help me thanks :crying::crying::crying:
Click to expand...
Click to collapse
There are quite a few ways the phones have been saved. Over in q&a, there are some on top with fixes. I'll go copy a few and get back to you.
Try this thread, lots of different fixes
http://forum.xda-developers.com/showthread.php?t=3056632
tribi said:
Hi i was trying to restore my lg & i deleted the boot.img & now the phone is not recognized by the computer a lot
of disks show up can someone please help me thanks :crying::crying::crying:
Click to expand...
Click to collapse
Those pop ups are actually each of your phone partitions trying to mount themselves to your computer. If you use a Linux computer system (I use Ubuntu) you can push to those partitions to fix it.
Here is the guide on how to do that. http://forum.xda-developers.com/showthread.php?t=2582142
sudosurootdev said:
Those pop ups are actually each of your phone partitions trying to mount themselves to your computer. If you use a Linux computer system (I use Ubuntu) you can push to those partitions to fix it.
Here is the guide on how to do that. http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
The guide is showing it works only for D802 does it work with LS980 too?
Just use the correct files
Could somebody provide us with a full eMMC backup of a 16GB and 32GB model so that we can build partition.xml and extract rawprogram0.xml and patch0.xml from it to unbrick our devices with QFIL/QPST?
(this issue is rather specific, you cannot access the phone by ADB,fastboot or LGUP, but Windows recognizes it as Qualcomm HS-USB QDLoader 9008 so it's fixable with the appropriate files)
qb74 said:
Could somebody provide us with a full eMMC backup of a 16GB and 32GB model so that we can build partition.xml and extract rawprogram0.xml and patch0.xml from it to unbrick our devices with QFIL/QPST?
(this issue is rather specific, you cannot access the phone by ADB,fastboot or LGUP, but Windows recognizes it as Qualcomm HS-USB QDLoader 9008 so it's fixable with the appropriate files)
Click to expand...
Click to collapse
I have no idea to make such a backup since I cannot access the device's emmc in Linux.
I've used this method on another phone but there I could access the emmc directly as external storage by using a key combo on boot.
Skickat från min Nexus 5X via Tapatalk
Nicktheprofessor said:
I have no idea to make such a backup since I cannot access the device's emmc in Linux.
I've used this method on another phone but there I could access the emmc directly as external storage by using a key combo on boot.
Skickat från min Nexus 5X via Tapatalk
Click to expand...
Click to collapse
here
it's for another chipset, but the same process applies for all chipsets.
qb74 said:
here
it's for another chipset, but the same process applies for all chipsets.
Click to expand...
Click to collapse
Can't help you with that one then since I'm running Linux on all my machines. Too bad, I wouldn't mind having a complete backup.
Skickat från min Nexus 5X via Tapatalk
Maybe the people with Linux machines and free time would wanna try this?
https://androidforums.com/threads/guide-how-to-create-partition-xml-gpt.1125433/
gogozombiii said:
Maybe the people with Linux machines and free time would wanna try this?
https://androidforums.com/threads/guide-how-to-create-partition-xml-gpt.1125433/
Click to expand...
Click to collapse
@Nicktheprofessor Try checking this out, if you got the time! You would help the community out a ton!
qb74 said:
@Nicktheprofessor Try checking this out, if you got the time! You would help the community out a ton!
Click to expand...
Click to collapse
I'll need an OTG storage device to do this. I can backup the entire thing using dd but it can't be written to the internal storage (for obvious reasons, it would then backup the backup and the backup of the backup and so on).
If I could access it on the computer or send it to the computer then that would work but I'm not aware of any way to do that without storing it locally first (which, as previously mentioned, is impossible to do).
[EDIT] I wonder if it's possible to use adb root pull from TWRP to pull /dev/mmcblk0, I'll try that after cleaning it up. If that works then it's a piece of cake to do this on any phone. [/EDIT]
qb74 said:
Could somebody provide us with a full eMMC backup of a 16GB and 32GB model so that we can build partition.xml and extract rawprogram0.xml and patch0.xml from it to unbrick our devices with QFIL/QPST?
(this issue is rather specific, you cannot access the phone by ADB,fastboot or LGUP, but Windows recognizes it as Qualcomm HS-USB QDLoader 9008 so it's fixable with the appropriate files)
Click to expand...
Click to collapse
OK, so I managed to do a complete backup via adb pull /dev/mmcblk0
For future reference, this is the easiest way:
From a fastboot boot twrp:
adb root
adb pull /dev/mmcblk0 emmc.img
Now, that's 13GB worth of data that you don't need, I can give you a part table on this (using part) or whatever you need but It's a bit too big to upload as is.
I can run an emulator and mount it as is and that works too but all I can extract from there is data.
Now, shutting down your device and inserting your USB cable while holding vol + AND vol- seems to mount emmc as portable storage, that should mean that you can dd the entire thing right onto the device?
Nicktheprofessor said:
OK, so I managed to do a complete backup via adb pull /dev/mmcblk0
For future reference, this is the easiest way:
From a fastboot boot twrp:
adb root
adb pull /dev/mmcblk0 emmc.img
Now, that's 13GB worth of data that you don't need, I can give you a part table on this (using part) or whatever you need but It's a bit too big to upload as is.
I can run an emulator and mount it as is and that works too but all I can extract from there is data.
Now, shutting down your device and inserting your USB cable while holding vol + AND vol- seems to mount emmc as portable storage, that should mean that you can dd the entire thing right onto the device?
Click to expand...
Click to collapse
Maybe? Not entirely sure if the dd method could work since this kind of hardbrick literally bricks your phone if you don't have the right files. Great job on the backup though! Mind telling me the steps for dd-ing the entire thing onto my device?
Or better, create partition.xml and extract & upload rawprogram0.xml and patch0.xml so that I can use myself as a test dummy.
its a guide for linux systems, hopefully you can help us get one step closer to fixing our devices!
qb74 said:
Maybe? Not entirely sure if the dd method could work since this kind of hardbrick literally bricks your phone if you don't have the right files. Great job on the backup though! Mind telling me the steps for dd-ing the entire thing onto my device?
Or better, create partition.xml and extract & upload rawprogram0.xml and patch0.xml so that I can use myself as a test dummy.
its a guide for linux systems, hopefully you can help us get one step closer to fixing our devices!
Click to expand...
Click to collapse
Yeah, that doesn't help since it's made for extracting a partition.xml from a .KDZ where these partition files exist.
In a copy of your disk that doesn't exist, there isn't a file to copy and paste into that.
I can do the partition table and partition sectors if you want that but without knowing what is actually needed (as in the source code in the tool used to fix the device) I can't really help.
I'll check if i can put a device in that state and see what happens with the emmc connection.
Nicktheprofessor said:
Yeah, that doesn't help since it's made for extracting a partition.xml from a .KDZ where these partition files exist.
In a copy of your disk that doesn't exist, there isn't a file to copy and paste into that.
I can do the partition table and partition sectors if you want that but without knowing what is actually needed (as in the source code in the tool used to fix the device) I can't really help.
I'll check if i can put a device in that state and see what happens with the emmc connection.
Click to expand...
Click to collapse
Get the partition table and partition sectors, that's a start! (even though I got no clue how to continue after that )
Do you mean the source code of QPST/QFIL? That's a rather impossible task though
qb74 said:
Get the partition table and partition sectors, that's a start! (even though I got no clue how to continue after that )
Do you mean the source code of QPST/QFIL? That's a rather impossible task though
Click to expand...
Click to collapse
I'm talking about the source code of the programming tool but I might not need that either if i can just examine it on my own and I have one of those devices on hand come tuesday.
I'm fairly confident that I can build a programmer to rewrite the emmc with whatever I want it to if i can just get a hold of the system calls.
Do you want to work together on this? It seems to me that it would be worthwhile even in the long run as QC are unlikely to change this procedure.
Nicktheprofessor said:
I'm talking about the source code of the programming tool but I might not need that either if i can just examine it on my own and I have one of those devices on hand come tuesday.
I'm fairly confident that I can build a programmer to rewrite the emmc with whatever I want it to if i can just get a hold of the system calls.
Do you want to work together on this? It seems to me that it would be worthwhile even in the long run as QC are unlikely to change this procedure.
Click to expand...
Click to collapse
Absolutely! Even though I don't have the necessary knowledge with Android/Linux, I do have basic Windows knowledge. I'd be glad to help out the community as a whole!
bump!
qb74 said:
Could somebody provide us with a full eMMC backup of a 16GB and 32GB model so that we can build partition.xml and extract rawprogram0.xml and patch0.xml from it to unbrick our devices with QFIL/QPST?
(this issue is rather specific, you cannot access the phone by ADB,fastboot or LGUP, but Windows recognizes it as Qualcomm HS-USB QDLoader 9008 so it's fixable with the appropriate files)
Click to expand...
Click to collapse
i just found for the nexus 5x the lg tot firmware u can use it to make the partition.xml
lg h791 16g
drive.google.com/uc?id=0B89Fk5GHkvZqb3I3bV9rTksxZFE&export=download
lg h791 32g
cloud.mail.ru/public/G1bp/vhoVk1MwW
i used BoardDiag to extract the frimware
drive.google.com/file/d/0Bw1P9EP0d9nZY0FUall1VWVvc0k/view
and here is how to build partition.xml and extract rawprogram0.xml and patch0.xml from it
youtube.com/watch?v=BmAuzbG9re4
now we need prog emmc firehose 8992.mbn to use with QFIL/QPST
i hope u can find a solution i'm stuck with a dead nexus 5x for the moment
do you need h798 16G version dd image? if you need I can dump to you
---------- Post added at 09:17 AM ---------- Previous post was at 08:40 AM ----------
Nicktheprofessor said:
OK, so I managed to do a complete backup via adb pull /dev/mmcblk0
For future reference, this is the easiest way:
From a fastboot boot twrp:
adb root
adb pull /dev/mmcblk0 emmc.img
Now, that's 13GB worth of data that you don't need, I can give you a part table on this (using part) or whatever you need but It's a bit too big to upload as is.
I can run an emulator and mount it as is and that works too but all I can extract from there is data.
Now, shutting down your device and inserting your USB cable while holding vol + AND vol- seems to mount emmc as portable storage, that should mean that you can dd the entire thing right onto the device?
Click to expand...
Click to collapse
adb pull /dev/mmcblk0 emmc.img
this command does not work
first there no device /dev/mmcblk0 but in /dev/block/mmcblk0 second adb pull /dev/block/mmcblk0 emmc.img does not work.
F:\BaiduNetdiskDownload>adb pull /dev/mmcblk0 emmc.img
adb: error: remote object '/dev/mmcblk0' does not exist
youxiaojie said:
do you need h798 16G version dd image? if you need I can dump to you
---------- Post added at 09:17 AM ---------- Previous post was at 08:40 AM ----------
adb pull /dev/mmcblk0 emmc.img
this command does not work
first there no device /dev/mmcblk0 but in /dev/block/mmcblk0 second adb pull /dev/block/mmcblk0 emmc.img does not work.
F:\BaiduNetdiskDownload>adb pull /dev/mmcblk0 emmc.img
adb: error: remote object '/dev/mmcblk0' does not exist
Click to expand...
Click to collapse
You need to reboot to a TWRP (or whatever recovery that supports unencrypted storage) that supports unencrypted devices before you attempt it.
You have to do this through fastboot boot recovery.img and not through flashing it. You are correct about /dev/block/mmcblk0 though. My apologies for the confusion caused by that.
I got it
Nicktheprofessor said:
You need to reboot to a TWRP (or whatever recovery that supports unencrypted storage) that supports unencrypted devices before you attempt it.
You have to do this through fastboot boot recovery.img and not through flashing it. You are correct about /dev/block/mmcblk0 though. My apologies for the confusion caused by that.
Click to expand...
Click to collapse
after formatting data partition, I removed whole disk encrypt and success run "adb pull /dev/block/mmcblk0 emmc.img" command.
https://pan.baidu.com/s/1bpcvqV1
and do I used "adb push emmc.img /dev/block/mmcblk0" to recover whole emmc when my phone soft bricked?
youxiaojie said:
after formatting data partition, I removed whole disk encrypt and success run "adb pull /dev/block/mmcblk0 emmc.img" command.
https://pan.baidu.com/s/1bpcvqV1
and do I used "adb push emmc.img /dev/block/mmcblk0" to recover whole emmc when my phone soft bricked?
Click to expand...
Click to collapse
file is not working, getting a error when unzipping it
qb74 said:
file is not working, getting a error when unzipping it
Click to expand...
Click to collapse
https://mega.nz/#!Oo9DxJyL!rzFl_s2ie1frCr79TpYTYKoeXNwg78d5dc-a71bkInE
try this again
Already extracted mmcblk0 can be found on the following thread here
Can someone with a rooted stock rom please pull the following partition and upload it here
Requirements
Rooted moto g5
TWRP recovery
Blank micro sd card (at least 32gb)
make sure adb debugging in enabled in dev options
enter TWRP recovery
Follow instructions from here but amend the extract command with the values given below
https://forum.xda-developers.com/showpost.php?p=76795590&postcount=1
If you have a 32gb varient use
dd if=/dev/block/mmcblk0 of=/storage/<STORAGE-ID>/mmcblk0.img bs=1048576 count=29820
and if you have a 16gb varient use
dd if=/dev/block/mmcblk0 of=/storage/<STORAGE-ID>/mmcblk0.img bs=1048576 count=14910
Please note this partition will be very large so compress it in a zip file as best you can and you will obviously need good internet connection and file storage to upload it
Please also enclude what varient the mmcblk0 was taken from with your upload
How to here
https://forum.xda-developers.com/showpost.php?p=76795590&postcount=1
but what we need is someone who has a motorola g5 cedric xt1671 that has root and twrp and can provide us with that file to be able to revive our cell phones
I don't have the stock ROM will it be fine
abhimanyuk said:
I don't have the stock ROM will it be fine
Click to expand...
Click to collapse
Prefer stock but it should work if you have a custom rom too
TheFixItMan said:
Prefer stock but it should work if you have a custom rom too
Click to expand...
Click to collapse
But it will include my device all info like imei serial number etc.
Will it be safe.
abhimanyuk said:
But it will include my device all info like imei serial number etc.
Will it be safe.
Click to expand...
Click to collapse
I'm asking for the bootloader block - I believe imei is on another partition
Either way it's up to you if you want to provide files
Google and research
TheFixItMan said:
I'm asking for the bootloader block - I believe imei is on another partition
Either way it's up to you if you want to provide files
Google and research
Click to expand...
Click to collapse
I was getting an error with that command so I have listed out all the partitions you can let me know which partition you need.
Device : XT1677
Variant: Amazon
ROM: Custom
abhimanyuk said:
I was getting an error with that command so I have listed out all the partitions you can let me know which partition you need.
Device : XT1677
Variant: Amazon
ROM: Custom
Click to expand...
Click to collapse
Try using the instructions here
With my method you probably have to mount the partition & I can't remember the commands
https://forum.xda-developers.com/showpost.php?p=76795590&postcount=1
If you don't have Linux/Ubuntu I presume you can use the terminal window in twrp - as long as it can get root access but better using Linux/Ubuntu either as stand alone or a virtual machine
TheFixItMan said:
Try using the instructions here
With my method you probably have to mount the partition & I can't remember the commands
https://forum.xda-developers.com/showpost.php?p=76795590&postcount=1
If you don't have Linux/Ubuntu I presume you can use the terminal window in twrp - as long as it can get root access but better using Linux/Ubuntu either as stand alone or a virtual machine
Click to expand...
Click to collapse
I have Linux installed. I will do that tomorrow Hope we will get the desired result.
Can anyone create a link for me to download this mmcdlk0 for the bike g5 xt 1672? because I need to put in a micro, so I recover my defective device in the bootloader. Thank you!
I'm still waiting for someone to provide the mmcblk0 partition
If you have a working rooted moto g5 see the first post
what's new, nobody could get the mmcblk0 file or esque do not want to help, this is the last straw.
just because I do not have another motorcycle g5 but towards the attempt, but good.
but it will be necessary to take it with a technician to the end that already came out a method to revive it through a box precisely Medussa pro, but we see light in that help us in this I think it will be the only alternative so far, or wait for the blank to come out flash that as I see it will take time.
what's new, nobody could get the mmcblk0 file or esque do not want to help, this is the last straw.
just because I do not have another motorcycle g5 but towards the attempt, but good.
but it will be necessary to take it with a technician to the end that already came out a method to revive it through a box precisely Medussa pro, but we see light in that help us in this I think it will be the only alternative so far, or wait for the blank to come out flash that as I see it will take time.
---------- Post added at 03:15 AM ---------- Previous post was at 03:11 AM ----------
https://www.youtube.com/watch?v=rJGsZuWkboo
You did it ?
gugsta said:
Can anyone create a link for me to download this mmcdlk0 for the bike g5 xt 1672? because I need to put in a micro, so I recover my defective device in the bootloader. Thank you!
Click to expand...
Click to collapse
You did it ? I'm having the same problem with the bike g5 xt1672 could you help me
dalissonetcaf said:
You did it ? I'm having the same problem with the bike g5 xt1672 could you help me
Click to expand...
Click to collapse
We are awaiting someone to upload the mmcblk0 partition for this device
Until that happens there is currently no known solutionn (other than motherboard replacement or specialist flash boxes) to revive a moto g5 with no access to the bootloader
Hi, I'm trying to make the mmcblk0.img but with the bs and count that says in the g5 forum, it only weighs 4GB.
can you give me the data
I think it has to do with the ram, the G5S is 3.
Happiness777 said:
Hi, I'm trying to make the mmcblk0.img but with the bs and count that says in the g5 forum, it only weighs 4GB.
can you give me the data
I think it has to do with the ram, the G5S is 3.
Click to expand...
Click to collapse
It's because of the file system. Fat32 can only handle files up to 4GB. Best way to get around this, is to first format the sdcard in exFAT or ext4 on your computer (sdcard reader).
Here is a mmcblk0 image someone sent me
Unzip it
Use an sd card boot image tool to create a bootable sdcard with the image (one that can handle a dd image)
You may need to format the sd card to ext4
If it works it may take a long time before it does boot from sd card
mmcblk0.zip
See below for how to write image
https://www.embeddedarm.com/blog/how-to-write-an-sd-card-image-linux-windows-mac-osx/
my mmcblk0 weighs 27.9 Gb (30,000,000,000)
Is it the right size?
Happiness777 said:
Friend and created the mmcblk0 but I am in doubt if the size is accurate
Click to expand...
Click to collapse
Either that link doesn't work or it's not accessible to me
Make sure the sd card is formatted to ext4 when you create the image
The image I posted is 15gb (once unzipped) but since I don't have this device I can't check it
Bricked my razer a while back reinstalling the stock firmware. The cable unplugged from the phone and corrupted the storage. Cant enter recovery or bootloader. But according to some resources that i came across while doing some research, im able to interface with the device using the qualcomm hs-usb protocol. With that im able to directly access the devices storage. If anyone is willing to help, what id need is for you to wipe your device clean, and run these commands
Adb shell
Su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=512 count=30535646
From there id be able to delete the partition table, and copy the devices storage config from the backup. Once thats established id be able to access bootloader recovery and system.
If anyone is able to help, id really appreciate it
Thanks
i too have done the exact same now stuck with a brick hope someone can help
slavix66 said:
Bricked my razer a while back reinstalling the stock firmware. The cable unplugged from the phone and corrupted the storage. Cant enter recovery or bootloader. But according to some resources that i came across while doing some research, im able to interface with the device using the qualcomm hs-usb protocol. With that im able to directly access the devices storage. If anyone is willing to help, what id need is for you to wipe your device clean, and run these commands
Adb shell
Su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=512 count=30535646
From there id be able to delete the partition table, and copy the devices storage config from the backup. Once thats established id be able to access bootloader recovery and system.
If anyone is able to help, id really appreciate it
Thanks
Click to expand...
Click to collapse
hi any look on finding emmc or a work around for this?.i been at it all day i even resorted to opening device up to disconnect battery...nothing
parky169 said:
hi any look on finding emmc or a work around for this?.i been at it all day i even resorted to opening device up to disconnect battery...nothing
Click to expand...
Click to collapse
Nope nothing yet, we need either emmc development files for the phone, no likely to find. And with the qualcomm tools the corrupted storage can be re partitioned and again be written to.
However if someone with a working razer was to wipe the device clean, and dump partition info. Then the images can be written to the device, over writing the damaged partitions.
Black screen on my razer phone. can't access download or recovery. any help will be greatly appreciated. the computer makes a sound when I plug in the razer phone.
sinkoo1979 said:
Black screen on my razer phone. can't access download or recovery. any help will be greatly appreciated. the computer makes a sound when I plug in the razer phone.
Click to expand...
Click to collapse
Your razer is in a state known as EDL. I5s the qualcomm Emergency Download mode. Used to program your emmc storage. That is exactly what the few of us are experiencing, however with no owners of the device willing to share a default wiped image of their emmc, there is no way for us to remap the partitions appropriately in order to once again flash and access the bootloader.
If you could let me know how one would do it I might be able to help you before I sell my razer phone
Thank you, if you restore your phone back to factory settings, connect to pc via adb and run the command in the initial post. That command should (from what i read elsewhere) create a full backup of the partitions on your device. If you are successfull and are able to share through some cloud storage such as dropbox or something of the like, i should be able to restore my razer.
slavix66 said:
Thank you, if you restore your phone back to factory settings, connect to pc via adb and run the command in the initial post. That command should (from what i read elsewhere) create a full backup of the partitions on your device. If you are successfull and are able to share through some cloud storage such as dropbox or something of the like, i should be able to restore my razer.
Click to expand...
Click to collapse
im guessing i will need root to run those commands, atm i am performing a full nandroid backup of everything before i do the reset, my phone is rooted and has twrp installed on both a and b partions
extracted the files, the img is 13GB so gonna compress it before i upload it, hopefully it should work but will have to be tomorrow now
uploading the file now
ok done, heres the link
http://www.mediafire.com/file/j3j6pp3ym161t0q/backup.7z/file
you will need 7zip to extract it which you can get from here for free www.7zip.org
slavix66 said:
Bricked my razer a while back reinstalling the stock firmware. The cable unplugged from the phone and corrupted the storage. Cant enter recovery or bootloader. But according to some resources that i came across while doing some research, im able to interface with the device using the qualcomm hs-usb protocol. With that im able to directly access the devices storage. If anyone is willing to help, what id need is for you to wipe your device clean, and run these commands
Adb shell
Su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=512 count=30535646
From there id be able to delete the partition table, and copy the devices storage config from the backup. Once thats established id be able to access bootloader recovery and system.
If anyone is able to help, id really appreciate it
Thanks
Click to expand...
Click to collapse
hi xda member dtronics has very kindly uploaded a complete back up approx 13gb
file.do you know how to use this to restore/repair our phones?.
Excellent, i will take a look and see if i can push it to the device in edl mode. The thread has been dead for a while, so it may take a while for me to review all the previous resources that led me to the point where i had posted this thread.
Thank you so very much!
This is the article I was using to attempt salvaging my phone.
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Unfortunately I am in the EDL mode where my device storage is not recognized, so I am unable to tamper with it until the razer phones flash programmer or firehose files have been leaked.
Hopefully someone else may have success resurrecting their device using dtronic's backup and or with the information provided in the link.
Thank you any and all of you who have contributed or followed the thread. But my trail ends here unless the flash programmer files are somehow made available.
Unfortunately sadly I too couldn't work out a way to flash or recover razer phone with the upload from dtronics.thank you to all involved,but I think it's time to chuck the old razer in the bin.this is my first ever failure or perm bricked device since I started rooting etc with the HTC wildfire.
?
Tried Klinik handphone medan (google search). They have firehose for msm 8998 but I removed the usb cable when it was flashing (didn't look like it was flashing anything) now the computer don't even recognize the phone....
getting this message "Unknown USB Device (Device Descriptor Request Failed)".
parky169 said:
Unfortunately sadly I too couldn't work out a way to flash or recover razer phone with the upload from dtronics.thank you to all involved,but I think it's time to chuck the old razer in the bin.this is my first ever failure or perm bricked device since I started rooting etc with the HTC wildfire.
Click to expand...
Click to collapse
is there any way to pull the firehose and xml file from working razer phone? getting another one for cheap.
---------- Post added at 04:07 AM ---------- Previous post was at 04:07 AM ----------
slavix66 said:
This is the article I was using to attempt salvaging my phone.
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Unfortunately I am in the EDL mode where my device storage is not recognized, so I am unable to tamper with it until the razer phones flash programmer or firehose files have been leaked.
Hopefully someone else may have success resurrecting their device using dtronic's backup and or with the information provided in the link.
Thank you any and all of you who have contributed or followed the thread. But my trail ends here unless the flash programmer files are somehow made available.
Click to expand...
Click to collapse
is there any way to pull the firehose and xml file from working razer phone? getting another one for cheap.
sinkoo1979 said:
is there any way to pull the firehose and xml file from working razer phone? getting another one for cheap.
---------- Post added at 04:07 AM ---------- Previous post was at 04:07 AM ----------
is there any way to pull the firehose and xml file from working razer phone? getting another one for cheap.
Click to expand...
Click to collapse
I wouldnt know for sure. But my understanding is the programmer files (firehose or sahara files) arent stored on the device. They are used by programmer interface to identify the processor as well as the storage media, possibly all harware for the device. If this were a more mainstream device the programmer files may have been available to us through a leak. Only way to fix it at this point would be to bring it to a shop, they should have access to the files one way or another.
I don't know, I don't have my razer phone any more, went and got myself a OnePlus 6t, the emmc file is still available to download from my post and still looking for people to mirror the file