Database Info

[Completed] [Q] [HELP] Lenovo A606 bricked, now I am stuck

Hello,
I have a new Lenovo A606, that came with a strange ROM (IMEI not recognized, some weird WIFI setup) from 2014. I was able to set it up and correct the problems (thanks to google), but I still had some language issues (the Lenovo Apps including dialer, contacts, sms, etc… were English only). I was able to root it fine, and no working problem.
I decided to install a clean stock ROM, ROW: the A606_USR_S036_1502271022_V3_MP_ROW that is more recent and fully supports multilanguage.
I took a PC with Windows XP, and installed the latest SP Flash Tool, following a tutorial.
I was able to install android adb drivers and the MTK driver from the ROM image. The phone was showing in the devices, then was disappearing, then showing again… I had an error, but then I tried again with the option to update the firmware, and the Flash Tool reached the end and said it flashed succesfully.
Problem: after that, the phone was totally bricked. It would not start at all. When I plug it on the PC, it shows sporadically a device called "VENDOR 0E8D - communication" that disappears very quickly. I cannot flash it again. I just lost my brand new phone…
I tried with SP Flash Tool, and Flash SPMDT, with different ROMs, CN only, ROW, different versions… But nothing. It always says that Flash failed. Even when the phone is not plugged, I have an error with Flash SPMDT, with all ROMs, saying that (1)COM ports number is repetitive or invalid, or (2) Brom and preloader have the same comport number! and it asks me to modify them in INI file or scan again. Of course, scan fails, when I plug the phone pressing vol up + vol down (only way to make the phone recognized by the computer without a battery), the progress goes to 100% then either stays stuck there, or says it failed. SP Flash Tools gives this error: 'BROM ERROR s_ft_enable_dram_fail (4032)'
I tried several drivers, to clean drivers with usbdview, I tried several versions of SP Flash Tools… I don't know what to do anymore. I hope that Lenovo has a warranty and that they could flash it back to normal.
I don't know if it is a problem accessing the META mode on the phone, or bad roms… I tried on one computer with XP, and another with Windows 8.1, and the problem is the same.
ANY HELP would be appreciated, thank you!

Hi, thank you for using XDA Assist. It sounds like you've tried everything possible. Since it sporadically shows up on your pc try a different USB cable. If that doesn't work then I think it is bricked and you'll have to check with whomever you purchased the device from to see if they can fix it.

Thread closed.

Help bring my G3 back to life!!!

So, here's the story: I wanted to root my d850 on LP version D85021R, Tried all methods posted here, including this, this, and this. None worked. So I decided to downgrade to KK using tot/kdz method by hyelton. Downloaded LGD850AT-01-V10d-310-410-JUN-19-2014+0.tot file and LG flash tool 1.8.x and flashed the tot file. Progress went above 85% and then phone rebooted, but never came back to life; super-bricked, no led, no boot screen, no download mode, no recovery mode, NOTHING! except that it identified as QHUSB_BULK in Win7, which upon installation of drivers turned to qhsusb_dload 9008. Tried all unbricking methods including Board Diag, Flashtool ,etc. none worked. So I took it to a repair guy, who probably used octopus box to copy image from another g3 (at least that's what I think, he would not let me see but i sort of glanced over). After copying that image to my g3, it turned back to life, i.e., boot screen appeared and download mode/recovery mode worked, but it was in a boot loop. however, that guy also tried flashing V10D using flashtool, and same thing happened, i.e., super-brick again. After a day of trying he gave up on it but was kind enough to give it back half alive. So now boot screen appears, download mode works, gets recognized as LGE Mobile USB Serial Port, and LGE Android MTP Device with a yellow triangle. I cannot access fastboot mode due to locked bootloader, or else I would have tried flashing partition images through fastboot, as bootloader and boot partitions are intact, so I would not touch them but could try flashing other partitions. LG Flashtool flashes the whole package so the boot sector also gets over written, which somehow is not compatible with stock rom. One thing which I have not mentioned is that I did not buy it new but refurb one, so may be some part was changed, but which one, no idea. I tried to get it recognized it in linux, but does not work; shows up as libmtp-1-1 in /dev, which is not mountable. However I was able to pullout one interesting fact, which might give some hint. dmesgs shows a serial number for this device which starts as LGD855xxxxxxx, whereas the serial number printed on the back is different, where it shows as d850 and serial number is also different, i.e., 406KPXVxxxxxx.
Now I am out of options. Can someone please suggest what else to do. Also, can someone confirm that the serial number shown in dmesgs when connected to USB port, starting with LGD855xxxxxx can be a d850?
Any help is welcome

