It's a Voyo's i8 pro 4G, i downloaded the officialy android 7 rom and used sp flash tool to flash the rom.
I choose the official scatter file and it'd loaded successfully.
I clicked download and connected my "power-off" tablet to win 10 via USB, it quickly recognized my tab and showed hardware info on the bottom right...
i went on for a sec and then a windowed message popped up that said something about "download...", it disappeared quickly and then everything stopped, nothing change on progress bar ....
i waited for a while and decided to quit... disconnected my tab and close the program, hoping to start everything again...
no USB detection of my tab, the tablet doesn't even turn on now, screen is all BLACK...NOTHING.....
tried to installed MTK USB driver in win 10 ( followed online guides) but got code 10....
May I ask what else I can do now? any advise will be greatly appreciated! THX!
Just reflash with SP-Flash Tool. If SP-Flash Tool doesn't detect your device you need to unplug the Battery and connect it after that to your PC
Related
Hello to all community,
strange things happened here... I use a Star H920+ phone. I had some problems with Bluetooth and Wifi, so i decided to flash rom again. I downloaded the rom from needrom dot com. (As new user, i cannot post the full url yet)
I used Smart Flash Tools to do the job. Firstly i had some difficulties getting some errors. After some search, i used MtkDroidTools and i got the right sizes for memory and write them at scatter file. The procedure went well and i got a green circle at Flash Tool.
And that's it...
After that, i get the absolute Black. But... the strange thing is that the Windows detects the phone. I tried every combination to get into recovery mode, but nothing. Only black screen.
I tried Flash Tools again to flash it with the same or an older rom, but after the some seconds, the application is not responding and Windows says that the Smart Flash Tools application has stopped responding and must be closed.
MtkDroidTools doesn't recognized the phone now.
But, as i have it connected with the pc, the sound of plug and unplug a device is heared all the time. ( Maybe it is rebooting continuously )
I hope that the hoping thing is that Windows detects the phone, but i cannot do anything more...
Do you have any idea to propose me ?
Thank you very much,
Periklis
This sub-forum is for the HTC Droid Incredible. Please post in the appropriate forum. Thread closed.
Hi
LG G3 D855 OS Android 5 V21c-TWN-xx
I am trying to upgrade to MM via the subject Flash Tool but it gets as far as 15% and then a Window pops up telling me
that the Phone has been disconnected and to reconnect and retry.
The phone is still connected and showing as such in explorer. I re-installed the drivers and still the same problem.
Tried compatibility mode Win 8 and the same thing happens. Anyone have this problem in Win 10 or know of a way round it.
I also have a WIn 8.1 Laptop which I used to update to the current OS with Flash Tool 2014 but it is now stopping and giving an error
"This programme has stopped working MS is checking Blah Blah"
Stransky
Having the same issue here with D852
Reinstall G3 usb drivers
hi, have you tried LGUP method? http://forum.xda-developers.com/showpost.php?p=64624353&postcount=3
I used windows 7 and usb 2 ports.
twisted_twice said:
hi, have you tried LGUP method? http://forum.xda-developers.com/showpost.php?p=64624353&postcount=3
I used windows 7 and usb 2 ports.
Click to expand...
Click to collapse
LG Up shows phone as "unknown" no matter what I do.
I also have a G Flex 2 and this shows up ok in LG Up.
Sent from my iPad using Tapatalk
I downgraded from MM to LP two days ago. I had the little window saying "unknown "
The problem was that windows wasn't seeing my phone. I unplug the cable and plug it back and it worked. As I wrote before I am using windows 7.
Hi
Managed to get LG Tool 2014 to work and D855 now on v30b (MM) global.xx. Problem was driver related. I downloaded Win 10 G3 specific driver from LG site and everything then worked.
good to know pal.
i have lg g2 mini
the keyboard dos not start and my phone has number password
what can i do to restor my phone?
it is not root
I have windows 10 pro and i get same problem, i have solved this with driver usb install (sorry for my poor english)
Found my old LG-VS450PP Optimus Exceed 2 for Verizon. It was working fine when put away.
Charged the battery on a working phone (same model) but this recently resurrected phone will not boot up. Same results using vol+ / power or just power button regardless of sequencing battery out/usb cord in or out.
Gives error "boot certification verify" and then shuts down. Back light remains lit.
I can get it to open into another screen (Vol- / power) that offers four options: continue reboot, factory data reset, wipe cache, safe mode boot. Selecting any of those options results in the unit shutting down.
Vol+ plus power do not open Download window.
While it fails to boot, I can still see two folders on my Win 7 PC: image and verinfo. Image contains numerous files . So the phone IS connected to the PC but there appears to be something else that fails to initiate "connection" as far as the LG Flash tool 2014 is concerned. Any suggestions welcome.
Thinking of last resorts, I read somewhere of shorting a test point on the board but can't find directions for this model.
This web site is goog and helpfull for me.
LG Flash Tool
<strong>LG Flash Tool</strong> is the best KDZ Flash software for all kind of LG Android devices or Windows. The new version of the LG flash tool can be <strong>Downloaded</strong> here.
www.lgflashtool.com
Hi all,
I got given this Tab3 because the smd power socket connection guts were physically broken inside socket.
Fitted new power socket (I'm an electronics repair engineer by trade) and checked all pcb (printed circuit board) tracks leading from new fitted socket to ensure there were no hidden breaks ...... new socket refit was 100% successful .....with no solder shorts / bridges and no broken tracks leading to mainboard.
I left Tab3 on charge overnight and next day switched Tab3 on only to be greeted with dreaded .PBL and .PIT failed issue.
After extensive (days!) research I gathered together all necessary firmware and tools and decided that its an easy firmware fix if flashed to an original Samsung SM-T210 UK firmware.
(Please note I dont know past history of this Tab3 .... I dont know if it was rooted / upgraded firmware etc ..... I doubt it though as it belonged to a 7 year old)
Big issue ..... Odin flash tool won't show coms port connection on PC via USB (have tried 3 different laptops one with XP, one with Win7 32bit and another with Win7 64 bit. I've installed / uninstalled / reinstalled multiple Samsung usb drivers that were verified to work with my Tab3 SM-T210 model on each PC .... no joy. Even installed / uninstalled / reinstalled Kies from Samsung .... still wont connect when Tab3 is in download mode. Have kept PC device manager open and nothing appears in device manager. Also have tried 6 different makes of Usb A to micro Usb cables. Have disabled all antivirus, UAC, firewall and Win defender etc ... still no go!
When I go into download mode (power + Vol- +Home buttons) a warning screen does appear BUT it only shows right hand side of graphic warning ..... left hand side is totally grey from top to bottom. (LCD screen is not faulty as it displays full screen info on failed .pbl / .pit flash memory checks) When I then select Vol+ this vertical half graphic info and half grey screen disappears just leaving the backlight on .... which I assume means Tab3 is in proper download mode?
I can go to all recovery modes which allows me to factory reset and delete user cache etc .... it seems to go through the proper routines of reset but upon restart .pbl and .pit failed error in red memory check list is still there.
I can also try and flash firmware file from external sd micro card .... Tab 3 recognises firmware OK and shows Install ..../SD, but then after approx 5 minutes it restarts to failed .pbl /.pit error list again.
Apologies for long post, but from reading above issues can anyone please confirm ....
1) Is half graphic normal when going into download mode? .... or does this point to a previous incorrect or unfinished flash issue?
2) I have downloaded proper .pit flash (LT02) file and original firmware flash for my Tab3 ..... can I flash this any other way other than using Odin ....eg is there any bdm flash method (direct hard wired) flash method to motherboard from external programmer ....like they use for car ecu flash recovery?
3) As I dont know exactly whether Tab3 was rooted / flashed with wrong firmware / incomplete flash upgrade, is there a software tool that can attempt to list what firmware is on my Tab3 at present?
4) I can get into ADB recovery within recovery mode but havent a clue how to use this method .... is this a possible recovery method to use, as I can see SMT210 ADB device in PC device manager when going into recovery mode?
many thanks in advance for help, :good:
Tab3SMD
OK all, here's more info .......AND another additional issue!
I got stuck back in again tonight because not knowing anything about Tab3 ADB recovery mode was bugging me, so here's what extra I've done so far
While "poking my nose" into tonnes more Xda forum troubleshooting guides I discovered I might need PitMagic tool to try and sort my .Pit partition error via ADB recovery mode.
I tried to find Pitmagic but discovered this is now part of EFS Professional, so downloaded EFS Pro and found this got me nowhere as I needed to also install Android SDK .... which also requires Java Development kit, so I downloaded the full Android Studio and Java JDK 8u91 and installed all (about 1.2Gb and requires ~ 4.2Gb hard drive space!)
Anyway, I now ran Android Studio and then ran EFS Professional, opened my Tab3 into ADB recovery mode and connected Tab3 and PC via usb .....
All looking good EFS reported
Initialising ADB server ..... Okay.
ADB server is running!
Searching for device..... OK
Connecting to device .....OK
Checking device status .....
THEN BAMMMM ....popup from EFS
Connected device is currently UNKNOWN
Please ensure ADB server has been authorised by the connected device by confirming your PC's RSA fingerprint, then press OK to continue
like, wtf! .... one step forward and 6 back!
Can anyone please tell me what this means or better still how to proceed from here?
Anyone?
Anyone??? .....Tab3 is still soft-bricked
I did figure out how to use ADB flash recovery mode using PC.
Unfortunately this also did not allow me to flash any firmware (original or custom) due to admin permissions
(I think this is due to USB debugging not activated within Developer options).
I'm sorta banging my head off the wall with this one .... a bit like what came first? egg or chicken?, because since Odin isn't being recognised by the PC, I cannot flash rom and even though the PC fully communicates with Tab 3 in ADB mode, it won't allow me permission to sideload any flash files because I reckon I need root based permissions, and since the darn thing isn't booting fully, I cannot manually change anything!
I then started thinking about trying to sneak around this permissions issue by flashing CWM or TWRP, but again flash fails due to no permission.
All in all, for me this has been a great learning experience tackling the multiple Android recovery modes, and since I feel so close to cracking this non boot issue, I hate to give up and bin it.
Perhaps someone with much more experience can please help me here?
Is there any way of forcing superuser status on this Tab 3 SM-T210, so as to allow me to flash stock rom via ADB recovery mode?
many thanks in advance for your help,
Tab3SMD
Hi everyone,
My zenfone 2 ZE551ML is bricked, so i followed this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
The problem comes when i arrived to the step of IntelSoc:
I install it, no problem until here, i got IntelSoc driver in my device manager .
But when i want to have the MOOREFIELD driver, I cant get it. Following this perfectly
Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables( I don't have hanging cables though, I just have the Logo Asus and write on the top in blue Fastboot mod !!!).
-Connect to your computer via USB cable, to standard Intel SOC driver position, wait a few seconds if the current add an item immediately below another MOOREFIELD new devices is successful.
-If You have not been, the test performed as follows: turn off the machine, plug the cable into the computer, press the power button until the device vibrates slightly, then release.
If you have an idea can you help me please. I think this is the only thing who blocks me in repairing my phone...
Thank you
Yea that problem also persists with my zenfone 2,cant install moorefield 'cause pc cant recognize my phone. Somebody please help us out.
Anagh21 said:
Yea that problem also persists with my zenfone 2,cant install moorefield 'cause pc cant recognize my phone. Somebody please help us out.
Click to expand...
Click to collapse
it is clearly instructed in that thread you mentioned. just keep few things in mind.. uninstall every mobile related driver before installing isoc. uninstall xFSTK tool if you already installed it before installing isoc. third as you are concerned about the line you mentioned morefield under intel soc. well during soc install you will see windows like attached below. at this stage you need to power cycle your device . ( turn off your device holding power button for 10 sec. then connect to pc and turn on. leave connected to pc and turn off again and turn on second time to make sure so driver are installed) don't worry if you don't see morefield under soc now. just go ahead and install xFSTK. now your concern that your device don't stays in morefield download stage ( i mean it appears in device manager and disapear) . after installing xFSTK. run it as administrator and load files. and change gp flag value. also change device detection timeout to 120. now click begin download it will start waiting for device. now turn off your device completely and connect to pc and turn on. xFSTK will force it to stay in required mode. if download do not starts. just power cycle the device while being connected to the tool.
( note: it is strongly recomended that you install isoc and connect mobile before installing. if you have already installed xFSTK then plz uninstall it and install it after performing above said steps. remove all other mobile related drivers also and if you are using windows 8 or 10 disable driver signature enforcement again even if you did it earlier)
The problem with asus flash tool solved
Solution : Open device manager i.r. Windows + X .... if your phone is not being detected... switch it on and off ... there will be ( other devices menu ) that will show your phone there..
right click on the phone , click update drivers, ofcoarse no drivers online, locate the drivers manually , wherever your bootloader file is i.e. the 1 gb file you download or the raw file as we can speak ... i didn't pin pointed it ... my file was on the desktop so I just chose desktop and it searched it and installed it.
After that the phone was successfully in the computer and being detected by the flash tool.
Hey guys,
Got two same devices -one deadbricked one working just fine. Connected working one used wwr with SP flash Tool to backup the firmware. Worked like a charm.
Now I want to flash it to deadbricked one. Here is the problem as SP Flash Tool throws enable dram error. I have started to mess with the drivers and now alive phone connects just fine (phone shown as VCOM in SP and RAM test works like a charm) but on the same drivers 2nd phone is stuck on 0:00 s on download (or any other activity if that matters).
Device manager is recognising 2nd phone as MTK USB Port now but SP Flash Tool is stuck anyways and if I disconnect the phone it throws an error that "maybe device power up too early".
Any suggestions what should I check or change? Those are the exact same devices so drivers should not be an issue here. Also I have checked like 20 different drivers already.
Update:
Got it connected again but now it is stuck on Download DA for several minutes and fails afterwards with enable dram failed 0xfc0