Introduction
3 days ago, I decided to flash my TB-7304F with its stock ROM, downloaded from NeedROM (https://www.needrom.com/download/le...ndroid-7-and-frp-instructions-and-flash-tool/).
Unfortunately, I was stupid enough to ignore the flashing instructions given below and decided to do it 'my way' (even though I was fully aware that it leads to problems 95% of the time).
Anyway, so I decided to go for the Firmware Upgrade option in SP Flash Tool. Initially, it progressed as expected:
The DA was downloaded successfully
The blue 'Format' bar filled up to 100%
Flashing was about to start
But suddenly, an error message popped up and I panicked and closed it without reading it first.
Then the problems started...
The Problems
I decided to boot up the device, even though I knew it wouldn't work (and it didn't, as expected).
After the full format, the device essentially has nothing inside it.
I have lost Bluetooth/Wi-Fi configurations, everything.
I didn't even keep a backup of the NVRAM, so I don't know how far I can go about restoring those informations.
Now, whenever I try to flash my device with the firmware, I get a different error with each mode (Download Only, Firmware Upgrade, Format All + Download).
In each case, the 'Downloading DA' bar fills up to 100%, followed by an error message.
Download Only
When I choose 'Download Only' for flashing, the error that I get is "ERROR: STATUS_SEC_DL_FORBIDDEN (0xC0020004)" (screenshot below).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Firmware Upgrade
When I choose 'Firmware Upgrade' for flashing, the message that I get is "Failed to get PMT info." (screenshot below).
Format All + Download
When I choose 'Format All + Download' for flashing, the error that I get is "ERROR: STATUS_SEC_WRITE_DATA_NOT_ALLOWED (0xC002000C)" (screenshot below).
What I Have Tried
Apart from the above mentioned things, I have also tried the following:
'i-x_flash_tool' (included within the ROM zip; it is made for TB-4304I and TB-4304X versions)
Results in BROM Error: BROM_CMD_SEND_DA_FAIL
Flash Tool from http://forum.gsmhosting.com/vbb/13243959-post13.html
Same Errors
Flashing without preloader (leaving preloader unchecked)
Results in ERROR: STATUS_SEC_DL_FORBIDDEN (0xC0020004)
Connecting the USB with Volume Up/Down/Both buttons pressed before flashing
Results in BROM Error: BROM_CMD_FAIL
All kinds of Download Agents within the zip:
DA_PL.bin (TB-7304F version)
DA_PL.bin (TB-7304I/X version)
DA_PL_CRYPTO20.bin (TB-7304I/X version)
DA_SWSEC.bin (TB-7304I/X version) - INCOMPATIBLE
DA_SWSEC_CRYPTO20.bin (TB-7304I/X version) - INCOMPATIBLE
MTK_AllInOne_DA.bin - INCOMPATIBLE
Additional Info.
Full Model Name: TB-7304F TAB 1G+8GBL-IN-Ons-NM
CPU: MT8167D 64-Bit
Any help will be deeply appreciated.
Bump.
It's been a while, but I haven't found a solution yet... Can someone please give me some suggestions? Thank you.
uncheck the preloader (as always: do not flash the preloader!)
aIecxs said:
uncheck the preloader (as always: do not flash the preloader!)
Click to expand...
Click to collapse
Thanks for the reply.
I've already tried it before (forgot to mention in in my post), but it still gives me "ERROR: STATUS_SEC_DL_FORBIDDEN (0xC0020004)".
try if read back of boot / recovery is working. you may try different download agents, again. provide the boot.img / recovery.img from read back
you mentioned you lost IMEI - does your device have slot for SIM card? In the link you provided there is another chipset for the 3G version: MT8735D
The ROM used is for the WiFi version: MT8167D (your screenshot says Flash-tool_for_WLAN_no_sim_device) I hope this is all well..
Please double check which chipset you have!
Have had the idea of formatting the FRP partition, therefore i wanted to look inside the scatter file. Now i read that this is already posted in the instructions. Have you done this?
Only for MT8167D
- Main SPFT Window - Go to "Format" tab, select "Validation", "Manual format flash",
copy/paste marked in red "Begin address" : 0x8000000 , "Format length" : 0x100000
Click to expand...
Click to collapse
aIecxs said:
you mentioned you lost IMEI - does your device have slot for SIM card? In the link you provided there is another chipset for the 3G version: MT8735D
The ROM used is for the WiFi version: MT8167D (your screenshot says Flash-tool_for_WLAN_no_sim_device) I hope this is all well..
Please double check which chipset you have!
Have had the idea of formatting the FRP partition, therefore i wanted to look inside the scatter file. Now i read that this is already posted in the instructions. Have you done this?
Only for MT8167D
Click to expand...
Click to collapse
No, my device does not have a SIM card slot. It is the Wi-Fi version, MT8167D, as is printed on the device's box. I must have mentioned IMEI accidentally.
Yes, I have already tried formatting the FRP partition (quite a few times now). Please note that formatting works fine with the DA_PL.bin meant for MT8167D. Mem-testing works fine too. It's just the flashing which is causing problems...
...which leads me to wonder whether there is some kind of write protection somewhere which is forbidding SPFT from flashing ...?
Unfortunately, this is the only time I forgot to take a read-back of the device before flashing, and the only time I messed everything up.
But fortunately, I have a friend with the exact same device, so I'll be able get a read-back from him. I'll try to contact him right away.
Also, since I have formatted the entire flash (except bootloader), it is very likely that the partition info. is lost, and I'll need to do a Format All + Download, which, as I've mentioned, gives me "ERROR: STATUS_SEC_WRITE_DATA_NOT_ALLOWED (0xC002000C)".
It may useful to get dump from your friend, but main reason i asked, i want to look into your current boot / recovery to see why it does not work. Can you flash each partition for each own, maybe it is only forbidden for one/some partitions (for example just flash boot, or just cache, ...)
Assuming your friends device have unlocked bootloader, if it is possible to flash preloader at least you should be able to boot twrp from fastboot. then you have a good base for recovering. Also interesting would be a read back of nvdata/nvram even if it was recently formatted, maybe we can restore the file system from raw image with testdisk or something (at least mac address should be still there somewhere)
partitions may deleted, but you still have the addresses where the partitions was, the scatter file defines the partition all we need is restore EBR
aIecxs said:
It may useful to get dump from your friend, but main reason i asked, i want to look into your current boot / recovery to see why it does not work. Can you flash each partition for each own, maybe it is only forbidden for one/some partitions (for example just flash boot, or just cache, ...)
Assuming your friends device have unlocked bootloader, if it is possible to flash preloader at least you should be able to boot twrp from fastboot. then you have a good base for recovering. Also interesting would be a read back of nvdata/nvram even if it was recently formatted, maybe we can restore the file system from raw image with testdisk or something (at least mac address should be still there somewhere)
partitions may deleted, but you still have the addresses where the partitions was, the scatter file defines the partition all we need is restore EBR
Click to expand...
Click to collapse
I have tried flashing partitions individually before, and I still get "ERROR: STATUS_SEC_DL_FORBIDDEN (0xC0020004)".
I haven't been able to contact my friend today, but I plan to tomorrow. I hope I'll be able to get a ROM dump soon.
does readback work?
aIecxs said:
does readback work?
Click to expand...
Click to collapse
Read-back seems to work fine. Just did a read-back of the preloader partition (0x0 to 0x40000 according to scatter).
[Deleted duplicate reply]
according to the gsm forum you need a combination of FIRMWARE UPGRADE + PRELOADER.bin + DA_SWSEC.bin + auth_sv5.auth and flash only preloader - imagine you already tried that, too? Regarding your NVRAM can you please share scatter file, i was not able to download the ROM. I wanna have a look into and then request readback from you
meanwhile found a mirror: https://firmwareos.com/download-lenovo-tab-7-essential-tb-7304f-firmware
and TWRP: https://gitlab.com/HosteBin/androidlover5842_1/tree/master/Lenovo/lenovotb_7304f
edit: what you have readed back is not the preloader (the preloader is not located EMMC_USER) just want to inform you in case you wanted to use this file (better delete it). if you want read back preloader repeat this for EMMC_BOOT_1
edit2: use this scatter file and do a read-back of:
nvram
boot
recovery
frp
metadata
(and provide a link via pm or post here)
Sorry, but somehow the system isn't allowing me to quote your message... Hope this will make sense without the quotes.
Already tried that. DA_SWSEC.bin gives me DA_SELECTION_ERR; it isn't compatible.
Thanks a lot for the TWRP link!
Yeah, my mistake... Actually, I did do a read-back on EMMC_BOOT_1, but forgot to take a screenshot. So, I decided to do another read-back just for the screenshot. The second time, I must have rushed through the process and forgot to select the right data area.
I'll send you the link in a while.
did you fix it ? the exact same thing happened to me a month ago..
@aIecxs:
Sorry for the delay... Here's the link: http://ge.tt/4drWbTw2
@AndroFluffy:
No, it's not fixed yet... But I really hope it will be. Glad to know I'm not the only person with this issue...
I am not able to sign up because of a non-working capture (I'm not a robot). tried with two different browsers. therefore i can not download the link
anyway because of the size of this rar file i don't believe there is anything left.
can you get into fastboot mode?
aIecxs said:
I am not able to sign up because of a non-working capture (I'm not a robot). tried with two different browsers. therefore i can not download the link
Click to expand...
Click to collapse
But you don't really need to sign up to download. You can directly download, even without an account on the service, I believe. Still, I'll upload it somewhere else, and edit this post with the link.
alecxs said:
anyway because of the size of this rar file i don't believe there is anything left.
Click to expand...
Click to collapse
Probably because it's compressed? But, even then, whatever's left doesn't seem to be of any use as of now.
alecxs said:
can you get into fastboot mode?
Click to expand...
Click to collapse
Well, I did mention it's 'hard-bricked'. Nothing comes up on the screen, however hard I try. So, no, I cannot get into fastboot...
downloaded with another PC. have had a look inside, all files are empty - seems your phone is completely ERASED by written Zeros.
i think you can not flash anything because of MTK Secure Boot. You should focus on how to unlock secro. (i found some other post where somebody mentioned you must remove battery for 10 minutes, but i think this is nonsense). unfortunately i didn't find a Tutorial, but someone on XDA mentioned this
https://blog.csdn.net/ouxie/article/details/48290077
from google translate, and my tiny less understanding, SEC_RO is always flashable (with device specific Secure Boot DA). i believe you don't have secro.img anymore, so best is to get a full dump of a working device. look inside scatter file, there you can change is_download: true or maybe playing around with type: NORMAL_ROM
besides this (i don't think this really matters) you can create your own scatter file based direct on working device, then you have a 100% complete scatter file (you can compare for differences, at least). here is the instructions: WwR MTK v2.30
i know this does not really help, but in case you figured out how to unlock secro and made it flashable again, you have a good base of fileset to start (pgpt sgpt nvram lk secro seccfg ...)
here's a bit more technical information for understanding preloader, there is mentioned a "ADVMETA_BOOT" boot mode (from what i believe you can write NVRAM, but guess this is already handled internal by SP Flash Tool itself)
http://www.lieberbiber.de/2015/07/04/mediatek-details-partitions-and-preloader
http://www.lieberbiber.de/2015/07/05/mediatek-details-little-kernel
at least, you need to flash lk.bin as minimum requirement to get fastboot working
attached Lenovo Secure Boot Download Agent
any unlocking / flashing update on this pos Lenovo tab?
Related
Regards to all!
Another brick I know...
I tried to install TeamWin, found this post on htcmania com showthread.php?t=591253.
Anyway on step 4. Ejecuta windows.bat the install-script I mess up recovery.img I suppose.
When I Power ON phone, I got this message:
Image signature verify fail!
Your boot/recovery image may have an incorrect signature.
...
Only have access to famous "Pink screen", tried many of update.app but every time it fails.
Also, is it necessary to unlock bootloader for this update.app, or to do something else, because it keeps fail on every firmware for G510 and Y300 that I try by now? I'm newbie to this, so sorry if is this stupid question (which I guess it is).
Is there any solution for this, any suggestions guys? Please, I'm close to breakdown.
----
Almost sure that I'm doing something wrong, tried these ROMs below (maybe some other also, but I wrote these in note later) and same error "Fail" .
B165
B166
B173
B178
B189
Anyone with idea?
I manage somehow (friend bought at same time) to find out potential ROM version, B195.
Googled for it, but no success by now.
To be specific: V100R001C00B195
Does someone have a link maybe?
Have a friend who works in phone service. They have an original ROM and he Flash it.
So for the future people who have same problem, here is explanation which I found on net:
"FAIL VERIFY IMAGE SIGNATURE":
The explanation is that the original recovery has a function to install zips with a particular firm, in this case should be Huawei.
However, almost all the ROMS officers who have taken both individual operators and Huawei for this phone have been format Update.app, installable using the "Firmware installer" phone and all had considerable weight.
But there have been some cases in which any operator like Orange Spain, used a zip supplied via OTA (like Update.app ) weighing approximately 90 MB (A minor update) whose function is to update the compilation B179 to B195, and what happens with this update zip format, is that the system makes a brief signature verification bootloader and the recovery and boot.img.
If the system detects that the Bootloader, the recovery or boot.img not have the original signature of Huawei or have been inserted through a hack or the like without having unlocked the bootloader officially, we will automatically display the following message after trying to install "Image Verify signature fail" in red letters.
The reason is surely and as I said before, we have unlocked the bootloader by an unofficial method or change some of those partitions by some hack before installing the zip, and this zip file contains the bootloader, recovery and boot.img because of their small weight, ie, is not able to replace him as the Update.app to return to the originals and leave us avoid this error signature verification.
A Update.app Bootloader completely regenerates us, so they used to solve 90% of problems. In this case we have no salvation unless there is a compilation format've tried installing Update.app or higher, and all other Update.app will Fail in the installation.
In the case of Orange model no Update.app the B195 is no compilation or compilation superior format Update.app , so we must take the SAT to have it fixed, and of course, do as we do not know what happened if we submit to third grade.
Solution is to find adequate ROM and flash with it. Mine was as I mention V100R001C00B195 and on net I can't find that one, so phone service was my destiny. Hope someone else will have more luck.
Regards!
1grouchy said:
Have a friend who works in phone service. They have an original ROM and he Flash it.
So for the future people who have same problem, here is explanation which I found on net:
"FAIL VERIFY IMAGE SIGNATURE":
The explanation is that the original recovery has a function to install zips with a particular firm, in this case should be Huawei.
However, almost all the ROMS officers who have taken both individual operators and Huawei for this phone have been format Update.app, installable using the "Firmware installer" phone and all had considerable weight.
But there have been some cases in which any operator like Orange Spain, used a zip supplied via OTA (like Update.app ) weighing approximately 90 MB (A minor update) whose function is to update the compilation B179 to B195, and what happens with this update zip format, is that the system makes a brief signature verification bootloader and the recovery and boot.img.
If the system detects that the Bootloader, the recovery or boot.img not have the original signature of Huawei or have been inserted through a hack or the like without having unlocked the bootloader officially, we will automatically display the following message after trying to install "Image Verify signature fail" in red letters.
The reason is surely and as I said before, we have unlocked the bootloader by an unofficial method or change some of those partitions by some hack before installing the zip, and this zip file contains the bootloader, recovery and boot.img because of their small weight, ie, is not able to replace him as the Update.app to return to the originals and leave us avoid this error signature verification.
A Update.app Bootloader completely regenerates us, so they used to solve 90% of problems. In this case we have no salvation unless there is a compilation format've tried installing Update.app or higher, and all other Update.app will Fail in the installation.
In the case of Orange model no Update.app the B195 is no compilation or compilation superior format Update.app , so we must take the SAT to have it fixed, and of course, do as we do not know what happened if we submit to third grade.
Solution is to find adequate ROM and flash with it. Mine was as I mention V100R001C00B195 and on net I can't find that one, so phone service was my destiny. Hope someone else will have more luck.
Regards!
Click to expand...
Click to collapse
If its not too late, have a look at this:
https://docs.google.com/file/d/0B1th-jpHK5tXeGt4WWJNS0R1d0k/edit
Its for the Y300 but:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Its worth a shot.
reply
1grouchy said:
I manage somehow (friend bought at same time) to find out potential ROM version, B195.
Googled for it, but no success by now.
To be specific: V100R001C00B195
Does someone have a link maybe?
Click to expand...
Click to collapse
did you find any solution for that
did you already solve it ?
I have the same problem, I only can go on the pink screen.
I'm a big noob and I don't speek very good english; can you help me?
How to flash it ? my phone doesn't boots even to recovery mode !
Hi I have googled for find the way to flash wbrambley y300 image but I didn't find the way . also , my phone is huawei ascend g510 and it was stock-factory rom and it was rooted with busybox
- sorry , I don't have perrmission to upload file or insert photo or even a link!
RGH_PRIME said:
Hi I have googled for find the way to flash wbrambley y300 image but I didn't find the way . also , my phone is huawei ascend g510 and it was stock-factory rom and it was rooted with busybox
- sorry , I don't have perrmission to upload file or insert photo or even a link!
Click to expand...
Click to collapse
You need to put the UPDATE.APP in a folder named "dload" in the sdcard and push vol - and + at the same time then power until it shows updating
nagalun said:
You need to put the UPDATE.APP in a folder named "dload" in the sdcard and push vol - and + at the same time then power until it shows updating
Click to expand...
Click to collapse
I know and I have done the same steps with pink screen on my older phones
but the problem is yhe usb driver . I tried to install kitkat custom rom from huaweiNews.com to repair it and I installed all the drivers for Huawei g510-0200 I found there and in windows control panel I have just found this and I couldn't transfer the files to flash it !
and also , this problem (image verify failed) caused by installing wrong version of CWM (sumsung's instead)
SORRY IF I SHOULDN'T ASK THIS QUESTION HERE .
RGH_PRIME said:
I know and I have done the same steps with pink screen on my older phones
but the problem is yhe usb driver . I tried to install kitkat custom rom from huaweiNews.com to repair it and I installed all the drivers for Huawei g510-0200 I found there and in windows control panel I have just found this and I couldn't transfer the files to flash it !
and also , this problem (image verify failed) caused by installing wrong version of CWM (sumsung's instead)
Click to expand...
Click to collapse
Um, just take out the sd card, put it in your PC with an adapter or something and copy the files there?
Help please
nagalun said:
Um, just take out the sd card, put it in your PC with an adapter or something and copy the files there?
Click to expand...
Click to collapse
Hi , sorry but my phone still doesn't works . I have tried several firmware updates and roms . but non of them worked , thanks from nagalun because of his wise answer, but still I have these problems :
1- it fails in any frimware update ( from huaweinews.com - huawei original frimware from company site - y300 frimwares , etc)
2- phone doesn't mounts in pink screen (I have found the question in the forum . so I'm following it and still no solution . if anyone knows the answer , search for the question and answer it there )
please help me
Hi,
as above, the same problem with my sons G510. He has a Huawei G510-0100 phone, with a 4.1.1 Android, Vodafone (European)version.
I'd try to flash TWRP to install a custom ROM, but the phone now shows only that the image/recovery signature is invalid. The phone doesn't starts, can't enter in fastboot or recovery mode, but I can acces the pink screen. Thats all, the phone is stucked there.
How can I repare this halfbricked device?
(PS.
From Huawei's webpage I downloaded the factory G510-0200 Kernel (3.4.0 version, .rar file).
My phone is G510-0100 version.)
Solved.
I had the same problem. I installed custom recovery and I woke up with error "Your boot/recovery image may have an incorect signature" bla, bla, bla.
How solved I? Simple.
You must reflash stock rom for your Huawei Ascend G510 (0100, 0200 or 0251). If not know your version? Don't wory. Download and flash everyone version until result is ok.
All you need find here http://huawei-g510.com/
Okay..
After a long testing and debugging session with AbduL_PT
This Guy is the only one who can make TWRP work with Rockhip devices. Check his thread and give him some BEER. He Deserve it!:good:
We finally come up with TWRP for our device!!! :victory:
DISCLAIMER: Rooting any Android device or installing a custom ROM firmware will void the warranty of the device and might only be restored by flashing the phone back to stock firmware and uninstalling custom recoveries and such.
I take no responsibility for any malfunctioning or any wrong doing happening to your device(s) by you following this guide. Proceed at your own risk!
Instructions.
Please make sure that you are familiar with RKtools and installing driver from device manager before you proceed on this
For fast booting to flash mode and recovery mode. Please install this app. ROOT required
Bootloader = Press Power + volume (nearest to the powerbutton) for 5 seconds or until Windows detect new device
Recovery = Press power + both volume buttons. One logo show up release power button and keep pressing volume buttons
1. Dowload the zip file to this LINK
includes
RKtool
stock and TWRP recovery
RK29adbdrivers
2. Unzip it and run update
3. Plugin your tablet to you PC .
4. Launch reboot app and choose "Bootloader" or turn off your device do and it manually with buttons
3. Windows will look for drivers and install driver like this guide using the driver I provided
4. Once RKtools detect your device (ii will show Found RKAndroid Loader Rock Usb). hit the "RUN" button and dont press anything else until your device reboot
5. launch reboot app and choose "Recovery" or turn off your device do and it manually with buttons
ENJOY
If you want to go back to stock recovery
launch RKTOOLS again and choose "recovery-stock" image from Recovery folder
I was able to do FULL NANDROID BACKUP and RESTORE successfully using this recovery
Since our device use /data/share as Internal SD card, we have manage the following (credits joe.stone)
Fixed Internal SD handling , now it is correctly /data/share not data/media .
Fixed wipe of Data . Now it does not removes the content of internal SD.
BUGS
1. Data nandroid backup the whole /data partition (includes /data/share which is Internal SD card)
2. Internal SD nandroid back up /data partition as well
3. Default Storage is internal SDcard (it can change to External SD on Mount Menu)
4. If FORMAT Data is chosen on Wipe Menu, reboot to recovery is required
5. For wiping Cust partition, put a tick on "Use rm -rf" on Settings
Credits:
Freaktab.com for all rockchip needs!
joe.stone for allowing us to use his source and provide some changes
and ofcourse..
AbduL_PT and for this TWRP thread for everything... Again this Guy deserves a Thanks and a BEER! LOL!
If you appreciate it , Give those Guys a THANKS and Click that THANKS button below ( dont be so ungrateful [email protected][email protected]#($! )
Reserved
Tried today your beta on my Huawei Mediapad 7 Lite (S7-931u) and seems to me, it is working just fine!
I can only say, great job guys! :good:
Had same issues with Cust partition like in BUGS section of you introduction post, but in the end recovery went OK.
Tried compressing backup and restore and it works.
Didn't try Install option of the recovery, cause i don't know any custom ROMs existing for this tablet, and didn't try Mount option cause don't know what to test.
One minor thing/bug I noticed (if it is even important), when recovery is done and press reboot my tablets screen flips upside down until reboot, afterwards it back to normal.
Anyway, thanks for your effort, now it is time to experiment without reinstall everything from scratch
So what exactly does this do to a device?
TWRP (Team Win Recovery Project) is a custom recovery just like CWM (ClockworkMod).
Custom recovery is used for different OS customization, but mostly is used for installing custom ROMs (like CyanogenMod, CarbonROM, etc.) and full device backup and restore, well at least that is why is mostly known for.
If you are interested in more on TWRP you can follow this links for more: link1, link2
prometej-zg said:
One minor thing/bug I noticed (if it is even important), when recovery is done and press reboot my tablets screen flips upside down until reboot, afterwards it back to normal.
Anyway, thanks for your effort, now it is time to experiment without reinstall everything from scratch
Click to expand...
Click to collapse
yeah.. the first twrp releases created for this device is inverted... Abdul just add some tweak to get the proper orientation for our device
good thing you confirm that nandroid back up works!
are you part of 4pda people?
Yes, nandroid backup works ok, at least on my model.
Didn't have other ROM to test, but I've tested it by "destroying" some parts of stock ROM (apps, settings, etc.) and tried recovery.
Maybe I'll try some RK2918 generic ROM if found something useful.
No, I'm not part of 4PDA people/community, why do you ask?
I'm just a enthusiast who started tinkering around this tablet frustrated with its stock ROM (in)stability.
I've read some 4PDA forum posts and they really have interesting discussions on the subject of Mediapad 7 Lite, but sometimes I'm a bit lost in translation even when using Google Translate. Cyrillic I can read, but speaking/writing Russian sadly no.
prometej-zg said:
Yes, nandroid backup works ok, at least on my model.
Didn't have other ROM to test, but I've tested it by "destroying" some parts of stock ROM (apps, settings, etc.) and tried recovery.
Maybe I'll try some RK2918 generic ROM if found something useful.
No, I'm not part of 4PDA people/community, why do you ask?
I'm just a enthusiast who started tinkering around this tablet frustrated with its stock ROM (in)stability.
I've read some 4PDA forum posts and they really have interesting discussions on the subject of Mediapad 7 Lite, but sometimes I'm a bit lost in translation even when using Google Translate. Cyrillic I can read, but speaking/writing Russian sadly no.
Click to expand...
Click to collapse
Thats nice... anyway i found some generic rk2918 cm10 i will to port one...
Since I am kinda new to this stuff, just to be clear, can I flash a custom ROM and update my Android using this and if yes, where do I get the ROM from and are there any particular instructions for flashing it?
TWRP is not custom ROM, but recovery/install tool that can help you install custom ROMs.
You can flash only custom ROM that is compatible with your device. E.g. MediaPad 7 Lite is based on RK2918 System-on-chip (aka. SoC), and it needs ROM with configuration (settings, drivers, etc.) for that hardware configuration, so it is not easy task to make fully compatible custom ROM, especially if you don't know or don't have source code for you device.
Android platform has very high device "fragmentation", so custom ROM for device with similar hardware specs, can still make your device unusable or bricked at worst if not careful.
As I said before, I didn't find any custom ROM for Mediapad 7 Lite, but I've seen some customization on stock ROM (based on SP19 firmware) on 4PDA forum (but I think it contains only Russian localization - I'm not sure!)
There are some RK2918 custom ROMs (mostly CM10) for some tablets, but don't know it they would be easily customized to this tablet.
Search XDA forum, it has a lot of forum threads on this and similar subjects.
Anyway... if you plan to experiment, you need to be careful, if you don't want your tablet to become "PaperWeight 7 Lite"
Thank you for you're reply. I will for now, keep my device as it is. Thank you for you're time.
just to let any Linux user know I have created a tutorial to flash OP's TWRP here
http://forum.xda-developers.com/hua...tutorial-linux-flash-twrp-mediapad-7-t3002557
OK just tested TWRP sideload with Linux PC that has udev rule set up and adb running
below image is Linux command
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
second image is of result in tablet, zip chosen was Chainfire's supersu
#############################
sorry if next appears negative, I am not an expert just seeking to clarify some things
I have unpacked our TWRP and it appears to be a port of another device.
eg inside build.prop I can see
ro.product.brand=yuandao
....
ro.product.model=n70s
Click to expand...
Click to collapse
secondly inside init.rc there is no line to import the usb rc file instead I only see this import
import /init.recovery.rk30board.rc
Click to expand...
Click to collapse
OOOH there is no usb rc file but I can bodgee one up if you are interested.
altho I have no experience with TWRP I have ported 3 CTRs that show at needrom, so I have some skills....modest too
Did you guys focus on the big picture and forget to update the text files?
Do you mind if I have a go at fixing and either pm you a download link or forum link?
cheers and thanks for reading
Hmmm!?
I am sorry to bring more bad news......but I think I have a found a possible answer to why the id is wrong in TWRP.
EDIT and I am hoping this is the reason why fastboot is not working for me, altho I know not all devices support fastboot. As my udev is right, rebooting and looking for fastboot is currently a fail........but thats one more test I shall have to do in rebuilding our TWRP.
The id is wrong in the stock BOOT image unpacked. That is, our porter may have taken that id as gospel without checking it independently. Also I am aware our device will still have different ids such as for the modem which is often a different manufacturer........I am often wrong.....but this I feel explains the human error in TWRP.
It shows for its init.rc
write /sys/class/android_usb/android0/idVendor 18d1
Click to expand...
Click to collapse
forgive me for pointing out the correct id is 12d1 as showing here
http://www.linux-usb.org/usb.ids
For anyone interested 18d1 is Google.
2) EDIT I was initially planning to have a go at fixing our current TWRP. The time to edit and check stuff is roughly the same time and effort to port a more recent TWRP.
For that reason, if I brick my device, only I have bricked it and all other users are not mislead.......giggles.
I have found that Samsung Galaxy Tab 2 is a 7 inch 600 x 1024 pixels and someone has kindly uploaded TWRP 2.8.4.0 for it at the TWRP site. So fingers crossed I can port that correctly. Later, if device is still alive, I can mod our boot image to correct specs.
cheers and thanks for reading
Go ahead.. Let us know what can you accomplish.. Remember samsung doesnt use Rk flatform.. If you want to go further more.. You can ask Abdul.. He is a very helpful guy
edit
slightly off topic so removed.
Hi
rather than pollute this nice thread about TWRP for our device I have started a new thread on some of my thoughts, feel free to peruse, abuse or comment there. I won't post any more here until I have a proven result or 2 or 6
I hope you understand why I am posting this as well?
cheers
http://forum.xda-developers.com/hua...mediapad-7-lite-s7-931w-online-notes-t3016947
can you please post the link again for the zip file of rk tools and twrp and drivers. it doesnt work anymore. i want to install twrp on my huawei medipad s7 931wd. thanks.
Download link's Down
I have the variant of this phone by boost Mobile. There is so far as I can tell no way to do a normal bootloader unlock procedure on this device. So I have been trying to experiment trying to break or disable verity. Before I get any more excited, let me make sure I understand correctly. None of the partitions for example system, or boot or recovery cannot be flashed while verity is enabled, most certainly if you don't have root access on the device.
Well somehow, and I have yet to be able to repeat this, I was able to flash a system image in Odin, but the device would not boot because I successfully flashed it but because the other binaries did not match the signature of the "custom system". While doing this I was also able to downgrade from binary 8 to binary 7 (android 10 to 9). So I guess my question is, if I am able to repeat this process then how good is it that I am able to flash a system image and How likely would I be able to continue flashing the other partitions? Before I get into detail on how I managed or how I think I managed to do this I want to make sure that this can actually go anywhere before I waste my time.
Okay I I'm not sure if this is what happened that caused the custom system. Inside the AP tar file of the firmware for this device, is a zip file called 'fota'.for a minute it was useless because in order to extract any of the files from it or modify it you need a password, and chain fire just so happen to figure it out a while back and it still works. So with the password I can essentially delete any number of the files I want inside that zip, and it will still flash to the device successfully. Inside that file are various other files like ADBD, sbin and other various interesting files and bin files. I guess I have to experiment more but wouldn't I just be able to modify the fstab, also inside that zip file, to remove verification from the various partitions (verity)? I guess the question is would it still flash. And there's no way to find out without trying because magisk does not touch that folder.
i rooted it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well it is a successful root, but it doesn't hold. Something stops it from taking fully. It will last for a minute or so before disappearing. So I looked at a logcat briefly and saw a few lines every so often mentioning something about the kernel and relocking it. I'm not at my PC right now so I can't post the logs.
DragonFire1024 said:
Well it is a successful root, but it doesn't hold. Something stops it from taking fully. It will last for a minute or so before disappearing. So I looked at a logcat briefly and saw a few lines every so often mentioning something about the kernel and relocking it. I'm not at my PC right now so I can't post the logs.
Click to expand...
Click to collapse
What files did you flash through odin?
sikkinixx said:
What files did you flash through odin?
Click to expand...
Click to collapse
only the ones I am able. Still haven't figured out how i downgraded from 10 to 9. I flashed the stock firmware (AIO firmware. apparently all carrier stock firmware can be flashed, regardless if its Boost Mobile [BST]). I however did flash the modem (CP) with modem.bin and modem_debug.bin from a combination firmware that's supposed to be factory binaries (which I can't flash any others from that combination because it tells me to get permission to flash them lol).
Im glad someone is trying this I just frp unlocked a galaxy s7 and im feeling confident about rooting this sm-a102u but its what i am using for my every internet access but Im cheering for you DragonFire1 You Got this !
majored said:
Im glad someone is trying this I just frp unlocked a galaxy s7 and im feeling confident about rooting this sm-a102u but its what i am using for my every internet access but Im cheering for you DragonFire1 You Got this !
Click to expand...
Click to collapse
I'm quite sure I don't. I've been able to mimic what I've been able to flash to the device. But regardless it doesn't matter because no matter what way I do or what I flash it fails all kinds of check sums. A lot of things do flash, but a bunch of red text comes across the screen that tells me about binary checks sum errors.but the images do flash to the device but until you restore the firmware that was previously on there it will never work again. I really do hate boost Mobile.
DragonFire1024 said:
I'm quite sure I don't. I've been able to mimic what I've been able to flash to the device. But regardless it doesn't matter because no matter what way I do or what I flash it fails all kinds of check sums. A lot of things do flash, but a bunch of red text comes across the screen that tells me about binary checks sum errors.but the images do flash to the device but until you restore the firmware that was previously on there it will never work again. I really do hate boost Mobile.
Click to expand...
Click to collapse
interesting well now that you mention that if you flash similar firmware cant you essentially add whats misssing i mean ive flashed over an install and still had wifi password saved and some apps im confusing myself now but im pretty sure thats how it went
majored said:
interesting well now that you mention that if you flash similar firmware cant you essentially add whats misssing i mean ive flashed over an install and still had wifi password saved and some apps im confusing myself now but im pretty sure thats how it went
Click to expand...
Click to collapse
It depends. So far I have only been able to use a different modem image and nothing else. Even if I flash the images that do match the flashed files that fail checksum, it still fails secure check. What i am confused about is how I am able to flash anything and even get a check sum failure. I was under the impression that images that fail anything, check sum or secure check, won't flash. So my question is how is it I am able to do so? If something is flashing there has to be a way to flash the files it needs.
So I have successfully made kingroot device owner. Not that it does any good because it doesn't seem to give me root. But using one of my favorite apps to seek the activity
Code:
com.kingroot.kinguser/.receiver.DeviceOwnerReceiver
I used dpm to set-device-owner. I did this from the most recent available firmware for this device on a fresh factory reset with no accounts attached.
Before that I also was able to make icebox apps freezer device owner and disable knox apps.
If anybody knows any other tricks I can use for device owner or something that can escalate privileges from here...
I love icebox apps freezer. You can set it as device owner and have the ability to freeze all applications Including system apps. I have been doing so one by one and as I do, some of Samsung's UI disappears and stock Android fills in. This is probably as close to root as I'll get for a while.
DragonFire, which files did you change in order to obtain root? I want to try this out for myself. Please respond
Nothing in the thread mentioning what files he flashed?
for anyone who needs to test code on this type device i have a sm-a102u1 unlocked running android 9 i wont send it off but i will test anybodys wierd root code maybe this exploit could work https://github.com/grant-h/qu1ckr00t let's make history guys i will be the dude who doesn't know what hes doing somebody compile this and tinker with it all you want and send it off to me to test i think CVE-2019-2215 will be our best bet of pwning this sucker i got a laptop running windows 10 for all your needs so if you like just wanna help but dont have the device or dont wanna brick yours be my guest
and even if you have almost 0 coding knowlage feel free to send your abomnation of a rooting software to just get it tested no matter how bad it is
even if you don't have the device
DragonFire1024 said:
Okay I I'm not sure if this is what happened that caused the custom system. Inside the AP tar file of the firmware for this device, is a zip file called 'fota'.for a minute it was useless because in order to extract any of the files from it or modify it you need a password, and chain fire just so happen to figure it out a while back and it still works. So with the password I can essentially delete any number of the files I want inside that zip, and it will still flash to the device successfully. Inside that file are various other files like ADBD, sbin and other various interesting files and bin files. I guess I have to experiment more but wouldn't I just be able to modify the fstab, also inside that zip file, to remove verification from the various partitions (verity)? I guess the question is would it still flash. And there's no way to find out without trying because magisk does not touch that folder.
Click to expand...
Click to collapse
DragonFire1024 said:
Well it is a successful root, but it doesn't hold. Something stops it from taking fully. It will last for a minute or so before disappearing. So I looked at a logcat briefly and saw a few lines every so often mentioning something about the kernel and relocking it. I'm not at my PC right now so I can't post the logs.
Click to expand...
Click to collapse
Sounds like debugging level needs set to Mid or High from the stock setting of low. This can be done and allow the root to stick until a user reboot.
Applying that whole method After, setting debug level, might actually work. It did for the Note5.
At that point, once root is achieved, it really comes down to making sure all partitions are mounted with the same options.
You can't just remount system as read/write only, if that partition normally has "noatime, etc" mounting options. That automatically triggers a verity panic reboot
You got to do the profit work, as well as, get every letter down to the T as far as copying stock fw. File names in Odin, CB, QL, Date fingerprints, file size to the byte (almost).
It's possible to spoof ALL Day, but most don't think (aka Over Think) all the possible checks and balances that would deviate from a standard stock download/flash.
DragonFire1024 said:
Well somehow, and I have yet to be able to repeat this, I was able to flash a system image in Odin, but the device would not boot because I successfully flashed it but because the other binaries did not match the signature of the "custom system". While doing this I was also able to downgrade from binary 8 to binary 7 (android 10 to 9).
Click to expand...
Click to collapse
Plenty of stock firmware packages in revision 8 ship as Android 9. So really it might not have downgraded as much as you think then.
And going from revision 8 to 7....which part of the firmware downgraded? Just the system image? Do you know this for sure if it couldn't boot?
The old samFAIL method would work something similar to that but you would've had to modify the system image you flashed first.
DragonFire1024 said:
Okay I I'm not sure if this is what happened that caused the custom system. Inside the AP tar file of the firmware for this device, is a zip file called 'fota'.for a minute it was useless because in order to extract any of the files from it or modify it you need a password, and chain fire just so happen to figure it out a while back and it still works. So with the password I can essentially delete any number of the files I want inside that zip, and it will still flash to the device successfully. Inside that file are various other files like ADBD, sbin and other various interesting files and bin files. I guess I have to experiment more but wouldn't I just be able to modify the fstab, also inside that zip file, to remove verification from the various partitions (verity)? I guess the question is would it still flash. And there's no way to find out without trying because magisk does not touch that folder.
Click to expand...
Click to collapse
But will flash successfully like you state or are you asking that question without modifying the otacerts first? Because normally the fota.zip contains a lot of data for most of those things you're saying is failing the checks.
So I'm just not sure about the entire story now....
Delgoth said:
Plenty of stock firmware packages in revision 8 ship as Android 9. So really it might not have downgraded as much as you think then.
And going from revision 8 to 7....which part of the firmware downgraded? Just the system image? Do you know this for sure if it couldn't boot?
The old samFAIL method would work something similar to that but you would've had to modify the system image you flashed first.
But will flash successfully like you state or are you asking that question without modifying the otacerts first? Because normally the fota.zip contains a lot of data for most of those things you're saying is failing the checks.
So I'm just not sure about the entire story now....
Click to expand...
Click to collapse
strange how he didnt post anything on how he did it
timba123 said:
If we pay $50 to $75 for a flash token, maybe factory combo could be flashed then root figured out from there but its not worth it to me to spend that for this pos. So stuck with adb debloat I guess. Oh well
Click to expand...
Click to collapse
I mean, after upgrading, yeah the A10e is a bit dated. BUT WAIT...
The A10e is still a device using an Exynos octa-core SoC. Not a snapdragon or mtk chipset. With full command line access and root privileges the hardware itself is actually still quite capable with its 2gb of RAM.
Moto G8 Play was a phone launched in October 2019 and that curiously had few (or none) mods created, and until today, February 2021, no one had managed to at least root this device, with guides that bricked the device(or made it bootloop), or at least did not work, where even with the boot.img patched, the magisk manager could not get root access on the device. Thinking about it and after losing many nights trying to do everything to root my phone, I finally got it, and decided to write this guide for you, with proof of operation and a lot of joy in having made such progress,
but enough with ceremonies, let's go to the guide in fact.
What do I need to do before read this guide?
First of all, backup all your data, you will surely lose it if you don't.
Second, keep in mind that I am not responsible for any errors or damage to the device, keep in mind that this is a mod guide that makes you lose the warranty on your device. What I did worked for me, and theoretically it works for you as long as you do everything correctly.
And lastly and most importantly, unlock the bootloader of your device, if you don't do this, it is possible to brick and transform it into a paper weight for lack of attention. Thinking about it, I wrote a quick guide to unlock bootloader, follow the steps:
1. Go to settings> System> About phone> Build Number and follow the image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Still in the settings, go to System> Advanced> Developer options and again follow the image:
3. On your computer, download platform-tools here and extract it to any folder you prefer. Also download and install Motorola USB drivers. After extracting and installing, open the platform-tools folder and copy the folder path, then open windows command prompt(cmd) and type the following commands:
in cmd, type cd and paste the path you copied, and hit enter. After that, type "adb devices" with your USB connected device(Remember to authorize USB debugging when connecting your device to the PC), if you did everything right, you will see something like this:
then type "adb reboot bootloader" to reboot your device for the correct mode. Once in bootloader mode, do not close cmd, it will still be useful. Access the motorola bootloader unlock site and follow the instructions provided. If you did everything right, your bootloader will appear with the status of flashing unlocked on the screen.
Ah, I talked about backup at the beginning, right? I'm glad you did the backup, because you just had your phone reset and data deleted. Now that you've installed everything right, let's start the hybridization process of your smartphone ... Let's install the Motorola One Macro ROM, which is basically the same thing as Moto G8 Play, but with more RAM, storage and 64- bit enabled, following this, download the One Macro Stock ROM here and extract it to the same folder as platform-tools:
It will look more or less like the photo above. After that, you will need a script to transform flashfile.xml into an appropriate flashfile.bat, and you can download this script here. Extract the .exe in the same folder as the platform-tools and the one macro rom, after this run and it will generate a flashfile.bat file. If your device is connected to the usb in bootloader mode you can now run the .bat and flash the rom on your device. Always remember to leave the battery with more than 50% charge to avoid problems and brick the device. If you did everything right, your device will start up normally. Configure, then go to settings and activate debugging following the steps at the beginning of the guide. You can notice that virtually your device is now a Motorola One Macro with the hardware of a Moto G8 Play, done that, let's go to the root process.
Copy the boot.img file from the platform-tools folder to any folder on your android. After that, install the magisk manager on the official website and open the app. In the magisk tab, click install and then "Select and Patch a file", select the boot.img file, after that make the selection process again, click the arrow and wait for magisk to finish the patch. After that, open google files and copy magisk_patched_XXXXX.img to your phone's root folder, and copy it to your computer again, in the platform-tools folder. Preferably rename it to an easier name, like magisk.img.
Do the process of opening cmd and pasting the folder path with the command "cd" before it. Then restart to bootloader mode as you learned above, and enter the command "fastboot flash boot_a magisk.img"
after finishing the process, type "fastboot flash boot_b magisk.img" and restart your device. If all goes well the magisk manager will detect the root and your phone will be ready.
This is the guide, I hope I have helped everyone who has gone so long without being able to root their devices. I wasted a night testing and writing this, so please consider giving feedback and if you post as a tutorial, leave the method credits to Daniel Santos (me).
Not works, when i flash the rom and the device restart, it give a message that is corrupt
CÆSAR said:
Not works, when i flash the rom and the device restart, it give a message that is corrupt
Click to expand...
Click to collapse
Did you unlock the bootloader correctly? If so, which version of Macro One did you use? If you want, I can pass the exact same version that I installed here and it works perfectly
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
CÆSAR said:
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
Click to expand...
Click to collapse
well, i used the version of the image i sent and it works 100% normal. As for the system, Motorola One Macro and Moto G8 Play have the exact same architecture. They differ only from some sensors, RAM and internal storage. If you want more details of the process, you can send me a dm on twitter (@danadsees) and I can give you the necessary support. I've never tested with the latest version, which uses Android 10, but versions using Android 9 work normally
ok, i will try with that version, and a last question, you tried to play games after install that version?
FInnaly i tried with your version and it works, thx
Does the G8 Play work flawlessly with the One Macro Rom?
RandoMike said:
Does the G8 Play work flawlessly with the One Macro Rom?
Click to expand...
Click to collapse
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
CÆSAR said:
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
Click to expand...
Click to collapse
That's curious. I'm gonna try to root my phone. I hope not to brick it haha.
RandoMike said:
That's curious. I'm gonna try to root my phone. I hope no to brick it haha.
Click to expand...
Click to collapse
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
RandoMike said:
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
Click to expand...
Click to collapse
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
RandoMike said:
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
Click to expand...
Click to collapse
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Daniel69cc said:
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Click to expand...
Click to collapse
Finally, there is some hope to revive this forum hahaha
Someone tryed with the android 10 version?
CÆSAR said:
Someone tryed with the android 10 version?
Click to expand...
Click to collapse
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
RandoMike said:
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
Click to expand...
Click to collapse
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
RandoMike said:
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
Click to expand...
Click to collapse
the root really works with the g8 play android 10 rom? i'm going to try
CÆSAR said:
the root really works with the g8 play android 10 rom? i'm going to try
Click to expand...
Click to collapse
Yep. I believed I would just get the "no bootable a/b slot" error, but it worked!
This guide is for moto g8 play or moto one macro or both ?
I know it's an old phone. The LG G5. But I bought it because my Galaxy died, the G5 was cheap, you can run Lineage OS on it! But wait! No you can't! You'll never make it past loading the custom recovery file. The guide on Lineage's website is worthless, as it's from before 8.0 Oreo. LG patched the that hole closed tighter than a... a.. <insert good simile here>. I have tried every way in the world to get into this phone. I've looked at every thread here. Dirtycow doesn't work. You can't revert back to 7.x Nougat anymore. It can't be done. LG won't let you in.
I have dreamed of escaping google's clutches. It's really important to me. But I can't afford to buy some $250+ dollar phone that may or may not have a working exploit right now.
This time I gambled and lost, so I'm asking for help. Does anyone know of any way I might salvage the situation? I'd be open to buying a phone with Lineage already on it, if it were reasonably priced. I'd also be open to paying someone else to install it on this LG G5, but I have serious doubts you'd be able to. Any help or advice to get Lineage would be greatly appreciated!
bennylava said:
I know it's an old phone. The LG G5. But I bought it because my Galaxy died, the G5 was cheap, you can run Lineage OS on it! But wait! No you can't! You'll never make it past loading the custom recovery file. The guide on Lineage's website is worthless, as it's from before 8.0 Oreo. LG patched the that hole closed tighter than a... a.. <insert good simile here>. I have tried every way in the world to get into this phone. I've looked at every thread here. Dirtycow doesn't work. You can't revert back to 7.x Nougat anymore. It can't be done. LG won't let you in.
I have dreamed of escaping google's clutches. It's really important to me. But I can't afford to buy some $250+ dollar phone that may or may not have a working exploit right now.
This time I gambled and lost, so I'm asking for help. Does anyone know of any way I might salvage the situation? I'd be open to buying a phone with Lineage already on it, if it were reasonably priced. I'd also be open to paying someone else to install it on this LG G5, but I have serious doubts you'd be able to. Any help or advice to get Lineage would be greatly appreciated!
Click to expand...
Click to collapse
Hey, easy man. There's some things you should consider before giving up on a phone. The quick search i did on Google let me know that this device can be bootloader unlocked, and rooted. At this point, I may ask: Is your device linked in someway with Verizon? Did you unlocked its bootloader? did you manage to install TWRP with no issues? Maybe you´re lucky enough to find a way out yourself. I'll try to help you in everything i can.
eduardvi995 said:
Hey, easy man. There's some things you should consider before giving up on a phone. The quick search i did on Google let me know that this device can be bootloader unlocked, and rooted. At this point, I may ask: Is your device linked in someway with Verizon? Did you unlocked its bootloader? did you manage to install TWRP with no issues? Maybe you´re lucky enough to find a way out yourself. I'll try to help you in everything i can.
Click to expand...
Click to collapse
Thanks! I could really use the help. I have unlocked the bootloader. Made it that far. But I haven't been able to root it because all the root exploits seem to have been patched out by the time I got the phone. It's running Android 8.0. It is a U.S Tmobile phone.
Here's where my progress ground to a halt: I can't get that LG program, LGup, to flash 7.0 to the phone. It gives me an error saying "Error - Invalid KDZ file". Well that's odd, I got that KDZ file from LG's official website. They have a section where they keep all the old stock ROMs.
Maybe I'm wrong here, but I think this part is absolutely necessary. You must install 7.0 Nougat in order to roll back the changes LG made when they patched up the recovery mode. Otherwise you can't install a custom recovery file, which is vital. No custom recovery file = no Lineage. Looking forward to your reply !
bennylava said:
Thanks! I could really use the help. I have unlocked the bootloader. Made it that far. But I haven't been able to root it because all the root exploits seem to have been patched out by the time I got the phone. It's running Android 8.0. It is a U.S Tmobile phone.
Here's where my progress ground to a halt: I can't that LG program, LGup, to flash 7.0 to the phone. It give me an error saying "Error - Invalid KDZ file". Well that's odd, I got that KDZ file from LG's official website. They have a section where they keep all the old stock ROMs.
Maybe I'm wrong here, but I think this part is absolutely necessary. You must install 7.0 Nougat in order to roll back the changes LG made when they patched up the recovery mode. Otherwise you can't install a custom recovery file, which is vital. No custom recovery file = no Lineage. Looking forward to your reply !
Click to expand...
Click to collapse
Here is what i found out. Considering your device is LG G5 H830, with android 8.0, it seems you cant install TWRP straight on. However, there is still something you can try. At this point I may ask: can you enter Fastboot Mode? this your only hope to actually root the phone, and then flash TWRP.
Check if you actually can enter fastboot. If you can, then try to send some basic commands like "fastboot devices" "fastboot reboot". I say this because some devices have Fastboot mode disabled on oem, rendering on useless fastboot. Hope this is not your case. Also, post here your exactly fingerprint version (your rom version). It has to be exactly the same one, otherwise it might soft-brick your phone. Maybe you can flash a patched boot image of your actual rom to then flash twrp.
eduardvi995 said:
Here is what i found out. Considering your device is LG G5 H830, with android 8.0, it seems you cant install TWRP straight on. However, there is still something you can try. At this point I may ask: can you enter Fastboot Mode? this your only hope to actually root the phone, and then flash TWRP.
Check if you actually can enter fastboot. If you can, then try to send some basic commands like "fastboot devices" "fastboot reboot". I say this because some devices have Fastboot mode disabled on oem, rendering on useless fastboot. Hope this is not your case. Also, post here your exactly fingerprint version (your rom version). It has to be exactly the same one, otherwise it might soft-brick your phone. Maybe you can flash a patched boot image of your actual rom to then flash twrp.
Click to expand...
Click to collapse
I can indeed send "fastboot devices" and "fastboot reboot", and it does work. The device will be listed in the command window on the computer, and the phone will reboot if you enter the command "Fastboot reboot".
As for the fingerprint version, here's what I was able to accomplish via a terminal in Manjaro Linux. Is this the full fingerprint?
[[email protected] ~]$ adb devices
List of devices attached
LGH8305d6bec71 device
[[email protected] ~]$ adb shell getprop ro.build.fingerprint
lge/h1_tmo_us/h1:8.0.0/OPR1.170623.032/182251913485f:user/release-keys
[[email protected] ~]$
bennylava said:
I can indeed send "fastboot devices" and "fastboot reboot", and it does work. The device will be listed in the command window on the computer, and the phone will reboot if you enter the command "Fastboot reboot".
As for the fingerprint version, here's what I was able to accomplish via a terminal in Manjaro Linux. Is this the full fingerprint?
[[email protected] ~]$ adb devices
List of devices attached
LGH8305d6bec71 device
[[email protected] ~]$ adb shell getprop ro.build.fingerprint
lge/h1_tmo_us/h1:8.0.0/OPR1.170623.032/182251913485f:user/release-keys
[[email protected] ~]$
Click to expand...
Click to collapse
Its seems you were lucky enough. I checked your rom build and compared it with the only rom on your phone that can be rolled back. It totally matchs the anti-rollback v01 firmware 8.0, so you still can roll-back to Nougat if you try the firmware version H83020c, wich you can download over here:
Fastboot-Flashable rom:
Codefire - Listing of H83020c
KDZ Format rom:
http://dl02.gdms.lge.com:5006/dn/downloader.dev?fileKey=FWAAZHZF92MNARE76685PNJ/H83020o_00_0205.kdz
Its seems the first one it's Fastboot-Flashable, so you should know what to do next if the KDZ Rom doesn't work. However, check this website and compare the rom build yourself, just to be clear about it:
Download T-mobile LG G5 H830 Stock kdz firmware H83030C
Download T-mobile LG G5 H830 Stock kdz firmware H83030C -
www.mylgphones.com
The first link has 3 flashable roms there. including KDZ and fastboot format. Make sure to try them all if one doesnt work
If both methods are useless to roll back to Nougat, dont hesitate to tell me. There's still a workaround available.
To be clear, the phone needs to be in "Firmware update" mode in order to use flashboot to flash that Fastboot rom, correct? That's where a "Firmware update" message appears on the screen, and it's encircled by two arrows. It's in the middle of the screen, and it's not small like when you're using fastboot.
I ask because iirc, KDZ files require the use of LGup, that LG official program.
bennylava said:
To be clear, the phone needs to be in "Firmware update" mode in order to use flashboot to flash that Fastboot rom, correct? That's where a "Firmware update" message appears on the screen, and it's encircled by two arrows. It's in the middle of the screen, and it's not small like when you're using fastboot.
I ask because iirc, KDZ files require the use of LGup, that LG official program.
Click to expand...
Click to collapse
It needs to be in firmware update mode only if you are flashing a kdz rom through Lg official flashtool. If you are going to flash through fastboot, you have to make sure your PC recognizes your device sending "fastboot devices". The fastboot flashable room is right in the first link (.zip file, 1,6 GB size file)
The one I'm seeing says it's 1.9 Gigabytes in size. It's #15 on that list, and it's called:
LG-H83020c-Flashable.COMPLETE-ARB01.zip
Correct?
Just wanna be clear on this, the last thing we need is a brick lol
bennylava said:
The one I'm seeing says it's 1.9 Gigabytes in size. It's #15 on that list, and it's called:
LG-H83020c-Flashable.COMPLETE-ARB01.zip
Correct?
Just wanna be clear on this, the last thing we need is a brick lol
Click to expand...
Click to collapse
That should be it. Download it and check it has all partitions (boot, system, recovery, etc...)
You are probably gonna have to flash each partition manually (for example, if you are flashing system, you should write "fastboot flash system system.img" and so on)
Below is a pic of everything that came in that zip file, just to make sure we're on the same page and I've got everything necessary.
I must admit that I'm a little intimidated by flashing each individual component in that zip file. I understand that you can just tell it "Flash this thing!" and it will do it. But how does it know where exactly to flash the new thing? How does it know not to just write it over the previous item you just flashed?
Next question: What all needs to be flashed individually? As you can see, there are a total of 28 entries shown in the pic. But the folders "bootloader" and "META.INF" both contain a lot of stuff. Do you just flash bootloader and META.INF, and it already knows to flash everything the folder contains?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bennylava said:
Below is a pic of everything that came in that zip file, just to make sure we're on the same page and I've got everything necessary.
I must admit that I'm a little intimidated by flashing each individual component in that zip file. I understand that you can just tell it "Flash this thing!" and it will do it. But how does it know where exactly to flash the new thing? How does it know not to just write it over the previous item you just flashed?
Next question: What all needs to be flashed individually? As you can see, there are a total of 28 entries shown in the pic. But the folders "bootloader" and "META.INF" both contain a lot of stuff. Do you just flash bootloader and META.INF, and it already knows to flash everything the folder contains?
Click to expand...
Click to collapse
You don't have to write "fastboot flash" 28 times. You can just write "fastboot flash all". But I'd rather flashing manually.
Ignore the META-INF folder. You can't flash any file inside there. You should only flash every file ending in "xx. Img* such as boot.img or. system.img.
This zip contains that folder because it was meant to be flashed through recovery, but if you try to do that, the recovery will not do it, or it will cancel installation, as there is a line that checks your actual fingerprint to avoid Rolling back.
So the command to flash that whole bootloader file at once is "flashboot flash all bootloader"? And it won't care that it's a folder, and not a .img file?
I see what you mean about flashing the .img files that are below the "bootloader" folder in that pic I posted. To me it makes sense that it would flash those. But as you said, you should only flash every file ending in .img and "bootloader" is actually a folder, even if it is full of those files. So I just want to be clear on how exactly to flash that bootloader file.
Sorry about all the newb questions lol. Once I see your reply here, I'm going to attempt the flash. After that, hopefully I won't need any more help.
bennylava said:
So the command to flash that whole bootloader file at once is "flashboot flash all bootloader"? And it won't care that it's a folder, and not a .img file?
I see what you mean about flashing the .img files that are below the "bootloader" folder in that pic I posted. To me it makes sense that it would flash those. But as you said, you should only flash every file ending in .img and "bootloader" is actually a folder, even if it is full of those files. So I just want to be clear on how exactly to flash that bootloader file.
Sorry about all the newb questions lol. Once I see your reply here, I'm going to attempt the flash. After that, hopefully I won't need any more help.
Click to expand...
Click to collapse
Let's try something a little bit easier first. As you say you unlocked bootloader, maybe you can flash the full rom through recovery. Copy the rom to a sdcard and try that first, maybe you will save yourself a lot of headaches doing this first.
I've bought two H830's and got both to TWRP/LOS ROM no problem. Regardless of your current official build on your phone, you can rollback to version 30c and dirtycow from there to get TWRP. You can get necessary tools/info from here.
0. (If you havn't already...) Enable OEM unlock in settings and unlock bootloader/fastboot
1. Use LGUP tool to clean flash an official 30c version (H83030c_00_0813.kdz) build to your LG H830
2. Dirtycow exploit to get TWRP
3. Use TWRP to install
Let me know how it shakes out
Also an important note, you CANNOT flash directly the recovery via fastboot to get TWRP, only the H850 can do that, NOT the H830. That's something important no one ever brings up. You must use the dirtycow exploit.
EDIT: Oh yeah, and I recommend using UPPERCUT to flash the kdz file since LGUP is such broken trash.
eduardvi995 said:
Let's try something a little bit easier first. As you say you unlocked bootloader, maybe you can flash the full rom through recovery. Copy the rom to a sdcard and try that first, maybe you will save yourself a lot of headaches doing this first.
Click to expand...
Click to collapse
So just put the zip file on my external SD card, and then tell flashboot to...? Or somehow use only the phone itself to flash the rom? Sorry I'm afraid I'm having trouble following along as I've never done this before.
But as per your instructions, the rom (the whole zip file) is now on the external storage SD Card.
Or did you mean to extract the zip file to a folder, and put that on the SD card? My next question would be thus:
What is the exact command to begin flashing, once I have everything in it's proper place? I did a little experiment where I tried to flash one of the files individually. The Linux terminal gave me the following error:
[[email protected] Desktop]$ cd bootloader
[[email protected] bootloader]$ fastboot flash aboot.img
unknown partition 'aboot.img'
fastboot: error: cannot determine image filename for 'aboot.img'
[[email protected] bootloader]$
As you can see, the bootloader folder is on the desktop, with many .img files inside it. Just as the pic in post #11 shows. Inside the bootloader folder is a .img file called "aboot.img". And for some reason fastboot "cannot determine the image filename for aboot.img"
DrowningInFreedom said:
EDIT: Oh yeah, and I recommend using UPPERCUT to flash the kdz file since LGUP is such broken trash.
Click to expand...
Click to collapse
Thank you for the reply! I've got two questions for you:
1. Do you have a link to the version of LG UP that you'd recommend using? It seems that there are many links out there in the wild, and some of them are to old versions. I'm not sure exactly which one I should use.
2. How exactly do you use Uppercut with LG Up? I got Uppercut, but it didn't seem to do anything when I double clicked on it. It just sat there. Is it like some kind of addon or modification to LG up? Or is it supposed to open as it's own program. Thanks!
Use the files provided by codefire , Launch UPPERCUT which will then hook into and launch LGUP automatically (All it does is make LGUP work without errors)
DrowningInFreedom said:
Use the files provided by codefire , Launch UPPERCUT which will then hook into and launch LGUP automatically (All it does is make LGUP work without errors)
Click to expand...
Click to collapse
Here's what happened when I tried to flash the right 80320a file (Nougat):
Any idea why it would say that?