First off when flashing almost every time it'll fail at 85%. That's normal. Anything after80% is just rebooting of the phone.
Now what your having is not normal. Maybe whatever the repair shop did changed the serial? And your issue usually means your bricked completely sadly.
Before your downgraded, was your phone booting normally or did the root do something to make it originally boot loop before trying to downgrade ?
Sent from my iPhone using Tapatalk

Thanks for replying hyelton. I fully understand that and also that rebooting should bring the phone to blue reset screen, but it didn't. Instead it died.
The serial number and IEMI fortunately are intact, and are read by firmware when present. Sadly I tried to flash the firmware again through Board DL option, but failed again, so back to QLoader 9800 mode. On WinXP, smart boot diagnostics recognized it and proceeded to flash boot/recovery, but sadly the accompanied AP_Chip file neither has D850 nor D855 Smart_Boot.bin files. So I flashed EUR xxxx.xxx version. Phone still dead, but no Qloader 9800 mode, instead Android Phone device started showing up, which had no supported drivers. After some effort, Windows 7 download drivers and it got recognized as AlCatel Android Phone, lol! No adb and fastboot in Windows, and no Serial communication was possible. I tried linux and there fastboot was showing a device without id, like ??????????, but it did allow me to flash individual mbn paritions extracted from D850 tot to their respective partition, but I discovered I cannot flash through fastboot files larger than 2GB, so no system and no userdata; those were erased only. Upon reboot and return to windows, phone is still dead (without any life) and back to Qloader 9800 mode.
So now I'm stuck due to lack of firmware files. I am afraid to flash a boot or recovery partition extracted from any other firmware, but can try D855 since it worked partially to bring download/recovery partitions and LG logo was also displayed upon turning on. I think it even booted basic kernel in download mode, because I was able to send reboot command through Send_Command.exe and it rebooted. So scripting was also a possible option, but not anymore.
Is the partition layout of D850 and D855 available somewhere? I tried to find but could only find for D851. If someone having these variants is willing to help, I'll post the commands to get partitions layout, or even partition images could be created using dd command if phone is rooted.
To your question, no, the rooting methods did nothing. It was working normal. But somehow I came across a lot of threads that suggested hassle-free downgrading to KK for rooting, and pointed to your guide which surely is hassle-free but not for a troubled phone like mine
BTW, I do have Flashtool log files for original downgrade and then reflashing yesterday. If someone wants to take a look...

Further development: Today I visited the main mobile market in my city, and first went to same shop from where I bought this set. They had a number of other sets in the same batch, so I copied partition tables info and prop files from each device. Also, I had to buy the same set for a friend. I have asked him to lend it over to me for weekend. Now, first I'll try to find the rom versions installed on these sets and see what I can do.
Secondly, is there a way I can copy the whole emmc partitions from alive phone to dead phone? The dead phone can be accessed on serial port. I know I can get partition dumps, but how to write them on bricked phone, that is the question. There must be a software that can access emmc through phone ports and clone it. Help please!

unikorn74 said:
Further development: Today I visited the main mobile market in my city, and first went to same shop from where I bought this set. They had a number of other sets in the same batch, so I copied partition tables info and prop files from each device. Also, I had to buy the same set for a friend. I have asked him to lend it over to me for weekend. Now, first I'll try to find the rom versions installed on these sets and see what I can do.
Secondly, is there a way I can copy the whole emmc partitions from alive phone to dead phone? The dead phone can be accessed on serial port. I know I can get partition dumps, but how to write them on bricked phone, that is the question. There must be a software that can access emmc through phone ports and clone it. Help please!
Click to expand...
Click to collapse
Flash it to D855 Lollipop version via octopus than write DUMP

