Database Info

[Q][Help]Nexus S major problems

SOLVED
Well I hope my Nexus S didn't brick. Well I will start off with what happened. I've been running ICS Slim for a while and I noticed it started to become very buggy. Been busy for a few days so I havnt had time to fix anything. Well today I had some free time so I was going to just connect my SNS to my pc to transfer important files and pictures. My PC (Windows 7) kept giving me "USB Device not recognised" errors. I have correctly installed the adb drivers and have connected my SNS to the same computer. I also tried another connection usb cable to see if my original was defective but no avail. I also tried my netbook with both usb cords becuase I also had this SNS connected to the netbook before (Win7 Also) with correct adb drivers.... still nothing. I then go to rom manager download codename android and successfully install the rom. Tried everything again and still no connection. After shutting down the SNS and strating it again multiple times and trying multiple things my SNS went into "safe mode". Curious I thought there must be something wrong with some system files that don't get written over when a new rom is installed with a factory reset. I decided to turn off my SNS and turn it on one more time and I get this screen which ive never seen before.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It also says between Downloading.... and Do not turn off target!!!!:
USB Control Init
USB Control Init end
Please help because I need this phone for work and I cannot afford a new one... Just really hope it didnt bite the dust.
Samsung Nexus S i9020a Koodo
FIX:
had the same problem. DEFINITELY FIXED NOW.
Whenever, I connected my Nexus S to any OS a USB Storage Mode dialogue used to pop up and once I clicked Turn On, the PC would find the mass storage. About a week ago, this functionality has stopped completely. I plug the USB cable and nothing happens but the phone starts charging.
I have read many posts about this. I have tried the removing the battery, Rebooting, Trying the boot loader screen, erasing the USB storage, resetting to factory settings, Erasing and dismounting the SD Card from the Boot loader, cleaning the USB Port, trying different USB cables (nokia, parrot, original Nexus etc)....
What has worked for me was the NEEDLE trick. Get a needle and bend the USB hub beneath the phone towards to the top. (What I realized is that it was pushed all the way to the bottom, lifting it up about 1 mm has centered it). I plug the USB and pops up the USB storage mode interface.
So, it turns out a hardware issue, probably a doggy USB port on the NEXUS easily gets disturbed. Using different cables usually helps the problem, especially cheap cables tend to damage the port easier.
So, I would recommend every one to use proper USB cables; the original nexus cable, a nokia cable or decent quality cable. (Do not use the ones from cheap car chargers etc).
Secondly, do not reset your phone for nothing.
Thirdly, keep your phone clean.
I hope this information helps someone. Thanks.
Click to expand...
Click to collapse
source: http://www.google.com/support/forum/p/Google Mobile/thread?tid=4dedeb14b7ccb58e&hl=en

Update: Decided to turn off the Nexus S..... Stupid idea I guess because It wont turn on any more.... Plugging into a computer still says "USB Device not recognised" though so I have no clue...
Would really love some help please

Can you get into recovery? Or Hboot?

rocket999 said:
Can you get into recovery? Or Hboot?
Click to expand...
Click to collapse
No recover. Whats Hboot? No fastboot screen... So I thinks its dead.

Trying unbrickable resurrector but cannot find device
Desperate need of help please

do you have CWM installed on your nexus??
use mount/storage then connect it to Computer

galaxy tab p1000
this screen shot is the same of download mode in the galaxy tab p 1000, in this mode, with program "ODIN" you can put in your device the rom, kernel and radio! ww w.team overcome.net/p1000/?page_id=17 this is a guide for flash the p1000, i don't know if that function for NS ! I'm sorry.

[Q][Help]USB Problems
I just removed my simcard and reinserted it again and my phone started normally.... weird...
But still at problem #1. Cannot mount usb. Windows 7 Still says "USB device not Recognised". My guess is that the usb port is broken. Its quite common apparently so i'm gunna see if Koodo will fix it.
Before I send it in should I go to a stock rom, stock baseband, and lock bootloader. or can I send it in with CyanogenMod 9?

