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
Related
Hey sorry but I am posting this because even after a lot of research I couldn't find a proper solution to this problem....
I am on twrp recovery version 2.1.3 and to upgrade to 2.5.0.0 I used the goo.im app but even after the message showing that recovery was flashed successfully, when I reboot into recovery I still see the 2.1.3 twrp only....
So I tried flashing it with terminal emulator but it didn't work..... This error shows up every time....
failed scanning partitions failed with error : - 1
I tried putting the .img file in the root folder as well but it didn't work.... I tried naming the root of sdcard as storage/emulated/legacy, storage/emulated/0, /sdcard, etc but it keeps on giving this error every single time!
Nowhere could I find a solution for this problem so please please PLEASE! HELP!
:crying: :crying:
flashing recovery the fastboot way
Dwait said:
Hey sorry but I am posting this because even after a lot of research I couldn't find a proper solution to this problem....
I am on twrp recovery version 2.1.3 and to upgrade to 2.5.0.0 I used the goo.im app but even after the message showing that recovery was flashed successfully, when I reboot into recovery I still see the 2.1.3 twrp only....
So I tried flashing it with terminal emulator but it didn't work..... This error shows up every time....
failed scanning partitions failed with error : - 1
I tried putting the .img file in the root folder as well but it didn't work.... I tried naming the root of sdcard as storage/emulated/legacy, storage/emulated/0, /sdcard, etc but it keeps on giving this error every single time!
Nowhere could I find a solution for this problem so please please PLEASE! HELP!
:crying: :crying:
Click to expand...
Click to collapse
Hi,
You may be able to wipe your tears .This worked for me on the Huawei Ascend y300 which was rooted and had its bootloader unlocked first. Since I got a similar error to you using flash_image these steps might work for you too:
disconnect usb cable from phone
Boot into the bootloader mode (usually power and volume down).
reattach usb cable to phone
Download fastboot
get a dos prompt
navigate to the fastboot directory
do these commands followed by pressing enter:
fastboot devices
(your device should be listed)
copy and paste your recovery.img into the fastboot folder in windows.
fastboot flash recovery recovery.img
fastboot reboot.
Now make sure your phone boots normally.
Now power it off. Hold down volume up while pressing power, it should put you in your custom recovery.
Keiichicom.
Hello, I'm a little bit new to all this, so any help and detailed instructions are very very helpfull.
So I have Gigabyte GSmart Aku A1 device (MediaTek 6589), I don't know if it's bricked or what but apparently is not working quite well.
When I turn on my phone, it just loads and loads and loads and nothing happens (waited for about 4-5 hours), that was starting to happen after I somehow installed CWM on my device with some tutorial, CWM worked for the first time and after next reboot, it disappeared and stock recovery came back (and the problem with infinite loading screen - only showing logo).
I have ADB drivers installed, SDK aswell, tried to put stock firmware (got it from official site) and in like 1/4 of installation it says:
Code:
symlink: some symlinks failed
After that, I tried to install few versions that I downloaded from that official site, but same error again and again. (I tried to install with SD card and with ADB too. ADB is only working when I go to "apply update from ADB" in recovery. I have also used 2 different types of SD cards.)
That didn't worked either, so I got to some russian forum, and using google translator I downloaded 5-6 types of custom ROM's / Firmwares. That didn't worked either, one time when installing one of those ROM's - it said something about signature..
After that I was trying to install those ROM's with ADB and with SD Cards aswell, but turns out that every single time I get error saying: "Installation aborted.".
I have ofcourse tried to wipe data/factory and to wipe cache too, but nothing helps..
Also, when I'm in ADB console, when I type any command besides adb sideload or adb devices, I get error saying: "error: closed". I cant get into fastboot with adb console.
I really don't know what to do anymore, so any help would be very very appreciated. Thank you for your help in advance, if you need any videos, pictures or something, just tell me.
Edit: When I go to "wipe data/factory reset" in recovery, it says: "Mount /data error.".
BUMP!
BUMP^2!
luuksa said:
BUMP^2!
Click to expand...
Click to collapse
i would look for stock rom in form of full mtkdroidtools backup and preloader drivers for your mtk chipset
and flash it using flashtool (it uses preloader[you can determine if it's available/undamaged by turning phone off and opening device manager on pc and plugging phone to pc if there will be a flash in device manager before the charging starts it will flash ])
Hello everyone,
This is my first post on xda and I've read some of the posts etc and I thought it's time to begin to start questions related to my problem. This will be kinda long post and I'll try to give as much as information from my device specs to what I did to my device up to this point so you guys can understand my problem maybe help me or simply you can say its bricked and I can done with it. And last, I'm kind of newbie with android environment.
As you can see from the title my device is 'Reeder a8i Quad tablet' which is currently in Turkey. Device specs are following:
Uses Intel atom bay trail, Android 4.4.4, TF card (similar to sd)
bootloader title says 'droidboot' and for the recovery there is no install from sdcard or something like that.
There is almost little knowledge with the device and official site is not helping ( I guess they don't care at all )
Some Turkish forums actually got some idea about rooting and flashing stock rom. ( Later in 2015-2016 they released 5.1 for the device and that's all ). Forums actually use old how-to's from reeder support with images how the process done for upgrading android system.
First I try to find some ways to root the device but unfortunately my lack of knowledge and almost no guide for root get me stuck in the first time. I had 4.4.4 android and I was looking at ways to root it. My friend used King Root to root an old samsung phone but later he deleted it and suggested me to use it since I couldn't find any other way. I give it a try and use king root and followed instructions and voila! I had root access on my tablet and quickly installed greenify, root browser, uninstall ( for stock applications and especially google apps ) and later I installed superSU with terminal. Now for the fun part. I did give all these apps root access and deleted stock apps including google apps and 1-2 apps that king root installed while rooting. After deleting google apps I screwed up and keep getting crash reports for some of the services. I didn't know what I did to that point for google so I simply wipe data and wishing reverting all the things. After boot, there is king root app, google services again crushing and tablet looked unstable. I installed root checker which gives me that no 'root access' so I opened king root app and it couldn't root with error messages. I installed gapps for 4.4.4 and google services returned normal. Connected my tablet to pc and use king root again to root. Again device is rooted. Installed same apps, deleted king root apps and entire google apps, services, etc from tablet. Now I got no problems with google, successful root and happy face.
After closing my tablet and opened some day I saw that I don't have root access and king root app again no help at all. Again connected pc, app seems unstable with says my device is rooted and sometimes says not rooted. There was something wrong for sure and again wipe data etc. But now I found reeder tablet stock rom from the internet ( website is closed just today! ) including tons of tools and drivers and roms for other devices including mine. It's not actually site just index so you just go in a folder click and download etc. Installed my drivers, I already had android studio so adb fastboot etc but I did download some quick tools for just for this. I remember my device couldn't open so I just did some things from adb and fastboot and after 1 day work it's opened with 4.4.4. But google kept crashing so I understand that I didn't flash a stock rom entirely. Again root with all the apps and I simply use the device for some apps.
Up to this point I want to call part 1 because after this may be 3-4 months passed and about 2 days ago I started to play with tablet again. Now I installed some network tools to play with. Trying to use some MITM or cookie stealing etc. I used tons of apps including kali linux's nethunter tools which I get from their zip file. Obviously some of them not work and some other are. Still my root is unstable one time it says rooted one time says not. So It kept bothered me but now I don't want to use king root tried to search other ways to replace it with supersu. There is a guide here to use a shell script but it didn't worked so I found an app to replace it. It says done but king root app kept crashing and this point is where I called point of no return ( at least for me ) I downloaded king root app to my pc and tried to root it. It says rooted and now reboot etc. After that nothing changed and still the same. Btw, before tried root I used fastboot to try to open bootloader with boot.img from stock rom but I don't know what it actually does so. Again app is crashing there is no root access so I wanted to install stock rom. There is a guideline for 4.4.4-5.1 for my tablet and there is a tool named 'Manufacturing flash tool v6+' from intel. But I need an OTG for that since I don't have one. Flashing tool uses an xml file. Since I have that from stock rom's folder. I thought give it a try but nothing happened and tool supposed to detect my device but it didn't. At that time I could use fastboot and adb without a problem so I assumed tool got some sort of bug and installed again but result were same. I tried to wipe data and reboot but I got recovery screen with '3E' error. I tried to get into recovery screen to use adb and do something. I desperately used fastboot flash boot boot.img, fastboot flash recovery recovery.img and system system.img from 4.4.4 but not only it failed with the error 'end of footer from /tmp/update.zip not 0xFFFF file exists' but somehow corrupt the device rom and now I was stuck with reeder logo with infinite loop. After that I wanted to give that manufacturing flash tool a try again and same result. I did buy an otg cable for tablet and for my phone which screen destroyed couldn't unlock since touch screen almost not working and usb debug is closed to open that phone as well. There are files from reeder help desk to upgrade it to 5.1. I copied those files to tf card and used otg cable on my keyboard. Guide says press ESC key until bot manager is coming up. There is a screen with bot manager including bios settings. Guideline and tools says it's for upgrading bios so I did those steps and now again recovery mode. Opened manufacturing flash tool with my 5.1 xml but no result so I found something under menu to 'Print flash file cmds' used it and it simply bunch of fastboot commands. I opened fastboot and executed all those commands one by one for myself. Eventually some of them are failed with 'fastboot oem unlock' etc. Since it's changed into flashing unlock which both commands give error from tablet 'unknown command' I followed steps. ( At the end of the post I will give the xml commands from manufacturing flash tool ) After that at I used 'fastboot flash esp_update' provided with esp.zip file successfully. After that 'fastboot flash fastboot droid.img' failed. Following with 'fastboot flash boot boot.img' 'fastboot flash recovery recovery.img' 'fastboot -S 200M flash system system.img' all those commands failed and couldn't install the 5.1 manually.
At this point if I wanted to open my device it simply tries to update bios with the same file ( if tf card inserted ) other than that still at recovery with 3E and adb sideload not working with the error I got above 'end of footer from /tmp/update.zip not 0xFFFF file exists'
I know that my post is long and tried to give as much as information as I can. I just hope device is not completely bricked and there is a way to solve this. Any questions about information about device etc you can shoot I try my best to answer. Thank you for people who are reading this to spare their time.
Manufacturing flash tool xml file commands and success or fail after I executed them in DNX mode ( volume up + down + power at the same time )
fastboot flash osloader "I861B1C_1601001_64_20160115\efilinux-userdebug.efi" - success
fastboot boot "I861B1C_1601001_64_20160115\droidboot.img" - success
sleep - failed
fastboot oem enable_oem_unlock - failed
fastboot oem unlock - failed
fastboot oem wipe ESP - success
fastboot oem wipe reserved - success
fastboot oem start_partitioning - can't remember
fastboot flash gpt "I861B1C_1601001_64_20160115\partition.tbl" - success
fastboot oem enable_oem_unlock - failed
fastboot erase system - success
fastboot format cache - success
fastboot format config - success
fastboot format logs - success
fastboot format factory - can't remember
fastboot oem stop_partitioning - failed
fastboot flash ESP "I861B1C_1601001_64_20160115\esp.img" - success ( After this point I assume device is rebooted and opened a screen which is kinda new with big green 'NORMAL BOOT' text )
fastboot erase keystore - success
fastboot oem verified - success
fastboot format data - success
fastboot flash esp_update "I861B1C_1601001_64_20160115\esp.zip" - success
fastboot flash fastboot "I861B1C_1601001_64_20160115\droidboot.img" - failed
fastboot flash boot "I861B1C_1601001_64_20160115\boot.img" - failed
fastboot flash recovery "I861B1C_1601001_64_20160115\recovery.img" - failed
fastboot -S 200M flash system "861B1C_1601001_64_20160115\system.img" - failed
fastboot continue - failed ( it says success but reboot never happened )
Wassup aliens!
So I got this gionee M3 and I rooted it with iRoot and tried to flash recovery in nearly every way possible....... I tried using Flashify, Rashr, TWRP manager..... Nothing worked.
1) On Flashify: I kept selecting Flash recovery but the message I get every time is "Error copying the file, please send me the log file".
2) On Rashr and TWRP Manager: They both say they flashed the file but when I boot into recovery all I see is gray screen with a gionee logo. I also lost my stock recovery this way.
3) On PC: My PC never detects my phone as an adb or VCom device........To check for VCom I tried SP Flash Tools..... didn't detects the device. For Adb I tried Adb devices in command prompt but the devices list is empty.
Some info:
I have USB debug mode enabled.
I have stock 5.0.2 android rom with no recovery just factory safe mode through which I can perform some tasks.
If you need any pics or any info just tell me in the comments.
I hope you guys help me.... Been trying for the last 6 days.
HELP ASAP SOS
Love,
Justin Biebar
Tarun0101 said:
Wassup aliens!
So I got this gionee M3 and I rooted it with iRoot and tried to flash recovery in nearly every way possible....... I tried using Flashify, Rashr, TWRP manager..... Nothing worked.
1) On Flashify: I kept selecting Flash recovery but the message I get every time is "Error copying the file, please send me the log file".
2) On Rashr and TWRP Manager: They both say they flashed the file but when I boot into recovery all I see is gray screen with a gionee logo. I also lost my stock recovery this way.
3) On PC: My PC never detects my phone as an adb or VCom device........To check for VCom I tried SP Flash Tools..... didn't detects the device. For Adb I tried Adb devices in command prompt but the devices list is empty.
Some info:
I have USB debug mode enabled.
I have stock 5.0.2 android rom with no recovery just factory safe mode through which I can perform some tasks.
If you need any pics or any info just tell me in the comments.
I hope you guys help me.... Been trying for the last 6 days.
HELP ASAP SOS
Love,
Justin Biebar
Click to expand...
Click to collapse
Hey i have the same problem. Can you suggest me something regarding this.
A very big question
Hello! I have an argentine copy of the M3, called Hyundai Ultra Energy, same processor, same storage, camera quality, all in the same place. My question is how do I install a custom rom and how do I flash the recovery at first. I use adb commands, but I know that I have to do it with spflash. How is the process? I download the rom, charge the scatter and tilt only in recovery? Would be dangerous? Is more safe to root with King Root?
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