It does work, indeed. We did it together, didn't we, aamszia?
To elaborate further, Aamir helped me out by writing D855 bootloader through octopus box. That was done before but flashing a KK rom again bricked it. Only this time, he flashed a d855 lollipop kdz rom (v20g, if I remember correctly). That made it functional; everything worked, except radio. Flashing a d850 LP radio would not work; flashing a KK radio would brick it. So I took a dump of mmcblk0 from a fully functioning, rooted, recovery flashed LP d850, via terminal using dd command (I chose to write only first 4gb or so due to smaller sdcard I had. That covered all partitions except cache and userdata, which were not needed anyway). Then I wrote back the dump on the bricked d850 using dd command from terminal. I tried flashing TWRP on it first, but somehow it did not work, and gave secure bootloader error. So I had to do it via terminal. I knew once it starts writing, the system would become unstable due to overwriting of partition table, kernel, system, and stuff, but I had to give it a try, and it worked! Screen went off immediately, but I touched it again after half an hour; pulled out and reinserted the battery; tried recovery and there it was. Rest was easy. Just formatted cache and data, and my phone was back to life.

My galaxy note 3 (SM-N9005) with a custom rom can't see my sim card. How to fix?

This is a bit of a longer story, but i'll try to make it brief.
I have a samsung galaxy note 3 (SM-N9005).
A few days ago, when I was deleting system bloatware and I must have also deleted some important parts of the system.
My homescreen stopped working and i couldn't see my phone when i connected it to my pc which is running win-10 (more on that later).
Unfortunately i didn't keep any backups, yes I was reckless.
Factory resetting with my default recovery mode didn't help at all.
After some time i managed to install twrp (team win project recovery) and flashed ressurection remix 5.8.5 (unofficial version from Lord_Eko) along with Magisk and the correct Gapps.
Everything is working fine except that I cant see my sim card (thus i can't call or text anyone) and I still can't see my phone when connecting it to my pc.
I wanted to try installing some firmware for my sim card or try flashing stock firmware before my custom rom but I can't, since I have to use bootloader/download mode for that.
I tried using Odin (v3.13 and v3.09) while in download mode, but it can't see my phone. Neither can Android debug bridge when using command "adb device" or "fastboot devices" (it just says list of attached devices and nothing).
Connecting my phone normally doesn't work either. My phone isnt even listed in device manager as an unknown device.
I even tried installing samsung usb drivers, but to no avail. My phone only gets charged from my pc.
I tried all sorts of things i don't even remember now, but none of them helped.
I read something about an IMEI being deleted and when i checked my IMEI through an app it was blank, so it seems to have been deleted.
My battery also keeps draining quite a lot, but that's probably because of how old it is.
I don't know anymore info i can give, so please, how do I get my simcard to work?
Thanks for any help and sorry if I posted this in the wrong section. <3

Alcatel Joy Tab 1/3T 8 - "System UI has stopped"

Hi all, I have an Alcatel Joy Tab that's all of a sudden decided to keep looping this error.
Error only pops up outside of the lock screen: on the lock screen, I'm able to swipe down the notifications bar and enter settings from there. Additionally, UI seems to be functional in the Camera app as well.
I've already factory reset once, and it was back to normal for a little while, but then it came back again. Any suggestions?
Specs:
Alcatel Joy Tab 1
Model 9027W
Android 8.1.0
Baseband version MT6739
Kernel Version 4.4.95

Most times the sole reason behind the issue “Android System UI Has Stopped” is the improper installation of the OS update or the corrupted one.
Hence do a clear re-flash of Stock ROM.

jwoegerbauer said:
Most times the sole reason behind the issue “Android System UI Has Stopped” is the improper installation of the OS update or the corrupted one.
Hence do a clear re-flash of Stock ROM.
Click to expand...
Click to collapse
Thanks for the reply, I've been looking for a stock ROM since I first had the issue. However I haven't been able to have any luck finding one. Do you have any suggestions on where to look? If I ultimately still can't find one am I SOL?
I've heard that you can just return to stock by using Alcatel's official Mobile Upgrade tool here but it keeps giving me a message saying that the version I'm using is the most updated version.
Software Drivers - Alcatel
Software Drivers
www.alcatelmobile.com

I would like to know more about this too. Same issue with poster. Any custom roms or anything out there for this?

No custom ROMs. There is one out there that is unlocked. But, I've lost the post about it. Used it to carrier unlock mine. Haven't had the time to see if it unlocked more.

This issue happens to me. Going into settings and removing the screen lock solves it (but obviously no screen lock). Formatting data allows you to use a screen lock for a while, until the issue decides to pop up again. Usually though it followed doing something like installing xposed framework or something advanced like that. But other times it seemed it may have been a result of booting my custom TWRP image. It's built from a generated device tree so it's not perfect yet.
Edit to add: I modified my fstab and removed the metadata encryption entry for userdata. I haven't seen the issue appear since. Encryption is now gone, but this thing is pretty weak as it is and I don't generally keep data that needs encrypting on it.
Edit: "SystemUI has stopped working" is solved with the latest firmware. If you can't get latest firmware (The alcatel mobile upgrade tool kept telling me I was on the latest or it would just crash) Do a google search for MTK Sugar Tool. Versions after 2018 will force the latest updates to the device over usb
Now for a better bit of info I have:
Bootloader unlock and proper Magisk root is possible on this device. In order to get to fastboot to unlock bl:
1. If you have basic experience with python, you can use this script to boot to fastboot:
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones - mtk-bootseq.py
gist.github.com
2. RISKY: If you are inexperienced, need to unlock bl, and have good AV software (This is how I did it the first time, but be warned: while my up-to-date installation of Kaspersky found nothing today (10-31-21), Virustotal.com showed that around 18 databases flag this program for trojan like behavior):
Search google for "MTK Boot Mode Selector Tool by mvirus team". There are several links available all over shady blogs and such. This tool does work and is a simple exe, requiring only that proper alcatel USB drivers and fastboot drivers are installed; However, it's sketchy as hell and I suggest you read up on python and just use the first option.
I AM NOT RESPONSIBLE FOR DAMAGE CAUSED BY POTENTIAL VIRUSES IF YOU USE THE SECOND METHOD
Use either method (but you should really learn how to run python scripts and identify the path or name of serial ports in linux or windows (respectively) and use the first method) to get to fastboot and bl unlock like normal.
In windows it's just a matter of rebooting your tablet while holding volume down and watching in device manager for the correct COM port number to enter as a parameter of the command. (I.E. COM7.) Once you have the port number, you send it to the script as a command.
I.E.:
Code:
python mtk-bootseq.py FASTBOOT COM7
To get the port number in windows:
My tablet rebooted three times and reconnected while holding the volume down key. Each time it reconnected, a new entry in the device manager named "Ports (COM & LPT)" appears. This will disappear as soon as it disconnects, which seems to be after something like 3 seconds, so you have to be actively watching. If you expand "Ports (COM & LPT), after the first two boots, "MTK USB Port (COM*)" will appear, with * being a number (I.E. COM7.) On the third boot, "Preloader USB VCom Port (COM*)" will appear. This is the COM port number you are after. It will likely be different than the port number of the first two, which were identical for me.
I may make a full tutorial on both the linux and windows python methods soon (though it's pretty simple if you have basic experience with python,) but it doesn't seem like demand for bootloader unlock on this device is very high. (I have put a lot of work into this post already, however.)

cheger32 said:
This issue happens to me. Going into settings and removing the screen lock solves it (but obviously no screen lock). Formatting data allows you to use a screen lock for a while, until the issue decides to pop up again. Usually though it followed doing something like installing xposed framework or something advanced like that. But other times it seemed it may have been a result of booting my custom TWRP image. It's built from a generated device tree so it's not perfect yet.
Edit to add: I modified my fstab and removed the metadata encryption entry for userdata. I haven't seen the issue appear since. Encryption is now gone, but this thing is pretty weak as it is and I don't generally keep data that needs encrypting on it.
Now for a better bit of info I have:
Bootloader unlock and proper Magisk root is possible on this device. In order to get to fastboot to unlock bl:
1. If you have basic experience with python, you can use this script to boot to fastboot:
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones - mtk-bootseq.py
gist.github.com
2. RISKY: If you are inexperienced, need to unlock bl, and have good AV software (This is how I did it the first time, but be warned: while my up-to-date installation of Kaspersky found nothing today (10-31-21), Virustotal.com showed that around 18 databases flag this program for trojan like behavior):
Search google for "MTK Boot Mode Selector Tool by mvirus team". There are several links available all over shady blogs and such. This tool does work and is a simple exe, requiring only that proper alcatel USB drivers and fastboot drivers are installed; However, it's sketchy as hell and I suggest you read up on python and just use the first option.
I AM NOT RESPONSIBLE FOR DAMAGE CAUSED BY POTENTIAL VIRUSES IF YOU USE THE SECOND METHOD
Use either method (but you should really learn how to run python scripts and identify the path or name of serial ports in linux or windows (respectively) and use the first method) to get to fastboot and bl unlock like normal.
In windows it's just a matter of rebooting your tablet while holding volume down and watching in device manager for the correct COM port number to enter as a parameter of the command. (I.E. COM7.) Once you have the port number, you send it to the script as a command.
I.E.:
Code:
python mtk-bootseq.py FASTBOOT COM7
To get the port number in windows:
My tablet rebooted three times and reconnected while holding the volume down key. Each time it reconnected, a new entry in the device manager named "Ports (COM & LPT)" appears. This will disappear as soon as it disconnects, which seems to be after something like 3 seconds, so you have to be actively watching. If you expand "Ports (COM & LPT), after the first two boots, "MTK USB Port (COM*)" will appear, with * being a number (I.E. COM7.) On the third boot, "Preloader USB VCom Port (COM*)" will appear. This is the COM port number you are after. It will likely be different than the port number of the first two, which were identical for me.
I may make a full tutorial on both the linux and windows python methods soon (though it's pretty simple if you have basic experience with python,) but it doesn't seem like demand for bootloader unlock on this device is very high. (I have put a lot of work into this post already, however.)
Click to expand...
Click to collapse
Bootloader Unlock failed. Is there any solution?

Azukegi said:
Bootloader Unlock failed. Is there any solution?
Click to expand...
Click to collapse
Did you enable OEM unlock in developer settings first?

cheger32 said:
Did you enable OEM unlock in developer settings first?
Click to expand...
Click to collapse
I eventually got it, but there's a patch for this device preventing any root and on top of that there's no custom recovery for this device :/

Azukegi said:
I eventually got it, but there's a patch for this device preventing any root and on top of that there's no custom recovery for this device :/
Click to expand...
Click to collapse
Really? I built TWRP for it, I can send it to you if you want to try it. What block is there for installing root? Originally I used a temp root to get the boot image (There should be a few exploits currently available in the latest Android release for this tablet, at least enough to dd the boot partition) and then patched it with magisk, then once I found the MTK bootseq script I flashed it with fastboot. Didn't need TWRP at all. If we have the same firmware version I could also just send my currently patched boot image.

cheger32 said:
Really? I built TWRP for it, I can send it to you if you want to try it. What block is there for installing root? Originally I used a temp root to get the boot image (There should be a few exploits currently available in the latest Android release for this tablet, at least enough to dd the boot partition) and then patched it with magisk, then once I found the MTK bootseq script I flashed it with fastboot. Didn't need TWRP at all. If we have the same firmware version I could also just send my currently patched boot image.
Click to expand...
Click to collapse
Dude no way, I would love to get that TWRP from you if possible

Azukegi said:
Dude no way, I would love to get that TWRP from you if possible
Click to expand...
Click to collapse
TWRP 3.6.1 for Alcatel 3T 8 (Maybe also generic Joytab 1?)
I built this last night, seems to work well. Let me know if there are any issues. This will be my last post in this thread as I've gotten off topic. I'll create a new thread with a guide if I find the time.
This is built from a twrp compatible device tree generated from a recovery image with a few modifcations and corrections. The kernel was built from sources released by alcatel (it took me nearly a year and some legal threats to get them to release it to me.)
just flash that to recovery in fastboot mode:
Code:
fastboot flash recovery <img filename>
Be sure to make a backup of your original if possible.
I just remembered that there's a bypass method and a useful utility in existence (located here: http://www.mediafire.com/file/qtmkilaimympapf/mtk_bypass_rev4.7z/file) for enabling the use of spflashtool to make backups and even flash images without fastboot with this device. Sorry, I'm still dusting the cobwebs off of this project.
EDIT: 23 builds later and I fixed /data decryption. As I said this will be my last post here but in case I never make a formal thread, here is a fully working twrp.
Edit again: I realized adb push and sideload wasn't working so I fixed it. Here's the latest build

I've got a 3T that I use rarely and it seems if I leave it for a while I get the same lock screen issue. I've discovered mention of a T-Mobile update that might resolve this:
Does anyone know where I can get this build and if I can force it on to my 3T. My carrier has no updates available.
Android 8.1.0
Build number: 1AWKUMK0May 14, 2021Resolves issue preventing device unlockAvailable May 14, 2021
Devices that meet the update requirements can be upgraded to the current software version.

So, I'm having the same problem. Just bought the joy tablet on Amazon. Yesterday it was working fine, then this morning got this error. I can't unlock the screen. If I use the pulldown menu I can click on one thing before the error pops up and the screen goes black then back to lock. I can't do anything on the tablet at all. Since I just bought it, should I just return it?

mnpeaches78 said:
So, I'm having the same problem. Just bought the joy tablet on Amazon. Yesterday it was working fine, then this morning got this error. I can't unlock the screen. If I use the pulldown menu I can click on one thing before the error pops up and the screen goes black then back to lock. I can't do anything on the tablet at all. Since I just bought it, should I just return it?
Click to expand...
Click to collapse
If it's too late to return it you can put it in recovery mode and try to restore it that way if that doesn't work then you can reflash it with SUGAR MTK SP

mnpeaches78 said:
So, I'm having the same problem. Just bought the joy tablet on Amazon. Yesterday it was working fine, then this morning got this error. I can't unlock the screen. If I use the pulldown menu I can click on one thing before the error pops up and the screen goes black then back to lock. I can't do anything on the tablet at all. Since I just bought it, should I just return it?
Click to expand...
Click to collapse
You can try SUGAR MTK SP

[TB-8504X] No WiFi or Sim card after restoring stock rom with Lenovo Rescue and Smart Assistant

Hello There,
I was trying out LineageOS 17.1 on Lenovo Tab4 8, 8504X, 8MP Rear camera model. Everything was fine except the very low volume during audio playback. I was trying to follow the volume fix guides and while in adb shell, device kept crashing. So I tried restoring the factory image using Lenovo Rescue and Smart Assistant. It downloaded and flashed the firmware image, but I saw afterwards, wifi was not working. After a few more attempts, the SIM card also stopped working. Now the device has no connectivity.
I did an oem lock after flashing the stock firmware, now I am not able to use fastboot to flash images. QFIL tool works. The stock firmware version flashed by the tool is TB_8504X_USR_S001024_1909061423_Q12000_ROW_SVC. I am not sure if this is the correct one. Does anyone have the same device with stock ROM? Or can someone please point me to the stock ROM image where things work? The region is India.
Thanks in advance,

Checking further, the baseband version is shown as unknown. Is there an image file that can be flashed to fix this ?
EDIT: Now I understand the QCN needs a restore Does anyone have a copy ?

I wanted to update on the thread on how I managed to fix this. I tried the whole thing again, so that I can make sure.
Using the same QFIL tool, I flashed TB_8504X_USR_S001024_1909061423_Q12000_ROW_SVC firmware. This helped booting back to the system. This also enabled diag mode and adb by default on the tablet. That was a big relief. I noticed that wifi is not working and not turning on during the initial setup. I completed the setup and did
Code:
adb reboot bootloader
Once in fastboot mode, I did
Code:
fastboot flash persist persist.img
I used the persist.img from the same firmware folder. Once I turned on the device, WiFi and Bluetooth were working. Since diag port was already on, I used the backup and restore QCN option in QFIL to flash TB-8504X[MPSS.JO.2.0.c1-00151-8937_GENNS_PACK-1].qcn.
I tried may QCN rebuilder tools, but this QCN file seems to be not conforming to the format they expect and they kept gaving error. So I flashed the QCN as it is, rebooted the device and then used a tool named "WriteDualIMEI-W-G-eMMC" to program the IMEI number. This worked perfectly and I have network back.
When I was trying to do this again, for some reason, Sahara errors kept popping up and none of the tools were able to access the device. I found that was because of the driver I used. It wasn't the same ones I used first time. But I used the QDL tool from Linaro in linux and flashed the images with it. It worked perfectly.
I wasn't able to restore the tablet serial number though. Couldn't find a way to do that.