Related
Hi,
Could someone please dump a system image for the 10.1? It's reeeealy easy
There are a few soft-bricks already due to people flashing the wrong image or to the wrong partition ( you know who you are, people! ) and you would be doing them a massive favour if you did.
If you already have busybox, all you have to do is run this:
Code:
dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Then you can pick it up the system.img from /sdcard
Code:
adb pull /sdcard/system.img
ZIP it and upload it somewhere ( Dropbox ) and you're done!
TIA
BC
Http://droidbasement.com/galaxy/sys-backup
The system_extra backup contains extra stuff (from the 'tools' compilation).
Thanks. There are a couple of people who will really appreciate that
OT: I just repacked your su/busybox update with the boot.img from the Voda 10.1 and it works fine. Link to the Voda boot.img is here
Would it be possible to get the original system image without the extra tools? I am trying to flash this image however I keep getting a remote error when I do so. Could it have something to do with the fact that this image is 600MB compared to other system images that are around 200 MB like for the gt 10.1v? Thanks again for posting it.
the extra stuff is not making it 600mb (maybe 10-20). It is quite big on the IO.
In order to fastboot flash it you must have an unlocked bootloader to do so (which in unlocked by default on the IO).
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
nadewad said:
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
Click to expand...
Click to collapse
ill retake the dump and upload it. ill do it tonight. maybe some corruption ocurred, etc.
It might be the same trick where you have to create a sparse ext4 image instead of ripping the image straight, because fastboot transfers the entire image in RAM before flashing it...
Try
Code:
make_ext4fs -l 512m -s /sdcard/system.img /system
If anyone has created a system image but isn't quite sure if it is the correct one, I'll be glad to try it out as I am one of those people who soft bricked their device. Just PM me and I'll be more than happy to flash my device and verify the stability of the system image. Thanks.
Nader
bump? Did anyone end up getting a system image? Thanks.
Nader
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
nadewad said:
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Run it on the device instead of using dd on the device.
ydaraishy said:
Run it on the device instead of using dd on the device.
Click to expand...
Click to collapse
He has a soft-bricked device so that's not an option unfortunately.
You can do a MD5 checksum of the file and get pershoot to check it against the original.
Otherwise, in the mean time, you can try this tool:
http://www.diskinternals.com/download/
You want the tool called "Linux Reader 2.0". It says it can only read ext2 and ext3, but I just tried it on my 10.1v system image which I created using the same method as pershoot, and it works fine.
...and see if you can mount it in Windows. If you can, the image is (probably) OK.
bcmobile said:
He has a soft-bricked device so that's not an option unfortunately.
Click to expand...
Click to collapse
Well, obviously, someone _else_ has to provide that image from a working device.
Same error here, while trying to flash the system.img. Any alternatives?
Thanks,
Eduardo.
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
nadewad said:
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
Click to expand...
Click to collapse
Samsung may charge you for the repair
Before you send it back, just have one more go at flashing the boot.img which smaskell provided from here. Just do a:
Code:
fastboot flash boot boot.img
The boot loop may be due to a different (incompatible) kernel if you still have the boot partition from the 10.1v
Failing that, if you're still up for it, do a:
Code:
adb logcat > %userprofile%\desktop\logcat-out.txt
...then open the locgat-out.txt file on your desktop and post the contents here or just zip and attach the file. That might give us something to work with
I am also not able to flash this system.img file. I get the same error.
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
nadewad said:
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
Click to expand...
Click to collapse
My tablet is showing P7100 as well. I tested with my employee's GT LE, and it shows the same. So, this is not the problem...
adb is not accessible to me as well.
Can I just erase from settings to restore to default?
Sent from my XT1058 using XDA Premium 4 mobile app
our best bet is probably to follow this guide here...
http://forum.xda-developers.com/showthread.php?t=2446515
Or maybe easier would be just to...
fastboot flash system <nameofsystemfilehere>.img
I would have to double check my last bit of advice though.
Newbie help
is there anyway to do this without deleting my stuff. Sorry im a newbie at this. i orginialy installed the first root moto app and it had a unroot option. the new one doesnt and i really need to get back to stock without doing anything complicated
MarcusSi1516 said:
is there anyway to do this without deleting my stuff. Sorry im a newbie at this. i orginialy installed the first root moto app and it had a unroot option. the new one doesnt and i really need to get back to stock without doing anything complicated
Click to expand...
Click to collapse
Well...
fastbooting the system should not delete your user data. and its not really complicated.
Do you have ADB set up on your computer?
i think so
thepolishguy said:
Well...
fastbooting the system should not delete your user data. and its not really complicated.
Do you have ADB set up on your computer?
Click to expand...
Click to collapse
yah i do. but i origginaly downloaded root app as apk
MarcusSi1516 said:
yah i do. but i origginaly downloaded root app as apk
Click to expand...
Click to collapse
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
####EDIT####
If fastboot will not flash the system.img use a different fastboot.exe created to flash the larger .img
arigi said:
The solution is to use the mfastboot.exe linked from here:
http://forum.xda-developers.com/showthread.php?t=2489249
Hope that helps someone trying to do this same thing.
Click to expand...
Click to collapse
And if you leave it named "mfastboot" then you must issue the commands with the "m"...
"mfastboot flash system system.img"
without the parenthesis of course
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Aarongauntt said:
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes it should. Just got to make sure you grab the correct images for your carrier.
Aarongauntt said:
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
should.
But I have a VZW MotoX and I dont want to jack anyone up.
As long as you are using the proper system and recovery. If you flash the ATT system to a VZW device you are going to have problems.
Aarongauntt said:
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Worked perfect on my ATT Moto x
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
This man deserves some props. Thanks for posting that.
Sent from my HTC One mini
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
Thanks for this! It cleared up a whole bunch of things about rooting and locked/unlocked bootloaders for me that just hadn't "clicked" before.
Sent from my Moto X
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
Thanks! This was very helpful. I got stuck in a bootloop from a rooted MotoX 4.2.2 whilst trying to accept the OTA to 4.4. I was able to erase the cache to stop the bootloop problem, but I wanted to accept the OTA. I followed this guide and it seemed to work.
For posterity, anyone on Win7 x64 might have had similar problems to me:
Code:
MX-17-57-X-1_CFC_1FF.xml>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
sending sparse 'system' (777329 KB)...
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
OKAY [ 49.985s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
The solution is to use the mfastboot.exe linked from here: http://forum.xda-developers.com/showthread.php?t=2489249
Hope that helps someone trying to do this same thing.
arigi said:
Thanks! This was very helpful. I got stuck in a bootloop from a rooted MotoX 4.2.2 whilst trying to accept the OTA to 4.4. I was able to erase the cache to stop the bootloop problem, but I wanted to accept the OTA. I followed this guide and it seemed to work.
For posterity, anyone on Win7 x64 might have had similar problems to me:
Code:
MX-17-57-X-1_CFC_1FF.xml>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
sending sparse 'system' (777329 KB)...
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
OKAY [ 49.985s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
The solution is to use the mfastboot.exe linked from here: http://forum.xda-developers.com/showthread.php?t=2489249
Hope that helps someone trying to do this same thing.
Click to expand...
Click to collapse
^^^^THIS^^^^
Thanks @arigi I added this to my original instructions.
Q&A for [Windows Tool] Moto G 2015 XT1072 Restore to to Stock Android 5.0.2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Windows Tool] Moto G 2015 XT1072 Restore to to Stock Android 5.0.2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
ah, waiting for your roms :good:
Will this also revert back to stock recovery? All I have to do after this is to lock relock bootloader (if I want to)?
skippieb0y said:
Will this also revert back to stock recovery? All I have to do after this is to lock relock bootloader (if I want to)?
Click to expand...
Click to collapse
When you perform this operation manually, you have your stock recovery restored. I did not try this automatic tool, but I think the result is the same.
i have adb installed but when i run this script i get and error saying mfastboot.exe is not a recognized internal or external command. any ideas?
djisgod said:
i have adb installed but when i run this script i get and error saying mfastboot.exe is not a recognized internal or external command. any ideas?
Click to expand...
Click to collapse
Tried a few times myself and get the same error message. As above, anyone any ideas?
fs1023 said:
Tried a few times myself and get the same error message. As above, anyone any ideas?
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=2427667 download that file and extract it into the folder where you have already placed all the files. it should then work fine. it is the mfastboot file that is missing. took a lot of trial and error to figure out how to get it working lol i found it by doing this whole process manually by following a guide on here.
djisgod said:
http://forum.xda-developers.com/attachment.php?attachmentid=2427667 download that file and extract it into the folder where you have already placed all the files. it should then work fine. it is the mfastboot file that is missing. took a lot of trial and error to figure out how to get it working lol i found it by doing this whole process manually by following a guide on here.
Click to expand...
Click to collapse
Good stuff djisgod. Have yo tried this recovery to stock method yourself?
fs1023 said:
Good stuff djisgod. Have yo tried this recovery to stock method yourself?
Click to expand...
Click to collapse
yeah i flashed back to stock using this method . relocked the bootloader. then unlocked it again and flashed cm12.1
this will bring back stock update notification? or I will have to do something more manually?
djisgod said:
yeah i flashed back to stock using this method . relocked the bootloader. then unlocked it again and flashed cm12.1
Click to expand...
Click to collapse
once again thanks djisgod. one more question if you don't mind. how do you relock the bootloader?
fs1023 said:
once again thanks djisgod. one more question if you don't mind. how do you relock the bootloader?
Click to expand...
Click to collapse
use the command :
fastboot oem lock
in ADB
Restore to Stock Android 5.0.2 for Motorola Moto G 2015 (XT1072)
"adb" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
< waiting for device >
The part in spanish says " "adb" isn't recognized as an intern or extern command, program or file executable" or something like that.
help? thank you in advance
edit: I don't know if it helps, but I was using CM 12.1 without problems. Then the phone froze and I restarted it. BAM! bootloop. I can't enter recovery.
CanallaManiaco said:
Restore to Stock Android 5.0.2 for Motorola Moto G 2015 (XT1072)
"adb" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
< waiting for device >
The part in spanish says " "adb" isn't recognized as an intern or extern command, program or file executable" or something like that.
help? thank you in advance
edit: I don't know if it helps, but I was using CM 12.1 without problems. Then the phone froze and I restarted it. BAM! bootloop. I can't enter recovery.
Click to expand...
Click to collapse
use the this http://forum.xda-developers.com/attachment.php?attachmentid=2427667. extract the files into the folder where you put the tool then it will work ok.
Everything works fine, just like the guys above said - you need to put the files in /platform-tools directory and rename fastboot.exe to mfastboot.exe.
I guess it saved my device from bootloop.
NOT WORKING: Image is too large
I have a problem when using this tool, I'm quite desperate to fix it because I don't have a recovery due to installing the wrong TWRP version (I installed Titan) at first, here is the problem:
When I start the script I get multiple 'Image file is too large' errors on my phone, this is in my cmd when the errors happen.
target max-sparse-size: 256MB
sending 'system' (256969 KB)...
OKAY [ 8.479s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.588s
target max-sparse-size: 256MB
sending 'system' (259819 KB)...
OKAY [ 8.578s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.643s
Click to expand...
Click to collapse
Clearly the 'Target max-sparse-size (256MB) is smaller than the file it's trying to write (for example 259819 KB > 256 MB), I wonder if there is a way to expand the target max-sparse-size, or if there is any other solution. These errors now result in an infinite ' bootloader unlocked screen'
I am 100% sure that I have a XT1072 .
I will donate if you help me fix this
Don't know what to do?
Hi.
I download the file through the link and i don't know what to do next, can you walk me trough what should i do next. Pls
can anoyone reupload the file , i had a moto g 2015 with bootloop problem
milanmore said:
I have a problem when using this tool, I'm quite desperate to fix it because I don't have a recovery due to installing the wrong TWRP version (I installed Titan) at first, here is the problem:
When I start the script I get multiple 'Image file is too large' errors on my phone, this is in my cmd when the errors happen.
Clearly the 'Target max-sparse-size (256MB) is smaller than the file it's trying to write (for example 259819 KB > 256 MB), I wonder if there is a way to expand the target max-sparse-size, or if there is any other solution. These errors now result in an infinite ' bootloader unlocked screen'
I am 100% sure that I have a XT1072 .
I will donate if you help me fix this
Click to expand...
Click to collapse
Take a look here: http://forum.xda-developers.com/moto-g-lte/help/moto-g-4g-lte-xt1072-bricked-t3091863 and here: http://forum.xda-developers.com/mot...ng-rom-stock-via-twrp-2-t3208614#post63312449
It seems to be an open issue that no one has solved so far. I have exactly the same problem.
Will this remove root and allow me to install OTA updates with no hassle?
Where I can find official ROM for asus me375cl based on android 5.1.1?
Finaly, i find zip with official ROM on 4pda:
4pda-ru/forum/index.php?showtopic=799982
(put '.' (dot) instead '-' in url)
A special thank to alexoid79 for instruction.
little_pindos said:
Finaly, i find zip with official ROM on 4pda:
4pda-ru/forum/index.php?showtopic=799982
(put '.' (dot) instead '-' in url)
A special thank to alexoid79 for instruction.
Click to expand...
Click to collapse
Thank you so much for posting where you found this, this is exactly what I needed!!! You saved my tablet, it is much appreciated! :good:
Flashing Factory Image
The following instructions worked for me when trying to reflash the factory firmware for the ATT Asus MemoPad 7 LTE (ME375CL). I did originally try using the Asus Flash Tool and the raw firmware file (link below) but the tool said it could not unzip the package for some reason or another. So the steps below show how I did it using ADB with fastboot.
I ASSUME NO LIABILITY SHOULD THIS GO WRONG FOR YOU! However, it probably shouldn't matter if you are bricked, I doubt it will make it any worse Either way, I will not replace your tablet or be responsible for troubleshooting it should you mess it up more...
This scenario is based on the tablet stuck on the Asus boot screen and not going any further. I was trying some in depth rooting attempts and bricked it badly. I was then trying to install a custom recovery and that is why I could not reset it and bricked it.
PRE-REQS:
1. ADB installed - Download: https://drive.google.com/open?id=0B0fKccJIuWsna04wMjY1eG9YREU
2. Asus Drivers installed
3. Firmware - Download: https://drive.google.com/open?id=0B0fKccJIuWsnWGhwYzA0Vkluc2s (file is 1 Gb + in size, may take a bit)
SETUP:
If you already have a working ADB setup, do not download the one above. If you are using the one above, I extracted the folder into my C: drive, so the path for ADB would be C:\adb (to keep it simple and less typing).
MAKE SURE THE ASUS DRIVERS ARE INSTALLED! If you have plugged the tablet in to a pc before, they should already be there. Otherwise search, download and install the appropriate drivers.
INSTRUCTIONS:
Extract the firmware zip file to somewhere easily accessible like your desktop. In there, you should see the boot.img, recovery.img and system.img files, copy/paste those files to your ADB folder (for easier typing later on). There are also additional files like these but start with "unsigned_", do NOT use those!
1. Ensure you probably have at least 30% battery charge, I would still recommend more though.
2. Put the tablet in Fastboot mode by ensuring the tablet is completely powered down and then press/hold the VOLUME UP and POWER keys at the same time. When the Asus screen appears, let go of the POWER button but continue to hold the VOLUME UP button. Let go of the VOLUME UP button when the fastboot screen appears.
3. Plug the tablet in to the computer and then open a CMD prompt as administrator.
4. The following uses the ADB downloaded and placed in the folder as listed above, you may need to adjust the location path as needed if you already have ADB installed or located in a different path.
Type in the following without the quotes: "cd c:\adb" (this will change the path to the ADB files for the CMD prompt)
Type in the following without the quotes: "fastboot devices" (you should then see a device listed)
Type in the following without the quotes: "fastboot flash recovery recovery.img" (flashes the factory recovery image)
Type in the following without the quotes: "fastboot flash system system.img" (flashes the factory system image, may take a while to flash)
Type in the following without the quotes: "fastboot flash boot boot.img" (flashes the factory boot image)
5. Once those 3 images have been flashed, you should have seen a message that says "OKAY" after each one. You should be fine as long as you do not have any red error messages on your tablet.
Type in the following without the quotes: "fastboot reboot" (reboots device normally)
6. If all goes well, it should now boot to the Asus screen and then go to the ATT screen. If so, it will stay on the ATT screen for a while, just wait it out. Mine took about 12-15 minutes and then it opened to the new setup screen to set the tablet up as if its new!
This is how I was able to recover my bricked tablet, hopefully it can help someone else that may run into this.
John, thank you for the write-up. Just bought my ME375CL with 4.4.4.4.
When I try to flash the recovery partition, I get the following error:
C:\Users\Myself\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11312 KB)...
OKAY [ 1.047s]
writing 'recovery'...
(bootloader) Official image.
FAILED (remote: flash_cmds error!
)
finished. total time: 2.344s
Click to expand...
Click to collapse
and on the tablet's screen:
FASTBOOT CMD WAITING...
RECEIVE DATA...
E:recovery flash failed!
FLASH FAILED!
RESULT: FAIL(flash_cmds error! )
Click to expand...
Click to collapse
I haven't tried the other commands for system.img or boot.img as I don't want to do anything out of order from the write-up. Ever run into this?
The firmware in the download is 5.1.1, not 4.4.4. That is probably the issue. If you are running good on that, I would try rooting it instead. If you are just wanting to upgrade, you will need to have an active AT&T SIM in the tablet to upgrade over the air. I am not sure if there is a flashable upgrade or not somewhere.
Oh ok John. I misread the title of the thread. I thought it was for updating from 4 to 5.
Quick question then: Is it possible, using the adb / fastboot tools, to backup the current 4.4.4.4 before I allow the tablet to update to Lollipop? After reading around, I understand that Lollipop can't be rooted but I have no real concern for it. But just in case I need the tablet to do something else in the future, I'd like to be able to return it to kit kat to be able to root.
Once you upgrade to lollipop, there is no downgrading for this tablet. There really is not much development for this device. I have kind of been working on a lollipop root when I can. Between my limited time and knowledge of android, I can't promise anything.
Overcoming red messages?
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Gor- said:
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Click to expand...
Click to collapse
Sounds odd that it did 2 out of 3 flashes. After you flashed those and rebooted, are you still on KitKat or did it actually update to Lollipop (5.1)? I ask because I assume the system image that flashed would be the operating system.
I still want to stress that this post is for recovering a bricked tablet that will not boot at all. I would not suggest using this as a flashing upgrade as I do not know if it will truly work. If you are still on KK (even after flashing) you could try installing the Asus Flash Tool and use the raw firmware that you downloaded and try it that way. It did not work for me so that is why I used fastboot. It might work for you.
Here is a link for the Asus Flash Tool:
https://drive.google.com/open?id=0B0fKccJIuWsndXJUa1FEbXVzTjA
johnkirchner said:
Sounds odd that it did 2 out of 3 flashes. After you flashed those and rebooted, are you still on KitKat or did it actually update to Lollipop (5.1)? I ask because I assume the system image that flashed would be the operating system.
I still want to stress that this post is for recovering a bricked tablet that will not boot at all. I would not suggest using this as a flashing upgrade as I do not know if it will truly work. If you are still on KK (even after flashing) you could try installing the Asus Flash Tool and use the raw firmware that you downloaded and try it that way. It did not work for me so that is why I used fastboot. It might work for you.
Here is a link for the Asus Flash Tool: ]
Click to expand...
Click to collapse
As a follow up on your question above, Tab restart stalled at a screen (after the Asus logo), presenting some options to do recovery, reboot, factory reset, etc. (factory reset did not help), and red error messages at bottom.
To the GOOD news for anyone interested. I used the Asus Flash Tool and the firmware zip for 5.1.1 (many thanks for the advice).
Note: Tool did not install correctly on Win10 pc, citing error in installing some devcon.exe or similar file (guess that may be a firewall/antivirus issue).
Flash tool took some 15 or so mins unzipping firmware, after which I saw some action on the tab. Another 15 mins, and it rebooted to the At&t logo, stayed here for another 15 mins and unraveled a whole new device on Android 5.1
Glad to hear it worked for you and that I guess you can use this to flash upgrade from kitkat!
There is working way to root our device on lollipop! It is for the other Asus model, but it works for our
http://4pda.ru/forum/index.php?s=&showtopic=640814&view=findpost&p=53047686
I will check this out!
The root works, installed without any issues and verified with a root checker!
Here is a direct download from my Drive folder: https://drive.google.com/open?id=0B0fKccJIuWsnN21ZbnZpc2F6b1E
1. Download the file above.
2. Extract the zip contents.
3. Plug your ME375CL tablet in to pc via usb cable.
4. Make sure you have enabled Developer Mode and allowed USB Debugging first!
5. Open the folder you extracted and double click the "Root-One-Click.cmd" file.
6. It should reboot to fastboot mode and flash the needed files and then reboot again.
You should now have root access. Verify this by installing a root checker app from the play store. Keep in mind, it may say root not installed on the first run. Sometimes it will take a moment for superuser to initially run or prompt for access.
Side note: the root uninstall did not seem to work, got an error...but oh well, the point is to have root!
Thanks go to @little_pindos for finding this file...you are a rockstar!
Anyone get xposed on LP?
ATT Boot Up Sound
Tired of the ATT boot sound? If you used the rooting method above, then you can get rid of the annoying ATT startup sound by doing the following:
1. Install a Root Browser app (I recommend Rom Toolbox Pro, it has a built in file manager)
2. Navigate to the following path:
root/system/media
3. Find the file named "powerup.wav"
4. Simply rename the file by adding .bak to the end (ex - powerup.wav.bak)
5. Make sure it took the name change (some file managers have issues with that)
6. Reboot and see if it got rid of the sound!
You can also use your own startup sounds as long as they are in a .wav format, I believe. Make sure that the name of the file is powerup.wav.
You can also change your boot animation with "boot animation" app.
Best tweak IMO is adding "ro.config.low_ram=true" to build prop, or installing the low ram device xposed module if we can get it to work (both do the same thing). You gain about 100mb more free RAM on average.
TimmyP said:
You can also change your boot animation with "boot animation" app.
Best tweak IMO is adding "ro.config.low_ram=true" to build prop, or installing the low ram device xposed module if we can get it to work (both do the same thing). You gain about 100mb more free RAM on average.
Click to expand...
Click to collapse
I'll have to try that!
AT&T no longer has updates in system for this tablet
Gor- said:
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Click to expand...
Click to collapse
AT&T removed the last update for this tablet months ago and no longer supports it. ASUS states AT&T has all the updates. Total cluster.
I got root and Magisk working on my G8s (LM-G810EAW)!!
The patched boot image I used for my German (NEU) G8s can be downloaded from (check your Android security patch date in the phone system settings and choose the corresponding version):
Version v10n: here (2019) or
Version v10p: here (January 2020 security patch) or
Version v10q: here (March 2020 security patch)
Version v10r: here (May 2020 security patch)
(then start on step 11)
If you have the same model (AND version!) you can use that, otherwise follow the steps below:
Guide:
0. Unlock the bootloader (https://developer.lge.com/resource/mobile/RetrieveBootloader.dev).
1. Go to https://lg-firmwares.com/lg-lmg810eaw-firmwares/#tab=firmwares and sort by date (newest first).
2. Download the kdz for your region (I chose NEU).
3. Download https://github.com/steadfasterX/kdztools (and install python 3.8 if you don't have it, and add it to your PATH variable).
4. Put the .kdz file in the same directory as the tools.
5. Open a command prompt and run "python .\unkdz.py -f .\YOURFILE.kdz -x". This will create a .dz file using the .kdz file.
6. The newly created .dz file is located in the "/kdzextracted" folder. Move it to the parent folder ("kdztools-master").
7. Run "python .\undz.py -f .\YOURNEWFILE.dz -s". This will make everything into .image files.
8. The output files are in the "/dzextracted" folder.
9. Find the "boot_a.image" file and copy it to your phone's internal storage with e.g. a USB cable.
10. Install the Magisk Manager app (https://github.com/topjohnwu/Magisk/releases).
11. Open the app and click Install -> Install -> Select and Patch a File. Choose the boot.image file. Magisk will then patch it and output a patched image file.
12. Copy the patched image (magisk_patched.img) file to your computer.
13. Put the file in the same directory as adb and fastboot.
14. Enable USB debugging in Android settings and then boot into fastboot with ".\adb.exe reboot bootloader".
15. When the phone is in fastboot, run ".\fastboot.exe flash boot .\magisk_patched.img".
16. Restart (".\fastboot reboot") and run the Magisk manager app and you should have root
17. If you do this process for new updates, remember to unhide the Magisk manager app before updating!
Otherwise, after updating: (If you have a hidden Magisk manager app (repackaged) then you need to uninstall it and reinstall the original version, otherwise it won't detect that you have root!)
Stock boot image:
v10p: here
v10q: here
v10r: here
Android 10 kdz: https://drive.google.com/file/d/1JaIOh96P0ptW2wMGcEamy4pgEAAoxUjw/view?usp=sharing
Edit 2020-03-19: Added patched boot image for January security patch
Edit 2020-06-10: To install OTA updates, you need to use LG Bridge on your computer!
Edit 2020-06-10: Added patched boot image for March security patch
Edit 2020-06-13: Added patched boot image for May security patch
Edit 2020-06-15: Added stock boot images
Edit 2020-09-11: Added .kdz for Android 10 update
you are pro :highfive: great job
Danke
Okay well, your image doesn't work for me (carrier-free German G8S, tells me it can't flash boot with unlocked bootloader which apparantly means the file itself doesn't work) and trying to unpack KDZs (whichever I try) result in weird python errors I can't get behind and no one had similar problems (on Windows, at least - so SALT is not an option for me right now as it is a Linux only app)
sigh
EDIT:
Found the solution!
You wrote down the wrong command to flash the img.
the correct one would be "fastboot flash boot_a FILENAME.img"
only stumbled over this after realizing that the boot image you pulled was called "boot_a" and fastboot tried to flash it onto "boota" with the normal "boot" command
3 hours wasted but at least I have root now!
Frau Son said:
Okay well, your image doesn't work for me (carrier-free German G8S, tells me it can't flash boot with unlocked bootloader which apparantly means the file itself doesn't work) and trying to unpack KDZs (whichever I try) result in weird python errors I can't get behind and no one had similar problems (on Windows, at least - so SALT is not an option for me right now as it is a Linux only app)
sigh
EDIT:
Found the solution!
You wrote down the wrong command to flash the img.
the correct one would be "fastboot flash boot_a FILENAME.img"
only stumbled over this after realizing that the boot image you pulled was called "boot_a" and fastboot tried to flash it onto "boota" with the normal "boot" command
3 hours wasted but at least I have root now!
Click to expand...
Click to collapse
That's weird, writing "boot" worked for me, it said it flashed "boot_a" automatically
Frau Son said:
B]EDIT:[/B]
Found the solution!
You wrote down the wrong command to flash the img.
the correct one would be "fastboot flash boot_a FILENAME.img"
only stumbled over this after realizing that the boot image you pulled was called "boot_a" and fastboot tried to flash it onto "boota" with the normal "boot" command
3 hours wasted but at least I have root now!
Click to expand...
Click to collapse
has worked very well for me according to instructions 5min , it is helpful to know the commands or to get an ADB command list if you do not know
as he described and named it worked well:good:
Code:
Microsoft Windows [Version 10.0.17763.864]
(c) 2018 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\Marie>cd C:\Program Files (x86)\Minimal ADB and Fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'boota' (25340 KB)...
OKAY [ 0.546s]
writing 'boota'...
FAILED (remote: Cannot flash this partition in unlocked state)
finished. total time: 0.554s
*shrug*
tried it with another ABD/Fastboot version too and still the same
I've rooted several phones from different brands over the last... I don't know, 5 years... and fastboot has never betrayed me like that before
LG seems to hate me though - particularly when it comes to rooting/flashing -, so maybe it's just my personal bad luck again
LG Mobile driver and "Minimal ADB and Fastboot" use it since LG G5 and everything has always worked reliably
I had to try this with my G8 (US, LMG820QM). The website:
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
Gave me this message:
Unfortunately, your device( LMG820QM.CCA )does not support
unlocking the bootloader. Your account will be locked if you enter the
wrong information more than 9 times.
So no supported for my G8 in the US. Yet. (A guy can dream.)
jimhark said:
I had to try this with my G8 (US, LMG820QM). The website:
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
Gave me this message:
Unfortunately, your device( LMG820QM.CCA )does not support
unlocking the bootloader. Your account will be locked if you enter the
wrong information more than 9 times.
So not supported for my G8 in the US. Yet. (A guy can dream.)
Click to expand...
Click to collapse
It will never support devices outside of eu
antintin said:
It will never support devices outside of eu
Click to expand...
Click to collapse
Dream killer. Worst part is I know you're almost certainly right.
jimhark said:
Dream killer. Worst part is I know you're almost certainly right.
Click to expand...
Click to collapse
Eh we will get an unofficial unlock method within a couple months probably
i have a question, the first step, "Unlock Bootloader“, how could it be done?
the website says,
==========================================================
Supported Devices
The following devices support unlocking the bootloader:
• LG V50: LMV500EM for the European market
• LG V40: LMV405EBW for the European market
• LG G7: LMG710EM for the European market
• LG V30: H930 and H930G for the European market
• LG G6: US997.USA for the U.S. open market
• LG G6: H870 for the European market
• LG V20: US996.USA for the U.S. open market
• LG V10: H960A for the European market and Android M (Except France)
• LG G5 SE: H840 for the European market
• LG G5: RS988.USA for the U.S. open market
• LG G5: H850 for the European market
• LG G4: H815 for the European market
Unlocking the Bootloader is only supported on selected devices.
==========================================================
there is no LG G8 or LG G8s
culmencasa said:
i have a question, the first step, "Unlock Bootloader“, how could it be done?
the website says,
==========================================================
...
there is no LG G8 or LG G8s
Click to expand...
Click to collapse
Yes I know. I tried to unlock the bootloader the day before, but it didn't work so I emailed them and asked when the G8s would be unlockable.
I got an answer saying that
it will not be activated in the near future
Click to expand...
Click to collapse
The day after I tried again and it worked, even though the G8s isn't on the list No idea why
All work fine after unlock the bootloader? Wifi, camera quality, network, etc...
Even better because i can set the kernel
With magisk everything runs without problems root and System works fine. No problems even bluetooth runs excellent :good:
Bunsenbrenner said:
Even better because i can set the kernel
With magisk everything runs without problems root and System works fine. No problems even bluetooth runs excellent :good:
Click to expand...
Click to collapse
Yeah! So let's go to try! ?
From now i have literally other phone!a better phone!
hej2010 said:
Yes I know. I tried to unlock the bootloader the day before, but it didn't work so I emailed them and asked when the G8s would be unlockable.
I got an answer saying that
The day after I tried again and it worked, even though the G8s isn't on the list No idea why
Click to expand...
Click to collapse
what's their email address, i'd like to ask them too XD
culmencasa said:
what's their email address, i'd like to ask them too XD
Click to expand...
Click to collapse
is open to all EU devices be Email was probably a coincidence ,rather too late the info on the homepage than too late security updates :laugh:
@hej2010
Can you modifire LG UP that we can use it ? that would be excellent
be carefull,magisk caused brick
juliheavy said:
be carefull,magisk caused brick
Click to expand...
Click to collapse
please write in complete sentences! or this isn't gonna help anybody else here. Explain what you did so that mistakes can be found
i use magisk with the modules and have no problems