Tw1tchy said:
I just removed my simcard and reinserted it again and my phone started normally.... weird...
But still at problem #1. Cannot mount usb. Windows 7 Still says "USB device not Recognised". My guess is that the usb port is broken. Its quite common apparently so i'm gunna see if Koodo will fix it.
Before I send it in should I go to a stock rom, stock baseband, and lock bootloader. or can I send it in with CyanogenMod 9?
Click to expand...
Click to collapse
go back to stock and lock bootloader so they wont void your warranty

sean1984 said:
go back to stock and lock bootloader so they wont void your warranty
Click to expand...
Click to collapse
Thx but I fixed my USB port myself ! But if I ever have problems again I will remember what you said.
Posted my fix on the OP

nexus s usb not recognized
sir, plz help me i have a nexus s i9023 i have tired everything like format system boot sd card cache everything so i think that my nexus s should recognized windows after thes. but now nothing effect and i can acces anythink just fastboot or clockwork mod recovery i have also noticed that when i pluged usb cable on nexus s with computer it stays on charging but after on fastboot my laptop not recognized my nexus s but the charging option is enable so i can ensure that there is no hardware problem i have charged nexus s through data cable but not recognized on coclworkmod i have also try to unmout sd card or usbstorage but nothing effect plz help me

Thanks for the thread.
" Needle trick " worked perfect. [ lifting the usb charging pin - with a needle - on the phone so its center. ]

Hard bricked my OnePlus One by just rebooting it, help! [5$ REWARD]

I will be straightforward:
I bought an used OPO, I booted it up, configured the phone, took a photo and then decided to reboot it (turn off and then turn on), then my device simply hard bricked.
1. I already tried turning it on, the device does nothing (no vibration).
2. I already tried using Power + Vol Up and Power + Vol Down, nothing happens (no vibration).
3. Windows recognizes the device as "QHSUSB_BULK", I already tried installing the drivers and using ColorOS flashing tool from here http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , the device IS RECOGNIZED by the tool, but when I start flashing, it starts a loop when trying to flash the "8974_msimage.mbn" file (the progress bar goes until the end and then the process repeat in the same file).
Yes, the device has the bootloader unlocked, because the previous owner flashed a custom ROM, custom kernel and SuperSU.
No, the device isn't recognized by adb.
No, the device isn't recognized by fastboot.
I already tried searching on Google for this issue, everyone who had this issue never replied saying that they fixed the issue...
I never had any kind of soft/hard brick on my Moto G 2014 (and I flashed custom ROMs constantly on it)... so... can someone help me? Thanks!
I'm also willing to give 5$ on PayPal to someone who can fix this issue.

Also, if I try to use the ColorOS flashing tool, the device disconnects in the middle of the process, causing the infinite flash loop.

First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English

sino1641 said:
First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English
Click to expand...
Click to collapse
Nah, your english is fine, I could understand what you are saying.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After I clicked "Start"
Then the "device plugged in" sound plays and the process repeats...
It keeps doing this:
(If you can't view the images, click here:
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-39-42.png
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-40-18.png
http://lori.mrpowergamerbr.com/sharex/2016-07-22_10-41-05.gif
)

Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.

sino1641 said:
Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.
Click to expand...
Click to collapse
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers

MrPowerGamerBR said:
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers
Click to expand...
Click to collapse
Open Device Manager.
Press Power &Vol Up for about 10 seconds.
See if it will change between 9008 and 9006.

I have same thing did it work
I am just wondering if u managed to fix it.

I had the exact same issue. To stop the device from disconnecting, I needed to remove all existing drivers, let the phone charge, plug it into the PC. Hold volume up + power until the PC recognises it. Then I used the color OS flashing tool.
I had to run it as administrator, and it worked fine on Windows 10, without anything extra. However remember you'll lose all your stuff. Lucky for me I had a backup of my entire phone on my PC when I switched file system to F2FS.
This issue in itself has really baffled me. It happened to me when flashing sultans rom, and the phone completely bricked. However I'm using the rom now after fully recovering the device... I guess it's just down to bad luck?

mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Nope, never fixed it, I don't even have the device anymore (now rocking a Moto G Turbo)

mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Don't use "msm8974-download-manager" use qfil to recover the phone. Worked for me.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/

Download 2012 qhs diagnostic driver and use xp machine.It will work just fine.

install a fresh windows either x32/x64 winxp/win 7 extract color OS and install the correct drivers

[Help][xperia f3113][dead]

Hello, excuse my bad english I'm using google translate.
The problem I have is that my xperia xa is dead.
the reason of it, was that I wanted to flash the rom of my cell to remove the applications that come with the mobile company.
when I realized my error, was that I did the following, in the flash tool, in the rom selection, I made the error, not selecting the following settings:
-APPS_LOG
-DIAG
-QNOVO
-USERDATA
-CUST-RESET
as shown in the following image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
when the flash operation ended, the cell phone did not want to turn it on, the only function it had and has so far, is that it does not vibrate, it does not turn on, it does not go into flash or fastboot mode, it's dead, it just turns on the red led.
when I try to perform the flash operation again, I simply get the following message when I connect the device.
in the windows device manager, recognizes the phone as "usb serial device (com)".
I searched the net, and I did not find the solution to this problem, I appreciate your attention, and I expect some help.
PD: I already tried the connection with pc companion, and even the function from system symbol of windows with the tool fastboot to flash the boot, with the img.
the problem is that the device does not go into any mode

1990macsfull said:
Hello, excuse my bad english I'm using google translate.
The problem I have is that my xperia xa is dead.
the reason of it, was that I wanted to flash the rom of my cell to remove the applications that come with the mobile company.
when I realized my error, was that I did the following, in the flash tool, in the rom selection, I made the error, not selecting the following settings:
-APPS_LOG
-DIAG
-QNOVO
-USERDATA
-CUST-RESET
as shown in the following image:
when the flash operation ended, the cell phone did not want to turn it on, the only function it had and has so far, is that it does not vibrate, it does not turn on, it does not go into flash or fastboot mode, it's dead, it just turns on the red led.
when I try to perform the flash operation again, I simply get the following message when I connect the device.
in the windows device manager, recognizes the phone as "usb serial device (com)".
I searched the net, and I did not find the solution to this problem, I appreciate your attention, and I expect some help.
PD: I already tried the connection with pc companion, and even the function from system symbol of windows with the tool fastboot to flash the boot, with the img.
the problem is that the device does not go into any mode
Click to expand...
Click to collapse
2 times so far, my XA died the same way after trying to flash a mod. Both times I was eventually able to resurrect it by holding down various combinations of buttons while plugging and unplugging, trying different cables, etc. The second time, it wouldn't do anything until the next day, and then it suddenly came to life when using a different cable and plugging into the wall while holding power and volume down. I would try it. I'm not too familiar with flashtool on XA. I have used it for 3 years with my Z1c and never hard bricked a phone with it. Seems like X series have a little bit different rules, but I don't see why your phone would hard-brick just because you didn't wipe a few partitions... Also good idea to check in with FT thread.

If the computer does recognize it, maybe you need to reinstall your usb drivers. If its not, then u have a big problem with it, before making anything you need to see if there is a way to connect it by Fastboot, and install his custom TWRP. if u are able to do that, there is a sollution for you.
Remember always to install your usb flash drivers, and the fastboot drivers too.

Same problem my XA F3113 is dead. The LOG says everything was ok but after disconnect it from PC the phone dies.
Look like exist a way to get it back to life but we need the SCATTERED FILE.
Can somebody share us the SCATTERED FILE of this Model?

Really appreciate this guy....
Awesome person. He had recover my dead XA ultra through online. Just with 500 INR.
wrundawan said:
Whats app me +918147499618 I can help you to fix your dead phone.
Click to expand...
Click to collapse

i have a same problem
please help. my phone f3113 is dead after downgrade

wrundawan said:
Whats app me +918147499618 I can help you to fix your dead phone.
Click to expand...
Click to collapse
Be careful this guy is a cheater he cheated $30 from me

Who the hell has cheated you?
Check your paypal with your open eyes since you had raised claim on your money inside paypal your money was refunded by them. And I am helpless as I didn't got your money.
mballe francois said:
Be careful this guy is a cheater he cheated $30 from me
Click to expand...
Click to collapse

