Related
[SOLVED] Read careful through the thread, and if you have the same problem, check the messages on the second page for a solution
Hi all,
Recently got a Lenovo P780 4gb, Chinese version.
It came with VIBE UI 1.0, installed by the vendor.
Now, I wanted to have a different ROM without the Chinese characters here and there, and reading through the forums, I decided to flash a stock ROW version, and then upgrade to another custom ROM.
So I downloaded the 4Gb P780_S123_ROW_131231 version from elsewhere on the forum.
Using the SP Flash tool, it started flashing, and on the bottom I saw some info saying DRAM 8Gb, which worried me because I thought it might have been the wrong version, but the flash completed, green circle shown.
Then tried to reboot...nothing. Phone wouldn't even turn on.
Plugged it again into PC through USB, and the red light comes on, and instead of the device being recognized as a MT Preloader device, it now connects just as a MediaTek USB Port.
The SP Flash tool still recognizes 'something', but when trying to download or upgrade firmware (with another ROM), then the red progress bar goes to 100% quickly, but then hangs, and I see the error message in the log (timestamps removed):
BROM_DLL[4312][2988]: ERROR: MT6589EMISettingFactory::IsComboDiscreteDram(): Bootloader sub-version (MTK_BLOADER_INFO_SUB_VER_00) is not supported! (FlashToolLib/source/common/generic/src/emi_setting.cpp:557)
BROM_DLL[4312][2988]: ERROR: DummyEMISetting::GetDramEMISetting(): Unsupported! (FlashToolLib/source/common/generic/src/emi_setting.cpp:610)
BROM_DLL[4312][2988]: ERROR: FlashTool_Connect(0x05CA13A8): SyncWithDA(): fail! (FlashToolLib/sv5/common/generic/src/flashtool_api.cpp:937)
BROM_DLL[4312][2988]: ERROR: FlashTool_Connect(0x05CA13A8): fail! "S_FT_ENABLE_DRAM_FAIL"(4032). (FlashToolLib/sv5/common/generic/src/flashtool_api.cpp:990)
BROM_DLL[4312][2988]: com_sentry::Close(\\.\COM6, 0000284C): OK! (FlashToolLib/host/windows/com_sentry.cpp:650)
Now, the above error is supposedly caused by using an incorrect ROM. But what would be a correct one ? I assume chinese but what version or it doesn't matter ?
I also downloaded the P780_S135_130917_rooted_twrp_gapps but when opening the scatter file, I see an entry UBOOT that is not available in the ROM, and I cannot download it(above error) or upgrade (UBOOT missing).
Any tips or do I now have a fancy paperweight ?
casaben said:
Hi all,
Recently got a Lenovo P780 4gb, Chinese version.
It came with VIBE UI 1.0, installed by the vendor.
Now, I wanted to have a different ROM without the Chinese characters here and there, and reading through the forums, I decided to flash a stock ROW version, and then upgrade to another custom ROM.
So I downloaded the 4Gb P780_S123_ROW_131231 version from elsewhere on the forum.
Using the SP Flash tool, it started flashing, and on the bottom I saw some info saying DRAM 8Gb, which worried me because I thought it might have been the wrong version, but the flash completed, green circle shown.
Then tried to reboot...nothing. Phone wouldn't even turn on.
Plugged it again into PC through USB, and the red light comes on, and instead of the device being recognized as a MT Preloader device, it now connects just as a MediaTek USB Port.
The SP Flash tool still recognizes 'something', but when trying to download or upgrade firmware (with another ROM), then the red progress bar goes to 100% quickly, but then hangs, and I see the error message in the log (timestamps removed):
BROM_DLL[4312][2988]: ERROR: MT6589EMISettingFactory::IsComboDiscreteDram(): Bootloader sub-version (MTK_BLOADER_INFO_SUB_VER_00) is not supported! (FlashToolLib/source/common/generic/src/emi_setting.cpp:557)
BROM_DLL[4312][2988]: ERROR: DummyEMISetting::GetDramEMISetting(): Unsupported! (FlashToolLib/source/common/generic/src/emi_setting.cpp:610)
BROM_DLL[4312][2988]: ERROR: FlashTool_Connect(0x05CA13A8): SyncWithDA(): fail! (FlashToolLib/sv5/common/generic/src/flashtool_api.cpp:937)
BROM_DLL[4312][2988]: ERROR: FlashTool_Connect(0x05CA13A8): fail! "S_FT_ENABLE_DRAM_FAIL"(4032). (FlashToolLib/sv5/common/generic/src/flashtool_api.cpp:990)
BROM_DLL[4312][2988]: com_sentry::Close(\\.\COM6, 0000284C): OK! (FlashToolLib/host/windows/com_sentry.cpp:650)
Now, the above error is supposedly caused by using an incorrect ROM. But what would be a correct one ? I assume chinese but what version or it doesn't matter ?
I also downloaded the P780_S135_130917_rooted_twrp_gapps but when opening the scatter file, I see an entry UBOOT that is not available in the ROM, and I cannot download it(above error) or upgrade (UBOOT missing).
Any tips or do I now have a fancy paperweight ?
Click to expand...
Click to collapse
Hi. This phones are a little tricky to reflash after is softbriked. Just in case try to reflash with Life 0.7 for 4GB Firmware.
Here is the link:
http://forum.xda-developers.com/lenovo-p780/development/life-rom-lenovo-p780-t2666626
Here is a litle HOW TO in case of softbriked Lenovo P780:
Step by step you wil do this:
>>>>> USE WINDOWS 7 FOR THIS TUTORIAL <<<<<<<<<<<
>>>>>>>>>>REMOVE THE USB CALBLE FROM PHONE! <<<<<<<<<<<<<
NOW:
- Unpack FlashTools, and Click on Flash_tool.exe
- Select a the MT6589_Android_scatter_emmc.txt in ROM from target_bin folder
- Wait file to be added into Flash Tool
- choose Option->USB Model,click USB Model SKIP THIS STEP IFF SELECTED
–> Choose Option->DA DownLoad All->Speed->High Speed, click High Speed
- Turn off your phone - skip this step if is allready powered off
- "Press F9 (hit Download button)" OR " if upgrade ROM Firmware->Upgrade "
- and ONLY NOW connect your phone into the computer via USB data cable.
- The process will start and a red progress bar will appear after color purple, yellow.
- And green circles display
- Finish !
- You can now safely disconnect your phone and turn it on!
After this tell me iff something goes wrong !
OR
Tell me if your phone is from 04.2014 production.
If it is you must remove the checkbox of the preloader when you flash your custom ROM.
Also highly recommended before manipulation of the phone to do a full backup and backup of NVRAM.
Hi,
Well I flashed the initial ROM with everything checked, so don't know if that can be undone?
I tried flashing the life version you linked to, and tried some other stock roms (like P780_S125_130529,P780_S129_130710), but it's all the time the same.
I start the tool, then unplug phone, press reset button, then click download or upgrade firmware.
In the status bar of the tool, I see a speed in bps, EMMC, COM5 (as long as phone not plugged in, this is USB).
Other ROMS froze the timer in this status bar straight away, it remained 0:00 sec, but with the Life ROM, it keeps counting.
But in the end, it always ends with the same error.
I've attached the log, which includes multiple tries (with PRELOADER unchecked, then again with PRELOADER and PRELOAD unchecked, then with all checked, update and download).
Can't I do something like format it all, then do a fresh install ? Guess it's not that simple
I used the flashtool included, and SP_Flash_Tool_v3.1332.0.187, no difference.
Don't see production date, only see sticker with 02-5707-131911 Lenovo P780 and a number. CMIT ID : 2013CP5888 on the battery itself there is a number 140315
Thanks already for your help and tips.
casaben said:
Hi,
Well I flashed the initial ROM with everything checked, so don't know if that can be undone?
I tried flashing the life version you linked to, and tried some other stock roms (like P780_S125_130529,P780_S129_130710), but it's all the time the same.
I start the tool, then unplug phone, press reset button, then click download or upgrade firmware.
In the status bar of the tool, I see a speed in bps, EMMC, COM5 (as long as phone not plugged in, this is USB).
Other ROMS froze the timer in this status bar straight away, it remained 0:00 sec, but with the Life ROM, it keeps counting.
But in the end, it always ends with the same error.
I've attached the log, which includes multiple tries (with PRELOADER unchecked, then again with PRELOADER and PRELOAD unchecked, then with all checked, update and download).
Can't I do something like format it all, then do a fresh install ? Guess it's not that simple
I used the flashtool included, and SP_Flash_Tool_v3.1332.0.187, no difference.
Don't see production date, only see sticker with 02-5707-131911 Lenovo P780 and a number. CMIT ID : 2013CP5888 on the battery itself there is a number 140315
Thanks already for your help and tips.
Click to expand...
Click to collapse
Hi. Can you do something for me? Open the case of the phone. Look on the accumulator. Tell me iff on the label there is writen something with 04.2014.
stympy said:
Hi. Can you do something for me? Open the case of the phone. Look on the accumulator. Tell me iff on the label there is writen something with 04.2014.
Click to expand...
Click to collapse
Nope, Just the numbers from previous post, IMEI, SN, and some other number, but nothing like 04.2014.
The original ROM (when received), was VIBEROM_V1.0_1415_2_ST_P780_OLK_W_A291.
Only found this rom as CWM recovery flashable, not SP Flash.
But at this point, it seems hopeless
casaben said:
Nope, Just the numbers from previous post, IMEI, SN, and some other number, but nothing like 04.2014.
The original ROM (when received), was VIBEROM_V1.0_1415_2_ST_P780_OLK_W_A291.
Only found this rom as CWM recovery flashable, not SP Flash.
But at this point, it seems hopeless
Click to expand...
Click to collapse
Tonight ill try to download for you. I do not know how long it will take me to download the flashable with Flash Tools.
stympy said:
Tonight ill try to download for you. I do not know how long it will take me to download the flashable with Flash Tools.
Click to expand...
Click to collapse
Wow thanks The closest version I found on needrom is VIBEROM_V1.0_1415_DEV_P780_OLK_W_A291 but I don't know what format it is, it's still downloading.
And then again, I got it with this VIBEROM already flashed on it, and going into the settings and even built in diagnostics menu (when I could still get there) I don't recall seeing any version numbers even closely related to the numbers I find on the stock roms.
From the official VIBEUI site, it's the wrong format. The software version said something with name lenovohome.net, but I gave up on that, Chinese is beyond my knowledge and Google translate doesn't quite get it
Further, read some people advise just try to dowload PRELOADER, and others talk about volume- and power while plugging in (META-mode?).
But I guess that is not related to the problem.
As I understand it, PRELOADER and bootloader versions do not work together ?
It's a real pity since I used one of the official stock roms found on this site, and it actually flashed without problems.
PS : I see the option to format, including bootloader. In other roms I find UBOOT image. Is there something in this area that I can try
So... What i found is like this:
Your ex system is not a system that installs with Flash Tools.
Here is something what i found:
First Install
1. Flash rom china P780_S129_130710 with Flash Tools
2. Root rom china with Framaroot
3. Install MobileUncleTools
4. Install P780_CN_CWM-recovery with MobileUncleTools
Second Install From CWM
5. Install VIBEROM_V1.0_1415_2_ST_P780_OLK_W_A291.zip
6. Install GApps_Core_4.2.2.zip
7. Install SuperSU.zip
8. Wipe Data/Factory Reset
9. Reboot
Here is the Link:
https://drive.google.com/folderview?id=0B2ORIgaV4iacUk5wdEg3ejhhbGM&usp=sharing
stympy said:
So... What i found is like this:
Your ex system is not a system that installs with Flash Tools.
Here is something what i found:
First Install
1. Flash rom china P780_S129_130710 with Flash Tools
2. Root rom china with Framaroot
3. Install MobileUncleTools
4. Install P780_CN_CWM-recovery with MobileUncleTools
Second Install From CWM
5. Install VIBEROM_V1.0_1415_2_ST_P780_OLK_W_A291.zip
6. Install GApps_Core_4.2.2.zip
7. Install SuperSU.zip
8. Wipe Data/Factory Reset
9. Reboot
Ill upload the files Tonight iff you want !
Click to expand...
Click to collapse
I already tried that file, but it was no different than the others. I'm downloading it again from the link on this site (http://forum.xda-developers.com/lenovo-p780/general/stock-rom-lenovo-p780-stock-roms-guides-t2656441).
So hold off downloading/uploading any files
I appreciate your help in this matter, although the outlook of things is not so good right now.
casaben said:
I already tried that file, but it was no different than the others. I'm downloading it again from the link on this site (http://forum.xda-developers.com/lenovo-p780/general/stock-rom-lenovo-p780-stock-roms-guides-t2656441).
So hold off downloading/uploading any files
I appreciate your help in this matter, although the outlook of things is not so good right now.
Click to expand...
Click to collapse
Update : so no, same error.
Since nothing to loose at this point, decided to try SP Flash format (EXCEPT bootloader), and I spotted these lines in the log :
05/14/14 01:24:14.618 BROM_DLL[676][1172]: DEBUG: MT6589EMISettingFactory::LoadEMICfgSetting(): sizeof(BLoaderInfo_v05_ST)(112), m_identifier(MTK_BIN), m_version(V116"Ʉ3Щ, m_start_addr(0x700090), m_num_emi_settings(1). (FlashToolLib/source/common/generic/src/emi_setting.cpp:481)
05/14/14 01:24:14.618 BROM_DLL[676][1172]: DEBUG: MT6589EMISettingFactory::LoadEMICfgSetting(): Type(0x202) (FlashToolLib/source/common/generic/src/emi_setting.cpp:488)
05/14/14 01:24:14.618 BROM_DLL[676][1172]: DEBUG: MT6589EMISettingFactory::IsComboMCPDram(): EMI list size(1), index(0), type(202317c57ba). (FlashToolLib/source/common/generic/src/emi_setting.cpp:522)
Given the rom I use comes from a Russian forum, and I see Russian characters, it might be from the image, but maybe something relevant.
Would it help or make it worse to format everything including bootloader, then just flash ...well...something ?
casaben said:
Update : so no, same error.
Since nothing to loose at this point, decided to try SP Flash format (EXCEPT bootloader), and I spotted these lines in the log :
05/14/14 01:24:14.618 BROM_DLL[676][1172]: DEBUG: MT6589EMISettingFactory::LoadEMICfgSetting(): sizeof(BLoaderInfo_v05_ST)(112), m_identifier(MTK_BIN), m_version(V116"Ʉ3Щ, m_start_addr(0x700090), m_num_emi_settings(1). (FlashToolLib/source/common/generic/src/emi_setting.cpp:481)
05/14/14 01:24:14.618 BROM_DLL[676][1172]: DEBUG: MT6589EMISettingFactory::LoadEMICfgSetting(): Type(0x202) (FlashToolLib/source/common/generic/src/emi_setting.cpp:488)
05/14/14 01:24:14.618 BROM_DLL[676][1172]: DEBUG: MT6589EMISettingFactory::IsComboMCPDram(): EMI list size(1), index(0), type(202317c57ba). (FlashToolLib/source/common/generic/src/emi_setting.cpp:522)
Given the rom I use comes from a Russian forum, and I see Russian characters, it might be from the image, but maybe something relevant.
Would it help or make it worse to format everything including bootloader, then just flash ...well...something ?
Click to expand...
Click to collapse
Update : tried formatting including bootloader : same error.
Tried enabling/disabling different modules : same error.
Seems the phone is hard bricked...
casaben said:
Update : tried formatting including bootloader : same error.
Tried enabling/disabling different modules : same error.
Seems the phone is hard bricked...
Click to expand...
Click to collapse
Indeed... I think you should go to some service and take a look...
Send us some feedback when you get it back...
Good luck.
Sent from my Lenovo P780 using XDA Free mobile app
stympy said:
Indeed... I think you should go to some service and take a look...
Send us some feedback when you get it back...
Good luck.
Sent from my Lenovo P780 using XDA Free mobile app
Click to expand...
Click to collapse
Hi, in another thread, where you were also active, a user mentions P780_136_140306.
Do you know where I can get that ROM ? It would be the only ROM I didn't try yet
Thanks!
casaben said:
Hi, in another thread, where you were also active, a user mentions P780_136_140306.
Do you know where I can get that ROM ? It would be the only ROM I didn't try yet
Thanks!
Click to expand...
Click to collapse
Here is the link:
https://drive.google.com/folderview?id=0B2ORIgaV4iacT01mTm5JVzFuRGs&usp=sharing
Good Luck.
Problem SOLVED !
Hi,
The phone is back to life!
So, here is what I did: thanks to user stympy, who gave some valuable advise, and was actually on the right track.
The phones with a production date starting from 03.2014 have an updated PRELOADER. If you try to use flashing the PRELOADER of any other rom here on these phones, you'll end up like me.
The production date, I think, is printed on the battery (if you have a Chinese model at least).
YOU CANNOT FLASH A PRELOADER OF THE ROMS ON THE FORUM ON PHONES WITH A PRODUCTION DATE 03.2014 OR LATER (at this moment)
So, I found on a Russian forum (sorry XDA but for Lenovo there is a lot more to find on 4PDA than here), a backup of the correct,new preloader.
- I took the P780_S129_130710 ROM, and replaced the preloader.bin with the one in this rom.
- Next, deleted the checksum.ini file in the rom to avoid errors
- Open SPFT, selected the ROM, made sure PRELOADER entry was pointing to the correct preloader.bin
- USB disconnected, I clicked Download with DA DL All with checksum activated
- Plugged in USB
- Flashed without issue, disconnected, and voila, boot!!!
Well, that gave me a Chinese interface, but some screenshot tutorials enabled me to switch it to English.
I luckily took a backup with MobileUncleTools of my IMEI, since that was gone.
Phone seems to work normal, with 2 SIM cards, but a lot of Chinese bloatware.
While I was at it in SPFT, I tried to flash pre-rooted, or ROW versions, but that was unsuccessful so far. Always the good old 4032 error, although I updated the preloader, or some other failures.
However, the problem I'm trying to fight now, is the recovery mode. Can't backup (and not going to try flash ROM through recovery), since I can't mount /data, /emmc, and other crucial partitions. I'm using CWM. My goal is to flash the SLX ROM or any other rom with less bloatware, in English, and stable.
Update : Flashed :
- P780_S135_130917_rooted_twrp_gapps + modified preloader and works fine: had to manually link the UBOOT to the LK file (SPFT did not do it by itself)
- VIBEUI_V1.5_1419_5_DEV_P780_rooted_twrp_gapps + modified preloader and works fine : same problem with UBOOT
- Some other (Chinese) versions. ALWAYS put in the preloader file I attached, and everything went smooth and OK
Decided to not use CWM anymore, it's buggy. I use the built in TWRP recovery, and that works like a charm. No issues whatsoever.
Decided to keep VIBEUI_V1.5_1419_5_DEV_P780_rooted_twrp_gapps, but my preferred one until now was just the old stock version.
Simple and good
I've attached the preloader.bin I used (use at your own risk!), I guess it might come in handy for all of you with the same problem
Note that this particular preloader worked for me on a Chinese model 4Gb, production date 15/03/2014
And thanks again to Stympy for all the help!
casaben said:
Hi,
The phone is back to life!
So, here is what I did: thanks to user stympy, who gave some valuable advise, and was actually on the right track.
The phones with a production date starting from 03.2014 have an updated PRELOADER. If you try to use flashing the PRELOADER of any other rom here on these phones, you'll end up like me.
The production date, I think, is printed on the battery (if you have a Chinese model at least).
YOU CANNOT FLASH A PRELOADER OF THE ROMS ON THE FORUM ON PHONES WITH A PRODUCTION DATE 03.2014 OR LATER (at this moment)
So, I found on a Russian forum (sorry XDA but for Lenovo there is a lot more to find on 4PDA than here), a backup of the correct,new preloader.
- I took the P780_S129_130710 ROM, and replaced the preloader.bin with the one in this rom.
- Next, deleted the checksum.ini file in the rom to avoid errors
- Open SPFT, selected the ROM, made sure PRELOADER entry was pointing to the correct preloader.bin
- USB disconnected, I clicked Download with DA DL All with checksum activated
- Plugged in USB
- Flashed without issue, disconnected, and voila, boot!!!
Well, that gave me a Chinese interface, but some screenshot tutorials enabled me to switch it to English.
I luckily took a backup with MobileUncleTools of my IMEI, since that was gone.
Phone seems to work normal, with 2 SIM cards, but a lot of Chinese bloatware.
While I was at it in SPFT, I tried to flash pre-rooted, or ROW versions, but that was unsuccessful so far. Always the good old 4032 error, although I updated the preloader, or some other failures.
However, the problem I'm trying to fight now, is the recovery mode. Can't backup (and not going to try flash ROM through recovery), since I can't mount /data, /emmc, and other crucial partitions. I'm using CWM. My goal is to flash the SLX ROM or any other rom with less bloatware, in English, and stable.
I've attached the preloader.bin I used (use at your own risk!), I guess it might come in handy for all of you with the same problem
And thanks again to Stympy for all the help!
Click to expand...
Click to collapse
Thank you for your feedback. I hope this information that you gived us today will help other people too.
Sent from my Lenovo P780 using XDA Free mobile app
The same problem, but...
Hi, I have the same problem - chinese P780 4GB, brand new, 04-2014.
After flashing wrong (as i know it now, but not 2 hours ago) ROM P780_S135_130917_rooted_twrp_gapps my brand new P780 don't want to turn on and seems to be bricked. :crying:
During flashing everything was ok - no errors, mistakes, or something something else wrong. Flashing finished with green circle. I've read carefully all the posts in this thread but I can not repeat your solution cause now Flash Tool can't connect to device. When USB cable is plugged into the phone red light turn on, but my computer didn't see any new devices - no "MTK USB port", or "Android device" or even "unknown device".
Any suggestions?
nagoHaK said:
Hi, I have the same problem - chinese P780 4GB, brand new, 04-2014.
After flashing wrong (as i know it now, but not 2 hours ago) ROM P780_S135_130917_rooted_twrp_gapps my brand new P780 don't want to turn on and seems to be bricked. :crying:
During flashing everything was ok - no errors, mistakes, or something something else wrong. Flashing finished with green circle. I've read carefully all the posts in this thread but I can not repeat your solution cause now Flash Tool can't connect to device. When USB cable is plugged into the phone red light turn on, but my computer didn't see any new devices - no "MTK USB port", or "Android device" or even "unknown device".
Any suggestions?
Click to expand...
Click to collapse
Here is a litle HOW TO in case of softbriked Lenovo P780:
Step by step you wil do this:
>>>>> USE WINDOWS 7 FOR THIS TUTORIAL <<<<<<<<<<<
>>>>>>>>>>REMOVE THE USB CALBLE FROM PHONE! <<<<<<<<<<<<<
NOW:
- Unpack FlashTools, and Click on Flash_tool.exe
- Select a the MT6589_Android_scatter_emmc.txt in ROM from target_bin folder
- Wait file to be added into Flash Tool
- choose Option->USB Model,click USB Model SKIP THIS STEP IFF SELECTED
–> Choose Option->DA DownLoad All->Speed->High Speed, click High Speed
- Turn off your phone - skip this step if is allready powered off
- "Press F9 (hit Download button)" OR " if upgrade ROM Firmware->Upgrade "
- and ONLY NOW connect your phone into the computer via USB data cable.
- The process will start and a red progress bar will appear after color purple, yellow.
- And green circles display
- Finish !
- You can now safely disconnect your phone and turn it on!
Flash this one: https://drive.google.com/folderview?id=0B2ORIgaV4iacT01mTm5JVzFuRGs&usp=sharing
It will work.
PROBLEM SOLVED / Thx casaben
Hello,
today i tried to flash my P780. The Build-Number of my phone was P780_S136_140306.
I flashed ROM P780_S135_130917_rooted_twrp_gapps with Smart Phone Tools and after that my phone was dead.
I flashed this ROM because i want to flash the ROM AOSP-4.4.2-v.1.8 after that.
Thx stympy for your tutorial to bring back my phone back to life!
I don´t know if my phone is chinese or not. There is no date on the battery, only chinese letters.
I need help to flash ROM AOSP-4.4.2-v.1.8.
Thx
Hi there
i have alcatel pixi 7 (i213)
i root it then backuped with MtkDroidtools
now i want to install recovery cwm BUT
my recovery size is 16 mb
im unpacking - repacking stock recovery but after flashing its even not booting
flashing recovery 16 mb and its booting
after repack it is 5-6 mb
i think its uses other pack method
help PLS
blabla
if someone needs...
stock recovery : https://mega.co.nz/#!G4kDkJpL!CH3oWWqDm_6rDLGlHgoOISvg-jd436FXnNkdtCboGh0
CTRecovery_2.5 : https://mega.co.nz/#!jh82HKoR!D-BbITkkfHqMNy6hewgCLV_7Xw9xZJoX8YfezwqHpKQ
Hi!
I have bricked my pixi 7 (i213). After root i have started debloating stock firmware and misstyped some command and of course i didn't made a copy.
If anyone could upload and share custpack and system (android) images/partitions or whole stock firmware it would be great.
Xcore_Rj said:
if someone needs...
stock recovery : https://mega.co.nz/#!G4kDkJpL!CH3oWWqDm_6rDLGlHgoOISvg-jd436FXnNkdtCboGh0
CTRecovery_2.5 : https://mega.co.nz/#!jh82HKoR!D-BbITkkfHqMNy6hewgCLV_7Xw9xZJoX8YfezwqHpKQ
Click to expand...
Click to collapse
whats that custom recovery for?
is it compatible with my zeki quad core 4.4.2 android tablet?
i need one!! :fingers-crossed:
hmmm
emm
download mobile upgrade
here's the link http://www.alcatelonetouch.com/glob...n/PIXI_7/otu/mobile-upgrade-s-4-1-8-setup.exe
open it
select pixi 7 or i213
and follow steps
contact if any problems
glad to help
Sent from my I213 using XDA Free mobile app
Thanks for the reply.
Mobile upgrade pops up message that there is no new firmware for my tablet. I think its stock fw wasn't from alcatel. It's custom made by Orange telecomunication company ... don't know what to do next .
Marcin Tomczczyk said:
Thanks for the reply.
Mobile upgrade pops up message that there is no new firmware for my tablet. I think its stock fw wasn't from alcatel. It's custom made by Orange telecomunication company ... don't know what to do next .
Click to expand...
Click to collapse
mine is from orange too..but its updating...
so i can give my system.img..its already rooted..try so..
https://onedrive.live.com/?cid=b84e72ba94787c35&id=B84E72BA94787C35%211315&ithint=file,img&authkey=!ACvvZMgyUIoS2rU
if after flashing it will not boot flash boot.img too https://mega.co.nz/#!T80ihQAA!wiofxhYpc_5sfrKpUYIINSU-Vzb7vFqENI1EbaPyT-0
Thanks for the upload, share and help!
I was talking about polish part of the Orange corporation, not the international one. So this might be the answer why mobile upgrade not updating my tablet firmware . They don't give a f... .
Also still not booting after flashing system and boot images.
Does your firmware have custpack partition? It is partition with stock apk's and other stuff from alcatel. I was deleting packages from this partition also.
I know i'm asking a lot but if your firmware does have this partition, could you also upload it?
Could you also upload custpack partition? I have no other way to unbrick this tablet .
zzzz
Is this compatible with my l212? I think its not. Can you check my Dump System? If we are the same partition then i can flash that.
How to root?
Hello everybody.
I bought the tablet, and try to find a way to root it.
All the tools I found didn't make the job...
How do you root your device?
Thanks for your support!
Greetings
ThMusch said:
I bought the tablet, and try to find a way to root it.
All the tools I found didn't make the job...
How do you root your device?Greetings
Click to expand...
Click to collapse
I Had some problems with rooting this piece of crap the conventional way, but I managed to do it using iRoot. The bad thing is that iRoot's SU app will keep installing a lot of useless stuff in Chinese. To get rid of them, you first need to install SuperSU from the Play Store (If I recall correctly CWM Superuser will work fine as well, but ChainsDD Superuser won't, so keep this in mind) after rooting it and then using manually remove the Chinese SuperUser apk that comes with iRoot and once you get rid of it, you can uninstall the remaining Chinese apps the normal way.
Marcin Tomczczyk said:
Could you also upload custpack partition? I have no other way to unbrick this tablet .
Click to expand...
Click to collapse
I am in the middle of unbricking my Pixi 7 after failed installation of fonts (my font folder CHMOD got messed up and now the device is not booting as it can't reed it), and if I success, I'll post here about the process.
@edit
Okay, if anyone ever has problem with recovering their Pixi 7, here are the steps to make a clean installation using Mobile Upgrade S. The only requirement is to have the device already installed on at least one of your USB ports (otherwise your OS won't detect it, as it will try to install the drivers, but will fail because it sees the device to be disconnecting shortly after plugging it in – at least it was my case):
1. Download Mobile Upgrade S and SP Flash
2. Grab this scatter file.
3. Open the file you just downloaded. Find the following section:
...
partition_index: SYS3
partition_name: PRO_INFO
file_name: NONE
is_download: false
...
Click to expand...
Click to collapse
And replace is_download to true;
4. Open Flash tool and in your download section select your edited scatter file.
5. Go to Readback and select Add.
6. Double-click the added line and save it as pro_info.img
7. Set it as follows: Type : hex , Region EMMC_USER , start : 0x100000 , lenght 0x300000
8. Click Read Back, turn off your Pixi and connect it to your PC via USB cable. It should start the read immediately and after few seccond you should get a success messgae. If it's not the case, try a different USB port.
9. After you got your read, disconnect your Pixi and open newly created pro_info.img file in a hex editor.
10. Find your device version (it's soimewhere at the beggining, around adress 0xA3, and looks like XXXI213-XXXXXXX, where X can be any character, for example mine was COXI213-2DRGPL1) and change it to ENXI213-2BALGB1.
11. Replace your software version (Right after your device ver. Mine was AAZY1AAZ0Z0BD00) for AAZY1AAY0Y0BD00.
12. Save changes to your file.
13. Go back to your SP Flash tool > Download tab
14. Select your scatter file. Deselect all checkboxes. Leave PRO_INFO checked only.
15. Click on PRO_INFO location and select the file you just edited.
16. Select Download and connect your Pixi.
17. When done, run Mobile Upgrade S and follow the standard upgrading process (be aware, that it will take a lot of time to download the ROM, as the download speed goes around 20-50 KB/s. It took me aroung 8h to download it).
18. After installation run your Pixi for the first time and wait for it to boot (don't panic if it takes a bit of time. It will be booting for about 2-5 minutes for the first time).
Nidrax said:
I Had some problems with rooting this piece of crap the conventional way, but I managed to do it using iRoot. The bad thing is that iRoot's SU app will keep installing a lot of useless stuff in Chinese. To get rid of them, you first need to install SuperSU from the Play Store (If I recall correctly CWM Superuser will work fine as well, but ChainsDD Superuser won't, so keep this in mind) after rooting it and then using manually remove the Chinese SuperUser apk that comes with iRoot and once you get rid of it, you can uninstall the remaining Chinese apps the normal way.
I am in the middle of unbricking my Pixi 7 after failed installation of fonts (my font folder CHMOD got messed up and now the device is not booting as it can't reed it), and if I success, I'll post here about the process.
@edit
Okay, if anyone ever has problem with recovering their Pixi 7, here are the steps to make a clean installation using Mobile Upgrade S. The only requirement is to have the device already installed on at least one of your USB ports (otherwise your OS won't detect it, as it will try to install the drivers, but will fail because it sees the device to be disconnecting shortly after plugging it in – at least it was my case):
1. Download Mobile Upgrade S and SP Flash
2. Grab this scatter file.
3. Open the file you just downloaded. Find the following section:
And replace is_download to true;
4. Open Flash tool and in your download section select your edited scatter file.
5. Go to Readback and select Add.
6. Double-click the added line and save it as pro_info.img
7. Set it as follows: Type : hex , Region EMMC_USER , start : 0x100000 , lenght 0x300000
8. Click Read Back, turn off your Pixi and connect it to your PC via USB cable. It should start the read immediately and after few seccond you should get a success messgae. If it's not the case, try a different USB port.
9. After you got your read, disconnect your Pixi and open newly created pro_info.img file in a hex editor.
10. Find your device version (it's soimewhere at the beggining, around adress 0xA3, and looks like XXXI213-XXXXXXX, where X can be any character, for example mine was COXI213-2DRGPL1) and change it to ENXI213-2BALGB1.
11. Replace your software version (Right after your device ver. Mine was AAZY1AAZ0Z0BD00) for AAZY1AAY0Y0BD00.
12. Save changes to your file.
13. Go back to your SP Flash tool > Download tab
14. Select your scatter file. Deselect all checkboxes. Leave PRO_INFO checked only.
15. Click on PRO_INFO location and select the file you just edited.
16. Select Download and connect your Pixi.
17. When done, run Mobile Upgrade S and follow the standard upgrading process (be aware, that it will take a lot of time to download the ROM, as the download speed goes around 20-50 KB/s. It took me aroung 8h to download it).
18. After installation run your Pixi for the first time and wait for it to boot (don't panic if it takes a bit of time. It will be booting for about 2-5 minutes for the first time).
Click to expand...
Click to collapse
Great to hear that my instructions helped you and good that you posted it here http://forum.android.com.pl/topic/211918-stock-rom-do-pixi-7/?p=3776346
KINGROOT 4.5.2 works for my pixi7 (i213)
Hi @Tzul / All,
You got me all excited when I saw you had created the custom recovery for the Lenovo Tab3... only to find out that Lenovo have another Tablet called the Tab3 that came out later this year, and it was this one that I was interested in getting.
The Tablet has a model No: ZA170136GB
Any idea if it is possible to create a custom recovery for this too?? Or does anyone know a decent Tablet in the UK for under £100, that has a Custom Recovery, and some fairly recent roms for it...
Mainly need the recovery to backup the current rom, and once I have set the Tablet up for my father, to make an image of that too...
Cheers, Lister
Hi @Tzul / All,
Just found this link, not sure if its for the same (newer Tablet) just the smaller 7" version, instead of the 8" version. But it mentions Android 6.0x which is the default OS on the newer Tablet.
https://webcache.googleusercontent....or-lenovo-tab3.html+&cd=7&hl=en&ct=clnk&gl=uk
The only thing I can't work out, is what the model number is for the newer 2016 8" model, as I've been told its "ZA170136GB" which seems a bit long... Where as most like the 7" version appears to be just "TB3-730X" and makes sense.
Cheers, Lister
Lenovo has quite a few tablets called "Tab3" / "TB3". There are at least 4 or 5 different versions of 7 inch models. Plus 8 inch and 10 inch models.
As far as I know, all of them are based on MediaTek chips, meaning if you need to create and restore backups of entire partitions, you don't even need a custom recovery, as you can use the MediaTek SmartPhone Flash Tool (SPFT) for that. However, in order to use the SPFT, you'll need a "scatter file" that matches the device in question. The scatter file contains details about the device's partitioning (start addresses, sizes, and more). You can create one manually, taking an existing one from a similar device as template, but that requires some specific knowledge and experience.
Creating a custom recovery isn't easy either, particularly if you don't have the device in question at hand. For starters, you need an existing firmware update or backup (e.g. a readback made with the SPFT), from which some required data can be extracted.
Hi @Tzul,
LOL, just found you in this thread too... spooky/small world...
https://forums.lenovo.com/t5/Lenovo...-me-unbrick-Lenovo-Tab3-850f-pls/td-p/3433458
Click to expand...
Click to collapse
Corr, they don't like to make it easy for their users... do they!!! There's even more than I first suspected then, talk about confusing!!! lol
Yeah this one I've spotted is also a MediaTek chipset too...
Does this SPFT tool belong to Lenovo/MediaTek, or apply to many different hardware configurations? Where would I obtain a Scatter file for this Tablet? I've done a bit more Google'ing, and think the unit could be a TB3-850F (although that links to an American version of the one Ive seen in the UK). Its a fairly good Tablet as it is anyway, so do you think its best just to get it anyway, and hope development / support comes for it at a later date??
Once I get the Tablet, I would be able to know what the EXACT model is for sure then... If so, is there anything I can do, in the way of dumping a rom... I believe I may of found the official rom for it on Lenovo's website earlier today at work too. So maybe able to get a rom dump that way...
If I could, do you think it would be possible to make a TWRP based on the Recovery.IMG dumped from the rom.... Or do you still need the device to actually develop and test on...??
Just wonna try get a good Tablet, that I can then create a backup/image of stock build (inc TWRP recovery) and one that I've customised App-wise for my dad to use and back that up. So if he messes it up, I can restore it quickly...
Many thanks for getting back to me so promptly, and so detailed reply.
Cheers, Lister
The SPFT software is by MediaTek and generally works with all MediaTek-based phones and tablets - provided you have a suitable scatter file.
Once you have the tablet, it should be easy to determine the exact type by going to the Android system settings, about the tablet, and check the values there; primarily model and build number. It should also be on the packaging.
I can build TWRP without owning the tablet, but it's more difficult that way as I basically have to do it "blind". I have done it for the TB3-710I, because a firmware dump was available, and someone provided me with all the info I needed. I guess I could do it for the TB3-850F as well, if I find the time and have all necessary data.
Is that the same tool that would or could be used, if ever I wish to factory reset it (if can't get TWRP onto it) or do you think Lenovo have another method, if things go really screwy?? lol
As for the model, I shall certainly be picking it up tomorrow... As I've spent many-a-days now trying to find an ideal one for my dad, and this one comes in really cheap esp for the spec. So if TWRP can go on it, it will make it an even bigger BONUS...
So will find out tomorrow what the exact model is, I'm hoping it will be a TB3-850F... As did a bit of Google'ing from the 7" model, came across that model for the 8" which appears to be exactly the same as the UK model... The website is the same, except the cpu seems to be 300mhz faster.. Im sure the UK model is 1GHz, where as they USA is 1.3GHz. Hopefully so, as that will be easier for you too I'm guessing, as it looks like you already have the Scatter file in the other forum... or at least a close template, with luck..
I'll do my best to get what ever, and as much info to you as possible... And really really appreciate any efforts you could spare to try and get TWRP on it. No worries if you can't and appreciate you're busy with other things in your life, so absolutely no rush... As said, any effort at all is really appreciated!!!
Thank you for even taking the time to read and reply to my request/info... thanks
Cheers, Lister
Hi @Tzul,
Ok, I picked the Tablet up from the shop yesterday for my dad and although we've not unboxed it yet. It is indeed the same model you appeared to be helping the use in the thread here. TB3-850F
Hopefully I'll be on it tonight, to find out more information. It appears there are at least 3 or 4 different models sold, WiFi and LTE versions, and they differ from USA to UK.
The USA version features a QuadCore 1.3 Ghz CPU
The UK vesion features a QuadCore 1.0 Ghz CPU
So not sure if that's gonna cause issues, I'll run some software on it tonight to find out the exact CPU inside it... (I have the UK version, 1.0 Ghz... if thats any use?)
I'm also gonna try ask Lenovo (not expecting a speedy response from that company, if I'm honest) to see if they have a factory restore image/tool.... Like all Samsung phones/Tablets have, and even the Tesco's Hudl. They should make it easy for end users to restore their devices, should disaster occur...
If can get a firmware dump, that may help in getting the Boot.Img and Recovery.Img in order to help make a TWRP. As that will be the preferred way of backing up and restoring the device...
How would one flash this to the Tablet, if it's possible...?? Through ADB fastboot?? What's the risk factor of BRICKING the device, outta of 100% say...? Such as Samsung have a Download Mode (which seems they are indestructible) and can always force a stock rom too them...
Cheers, Lister
I doubt that the CPU frequency differs between the US and UK version. They should be exactly the same. I wouldn't trust the info on websites. For my Tab 2 A10-70F, figures differed as well (some sources said 1.5 GHz, others 1.7 GHz; but in reality, it's 1.69 GHz).
Typically, the back of the box should list the correct specs. Does it say anything about the used MediaTek chip (MTxxxx)?
You can use the fastboot flash command to flash at least some partitions, but you might have to "unlock" the bootloader first (there should be an option in the Android developer settings). Alternatively, I can easily patch the bootloader to allow fastboot flash, but in order to install the patched bootloader, you need the SPFT or TWRP.
If you mess up something, you'll "brick" the tablet, but with the SPFT you can almost always restore the firmware.
Hi @Tzul,
Yeah, was just going via what the website says for both devices. Seems a little silly to change the builds, for different parts of the world. Prolly the same CPU and then either under or overclocked in various regions.
Just got home, and on the back of the box it says... CPU: MT8161P QC 1.0GHZ 64Bit
I'll have to wait an hour or so, as my dad is round our elderly neighbours house helping him out. But when he is back, I'll open the Tablet with him, then enable the "Android Developer Settings" through double/tapping the Build No 7x times. Once I'm in there, I assume it's "USB Debugging" you want me to enable/turn on...??
How will I know if the Bootloader is locked / unlocked? Is there a command / test, to fastboot the device and see if it responds, says anything back?? I don't know much about Fastboot, as my my flashing experience is either done through programs/utilities of via the device itself... Is there anyway to pull the Boot.Img / Recovery.Img via Fastboot?? Or is that done via that SPFT app...?
So you saying, no matter what happens/goes wrong... I can pretty much restore/recover it like Factory via the use of SPFT... There will always be a way to PUSH a firmware to the device???
I'm fully use to using Odin (not sure if you know/aware/used that App) but if SPFT is anything like that... I know that Samsung is almost indestructible via flashing with Odin... Is SPFT the same???
I'm trying to contact Lenovo to see if they have a Factory Image, or process to see if they can have a Restore Image too... That way maybe able to pull those partition from the image file??
Cheers, Lister
Lister Of Smeg said:
Just got home, and on the back of the box it says... CPU: MT8161P QC 1.0GHZ 64Bit
Click to expand...
Click to collapse
Thanks, that's what I expected. The actual CPU frequency might be 988 MHz, but rounded up it's 1.0 GHz.
Lister Of Smeg said:
Once I'm in there, I assume it's "USB Debugging" you want me to enable/turn on...??
Click to expand...
Click to collapse
USB debugging is required for ADB, which is a useful tool. But I was thinking about the option "OEM unlocking - Allow the bootloader to be unlocked", which might or might not be present in the developer menu on your tablet.
Lister Of Smeg said:
How will I know if the Bootloader is locked / unlocked? Is there a command / test, to fastboot the device and see if it responds, says anything back?? I don't know much about Fastboot, as my my flashing experience is either done through programs/utilities of via the device itself... Is there anyway to pull the Boot.Img / Recovery.Img via Fastboot?? Or is that done via that SPFT app...?
Click to expand...
Click to collapse
Strictly speaking, a locked bootloader performs integrity checks and refuses to start the system when it was tampered with. A locked system wouldn't boot an unofficial boot.img or recovery.img (such as TWRP). That's rarely the case with MediaTek-based devices, i.e. they are usually "unlocked". However, they often have the fastboot flash command restricted/disabled, meaning you can't use fastboot to flash TWRP or other stuff, until you "unlock" the bootloader, or use a patched bootloader.
To make backups of boot.img, recovery.img, etc. you can use the SPFT or a custom recovery. Or you can do it from within Android, provided you have root.
I suggest you first try this:
Open an ADB shell (USB debugging enabled, tablet running Android connected to PC via USB), or use a terminal app, then type
Code:
getprop ro.build.version.incremental
getprop ro.product.ota.model
and tell me the output. I might be able to use that information to find Lenovo's official firmware packages for your tablet.
For my TB3-710F for example, the values are ro.build.version.incremental=Lenovo_TB3-710F_S000026 and ro.product.ota.model=LenovoTB3-710F_L.
Furthermore, boot the tablet by pressing and holding power+volume_up. That should either display a little boot menu ("normal, recovery, fastboot"), or take you directly to the recovery. In the former case, choose "fastboot", in the latter case, the recovery menu should have a "reboot to bootloader" entry at the bottom.
That should take you into fastboot mode. Connect the tablet to PC via USB, and use a fastboot client to run "fastboot getvar all". That'll dump a lot of info, including partition info, which could help with creating a scatter file.
With "fastboot reboot" you can leave fastboot mode.
Lister Of Smeg said:
So you saying, no matter what happens/goes wrong... I can pretty much restore/recover it like Factory via the use of SPFT... There will always be a way to PUSH a firmware to the device???
Click to expand...
Click to collapse
Yes, if you have a complete firmware backup including scatter file.
The MediaTek SPFT is comparable to Samsung's Odin, except that it also allows to make backups (readbacks). But again, you always need a proper scatter file first. You might be interested in reading this.
Hi @Tzul,
First of all, Wow... oh WOW!!!! Are you an Android developer, as in OS specialist.... that post was epic in both detail and knowledge. Wow, you really know you're stuff... Do you work for a big company, or just a very clever/gifted hobbyist?? WOW Thanks for pointing me to that post, very interesting and giving me a heads up in the process of Lenovo architecture...
Ok, I've unboxed dad's Tablet (he doesn't know this yet... LOL). Turned it on, wow... what an experience, this is the best Android/Tablet (and we've had several over the years, from ZTE phones... to Samsung phones and HP/Tesco Hudl Tablets)... Beautiful experience!
Ok,
1) I've enabled Developer Tools (tapped Build No 7x times)
2) I've enabled [ADB Debugging]
3) I've turned on / enabled "OEM Unlocking".
Will this trigger Lenovo software to feel it's been tampered with? Or will it just be normal and allows the bootloader to passthrough / flash a modified recovery to it?
4) getprop ro.build.version.incremental = TB3-850F_S100025_160608_ROW
getprop ro.product.ota.model = LenovoTB3-850F_ROW
5) I couldn't do the Power button + Holding Volume Up button, as when holding both down... The Tablet keeps rebooting, and not loading anything up other than the Lenovo logo, then reboots again...
So I tried Power button + Holding Volume Down button, and it appears to show a menu... But it was ALL in Chinese, other than the word eMMC. I had no idea how to get out of it, other than holding "Vol Up and Power button" as I found from previous, it just boots/reboots loop until let go. I did so, then it said something about SD.. and the rest in Chinese and made a loud beep, before rebooting...
So not sure if I've done anything to an SD Card, internal...?? As we've not put in an external one yet...
So not sure how to get into Bootloader / Recovery yet? As it keeps restarting...
Interestingly, when I first turned this device on and connected it to the network, it wants to pull down a small update....
TB3-850F_S100025_160608_ROW_TO_TB3-850F_S100026_160923_ROW
What it currently is...
What it wants to go too...
The update is only 22Mb in size....
I hope this helps?
Cheers, Lister
My job doesn't really involve Android, but I've studied this, more or less.
Glad to hear that the tablet is good. I'm still satisfied with my Tab 2 as well.
Lister Of Smeg said:
3) I've turned on / enabled "OEM Unlocking".
Will this trigger Lenovo software to feel it's been tampered with? Or will it just be normal and allows the bootloader to passthrough / flash a modified recovery to it?
Click to expand...
Click to collapse
The latter, as far as I know.
Thanks for the property values. With those, I could find the small update you mentioned. Unfortunately it doesn't contain a complete boot.img file, but at least it contains a barebones scatter file (just the partition start addresses):
Code:
preloader 0x0
pgpt 0x0
proinfo 0x80000
nvram 0x380000
protect1 0x880000
protect2 0x1280000
lk 0x1c80000
para 0x1d00000
boot 0x1d80000
recovery 0x2d80000
logo 0x3d80000
expdb 0x4580000
seccfg 0x4f80000
oemkeystore 0x5000000
secro 0x5200000
keystore 0x5800000
tee1 0x6000000
tee2 0x6500000
frp 0x6a00000
nvdata 0x6b00000
metadata 0x8b00000
system 0xb000000
cache 0xcb000000
userdata 0xe5800000
flashinfo 0xFFFF0084
sgpt 0xFFFF0004
Exactly the same values I used for the preliminary scatter file that you found on the Lenovo forums.
If you like, you can try to use it with the SPFT to make a readback.
Download the latest SPFT, unzip it, find its "option.ini" file, open it, and at the very end change "ShowByScatter=false" to "ShowByScatter=true".
Download and install the USB Preloader driver (cdc-acm).
Finally, run the SPFT, load my scatter file, and make a readback.
Lister Of Smeg said:
5) I couldn't do the Power button + Holding Volume Up button, as when holding both down... The Tablet keeps rebooting, and not loading anything up other than the Lenovo logo, then reboots again...
Click to expand...
Click to collapse
If you hold down the power button for too long, the tablet will probably reboot.
Try this: Shut down the tablet. Hold volume up, then hold power. When the screen turns on, release the power button, but keep holding volume up.
That should take you to the boot menu or recovery. If not, you can still try to get there via "adb reboot recovery" or "adb reboot-bootloader" (for fastboot).
Lister Of Smeg said:
So I tried Power button + Holding Volume Down button, and it appears to show a menu... But it was ALL in Chinese, other than the word eMMC. I had no idea how to get out of it, other than holding "Vol Up and Power button" as I found from previous, it just boots/reboots loop until let go. I did so, then it said something about SD.. and the rest in Chinese and made a loud beep, before rebooting...
Click to expand...
Click to collapse
Yeah, on these MediaTek-based devices, that key combination usually takes you to the factory test menu. Avoid going there, you could mess something up.
The bottom-most menu entry gets you out of there (reboot). The menu entry with "eMMC" is "wipe eMMC" - sounds as if it would delete the entire internal flash memory (the eMMC chip), but in actuality, it just does as factory reset, i.e. it only wipes the /data partition (where all user apps and settings are stored). At least it's like that on every device I've tested so far.
Hi @Tzul,
Well, ya certainly know what ya talking about... was a great read. I am technically minded. I do (and have done for about 15/20 years) IT Support. I understand the talk, sometimes we all gotta re-learn new tricks...
Ok, you'll love this... I spoke to Lenovo today... Actually very good support really, much better than when we phone up about PCs not working in our company. Anyway, they were still unable to help me with the Tablet.
I spoke to them about not being able to get into Recovery / Bootloader. Didnt tell them why of course, but explained that I wanted to know if there was an official firmware I could download if I wished to return the Tablet to fully stock without any Apps. Blamed my dad messing it up, which is kinda true... even though he has not touched it yet. Anyway, they talked me through many things, BASICALLY WHAT YOU'VE ALREADY TOLD ME.... About holding down Vol Up and Power button. After many attempts, still not working. So I said there is a 22mb update pending, I'll try that and see if that allows me to do the key combo... Still no joy. He told me to do a factory reset in the Android OS (which I knew anyway). And so did that, and sure enough it wiped everything, even Developer Settings. However after re-enabling it again, the OEM Bootloader was STILL UNLOCKED? lol.
Anyway, needless to say... I still cannot get into recovery on this device, and he seems certain I should be able too. He thinks the device may be faulty, and suggests returning it... Apart from not being able to get into Recovery, I dont think it is faulty as seems fine everywhere else.
I also tried "Lenovo Smart Assistant" as it seems that can download firmware from there site. After spending a couple of hours trying to get all the (10x different Android device drivers installs, MTP, ADB, MIDI, blah blah) it still didnt automatically detect in their Smart App. So I tried to select the "Dead Device" mode, where you have to enter "Model No" and Hardware ID, typed in various things... but neither showed up the Tablet??? lol
Anyway, going back to above....
1) Installed the suggested signed drivers for the PreLoader
2) Downloaded, edited Options.ini and ran the latest SPFT
3) Opened the Scatter file, nice to see all the partitions.
4) Tried to do a ReadBack of just Boot.img and Recovery.img but nothing downloaded or seemed to happen. But was doing this in a hurry on my lunch break. Shall have another go at home, or back at work tomorrow.
Ah, think I've seen where I went wrong... I didnt double click on the [File] column. I just assumed the path was already correct, looking at it. Also, can't remember the state of the device, think that was also on at the time. So will have a proper go later... and upload the boot.img and recovery.img
-- Just out of interest, if I was making a STOCK ROM backup. What partitions do I need to select / include / tick, for that??
And assume if I wanted to restore it, just do the exact same. Select the partitions, select the files in the [File] tab as to what I want to restore and use DOWNLOAD only mode? Or would it be best just to make the backups in TWRP once/if it's possible...??
As I'm having no joy with the key combo, I'm gonna try the ADB commands in a sec, and let you know how those go....
Yeah, I wont be going there again in a hurry... Didnt have a clue what any of it was, and it wasn't clear at the time how to get out of it either... Sadly I selected the very first open, no idea what that was / is ???? but couldn't get out of it either and had to wait till it finished...
I saw eMMC and panicked, as I have 3x Samsung devices that all suffer from the eMMC brickbug issue. Where the chip dies if using a faulty kernel. Thankfully this kernel is all but disappeared, as only came about in an official LEAKED Samsung build. And all previous/after official kernels and all custom kernels had this faulty switch removed... But whenever I see eMMC, I worry now... lol
Many thanks, Lister
Hi @Tzul,
Well, after my chat to Lenovo and doing some more testing last night... I think my Tablet could be genuinely faulty...
You know I said how I can't enter Recovery (Power & Vol Up) despite you and Lenovo saying that it should work. Well Lenovo think and said it could be faulty and return to place of purchase.
I tried the ADB commands last night, the Reboot Bootloader worked and sent me into Fastboot. However the Reboot Recovery gives me this error...
{
"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"
}
Which I am wondering if I don't have a Recovery or it's corrupted...??
I am also failing to get those ReadBacks of either Boot.img or Recovery.img, as depsite having the Tablet off and clicking on the file names, and pointing it where to save. Nothing appears to happen, no data transfers...??
Do you think I'll be able to get those files if I root the device, and use a Root File Manager???
Also, without any official firmware from Lenovo yet... If I root it, will I be able to unroot it by just doing a simple "Factory Reset" within Android OS, or does this keep the root do you know?? Never really used Factory Reset, as always wipe the device in a custom recovery....
Cheers, Lister
Lister Of Smeg said:
You know I said how I can't enter Recovery (Power & Vol Up) despite you and Lenovo saying that it should work. Well Lenovo think and said it could be faulty and return to place of purchase.
Click to expand...
Click to collapse
That sounds quite unlikely to me. Have you tried what I wrote before? Start holding the volume up button before you turn on the tablet. Then press the power button to turn it on, release the power button again, but keep holding volume up all the time.
Lister Of Smeg said:
I tried the ADB commands last night, the Reboot Bootloader worked and sent me into Fastboot. However the Reboot Recovery gives me this error...
Click to expand...
Click to collapse
That's not an error, that is in fact the stock recovery! The menu is missing, but that's normal for some devices. There's a "secret" key combination you need to press to activate the menu. Try power+volume up again (or to be more specific, hold down the power button, then "click" the volume up button, then release the power button; do not hold down the power button for 10 seconds or longer, that'll probably reboot the tablet).
Lister Of Smeg said:
I am also failing to get those ReadBacks of either Boot.img or Recovery.img, as depsite having the Tablet off and clicking on the file names, and pointing it where to save. Nothing appears to happen, no data transfers...??
Click to expand...
Click to collapse
Are you sure you're doing everything correctly? When the tablet is off and you connect it to the PC via USB, Windows should play the "USB device connected" sound effect, quickly followed by the "USB device disconnected" sound effect. Take a look at the Windows device manager - the Preloader VCOM device should appear there for this brief period, and it must not have a warning triangle (that would be a sign of missing drivers).
Lister Of Smeg said:
Do you think I'll be able to get those files if I root the device, and use a Root File Manager???
Click to expand...
Click to collapse
Yes, that should work, BUT I would not advise it. Looking at the update file, I saw it uses the newer block-based format. That means if you change the system partition in any minor way, e.g. by installing root / su binaries there, future updates will fail! Therefore, you shouldn't do anything that could modify the system partition (installing root, or even running TWRP), until you have a backup of the original state.
Lister Of Smeg said:
Also, without any official firmware from Lenovo yet... If I root it, will I be able to unroot it by just doing a simple "Factory Reset" within Android OS, or does this keep the root do you know?? Never really used Factory Reset, as always wipe the device in a custom recovery....
Click to expand...
Click to collapse
No, a factory reset will not unroot! Root is either installed on the system partition (the old way), which Android considers read-only, or it is installed in a modified boot.img (the new way), which also won't be touched by Android. A factory reset, regardless whether performed by Android or a custom recovery, just wipes the data and cache partitions.
That sounds quite unlikely to me. Have you tried what I wrote before? Start holding the volume up button before you turn on the tablet. Then press the power button to turn it on, release the power button again, but keep holding volume up all the time.
Click to expand...
Click to collapse
Yes, I tried that... no matter what order/process I take. It each ends up in the same result. I did the holding of the Vol Up, then pressing Power (waited it for it to Vibrate, before letting go of Power... as instructed by Lenovo tech Support) and still would not get past the white screen, with Lenovo logo.
That's not an error, that is in fact the stock recovery! The menu is missing, but that's normal for some devices. There's a "secret" key combination you need to press to activate the menu. Try power+volume up again (or to be more specific, hold down the power button, then "click" the volume up button, then release the power button; do not hold down the power button for 10 seconds or longer, that'll probably reboot the tablet).
Click to expand...
Click to collapse
I thought that was recovery, as I've seen the ill looking Android collapse on other Android devices when a flash has failed, but normally I see more of a menu... Like to Apply Update (I guess official internal OS updats). I shall try that trick in a second, to see if I can get the menu to appear. May have to do it at home, as I know ADB app sends our works AV to thinking its a virus, when it's safe... lol
Are you sure you're doing everything correctly? When the tablet is off and you connect it to the PC via USB, Windows should play the "USB device connected" sound effect, quickly followed by the "USB device disconnected" sound effect. Take a look at the Windows device manager - the Preloader VCOM device should appear there for this brief period, and it must not have a warning triangle (that would be a sign of missing drivers).
Click to expand...
Click to collapse
The drivers installed correctly here (work, running Windows 10 x64), all went smoothly. When I plugged the Tablet in, it came up saying something about PreLoader driver... However at home, the drivers failed... But that could be my old screwy build of Windows 7x x64.... So gonna try again at work for that part.
Yes, that should work, BUT I would not advise it. Looking at the update file, I saw it uses the newer block-based format. That means if you change the system partition in any minor way, e.g. by installing root / su binaries there, future updates will fail! Therefore, you shouldn't do anything that could modify the system partition (installing root, or even running TWRP), until you have a backup of the original state.
Click to expand...
Click to collapse
Oh great, terrific... So I gotta be extra careful then!! lol. No rooting or mods until at least I can pull this ReadBack backup off... Oh I do love my Xposed!!
So once I've got my first official ReadBack backup, with no mods or alterations. Then I'm safe to do whatever...??
Providing I've got my first ReadBack before I do anything, if we are able to get TWRP into the Recovery Partition of the Tablet. Will this TWRP Recovery affect /System and OTA updates?? or is that only the Recovery partition affected, and System will stay intact??
Also, once (or, IF) I have TWRP, could I do a full system backup there. Prior to any mods, and can fully restore to stock (with the addition of TWRP recovery and not Stock) via the TWRP Recovery then... As wonna get an as close to stock backup as poss in TWRP. And then a fully setup with all the Apps, Mods, Tweaks and root Apps setup and then back that up. I assume I can always restore to the first TWRP backup without root at a later.
/ If any of that ^ makes sense? lol
No, a factory reset will not unroot! Root is either installed on the system partition (the old way), which Android considers read-only, or it is installed in a modified boot.img (the new way), which also won't be touched by Android. A factory reset, regardless whether performed by Android or a custom recovery, just wipes the data and cache partitions.
Click to expand...
Click to collapse
Fair enough, I kinda assumed that a Factory Reset within the Android OS will keep the root, and only wipe user added data, such as Apps, Pictures, Music, Files... and anything added to the /System would be left behind. My old devices (N7000 and i9100) only use the old way at the moment for rooting, as in writing to the system partition. When trying to use the new Boot.img way (as in Systemless root) causes both devices to crash, as they don't have the pre-modded Boot.img yet.
But assuming if I made a previous backup of the whole Tablet in TWRP before rooting (or do I need root, to push TWRP). Then go onto root the Tablet afterwards, if I then restore the Tablet to the first pre-root backup in TWRP will over write the root files back to stock??
/ sorry for all the questions, and what-if's.... ? I understand Android, and fully know my Samsung models inside out... Just not sure when it comes to Lenovo, as it seems to use a different structure, and partition layout. And at moment, till I get my head around it, seem as stable/fool-proof in not making non-changeable choices, that can be corrected at a later date. Just it's my dads Tablet, and don't want to mess anything up as yet... As I'll prolly have to buy it off him lol
Anyway, thanks for your continued help on this.... I'll let you know how I get on...
Cheers, Lister
Lister Of Smeg said:
The drivers installed correctly here (work, running Windows 10 x64), all went smoothly. When I plugged the Tablet in, it came up saying something about PreLoader driver... However at home, the drivers failed... But that could be my old screwy build of Windows 7x x64.... So gonna try again at work for that part.
Click to expand...
Click to collapse
The driver I linked can be installed with a simple right-click in Windows 8 and later. But in Windows 7, the installation procedure is more involved, as described in the included readme.
Lister Of Smeg said:
Oh great, terrific... So I gotta be extra careful then!! lol. No rooting or mods until at least I can pull this ReadBack backup off... Oh I do love my Xposed!!
So once I've got my first official ReadBack backup, with no mods or alterations. Then I'm safe to do whatever...??
Click to expand...
Click to collapse
Yes, if you get the SPFT to work with your tablet, you can make a backup and restore it anytime you want.
Lister Of Smeg said:
Providing I've got my first ReadBack before I do anything, if we are able to get TWRP into the Recovery Partition of the Tablet. Will this TWRP Recovery affect /System and OTA updates?? or is that only the Recovery partition affected, and System will stay intact??
Click to expand...
Click to collapse
The first time you run TWRP, it asks you whether or not you'd like to allow changes to the system partition. If you choose yes, TWRP will rename a certain system file on exit, and will also offer to install a SuperSU stub for root. You see, Android has a mechanism that restores the stock recovery on every Android boot! Therefore, TWRP will be automatically replaced by the stock recovery again, unless you allow TWRP to rename that file, or install SuperSU. Both these things will intentionally break that Android restore mechanism.
On your tablet, you should probably forbid TWRP to make those changes. But even if you do, other things in TWRP can still change the system partition regardless. Installing the zip files for Xposed or SuperSU, for example. Or even restoring a TWRP backup of the system partition (because they are file based, but a block-based update doesn't just care about the file contents, but also about where exactly the files are located on the partition/disk, which will change with a file-based restore).
That's why "systemless" Root and Xposed are a thing these days. They don't install the files to the system partition anymore like they used to, but somewhere else (the ramdisk of the boot image, as far as I know), and use some trickery to make the files appear in the filesystem where they are expected.
Concerning OTA updates: they will fail if the system partition was modified. So if you want to install one, you either have to roll back to an unmodified system and stock recovery, then install the update, then install root, Xposed, etc. again (tedious). Or you can modify the updater-script inside the update, and make it work with modified systems, then install the adjusted update with TWRP. But that requires know-how and will only work with the old file-based updates, not the new block-based ones.
Lister Of Smeg said:
Also, once (or, IF) I have TWRP, could I do a full system backup there.
Click to expand...
Click to collapse
No. As just mentioned, TWRP backs up the files (their content), which is not enough for block level accuracy. You need a system image backup. Which can also be made with TWRP, if it has been configured properly.
Lister Of Smeg said:
But assuming if I made a previous backup of the whole Tablet in TWRP before rooting (or do I need root, to push TWRP). Then go onto root the Tablet afterwards, if I then restore the Tablet to the first pre-root backup in TWRP will over write the root files back to stock??
Click to expand...
Click to collapse
Yes, but again, you need to backup and restore the system image (the entire partition, including "empty" space, not just the files as TWRP normally does).
Lister Of Smeg said:
/ sorry for all the questions, and what-if's.... ? I understand Android, and fully know my Samsung models inside out... Just not sure when it comes to Lenovo, as it seems to use a different structure, and partition layout. And at moment, till I get my head around it, seem as stable/fool-proof in not making non-changeable choices, that can be corrected at a later date. Just it's my dads Tablet, and don't want to mess anything up as yet... As I'll prolly have to buy it off him lol
Click to expand...
Click to collapse
It has nothing to do with Samsung vs. Lenovo. It's about the chipset - MediaTek in your case. A Lenovo device with a Qualcomm chip, for example, will have a different partition layout and obviously won't work with the SPFT. And most of the things I just talked about (file-based vs. block-based updates, the "sanctity" of the system partition, etc.) are general Android things and not specific to the chipset.
Hi @Tzul,
Ok, slowly making progress here... Yippie!! lol
Still can't enter recovery via hardware buttons... No matter how many times I try, and in whatever order and timing. I even tried holding Power & Vol Up, then when it FREEZES on white screen with Lenovo logo. Then tried releasing Vol Up also, and then holding it down again... like how to reveal 'Secret Menu'. But still nothing appears for recovery!!
However, that said... I am now able to enter Recovery... via using ADB Fastboot Recovery, then using those key combo commands to reveal the secret menu. Which that all now works, and get a full list of options to choose from there... So thank you for that!!
I've had another go at trying to install PreLoader driver again on my home PC (Win7 x64) and it now appears to do something, more than previously done... But errors, and still does not pull those files. Maybe you might be able to see where going wrong via the screenshot??
Yes, if you get the SPFT to work with your tablet, you can make a backup and restore it anytime you want.
Click to expand...
Click to collapse
Once I get this App working, and working reliably... I think I'd feel a lot more comfortable and happier, knowing I have a decent back up to rely on. Just this App is new to me, and at moment (with difficulties of entering Recovery and getting this App to work). Where as comparison to Odin. Just have to put phone into Download Mode, add the Firmware File... and thats it. By the looks of things, this App is very very similar. Just with its hit/miss at moment, till I've ironed out why its not working... Just want to know I have STOCK rom to return too, in aid of firmware updates.
Concerning OTA updates: they will fail if the system partition was modified. So if you want to install one, you either have to roll back to an unmodified system and stock recovery, then install the update, then install root, Xposed, etc. again (tedious). Or you can modify the updater-script inside the update, and make it work with modified systems, then install the adjusted update with TWRP. But that requires know-how and will only work with the old file-based updates, not the new block-based ones.
Click to expand...
Click to collapse
I've seen TWRP (more specifically, TWRP 3.x) mention about allowing System modifications with my Samsung device. I think in the past, I've answered both ways... Allow / Do Not Allow when switching Roms every so often.
So basically it's a toss up of whats more important...? Receiving OTA updates, or running Root on the device. As long as I can get this first initial ReadBack backup, then should be happy either way... As can always restore back to fully STOCK, run the update, then flash TWRP and Root apps again??
No. As just mentioned, TWRP backs up the files (their content), which is not enough for block level accuracy. You need a system image backup. Which can also be made with TWRP, if it has been configured properly.
Click to expand...
Click to collapse
Will have a look on my current Samsung / TWRP about making full system based images. But that said, I still won't receive OTA updates restoring back to this way, as already modified the device/OS with TWRP... preventing this. But could be quicker/easier way to return to STOCK (minus updates). And this would be safe to do, based on the BLOCK BASED partition on this device? (Only ever been used to FILE BASED twrp backups).
It has nothing to do with Samsung vs. Lenovo. It's about the chipset - MediaTek in your case. A Lenovo device with a Qualcomm chip, for example, will have a different partition layout and obviously won't work with the SPFT. And most of the things I just talked about (file-based vs. block-based updates, the "sanctity" of the system partition, etc.) are general Android things and not specific to the chipset.
Click to expand...
Click to collapse
Yeah I hear you on Samsung vs Lenovo, being Exynos vs MediaTek... What I mean't, is I'm just more used too and comfortable with the way things work on Samsung. I know (so far... lol) that I can never really brick my Samsung devices (other than the leaked ICS kernel) as I can restore fully with STOCK rom in Odin. And that all my devices (Samsung, HP Touchpad, ZTE Blade) all use partitions one way or another... as it was a curve to learn Samsung shares Recovery with its Kernel and vice versa... Where as the Blade, they were both separated... I'll get there slowly with MediaTek devices... lol... But most of all, I thank you, for all your time, patience and support guiding me along this way... MUCH APPRECIATED!!!
Edit: I am amazed that Lenovo don't have anything public on their website regarding firmware, to allow customers to restore themselves. I've downloaded their "Lenovo Smart Assistant" App which is supposed to support phones and Tablets. But does not detect mine, either alive or dead mode. When searching for it within the App, nothing shows for it either... Or the Tab2 family either..?? May try another cheeky online chat support call to them again, see if they can release anything firmware wise lol
Many thanks, Lister
Lister Of Smeg said:
I've had another go at trying to install PreLoader driver again on my home PC (Win7 x64) and it now appears to do something, more than previously done... But errors, and still does not pull those files. Maybe you might be able to see where going wrong via the screenshot??
Click to expand...
Click to collapse
That's the same error the other person on the Lenovo forum had. I have a feeling that the driver isn't installed correctly. Have you looked at the Windows device manager, Ports (Com & LPT) section? Does a new device appear there after connecting the powered-off tablet, and does that device NOT have a warning triangle?
Maybe you could try the SPFT on a Windows 8 or 10 machine, where the signed driver can be installed with the simple right-click method. Otherwise, you could find an install an unsigned driver for Windows 7, and try again. Maybe this error is also caused by an incorrect scatter file, wrong download agent, or bug in the specific SPFT version. You could try an older version such as v5.1516. Here's someone who encountered the same error and "fixed" it by using this older version and a slower PC...
Lister Of Smeg said:
So basically it's a toss up of whats more important...? Receiving OTA updates, or running Root on the device. As long as I can get this first initial ReadBack backup, then should be happy either way... As can always restore back to fully STOCK, run the update, then flash TWRP and Root apps again??
Click to expand...
Click to collapse
Yes. You should probably go with systemless root on this tablet, but whether the system or boot image get modified, an OTA update will fail either way if it does integrity checks. So there's no way around making backups of the untouched partitions and restoring them when necessary.
Lister Of Smeg said:
Will have a look on my current Samsung / TWRP about making full system based images. But that said, I still won't receive OTA updates restoring back to this way, as already modified the device/OS with TWRP... preventing this. But could be quicker/easier way to return to STOCK (minus updates). And this would be safe to do, based on the BLOCK BASED partition on this device? (Only ever been used to FILE BASED twrp backups).
Click to expand...
Click to collapse
That option might or might not exist in your Samsung's TWRP. Usually, newer TWRPs are configured to have a "System Image" entry in the Install -> Install Image partition list, so that it is possible to flash a system.img file easily from within TWRP. This same "System Image" entry can also be made visible in the Backup/Restore partition list, but normally it isn't.
Lister Of Smeg said:
I am amazed that Lenovo don't have anything public on their website regarding firmware, to allow customers to restore themselves. I've downloaded their "Lenovo Smart Assistant" App which is supposed to support phones and Tablets. But does not detect mine, either alive or dead mode. When searching for it within the App, nothing shows for it either... Or the Tab2 family either..?? May try another cheeky online chat support call to them again, see if they can release anything firmware wise lol
Many thanks, Lister
Click to expand...
Click to collapse
Well, you're not supposed to mess with these devices. Only a fraction of users install root or Xposed anyway. I've never tried the "Lenovo Smart Assistant", so I can't say anything about that.
Anyway, you're welcome.
Hi @Tzul,
Still not having any luck with this... Boo-hoo.... As below, is what happened and what I've tried..
Tzul said:
That's the same error the other person on the Lenovo forum had. I have a feeling that the driver isn't installed correctly. Have you looked at the Windows device manager, Ports (Com & LPT) section? Does a new device appear there after connecting the powered-off tablet, and does that device NOT have a warning triangle?
Maybe you could try the SPFT on a Windows 8 or 10 machine, where the signed driver can be installed with the simple right-click method. Otherwise, you could find an install an unsigned driver for Windows 7, and try again. Maybe this error is also caused by an incorrect scatter file, wrong download agent, or bug in the specific SPFT version. You could try an older version such as v5.1516. Here's someone who encountered the same error and "fixed" it by using this older version and a slower PC...
Click to expand...
Click to collapse
Installed at home, old dual core computer running Windows 7 x64. Installed driver as per instructions (Installed to Com18 port). On first install, it shows a new device with yellow explanation mark. So I delete the device, but keep the driver software files installed. Same error...
At work, Quad Core i5 running Windows 10 x64. Installed the driver using Right Click / Install option... Driver installs fine, no errors (Installed to Com15 port). Same error.
Tried with the very latest version of SPFT, and with the other older version as quoted on that website. At first the older one wouldnt show the partition on ReadBack mode, even with the ScatterFile=true remark at the end. So I just copied contents out of one of the other option.ini files and then it did. But still no joy. Tried various versions of SPFT (not all of them, will do some more tonight). Tried different USB cables, including the original official one at of the box.
Only thing not tried, finding a really really old computer...
Tzul said:
Yes. You should probably go with systemless root on this tablet, but whether the system or boot image get modified, an OTA update will fail either way if it does integrity checks. So there's no way around making backups of the untouched partitions and restoring them when necessary.
Click to expand...
Click to collapse
I'm assuming there will never be a Systemless root for this device. As that requires someone to mod the Boot.img. And other than your good self, not seen anyone else offer support (or even use) this device, and I can't expect you to do that. Not to mention, can't even get the files off or access a firmware file for it.
I was hoping if I could get a STOCK firmware of backup of this device. Then if there was news of an update coming out. I could reflash back to STOCK, loosing all my mods and changes. Just to get the update, then attempt to re-root and tweak again... Gonna be a cat-n-mouse game me thinks... If I can ever get this backup to work in the first place...?? lol
Tzul said:
That option might or might not exist in your Samsung's TWRP. Usually, newer TWRPs are configured to have a "System Image" entry in the Install -> Install Image partition list, so that it is possible to flash a system.img file easily from within TWRP. This same "System Image" entry can also be made visible in the Backup/Restore partition list, but normally it isn't.
Click to expand...
Click to collapse
Didnt get chance to check TWRP last night on Samsung devices, by time I went to bed... was too knackered and straight asleep... lol. Will check tonight...
Tzul said:
Well, you're not supposed to mess with these devices. Only a fraction of users install root or Xposed anyway. I've never tried the "Lenovo Smart Assistant", so I can't say anything about that.
Anyway, you're welcome.
Click to expand...
Click to collapse
No, it appears your not... I tried to speak to Lenovo again today... (sob story... Need to access a backup firmware in case Tablet dies under dads use, which is not too far from the truth...) However he was under the impression I could restore fully to STOCK if I access the Recovery (which I told him only works via ADB commands. He suggested again I should take it back to shop and get it replaced).
Anyway, I said... So does that mean the Lenovo Tablet has a hidden recovery image / rom / partition. And that if I was to "root the device, in order to make some Apps/Tweaks work" I could enter Recovery, and run the recovery option in the hidden menu and restore Tablet back to STOCK.
To which sadly I had to go back to work, and told him this. I said if he could leave me the reply, I'd check when back. Which he then said, "If the Tablet is rooted, it will then delete the recovery partition, meaning no recovery would be possible" which to me sounds a little far fetched... that rooting will actually DELETE a hidden recovery image/partition???
I'm sadly starting to think, have I picked the wrong device for my dad?? Same as with all mine, and what I did for my mums... I was able to install custom recovery easily. Especially in the case of my mum's Tesco's Hudl, I set it all up with STOCK rom (as there are no custom roms), however there is custom recovery which I flashed, rooted, and installed all rooted Apps. However, I have since been able to reflash it back to fully STOCK without any Root, and able to go back and fourth as often as like without fear of bricking, or potentially damaging any future updates/recovery....
Gonna try a few more times to get this to recognise and accept SPFT backing/restoring... Otherwise next week, I may consider taking back to the shops. Pity, as the Tablet itself is seems really nice so far (even though barely used it yet). But just worried cannot make backup images, or can easily break Updates/Stock Restoring....
Cheers, Lister
Hi folks,
Today it's a great day for me : I have successfully patched the kernel to have a 100% working TWRP 3.2.1 for our Maze Alpha 4G.
I have port a Jemmini build for Bluboo S1 and I have patch the kernel to have a working touch panel
I have followed this Thead
For the Maze Alpha 6G version, you can test it and tell me please.
How to flash:
I Fastboot method (must unlock device) :
1- Reboot your phone in bootloader mode : adb reboot bootloader or phone off, press and hold at the same time POWER and Vol+ buttons
2- Connect your phone to your computer with adb/fastboot already installed
3- Unlock your bootloader : fastboot oem unlock (it will erase you data, only data)
4- Flash the recovery : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
II SPFlashTool method (no need to unlock device) :
1- Download latest version of SPFlashTools.
2- Execute it and load the provided scatter (the recovery image must be in the same folder as the scatter and must be renamed to recovery.img) then press "Dowbload" button
3a- windows SPFlashTools users : phone off, press VOL+ and connect it to your PC (running SPFlashTool and waiting for phone connetion)
3b- linux SPFlashTools users : phone off and connected to PC , press VOL+ and POWER while your PC is running SPFlashTool (with sudo) and waiting for phone connetion.
Update : you can found here the latest version: TWRP 3.3.0 for MAze Alpha 4Ghttps://github.com/dreambo/android_device_maze_alpha/releases/tag/3.3.0
have a nice day.
Works great on Maze alpha 4G. Thanks.
But I forgot to save original recovery...
super_sonic said:
Works great on Maze alpha 4G. Thanks.
But I forgot to save original recovery...
Click to expand...
Click to collapse
You can get the original recovery from the stock rom designed for SPFlashTool, provided here
dreambo said:
You can get the original recovery from the stock rom designed for SPFlashTool, provided here
Click to expand...
Click to collapse
Thanks. Can you share stock recovery.img, if you have it? I have recovery-verified.img from V05 but I don't know if there is a new update and if size is correct: 11,54MB. Your TWRP recovery has got a size of 14.24MB...
Can you make a small procedure on how to install it? Will help many nOOb's out.
And people need to report back issues and successes !!!! Again I see many questions and people with issues that we seniors try to help out with that end up in no more response which to me is not done and not helping others.
I have a 6GB version that I could test on but at the moment I am using it for other stuff and I can't risk bricking it this week.
Would finally love to start some stuff happening on this phone.
Ok in the process of doing so on my 6GB/64GB version.
edit : congratz I now have a 'phone' that can only go into TWRP . Should have never ever done this!
Says no OS installed ... really nice
Edit 2: after hours wasted was able to get your zipped rom on the Maze but I got no boot with that TWRP, so flashed recovery-verified.img from the 6GB rom from Alpha I had downloaded ... It would then start up but show 4GB out of 6GB. No good but at least all the rest seemed to work. All other effort to get it going back with the proper kernel etc resulted in frustration.
So now to flash the official rom back via their tool... that one got me really frustrated and was completely my fault that I couldn't figure it out. But you know angry, frustrated, must get it back to work, can do this ... After all these years of toying with phones we are so used to pressing 'power and vol+ or vol-' together to make something work. Now in the end I re-read the manual again and saw that you only have to push vol+ and NOT vol+ and power together or it wont go in the mode it should go to make it flash!!
In case this happens : The best advice I can give to people is to download the proper MTK drivers. Search for vcom drivers for MTK and you will find.
Print out the instructions and mark every step you do to the letter. The flashing itself only takes like 3 or 4 minutes
lukesan said:
Ok in the process of doing so on my 6GB/64GB version.
edit : congratz I now have a 'phone' that can only go into TWRP . Should have never ever done this!
Says no OS installed ... really nice
Edit 2: after hours wasted was able to get your zipped rom on the Maze but I got no boot with that TWRP, so flashed recovery-verified.img from the 6GB rom from Alpha I had downloaded ... It would then start up but show 4GB out of 6GB. No good but at least all the rest seemed to work. All other effort to get it going back with the proper kernel etc resulted in frustration.
So now to flash the official rom back via their tool... that one got me really frustrated and was completely my fault that I couldn't figure it out. But you know angry, frustrated, must get it back to work, can do this ... After all these years of toying with phones we are so used to pressing 'power and vol+ or vol-' together to make something work. Now in the end I re-read the manual again and saw that you only have to push vol+ and NOT vol+ and power together or it wont go in the mode it should go to make it flash!!
In case this happens : The best advice I can give to people is to download the proper MTK drivers. Search for vcom drivers for MTK and you will find.
Print out the instructions and mark every step you do to the letter. The flashing itself only takes like 3 or 4 minutes
Click to expand...
Click to collapse
Haha I did the same exact thing..and managed to get it working after flashing it with the spflash tool but the trick is if you have Windows 10 latest version you won't be able to do this..at least I couldn't because of driver incompatibility so in my case:
1 I installed Windows 7 and installed mtk drivers for spflash tool
2.booted into twrp
2.1 if you can't boot into twrp or it doesn't turn on you can still try this
3.Start sp flash tool and download the zip the one(in case of trouble)that the moderator published
4. Load the scatter file and make sure that all of the files and the scatter are in the same folder.
5.click download and leave it like that
6.plug in your phone in fastboot if you can't try one of the following
6.1 just plug it in turned off and monitor spflash tool status
6.2 plug it in holding volume up key (just volume not power)
6.3 in twrp go to boot and boot into bootloader
And the tool should do the rest
If all else fails check the drivers one more time
After all that if you are feeling adventurous flash twrp one more time and do not factory reset through twrp ! Because that was the problem in my case and after you unlock bootloader boot your phone and go through the setup without setting the password because twrp will be locked.
Good luck.
frumac96 said:
Haha I did the same exact thing..and managed to get it working after flashing it with the spflash tool but the trick is if you have Windows 10 latest version you won't be able to do this..at least I couldn't because of driver incompatibility so in my case:
1 I installed Windows 7 and installed mtk drivers for spflash tool
2.booted into twrp
2.1 if you can't boot into twrp or it doesn't turn on you can still try this
3.Start sp flash tool and download the zip the one(in case of trouble)that the moderator published
4. Load the scatter file and make sure that all of the files and the scatter are in the same folder.
5.click download and leave it like that
6.plug in your phone in fastboot if you can't try one of the following
6.1 just plug it in turned off and monitor spflash tool status
6.2 plug it in holding volume up key (just volume not power)
6.3 in twrp go to boot and boot into bootloader
And the tool should do the rest
If all else fails check the drivers one more time
After all that if you are feeling adventurous flash twrp one more time and do not factory reset through twrp ! Because that was the problem in my case and after you unlock bootloader boot your phone and go through the setup without setting the password because twrp will be locked.
Good luck.
Click to expand...
Click to collapse
Wait a sec., missing a couple of things here.
1) Do you have a 6GB ?
2) In case you have a 6GB did you manage to get it working, rooted and all?
Your point 6) well I flashed mine on the latest 64bit win10 ... but.... if the phone is off and you connect the usb cable my phone tried to boot up either in twrp with no com port. Also booting it in bootloader doesn't make the comport visible so you can't flash.
The only way to make mine visible for the flashtool was to press vol+ and then connect the usb cable.
Btw I am glad someone finally responds and spreads information. A very good post! Your first 'thanks' well deserved!
I wonder where the guys are that I was trying to help. Did they throw their phones away or something? Sharing is caring I thought.
I want to root mine to alter the camera settings and the media xml file. I find it strange that our sensor, which is the same as in my wife's Xiaomi's, takes seriously bad pictures.
lukesan said:
Wait a sec., missing a couple of things here.
1) Do you have a 6GB ?
2) In case you have a 6GB did you manage to get it working, rooted and all?
Your point 6) well I flashed mine on the latest 64bit win10 ... but.... if the phone is off and you connect the usb cable my phone tried to boot up either in twrp with no com port. Also booting it in bootloader doesn't make the comport visible so you can't flash.
The only way to make mine visible for the flashtool was to press vol+ and then connect the usb cable.
Btw I am glad someone finally responds and spreads information. A very good post! Your first 'thanks' well deserved!
I wonder where the guys are that I was trying to help. Did they throw their phones away or something? Sharing is caring I thought.
I want to root mine to alter the camera settings and the media xml file. I find it strange that our sensor, which is the same as in my wife's Xiaomi's, takes seriously bad pictures.
Click to expand...
Click to collapse
Sorry forgot to mention I have a 4 GB version but since maze is not providing the roms on their website any further development will be limited..thank God for dreambo he is the only guy doing any work here and like you said nobody is responding to any questions asked..shame really because maze is a great phone with a terrible camera..which drivers did you use on Windows 10? because I tried a hundred of them and non of them recognize my phone..and in adb I can run the command fastboot reboot bootloader but after reboot none of the commands are working .
And yes I did manage to install twrp and root using magisk and I to hope that all those other guys didn't brick their phones
frumac96 said:
Sorry forgot to mention I have a 4 GB version but since maze is not providing the roms on their website any further development will be limited..thank God for dreambo he is the only guy doing any work here and like you said nobody is responding to any questions asked..shame really because maze is a great phone with a terrible camera..which drivers did you use on Windows 10? because I tried a hundred of them and non of them recognize my phone..and in adb I can run the command fastboot reboot bootloader but after reboot none of the commands are working .
And yes I did manage to install twrp and root using magisk and I to hope that all those other guys didn't brick their phones
Click to expand...
Click to collapse
This is the filename I used on Windows 10 VCOM Drivers (All MTK Devices & All Windows OS version).zip I think I downloaded it from XDA somewhere.
Also something you must know https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Another thing I experienced is that one USB connector is not the other one on a pc. Always connect it to the ones directly on the main board next to the other device outputs like audio etc. and preferably not go through ones that have been extended via a cable like the ones on top of the casing or so. Also a must have application is usbdeview.
Well should be easy to get it going if you can boot it into 'fastboot' then you can try as much as you want to. But djeeeeezzzz the letters are very small when you boot it with a power+volume up . Also check that volume up will toggle between 'fastboot', 'recovery' and 'normal start' and volume minus will select it, not the power button which would be more logical to me.
I might have another go at trying to get it working on my 6GB but it involves having a lot of time and knowing that I will get frustrated. Installing all apps and settings is also a time consuming thing. Once you have TWRP on it it all becomes easy to backup. So many things to test or try.
Maybe dreambo has an idea on how to get mine up to a 6GB one as it is probably only indicated in the kernel.
Anyway I will continue to write down my progress.
Ok more frustration. Done multiple things to try to get this running. It's good to know that the original rom is easy to install again after practice.
Take 1: Try to install clean 6GB rom and immediately install TWRP.
Results: Dreambo forgot 1 step and that is to allow OEM unlock in the developer options. If you do the adb command to unlock press volume up and it will unlock (very hard to see, very small letters on the display in bootloader mode)
Well TWRP starts but immediately I get a message 'mount decrypt data password' which I tried a couple of things but no go. Also googled... different solutions but always ending in a bootloop to TWRP
A possible solution that I read was to create a startup pin .... no go 'pin not valid'
Take 2: Take all the rom files and change the scatter file with the one dreambo provided.... Thought it was successful but ended up with the same Chinese recovery. Trying to figure out why since the filename was correct like indicated in the scatter file. Came to the conclusion that the original file was/is called recovery-verified.img and not recovery.img. Really really strange this one as in the original scatter file it also points to recovery.img. So this one I will have to investigate. Renaming the TWRP file to recovery-verified.img lead to a error during the initial scan of the flashtool.
So moral of the story is that I am back on square 1 and lost 2 hours today (plus putting all apps and settings back) today.
I get a bit lost, is this TWRP method only working with the 6GB or also with the 4GB version?
CYberdog11 said:
I get a bit lost, is this TWRP method only working with the 6GB or also with the 4GB version?
Click to expand...
Click to collapse
There is no fundamental difference between 6G and 4G version.
It must works in boat versions.
If you have issues with SPFlashTool try this (no need to install any drivers on Windows 10) :
Put the preloader.bin (found in the rom package designed for SPFlashTool) in the same folder as the recovery.img without checking it the list of partitions (only recovery must be checked) and click on Download to flash the recovery, as usual.
Perhaps SPFlashTool cannot read by himself the preloader in the EMMC, and we must provide it.
The linux version of SPFlashTool not works at this moment, I do not know why
With the SPflashtool I always get the error:
ERROR:STATUS_DA_HASH_MISMATCH (0xC0070004)
HINT
CYberdog11 said:
With the SPflashtool I always get the error:
ERROR:STATUS_DA_HASH_MISMATCH (0xC0070004)
HINT
Click to expand...
Click to collapse
From another thread:
mmakdz said:
google translate
Hello
I had the same problem, (error BROM ERROR: STATUS_DA_HASH_MISMATCH)
what I did: I use Windows 7 System
1- clear all drivers for smartphones with "usbdeview-2-17"
2- install Drivers "Drivers_Auto_Installer_v1.1236.00"
3- install "PdaNetA4170"
4- use "SP_Flash_Tool_v5.1708_Win" to flash the rom. first flash the preloader alone and then flash the others.
the problem was the bad installation of the drivers, after that everything went well for me.
try it can work for you too.
the mentioned software is easy to find on google
Click to expand...
Click to collapse
dreambo said:
There is no fundamental difference between 6G and 4G version.
It must works in boat versions.
If you have issues with SPFlashTool try this (no need to install any drivers on Windows 10) :
Put the preloader.bin (found in the rom package designed for SPFlashTool) in the same folder as the recovery.img without checking it the list of partitions (only recovery must be checked) and click on Download to flash the recovery, as usual.
Perhaps SPFlashTool cannot read by himself the preloader in the EMMC, and we must provide it.
The linux version of SPFlashTool not works at this moment, I do not know why
Click to expand...
Click to collapse
If there is no difference between the 4GB and 6GB then why did I literally spend days on trying this and documenting what happened?
lukesan said:
If there is no difference between the 4GB and 6GB then why did I literally spend days on trying this and documenting what happened?
Click to expand...
Click to collapse
Do you have the 2 versions of the phone and do you have notice any difference of the flashing procedure ?
dreambo said:
Do you have the 2 versions of the phone and do you have notice any difference of the flashing procedure ?
Click to expand...
Click to collapse
I only have the 6GB version of the Maze Alpha. But you wrote that the procedure should work for both versions. I think I wrote down what happened with mine if I installed TWRP.
I tried both the 'regular' flashing and then the full rom install with the trick to put the files in the directory and rename but both ended up as I've written in my previous post.
lukesan said:
I only have the 6GB version of the Maze Alpha. But you wrote that the procedure should work for both versions. I think I wrote down what happened with mine if I installed TWRP.
I tried both the 'regular' flashing and then the full rom install with the trick to put the files in the directory and rename but both ended up as I've written in my previous post.
Click to expand...
Click to collapse
From times to times, I notice trouble with flashing using SPFlashTools.
First (when I post my first post relating of the root) I use the linux version : no issues it works perfect, no need of any drivers!
Actually, no way to have it working on linux, why I do not know!
I have tried Windows 10 and I notice that we have to provide the preloader to have it working, as I write in my post.
In theory, and only in theory, the SPFlashTool must works the same manner in any phone with a Mediatek SOC.
But in reality, we have notice that with exactly the same phone the flashing procedure works for some users and not for others!
SPFlashTool is a very capricious software, there is no warranty to have it 100% working in any platform, even with the same OS.
dreambo said:
From times to times, I notice trouble with flashing using SPFlashTools.
First (when I post my first post relating of the root) I use the linux version : no issues it works perfect, no need of any drivers!
Actually, no way to have it working on linux, why I do not know!
I have tried Windows 10 and I notice that we have to provide the preloader to have it working, as I write in my post.
In theory, and only in theory, the SPFlashTool must works the same manner in any phone with a Mediatek SOC.
But in reality, we have notice that with exactly the same phone the flashing procedure works for some users and not for others!
SPFlashTool is a very capricious software, there is no warranty to have it 100% working in any platform, even with the same OS.
Click to expand...
Click to collapse
The thing is that I have no issue with flashing the software as I can perfectly flash the original rom. The problem is that when flashing the TWRP file, in both options by the way, so also via method 1, I get a boot loop.
hi
the other day i tried to dd in a bootloader to add fastboot to my K8+ (2018) LMX210ULMA and wiped my preloader. The device uses an mt6750 chipset and i had made a back up so i have the approriate software to restore it, i even have the scatter file.
The problem is that there is no da_pl.bin file for lg phones to use sp flashtool, i have no download mode and no fastboot.
i have two pc`s one running ubuntu the other windows 7.
i would appreciate any help
any help at all
ok so ive found some versions of sp flash tool that are supposed to get around the authorization stuff and i have an auth file but i keep getting brom errors. the same one in fact. on linux ifs 0x00. ive been looking at and following the tutorials ivs made android rules and all kinds of things but i cant get it to flash. it started to befote i added the stuff in the tutorials. The red line would go acrross the bottom but now i just get the brom errots.
Thumb up for boldness... :good:
Now you have some interesting project there.
Keep us update if you manage to find out any solution.
No idea how to help but Good luck!
https://blog.hovatek.com/so-whats-all-this-talk-about-meditek-secure-boot-and-da-files/
https://ifindhub.com/download-mtk-secure-boot-da-loader-files-mtk-devices.html
ill get there eventually. I have been looking at all the config and ini files and i hate to say it but security might be essier than you think to overcome. just have to erase a few lines here and there and teplace some as needed. idk ty. Dont worry ill keep you guys posted
i really think sometime we over think and see past the easiest solutions. but what do i know im trying to flash an mtk preloader on an lg phone.
im actually trying to unbrick a few phones. two qc `s and the mtk. I kinda bricked one of my lmx210`s on purpose not thinking it would brick. well jokes on me.
Im have a couple questions maybe somebody can help with. In the past couple months on my journey through madness i have tried a few hindred different ways and more flashtools than you could imagine. So far nothing has worked but ive learned alot of theory.
so far though i know that the mtk board is in bootrom mode. We will get back to that as i have an idea....
ok on the qc boards we have the dreaded 9008 mode. I made some progress today. i wanted to see if the LMX210 could boot from SD card instead of the internal. I believe it can but im having trouble with what to do next. p
i used dd to flash the gpt on my sdcard then formatted the partitions to the proper filesystem. when i plugged it in to the usb it lit up but did not boot. But it lit up for the first time since bricking.
But it only lights up with usb plugged in. Add the batrery and it goes dead. It also doesnt show 9008 mode any more.
i went back and changed the boot and recovery images to reflect using the mmcblk system and now windows device manager can see it. But no boot. im wondering first if i might need a special boot loader to boit from sd and two if i might be able to use the same trick to get the mtk running
Some LG firmwares include some files for SPFT, like LGX240ARAT and LGX230HAT.
but do they work with MT6750? In LGX240ARAT there is a dll that mentions MT6755,
but not MT6750. Newer versions probably needed. Or maybe you could hack it. ??...
part of my problem is not knowing what scatter file to use. these phones have thier info all twaktup. the mtk gives several different board/chip types. like we have 6722, 6755, 6750, 6736 and so on. im pretty sure though its a 6750 board with 6755 chipset but do i use the scatter for the board or the chipset.
Ok idea!!
I can pick the phone up as bootrom mode on port in my ubuntu as /dev/ttyACM0.
That means i can write to it. How can i dd the preloader.bin to the right place on there
Duhjoker said:
Ok idea!!
I can pick the phone up as bootrom mode on port in my ubuntu as /dev/ttyACM0.
That means i can write to it. How can i dd the preloader.bin to the right place on there
Click to expand...
Click to collapse
As I don't know much about but have played a bit with these.
https://gitlab.com/zeroepoch/aftv2-tools
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
And there is tools like eMMC Pro, etc. that might work too... ?
I think the m250 did answer to some handshake but there was some problems
because I didn't continue testing those py scripts...
I would try what I could read from it first. From those scatter files I guess that
preloader is on its own partition. The other one should start with partition table, pgpt .. ??
CXZa said:
As I don't know much about but have played a bit with these.
https://gitlab.com/zeroepoch/aftv2-tools
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
And there is tools like eMMC Pro, etc. that might work too... ?
I think the m250 did answer to some handshake but there was some problems
because I didn't continue testing those py scripts...
I would try what I could read from it first. From those scatter files I guess that
preloader is on its own partition. The other one should start with partition table, pgpt .. ??
Click to expand...
Click to collapse
Hi,
If you can reach bootROM mode by pressing any of the volume keys while you connect the phone (Mediatek Inc. MT6627) you should be able write and read the EMMC with amonet.
The tool needs some modifications in order to make it work to MT6750. You can probably try with the mt6753 version which may work for MT6750:
https://github.com/Dinolek/amonet
For reference, use this commit:
https://github.com/R0rt1z2/amonet/commit/6b57d0a99f42739d3b3b2ce962b32ecb8fefd950
Contains all the stuff that needs to be edited in order to make it work for that phone
Regards!
Thank you i can give it a try. Its already in bootrom mode though and accepts the handshake. The problem is that the py command that flashes the preloader and stuff on it also wants to flash other stuff as well that i dont have or does not work with the board.
The py command needs to be modified to only flash the preloader, lk.bin, laf and twrp. If those items only could be flashed i could bring the rest of the device up using lgup
I have tried to modify the commands myself to include just those items but it errors. I dont know enough about the python language to be able to do it on my own.
Duhjoker said:
Thank you i can give it a try. Its already in bootrom mode though and accepts the handshake. The problem is that the py command that flashes the preloader and stuff on it also wants to flash other stuff as well that i dont have or does not work with the board.
The py command needs to be modified to only flash the preloader, lk.bin, laf and twrp. If those items only could be flashed i could bring the rest of the device up using lgup
I have tried to modify the commands myself to include just those items but it errors. I dont know enough about the python language to be able to do it on my own.
Click to expand...
Click to collapse
PM me if you need help editing the python script
Regards.
I really appreciate your offer for help. I was looking at the reference for porting and now that i can see the things that would need changing why not go ahead and unlock the bootloader while we are at it. We could save a ton of devices and at the same time give them th3 extra value of being able to twrp and root them.
I have been looking for some way to unLock the bootloader on these phones for days and though it will be some work being able to reflash the preloader AND unlock the bootloader which was my main intent when i bricked it would be worth the extra effort.
Rortiz2 said:
PM me if you need help editing the python script
Regards.
Click to expand...
Click to collapse
I couldnt post the main.py script in the pm but i can attach it here. Thank you so much.
Here is the raw preloader extracted using salt on my pc.
Ok so i went through your source code for the meizu m2 amonet to match it with source code for the mt6750 and i only had to change a couple things. Its pretty much identical to the commit you pointed me too.
As far as i can see your amonet should work just fine with the sp200/lm-x210ulma boards. I did add my .img files to the bin folder though.
Any way i keep getting errors.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 501, in read
'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Rortiz2 said:
Hi,
Contains all the stuff that needs to be edited in order to make it work for that phone
Regards!
Click to expand...
Click to collapse
Hi,
Didn't continue experiments but now also @Duhjoker might be interested about this last new development...
[EXPLOIT] [BOOTLOADER] Mediatek based LG K10 2017 M250 bootloader secure boot bypass. by @OficerX
https://forum.xda-developers.com/lg-k10/how-to/exploit-mediatek-based-lg-k10-2017-m250-t4183545
MT6755 and MT6750 are essentially the same, MT6750 is cheaper and slower version of MT6755, these are compatible, you can use tools for 6755 on 6750.
Here (https://github.com/arturkow2000/lgk10exploit) you have tools that can help you flash preloader (write_boot0.py), these should work on your device.
Open config.py set BR_DEV_PATH to /dev/ttyACM0
then write: python write_boot0.py --brom path_to_your_preloader_bin
This is slow process, may take few minutes (you will see progress while flashing).