Related
Hi all.
I guess I am in deep trouble.
I have a Lenovo P780 (chinese base rom) 4gb version. Rooted it and installed with CWM recovery for P780. Installed Muse UI 3.0 custom rom from custom recovery via sd card. Swapped the internal SD with External SD card by editing the vold.fstab and vold.fstab.nand also.
However, I realised that there are a lot of bloatwares that took up the RAM and started uninstalling chinese apps that seems to come with the custom rom from system. However, when I restarted the phone, its now unable to boot beyond the 1st boot screen. (Boot loop)
Current state of the phone now:
1. Able to enter custom recovery mode, but menu is blank except for the navigation commands. (return, up, down, confirm)
2. Able to enter adb only when the phone is in custom recovery mode.
3. Able to connect to PC (Windows 7 64bit). Mediatek MT6589 usb drivers installed. Many versions of sp flash tools installed and tried.
4. Can't seem to enter fastboot for this phone. (Tried many key combinations. Only Meta mode, recovery mode and factory mode are found)
Things I had tried:
1. Flashing stock rom.
I had downloaded the stock roms and tried flashing with sp flash tools, but I always encounter the following errors. Had also tried switching to another windows XP based pc and still encounter these errors.
(a) Firmware -> upgrade. Tried Auto Format Flash also and it returns with the same errors.
- BROM ERROR: S_FT_FORMAT_FAILED (4010)
Format flash error. Possibly given wrong format range. Please check your format settings.
(b) Download (all img boxes checked)
- BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
Download to flash fail!
(c) Download (only one img checkbox ticked, tried system.img and recovery.img)
- - BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
Download to flash fail!
2. Flashing recovery from adb terminal via windows and usb connection
When I put the phone to the custom recovery (with missing menu options), the adb terminal is able to recognise the phone and returns the following after the command 'adb devices':
0123456789ABCDEF recovery
Upon entering the shell via 'adb shell', I am given the # sign. (already in SU mode?)
Tried to flash a recovery image from this mode via terminal command flash_image, but encounters the following problems:
(a) unable to mount/remount
- mount -o remount rw /system
mount: mounting rw on /system failed: Invalid argument
chmod 777 /system/flash_image
# flash_image recovery /sdcard/recovery.img
no response from the terminal after this command.
I had tried and tried these for more than a week after work, but had not been successful in reviving this phone. Appreciate if anyone can assist me as I had ran out of ideas already.... Please assist me in reviving this good phone. Many Thanks!
Axis76 said:
Hi all.
I guess I am in deep trouble.
I have a Lenovo P780 (chinese base rom) 4gb version. Rooted it and installed with CWM recovery for P780. Installed Muse UI 3.0 custom rom from custom recovery via sd card. Swapped the internal SD with External SD card by editing the vold.fstab and vold.fstab.nand also.
However, I realised that there are a lot of bloatwares that took up the RAM and started uninstalling chinese apps that seems to come with the custom rom from system. However, when I restarted the phone, its now unable to boot beyond the 1st boot screen. (Boot loop)
Current state of the phone now:
1. Able to enter custom recovery mode, but menu is blank except for the navigation commands. (return, up, down, confirm)
2. Able to enter adb only when the phone is in custom recovery mode.
3. Able to connect to PC (Windows 7 64bit). Mediatek MT6589 usb drivers installed. Many versions of sp flash tools installed and tried.
4. Can't seem to enter fastboot for this phone. (Tried many key combinations. Only Meta mode, recovery mode and factory mode are found)
Things I had tried:
1. Flashing stock rom.
I had downloaded the stock roms and tried flashing with sp flash tools, but I always encounter the following errors. Had also tried switching to another windows XP based pc and still encounter these errors.
(a) Firmware -> upgrade. Tried Auto Format Flash also and it returns with the same errors.
- BROM ERROR: S_FT_FORMAT_FAILED (4010)
Format flash error. Possibly given wrong format range. Please check your format settings.
(b) Download (all img boxes checked)
- BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
Download to flash fail!
(c) Download (only one img checkbox ticked, tried system.img and recovery.img)
- - BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
Download to flash fail!
2. Flashing recovery from adb terminal via windows and usb connection
When I put the phone to the custom recovery (with missing menu options), the adb terminal is able to recognise the phone and returns the following after the command 'adb devices':
0123456789ABCDEF recovery
Upon entering the shell via 'adb shell', I am given the # sign. (already in SU mode?)
Tried to flash a recovery image from this mode via terminal command flash_image, but encounters the following problems:
(a) unable to mount/remount
- mount -o remount rw /system
mount: mounting rw on /system failed: Invalid argument
chmod 777 /system/flash_image
# flash_image recovery /sdcard/recovery.img
no response from the terminal after this command.
I had tried and tried these for more than a week after work, but had not been successful in reviving this phone. Appreciate if anyone can assist me as I had ran out of ideas already.... Please assist me in reviving this good phone. Many Thanks!
Click to expand...
Click to collapse
BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
have you try to re-install the driver for sp flashtool
and use new sp flash tool for flashing
droidinterest said:
BROM ERROR: S_FT_DOWNLOAD_FAIL (4008)
have you try to re-install the driver for sp flashtool
and use new sp flash tool for flashing
Click to expand...
Click to collapse
Yep. Tried using several versions of the drivers downloaded from different places and used USBDeview to remove/reinstall them. The error still comes back and haunt me.
maybe this can help you
No luck.... formatting is not working in sp flash tool (4010 error) and the preloader in the thread is not for my phone.....
Anyone able to help pls....?
Axis76 said:
Anyone able to help pls....?
Click to expand...
Click to collapse
have you use google my brother ? google is our true friend.
but i glad if i can help you:angel:
you can visit this for factory rom
or you can visit lenovo forum
or you can go to needrom
Yeah. Google had been my fren, but no more after googling for 2 weeks without a solution. Trust me. I had looked thru most solutions found in google and had tried without any success before I post here.
All those stock roms of all release numbers I had already tried as mentioned above, with sp flash tools (tried many versions of that also.) ALL attempts are stucked with the errors mentioned above. The sp flashtool simply just fills the red status bar, and stopped with one of the errors in my 1st post.
I've even checked the chinese forums. My situation seems to be this:
The partition table of the flash memory had been reformatted thanks to the custom rom flashed via sd card. That's why it always returns a format flash error when I attempt to flash back to the stock rom which uses a different format range using sp flash tools. The only way out is to do a clean format of the flash memory. But I haven't find a way to do that via sp flash tool or mtk droid tool.
My only recourse is on of the following:
1. If I can restore the custom recovery (via adb in recovery mode(no fastboot) or meta mode) and make it workable to do another sd card flash with a custom rom. I have no idea why the options in my custom recovery went missing. It was working before I flashed the custom rom. I guess that accursed rom somehow erased my custom recovery during boot.
2. If I can somehow be able to do a complete flash format with the correct format parameters using some tools. Sp flash tools had failed me so far.
Anyone is able to help in these directions? Many thanks....
The sp flash tool log also have this line when I searched for 'Errors'
FlashTool[2684][8556][DEBUG]: ERROR: OperationIndicator::QueryDADLHint(): da_dl_type(??) error, could not find DA download hint!(.\OperationIndicator.cpp,98)
anyone can help......?
Axis76 said:
The sp flash tool log also have this line when I searched for 'Errors'
FlashTool[2684][8556][DEBUG]: ERROR: OperationIndicator::QueryDADLHint(): da_dl_type(??) error, could not find DA download hint!(.\OperationIndicator.cpp,98)
Click to expand...
Click to collapse
if i view logcat, there are some cause.
what sp flash tool do you use?
try flash one file with sp flash tool like recovery.img
and how the results ?
i will be back
droidinterest said:
if i view logcat, there are some cause.
what sp flash tool do you use?
try flash one file with sp flash tool like recovery.img
and how the results ?
i will be back
Click to expand...
Click to collapse
Almost every sp flash tool version I came across to....
SP_Flash_Tool_exe_v3.1248.0.96-MT6589
SP_Flash_Tool_exe_v3.1312.0.139
SP_Flash_Tool_exe_v3.1316.0.150
SP_Flash_Tool_v3.1224.0.sn85
SP_Flash_Tool_v3.1304.0.119
SP_Flash_tool_v3.1308.0.125
SP_Flash_Tool_v3.1320.0.163
SP_Flash_Tool_v3.1328.0.183
SP_MDT_exe_v3.1304.00_A2013.02.26_customer6589
SP_MDT_v3.1228.00
etc
As mentioned in my first post, 4008 error when I flashed 1 file.
Axis76 said:
Almost every sp flash tool version I came across to....
SP_Flash_Tool_exe_v3.1248.0.96-MT6589
SP_Flash_Tool_exe_v3.1312.0.139
SP_Flash_Tool_exe_v3.1316.0.150
SP_Flash_Tool_v3.1224.0.sn85
SP_Flash_Tool_v3.1304.0.119
SP_Flash_tool_v3.1308.0.125
SP_Flash_Tool_v3.1320.0.163
SP_Flash_Tool_v3.1328.0.183
SP_MDT_exe_v3.1304.00_A2013.02.26_customer6589
SP_MDT_v3.1228.00
etc
As mentioned in my first post, 4008 error when I flashed 1 file.
Click to expand...
Click to collapse
I think it's because the driver is not installed, try to disable digital signature on your windows, and reinstall driver for your phone
for how to disable digital signature go to this
droidinterest said:
I think it's because the driver is not installed, try to disable digital signature on your windows, and reinstall driver for your phone
for how to disable digital signature go to this
Click to expand...
Click to collapse
Already tried this. I had tried on 2 pcs. Windows 7 and windows xp (no digital signature). Same errors occur in both pcs. I really don't know what is going on with this phone. Nothing seems to work.
PS: Have been running the program as administrator all along also.
Sent to a phone repair shop and its at worst state than before now. Unable to power on. Connecting phone to computer and tried using sp flashtool now gives 4032 error (Enable Dram failed).
Any hope with reviving this phone now?
leno p780 in bootloop
please help
I tried to flash viberom from needrom but failed miserably & now the phone is in infinite bootloop.
screens just lights up slightly & then phn vibrates & then screen lights out & the loop continues even the boot logo doesn't show up
no keys working for CWM mode or anything
AshishKhalkho2013 said:
please help
I tried to flash viberom from needrom but failed miserably & now the phone is in infinite bootloop.
screens just lights up slightly & then phn vibrates & then screen lights out & the loop continues even the boot logo doesn't show up
no keys working for CWM mode or anything
Click to expand...
Click to collapse
Hi, first, do you have SP Flash Tool installed on your PC and have the drivers installed? If yes, download the stock ROM of your choice from here and flash it with via SP Flash Tool, and your phone should be revived.
Flashing methods are clearly stated in case if you don't know how to do it.
lenovo p780 not booting
Help please by mistake i tried to convert a system app to user the name of app is classical i tried to convert by system/app application suddenly my phone gets off automatically and now not booting up stucked at boot logo tried pressing the reset button nothing happend plzz help
somu12345 said:
Help please by mistake i tried to convert a system app to user the name of app is classical i tried to convert by system/app application suddenly my phone gets off automatically and now not booting up stucked at boot logo tried pressing the reset button nothing happend plzz help
Click to expand...
Click to collapse
http://forum.xda-developers.com/lenovo-p780/help/lenovo-p780-brick-t2782696/post53395430
WHAT CAN I DO___???
hardware
Axis76 said:
anyone can help......?
Click to expand...
Click to collapse
check on hardware, there must be trouble with your flash chip ic, try to rehot it first.
if doesn't work that mean your flash chip ic completely dead
Hi all ,
i'm new.
I have a rooted p4502 (op3ndott)
specs
mtk 6582
1 gb ram
I accidentally deleted the folder "framework" in system partition. The phone crash and when i start it go in boot loop.
i can go in recovery and also i do a data/factory reset, and always boot loop.
i havent did a backup of rom and now i can find the original rom on the web.
What i can do ? it's recuperable ?
(sorry for my english but i'm italian )
please answer
i have same problem :crying:
You must install CWM or TWRP with spflashtool. I install twrp in terminal, I don't now method install it with spflashtool, you must looking in network. I can upload twrp and backup firmware ver 208 and ver 213.
------
1. Install MediaTek DA USB VCOM drivers
2. Download and run SPFlashTool
3. Click Scatter-loading button to load the correct scatter file
4. Deselect all parts except recovery.img, set path to recovery.img
5. Turn off your phone, remove the battery and replace it after some seconds (and don't turn on the phone).
6. Press Download and connect your phone into the computer via USB data cable.
7. The process will start and a red progress bar will appear.After the red progress bar is complete, there will appear a purple progress bar.When the yellow bar is complete, you'll get a popup with a green circle and Download OK message,
which means that the process has been successfully terminated.
If you have installed recovery you can install backup. I can upload my backup.
shanti77 said:
You must install CWM or TWRP with spflashtool. I install twrp in terminal, I don't now method install it with spflashtool, you must looking in network. I can upload twrp and backup firmware ver 208 and ver 213.
------
1. Install MediaTek DA USB VCOM drivers
2. Download and run SPFlashTool
3. Click Scatter-loading button to load the correct scatter file
4. Deselect all parts except recovery.img, set path to recovery.img
5. Turn off your phone, remove the battery and replace it after some seconds (and don't turn on the phone).
6. Press Download and connect your phone into the computer via USB data cable.
7. The process will start and a red progress bar will appear.After the red progress bar is complete, there will appear a purple progress bar.When the yellow bar is complete, you'll get a popup with a green circle and Download OK message,
which means that the process has been successfully terminated.
If you have installed recovery you can install backup. I can upload my backup.
Click to expand...
Click to collapse
Hi.
I have the original software on my phone without root, i can make this operation ?
thankyou
Good evening,
I installed TWRP with flash tool, it works but missing the OS.
With flash tool i used those files:
logo.bin, lk.bin, MBR, preloader.bin, secro.img, MT6582_Android_scatter.txt, boot.img, recovery.img, system.img
But i don't have any files for:
ebr1, ebr2, cache, usrdata
If someone has got the files or can help me...
Thx you.
Firmware backups(TWRP)
ver208
ver213
Files must be in internal memory(you can copy it from external sd in TWRP)
Path:
/TWRP/BACKUPS/P4502/ver_or_date/files(boot.mmc.win,system.ext4.win ...)
Hi everyone, as the title says, my lyo-l01 is soft-bricked. I searched everywhere online to find the UPDATE.APP file and an official ota package...my actual build is lyo-l01c600b105, and the most close firmware I could find is c600b103. Now, this file has an UPDATE.APP file, but also a scatter file and full SYSTEM, BOOT, RECOVERY etc...imgs. I already have huawei update extractor, mtk droid studio, huawei multi-tool, mtk rom studio and sp flash tool installed on my pc.
Unfortunately multi tool won't work because I have an unlocked bootloader but a frp lock, which I tried to unlock via adb and fastboot but no success (I even tried to relock the bootloaader but it won't allow me to, because of the frp). I also tried using sp flash tool with the scatter file I have, but when I select it the tool gets an error saying "this application has requested the Runtime to terminate it in a unusual way. Please contact the application's support team for more information."
Mtk droid studio only recognizes the processor (MT6735), build date UTC (19700101-000000) and LCD driver IC: 1-ili9881c_dsi_vdo_txd (I really don't know what this is); and on start it says: "--- ERRORE : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!" and "--- WARNING! Recovery is not compatible with this device!". The recovery is a TWRP 3.0.2.
I was forgetting that I also tried to create a dload folder on the sd card and putting in it the UPDATE.APP file, but when pressing vol up + vol down + power my phone will boot into recovery.
So, summarizing:
- BUILD: lyo-l01c600b105
- PROCESSOR: MediaTek MT6735P
- Unable to boot to system, only recovery and fastboot (sideload too)
- Unable to relock bootloader, unlock frp, unbrick via above mentioned methods
Can someone please help me? I'm stuck from 3-4 days and I really need this phone back
Thanks in advance for any help!
Hello everybody,
first of all I'm, sorry for my newbie's awkwardness and for my bad english too...
I'm a linux (Debian) enthusiast and I'd liked to install it on my Lenovo Tab M10 Plus; my choice felt on "Linux Deploy" but it needs a rooted device so, after an internet search for tutorials and tips and a system backup (.adb file saved on PC) I bravely tried with Magisk... and I failed (or I think so).
The tablet start in a never-end booting loop and on the splash screen appears the message
"
Orange State
Your device has been unlocked and can't be trusted
You device will boot in 5 seconds
"
I can access in fastboot mode so I tried to flash a no-rooted (downloaded) boot.img but it didn't works (the flashing process reports OKAY but the device reboot anyway in Orange Status), I tried with the flashall command that reports
"
error: ANDROID_PRODUCT_OUT not set
"
I tried to wipe and flash but it didn't works, I granted the access in some recovery mode and tried to install the .adb backup file from the SD card but the system says :
"
E: signature verification failed
E: error: 21
Installation aborted.
"
I thought to open the backup .adb file for extract the original files (I don't know if it could be done and if it could be useful) but how?
I think someday someone more skilled than me will solve the problem but, waiting for that day... any advice ?
Thanks, anyway.
Cheers, Ste.
Use official Lenovo Rescue and Smart Assistant
Same problem...lenovo tab x606F firmware is not present in Lenovo Rescue Smart Assistant and you can't add it manually!
Yes hello, sadly I am having the same issue as well. Anyone have any ideas? Here's what I've tried:
[edit]
the phone reboots into recovery (I install the wrong recovery, that's why the bootloop), it does not enter the fastboot and when you enter the recovery it just turns off on the boot screen. I can't get into the system either. The bootloader is unlocked. I tried the SP flash tool and it gave me an error brom. And mtk-client, as I understand it, was fixed on miui 14. because there is also an error there. help me please
Hi, did you manage to solve this problem?
What have you tried with mtk client?
hi, I still haven't solved the problem. In mtkclent, I tried to flash the "boot.img" file through brom mode
If the boot flash was successful but you still cant access fastboot or recovery try reflashing the stock rom using brom mode
Step1: Setting up the files
Download the stock rom for your device (I prefer miuirom website)
Extract the downloaded rom
Check if Mediatek USB VCOM Drivers and UsbDK are installed correctly.
Set up mtkclient (follow official guide)
TIP:
After some research i found out that you can speed up the mtk process by modifying the mtk_daxflash.py file. (Source)
Open the file using notepad and search for this line:
Python:
dsize = min(length, 0x200)
And replace it with this:
Python:
dsize = min(length, 0x2004)
Step2: Fix your device
Open the command prompt in the mtk folder
Run this command WITHOUT your device plugged in:
WARNING! This will erase all data on the device
py -3 mtk wl <extractedrompath>\images\
(py -3 or python depending on the installed python version)
plug in your phone and put it in brom mode. the procedure should start immediately
This will flash all the files inside the images folder in the correct partitions (may take a while)
In the procedure you may see some partitions error but thats normal
When the first command is done run this second command:
py -3 mtk w boot_a "<extractedrompath>images\boot.img"
And this command:
py -3 mtk w boot_b"<extractedrompath>images\boot.img"
This will write the boot image to the boot_a and boot_b partition.
Now if everything succeded you should be able to boot into miui.
If not you should be able at least to boot into fastboot, try following step3
Step3: Flash the rom in fastboot (If required)
In the extracted rom path you should see a .bat and a .sh named flash_all.
Put your phone in fastboot mode and run the bat (Windows) or the sh (macOS/Linux) file.
If everything succeded you should have your phone working again .
Hope that your device will work again!
Tria13 said:
the phone reboots into recovery (I install the wrong recovery, that's why the bootloop), it does not enter the fastboot and when you enter the recovery it just turns off on the boot screen. I can't get into the system either. The bootloader is unlocked. I tried the SP flash tool and it gave me an error brom. And mtk-client, as I understand it, was fixed on miui 14. because there is also an error there. help me please
Click to expand...
Click to collapse
Please PM me if you want your device to be flashed using authorised Xiaomi Server.
I have the same device and I bricked it a while ago by flashing twrp and booting to recovery
From my understanding edl flashing can only be done with an authorized xiaomi account. I don't have one so I had to pay someone on telegram who had one and who could unbrick it. He used a modified version of SP Flash Tool. Although he struggled a bit he got it fixed the next day after I downgraded to windows 10. If you want to avoid bricking this device I recommend you don't use twrp altogether or be very cautious and only use twrp builds from the official telegram group. Compatibility depends on the kernel and android version. For now aosp-based roms have issues with the gpu anyways. (always under 100% load)
Also there is a mtk bootprotect magisk module which might help. (I don't think it will if you flash wrong twrp tho)
I hope these informations are somewhat useful
WolfnHex said:
If the boot flash was successful but you still cant access fastboot or recovery try reflashing the stock rom using brom mode
Step1: Setting up the files
Download the stock rom for your device (I prefer miuirom website)
Extract the downloaded rom
Check if Mediatek USB VCOM Drivers and UsbDK are installed correctly.
Set up mtkclient (follow official guide)
TIP:
After some research i found out that you can speed up the mtk process by modifying the mtk_daxflash.py file. (Source)
Open the file using notepad and search for this line:
Python:
dsize = min(length, 0x200)
And replace it with this:
Python:
dsize = min(length, 0x2004)
Step2: Fix your device
Open the command prompt in the mtk folder
Run this command WITHOUT your device plugged in:
WARNING! This will erase all data on the device
py -3 mtk wl <extractedrompath>\images\
(py -3 or python depending on the installed python version)
plug in your phone and put it in brom mode. the procedure should start immediately
This will flash all the files inside the images folder in the correct partitions (may take a while)
In the procedure you may see some partitions error but thats normal
When the first command is done run this second command:
py -3 mtk w boot_a "<extractedrompath>images\boot.img"
And this command:
py -3 mtk w boot_b"<extractedrompath>images\boot.img"
This will write the boot image to the boot_a and boot_b partition.
Now if everything succeded you should be able to boot into miui.
If not you should be able at least to boot into fastboot, try following step3
Step3: Flash the rom in fastboot (If required)
In the extracted rom path you should see a .bat and a .sh named flash_all.
Put your phone in fastboot mode and run the bat (Windows) or the sh (macOS/Linux) file.
If everything succeded you should have your phone working again .
Hope that your device will work again!
Click to expand...
Click to collapse
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Tria13 said:
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Click to expand...
Click to collapse
The thing is ---- Auth bypass is not yet available for your chipset type MT6895.
We have to wait until we can bypass auth to flash using SP Flash tool.
Tria13 said:
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Click to expand...
Click to collapse
im sorry to hear this
mvikrant97 is right. MT6895 is currently unsupported. you just have to wait
mvikrant97 said:
Please PM me if you want your device to be flashed using authorised Xiaomi Server.
Click to expand...
Click to collapse
Hi, sorry I didn't see your post earlier. Can you solve your phone problem with an authorized Xiaomi Server? You can write your telegram or something else by which I can write to you. Thanks for the answer