hi every one
i have an 'galaxy mini 2 gt s6500d" and it's locked with pattern ! i don't have the gmail ....so i was trying this topic :
http://forum.xda-developers.com/showthread.php?t=2225695
when i reboot to recovry mode , there is no install zip option .....
it's very important that i get rid of the pattern and keep all my data , i don't want to flash the phone ... i don't want to lose my data
please any one can help me ? !
i'm kinda new to android ...
thank's in advance
datornado said:
hi every one
i have an 'galaxy mini 2 gt s6500d" and it's locked with pattern ! i don't have the gmail ....so i was trying this topic :
http://forum.xda-developers.com/showthread.php?t=2225695
when i reboot to recovry mode , there is no install zip option .....
it's very important that i get rid of the pattern and keep all my data , i don't want to flash the phone ... i don't want to lose my data
please any one can help me ? !
i'm kinda new to android ...
thank's in advance
Click to expand...
Click to collapse
You'll need a custom recovery to install the Arome file manager. And there's no guarantee that method will work for your phone and the update it is on either as this is not a universal fix (there is none).
es0tericcha0s said:
You'll need a custom recovery to install the Arome file manager. And there's no guarantee that method will work for your phone and the update it is on either as this is not a universal fix (there is none).
Click to expand...
Click to collapse
if it is possible i'll try it my friend ...
q : if i installed a custom recovery i'll lose the data on the phone like flashing it , or i'll just change the recovery mode ...??
also : can i use linux to unlock it ???
well , i tried odin 3 v1.85 and my device is not recognized , looks like : usb debugging not enabled , no install zip file from recovery mode ....i'm dead
datornado said:
well , i tried odin 3 v1.85 and my device is not recognized , looks like : usb debugging not enabled , no install zip file from recovery mode ....i'm dead
Click to expand...
Click to collapse
Or you could figure out why your device is not recognized by Odin. Likely suspects:
PC Drivers (most common - uninstall all Samsung drivers, reboot, and reinstall Kies)
USB cord (even though it might work to charge or on other devices, it is possible that the cord is not working right in Download mode from like a bent pin)
USB ports on PC (try different ones or different PC)
USB port on the phone (yes, this can be damaged and cause drivers not to load correctly, even if it charges fine)
es0tericcha0s said:
Or you could figure out why your device is not recognized by Odin. Likely suspects:
PC Drivers (most common - uninstall all Samsung drivers, reboot, and reinstall Kies)
USB cord (even though it might work to charge or on other devices, it is possible that the cord is not working right in Download mode from like a bent pin)
USB ports on PC (try different ones or different PC)
USB port on the phone (yes, this can be damaged and cause drivers not to load correctly, even if it charges fine)
Click to expand...
Click to collapse
Thank you so much
i solved the problem hours ago ...
and now i'm going to put the solution to anyone else with the same issue :
My Device is : galaxy mini 2 gt s6500d
it wass locked with pattern , and it require Gmail password to Enter ( i don't have it )
i tryed booting to recovery mode , no install zip File
so i installed different recovery mode by following this tutorial
http://forum.xda-developers.com/showthread.php?t=2156194
and video tutorials from youtube
(Odin3 v1.85+cwm-6.0.3.2-jena-build-2.tar.md5)
--------------
after that i followed this tutorial to install aroma
http://forum.xda-developers.com/showthread.php?t=2225695
-------------
after that i followed this tutorial to delet settings database
http://forum.xda-developers.com/showthread.php?t=2783330
( note : i deleted it manually using amora in recovery mode , i deleted : /data/data/com.android.providers.settings/databases/settings.db)
And Baaaam Device is working very well ( no more ugly screen to enter the gmail + password )
Note : i tried a lot of explanations in the forum like :
deleting gesure.key : i didn't found the gesture.key
Pattern Password Disable.zip : it didn't disable anything
delet gesture.key using the cmd in amora file manager : i tried :
-su
-rm *.key
in data/system path
and it didn't work
i also tried : rm gesture.key , didn't work
_
i also copied accounts.db to the internal storage and mounted it to pc , and tried to Unlock The Gmail password , But unfortunally it's encrypted with a SHA1 hashing algorithm. Since SHA1 is a one-way algorithm there is no reverse function to convert hash to original sequence .
That's it Guys i gived You all my 20 Hours carrier
Thank you es0tericcha0s
And Special thank's to anyone have a tutorial or a software that i used to solve my problem
i forgot to mention that i installed SAMSUNG USB Drivers for Mobile Phones (x86 & x64) v1.5.33.0
from this topic
http://forum.xda-developers.com/showthread.php?t=961956
Related
Out of the blue , I cannot run adb from recovery anymore , whether its DA_G 's or the Alpha CWM that is out ..
Now , this use to work , on both of them recoveries , I pushed many things via adb and then out of the blue , I power down my phone, then 3 button combo to boot in recovery, and 'error no device' , the driver fails to install , I tried many things , no go .
I can still use adb but only if phone is booted ..
Searching the web this seem to be a common issue for GS2 owners wanting to use Kies on Win7 and for many other android device as well ...
This is not my case Im not using Kies . And the mtp driver works just fine when phone is booted (inside Android) .
For the record , my other Phone ( i897 - Samsung Captivate) works jsut fine in both .
Edit L nvm seems to be fixed factory reset and da_g 's recovery together seem to fix the problem .
hi guys!
i have a problem ...
my friend has the GT 5830c, I installed a custom ROM and it worked perfectly!
But after 5 days of use. the phone crashed and restarting it did not load the system and is in the samsung logo screen!
go for recovery and follow the standard process to reinstall the OS. after reinstalled the system, it gave the same problem! to restart it gets stuck at the boot screen!
Another is that I can only access the download mode. after this try mode recovery, this mode recovery does not enable more!
I tried to flash the stock rom, but the system windows 7 does not recognize the device! already tested on four different PCs and it is not recognized!
already reinstalled windows driver several times and does not work. the computer does not even detect that something was connected to the same!
anyone have a light?
excuse my bad english!
thanks
First of all it is on wrong section.
Definitely, I can't understand your english.
All what I understand from this post is :
1) You installed a Custom ROM on your friend's GT-S5830C device.
2) It worked good until the phone "crashed" and it stuck on bootlogo.
3) After this , you went to CWM Recovery and flash a new Custom ROM again ( You deleted data , cache and dalvik cache ? ). If you install a Custom ROM on your current ROM of course there are high chances of bricking device.
4) So , now it stucked on the bootlogo and it didn't go even of CWM Recovery, right ?
5) Now , you could only access download mode. Sure you would do because the device was bricked.
6) You tried to flash stock ROM.
- Now : What version of ODIN you used ? What PDA , CSC , MODEM , or even pit you put on the ODIN Brackets ? Where did you download , or what TUT you followed to flash Stock ROM ?
- What drivers you installed on PC ( all of them ) ?
- You tried all Computer's USB Porters ?
Answer this questions and let me know what specified problem is it.
Regards,
Sniper Killer
If you are in download mode (not recovery) and different pc's don't recognize the device than probably you have a defected usb cable. Try another cable.
Download mode: Vol up + Vol down + Power.
If recognized as an Unknown device than in device manager remove the device, remove drivers, reboot pc, reinstall drivers, reboot and try plugin device in download mode.
:: Today is the first day of what's left of your life. ::
thanks !!
Sniper Killer said:
First of all it is on wrong section.
Definitely, I can't understand your english.
All what I understand from this post is :
1) You installed a Custom ROM on your friend's GT-S5830C device.
2) It worked good until the phone "crashed" and it stuck on bootlogo.
3) After this , you went to CWM Recovery and flash a new Custom ROM again ( You deleted data , cache and dalvik cache ? ). If you install a Custom ROM on your current ROM of course there are high chances of bricking device.
4) So , now it stucked on the bootlogo and it didn't go even of CWM Recovery, right ?
5) Now , you could only access download mode. Sure you would do because the device was bricked.
6) You tried to flash stock ROM.
- Now : What version of ODIN you used ? What PDA , CSC , MODEM , or even pit you put on the ODIN Brackets ? Where did you download , or what TUT you followed to flash Stock ROM ?
- What drivers you installed on PC ( all of them ) ?
- You tried all Computer's USB Porters ?
Answer this questions and let me know what specified problem is it.
Regards,
Sniper Killer
Click to expand...
Click to collapse
hi guys !
I followed this topic that I created myself when I still had a ACE 5830M !
http://www.androidpt.com/index.php?...ck-rom-galaxy-ace-s5830i-c-e-m-via-odin-root/
it always worked! But this device is not mine, more's the same model!
dont worry guy !
tested on another computer and it worked, i already used much this ACE 5830 before. coincided at 4 micros do not recognize the phone, but the fifth computer tested and recognized!
the custom ROM that gave the problem is exactly a one you are using!
thanks for the help!
admins can lock the topic!
ChelebiTech said:
If you are in download mode (not recovery) and different pc's don't recognize the device than probably you have a defected usb cable. Try another cable.
Download mode: Vol up + Vol down + Power.
If recognized as an Unknown device than in device manager remove the device, remove drivers, reboot pc, reinstall drivers, reboot and try plugin device in download mode.
:: Today is the first day of what's left of your life. ::
Click to expand...
Click to collapse
Thank you friend, have solved the case!
Hey,
I have been years just reading these forums but never made any posts, so thats why I cannot post to development section anyways. I happened to totally brick my phone by flashing wrong preloader into it. However this morning i succesfully reflashed it and now I have somehow working phone (just need to find new rom now) but anyways. This thread is to help other people who has semi bricked their phones as well.
Current situation.
-Phone doesn't charge,
-Phone doesn't turn on (nothing happens)
-Computer sees phone for few secs, so you have "META mode" access. If your computer doesn't see your phone at all make modified USB connect the 4pin to ground. This is what I did actually. If that doesn't work you can google for test points.
My device:
MTK6575 (Fake mt6589)
512MT RAM (fake 2GB)
800x460 resolution (fake 1920x1080)
4GB internal memory (fake 8gb)
5" screen
2200mah battery (fake 3000mah)
OK this is the prodecure that got my phone back to live!
Install windows XP (Yes, windows 8 didn't work for me. most likely drivers are not ready for it. I will not write steps how to install windows xp)
Install USB deview
-Google it, download it, extract package and run it
-Remove all drivers related to Mediatek, android, usb vcom etc.
Download and install VCOM USB Drivers
-Download these drivers http://www.mediafire.com/download/31nddwqdot5ajp2/MT6575+USB+VCOM+drivers.zip
-Put your phone battery in (50% charge) required. wait 10s. Take battery off and connect your phone to PC as meta mode ( modified USB cable, VOL+/- while connecting, you can read more about this from here: http://forum.xda-developers.com/showthread.php?t=1943442
-When your phone is connected it will disconnect after ~3-5seconds. Now you have to wait in device manager connect the phone right click the device when it shows up. Install driver from the location where you unpacked your VCOM USB drivers/2K_XP_COM/ dont automaticly install them but manually. After windows have found drivers UNTICK show compatible devices. And MANUALLY select preloader driver. Now it will install it the next time the device connects. OK now we have Preloader driver in place. Notice that we will install one more driver later needed in flashing procedure. Disconnect phone.
Now download compatible rom. for me My backup was not working, but this rom worked out perfectly:
http://search.4shared.com/postDownload/wILsUT7J/MTK6575_S4_FLASH_TOOLS_YEDEK.html
Download SP Flash Tool v3.1222.00, extract it.
Ok lets recap what we have now:
-preloader drivers
-phone disconnected
-SP Flash Tool v3.1222.00
-back up we can use to flash
Open flash tool, enter scatter file and go to Format
-Select Format whole flash except bootloader and nvram bin region. -> connect phone -> succeed
-Select Format NVRAM bin region ONLY -> connect phone -> succeed
-Select Format whole flash -> connect phone -> succeed
Ok. Next we need to flash compatible rom this part is tricky. Read before doing anything.
-Disconnect your phone, enter battery (50% charge required)
-wait atlaest 15seconds, and remove battery
-(I dont know why those steps were required, but didn't work without it)
-Open SP Flash tool select scatter file and select all checkboxes
-press download
-connect your phone in META mode with Preloader drivers we installed before.
-Now red prograss bar will start going and phone will disconnect After it reconnect We want ANOTHER drivers are located in the same place but now we need to select Mediatek DA Vcom USB drivers. If everything went fine you get yellow progress bar and it will reflash your phone! :victory:
In the last part if you got Error 5054, This is good. It means your phone is still alive! but your current preloader does not match the data you are going to flash. So you need to go back to google and download other rom try flashing everything (thats what I did, before hitting jack pot, eventually you will find compatible rom)
If you got ERROR 3002 switch back to SP Flash Tool v3.1222.00 newer one doesn't work!
I got some other errors as well when flashing and I solved them but didn't write down the errors so I cant remember them sorry
Remember before connect phone as META mode. Plug in battery with atlaest 50% power wait 15s. remove it. and connect the phone to PC. This was the mysterious step I was missing when struggling with this 5 days!
By the time of writing this article I got my phone working rom, everything works.
GOOD LUCK
ps. Sorry for typos.
:angel: kthxbai
thanks!
AND THANKS FOR yuweng and rui1 who made this all possible!
anyway now I'm back to porting CM to our device. hopefully this helped somebody (and yes, I will be more careful this time)
Hi, it worked for me and i could unbrick my mtk6575
Hi, there
rom given in post worked for me
and i could finally unbrick my phone, but now it asks for the password to decrypt storage after boot. I don't know what to do.
please provide password or any solution to it.
my device is stuck on boot?
Havunen said:
Hey,
I have been years just reading these forums but never made any posts, so thats why I cannot post to development section anyways. I happened to totally brick my phone by flashing wrong preloader into it. However this morning i succesfully reflashed it and now I have somehow working phone (just need to find new rom now) but anyways. This thread is to help other people who has semi bricked their phones as well.
Current situation.
-Phone doesn't charge,
-Phone doesn't turn on (nothing happens)
-Computer sees phone for few secs, so you have "META mode" access. If your computer doesn't see your phone at all make modified USB connect the 4pin to ground. This is what I did actually. If that doesn't work you can google for test points.
My device:
MTK6575 (Fake mt6589)
512MT RAM (fake 2GB)
800x460 resolution (fake 1920x1080)
4GB internal memory (fake 8gb)
5" screen
2200mah battery (fake 3000mah)
OK this is the prodecure that got my phone back to live!
Install windows XP (Yes, windows 8 didn't work for me. most likely drivers are not ready for it. I will not write steps how to install windows xp)
Install USB deview
-Google it, download it, extract package and run it
-Remove all drivers related to Mediatek, android, usb vcom etc.
Download and install VCOM USB Drivers
-Download these drivers http://www.mediafire.com/download/31nddwqdot5ajp2/MT6575+USB+VCOM+drivers.zip
-Put your phone battery in (50% charge) required. wait 10s. Take battery off and connect your phone to PC as meta mode ( modified USB cable, VOL+/- while connecting, you can read more about this from here: http://forum.xda-developers.com/showthread.php?t=1943442
-When your phone is connected it will disconnect after ~3-5seconds. Now you have to wait in device manager connect the phone right click the device when it shows up. Install driver from the location where you unpacked your VCOM USB drivers/2K_XP_COM/ dont automaticly install them but manually. After windows have found drivers UNTICK show compatible devices. And MANUALLY select preloader driver. Now it will install it the next time the device connects. OK now we have Preloader driver in place. Notice that we will install one more driver later needed in flashing procedure. Disconnect phone.
Now download compatible rom. for me My backup was not working, but this rom worked out perfectly:
http://search.4shared.com/postDownload/wILsUT7J/MTK6575_S4_FLASH_TOOLS_YEDEK.html
Download SP Flash Tool v3.1222.00, extract it.
Ok lets recap what we have now:
-preloader drivers
-phone disconnected
-SP Flash Tool v3.1222.00
-back up we can use to flash
Open flash tool, enter scatter file and go to Format
-Select Format whole flash except bootloader and nvram bin region. -> connect phone -> succeed
-Select Format NVRAM bin region ONLY -> connect phone -> succeed
-Select Format whole flash -> connect phone -> succeed
Ok. Next we need to flash compatible rom this part is tricky. Read before doing anything.
-Disconnect your phone, enter battery (50% charge required)
-wait atlaest 15seconds, and remove battery
-(I dont know why those steps were required, but didn't work without it)
-Open SP Flash tool select scatter file and select all checkboxes
-press download
-connect your phone in META mode with Preloader drivers we installed before.
-Now red prograss bar will start going and phone will disconnect After it reconnect We want ANOTHER drivers are located in the same place but now we need to select Mediatek DA Vcom USB drivers. If everything went fine you get yellow progress bar and it will reflash your phone! :victory:
In the last part if you got Error 5054, This is good. It means your phone is still alive! but your current preloader does not match the data you are going to flash. So you need to go back to google and download other rom try flashing everything (thats what I did, before hitting jack pot, eventually you will find compatible rom)
If you got ERROR 3002 switch back to SP Flash Tool v3.1222.00 newer one doesn't work!
I got some other errors as well when flashing and I solved them but didn't write down the errors so I cant remember them sorry
Remember before connect phone as META mode. Plug in battery with atlaest 50% power wait 15s. remove it. and connect the phone to PC. This was the mysterious step I was missing when struggling with this 5 days!
By the time of writing this article I got my phone working rom, everything works.
GOOD LUCK
ps. Sorry for typos.
:angel: kthxbai
Click to expand...
Click to collapse
my rooted mt6575(spice mi-315) device stuck on boot logo. i also tried clar cache and wipe all data bt still same boot logo appear . i am going to ur theard when i format whole flash except bootloader and navram. and connect my device to pc and error occured.....
does some know where to find a latest rom for my mtk 6575(samsung glx,y grand duo hard copy) plz i really need 1
google play service was not working so i uninstalled it to intall a proper vrsion but when i try install it from google play store it says imcompatible with same shared id what can i do plz hlp me coz some of my apps and game r not working...
gapps and cwm problems
soulindub said:
google play service was not working so i uninstalled it to intall a proper vrsion but when i try install it from google play store it says imcompatible with same shared id what can i do plz hlp me coz some of my apps and game r not working...
Click to expand...
Click to collapse
Quote:
Originally Posted by Snekhers
I need this informations roms!
Screen : 540x960
BB Chip : MT6577
Ms Board : Glaxy S3
IMEI1 : XXXXXX
IMEI2: XXXXXX
Modem Ver. : MAUI.11AMD.W11.50.SP.V12. 2012/09/20 18:56
Bar code : 030801050804260123456788.81_20390210
Build Time : 2012 10 17 15:02:47 CST
UBoot Ver. : 2010.06
Kernel Ver. : 4.1.1
SW Ver. : ALPS.ICS.MP.V2.6
Custom Build Verno. : 005121017
hi, a have same phone and is it possible update new rom? Why? Because thşs rom very stable but one except, google contacts cant sync.
And i m trying cwm install with MTKdroid tools its runing but ONLY ONE TAKE. After the reboot in CWM menu coming orginal factory recovery(yellow simple screen and only have test etc. menus) why? ((
Hello,
my device (i9300) as mentioned above got stuck in a boot loop.
First I did was I installed the latest pac-man ROM from here. After successful testing I decided to flash the latest OmniRom 4.4 from here.
Now here comes the dilemma with: My Failure was that I had a old Recovery (CWM-based Recovery v5.5.0.4) and I didn't see the point where it says that I have to update it first.
My USB Connection to my PC was already broken before I started to flash any of the ROMs. So I can't connect to the PC to flash via Odin. It fails on the driver installtion. (I copied everything in my cloud and downloaded it to the internal sd)
The Device Manager shows alwas a ! in a yellow triangle near the "Samsung Mobile USB CDC Composite Device" (Download Mode) with a errer code 10: Device cannot start. I did millions of solutions but nothing worked against this issue ...
Currently my device starts where the Samsung galaxy s3 logo pops up, get stuck by that with a red 1 on the upper left corner and boots into the "old" recovery.
This is my Problem. Please help me to fix this (and the USB bug).
Thank you very much
Kind regards,
A.R.Cante
A.R.Cante said:
Hello,
my device (i9300) as mentioned above got stuck in a boot loop.
First I did was I installed the latest pac-man ROM from here. After successful testing I decided to flash the latest OmniRom 4.4 from here.
Now here comes the dilemma with: My Failure was that I had a old Recovery (CWM-based Recovery v5.5.0.4) and I didn't see the point where it says that I have to update it first.
My USB Connection to my PC was already broken before I started to flash any of the ROMs. So I can't connect to the PC to flash via Odin. It fails on the driver installtion. (I copied everything in my cloud and downloaded it to the internal sd)
The Device Manager shows alwas a ! in a yellow triangle near the "Samsung Mobile USB CDC Composite Device" (Download Mode) with a errer code 10: Device cannot start. I did millions of solutions but nothing worked against this issue ...
Currently my device starts where the Samsung galaxy s3 logo pops up, get stuck by that with a red 1 on the upper left corner and boots into the "old" recovery.
This is my Problem. Please help me to fix this (and the USB bug).
Thank you very much
Kind regards,
A.R.Cante
Click to expand...
Click to collapse
To fix the USB bug, you must uninstall that driver and download the driver ( try to install kies for example )
To fix the bootloop try to do a full wipe in recovery mode
abidifethi said:
To fix the USB bug, you must uninstall that driver and download the driver ( try to install kies for example )
To fix the bootloop try to do a full wipe in recovery mode
Click to expand...
Click to collapse
None of your advices worked. I did unistall all drivers and also Kies. Reinstalled and it doesn't worked. So I uninstalled it again and installed only the drivers but this didn't worked too.
Everytime I uninstall the drivers and connect the device to the PC it is trying to Install the Drivers over Windows Update and Kies isn't reacting at all.
Now since I wiped data/factory reset, cache partition, dalvik cache and formated /system and /preload my device won't start automatically in the recovery anymore. It get stuck on the Samsung Galaxy SIII Logo with the red 1 in the upper left corner. To Access to the Recovery I have to take the battery out and and insert it again and press volume up + home + power.
What can I do now?
Thanks in advance
A.R.Cante said:
None of your advices worked. I did unistall all drivers and also Kies. Reinstalled and it doesn't worked. So I uninstalled it again and installed only the drivers but this didn't worked too.
Everytime I uninstall the drivers and connect the device to the PC it is trying to Install the Drivers over Windows Update and Kies isn't reacting at all.
Now since I wiped data/factory reset, cache partition, dalvik cache and formated /system and /preload my device won't start automatically in the recovery anymore. It get stuck on the Samsung Galaxy SIII Logo with the red 1 in the upper left corner. To Access to the Recovery I have to take the battery out and and insert it again and press volume up + home + power.
What can I do now?
Thanks in advance
Click to expand...
Click to collapse
Try to download any custom ROM if you don't done yet and put it in your external sd card ( use an other phone or card reader ) and now try to enter in recovery mode and install it and let us know the result
abidifethi said:
Try to download any custom ROM if you don't done yet and put it in your external sd card ( use an other phone or card reader ) and now try to enter in recovery mode and install it and let us know the result
Click to expand...
Click to collapse
I tried this now on my Desktop Computer and it worked fine. I didn't need to install drivers manually. It installed it by itself and therefore i was able to use odin!
I flashed the new recovery and put the omnirom and pa-gapps on my sd card (I also tried this on my notebook but my card reader is maybe broken)
so i installed teamwin recvovery over pc, put rom and gapps on my sd card and flashed them over recovery.
Now all works fine.
Thank you for your help.
But what I don't understand is my Win 7 OS (32 bit) is recently set up on my VM everything was fresh but it didnt recognized my device... Google says a lot of people are having this issues. I've tried everything whenever I found allegedly a solution for this problem. None of them worked. I simply switched the computer and everything is fine. This is ridiculous. One year ago, when I had running windows as main OS, there were no problems at all. If the problem was caused by a virtual machine I think that not many people would complain about this issue.
Kind regards
Why would old Win 7 recognize your device unless you install drivers .
JJEgan said:
Why would old Win 7 recognize your device unless you install drivers .
Click to expand...
Click to collapse
I don't really understand your comment. The Problem of this USB error has no root. When your Windows System says error code 10: device cannot start then you have a big problem because you don't know why and how to fix this. Try and Google this. You will find thousands of people complaining the same error. Everyone has other solutions for that. Some edit their registry, others simply do a soft-reset and try another USB-Port.
Samsung support can't help you at all because they don't know why this is happening. And the solving of this problem is really random. i tried for hours to solve this with no success (except switching to another computer).
Windows says on my laptop the device cannot start but it is perfectly connecting to my other computer. How can this happen? I don't know. Maybe the error code 10 is not that specific and there is something other wrong than my device.
I had a phone stuck on third SAMSUNG splash screen, so I flashed a stock ROM (successfully) with Odin and either something had destroyed all my data (all data directories were empty) or flashing destroyed all my data. But at least the whole phone (which had been semi-bricked) sprang back to life and starts working properly, going into recov mode and download and was properly recognised by the computer etc.
So i thought I must now see if my Philz backup files contain anything which I can restore to the device. I got the device easily recognised in Odin and flashed Philz successfully onto it.
Now however the phone (starts properly but) wont go into recovery, it gives the blue 'recovery started' on the splash screen and then the screen goes dead.
Even worse, the whole device is no longer recognised by the PC on startup into download mode at all?? And obviously cant be seen in Odin.
Is there any keystroke combination I can try from startup please? I didnt think one could flash so badly that you cant get a WORKING phone into recovery or properly recognised by PC when in download mode!
remover battery and change ? or charge full, you dont have sds?
No amount of removing battery helps, nor does trying to get what recover mode there is (it will very occasionally go into the simple three line one) from batteryless state have any effect, nor can I do all that much with the unit in turned-on state with the SD cards nor do I know how to do anything from download mode with the SD card? Is this even possible?
usb port in telephone is ok ? in download mode you have custom binary download : yes ?
if /sdcard path is removed recovery will slow boot,
reinstall windows 7 and drivers
exe98123q said:
usb port in telephone is ok ? in download mode you have custom binary download : yes ?
if /sdcard path is removed recovery will slow boot,
reinstall windows 7 and drivers
Click to expand...
Click to collapse
Not sure what this means but download mode shows:
ODIN MODE
PRODUCT NAME SGH-T999
CUSTOM BINARY DOWNLOAD: YES (12 COUNTS)
CURRANT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOM SECUREBOOT: ENABLE
WARRANTY STATUS: 1
BOOTLOADER AP SWREV: 1
exe98123q said:
usb port in telephone is ok ? in download mode you have custom binary download : yes ?
if /sdcard path is removed recovery will slow boot,
reinstall windows 7 and drivers
Click to expand...
Click to collapse
And the port was working fine before the flash, it was something in the flash which is stopping it from being recognised by the computer AT ALL. Not recognised but with no or improper drivers, nothing happens on the Computer on connecting up to the computer. (same with connecting it up to a WIN10 and LinuxMint computer. Nada.
ok, mayby you flash wrong rom/recovery ? if usb port/cable, drivers ok,
dunno