EDIT: THE DEVDB PROJECT HAS RISEN UP!
https://forum.xda-developers.com/moto-z-play/development/project-real-unbrick-hard-bricked-moto-t3927107
This is so easy to do, and can be sooo helpful if one day You will end with hard-brick.
If you have any questions send me a private message. :good:
Hey! My name is Jacob and I must tell you that there is one common problem with Moto Z Play - OTA after downgroading results in hardbrick :silly:
I have also bricked my device some days ago, since then I have gathered interesting info, probably all old and not so old blankflash files (these were used in the past to unbrick, but don't work now) and two tools, that allowed me to make proper rawprogram0, patch0 and gpt_main0.bin needed for making files, that will allow everyone to unbrick.
But this can be worth nothing without your help. Problem with unbricking, is that last OTA, updated chip security making unable to flash older chip firmware rendering all flashfiles useless. To make new one, I must get some files that are not present in the internet, but are present in ALL working phones. All I need is full mmcblk0 backup. If you want to help follow these easy-peasy instructions:
INFO: Procedure bellow excludes EFS, MODEMST1, MODEMST2, FSG, BACKUP partitions from backup. These are your phone specific partitions, that contain sensitive information like IMEI, serial numbers etc, but this guide shows how to avoid them while backing up so you don't have to worry about it
Prerequisites:
1. Your phone might be rooted (but doesn't have to be), definitelly should be working and not messed up too much.
2. You must have at least 32 GB micro sd card
3. Any ROM, even custom will be good, but if you have stock, you get +1 point
Steps:
1. If you have TWRP recovery, boot into it and go to step 2.
If you don't have, here is official one https://eu.dl.twrp.me/addison/ - rename it to "twrp.img" and boot to it with
Code:
fastboot boot twrp.img
2. Backup your /data partition and keep it in safe place
3. Format sdcard in ext4 (it is more robust and failsafe) or FAT32/exFAT (if you are on windows).[/URL]
4. Wipe /data on your phone and insert sdcard. Under "Mount" tab in TWRP, check box next to SD-CARD.
5. Open TWRP terminal emulator (It is in advamced tab), type "su" and run these command:
If you trust me that I won't do bad things with your IMEI:
Code:
dd if=/dev/block/mmcblk0 of=/[U][I]"Ext sd location here"[/I][/U]/Loader.img bs=4096
This just makes full-backup of your all partitions from Qualcomm chip.
OR
If you don't trust me:
Code:
dd if=/dev/block/mmcblk0p[B][COLOR="Red"]X[/COLOR][/B] of=/[B][COLOR="DeepSkyBlue"]Y[/COLOR][/B]/mmcblk0p[COLOR="Red"]X[/COLOR] bs=4096
Where X is number of partition from 1 to 54 BUT NOT: 27 (modemst1), 28 (modemst2), 29 (fsg)
and Y is location of your SD-CARD. This will only back up partitions without IMEI, and other phone-specific info.
6 Generated files will be HUGE (~27GB). Copy them to pc and upload to cloud. Maby https://mega.nz/ - probably only they have enough space for that file for free.
7 Post link here or send it to me via Private Message.
8 That's all! If you managed to get here, all comunity is grateful, :highfive: you will be included as biggest contribuor to the new thread I will make in near future!
If I find the time I will throw my old Z Play back to stock and try this. But can take a while before I have that time. Especially uploading that amount of data which would take me at least 12 hours. So if I do that, I will most likely get it into a split archive
Unfortunately I don't have a 32Gb sdcard. If there's another way to do this, I'm willing to help
Camarda said:
Unfortunately I don't have a 32Gb sdcard. If there's another way to do this, I'm willing to help
Click to expand...
Click to collapse
The only other way I know would be a USB C OTG adapter and a USB stick...
Artim_96 said:
If I find the time I will throw my old Z Play back to stock and try this. But can take a while before I have that time. Especially uploading that amount of data which would take me at least 12 hours. So if I do that, I will most likely get it into a split archive
Click to expand...
Click to collapse
Camarda said:
Unfortunately I don't have a 32Gb sdcard. If there's another way to do this, I'm willing to help
Click to expand...
Click to collapse
Thank you very much guys! You don't even know how much did you motivated me to continue research when I got your responses. If you will have any problem, ask me for advice - I will try to help. :highfive:
In case of Artim_96, you probably know this one, but to split dd image, you can use (obviously) "skip" parameter, for example:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_1.img bs=4096 count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_2.img bs=4096 skip=10GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_3.img bs=4096 skip=20GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_4.img bs=4096 skip=30GB
In case of Camarda: ...
Code:
adb -d shell su -c busybox dd if=/dev/block/mmcblk0 bs=4096 > D:\mmc.bin
... should do the job, where "D:\mmc.bin" can be any other valid location on your pc.
To make this work, you must have root and busybox installed.
Bobernator said:
In case of Artim_96, you probably know this one, but to split dd image, you can use (obviously) "skip" parameter, for example:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_1.img bs=4096 count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_2.img bs=4096 skip=10GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_3.img bs=4096 skip=20GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_4.img bs=4096 skip=30GB
Click to expand...
Click to collapse
that would be a solution, but I guess it's way easier to create one image, zip it and let it get split to about 5 GB chunks, and probably creating a check sum for each before upload
---------- Post added at 17:02 ---------- Previous post was at 16:56 ----------
but what I don't get: I should make a backup of /data, for what? And then I should connect the phone to my PC, but the following commands look very much like linux commands, so the connection to PC seems unneccessary. Plus, for what reason does the SD Card need to be ext4? the commands should work with exFAT too plus no windows system can read ext4. And there is no program to read it for Windows that's slow as hell
Artim_96 said:
that would be a solution, but I guess it's way easier to create one image, zip it and let it get split to about 5 GB chunks, and probably creating a check sum for each before upload
---------- Post added at 17:02 ---------- Previous post was at 16:56 ----------
but what I don't get: I should make a backup of /data, for what? And then I should connect the phone to my PC, but the following commands look very much like linux commands, so the connection to PC seems unneccessary. Plus, for what reason does the SD Card need to be ext4? the commands should work with exFAT too plus no windows system can read ext4. And there is no program to read it for Windows that's slow as hell
Click to expand...
Click to collapse
Sorry, I was in a bit hurry when I was writing tutorial. I have just corected misteakes in it. :silly:
That part with backing up /data and wiping it is just for Your comfort - You probably don't want to include all you photos, videos contacts etc, in the backup, I am wrong?
EDIT: You are right, solution with splitting archive is clearly better, becouse of smaller size and auto merging archives
Bobernator said:
Sorry, I was in a bit hurry when I was writing tutorial. I have just corected misteakes in it. :silly:
That part with backing up /data and wiping it is just for Your comfort - You probably don't want to include all you photos, videos contacts etc, in the backup, I am wrong?
EDIT: You are right, solution with splitting archive is clearly better, because of smaller size and auto merging archives
Click to expand...
Click to collapse
Would it help you to get /data too? It's my old phone, screen is quite damaged so there is nothing worth looking for on it. Plus it was completely wiped twice by flashing the firmware with flashfile and unlocking the bootloader again since flashing the firmware locked it.
Data partition is absolutely not needed, but thanks for asking!
zip compressing was totally worth it. It went from 29.1 GB to just 2.58 GB?
Artim_96 said:
zip compressing was totally worth it. It went from 29.1 GB to just 2.58 GB?
Click to expand...
Click to collapse
Thanks for support!
@Camarda - You are from Brasil, so you probably have different version of software, so if you will upload it, phones outside of Europe can be safed too. Do you still want to help?
Bobernator said:
Thanks for support!
@Camarda - You are from Brasil, so you probably have different version of software, so if you will upload it, phones outside of Europe can be safed too. Do you still want to help?
Click to expand...
Click to collapse
I just sent you the file, tell me if everything is ok
Thank you! Artim's backup is not working on my phone, and I suddenly realised that my exam ending my school are in less than month (!), so I didn't have time neither to write a thread, nor to reverse engineer the file, but I will try to find time and test your backup!
Ps. Don't worry about me beeing temporiarly inactive, this thread is my current target and I won't give up!
Bobernator said:
Thank you! Artim's backup is not working on my phone, and I suddenly realised that my exam ending my school are in less than month (!), so I didn't have time neither to write a thread, nor to reverse engineer the file, but I will try to find time and test your backup!
Ps. Don't worry about me beeing temporiarly inactive, this thread is my current target and I won't give up!
Click to expand...
Click to collapse
Bobernator, I'm just posting to let you know that I am very thankful for your efforts and to take as long as you need. I have a LATAM XT1635-02 that got bricked by an automatic update quite a few months ago. It's in fastboot state. If there is anything I can do to help, let me know.
I now own a XT1710-06, so if you think the files from it could be useful, let me know.
Welcome again! My exams have just ended (I hope they went well) I am temporally at my uncle's house so I don't have access to files and info I've gathered, but I will return to home at friday and even Easter will not stop me, becouse I have decided to start DevXDA project!
Stay with me guys
Fulcano said:
Bobernator, I'm just posting to let you know that I am very thankful for your efforts and to take as long as you need. I have a LATAM XT1635-02 that got bricked by an automatic update quite a few months ago. It's in fastboot state. If there is anything I can do to help, let me know.
I now own a XT1710-06, so if you think the files from it could be useful, let me know.
Click to expand...
Click to collapse
I think I you can easly fix your phone, since fastboot works. You will need factory update zip, it is pinned somewhere in this forum, but if you feel unsure (you can brick phone even harder with this method if it goes wrong), I can assist you during the weekend and share a link with correct zip.
And thanks for support!
Device which you have is Moto Z2 Play (albus) that have next version of the chip in Moto Z Play (addison). My plan is to fix addison by combining some of the firmware from it and albus, but these files are available freely and you don't need to send them.
Bobernator said:
I think I you can easly fix your phone, since fastboot works. You will need factory update zip, it is pinned somewhere in this forum, but if you feel unsure (you can brick phone even harder with this method if it goes wrong), I can assist you during the weekend and share a link with correct zip.
And thanks for support!
Device which you have is Moto Z2 Play (albus) that have next version of the chip in Moto Z Play (addison). My plan is to fix addison by combining some of the firmware from it and albus, but these files are available freely and you don't need to send them.
Click to expand...
Click to collapse
Thanks for the reply! Sorry, i've been quite busy with exams as well.
It's been a while since the phone is bricked, and i think fastboot was the wrong word. When it is plugged in it appears as a qualcomm device and the LED blinks, but other than that the phone does absolutely nothing. I remember being unable to unbrick it because of needing a `programmer.pem` file specific to the version of android that was installed.
The phone had an unlocked bootloader, twrp and supersu. It got stuck during an OEM update from 7.1.1 (i think) to 8.0.0. It was stuck for over four hours, I turned it off by force and then it never turned on again .
With regards to the Moto Z2 files, that's fantastic to hear. If there's anything else I can do to help, please say so. I've configured email alerts now so i'll get notified when you reply .
Thanks for the effort!
Related
Similar to Adrynalyne's post, I would greatly appreciate anyone that could do this. What I am looking for is a dump from a completely stock system, the only requirement is that you be rooted. So, if ANYONE has a completely stock Continuum and would be willing to do this, that would be great. It would also be good to get this from both DJ20 and DL17 if possible, but even getting it from just one of the two would be great. Here are the steps to produce the files.
This is easiest to do via adb.
As root (#)
To backup the .lfs partition
Code:
dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
To backup the kernel parition:
Code:
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
To backup the recovery partition:
Code:
dd if=/dev/block/bml8 of=/sdcard/recovery.bin bs=4096
To backup the system partition:
Code:
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
To backup the dbdata partition:
Code:
dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096
To backup the cache partition:
Code:
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
Once you have the files, zip them together and upload them to a sharing site (Dropbox, MediaFire, Megaupload, personal webhost, etc.) and post a link to them. If you don't want the link in the public, feel free to PM me a link to download the file. Once we have these, it will be much easier to do development work, especially with the voodoo kernel. Thank you to anyone that follows this and sends files.
EDIT: Received stock DJ20, which is a definite plus. Now for DL17
is it possible to grab these from a non-activated continuum?
I still have that phone that won't boot if you end up with something you'd like to try... for now..buddy's leg is broken and he's not moving around too much right now.. plus he's been playing on a droid X...
dottat said:
is it possible to grab these from a non-activated continuum?
I still have that phone that won't boot if you end up with something you'd like to try... for now..buddy's leg is broken and he's not moving around too much right now.. plus he's been playing on a droid X...
Click to expand...
Click to collapse
It is possible as far as I know. The only thing this really requires is root access, the phone being activated shouldn't really do anything to the file dump. If you'd like to try to resurrect the dead phone, I'll be posting up a DJ20 Odin file later tonight or tomorrow morning that should hopefully work to fix it if all that is dead is the file system structure.
Yah,
it if nearly impossible to brick the galaxy s phones (as long as you see the samsung logo even for a second), because we can use odin.. The only problem is getting the files to flash to fix it xP
Dottat: since you are not using this phone, may you please allow us to use this device for our sake? We need a device to send to the devs
Please man, it would be much appreciated and, you would eventually get it back, so no worries <3
Well... this phone is due back to the carrier (surprised they haven't called for it yet).... so at this point i would just like to prove proof of concept on the recovery piece. Download mode is all this phone will do so i'll be curious to see where we get with the odin imnuts is posting tonight..
imnuts said:
Similar to Adrynalyne's post, I would greatly appreciate anyone that could do this. What I am looking for is a dump from a completely stock system, the only requirement is that you be rooted. So, if ANYONE has a completely stock Continuum and would be willing to do this, that would be great. It would also be good to get this from both DJ20 and DL17 if possible, but even getting it from just one of the two would be great. Here are the steps to produce the files.
This is easiest to do via adb.
As root (#)
To backup the .lfs partition
Code:
dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
To backup the kernel parition:
Code:
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
To backup the recovery partition:
Code:
dd if=/dev/block/bml8 of=/sdcard/recovery.bin bs=4096
To backup the system partition:
Code:
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
To backup the dbdata partition:
Code:
dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096
To backup the cache partition:
Code:
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
Once you have the files, zip them together and upload them to a sharing site (Dropbox, MediaFire, Megaupload, personal webhost, etc.) and post a link to them. If you don't want the link in the public, feel free to PM me a link to download the file. Once we have these, it will be much easier to do development work, especially with the voodoo kernel. Thank you to anyone that follows this and sends files.
EDIT: Received stock DJ20, which is a definite plus. Now for DL17
Click to expand...
Click to collapse
Unable to dump . Keep getting this error with each block.
sdcard
sdcard not sdram
PZ PZ
I have a DL17 I want to root the phone but i dont want to make my phone un-returnable if something were to happen to it. so My question is what does Verizon consider illegal software. Does this mean root and all Available after market roms. is it the same as buying a new car on loan and putting after market parts Rather.?
remotehunger said:
I have a DL17 I want to root the phone but i dont want to make my phone un-returnable if something were to happen to it. so My question is what does Verizon consider illegal software. Does this mean root and all Available after market roms. is it the same as buying a new car on loan and putting after market parts Rather.?
Click to expand...
Click to collapse
rooting does void your carrier warranty...but not your samsung warranty...
however if you unroot/return to stock before returning your phone for whatever reason thats fine, they wouldnt know
*if* you brick your phone (nearly impossible to do with odin files) and try and return after a mod/rom gone bad....thats a big no-no...and the reason carriers/oems are locking down devices.
read up on rooting and the pros/cons before diving in...but for the most part if you are careful...its safe
I know how I know how I'm pretty experienced I have rooted 5 phones including hero cdma a droid erris to touch pro 2 2 different carriers also some minor a developing a bit but the only thing is I don't wanna have to send it samsung is something
Sent from my SCH-I400 using XDA App
if something does go wrong because accidents do happen I just wanna make sure that the phone is
unrootable and that there are available stock odin files but other then that I would be more than happy to dump for you guys and I could possibly help with the dip in developing as well give me your instant messenger or phone number so we can get together
Sent from my SCH-I400 using XDA App
EDIT: i must've been high LOL!
i was wondering if anyone knows where i can get all of these as i sorta repartitioned the phone and lost everything on it. i can get it into download mode just fine just im missing alot of peices. it loads the factory.rfs fine but i think the bootloader is gone. i even managed to get it into clockwork but since the boot partition is kinda messed up it wont boot into anything else. since theres not a factory firmware that i can find im sorta stuck
I figured Id start another thread so no one has to search and read thru all other threads for help like I had to.
I had to write this because i thought other guides were incomplete, and frankly they didnt work.
I will try to update and make things easier to read and use spellchecker when time permits.
and add in-between steps that i left out because i have no dam time. Thats why i call it expert guide-you need some knowledge of doing this.
This is just to help out someone who has had a hard time with other guides
It is not a step by step
Knowledge of cygwin and adb is expected.
Learn it, and how to setup, using google and xda like the rest of us.
I TAKE NO RESPONSIBILITY OF BRICKING YOUR PHONE ANY MORE THAN IT IS.
Here is were I made the mistake:
http://forum.xda-developers.com/showthread.php?t=1745865
These are the 2 files
1.Galaxy-S-fre3-2.51.zip
2.Galaxy-S-fre3-MD4FirmwareModemAIO.zip
First of all I ALWAYS CHECK MDMSUMS
The second zip was flashed first, and wamo no andro
Heres my specs.
Android Ver:
4.3
Baseband Ver:
L710VPUCMK3
Build:
JSS15JL710VPUCMK3
Hardware Ver:
L710.14
Im guessing it bricked my phone because I flashed the Galaxy-S-fre3-MD4FirmwareModemAIO.zip before the actual rom itself "Galaxy-S-fre3-2.51.zip"
Obviosly I should have done it the other way around, well im only hu............ngry. haha, so im a knuklehead.
I refuse to go to that particular site to read the first post and see if there is some sort of DONT FLASH OUT OF ORDER OR RISK LOOSING A LIMB, warning posted.
I thought i lost my device (this is still a bad-ass phone, almost too nice to be in a roofers pouch and getten toren up. But it takes really nice pictures of my custom work, and takes em fast so i can get back to work.
I lost 12 hours for stupid mistake, (im sure someone will say thats the business, of course thats why we do it.)
Not to mention the last device i bricked was my first (Hero) and thought was my last.
When you play the Rom Game you may get Ram'd
I will post this to that fre3 site, however unless the OP makes note of this others will be in the same mess.
The only life left in the device, was red light, when battery removed (when battery was placed in during charge, red light went out in 5 to 10 sec.)
When battery was in unit, no lights at all.
I noticed when usb cable attached to ubuntu, oh **** i forgot what and how i saw it but it was some kind of Qualcomm Device _DLMODE or somthing.
I will edit this post when i find it again, but anyway that led to nothing.
My first attempts were made following this guide: http://forum.xda-developers.com/showthread.php?t=2369125
I couldnt figure out by reading the threads if how I was to format the fat32 partition default 8 or 4 or 1Mg
I couldnt understand why we would have to try to write the image over and over...Why it wouldnt write it right the first time.
I had a hard time trying to write the image file ..debrick_sph_l710.img to sdcard using my v-box..
(Virtual-Box under windows 8 with Ubuntu 13.10 installed ....Android-Kernel-Build ready ).
After trying all the different ways and different images, I said screw it i give up.
.........Till after dinner
wife made a roasted chicken not gonna be late.
Finally I made my own image from my wifes phone, because we bought them at the same time.
One problem hers isnt rooted and she wasnt about to let me touch it.............
Solution: I bought her a galaxy4 for 49.00 /w upgrade, now i have 2 galaxy 3's. But only one works.:/
That was a pain rooting because she always excepts the firmware upgrades when they come over air.
Couldnt get the "seLinux seAndroid" thing so i just went back to 4.1 for now so that i could adb.
Heres What Did It...
http://forum.xda-developers.com/showthread.php?t=2345860
HERES HOW I DID IT
To extract a de-brick image from your phone (an UnBricked Phone) do in an adb shell:
If you know the partition use:
dd if=/dev/block/mmcblk0 of=/sdcard/HomefixSprint_S3_L710.img bs=1048576 count=70
If not use:
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/HomefixSprint_S3_L710.img bs=1048576 count=70
MY TERMINAL SHOWS:
C:\Users\dad>adb shell
[email protected]:/ # busybox dd if=/dev/block/mmcblk0 of=/sdcard/HomefixSprint_S3_L710.img bs=1048576 count=70
0 of=/sdcard/HomefixSprint_S3_L710.img bs=1048576 count=70 <
70+0 records in
70+0 records out
73400320 bytes (70.0MB) copied, 4.578239 seconds, 15.3MB/s
Take that image, copy it to your cygwin directory and write it to an unformatted 16mb sdcard using cygwin:
TO GET THE SDCARD READY:
get EaseUS Partition Master Free Edition-Free For Home Users
and find the sdcard, its about 14.82GB, if u have more than 1 your on your own.
Select that one, and delete all partitions.
Then, New partition, select fat32, and then finish by applying the operations.
DO NOT FORMAT
IN CYGWIN:
Get sdcard info:
cat /proc/partitions
MY TERMINAL SHOWS:
[email protected] ~
$ cat /proc/partitions
major minor #blocks name
8 0 976762584 sda
8 1 976759808 sda1
8 16 117220824 sdb
8 17 358400 sdb1
8 18 116859904 sdb2
8 32 976762584 sdc
8 33 976759808 sdc1
8 48 244198584 sdd
8 49 244196001 sdd1
8 64 976762584 sde
8 65 976657408 sde1
8 80 976762584 sdf
8 81 976760001 sdf1
8 96 976762584 sdg
8 97 976760001 sdg1
8 112 976075776 sdh
8 113 976074752 sdh1
8 128 15558144 sdi
8 129 15558110 sdi1
[email protected] ~
$ ls
debrick_sph_l710.img HomefixSprint_S3_L710.img kitchen
[email protected] ~
$ dd if=HomefixSprint_s3_L710.img of=/dev/sdi
143360+0 records in
143360+0 records out
73400320 bytes (73 MB) copied, 338.771 s, 217 kB/s
I DID WHAT I WAS SUPPOSED TO DO:
Put battery in
Connect usb cable
Insert sdcard
Vol-up/Home and Power
I felt the vibration no more than a second after pressing power (along with vol_dwn and home key pressed and held)
As you can imagine, my adrenilin was pumpped to the point of feeling like i smoked a pack of camel ciggirettes, AGAIN, as i try to boot the phone.
I knew i was out of the woods after I saw the samsung logo.
It Skipped past download.
I was able to boot right into my desktop, however there were no signal bars.
and the Baseband ver: was unknown.
I powered down the phone (man that was hard to do) but i did.
Tried to get into download mode but failed at first, recovery failed also.
Finally got to download then i was good.
NOTES:
After I revived the phone I had nothing too loose because now I had 2 S3's, so I played a bit.
Its fun to brick your phone on purpose haha
I fed this PIECE OF S#!+ Galaxy-S-fre3-MD4FirmwareModemAIO.zip to my phone the first time and i lost 12 hrs plus the time write this.
:The debrick_sph_l710.img or the Debrick_Sprint_S3_L710_4.3.img did not work for me
:I did not need the class 10, class 4 worked too
:did not need cable attached
:did not Matter wich order i put battery, sdcard, usb-cord to boot
:did not format card
nly took 1 try to write working image each time ( didnt take several attemts) I wrote and tested 3 different images.
:Upon booting It seems to be the same each time ,couple three four sec (out of a few times playing it may have taken 10sec to boot on one occasion).
:I think the issues with ubuntu was,the sdcard was not ejecting properly and corrupting the image.
:If you have a sucssesful write to sdcard, it may not show up in file explorer until you pull out card reader and re-insert it... then it will show up in file explorer as a folder called "image" with bunch of files or somthing in it, then you know it wrote ok.
:for some reason after i haha... BRICKED MY SG3 ON PURPOSE....Oh my GOD....Im SHOT, booted to my homemade image, i was able to boot into recovery as well as Download.
:Not for nothen I tried to:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/sdcard/modem.img of=/dev/block/platform/msm_sdcc.1/by-name/modem
(Remember i was able to boot to system, so adb worked)
Did not work, however it may have worked if i used the syntax...mmcblk0 and such.
Questions:
Why is my debrick.img smaller than others on this site
Why my image works for my device and no others will work
Are all phones with these snapdragon cpu's have the ability to "sdcard boot"
Why do we spend endless hours with our phones and forget we have a family.
MY FILE:................ http://rooferdave.com/Downloads/sprintsg3.html
Like I replied to you in the other thread, the problem with what you did is that you flashed MD4 firmware while on the MK3 bootloader. It has nothing to do with the ROM.
At the time the MD4 rom was posted, MK3 had not even come out. So anger at the lack of a warning in that thread is misguided.
Further, there are multiple places where you could have found information on this.
1) http://forum.xda-developers.com/showthread.php?t=2541343
2) http://forum.xda-developers.com/showthread.php?t=2637424
I did the EXACT same thing as you did and bricked my S3 this morning.
I've attempted your fix but I am really all over the place.
Is there any way your guide could be simplified/condensed for someone like me?
I can get Ubuntu to run on another machine. I have a 16GB Micro SD. But I am not sure at all on the following things...
a) which file I am supposed to flash to the micro sd card
b) once I open Ubuntu/linux how to find that file by navigating to my Windows installation.
If you don't have time...thanks anyway for your guide..I'm sure I'll get there eventually.
CNexus said:
Like I replied to you in the other thread, the problem with what you did is that you flashed MD4 firmware while on the MK3 bootloader. It has nothing to do with the ROM.
At the time the MD4 rom was posted, MK3 had not even come out. So anger at the lack of a warning in that thread is misguided.
Further, there are multiple places where you could have found information on this.
1) http://forum.xda-developers.com/showthread.php?t=2541343
2) http://forum.xda-developers.com/showthread.php?t=2637424
Click to expand...
Click to collapse
No reason why op didnt take the extra step and warning us this can happen, I would.
My time is very limited lately, and dont have the time to read thru all fourms.
As far as my residual anger, left over from wasting my time, unbricking my phone. Oh well
Like I said I would have placed a warning for half-noobs like myself to prevent this. OTHERS DO!
And not for nutten I still dont see any warning up it up.
edderspcs said:
I did the EXACT same thing as you did and bricked my S3 this morning.
I've attempted your fix but I am really all over the place.
Is there any way your guide could be simplified/condensed for someone like me?
I can get Ubuntu to run on another machine. I have a 16GB Micro SD. But I am not sure at all on the following things...
a) which file I am supposed to flash to the micro sd card
b) once I open Ubuntu/linux how to find that file by navigating to my Windows installation.
If you don't have time...thanks anyway for your guide..I'm sure I'll get there eventually.
Click to expand...
Click to collapse
Sorry I really dont i wasted it unbricking my phone
Look on the bright side, you have a really good shot of unbricking your phone.
wasnt long ago this kind of thing would be impossible.
Good Luck
Homefix said:
Sorry I really dont i wasted it unbricking my phone
Look on the bright side, you have a really good shot of unbricking your phone.
wasnt long ago this kind of thing would be impossible.
Good Luck
Click to expand...
Click to collapse
Actually got it. I got some help on Cygwin in the other thread and trial and error from there. Your debrick file was the one that finally worked. Thanks.
Homefix said:
No reason why op didnt take the extra step and warning us this can happen, I would.
My time is very limited lately, and dont have the time to read thru all fourms.
As far as my residual anger, left over from wasting my time, unbricking my phone. Oh well
Like I said I would have placed a warning for half-noobs like myself to prevent this. OTHERS DO!
And not for nutten I still dont see any warning up it up.
Click to expand...
Click to collapse
The biggest thing that sticks out here is the word READ. You say you don't have time to read the forums, but yet you find the time to search a thread that has not been update since July 2013 in the OP (Last edited by freeza; 31st July 2013 at 12:36 AM.). And yes Noobs will be Noobs, But not all Noobs don't take the time to read before flashing stuff to there phone.
This was the one that worked!!! Thanks!
Question
Where you asay Connect usb cable was it plugged into power or your computer ?
WOW! is all I can really say.
Well that and Freeza! Really!
Freeza, BTW has 9,465 thanks on XDA. oh, I would also add that heaven help us if dev has to start putting warnings on that state "you may have problems with any future upgrades that samsung/sprint may put out in the coming years".
I guess I could say even more. Just won't...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
[OBSOLETE THREAD]
This thread is obsolete. A solution was found, which is posted here:
http://forum.xda-developers.com/g4/help/method-to-root-lg-g4s-model-h735-lg-g4-t3248030
Please use the new thread for discussions.
------------------------
Original thread:
------------------------
Hi,
I have been trying to root the LG G4S (H735), also known as "LG G4 Beat".
I tried two things:
Approach 1
I tried the method posted by konsolen in this thread:
http://forum.xda-developers.com/g4/general/lg-g4s-world-root-lg-devices-t3231759
but it didn't work for me. I tried several times with varying approaches, but the boot process always gets stuck on the LG logo.
Approach 2
I also tried to inject the root as suggested in this thread for the G4:
http://forum.xda-developers.com/g4/help/rooting-lg-h735-g4-beat-t3192491
I've used the Inject_Root_G4.zip from this link, which I believe is the same shared elsewhere:
https://mega.nz/#!BIxUzbqI!nt2YnGnGQlSiBQ-Ar-c-q7oDMIEsg6xd0Kmek-q0clg
And I get the same problem - stuck on the LG logo when booting.
For anyone who wants to reproduce Approach 2 to maybe find a solution:
1. Start up LGFlashTool2014. You can follow instructions in thread by konsolen (see Approach 1 above). You can use his .kdz file as well. Important: Pull out your USB cable as soon as the green letters COMX (with a number instead of X) appear on the phone. My flashtool actually didn't display the progress percentage, but apparently this at 9%. It doesn't matter if you don't see the percentage though, I've verified with this KDZ image that if you pull the cable at the very moment the green letters appear, nothing is corrupted. The phone will still display 0%. Leave it as it is after you unplugged the cable.
2. Kill your flash tool with the windows task manager. After it closed, you can plug the phone back in and open a windows command line in the folder where your Send_Command.exe is (you can download the package in konsolen's instructions which contains Send_Command.exe as well).
3. Open the console to your phone with
Code:
Send_Command.exe \\.\COMX.
(with your number instead of X)
You will have to do steps 1-3 every time you want to get this console, for example to run all the dd commands below.
4. Calculate the dd parameters and backup your system partition into a .img file. There is an excellent guide by dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
5. Keep a copy of your system.img somewhere safe, you can use it to restore your system if something goes wrong. So don't use this original in the next steps!
6. Copy the .img file to a linux system and mount it. I'm guessing who is trying this knows how to do this. Anything you change in the folder you mounted the image on, will be saved in the image. You can then use this updated image to overwrite your original system partition, again with dd (as described in the thread by dominik-p) using your parameters. So here's the crucial bit: You get root access to your system files via linux. When you know the right things to mess with, you can root your phone with the updated image. Injecting the root as done in step 8 is one way to change the system on the G4 in order to root it.
7. [Optional] If you are new to this, you may want to do a simple test before you continue.
Create a testfile (test.txt) on the mounted system partition. Then copy the .img file back to your phone and try to "dd" it back over your system partition.
Then, check if you see the test file on your system partition -- you may have to reboot the phone after the dd command (and log back in with Send_Command.exe) in order to see the updates.
8. Inject root with the Inject_Root_G4.zip on the mounted folder of the image on your linux system. You can follow instructions (Step 2) here:
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
9. Copy the new img file to your phone and "dd" it over your system partition, using your own dd parameters.
10. Reboot the phone (you can also just type LEAVE in the Send_Command.exe console).
Now, it should be rooted - if it worked for you!
If it worked for you, that's great. It didn't for me, it got stuck on the LG logo in the boot process again. So I had to write my original system.img back onto my system partition to get the phone back.
I did get the following errors in Step 8 above, though I did try anyway to use the resulting image. The errors may have something to do with my problem, but it may also be because the inject root is for the G4, not the G4s.
Code:
sudo ./autoroot.sh
cp: cannot create regular file ‘operatingtable/lib64/libsupol.so’: No such file or directory
chmod: cannot access ‘operatingtable/lib64/libsupol.so’: No such file or directory
chcon: cannot access ‘operatingtable/lib64/libsupol.so’: No such file or directory
chmod: cannot access ‘operatingtable/bin/app_process64_original’: No such file or directory
chcon: cannot access ‘operatingtable/bin/app_process64_original’: No such file or directory
chmod: cannot access ‘operatingtable/bin/app_process_init’: No such file or directory
chcon: cannot access ‘operatingtable/bin/app_process_init’: No such file or directory
If anyone finds a solution to this, or has any ideas what could be tried, I would be very interested to hear it. I'm new to rooting phones and don't have much experience beyond what I did in the last days.
Cheers
Jennifer
jen.magnolis said:
4. Calculate the dd parameters and backup your system partition into a .img file. There is an excellent guide by @dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Click to expand...
Click to collapse
Happy that my guide has helped you
As I said here:
http://forum.xda-developers.com/g4/help/rooting-lg-h735-g4-beat-t3192491/page5
Everyone who is interested to inject root must edit the autoroot.sh from the inject.zip and use the correct files from SuperSU
More information about the files:
https://su.chainfire.eu
Maybe you have to use other files. Not the files from the inject.zip
Download the Update-SuperSU zip from http://download.chainfire.eu/supersu
Copy the files you need to the "su" folder of the extracted inject.zip
For information which files are needed read the "update-binary" file from the SuperSU zip.
(located here META-INF/com/google/android/update-binary)
Good luck everyone :good:
Thanks again for the links! I'll try again soon, when I get time for it, and report the results here
By the way, here's the ls -lR of my system.
Ok, no problem, take your time.
I've got also lot of other work to do...
I just read your system.txt (thanks)
According to these lines:
Code:
lrwxr-xr-x. 1 root 2000 13 Aug 24 02:05 app_process -> app_process32
-rwxr-xr-x. 1 root 2000 13588 Aug 24 02:05 app_process32
It seems that the firmware is 32 bit.
More info about your firmware is in /system/build.prop
So you have to take the right lines from update-binary and copy them and edit the autoroot.sh
Please don't ask me which lines. It's a bit difficult... (you have to understand the logic in update-binary)
Then copy the files from the right folder (arm?) to the "su" folder.
Sorry. I'm out now here for the next time. I have a H815 and happy with it.
I think you will find the solution. :good:
Custom Recoverys
Hi All
Are there any custom recovery's for the G4 beat/G4s
Thanks
Thanks dominik-p for your help. Good luck with your other work, don't worry I won't distract you with asking questions You already helped a lot.
benji5688, you can check for official firmware (.kdz file) on this link, pasting your IMEI instead of YOUR-IMEI in the link below.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI
I did not find any for mine there, but I did find it on
http://devtester.ro/projects/lg-firmwares/
Which brought me to this link where I could find mine:
http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz
but you should look for your specific model.
jen.magnolis said:
Hi,
I have been trying to root the LG G4S (H735), also known as "LG G4 Beat".
I tried two things:
Click to expand...
Click to collapse
LOL
I did the exact same thing as you, and really the EXACT, I also contacted dominik-p for the same problem you got with the bs. LOL
Was about to do the same thing you did here too just told that to dominik-p lol.
You post is great, well detailled. Hope someone found something
But got something different. my phone is the LGH731 LG G4 Vigor from Videotron in Canada.
If someone need files or system.img LINK
That's not the exact same thing as the post owner but i'm pretty sure the root method will be. (DON'T use this system.img to inject in you H735) it's from a H731 and they don't have the same partition size.
Ha, that's funny, and you got the same problem of course (frozen logo boot).
We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.
First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back
Meanwhile, if you get any new results, let me know.
Cheers
jen.magnolis said:
Ha, that's funny, and you got the same problem of course (frozen logo boot).
We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.
First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back
Meanwhile, if you get any new results, let me know.
Cheers
Click to expand...
Click to collapse
Yes i'm trying this today (the 32-64 bits thing)
Custom recovery
What does this file do though?
Is it a custom recovery or is it the stock rom?
Thanks Benji
benji5688 said:
What does this file do though?
Is it a custom recovery or is it the stock rom?
Thanks Benji
Click to expand...
Click to collapse
It's the stock ROM. It can be used for recovery, depending what your problem is. If you destroyed your ROM by trying to root, you can recover with this.
If you mess with something in your system partition (where the Android OS is installed), you'd need a copy of your individual system partition (like a "backup") to restore. This highly depends on your phone/version, so you have to do this backup yourself. You can follow the instructions with the dd parameters, linked to from the main thread.
Are there any custom recoverys
Hi
Are there any custom recovery available, I want to get Xposed.
Can anyone make one?
Thanks for all the help
benji5688 said:
Hi
Are there any custom recovery available, I want to get Xposed.
Can anyone make one?
Thanks for all the help
Click to expand...
Click to collapse
I far as I know to get Xposed you need to be rooted... Well there is no root method availaible, well you can try the methods that Jen explained here but I doubt they will work... if yes, you lucky ****
Is the g4s running marshmallow? Is so you would need to use a compatible su install.
Sent from my VS986 using XDA Free mobile app
larsdennert said:
Is the g4s running marshmallow? Is so you would need to use a compatible su install.
Sent from my VS986 using XDA Free mobile app
Click to expand...
Click to collapse
No the problem is really just changing the 64 bits command to make then use the 32 bits ones
I manage everything except this one
Code:
chcon --reference=operatingtable/bin/app_process32 operatingtable/bin/app_process64_original
I agree with xsteacy, this will most likely not work, that's why we opened this discussion
We just have to find the right files to use (instead of the 64 bit ones).
I will get back onto the subject by Wednesday when I have time.
I solved it! My phone is rooted
I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.
Good times!
jen.magnolis said:
I solved it! My phone is rooted
I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.
Good times!
Click to expand...
Click to collapse
0.0 OH!?
Ok I'm putting it out there for others to test as well.
Please report if it worked so I can take this into account before updating the main thread instructions.
In the attached .zip file there is a README with instructions.
Note: Thanks goes to @konsolen who shared instructions on how to open the COM port on the H735.
The script in konsolens post is essentially the upater-binary script of the SuperSU package, but with a few modifications.
That may have been necessary on konsolens phone, but it didn't work on mine. For me, using the original script worked.
However, the zip file has to be extracted manually with busybox before the updater-binary script is started. I am not
sure if busybox absolutely needs to be in the /sbin folder, but that's where I saw elsewhere that it belonged, so
I moved it over there in my script. I haven't tested this with busybox being elsewhere.
Thanks goes also to @dominik-p for sharing the link to excellent documentation and for his instructions on how
to make a backup (with dd) of your system, in case anything goes wrong.
UPDATE: I did all commands in root_lgh375.sh manually when I found it already worked, so please report if all is good with the script, but I think it should be, it only does what I did manually.
Congratulations @jen.magnolis
Well done
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