Related
Hi,
I have a SGS I9000
After upgrading firmware by keis my phone goes into a mode that displays a mobile icon and a computer icon, between them there is a yellow sign with a ! Mark on it.
Nothing Works! Absolutely nothing!
I can not go into recovery mode by all methodes listed at sites
When I connect the phone to pc, nothing happens, no sound, absolutely nothing
When I try linux and taild -f /var/log/syslog did not get anything, meaning that the device is completely dead
please help
Try to enter in download mode and flashing a new firmware with odin
Sent from my GT-I9000 using XDA App
mf_417 said:
Hi,
I have a SGS I9000
After upgrading firmware by keis my phone goes into a mode that displays a mobile icon and a computer icon, between them there is a yellow sign with a ! Mark on it.
Nothing Works! Absolutely nothing!
I can not go into recovery mode by all methodes listed at sites
When I connect the phone to pc, nothing happens, no sound, absolutely nothing
When I try linux and taild -f /var/log/syslog did not get anything, meaning that the device is completely dead
please help
Click to expand...
Click to collapse
also look up the SGS forum. you will find plenty of help there.
@Gaarax992: The problem is that I can not enter downlaod mode! Even using this mood: i-thinkbig.blogspot.com/2010/11/modified-usb-with-resistor-to-force.html
@hanifh: what is the address of SGS Forum? I was unable to find it by search
Howdy folks!
I am working my way through a minor (?) technical difficulty.
Would appeciate any suggestions you folks can off this newbie along the way.
Earlier today, I made an absent-minded mistake. Tried to go to my stock Froyo kernel without undoing my voodoo/lagfix/ext/watchamacallit setup. Whoops. Bootloop. No recovery mode available.
So, I attempted to use the procedure described in [ROM] [2.3.6] Heimdall One-click Back-To-Stock UCLB3 here:
http://forum.xda-developers.com/showthread.php?t=1524081
I’m in Windows 7.
I right-clicked on the Heimdall one-click program (Stock_SGH_I997_UCLB3_Repartition-One-Click), but there was no option to run as administrator. So I just double clicked it and it opened it (deviated from instructions on the first step...oh oh).
With the Heimdall one-click program now open, I put my phone in download mode and it indicated connected (perhaps in retrospect I connected too early)
I followed instruction on the PC program to install drivers, which it did (I already had Samsung drivers installed that I used successfully for SOC root program and for EFS Pro, I’m not sure what it was installing).
The pc program told me it needed to reboot. The phone screen said something about “dont’t shut off...”. I wasn’t sure what to do at that point, so I granted the pc permission to reboot.
PC rebooted, phone remains attached the whole time
Upon reboot, the Heimdall one-click program did not start up again.
So I double-clicked it and started it again.
The phone remained attached, but was not recognized as connected by the pc one-click program.
So I pushed 3 buttons on the phone to get it to turn off, then removed the batteries.
.
Then started pc Heimdal one-click program again. Then put my phone in download mode which it did successfully.
Then ran the flash and go the message “The FACTORYFS upload failed!”
(This occurred run without the checkbox about bootloaders)
At that point I checked the checkbox about bootloaders, and it came up with some scarey warning so I didn’t flash (probably should have).
I once again deenergized the phone (three-buttons, remove battery during the brief period it’s deenergized). Shut down pc heimdall one-click program.
Then started pc heimdall program.
Tried to put phone into download mode and received the following inauspicous message:
“Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again”
Deenergized phone again. Shutdown pc program. Powered PC off. Restarted pc. Restarted Heimdall one click.
Tried to put the phone in download mode again and got the same error message.
I don’t know anything about selcting recover mode, not sure how to follow that instruction (any ideas?).
What I did next was search for the error message. It apparently has not been reported in the Infuse section, but I found two threads with this message discussed in the Galaxy S2 section.
“help” is the title of the first
http://forum.xda-developers.com/showthread.php?t=1189473
“Firmare upgrade encountered an issue - Am i done for?” is the title of the 2nd:
http://forum.xda-developers.com/showthread.php?t=1386232
There may be some more out there...
What I gathered was that I needed to remove my drivers.
I did remove the Sansung USG drivers in my control panel. I think these are the one’s I already had installed prior to me SOC root.
Rebooted.
Reinstalled drivers (filename SGH-i997_Infuse4G_USB_Drivers_5_2_0_2)
Restarted Heimdall one-click.
Put phone in download mode.
The same error message indicating that my phone has “issues”
Uninstalled my Samsung USB driver again.
Went back and looked at my control panel, there is another program. Keis. Uninstalled that. Rebooted.
Reinstalled SGH-i997_Infuse4G_USB_Drivers_5_2_0_2 driver
Reinstalled Kies_Mini_For_Captivate_11011_4.exe
Rebooted
Started the Heimdall one-click program.
Put phone in download.
Get the same error message on the phone (firmware upgraded encountered an issue...).
PC at this time thinks the phone is “connected”. So I clicked flash.
It proceeds to the next screen for driver installation.
I selected options / all / Samsung usb / Replace
PC Error message: Driver installation failed.
From those other threads, I’m pretty sure if I get my drivers straightened out I’ll be all right.
I don't know what I did wrong with the drivers... if anyone has a link with concise instructions for uninstalling/reinstalling the required drivers, maybe that would help me see if I've done something wrong.
Any other suggestions?
My java version is Version 6 Update 25
I have made a couple of change to this, a post I did for someone else today. You have done an excellent job of trying to resolve this- I hope this will be helpful.
There are a couple of things to point out:
Get Kies off your computer - it is a source of problems. Also means delete from recycle bin if there.
Download the Infuse drivers from bigjoe's ISET here: http://d-h.st/sKF
Thanks to bigjoe for an amazing page of resources !!
Be sure you have the latest version of Java here: http://www.java.com/en/download/index.jsp
Follow qkster's instructions he provides here:http://forum.xda-developers.com/showthread.php?t=1524081
Post 1 gets you back to stock- Post 2 gets root back.
Big thanks to qkster for doing this - saved many phones for countless number of users !! Me alone over a million times and counting
A video- no academy award nomination, but can be helpful : http://www.youtube.com/watch?v=sHyY7WHx4zc
Video is returning to Gingerbread.
You are willing to learn - therefore there will be many who are willing to help.
Take your time- do it right once and it will be easy next time !!
Heimdall uses it's own driver.
Once you install heimdall on one USB port of your pc, reserve that 1 port for going back. Also good to use that same USB cord.
The first part where it failed was because of bad connection. You just needed to change USB cord or change the port.
Read the heimdall thread and the how to thread a few times...
You could also use the froyo heimdall i put together for ucke3..see my sig link
Thanks very much for the replies.
Updated java.
Uninstalled Kies and Samsung driver (SGH-i997_Infuse4G_USB_Drivers_5_2_0_2)
Rebooted.
Reinstalled Samsung driver from bigjoe's link (same file).
I think it asked me to reboot.
Started the PC Heimdall program.
Attempted to put phone in download mode, it says "Firmware upgrade encountered an issue....".
So phone is not recognizing PC.
But PC recognizes the phone as connected.
Press flash. It goes to next page... I list all drivers, there is nothing Samsung in there.
Disconnected phone. Shut down program. Removed drivers/rebooted / reinstalled Samsung driver
Started Heimdall.
Attempted download mode, same error message "Firmware upgrade encountered an issue..."
Tried flash anyway, the next screen list of devices still has no Samsung.
Oddly when I go back to the first pc screen and try plug/unplug the phone, the PC recognizes phone as connected/disconnected. But it doesn't recognize it on the 2nd page where it tries to install the driver. And the phone has never successfully entered download mode since the first one or two tries...I get this "Firmware upgrade encountered an issue with yellow triangle screen every time since.
All above was on a single USB. I then tried on two other USB's same result. I may try another PC tomorrow night after work.
And will review the qkster's thread again as well as the video link posted by Pony Express.
Will report those results...
For now my head hurts . Time to call it a day.
Thanks for all your help.
I definitely appreciate it.
post deleted by op
meaning of this error message?
deleted
I see there is one other current thread in this forum on similar issue
"stuck on screen with (phone)---!----(Computer) "
http://forum.xda-developers.com/show...rch+this+forum
I noticed one thing we had in common is we both had Kies installed at some time early in our process (now removed).
I have some questions about the meaning of this screen that appears on my phone when I attempt to get to download mode:
"Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again"
The screen has a yellow warning triangle on it
Is that a common screen to see on your phone during this process ?
Does it represent download mode? (I don't think so, since I saw a different screen on my phone the first time I connected... but maybe that had something to do with Kies?)
Is there any point in even trying to flash/download drivers when I see that message?
If the opportunity presents itself, is it advisable to attempt flash with "download bootloaders checked" when this error message is present?
(* If these questions are answered by the video, then I apologize in advance. I don't have the opportunity to watch that video here from my work computer, but I am eager to get a head start so I can hit the ground running when I get home after work tonight).
electricpete1 said:
I see there is one other current thread in this forum on similar issue
"stuck on screen with (phone)---!----(Computer) "
http://forum.xda-developers.com/show...rch+this+forum
I noticed one thing we had in common is we both had Kies installed at some time early in our process (now removed).
I have some questions about the meaning of this screen that appears on my phone when I attempt to get to download mode:
"Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again"
The screen has a yellow warning triangle on it
Is that a common screen to see on your phone during this process ?
Does it represent download mode? (I don't think so, since I saw a different screen on my phone the first time I connected... but maybe that had something to do with Kies?)
Is there any point in even trying to flash/download drivers when I see that message?
If the opportunity presents itself, is it advisable to attempt flash with "download bootloaders checked" when this error message is present?
(* If these questions are answered by the video, then I apologize in advance. I don't have the opportunity to watch that video here from my work computer, but I am eager to get a head start so I can hit the ground running when I get home after work tonight).
Click to expand...
Click to collapse
For the moment don't check the bootloaders. You will only need them for ICS and JB to get rid of rainbows in the recovery. A bootloader flash is practically the only thing that can brick our phone.
Is that "firmware upgrade.." screen the one with the pc!phone? It has been a long time since I soft bricked so I don't recall if it said that somewhere.
If heimdall is giving you issues, try Odin and see how it goes there.
Sent from my sweet & buttery Infuse
electricpete1 said:
I see there is one other current thread in this forum on similar issue
"stuck on screen with (phone)---!----(Computer) "
http://forum.xda-developers.com/show...rch+this+forum
I noticed one thing we had in common is we both had Kies installed at some time early in our process (now removed).
I have some questions about the meaning of this screen that appears on my phone when I attempt to get to download mode:
"Firmware upgrade encounted an issue. Please select recovery mode in Kies and try again"
The screen has a yellow warning triangle on it
Is that a common screen to see on your phone during this process ?
Does it represent download mode? (I don't think so, since I saw a different screen on my phone the first time I connected... but maybe that had something to do with Kies?)
Is there any point in even trying to flash/download drivers when I see that message?
If the opportunity presents itself, is it advisable to attempt flash with "download bootloaders checked" when this error message is present?
(* If these questions are answered by the video, then I apologize in advance. I don't have the opportunity to watch that video here from my work computer, but I am eager to get a head start so I can hit the ground running when I get home after work tonight).
Click to expand...
Click to collapse
Yes...that's represents download mode...just another form...heimdall should still work
Sent from my SGH-I997 using Tapatalk 2
Thanks to everyone. That is very helpful.
I have some more questions. I'm not trying to be nit-picky, but just want to make sure I understand exactly what is being said.
qkster wrote:
Heimdall uses it's own driver.
Click to expand...
Click to collapse
Does that mean we don't need the Samsung driver SGH-i997_Infuse4G_USB_Drivers_5_2_0_2 driver ?
Any guess whether it works better with or without it? I will definitely try without it, but if anyone knows a preferred configuration, that would be helpful so I can focus on changing other things.
qkster's how to:
2. If you have not used Heimdall, you will need to set up the driver for device recognition
Click to expand...
Click to collapse
As a clarification. I'm not sure precisely what that means. All I'm doing is starting the program, letting it load drivers on first screen, connecting the phone in download mode (with error screen), pushing flash which will hopefully get me to the 2nd screen where I select options/all/Samsung/Replace to set up the driver. Is this statement intended to say anything different?
qkster's how to:
6. If it did not work, you will have to put it back into DOWNLOAD mode and reflash a second time, with the FLASH BOOTLOADER box checked.
Click to expand...
Click to collapse
I take it that in my situation (with error message and no evidence of success in previous flashing, and going to GB) this is really only a last resort after all other options exhausted as per andros' suggestion above?
By the way, I'm going to keep trying to install the UCLB3 GB (vs Froyo), as long as the chance of success is the same on both.
qkster's how to
4. Click on the FLASH button. (In my opinion: I recommend that you do this in a safe environment. Do not disturb your phone will flashing this firmware. Turn off Antivirus. Do not run any other programs, upload/download/youtube/burning DVD etc)
Click to expand...
Click to collapse
I'm a little nervous about turning off my security program (a/v, firewall etc) since I haven't done that in years.
Have there been problems attributed to doing this with security enabled, or is it just a general suggestion to avoid interruptions from unexpected scans or pop-ups etc? (my security runs peacefully in background and never interrupts me unless I ask it)
If it's really necessary to disable security program, I'd feel better about keeping my internet disconnected for the duration that the anti-virus is off. Is there any problem created if the internet connection remains disconnected for the duration of this process?
electricpete1 said:
Thanks to everyone. That is very helpful.
I have some more questions. I'm not trying to be nit-picky, but just want to make sure I understand exactly what is being said.
Does that mean we don't need the Samsung driver SGH-i997_Infuse4G_USB_Drivers_5_2_0_2 driver ?
Any guess whether it works better with or without it? I will definitely try without it, but if anyone knows a preferred configuration, that would be helpful so I can focus on changing other things.
As a clarification. I'm not sure precisely what that means. All I'm doing is starting the program, letting it load drivers on first screen, connecting the phone in download mode (with error screen), pushing flash which will hopefully get me to the 2nd screen where I select options/all/Samsung/Replace to set up the driver. Is this statement intended to say anything different?
I take it that in my situation (with error message and no evidence of success in previous flashing, and going to GB) this is really only a last resort after all other options exhausted as per andros' suggestion above?
By the way, I'm going to keep trying to install the UCLB3 GB (vs Froyo), as long as the chance of success is the same on both.
Click to expand...
Click to collapse
Drivers: when you launch heimdall it will install its own custom drivers for whatever usb port its pluged into...so if you plug it into one of your ports in the front and run heimdal only the port the phone is currently plugged into will be effected by the new driver. the driver is only used when in download mode...so dont uninstall your current drivers
selecting device: i think you got it (if my memory is correct...) just launch and run heimdall with device connected in dl mode...when you get to installing drivers just go to options and choose list all...i cant remember the exact name the infuse shows up as though
Bootloaders: just flash the first time without it checked...if it doesnt go through then check it and flash again
Antivirus: i have never turned off my anti virus when using heimdall on any of my computers (one computer uses norton 360 premier, the other one uses avast free) i never had it conflict with the process...so just leave it on for now...and only turn it off if you are having problems...if your worried about viruses then disconnect from the internet when you turn off your anti virus -i dont think the heimdall relies on internet at all...well maybe for the drivers...so just dont turn anything off until after you get the drivers
EDIT: i have a frseh install of windows 7 on my dev computer that i havent used heimdal on yet...so ill run it and clarify the driver section...i dual boot both linux and windows...currently im near the end of a repo sync so as soon as that finishes ill boot into windows and run heimdal...in less then a half hour hopefully...
Thanks mg2195.
Very good info.
I have tried my Windows 7 PC and another windows Vista PC.
On both pc's I tried with drivers pre-installed on the pc and without. Reboots in between.
I also used two different cables and tried all usb ports that were available.
In all cases but one, the anti-virus/firewall was on and pc connected to internet
In one case I tried with anti-virus off and pc diconnected from internet.
In all cases (except for the first one or two at the beginning of this thread), here's what happens:
I start Heimdall, it takes me to the first Heimdall screen, which shows "device status" red/disconnected as expected.
I try to put phone in download. Get the error message screen on the phone (see subject line). The "device status" shown on the pc changes from red/disconnected to green/connected (as expected).
I Click flash.
It asks to run the program, I say ok, it takes me to the second Heimdall screen, where I select Options/List-all.
There is no samsung driver choice.
I close the selection window (click x in upper right hand corner), it takes me back to the first Heimdall screen.
Device status still shows green/connected on the first Heimdall screen.
If I press flash again, the experience at the second screen repeats without showing Samsung driver.
Before I go to the next configuration (next usb port or cord or whatever), I remove the phone and close out the Heimdall program.
The bootloader option is available to be checked in the first Heimdall screen, but I have not done it
I’m not sure if I explained before that I have not had a successful driver installation in that second Heimdall screen (since the first one or two attempts). Does this change fact change your suggestion about checking the flash bootloaders box?
electricpete1 said:
Thanks mg2195.
Very good info.
I have tried my Windows 7 PC and another windows Vista PC.
On both pc's I tried with drivers pre-installed on the pc and without. Reboots in between.
I also used two different cables and tried all usb ports that were available.
In all cases (except for the first one or two at the beginning of this thread), here's what happens:
I start Heimdall.
Try to put phone in download. Get the error message screen.
Click flash in the first Heimdall screen.
It asks to run the program, I say ok, it takes me to the second Heimdall screen, where I select Options/List-all.
There is no samsung driver choice.
I close the selection window (click x in upper right hand corner), it takes me back to the first Heimdall screen.
The bootloader option is available to be checked in the first Heimdall screen, but I have not done it.
I’m not sure if I explained before that I have not had a successful driver installation in that second Heimdall screen (since the first one or two attempts). In this circumstance, do you still think it’s ok to check bootloaders?
Click to expand...
Click to collapse
you should probably wait until you get the heimdal drivers installed...im still wating for my reposync to finish...for some reason the download slowed down to 200kb/s,,,so it could take a while...
but for the drivers do this
1) On the menu bar (Device,Options,Help) Click Options --> List All Devices
2) Under USB Device select “Samsung USB Composite Device”
if its not locating it then try differnt ports/cables...if still no then run as admin...rightclick or shift+rightclick...if still not showing up...maybe bad usb port on the phone?
Quick response... thanks again!
Bad usb on phone is certainly possible, but I've never had a problem with it before.
I can believe the pc usb port might be finicky. Because historically on my Windows 7 PC, every once in awhile when I insert a flash drive memory stick, it does not get recognized. I will see if I can try a 3rd computer.
Regarding "run as administator":
When I right-click on the file, I don't see any option for "run as administrator" in either my Windows 7 pc or my Windows Vista pc.
So I have just been double-clicking the file. I think the Windows Vista asked me if I trusted the program and I said yes. Windows 7 just launches it.
Maybe there's some setting I need to change somewhere in order to get this "run as administator" ....I will google that... tomorrow. Right now, my pillow awaits.
electricpete1 said:
Quick response... thanks again!
Bad usb on phone is certainly possible, but I've never had a problem with it before.
I can believe the pc usb port might be finicky. Because historically on my Windows 7 PC, every once in awhile when I insert a flash drive memory stick, it does not get recognized. I will see if I can try a 3rd computer.
Regarding "run as administator":
When I right-click on the file, I don't see any option for "run as administrator" in either my Windows 7 pc or my Windows Vista pc.
So I have just been double-clicking the file. I think the Windows Vista asked me if I trusted the program and I said yes. Windows 7 just launches it.
Maybe there's some setting I need to change somewhere in order to get this "run as administator" ....I will google that when I get a chance.
Click to expand...
Click to collapse
Did you try holding shift while right clicking?
Sent from my SGH-I997 using Tapatalk 2
electricpete1 said:
I take it that in my situation (with error message and no evidence of success in previous flashing, and going to GB) this is really only a last resort after all other options exhausted as per andros' suggestion above?
Click to expand...
Click to collapse
Thanks for pointing out the imprecise grammar, Pete.
I corrected the op.
Recheck step 6 and 7.
To get heimdall to install its drivers, Zadig, you need the initial Samsung Android drivers. so when you pull down the zadig menu, Samsung Adroid device should show up.
Then reboot the PC.
Then try connect in dl mode again.
You had it at some point...
Thanks all.
That is now very clear qkster. (Actually it was reasonably clear before and I was pretty sure I knew what you meant, but just wanted to double check in case I was misunderstanding something)
I've had some trouble running as administrator, apparenlty others don't
Here's my difficulties and how I resolved it (I think):
DIFFICULTIES IN RUN-AS-ADMINISTRATOR.
If I right-click on an executable file (anything.exe), I get option to run as administrator. Great.
If I right click on a jar file (like the one I'm trying to run), no such option. Sad.
Same thing with short-cuts.
If I right-click on shortcut to exe, I can choose compatibility tab and select run as administrator. Great.
If I right-click on shortcut to jar, there is no compatibility tab. Sad.
HOW I RESOLVED RUN-AS-ADMINISTRATOR (I think)
I found some instructions for specifically for running jar as administrator here:
http://stackoverflow.com/questions/...r-with-administrators-privileges-on-windows-7
Specifically, click start, type cmd in the window just above start, right-click on the cmd result, and click "run as administrator.
That takes you to an elevated command prompt with the word administrator in the window heading.
Navigate to the directory and type
java -jar myfile.jar
where myfile is your file name (I renamed it to shorter name to make it easier).
RESULT:
I was able to launch Heimdal from the elevated command prompt.
Unfortunately, results have been the same thus far when using Heimdall launched from elevated command prompt as the previously reported results.
QUESTION: is there any way to check the program truly has admin priveleges?... it didn't ask any permission when launching Heimdall from the elevated command prompt.. the only permission asked was when launched cmd from the windows start menu screen.
I will repeat a few of yesterdays trials.
If those are unsuccessful, I think next step is trying GTG's package with ODIN.
QUESTION: Is there any way to clear any settings loaded into the USB ports by the Heimdall so they don't interfere with ODIN?
For Odin, just install the drivers you see at the iset page or kies drivers.
If you had a pc, one user when you log on, it is auto assume admin.
You can also go to control panel, users, look at privileges
Hey guys! My phone is now a brick. Can anyone show me how to repair the boot for it? Many thanks.
hungtrauvang said:
Hey guys! My phone is now a brick. Can anyone show me how to repair the boot for it? Many thanks.
Click to expand...
Click to collapse
Flash a new rom
Watch this video...
hungtrauvang said:
Hey guys! My phone is now a brick. Can anyone show me how to repair the boot for it? Many thanks.
Click to expand...
Click to collapse
What happens if you power it on while holding down the up and down buttons?
Frogmanstar said:
What happens if you power it on while holding down the up and down buttons?
Click to expand...
Click to collapse
Nothing happens. Really sad.
hungtrauvang said:
Nothing happens. Really sad.
Click to expand...
Click to collapse
This just means you don't have a recovery.. just flash a new rom.
hi XDA community i have a problem regarding my a850 and i hope u or anybody can reply this comment in an instance cuz im in emergency...
IM EXPLAINING MY PROBLEM VERY DETAILED SO IT'S GONNA BE VERY LONG COMPOSITION, INCLUDING FROM IM ROOTING THE PHONE UNTIL I TYPED THIS COMPOSITION
so recently i "Framarooted" my device and was working properly as i expected,then i want to install TWRP, i see my baseband version does not have ROW or CN in there, it kinda like "A850.V13 ...(cant remember)", but i flashed anyway using the ROW version of TWRP and Mobileuncle MTK Tools. When I want to enter recovery (via MTK Tools) it doesnt show up, just stuck at white,big "Lenovo" logo (it probably doesnt work) but i was able to boot back to normal. Then i used System App Remover from Play and attempted to delete some chinese apps, and I DID a mistake... i was so clumsy enough to delete all chinese apps that origins from the rom i accidently deleted the file "classical" (which i guess the entire system ui, launcher etc) . Upon after deletion of that file I SHOULD HAVE NOT DELETE , it suddenly booted off with the startup sound muted halfway (its like, the boot startup sound have like 4 second duration and i heard the sound just for 1 sec).
Then it boots up again, but stuck at the logo "Lenovo For Those Who Do" after startup animation, so i assume this is bootloop or soft brick
Realising this incident i GOOGLED " a850 bootloop","a850 unbrick","a850 stock rom","a850 emergency reset" and "a850 emergency backup", then I found a website which describes how to flash stock rom to a850, so i did that, as it might work, but actually not for my case. I followed and downloaded exactly steps and files from that website and loaded Flashtool with its scatter file, then ticked PRELOAD and selected the preload.img, followed by checking USB mode ,clicking "Forced High Speed", checked the DA DL thingy, clicked Firmware Upgrade and the progress bar moved, after that i plugged my phone, without battery, to the pc via usb. I heard the hardware insert sound, but, Flashtool did not start flashing, it;'s still SEARCHING.
Then I read that u need the USB drivers, so I assume i do not have drivers for this phone. I used the Device Manager step and when I plug my phone, it pops up "MT65xx Preloader"(or MTK i dont remember) then I quickly rightclick and "Update Driver". It has two selections, ONLINE or BROWSE, so i clicked the online solution, but Windows seems cant find the driver i need,
so i used BROWSE option, which i used your usb driver by entering the directory of the driver in your file in "C:\Users\User\Downloads\Compressed\Lenovo_Drivers_SP_Flash_Tool_v3.1316.0.150\Drivers" clicked install then it pops up an error "The third party INF does not contain digital signature information", so it doesnt install. So I used USBDeview and plugged my phone again without battery, it pops up "MT65xx Preloaded" with a purple dot, and if you need, i rightclicked that purple dot and clicked PROPERTIES, and here's information it gave:
Device Name: MT65xx Preloader
Device Type: CDC Data
Description: MT65xx Preloader
Connected: Yes
Safe to Unplug: NO
Disabled: NO
USB Hub: NO
Drive Letter:*blank
Serial Number:*blank
Created Date: 12/10/2014 2:01:15 AM
Last Plug/Unplug Date:12/10/2014 2:01:15 AM
VendorID: 0e8d
ProductID :2000
Firmware Revision : 1.00
USBClass: 0a
USBSubClass:00
USBProtocol: 00
"Hub Port" until "DeviceMfg" is blank
Power: 500mA
USB Version: 2.00
Driver Description: *blank
Driver Version:*blank
Instance ID: USB\VID_0E8D&PID_2000\5&9ec43f0&0&9
After checked, i resorted to HARD RESET via recovery (i tried to go to recovery again to see there's hope in there) and it BOOTED TO RECOVERY! (yay) but again problem strikes, the recovery I see now is FULLY CHINESE i dont understand even a single option i gave there.
So now my phone condition is still cant boot to launcher, and my very last resort is to use the JTAG option
pls help me u all and pls reply ASAP
thank you
irfanadli97 said:
...clicked install then it pops up an error "The third party INF does not contain digital signature information", so it doesnt install.
Click to expand...
Click to collapse
You should log in to windows with out drivers verification in order to install the drivers. Tutorial on how to do than on windows 8 here. Then flashtool should regognize the phone... (you should fix this problem because you may also need it in the future)
There is also a way to fix your phone (if the classic theme is the problem) using ADB. Go to this page and scroll down to ADB method(tutorial) in order to install the classic.apk as a system apk through ADB.
(i am attaching you the apk: View attachment Theme_classic.apk)
Very thanks though cuz this actually solves my problem on my previous devices which doesn't detect upon connection, but I've actually resorted
to do unsoftbrick by a more professional person in my town (he sells and services phones) and it charged me RM50 ($15). Now my phone is back to normal with a rooted state (Chinese superuser app)
Again thanks for replying.
PS:also can somebody redirect me to lenovo a850 modding page? anybody
irfanadli97 said:
Very thanks though cuz this actually solves my problem on my previous devices which doesn't detect upon connection, but I've actually resorted
to do unsoftbrick by a more professional person in my town (he sells and services phones) and it charged me RM50 ($15). Now my phone is back to normal with a rooted state (Chinese superuser app)
Again thanks for replying.
PS:also can somebody redirect me to lenovo a850 modding page? anybody
Click to expand...
Click to collapse
You did good going to a shop...
What do you mean by "Lenovo a850 modding page"?
u know, where rooted users mod their phone with frameworks, custom roms, installing awesome stuff in theirs'
Sent from my Lenovo A850 using XDA Free mobile app
irfanadli97 said:
u know, where rooted users mod their phone with frameworks, custom roms, installing awesome stuff in theirs'
Sent from my Lenovo A850 using XDA Free mobile app
Click to expand...
Click to collapse
This is such a forum
Tried Installing a custom rom using Flashtool. Now the phone can't come and can't be dected by my pc. Installed the Drivers and they Installed. At first first I was having a Brom Error report Now nothing happens when I p,lug the phone.
I rooted my my few weeks ago with snapdragon root, and yesterday I realized that some apps kept crashing, so I rebooted my phone, but it stucks at Tmobile logo. So I opened up smart switch on my pc, tries to restore my phone, but it said that : SM-G930T does not support initializing. It's confusing since I restore using smart switch before, but I downloaded stock firmware from xda forum, and flashed with odin. And it shows sw rev check fail device 4, binary 3. And it boots in to recovery mode everytime I forced to restart. btw, it says dm-verity verification failed. What can I do to fix this? Thanks for any suggesions.
i had the same problem with my s7 SM-G930T
JokerCat233 said:
I rooted my my few weeks ago with snapdragon root, and yesterday I realized that some apps kept crashing, so I rebooted my phone, but it stucks at Tmobile logo. So I opened up smart switch on my pc, tries to restore my phone, but it said that : SM-G930T does not support initializing. It's confusing since I restore using smart switch before, but I downloaded stock firmware from xda forum, and flashed with odin. And it shows sw rev check fail device 4, binary 3. And it boots in to recovery mode everytime I forced to restart. btw, it says dm-verity verification failed. What can I do to fix this? Thanks for any suggesions.
Click to expand...
Click to collapse
I had the exact same problem with my phone which is the same model as yours, and after almost 2 days of surfing in the internet like crazy and trying all the diferent programs I found the solution.
1. first go to this video youtube,com/watch?v=RSZiVxJyFb4 (I cant post links so I will substitute the dot in "DOT COM" by a comma)
2.Download the firmware and Samsung drivers in the link in the video which is pangu.in/samsung_firmware.html skip thru the pages until you find your model(this link will download the drivers and a notepad with the link to the actual firmware download page which is sammobile,com/firmwares/
3. type the model number in the search bar (SM-G930T) and select the first one in the list and download it(note: you will need to create an account in this page in order to download the firmware but its only put your email and choose a password so it shouldn't be a problem. extract the firmware after downloaded.
4.Download the version of odin that is linked in the video link: pangu.in/odin_tool.html . Scroll down a lil bit and download the one that says "ODIN 3.11 (GALAXY S7)"HAS TO BE THIS ONE other versions wont work. extract it.
5.After you have downloaded everything(make sure you installed the drivers if you haven't done before) proceed to run ODIN with your phone unplugged from your pc and turned off
6.Load the AP file from the extracted firmware file into the AP tab you will see in ODIN(do all this with your phone UNPLUGED from the PC.
7.Now put your phone(which should be off and disconnected from the PC) into download mode[hold vol down+home+pwr button
then you will be aske to press button up to continue, do so(you probably know how to do this but I said in case other people don't)
8.connect your phone onto your pc and you should see your device show up in odin, now click start and you should be good to go
I hope it works for you since I know how frustrating it is to have such and expensive phone bricked.
juanernestous said:
I had the exact same problem with my phone which is the same model as yours, and after almost 2 days of surfing in the internet like crazy and trying all the diferent programs I found the solution.
1. first go to this video youtube,com/watch?v=RSZiVxJyFb4 (I cant post links so I will substitute the dot in "DOT COM" by a comma)
2.Download the firmware and Samsung drivers in the link in the video which is pangu.in/samsung_firmware.html skip thru the pages until you find your model(this link will download the drivers and a notepad with the link to the actual firmware download page which is sammobile,com/firmwares/
3. type the model number in the search bar (SM-G930T) and select the first one in the list and download it(note: you will need to create an account in this page in order to download the firmware but its only put your email and choose a password so it shouldn't be a problem. extract the firmware after downloaded.
4.Download the version of odin that is linked in the video link: pangu.in/odin_tool.html . Scroll down a lil bit and download the one that says "ODIN 3.11 (GALAXY S7)"HAS TO BE THIS ONE other versions wont work. extract it.
5.After you have downloaded everything(make sure you installed the drivers if you haven't done before) proceed to run ODIN with your phone unplugged from your pc and turned off
6.Load the AP file from the extracted firmware file into the AP tab you will see in ODIN(do all this with your phone UNPLUGED from the PC.
7.Now put your phone(which should be off and disconnected from the PC) into download mode[hold vol down+home+pwr button
then you will be aske to press button up to continue, do so(you probably know how to do this but I said in case other people don't)
8.connect your phone onto your pc and you should see your device show up in odin, now click start and you should be good to go
I hope it works for you since I know how frustrating it is to have such and expensive phone bricked.
Click to expand...
Click to collapse
Thanks alot！ I fixed it somehow, I reflash the root ap file, and it works
I never EVER post in these chats/forums, but you, whoever you are, you are a life saver. Thank you, THANK you, THANK YOU so much. it worked like a charm on my t-mobile SM-G930T
Hi,
Yes, I know, there's a million topics about this and I'm pretty sure I tried them all!
Long story short: been running Lineage OS on my Tab 2 for a while but it's been sitting in a drawer. Saw a video about using old tablets for emulating retro consoles and the Tab works a dream for that. So I bought a Bluetooth controller for better gameplay but it just wouldn't work under Lineage so thought I'd flash the original ROM back onto it to see if that would work. I'm not a n00b, but haven't done it for a while so thought to be safe I'd follow a guide. All seemed to be working well when Odin crashed and left me with the Firmware Upgrade Failed error.
I've been trying for about four hours to get it back, but having no luck. I've tried the latest version of Odin, as well as the old 1.7 version I was using; tried Kies, tried uninstalling Kies; tried uninstalling the stock drivers MS installed when connected, no go. Interestingly Odin doesn't seem to see the Tab at all now, so I tried the UniversalADB installer, tried installing ADB drivers as well as Samsung drivers manually, but nothing works, it just sits at "connecting" but never actually does. Also tried different stock ROMs to no avail. I think my issue is with the ADB drivers, just don't know how to fix it.
I don't know what to try now. Any advice?
Using MS Surface Pro (2017) running Win10.
Not allowed to post screenshots, but do have some.
Thanks.
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Tab_Triggerhappy said:
How is the tab behaving after this crash?
Can you use the tab as usual? But you are still in LineageOS? If Yes, what version of LineageOS?
Can you still get into Recovery Mode? If Yes, what Recovery and version do you have?
Download Mode seems Ok, but not Odin at the PC end. Correct?
The more info you can give the better. Also if you prepared the tab in any way other than just entering download mode.
Did you enable USB Debugging for example? (but I'm not sure how important that is)
Or wiped anything in recovery?
I'm not sure if I can help, but surely there must exist someone here that can. I'm new to the android world, but used to work in IT Support and Network Administration.
And 100 years ago I blogged with Blogger, but sat and amended the xml-file to get the design I wanted more than creating blog entries
Anyway, I hope it gets sorted.
Click to expand...
Click to collapse
Hi,
Thanks for your reply and sorry it's taken me so long to respond; I've got several health issues I have to work around!
I can't get into the OS at all, it's just stuck at the "Firmware upgrade..." screen and there's nothing else I can do with it.
It was rooted and I was running TWRP recovery, but can't access it at all now. I did a wipe in TWRP but was still able to boot into it before I ran Odin. Odin worked fine, then it just stopped for reasons unknown and now there's nothing I can do with the Tab at all.
I see this in Device Manager: samsung mobile usb cdc composite device. Have tried manually installing driver but nothing seems to work.
Have tried it on my Mum's Win7 machine, but to no avail. I really need ADB drivers but I can't install them without turning on debugging on the Tab and I can't do that because I can't get out of this blasted error screen!
There's literally nothing else I can say about it as this is all that's happening.
Annnnd, now it doesn't seem to want to hold a charge. :crying:
Thanks again.
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Tabby22020 said:
I've tried following a few tutorials, but I can't get past the ADB issue. Does anyone know of, or can link to, a solution to this please? I really want my Tab back!
Thanks!
Click to expand...
Click to collapse
Maybe a longshot, but you can test if this free version can access the tab:
https://www.tenorshare.com/products/reiboot-for-android.html
No use buying if it can't.
But since Device Manager sees something it's worth a shot.
Do you have to longpress power button to turn it off?
If so... when the screen goes off, have you tried to quickly let go of the power button and immediately press it again together with Volume Up?
Or down, for download instead of Recovery.
With my P3100 it was much easier with no charger plugged in...
Edit:
Tried the software and my tab is OK, but no connection established anyway. Only result was that I couldn't access tab in File Explorer and MTP state... only PTP.
In Device Manager I got a new Android Device: Something like Google Nexus ADB... sorry but I uninstalled it directly without noting exact name.
Replugged USB cable and MTP working again.