Related
Hi guys.
I have a rooted DZ thas is acting up on me and i have decided to send it in for repairs.
Somehow i managed to lose my part7backup file. Am I out of luck or is there any way to return it to stock?
my carrier is Tele2 but they sell all their phones unbranded and unlocked if that is of any help.
Thank you in advance
PS. Im sorry for my bad english.
chriva said:
Hi guys.
I have a rooted DZ thas is acting up on me and i have decided to send it in for repairs.
Somehow i managed to lose my part7backup file. Am I out of luck or is there any way to return it to stock?
my carrier is Tele2 but they sell all their phones unbranded and unlocked if that is of any help.
Thank you in advance
PS. Im sorry for my bad english.
Click to expand...
Click to collapse
Search for the HTC RUU's. That should get you back to stock.
Also, wrong forum. Should have posted in General/Q&A.
bogdan5844 said:
Search for the HTC RUU's. That should get you back to stock.
Also, wrong forum. Should have posted in General/Q&A.
Click to expand...
Click to collapse
Thanks =)
Unfortunantly that did not work. i managed to restore my system and hboot to default, but i rooted my phone using the gfree method. that piece of software also change cid and som other stuff efter making a backup. somehow i managed to forget where i put that file.
You are not screwed without it.
You'll just have to use gfree to restore it back to the way it was.
First you need your original CID, which you can find with
Code:
dd if=/dev/block/mmcblk0p17 bs=1 count=8 2>/dev/null; echo
then you use gfree to restore s-on and your cid
Code:
./gfree -s on -c ORIG_CID
-Nipqer
Thanks
Thank you! Your an angel
Lets cross fingers and hope that ive done everything right before sending it in for repairs =)
Nipqer said:
You are not screwed without it.
You'll just have to use gfree to restore it back to the way it was.
First you need your original CID, which you can find with
Code:
dd if=/dev/block/mmcblk0p17 bs=1 count=8 2>/dev/null; echo
then you use gfree to restore s-on and your cid
Code:
./gfree -s on -c ORIG_CID
-Nipqer
Click to expand...
Click to collapse
Strange :S
All problems went away after doing a stock restore.
It had strange rebooting problems and sometimes it would not even enter hboot. The only way to get it runing was by pushing vol up + power and enter the msm debugmode, ripp the battery and then let it start normally.
Yes i tried ripping the battery before starting it again but the only thing that workes whas as i said.
Send it in?
Sent from my HTC Vision using XDA App
If its working fine I see no reason to send it in, maybe check which emmc chip you have first to help you decide (there is a bad batch of chips that are somewhat more prone to breaking)
Otherwise maybe try running a custom rom again and seeing if it decides to work now
-Nipqer
It works just fine. The question is why. I dont see why a custom rom would kill the phone just by moving it. Sometimes it worked fine, one day later it would die by picking it up from the table, retracting the keyboard etc. Ive checked the battery terminals and even tried another battery.
Its on its third day with stock rom. No problems so far :S
Sent from my HTC Vision using XDA App
Hi there,
My phone's (HTC vision from Orange) wifi & bt doesn't work anymore (says error and unable to load wifi driver) since 5 days at least.
After trying some roms (cyanogenmod 6 & 7, HTC stock rom, Orange stock rom)
and trying to find someone with the same problem without success, i have finaly given up and am going to send it back for warranty
but....
I lost my partition7 backup
thank to Nipqer, I have retrieved my original CID
but the ship seems to be stuck in S-OFF mode
I have done the gfree -s on command without success
even if the program seem to work properly, well at least I haven't read errors
here are the followings logs :
Code:
# ./gfree -s on
./gfree -s on
--secu_flag on set
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.21-g132894e
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02adc44, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02ad000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc02adc44 + 0x34c
- ***WARNING***: Found fuzzy match for brq filter, but conditional branch isn't
. (0xea000012)
Backing up current partition 7 and patching it...
Backing up partition /dev/block/mmcblk0p7 to /sdcard/part7backup-1326505037.bin
...
patching secu_flag: 1
Done.
# reboot bootloader
reboot bootloader
c:\android-sdk-windows\platform-tools>
Can someone explain the warning to me ?
Bootloader's phone display actually :
Code:
VISION PVT SHIP S-OFF
HBOOT-0.85.0010
RADIO-26.04.02.17_M2
eMMC-boot
Dec 27 2010,22:19:17
I used CyanogenMod's tutorial for rooting my vision
Everything was fine during the process (didn't fix my wifi & bt problems)
Can someone share me a part7backup ... or explain me what's going wrong (so I can find a way to fix the S-ON) please ?
thank you.
Aalaesar.
First off, don't ever share your part7backup. It is unique to your phone and contains your IMEI and other personal data.
Aalaesar, I think your problem is your radio version. From memory gfree requires a 26.03.xx.xx radio or lower. You should be able to easily downgrade with a radio from the official radio thread.
Also, if you didn't manage to change back to S-ON, you most probably don't have your original CID instead of SuperCID, so make sure you change that back.
-Nipqer
Thank you for the advice Nipqer.
Dowgrading the radio did the trick
I'm back in S-on.
Thank again.
Nipqer said:
If its working fine I see no reason to send it in, maybe check which emmc chip you have first to help you decide (there is a bad batch of chips that are somewhat more prone to breaking)
Otherwise maybe try running a custom rom again and seeing if it decides to work now
-Nipqer
Click to expand...
Click to collapse
I have M4G2DE, correct me if I´m wrong, but that means trouble, right?
I´ve read that I could dd the hboot before sending it in to make sure they wont find out that I have flashed custom roms, rooted etc. Is it a safe way to make sure they replace my mb under warranty?
It began again. this time with stock ROM :/
I´m sorry for my stupidity, This is my first Android phone so there is still much to learn
Thank you in advance
The M4G2DE does not mean trouble, just that there is a somewhat increased chance your phone will die.
If your phone is back to SHIP S-ON status, they shouldn't be able to know you rooted it.
I don't know if there's a way to be sure that they'll swap the mb, short of maybe bricking it nice and proper.
If you have an eng hboot I can give you a command to brick the phone (so long as your emmc is still working)
-Nipqer
There is a modem for the optimus G here:
http://downloads.codefi.re/houstonn/lgog/modem/E975_E977_E976
but it is from firmware 10b. You may want to try if it works better than your firmware. In this case, it is better if you make a backup of your current modem firmware, so you can go back to your version. Here I will write instructions to backup your modem, so you can restore it if you need.
Probably some of you know this already and feel like these are old news, but maybe we can build a modem firmware library.
You need root and a way to make an adb connection to your phone. If you cannot use adb, you can always use a terminal emulator on your phone, but this makes it a bit harder to type the commands. Also, this is for people who understand what they are doing. If after reading the tutorial you don't understand what the commands do, please don't try it. Or at least don't make me responsible if your phone bricks. Here we go.
NON NEEDED STEPS: This steps are here to show why this works.
1-Connect to your phone by adb.
2- On the terminal type :
Code:
mount
You'll see the following (amongst other things):
Code:
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=u:object_r:radio_efs_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
This means that the partition containing the firmware is /dev/block/platform/msm_sdcc.1/by-name/modem and it is mounted at /firmware.
NEEDED STEPS
1- Connect by adb
2- On the terminal type
Code:
su
Check if confirmation is needed on the phone screen. If needed, accept.
3-
On the terminal type:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modem.img
4-You will receive the following after some seconds:
Code:
131072+0 records in
131072+0 records out
67108864 bytes transferred in 29.959 secs (2240023 bytes/sec)
5-Type
Code:
exit
exit
adb pull /sdcard/modem.img
6-Now you have your backup.
HOW TO PACK THIS BACKUP FOR FLASH:
1-Download the file: cwm-lgog_e975-europe-10b_modem.zip from http://downloads.codefi.re/houstonn/lgog/modem/E975_E977_E976
2-Open the zip file and replace the existing modem.img with your file
3-Rename the file to something meaningful, like cwm-lgog_e975-europe-10f_modem.zip
After these steps, you should be able to flash any modem, knowing that you can go back to your old version.
You can upload the packed files here, so we can have a library. I will upload the modem from european 10f version here. I tested it and it works correctly, but I won't take any responsibility for what you do with this file.
Good luck.
All this info is obtained from examining the houstonn LGOG modem flasher from team codefire, so all thanks go to them. Thanks.
Very nice tutorial man. It will help newbies like me to back up and restore our modem.img, especially those who have F180* phones that wants or being converted to E975. Nice job. :good:
Nice,i'll add this to the Freaking Annoying Questions.
Sent from Asylum via LG E975/smart phones,dumb people.
Nice job.. Its work in e977 with 10a firmware?
Thx.
Sent from my LG-E975 using xda app-developers app
You should be able to backup your e977 modem following this tutorial.
renatonolo said:
Nice job.. Its work in e977 with 10a firmware?
Thx.
Sent from my LG-E975 using xda app-developers app
Click to expand...
Click to collapse
could you please do the same thing for the misc partition and upload it somewhere?
I saw that freegee is touching this one so please mention if your phone was opened with freegee.
sonty said:
could you please do the same thing for the misc partition and upload it somewhere?
I saw that freegee is touching this one so please mention if your phone was opened with freegee.
Click to expand...
Click to collapse
I am sorry, I am not going to upload my misc partition, as this partition contains my IMEI.
I can, however, tell you how to backup it:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/misc.img
Can I ask why you need that?
dapaua said:
I am sorry, I am not going to upload my misc partition, as this partition contains my IMEI.
Can I ask why you need that?
Click to expand...
Click to collapse
I had no idea the IMEI is also there. I asked for it because the baseband version is also stored there and it's kind of odd to know I'm flashing the modem from EU-10f and the displayed version is TW-10a. I'm still hoping to solve that issue.
Ah, OK. Tomorrow I'll check if the misc partition can be mounted, this would make editing it much easier.
dapaua said:
Ah, OK. Tomorrow I'll check if the misc partition can be mounted, this would make editing it much easier.
Click to expand...
Click to collapse
I think it is not possible to mount the misc partition.
“In any case, the misc partition isn't a "filesystem" partition as you are familiar with. It is actually just a simple data structure. In fact, only the system, cache, and userdata partitions are actually filesystem partitions, and the cache partition is only a filesystem partition part of the time -- during radio and spl updates, it also is used as a simple data structure with a header field and a payload field...”
http://forum.xda-developers.com/showpost.php?p=7254425&postcount=3
I was trying to find some additional info about this structure but without success so far.
On may F180K the misc partition has 16 777 216 Bytes. Some interesting offset:
0x8000 – 0x800E IMEI (15Bytes)
0x8800 – 0x8824 Baseband version (37Bytes)
0x9000 – 0x9024 Baseband version (37Bytes)
CyanogenMod display the last one data on the Settings->About phone->Baseband version
jumper8 said:
I think it is not possible to mount the misc partition.
“In any case, the misc partition isn't a "filesystem" partition as you are familiar with. It is actually just a simple data structure. In fact, only the system, cache, and userdata partitions are actually filesystem partitions, and the cache partition is only a filesystem partition part of the time -- during radio and spl updates, it also is used as a simple data structure with a header field and a payload field...”
http://forum.xda-developers.com/showpost.php?p=7254425&postcount=3
I was trying to find some additional info about this structure but without success so far.
On may F180K the misc partition has 16 777 216 Bytes. Some interesting offset:
0x8000 – 0x800E IMEI (15Bytes)
0x8800 – 0x8824 Baseband version (37Bytes)
0x9000 – 0x9024 Baseband version (37Bytes)
CyanogenMod display the last one data on the Settings->About phone->Baseband version
Click to expand...
Click to collapse
Thanks.
You are totally right, this partition is not a filesystem. And it is mostly empty, it's all zeros except for some bytes. Most of it are text strings, but there are some small binary parts.
I think the 0x8800 - 0x8824 part is the original firmware version.
I wouldn't touch that partition, seems too dangerous .
dapaua said:
I wouldn't touch that partition, seems too dangerous .
Click to expand...
Click to collapse
freegee touches it. I see it made a backup and the difference is that it changed some bytes to 0 (offsets 0x40-0x52), then wrote ANDROID-BOOT at offset 0x4000. the rest is the same. it seems there's nothing like a crc so basically I could write whatever I want in that version field. the bad part is that as an user you'll never know what modem version you have since its version is not stored on the modem partition. I wonder who came up with this system and what was he thinking.
thanks for the clarification. offtopic over .
sonty said:
I had no idea the IMEI is also there. I asked for it because the baseband version is also stored there and it's kind of odd to know I'm flashing the modem from EU-10f and the displayed version is TW-10a. I'm still hoping to solve that issue.
Click to expand...
Click to collapse
Some time ago I had the same issue. I solved it by modifying binary data on the misc partition. I was done this only on CM10.1 (F180K). I don’t know if it will work on other custom rom especially stock one.
Today I’ve done this one more time for preparation the following procedure. Maybe some one will use it on the future.
STEPS:
0. Backup the misc partition with your recovery. I was used CWM Advance Edition PhilZ Touch 5:
Backup and Restore-> Custom Backup and Restore->Custom Backup Job->Backup misc (*)
I’m not sure if all CWMs version support misc partition backup. TWRP not support it right now.
1. Dump the misc partition to /sdcard.
Code:
adb wait-for-device
adb root
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/misc_orig.img"
OUTPUT:
32768+0 records in
32768+0 records out
16777216 bytes transferred in 6.539 secs (2565715 bytes/sec)
2. Pull the image to your PC
Code:
adb pull /sdcard/misc_orig.img misc_orig.img
3. Edit downloaded image file by your favorite hex editor (e.g. Notepad++ with Hex-Editor plugin)
Find both baseband name strings (mine were on offset 0x8800 and 0x9000) and change them (CM10.1 use the last one to set gsm.version.baseband in file /system/bin/fetch-swv).
REMEMBER:
- Do not use regular text editor (like Notepad or vi) – they can add some extra characters to the file.
- If possible try to modify only bytes responsible for original baseband name. If the new name is shorter, simply put spaces char (0x20) to clear unwanted chars. If you need to put the longer name, be careful. I don’t know the max size for this string. There are dozens of zeros behind the baseband name on my image file. So, for testing I added extra 20 Bytes text. The new baseband name was shown without problem.
4. Push the modified image file to your phone
Code:
adb push misc_orig.img /sdcard/misc_mod.img
Check if size of the original and modified files are equal.
5. Write the modified image to the misc partition
Code:
adb shell "dd if=/sdcard/misc_mod.img of=/dev/block/platform/msm_sdcc.1/by-name/misc "
OUTPUT:
32768+0 records in
32768+0 records out
16777216 bytes transferred in 4.183 secs (4010809 bytes/sec)
6. Reboot your phone
DONE.
Hi all,
I just create a .zip to backup your modem / baseband / radio with your recovery (CWM / TWRP...)
ok as a newbie i cant figure out how to back up modem using adb... but after reading stuff what i did :
downloaded "Android Terminal Emulator" from playstore
open emulator in phone wrote as u mentioned :
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modem.img
after some seconds this came out :
131072+0 records in
131072+0 records out
67108864 bytes transferred in 15.229 secs
then :
exit
exit
after that i checked sdcard but there was no img file...
then i open file manager from the phone and there it was my precious :laugh:
size = 64mb... is it normal?
anyway .. made a new folder "modem" copied the img file into modem folder (using file manger) again connected the phone to pc copied the modem folder on my desktop...
hope it will help new guys here like me :good:
after installing the European kitkat I lost my LGOG E977 modem, anyone have some backup there to help me?
how to fix this?
:crying::crying::crying::crying::crying::crying::crying::crying::crying:
pedro5148 said:
after installing the European kitkat I lost my LGOG E977 modem, anyone have some backup there to help me?
how to fix this?
:crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
root using towelroot. unlock and install custom recovery using freegee and flash the modem in this post via recovery: http://forum.xda-developers.com/showpost.php?p=54016773&postcount=4
akahroba said:
root using towelroot. unlock and install custom recovery using freegee and flash the modem in this post via recovery: http://forum.xda-developers.com/showpost.php?p=54016773&postcount=4
Click to expand...
Click to collapse
I already did that, did not work out ...
any more solution?
pedro5148 said:
I already did that, did not work out ...
any more solution?
Click to expand...
Click to collapse
Get back to JB and wait for your midel update
Back to JB I recovered the IMEI, but I have no carrier signal.
So do the root with towelroot, unlock custom recovery with FreeGee, do I back up EFS, and when I restart the machine it loses the IMEI.
So I install the modem and E97710b.kdz for E97710b model recover EFS and nothing happens, still no sign of the operator ...
---------- Post added at 02:22 PM ---------- Previous post was at 02:22 PM ----------
akahroba said:
Get back to JB and wait for your midel update
Click to expand...
Click to collapse
even going back to JB, I continued without the modem
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
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
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!