mtk scatter

I think I killed my brand new phone

I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.

Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David

DvdStrbl said:
Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David
Click to expand...
Click to collapse
Well see the issue is I'm trying to get All in One to recognize my phone but it won't seem to boot into EDL mode. I installed the Qualcomm USB drivers but it's still not showing my phone. When I use the key combo suggested to boot into EDL mode my phone does refresh in device manager giving me the qualcomm device so I assume this is download mode just not displaying the text anymore. If i try the key combo with my phone unplugged it takes awhile but eventually goes into fastboot.

In this case I can't help you, i googled EDL, it is what I meant and it was all I got :-/
Wish you good luck

If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424

Bradl79 said:
If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
When I try flashing anything at fastboot it just hangs waiting

viralhysteria said:
I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.
Click to expand...
Click to collapse
what the problem u are facing while flashing from msm tools?

If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.

whoamanwtf said:
If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.
Click to expand...
Click to collapse
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date

Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.

viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
During Installing drivers again choose the option (something of) search from internet. And let the file be downloaded and install. Trust me this method works. I too had same problem

whoamanwtf said:
Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.
Click to expand...
Click to collapse
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?

viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
viralhysteria said:
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good. It's Android 9 but that doesn't matter, you can update from there once your phones working again.

whoamanwtf said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good.
Click to expand...
Click to collapse
It says to wait about 5 minutes after starting but I get stuck at this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work

whoamanwtf said:
Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work
Click to expand...
Click to collapse
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?

viralhysteria said:
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?
Click to expand...
Click to collapse
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.

whoamanwtf said:
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.
Click to expand...
Click to collapse

So it sounds dumb but try rebooting your computer and switching USB ports then trying again.

whoamanwtf said:
So it sounds dumb but try rebooting your computer and switching USB ports then trying again.
Click to expand...
Click to collapse
Same thing it just assigned a new COM port

[SOLVED] Lenovo TAB 2 A7-20F Hard Brick (Dead)

I wanted to update Lenovo TAB 2 A7-20F trough SP Flash tool since Android 4.4.2 is really old and kind of useless. I started flashing Lollipop update but after some time flash tool showed error that I can't remember. The device got bootloop. I have seen that I have putted to "Download Only" mode in flash tool instead of "Firmware Update" or "Download Only + Format All", so I tought that's the reason why my device got bricked . Now Instead of just flashing ROM again I used Format Tab in SP flash tool and formated Tablet. And now it's hard bricked. It's not charging or turning on. Not detected by PC when pluged . I tried opening it and removing battery and trying different key combo to put it in META mode since I think preloader is formated as well. If anyone has any idea how can I fix it please replay. I watched youtube tutorials that didn't help . I probably missed something so send help . I guess I have to learn hard way.
IF you want specs here they are:
Lenovo Tab 2 A7-20 - Full tablet specifications
www.gsmarena.com

try to open and search for kcolo or colo + gnd in motherborad and make a jumper and its gonna back to life after that try to flash this rom
like in the image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lenovo_Tab_2_A7-20F_MT8127_S000011_160318
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

Ugh...
I think I have problem. I know for kcolo and gnd method but just take a look at this picture.
This is motherboard of my tablet. Most of points aren't labeled and bruteforcing them could damage motherboard. And there is this big heatsink I guess so , maybe it's under there...
I did find stock ROM, only problem is that it's not detected in device manager at all.

Here is the image the closeup image without heatsink.
These are all contact point I could find. There are 9 total. 4 of them near USB port , 3 near battery plug at bottom that you can't rly see but they are unlabeled , and 2 more that I am not sure about what they do. One of them is near camera and other near sd card reader. Not even sure if these are possible test points.

I was able to find and join kcolo ( volume + and volume - points in my case). Now the problem is that after installing driver and trying to flash I get error 4032 in sp flash tool. I tried older versions but they don't support it;
I tried different drivers but didn't help. If anyone can help pls replay.

