Related
Hi all,
I installed CM11 onto my S5830i (GB) and managed to get it all working. I had to install S5360_XXMK1 modem and a newer version of CWM to prevent the "Status 7" error. Anyway, it all worked and I had CM11 up and running. Unfortunately, I had to remove it, I couldn't click any links in the browser and the browser was slow as all buggery even on a fast wifi connection. So I fired up Odin and tried to put the stock firmware on (i don't have an original state backup, the phone came with a custom rom on it already). I got these files
CSC_S5830i_BTUMD1.tar.md5
MODEM_S5830i_XXMD1.tar.md5
PDA_S5830i_XXMD1.tar.md5
But something's messing up, after Odin does its thing and the phone restarts, I notice something on the screen during restart saying it failed to format the /data partition. When I let the phone boot up normally it just stays on the "Samsung" startup animation forever. If I go into samsung recovery and try to do a factory reset, this is what I see
Code:
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/stl11
Formatting /cache...
Data wipe complete.
Obviously, something's wrong there, can anyone tell me how to fix it pleeeeese, I'd be eternally grateful.
Thanks
NS
EDIT: I think the CM install may have messed around with my partitioning. I do not have a pit file for the phone (GB Version) and am reluctant to be using the re-partition option in Odin. I can find pit files online, but they're either not the correct version or the poster doesn't even say what version it is. I am just so lost and confused with all this.
@NicSure, Flashing wrong base band into your Ace-i is ill advised mate, go to CM11 discussion topic and read my comments . ( You will damage your EFS partition,thus device may become hard bricked in many cases)
As for troubleshooting : Already explained all of the instructions in details in many places, So I will provide links/hints for now. If your problem persisted, let us know
Here we go mate:
1. Official source for your stock firmware CSC/MODEM/PDA >> this page (sammobile.com)
2. Study this topic to get the hang of Wipe flash-able packages,,, How to produce them, Boot looder and pit files required for the process , etc etc,, all well instructed here
3. Read few last pages of this topic; my comments; for more insight into your problem. Please be advised you have already converted your partitions into MTD ,therefore formatting /data ( concerting back into RFS partitions ) might be failure through CWM/e3 recovery >> Odin process is required for"stl11" .
Hope I did help you
ehsanotaku said:
@NicSure, Flashing wrong base band into your Ace-i is ill advised mate, go to CM11 discussion topic and read my comments . ( You will damage your EFS partition,thus device may become hard bricked in many cases)
As for troubleshooting : Already explained all of the instructions in details in many places, So I will provide links/hints for now. If your problem persisted, let us know
Here we go mate:
1. Official source for your stock firmware CSC/MODEM/PDA >> this page (sammobile.com)
2. Study this topic to get the hang of Wipe flash-able packages,,, How to produce them, Boot looder and pit files required for the process , etc etc,, all well instructed here
3. Read few last pages of this topic; my comments; for more insight into your problem. Please be advised you have already converted your partitions into MTD ,therefore formatting /data ( concerting back into RFS partitions ) might be failure through CWM/e3 recovery >> Odin process is required for"stl11" .
Hope I did help you
Click to expand...
Click to collapse
Thanks but you were too technical. I have been to a lot of those pages you linked and it's not all obvious what's going on. You spoke about "base band", I have no idea what that is. I have no idea what RFS, MTD
are (file systems?), not do I know where to get a bootloader from. Sam mobile won't let me download anything without paying and/or signing up which I'm reluctant to do. I'll re-read the posts you linked to (I had already seen them) and see if something starts to make more sense.
For instance:
"Please be advised you have already converted your partitions into MTD ,therefore formatting /data ( concerting back into RFS partitions ) might be failure through CWM/e3 recovery >> Odin process is required for"stl11"
May as well have been in Klingon, I didn't understand a word of it.
EDIT:
I've reviewed those threads again. Seems I need to use split fus on the downloaded file from SamMobile (which I had to register to download, not happy about that) and use the "wipe" versions. I need a pit file, there's no info anywhere on how to get that. So I've just done a general google and hopefully I've downloaded one (more info on that is needed in the tuts). And the bootloader is attached to the unbrick thread, but, is that the ONLY bootloader? Do I need a specific one for my region? Do I need a specific pit file for my region? All this info is not supplied anywhere, Newcomers are not going to know this stuff and it needs to be made clear in the tutorials. Most of the tuts have broken links (split fus for instance), so I'm not sure if the stuff I googled is actually the same. Absolute nightmare.
NicSure said:
You spoke about "base band", I have no idea what that is.
Click to expand...
Click to collapse
Please read the link was provided for your convenient. ( Absolutely suitable for beginners).
NicSure said:
I have no idea what RFS, MTD
are (file systems?)
Click to expand...
Click to collapse
"Robust File System" is more or less equivalent to your FAT/FAT32 of your PC ( Samsung file system Format,, not going to add "Journalling system" to the mix, since you are not a sport ,,FYI : You are supposed to know common terms such as MTD , RFS when you are massing with CM11 mate >> Read the first page thoroughly, before start experimenting with Cyanogen stuff,,,
MTD (Memory Technology Device) supports YAFFS2 as a file system residing on it and is considered some type of of Partition Map.
NicSure said:
not do I know where to get a boot loader from. Sam mobile won't let me download anything without paying and/or signing up which I'm reluctant to do
Click to expand...
Click to collapse
Again actually start reading this topic ( quite self explanatory).
NicSure said:
Seems I need to use split fus on the downloaded file from SamMobile (which I had to register to download, not happy about that) and use the "wipe" versions.
Click to expand...
Click to collapse
This topic contains well made Wipe packages ( European version is compatible with your device, If you are reluctant to register though).
NicSure said:
I need a pit file, there's no info anywhere.
Click to expand...
Click to collapse
Again, Read the topic I mentioned above. You are on Cooperve device, so be aware of wrong file ( "cooperve_0623.pit" resided inside Odin3.v3.07.Cooperve folder) All of the related links already provided , Just take your time and read mate.
I'd already read the posts you linked to multiple times thank you. They may be "straight forward" to you, but I can assure you they are certainly not so for a newcomer. Too many things are vague, missing or not explained properly.
In any case, I managed to get the stock firmware back on after trawling the internet for a .pit file, downloading the firmware, splitting it, taking the wipe versions with the pit and the bootloader and using Odin to fully flash the phone back to stock firmware, Finally. The tuts here are indeed a lot of help, but so so so disjointed.
Also, why would changing the base band effect the file system? How could it cause physical damage to NAND memory. I'm confused. I assume you mean physical damage, because if not, why would it be ill-advised to change it if it could just be changed back with no ill-effects?
@NicSure, First of all Thanks button implanted here for a good reason and most likely you are the first person who was complaining about my assistance (How information is organized and distributed for new commers is not my responsibility nor distribution of step-by-step instructions ) . Second of all You were complaining about the technical terms and jargon, But know you are asking for technical reason in regard of the consequences of flashing Galaxy Y GT-S5360 inside your ACE-i device !
I did mention about EFS partition corruption, which renders your device mobile network communication useless and hard bricking of your device.which is a phone that shows no signs of power-on and will not access download mode with button combo. You did assume wrong mate.
Generally speaking, Carriers use different radio frequencies in our respective countries , Different Devices do contain different modem hardware inside, So you are not encouraged to do what you have done in the first place.
If you are not flashing the correct versions for your phone , or if the flash gets interrupted there’s a good chance you will Hard Brick your device, thus we may need hardwired access to modify/erase and rewrite chip's code ( Service is required).
When a phone is in a hard-bricked state it’s most likely that the bootloaders, which is the phones initial code to launch the phones ROM, becomes corrupted.
The only way to revive the phone is to rewrite the bootloader code, because the phone does not power on ., So you see so many things could go wrong :silly:
ehsanotaku said:
@NicSure, First of all Thanks button implanted here for a good reason and most likely you are the first person who was complaining about my assistance (How information is organized and distributed for new commers is not my responsibility nor distribution of step-by-step instructions ) . Second of all You were complaining about the technical terms and jargon, But know you are asking for technical reason in regard of the consequences of flashing Galaxy Y GT-S5360 inside your ACE-i device !
I did mention about EFS partition corruption, which renders your device mobile network communication useless and hard bricking of your device.which is a phone that shows no signs of power-on and will not access download mode with button combo. You did assume wrong mate.
Generally speaking, Carriers use different radio frequencies in our respective countries , Different Devices do contain different modem hardware inside, So you are not encouraged to do what you have done in the first place.
If you are not flashing the correct versions for your phone , or if the flash gets interrupted there’s a good chance you will Hard Brick your device, thus we may need hardwired access to modify/erase and rewrite chip's code ( Service is required).
When a phone is in a hard-bricked state it’s most likely that the bootloaders, which is the phones initial code to launch the phones ROM, becomes corrupted.
The only way to revive the phone is to rewrite the bootloader code, because the phone does not power on ., So you see so many things could go wrong :silly:
Click to expand...
Click to collapse
Firstly, I'm not complaining, I'm criticizing, there's a difference. I was critical of your language and terminology as it didn't match the links you posted. Also the level of technical talk you used toward a clear newbie who would obviously never understand it without clarification. If that offends you then I'm sorry, I'm just speaking my mind. Help offered, no matter how kindly or freely is useless if it cannot be understood. I generally take a very irritated approach to people who post links (with the implication that the information is freely available if you'd bother to look) in response to perfectly polite questions, especially when I'd already read ALL the posts you linked to before and had trouble with them, that is why I posted, to get a little more basic understanding, not be presented with links to material I'd already read and needed help with. Also, after some researching, with regard to the base-band, I think you're wrong, there's no way flashing a different base-band separately could effect the bootloader, no way at all. I seriously doubt it could even cause corruption, that's liek saying installing the incorrect driver for a graphics card on a PC could corrupt the file system, just no. So far I've flashed many many different MODEM types onto my phone to try to test this, in some caes the phone boots, in some cases it doesn't etc.. Not once has the phone failed to go into Odin flash mode, and if it can get to that, it can be restored. So based on research and some experimental evidence conducted to test your assertion, I'd have to say that my initial findings are that your assertion is probably incorrect.
Also I learn very quickly. My knowledge of the subject had increased dramatically from my first post to my second. I learned c++ in a day for example, and was posting similar newbie questions on programming forums to which I was later replying with a level of knowledge that wasn't consistent with my initial post. It's just me, sorry about that. And thanks for trying to help, but I got it myself.
NicSure said:
... I can assure you they are certainly not so for a newcomer. Too many things are vague, missing or not explained properly. In any case, I managed to get the stock firmware back on after trawling the internet for a .pit file, downloading the firmware, splitting it, taking the wipe versions with the pit and the bootloader and using Odin to fully flash the phone back to stock firmware, Finally. The tuts here are indeed a lot of help, but so so so disjointed.
Click to expand...
Click to collapse
Dear NicSure, I am in the same situation as yours, I was planning to "simply" (or maybe wrongly?) use Odin 3.09 and flash the Splitted files from here (http://forum.xda-developers.com/galaxy-ace/s5830i-develop/stock-rom-odin-flashable-firmware-t3002776).
But you mentioned that also the ".pit" file is needed. Could you guide me through the process you followed to have back a Stock from CM11 ROM?
Thank you in advance!
thePanz said:
I was planning to "simply" (or maybe wrongly?) use Odin 3.09 and flash the Splitted files from here (http://forum.xda-developers.com/galaxy-ace/s5830i-develop/stock-rom-odin-flashable-firmware-t3002776).
But you mentioned that also the ".pit" file is needed. Could you guide me through the process you followed to have back a Stock from CM11 ROM?
Thank you in advance!
Click to expand...
Click to collapse
Per your request/confirmation @ development section/twr topic i would resume troubleshooting .
What is your device variation (5830i/C/M/V/5839i ) ? Do you have any Nandroid back up left inside your SD card from your original stock firmware partitions ? Can you see your IMEI number , when you are dialing "*#06#" ? Your original stock CSC/PDA/MODEM you are coming from ? Your Region / Country / carrier you are staying with at the moment and please give me the Totoro Modem part you did flash to get into the CM11 ? and for addressing part of your primary queries , Odin 3.07 works very well with variation I mentioned above ( you could use 3.09 with no harm though , but not recommended ) . Pit file also must be relevant, otherwise you will hard brick your device in many cases I observed .
EDIT: no longer need this. It is possible to make your own...
There is a chance that I may not have fried my V10 by shorting the test point, but to test that I need a full Nougat dump (something I can not believe I didn't make from my own phone -- I only have a full MM dump).
If there is someone that has rooted Nougat AND flashed all the Nougat partitions (v30b_update.zip and full_nougat.zip), and is willing to do a full dump, please let me know.
It is preferable if you have access to Linux because you will need to null out some partitions that have private data, and it is much easier to explain how to do it on Linux.
Lastly, this image will be 64gigs uncompressed, but it compresses very well.
Thanks,
-- Brian
Wish I can help, but mine is not rooted..
Hopefully I can bring my phone back to life (one way or another) so I can continue on. I got my board of eBay, but it was more dead than my current board.
runningnak3d said:
Hopefully I can bring my phone back to life (one way or another) so I can continue on. I got my board of eBay, but it was more dead than my current board.
Click to expand...
Click to collapse
That sounds bad. Hopefully someone will upload it.
if i can downgrade it , ill re upgrade to rooted nougat and get a dump but i dont know how to dump and dont have the image for downgrade.
@runningnak3d There's a guy selling one in General. Perhaps you can get a dump off of him?
@runningnak3d I currently have one V10 that I cannot get past the Checking Updates screen in the setup wizard on Nougat (with TWRP) which I am considering performing a KDZ wipe and another that went black screen after I flashed MM (also with TWRP). If I do a KDZ wipe on the first one, I could do a dump for you but I would have to look up how to. You are also welcome to buy the board from the second V10 from me but I'm unsure if you can revive it.
Thanks all, but everything I needed to make my own was staring me in the face.
-- Brian
i will help if i can , but didnt have root yet
@runningnak3d I'm in a need of a Nougat dump for H901, to make a bootable sdcard. Could you share yours or guide how to make one from nougat kdz?
Due to messing the aboot partition (while trying to shut the "big cores" off) the phone does not boot, nor enter download mode. On powering on, it only vibrates. QPST does not work with the phone put into 9008, it returns "target may be unstable". Before that, the phone was rooted, with bootloader unlocked, updated to nougat via the recovery, with the ZIPs.
Any help would be greatly appreciated
Be glad to, and it is easy, but you need dd. If you use Windows, there may be some program that can do something similar, but I haven't used Windows in years. You can always install a very basic Cygwin environment...
* Insert 64gig SD card
* Dump KDZ
* dd if=PrimaryGPTxxxxxx of=/dev/mmcblk0
The xxxxx above is because I can't remember what it gets dumped as, but it will be obvious.
Once you have the partition table on the sdcard, get a list of the partitons:
* gdisk -l /dev/mmblck0
Then proceed to flash the rest of KDZ onto their individual partitions.
For example, I believe that modem was partition 1, so:
* dd if=modemxxxxx of=/dev/mmcblk0p1
Repeat for every partition from the KDZ except system (unless you want to fully boot from the SD card). Also, you can flash recovery with TWRP, and then you can boot from the SD card to recovery and then you only need to flash your aboot partition, so you don't have to use download mode to flash the entire KDZ.
Let me know if you need me to clarify anything.
EDIT: If you do boot to recovery from the SD card, you will need to make sure to flash the correct device. When you go into an adb shell, you will have two mmcblk devices (mmcblk0 and mmcblk1). I don't remember which will be which, so to be safe flash the aboot partition on both...
-- Brian
@runningnak3d Thank you for your reply! I have Ubuntu 17 as a bootable DVD. Does the sdcard have to be formatted in a specific filesystem before doing this? Another question I have, is that the sdcard shows up as dev/sdd for me but it also shows that dev/sdd1 exists on it, so to which should I dd the GPT table to?
I tried to dev/sdd and wrote the rest of KDZ to the partitions, but the phone has not booted (its 64gb sd hc class 10 card). After dd-ing the PrimaryGPT, the terminal mentions that backupGPT is corrupted and that MBR is protective on the sdcard. Also, GParted shows "unknown" for each partition, and modem partition shows up as fat16 one.
Perhaps I should try different nougat KDZ? the phone's sticker under battery says it's H901, so was written in the phone under settings menu (phone also had t-mobile bloatware) and in LGUP when updating to MM, yet the motherboard has VS990 written on it.
My phone said vs990 on the board as well, so that isn't the issue. You need to flash a few partitions from the phone that aren't in the KDZ ... you will have to get someone to dump them for you.
The only place I had them was on an SD card that I have already wiped since I don't have a v10 anymore.
I will have to look in SBL1 to get you a list that you will have to ask for.
They are all just firmware, and contain nothing specific to a users phone, so anyone with a rooted Nougat phone can safely dump them for you.
Please bear with me. I am currently trying to revive my H910 and I order an H918 that I am going to use to help someone with, but I will try to get you the info ASAP.
H901 VS990 board 9008 brick help
@runningnak3d Hey, you seem like an expert at unbricking V10s. I have a H901 that has vs990 motherboard in it. It bricked while I was updating through LG Bridge. I now only have access to qualcomm 9008 mode.
From my understanding, there are 2 ways to solve this. QFIL or booting from dump image through sdcard. The qfil way didn't work for me, since there aren't any compatible .mbn files and xml for VS990 owners. So my only other option is getting to download mode via sdcard method, and I need the dump files for that. If I do what you've told @Mr_pringle, would my phone enter download mode? What exactly would I have to do? Thanks
@N3XTN3XUS What version were you on, and what version did LG Bridge try to update you to?
runningnak3d said:
@N3XTN3XUS What version were you on, and what version did LG Bridge try to update you to?
Click to expand...
Click to collapse
mm to nougat. Do you have the dump img for mm by any chance?
Unfortunately you are going to have to roll your own with the instructions I gave above.
In order to do that, you need to find out what model you should be flashing. I know you said your board said VS990, I am sitting here looking at my dead board, and it says VS990 on it as well, so H901 Nougat *should* have worked for you. I don't have any idea where you should start looking, but you do need to know that before making an SD card or even if you make a perfectly good card, it won't work
-- Brian
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
duraaraa said:
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei.
It's just a preliminary build so I can't promise anything/everything will work! Keep that in mind. I'm not responsible if you brick your device.
EDIT: Does not work with Mate 10 series.
DOWNLOAD LINK:
https://drive.google.com/open?id=0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei/comments/75uwkd/october_12_first_official_android_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you've got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don't mess around too much with TWRP, to be sure you don't brick your system!
Click to expand...
Click to collapse
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
AndDiSa said:
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
Click to expand...
Click to collapse
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
I've tried flashing the entire update.zip file in TWRP...but as noted TWRP is unable to mount internal storage. I'm not sure if I need to wipe and reformat first. I also have no clue whether the TWRP build I installed is properly compatible with the device. I had nothing to lose by giving it a shot.
thref23 said:
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
Click to expand...
Click to collapse
This will not work as the boot chain will be broken due to mismatching checksums. You need to have the correct images. To flash a OTA image you also need to have the standard recovery image installed ...
So...will someone correct please correct me if this is wrong?
If I were to flash a c00 oeminfo file, I could then install a c00 update.zip via dload folder?
Would c432 work as well (with a flashed oeminfo), even though the Euro hardware has different bands than my hardware?
There is now a full OTA on FF for C635.....still nothing for c636...
Finally, a full OTA is available for c636.
But the 'dload' method (update.app on an sd card) failed at 5%. And flashing ramdisk/recovery/erecovery/system images also failed.
Is this possibly because the OTA is B153, whereas my M5 was shipped B121?
(I hate to be that guy bumping his own thread, sorry)
I'm unbricked!
For those in a similar spot, looking to rebrand, or otherwise interested...
I finally e-mailed Funky Huawei for assistance. Their unbrick tool did not work. However, their e-recovery method worked perfectly (basically, you point your router's DNS to Funky Huawei, enter stock recovery and connect to wi-fi, and Funky Huawei's servers mimic Huawei's servers. If they do not have your firmware on their server, they will add it by request (provided it exists on the internet).
I paid $65 for a 30 day pass - a little steep, but I was impatient. I'm not sure if I could have gotten away with paying less. If you want to try and use my FH account over the next 30 days PM me (although I don't want to get carried away with that).
For those looking to rebrand, if you can flash an OEMinfo file successfully (FH has a rebrand tool and I have no clue how well it works), you should be able to use FH's erecovery method to flash firmware (don't blame me if something goes wrong).
One reason for the trouble I was having, if because I bootlooped after making a change to the vendor/build.prop file. This file was on the vendor partition, not the system partition, and for whatever reason the vendor partition cannot be flashed via fastboot (in theory it can be flashed, in reality it returns an error that doesn't have to do with the size of the partition).
Before reverting to FH, I finally got TWRP installled and functioning, and after all the attempts I made to recover my device, the same build.prop file which initially caused a bootloop was still in the /vendor folder. And TWRP wouldn't mount the system and vendor partitions as read/writeable - that was frustrating.
Now off to experiment with AOSP GSIs while I feel like I have little to lose...
Please help me
hello everyone,
i tried to rebrand my m5pro with help of ministryofsolutions. Something went wrong and my tablet (CMR-AL19) is stucked in the recovery mode. how can i fix it? Someone who ca help me? I will pay
Greeztings
Luigi
thref23 said:
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
Click to expand...
Click to collapse
As the title implies , this thread will contain g8x att firmware backs ups for people to use, since we don't have kdz for our version of the g8x, these backups will hopefully help people recover phones.
If you have a backup please pm me or post it here and i will add it to the main OP. Also an easy way to dump your firmware is to use Partition Backup
If you do decide to dump your firmware, only backup slot partitions, mostly only those can be shared. Most others are device unique. (you need Bl unlock and root to dump them with this app, with firehose/qpst you dont.)
Only restore this on a Android 10 slot
Also this vendor parttion is decrypted keep this in mind while restoring it.
Firmware List:
ATT G8X 20e Android 10 (Security patch April 1st 2020)
"People cant have nice things =/. look for me on the blue old app"
If you have issues downloading let me know.
Do you have a AT&T LG G8 Android 10 dump?
Also, how would one go about using the Android 10 dump on their LG G8? (Basically how do you install it?)
wwechampian said:
Do you have a AT&T LG G8 Android 10 dump?
Also, how would one go about using the Android 10 dump on their LG G8? (Basically how do you install it?)
Click to expand...
Click to collapse
Not for att g8, i only have a g8 from sprint, im not sure how you would go about using this to upgrade from 9 to 10, i think it has to be flashed on secondary slot. i would go to the lg v50 telegram group and ask there, so you can be sure 100%
so i can only do this if i have root access on my lg g8x from at & t?
siulmagic said:
ATT G8X 20e Android 10 (Security patch April 1st 2020)
att-20e-firmware-backup-slot.7z
drive.google.com
If you have issues downloading let me know.
Click to expand...
Click to collapse
Forgive my ignorance but how does one go about using this backup to restore a bricked G8X...?
Need a step-by-step primer on this if anyone would be kind enough to teach, as I'm only familiar with KDZ's and using LGUP 1.14 Dev Mode for older LG devices...the G8X will not function with this version, so it's not straightforward
Thanks in advance
HanselCustodio said:
so i can only do this if i have root access on my lg g8x from at & t?
Click to expand...
Click to collapse
no, you can use it without root(use firehose/qpst), though my vendor is decrypted no idea how that will affect it.
siulmagic said:
ATT G8X 20e Android 10 (Security patch April 1st 2020)
att-20e-firmware-backup-slot.7z
drive.google.com
If you have issues downloading let me know.
Click to expand...
Click to collapse
Just want to offer a warning to anything thinking about using the above referenced backup - I used it myself on a soft bricked G8X (AT&T) using QFIL on EDL/9008 mode to upload the unpacked IMG's. I went from soft brick to hard brick.
When I first started off using this I uploaded only the system, boot and abl...when I started seeing a fastboot screen (which I hadn't seen since) I felt like I was moving in the right direction so I uploaded the remaining partitions. After exiting EDL the device refuses to turn on...no LG splash, no android warning, no longer any access to download mode. No amount of button pushing brings EDL mode back while connected via USB. Doesn't charge using wireless charger (which it used to before).
I'm very confident I did not mismatch any partitions, though uploading the OP image did mention that there was data overflow and asked me if I wanted to continue. Further, this backup did not contain all of the img's that would ordinarily be present in a KDZ, but contained imgs that a standard KDZ do not have.
Since I can't get to EDL I can't restore the backups I had made of it's previous soft-bricked state.
It's just really frustrating, and I've learned my lesson never to buy a device from a carrier that doesn't allow access to it's KDZ firmware file (or cannot be crossflashed to one that does).
Your mileage may vary of course but I definitely feel like I'd want to stop someone from trying the attached if they're still in a soft-bricked state.
As an aside I would appreciate anyone who might have any ideas of how to reach EDL mode again. Thanks
cliffswallow said:
Just want to offer a warning to anything thinking about using the above referenced backup - I used it myself on a soft bricked G8X (AT&T) using QFIL on EDL/9008 mode to upload the unpacked IMG's. I went from soft brick to hard brick.
When I first started off using this I uploaded only the system, boot and abl...when I started seeing a fastboot screen (which I hadn't seen since) I felt like I was moving in the right direction so I uploaded the remaining partitions. After exiting EDL the device refuses to turn on...no LG splash, no android warning, no longer any access to download mode. No amount of button pushing brings EDL mode back while connected via USB. Doesn't charge using wireless charger (which it used to before).
I'm very confident I did not mismatch any partitions, though uploading the OP image did mention that there was data overflow and asked me if I wanted to continue. Further, this backup did not contain all of the img's that would ordinarily be present in a KDZ, but contained imgs that a standard KDZ do not have.
Since I can't get to EDL I can't restore the backups I had made of it's previous soft-bricked state.
It's just really frustrating, and I've learned my lesson never to buy a device from a carrier that doesn't allow access to it's KDZ firmware file (or cannot be crossflashed to one that does).
Your mileage may vary of course but I definitely feel like I'd want to stop someone from trying the attached if they're still in a soft-bricked state.
As an aside I would appreciate anyone who might have any ideas of how to reach EDL mode again. Thanks
Click to expand...
Click to collapse
You will have to open the back and short some contacts.
Or give to service center if in warranty.
[QUOTE = "lefttobleed, publicación: 84319395, miembro: 2516025"]
Tendrás que abrir la parte trasera y cortar algunos contactos.
O entréguelo al centro de servicio si está en garantÃa.
[/CITAR]
Lo hiciste ??
Can anyone dump they're .xml partition data file? I am very desperate as my devices partitions are missing. Please help! Cheers!
cliffswallow said:
Just want to offer a warning to anything thinking about using the above referenced backup - I used it myself on a soft bricked G8X (AT&T) using QFIL on EDL/9008 mode to upload the unpacked IMG's. I went from soft brick to hard brick.
When I first started off using this I uploaded only the system, boot and abl...when I started seeing a fastboot screen (which I hadn't seen since) I felt like I was moving in the right direction so I uploaded the remaining partitions. After exiting EDL the device refuses to turn on...no LG splash, no android warning, no longer any access to download mode. No amount of button pushing brings EDL mode back while connected via USB. Doesn't charge using wireless charger (which it used to before).
I'm very confident I did not mismatch any partitions, though uploading the OP image did mention that there was data overflow and asked me if I wanted to continue. Further, this backup did not contain all of the img's that would ordinarily be present in a KDZ, but contained imgs that a standard KDZ do not have.
Since I can't get to EDL I can't restore the backups I had made of it's previous soft-bricked state.
It's just really frustrating, and I've learned my lesson never to buy a device from a carrier that doesn't allow access to it's KDZ firmware file (or cannot be crossflashed to one that does).
Your mileage may vary of course but I definitely feel like I'd want to stop someone from trying the attached if they're still in a soft-bricked state.
As an aside I would appreciate anyone who might have any ideas of how to reach EDL mode again. Thanks
Click to expand...
Click to collapse
This should only be used mostly to restore certain parttion, not the whole backup in one go, as you said this is not a kdz. Also messing with op partition is never recommended, edl did warn you of the parttion size mismatch. Also depends what you had on your primary slot, i would not recommend flashing this on a pie slot. Sucks that you hard bricked.
Need dump full G8X ATT, thank all, I need all partitions except the userdata partition, please help me, thanks
Hey guys, I'm really needing firmware to G850UM10F AT&T. Any one sees this variant come across their screen on a Telegram group or in their searches let me know please.
#Rooty_Mikes# said:
Hey guys, I'm really needing firmware to G850UM10F AT&T. Any one sees this variant come across their screen on a Telegram group or in their searches let me know please.
Click to expand...
Click to collapse
did you find one? I'm looking for a firmware in android 9 for at&t
siulmagic said:
As the title implies , this thread will contain g8x att firmware backs ups for people to use, since we don't have kdz for our version of the g8x, these backups will hopefully help people recover phones.
If you have a backup please pm me or post it here and i will add it to the main OP. Also an easy way to dump your firmware is to use Partition Backup
If you do decide to dump your firmware, only backup slot partitions, mostly only those can be shared. Most others are device unique. (you need Bl unlock and root to dump them with this app, with firehose/qpst you dont.)
Only restore this on a Android 10 slot
Also this vendor parttion is decrypted keep this in mind while restoring it.
Firmware List:
ATT G8X 20e Android 10 (Security patch April 1st 2020)
att-20e-firmware-backup-slot.7z
drive.google.com
If you have issues downloading let me know.
Click to expand...
Click to collapse
Can you unblock bootleader g8x att android 9?
Duythiem said:
Can you unblock bootleader g8x att android 9?
Click to expand...
Click to collapse
I believe to unlock bootloader for any variant you have to be on 10.
conbak49 said:
I believe to unlock bootloader for any variant you have to be on 10.
Click to expand...
Click to collapse
However, i don't have firmware android 10, because i live outside the USA....
Duythiem said:
However, i don't have firmware android 10, because i live outside the USA....
Click to expand...
Click to collapse
Only thing I know to suggest is ask in this thread: https://forum.xda-developers.com/t/...nlock-and-magisk-root-using-firehose.4221793/
i was able to unlock the bootloader on android 9
yoctan1 said:
did you find one? I'm looking for a firmware in android 9 for at&t
Click to expand...
Click to collapse
I might still have a copy on my drive if you still need it
I dont know where else to look for the result to fix my issue.
I cant get my previously Nord N200 (de2118) i say previously because at somepoint ive flashed a 2117 at some point. before SHTF i was running /e/os unlocked and rooted. I was planning on switching to LibremobileOS and the WIKI was down so I decided to try it myself. Well now i cant get it to boot. And me thinking since ive use MDM before to fix it once, I've just been tyrying to flash TWRP and recoveries on boot and recovery and im at a loss. I cant get this tutorial https://forum.xda-developers.com/t/...le-slot-requires-unlocked-bootloader.4401113/ or this one https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4324431/
i've read almost unbricking and downloaded everything provided and im stuck aganist the wall and need some guideance.
if someone can help me fix this, you will be saving my ass. i have 20 hours beofre i need my phone!
just restore the factory image using the "MSM download tool repacked" thats been posted in the n200 forums. for the de2118 use one below
[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...
forum.xda-developers.com
AiM2LeaRn said:
just restore the factory image using the "MSM download tool repacked" thats been posted in the n200 forums. for the de2118 use one below
[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...
forum.xda-developers.com
Click to expand...
Click to collapse
finally got it to boot, idk what differently i did but ive tried that tutorial a few nights ago. thanks