Nem1x said:
I was able to find and join kcolo ( volume + and volume - points in my case). Now the problem is that after installing driver and trying to flash I get error 4032 in sp flash tool. I tried older versions but they don't support it;View attachment 5557329
I tried different drivers but didn't help. If anyone can help pls replay.
Click to expand...
Click to collapse
Can you provide a picture or explain what you did? I cant seem to find the kcolo/colo and ground pins i need to connect. I would aprechiate it a lot if you gave me an explanation on the process!

You kinda destroyed the whole software by using the format tab. If you didn't, you could've still reinstalled the stock ROM. I have a Lenovo Tab 2 A7-10F that was bricked itself, but I have no idea what's going on

ImmortalChanger said:
You kinda destroyed the whole software by using the format tab. If you didn't, you could've still reinstalled the stock ROM. I have a Lenovo Tab 2 A7-10F that was bricked itself, but I have no idea what's going on
Click to expand...
Click to collapse
Im in a similar situation, i flashed a Lenovo Tab 2 A7-10F rom at Lenovo Tab A7-20F. Tablet wont get recognized by a computer, nor boot nor show any signs of life. Its like this for 1,5 year. Is it possible to bring it back to life?

zisinikos said:
Im in a similar situation, i flashed a Lenovo Tab 2 A7-10F rom at Lenovo Tab A7-20F. Tablet wont get recognized by a computer, nor boot nor show any signs of life. Its like this for 1,5 year. Is it possible to bring it back to life?
Click to expand...
Click to collapse
It’s complicated. The Lenovo Tab 2 A7-10F and 20F are different tablets, so the ROMs compatible with either won’t be compatible with the other. First, make sure the battery is somewhat charged. The energy transfer should depend on the hardware, not the software. I did unbrick my 10F recently but I was able to power it on and the PC recognised it, although it took some time to find the right drivers. Assuming you’re using Windows, have you checked in Device Manager to see if the device is present? I had the same issue where I couldn’t interact with the tablet from the PC but that was because of the absence of drivers. I don’t know precisely what can be done if it doesn’t even turn on, but it could just be a dead battery (that is, if you haven’t tried to hook it up to the charger).

I was able to completely fix and update tablet to Android 5. The golden points are located at back of the motherboard:
The two points at the bottom when connected should make your device recognized in device manager.
After that you install mediatek drivers onto that device and flash stock rom with SP Flash tool.
I unbricked it more than 2 months ago but I was lazy to write this so sorry for waiting.

ImmortalChanger said:
It’s complicated. The Lenovo Tab 2 A7-10F and 20F are different tablets, so the ROMs compatible with either won’t be compatible with the other. First, make sure the battery is somewhat charged. The energy transfer should depend on the hardware, not the software. I did unbrick my 10F recently but I was able to power it on and the PC recognised it, although it took some time to find the right drivers. Assuming you’re using Windows, have you checked in Device Manager to see if the device is present? I had the same issue where I couldn’t interact with the tablet from the PC but that was because of the absence of drivers. I don’t know precisely what can be done if it doesn’t even turn on, but it could just be a dead battery (that is, if you haven’t tried to hook it up to the charger).
Click to expand...
Click to collapse
Thanks for the help but unfortunately I've already lost all hope. Ive tried everything. I don't really care about the device that much so it doesn't bother me.

zisinikos said:
Thanks for the help but unfortunately I've already lost all hope. Ive tried everything. I don't really care about the device that much so it doesn't bother me.
Click to expand...
Click to collapse
Have you tried the method I showed above? Maybe your drivers are not installed correctly. Windows should detect device even without drivers and you will hear the connected sound, just like you pluged your USB in.

Nem1x said:
Have you tried the method I showed above? Maybe your drivers are not installed correctly. Windows should detect device even without drivers and you will hear the connected sound, just like you pluged your USB in.
Click to expand...
Click to collapse
I am the guy that contacted you on telegram a while back. I have indeed tried your method but no luck in there.

zisinikos said:
I am the guy that contacted you on telegram a while back. I have indeed tried your method but no luck in there.
Click to expand...
Click to collapse
Ohh.. yeah. I don't really look who replied to thread.