Related
Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium
Reserved for updates
Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
iowabowtech said:
Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Click to expand...
Click to collapse
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250
bk201doesntexist said:
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250
Click to expand...
Click to collapse
Yup, tried it but its still the same. Fastboot still dosent work and relashing packaged factory images in odin dosent fix the fastboot
Sent from my GT-I9100 using xda premium
Saw a Jtag service nearby and thinking of sending it in. Its roughly after conversion from RM(Malaysian Ringgit) around USD$90. Possible recovery from the issue?
Sent from my GT-I9100 using xda premium
does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.
override182 said:
Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.
chadouming said:
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.
Click to expand...
Click to collapse
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
killersloth said:
does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.
Click to expand...
Click to collapse
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium
override182 said:
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it. Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options. But that would be strange that adb work on safe mode. There is probably a way to that with adb but you will have to google it. Tell your friend to follow instruction next time. And ffs, do not use odin ! (Little idea too, try to get in fastboot not connected on PC and wait a few minutes then see if you can move with the volume button, then try to connect it on pc)
chadouming said:
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it.
Click to expand...
Click to collapse
Yes i have already did that few times. Few times of ICS factory image and few with JB. All are repacked version provided by chainfire. Its the full package not the software only with stripped bootloader n recovery. Its still the same
Sent from my GT-I9100 using xda premium
http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work
killersloth said:
http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work
Click to expand...
Click to collapse
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium
override182 said:
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?
killersloth said:
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?
Click to expand...
Click to collapse
Yes i had, still boots to safe mode and the fastboot is still dead. Yes ive tried adb reboot bootloader but its dead in fastboot, again.
Sent from my GT-I9100 using xda premium
only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.
Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639
killersloth said:
only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.
Click to expand...
Click to collapse
Tried yesterday, nothing happened
Sparx639 said:
Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639
Click to expand...
Click to collapse
First tried pda only with auto reboot, no gooding. The i tried with booloader, no good. Then bootloader only, still no good. Then i tested all including pit file, still no good.
Update, sent in for Jtagging few min ago. The phone is not with me now and ill get it back in 3days working or not. I shall report in back after 3 days. Thanks to all by giving suggestion and ideas. See u guys again in 3 days
Sent from my GT-I9100 using xda premium
chadouming said:
Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options.
Click to expand...
Click to collapse
adb does not work in download mode/bootloader. adb only works when adbd (adb service) is started, and that happens in android boot process. it means android debug bridge.
sent from my i9250
Sorry for the long delay to anyone waiting for the answer/status.
Jtag cant fix it. Returned the device to a friend. Prolly a mobo replacement is the solution but its damn pricy here in Malaysia. It costs 80% of the price to get a new Gnex.
Hell yeah and thx to everyone supporting this.
Sent from my GT-I9100 using xda premium
I recently flashed CM9 to my phone, but now i want to move on to JB, but for some reason i can not get into flash mode to write a different FTF.
When i I try to get into flash mode, I power the device off, hold the back button, and insert the USB cable. The LED on top flickers green then the screen comes on the the charging screen.
The same happens when I try to use fastboot except blue light flickers.
I have tried diferent computers, cables and OS's im not sure what else to try.
Download flashtool and install the drivers for your phone then leave your phone and enable unknown sources and enable usb debugging then open flashtool then press flash icon and select fastboot mode then plug your phone in then select reboot into fastboot mode via adb
Sent from my R800i using xda app-developers app
FaiselW said:
Download flashtool and install the drivers for your phone then leave your phone and enable unknown sources and enable usb debugging then open flashtool then press flash icon and select fastboot mode then plug your phone in then select reboot into fastboot mode via adb
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
I ran the driver utility and even when I send reboot bootloader via adb, the LED only flickers blue for a moment, then it boots to CWM.
I didn't think the drivers on the computer would change if the phone goes into flash mode or not though.
Default Cant Get To FastBoot or Flash Mode
You would need to be in flashmode (green light) to install a stock FTF not fastboot mode has suggested above. Have you tried flashing another version of CM9 with your phone via cwm and then trying from there see if the problem is not your rom.If not it could be a driver issue.
tallman43 said:
You would need to be in flashmode (green light) to install a stock FTF not fastboot mode has suggested above. Have you tried flashing another version of CM9 with your phone via cwm and then trying from there see if the problem is not your rom.If not it could be a driver issue.
Click to expand...
Click to collapse
I know i need to be in flash mode, i just reinstalled cm9.1.0 and it still has the same problem. I dont know what to do. I have tried multiple cords, I have used ubuntu ,win7 and win8 with the drivers installed and reinstalled. Im worried that my phone is broken.
Ngong0 said:
I know i need to be in flash mode, i just reinstalled cm9.1.0 and it still has the same problem. I dont know what to do. I have tried multiple cords, I have used ubuntu ,win7 and win8 with the drivers installed and reinstalled. Im worried that my phone is broken.
Click to expand...
Click to collapse
(1) Have you installed other roms before your problem started did this only start after installing CM9
(2) Have you flashed any other kernels before CM9 or was CM9 your first rom/kernel flash
Noticed on your first post you wrote that you hold the back button then attached the usb did you do this when flashtool said or before, you need to connect the usb exactly when flashtool tells you to like below step 5
(1) How to flash a stock .ftf Rom
(2) load & place .ftf rom in Windows/flashtool/firmware folder
(3) Open flashtool press lightening icon press flashmode
(4) Select your .ftf you placed in flashtool /firmware folder earlier
(5) Wait! Flashtool will tell you to connect your phone!
(6) Press & hold back button while connecting phone to PC green light will come on.
(7) Wait while flashtool starts flashing your stock rom.When finished it will tell you to reboot
(8) Finished unplug switch your phone on done!
Sorry if you already do it like this but some people forget and connect the usb too early Also I would recommend downloading a different version of flashtool some people have managed to get there phone working by using a older version of flashtool:good:
tallman43 said:
(1) Have you installed other roms before your problem started did this only start after installing CM9
(2) Have you flashed any other kernels before CM9 or was CM9 your first rom/kernel flash
Noticed on your first post you wrote that you hold the back button then attached the usb did you do this when flashtool said or before, you need to connect the usb exactly when flashtool tells you to like below step 5
(1) How to flash a stock .ftf Rom
(2) load & place .ftf rom in Windows/flashtool/firmware folder
(3) Open flashtool press lightening icon press flashmode
(4) Select your .ftf you placed in flashtool /firmware folder earlier
(5) Wait! Flashtool will tell you to connect your phone!
(6) Press & hold back button while connecting phone to PC green light will come on.
(7) Wait while flashtool starts flashing your stock rom.When finished it will tell you to reboot
(8) Finished unplug switch your phone on done!
Sorry if you already do it like this but some people forget and connect the usb too early Also I would recommend downloading a different version of flashtool some people have managed to get there phone working by using a older version of flashtool:good:
Click to expand...
Click to collapse
(1) yes, i have installed several roms before CM9 and i was always able to enter flash mode.
(2)I have tried doom kernel and several other kernels as well
I have waited till flash tool prompts, but IIRC id didn't matter in the past, flashtool would see what mode it was in and proceed.
Thank you for the descriptive reply.
Did you try a older version of flashtool http://androxyde.github.io/index.html?1375894152000
tallman43 said:
Did you try a older version of flashtool http://androxyde.github.io/index.html?1375894152000
Click to expand...
Click to collapse
I just tried versions 7 and 8, it doesn't seem to help.
I feel like this is something wrong with my phone though, I remember the phone being able to go into fast boot and flash mode at any time, as long as the computer was on. It is really weird how it flashes the color on the LED.
Ngong0 said:
I just tried versions 7 and 8, it doesn't seem to help.
I feel like this is something wrong with my phone though, I remember the phone being able to go into fast boot and flash mode at any time, as long as the computer was on. It is really weird how it flashes the color on the LED.
Click to expand...
Click to collapse
I so this quote on another thread similar problem to yours this is what he did:
Quote: Funny thing though is that in order to get into either mode, I have to remove the battery while it is plugged in and then hold down the corresponding key while inserting the battery and the corresponding light will then light up. That seems to be the only way to get into the modes. And sometimes this does't work, but it seems to work more than not.
This guy did this to get into fastboot and flashmode worth a try?
tallman43 said:
I so this quote on another thread similar problem to yours this is what he did:
Quote: Funny thing though is that in order to get into either mode, I have to remove the battery while it is plugged in and then hold down the corresponding key while inserting the battery and the corresponding light will then light up. That seems to be the only way to get into the modes. And sometimes this does't work, but it seems to work more than not.
This guy did this to get into fastboot and flashmode worth a try?
Click to expand...
Click to collapse
no luck... The light only blinks then goes into charging mode...
Edit:Is there a test point or something that would force the phone into one of these modes?
Ngong0 said:
no luck... The light only blinks then goes into charging mode...
Edit:Is there a test point or something that would force the phone into one of these modes?
Click to expand...
Click to collapse
Sounds like TA damaged you could try this but it's a paid service http://octopusbox.com/eng/news/details/259....Or someone reading this thread might know a better way :fingers-crossed:
tallman43 said:
Sounds like TA damaged you could try this but it's a paid service http://octopusbox.com/eng/news/details/259....Or someone reading this thread might know a better way :fingers-crossed:
Click to expand...
Click to collapse
Im looking to possibly switch carriers and this will be just another push towards it. lol
tallman43 said:
Sounds like TA damaged you could try this but it's a paid service http://octopusbox.com/eng/news/details/259....Or someone reading this thread might know a better way :fingers-crossed:
Click to expand...
Click to collapse
I read this for another phone and it is a shot in the dark, but if the boot block were zeroed out, it forces it into fastboot. If this can possibly work, what block device is the boot partition?
I will not bee too disappointed if the phone is bricked.
Ngong0 said:
I read this for another phone and it is a shot in the dark, but if the boot block were zeroed out, it forces it into fastboot. If this can possibly work, what block device is the boot partition?
I will not bee too disappointed if the phone is bricked.
Click to expand...
Click to collapse
huh? can you say that again please.
Hi guys!
I have Sony Xperia Arc S.
Is it possible to put it in a Flashmode without a "Back" button? My BackButton is broken, I think it is a road-wire on the button's board.
BTW Fastboot mode working fine.
Hi,
I tried to install TWRP (by a lot of different methods) but they didn't work. I was also have a fastboot & flashtool driver problem so I couldn't install it using computer either.
One day I saw an app in the play store called ROM Installer. I downloaded it and tried to flash twrp.img using it. It said flashing was succesful. Now I rebooted my phone to recovery (by the NDR Utils app) but it was just powered off and than red LED lighted up. After 20 minutes I removed the battery. (It didn't react to anything else) Then I tried to boot it but it didn't react. (nor boot to recovery or boot to safemode)
After 5 hours when I tried to boot it again it showed that battery is exhausted (by the red LED) I connected it to charger but it didn't do anythig except the LED lighting. If I disconnect it it shows the -exhausted battery sign- again.
If I connect it to my computer the red LED lights up but nothing else. The computer doesn't recognise it. I have no idea how to power it again.
Really thanks guys to help me.
PS I'm a novice so pls be patient (and sorry for my mistakes as well)
Other details:
Phone: Xperia M C1905
Android: 4.3 Jelly Bean
Build number: 15.4.A.1.9
Phone is rooted and has an unlocked bootloader
did u unlock your bootloader before flashing the recovery????
balintd said:
Hi,
I tried to install TWRP (by a lot of different methods) but they didn't work. I was also have a fastboot & flashtool driver problem so I couldn't install it using computer either.
One day I saw an app in the play store called ROM Installer. I downloaded it and tried to flash twrp.img using it. It said flashing was succesful. Now I rebooted my phone to recovery (by the NDR Utils app) but it was just powered off and than red LED lighted up. After 20 minutes I removed the battery. (It didn't react to anything else) Then I tried to boot it but it didn't react. (nor boot to recovery or boot to safemode)
After 5 hours when I tried to boot it again it showed that battery is exhausted (by the red LED) I connected it to charger but it didn't do anythig except the LED lighting. If I disconnect it it shows the -exhausted battery sign- again.
If I connect it to my computer the red LED lights up but nothing else. The computer doesn't recognise it. I have no idea how to power it again.
Really thanks guys to help me.
PS I'm a novice so pls be patient (and sorry for my mistakes as well)
Other details:
Phone: Xperia M C1905
Android: 4.3 Jelly Bean
Build number: 15.4.A.1.9
Phone is rooted and has an unlocked bootloader
Click to expand...
Click to collapse
are you sure your device is really on unlocked bootloader condition? if that really on unlocked bootloader condition you only need to wipe data via flashtool. BTW install recovery on stock rom is only using flashtool for safe way. and usually CWM is only work on stock rom but if you want TWRP you can using FOTARecovery. i think that from kernel problem, cause if you install any recovery from app in playstore they will change your kernel with another kernel that have recovery mode. but if that kernel isn't compatible with your phone, your phone will soft brick. are you sure you have problem with flashmode and fastboot driver on your pc? i can tell you advanced than this if you can tell me which OS do you using it right now on your pc.
Don't worry your phone not fully broken
Nicklas Van Dam said:
are you sure your device is really on unlocked bootloader condition? if that really on unlocked bootloader condition you only need to wipe data via flashtool. BTW install recovery on stock rom is only using flashtool for safe way. and usually CWM is only work on stock rom but if you want TWRP you can using FOTARecovery. i think that from kernel problem, cause if you install any recovery from app in playstore they will change your kernel with another kernel that have recovery mode. but if that kernel isn't compatible with your phone, your phone will soft brick. are you sure you have problem with flashmode and fastboot driver on your pc? i can tell you advanced than this if you can tell me which OS do you using it right now on your pc.
Don't worry your phone not fully broken
Click to expand...
Click to collapse
Thanks for replying.
My device on unlock bootloader I'm sure. (I called a strange number it showed a menu and in device info option it showed bootloader is unlocked.
Driver problems: When I connect the phone in fastboot mode the flashtool usually says: device not found - install the drivers from... I installed the drivers of my phone but it still didn't worked. I tried to update the 's1 boot fastboot' driver in device manager (picked the winusb inf file) but it said that that was a problem during installing: adb interface is missing. (but now I can't boot my device into fastboot mode)
balintd said:
Thanks for replying.
My device on unlock bootloader I'm sure. (I called a strange number it showed a menu and in device info option it showed bootloader is unlocked.
Driver problems: When I connect the phone in fastboot mode the flashtool usually says: device not found - install the drivers from... I installed the drivers of my phone but it still didn't worked. I tried to update the 's1 boot fastboot' driver in device manager (picked the winusb inf file) but it said that that was a problem during installing: adb interface is missing. (but now I can't boot my device into fastboot mode)
Click to expand...
Click to collapse
Okay, now I know you're using windows, but which version of windows did you using it? 7,8,8.1 or 10?
Sent From My Sony Xperia™ M Powered By Seal Of Metatron
Nicklas Van Dam said:
Okay, now I know you're using windows, but which version of windows did you using it? 7,8,8.1 or 10?
Click to expand...
Click to collapse
I'm currently using windows 10.
Nicklas Van Dam said:
Okay, now I know you're using windows, but which version of windows did you using it? 7,8,8.1 or 10?
Click to expand...
Click to collapse
Please answer because I still have the trouble.
Firt unlock bootloader of your device becuse recoveries cant be install on locked bootloader
Hi,
My phone got a message about a virus which I assumed was a devious add, it wouldn't go away so I rebooted. It has gone into Mi-Recovery 3.0 and I cant get out. I've tried to connect to PC suite but it won't connect to my laptop
without debugging, which I can't do. I've wiped data but no good. Any ideas?
Flash full rom img via EDL mode and MiFlash software. Check out the official forums how to do it all.
For me the command fastboot oem edl works to get into edl mode.
pr0x2 said:
Flash full rom img via EDL mode and MiFlash software. Check out the official forums how to do it all.
For me the command fastboot oem edl works to get into edl mode.
Click to expand...
Click to collapse
Thank you for answering. I have downloaded a full rom and the MiFlash software. I have made an EDL cable but nothing happens. From what I read it says turn the phone off and connect the modified cable and it will enter EDL mode however it just stays on the Mi-Recovery 3.0 page. I've tried the command line you suggest but that can't find the phone. I've also tried the test point method and still can't get into edl mode. What am I doing wrong?
Sorry, I'm new to this so don't really know what I'm doing. Would you be able to give me some easy to follow advise or some links please.
Multi57 said:
Thank you for answering. I have downloaded a full rom and the MiFlash software. I have made an EDL cable but nothing happens. From what I read it says turn the phone off and connect the modified cable and it will enter EDL mode however it just stays on the Mi-Recovery 3.0 page. I've tried the command line you suggest but that can't find the phone. I've also tried the test point method and still can't get into edl mode. What am I doing wrong?
Sorry, I'm new to this so don't really know what I'm doing. Would you be able to give me some easy to follow advise or some links please.
Click to expand...
Click to collapse
You need your normal USB C cable. When you are in fastboot you need to type "fastboot oem edl" your screen will go to black and you are now in EDL mode. Now flash full img via miflash software.
pr0x2 said:
You need your normal USB C cable. When you are in fastboot you need to type "fastboot oem edl" your screen will go to black and you are now in EDL mode. Now flash full img via miflash software.
Click to expand...
Click to collapse
I cant get to fastboot as I'm stuck in Recovery. My only choices are Reboot to System and Back to Main Menu. When I'm in Main Menu my choices are Reboot, Wipe Data or Connect with MIAssistant.
Multi57 said:
I cant get to fastboot as I'm stuck in Recovery. My only choices are Reboot to System and Back to Main Menu. When I'm in Main Menu my choices are Reboot, Wipe Data or Connect with MIAssistant.
Click to expand...
Click to collapse
When you turn off the phone and press vol down + power what does that do?
It shows the Mi start screen then boots strait into recovery Main Menu. I can't turn the phone off without it rebooting.
Does anyone know how I can get around this? I've run out of things to try.
Did you try reflashing the recovery maybe that fixes it?
Sent from my MI 5s using Tapatalk
Can you explain how I do that? I can't connect to my computer so not sure what you mean. I'm new at this so unsure of the options.
Multi57 said:
Can you explain how I do that? I can't connect to my computer so not sure what you mean. I'm new at this so unsure of the options.
Click to expand...
Click to collapse
Oh hmm never mind. Ignore what I said above. I thought you had TWRP recovery but you've got the stock one.
Sent from my MI 5s using Tapatalk
templeka said:
Oh hmm never mind. Ignore what I said above. I thought you had TWRP recovery but you've got the stock one.
Sent from my MI 5s using Tapatalk
Click to expand...
Click to collapse
Is there no way of getting out of stock recovery?
Maybe your volume rocker buttons are faulty .
Happened with one of my friend his device was only booting into recovery mode on reboot because vol+ button was permanently stuck ?
Try to lift up the button if it is stuck or
press button repeatedly for sometime .
Ashish 289, you are right, it was a faulty volume rocker. Once disconnected it booted. Thanks.
Multi57 said:
Hi,
My phone got a message about a virus which I assumed was a devious add, it wouldn't go away so I rebooted. It has gone into Mi-Recovery 3.0 and I cant get out. I've tried to connect to PC suite but it won't connect to my laptop
without debugging, which I can't do. I've wiped data but no good. Any ideas?
Click to expand...
Click to collapse
now its my turn brother got my mi5 bricked in the same way .
it stays in mi recovery 3.0 always . if you tell me what you did after these steps not working ? could you do anything ?
need a solution man, please help .
thanks in advance.
Hi all,
After reading many posts i got a little confused and i'm not getting any result. Please help.
What i want?: Flash stock rom and later consider rooting, and flashing haden or lineagos. (already found guidance but..)
The issue?: It doesn't get recognized through USB with my PC. (drivers installed, cable connected but...)
My questions? (correct me if wished):
1) In Odin mode (which i enter) is the usb port enabled by default? or it depends on the phone configuration.
2) In recovery mode i still cannot see the phone through the USB so is it open by default on stock recovery?
3) Finally can i flash stock rom i downloaded from sammobile through SD card? i found that to be my last resort but i think odin actual proper way or not?
I first thought it was the cable...since is not the original but it seems not be the case...which leads me to think its the phone's usb port....but with the cable i can charge the phone although i cannot see it through my PC.
So bottom line if the answer to my questions are that is always open (accesible through usb port) then it HAS to be the cable right?
If last quesiton is possible then i will conclude my searchings to be ended for now.
Thanks to all the posts within this tree.
Findings
Is it normal that when boot to bootloader from stock recovery the ADB console keeps <waiting for device> while phone actually boots normaly?
I found that bootloader booting is accesible through fastboot independently from USB debugging option...
I'm considering buying official usb cable but store guy confirmed it works for data/power uses...
There definitely is a way to flash stock via TWRP, i once did that myself. However you need a dedicated tool on the PC to create a flashable zip, because the firmware can't be flashed by itself
Edit: i saw that you have FRP-lock enabled. Search for a guide on how to disable it and try again
verdugon said:
Is it normal that when boot to bootloader from stock recovery the ADB console keeps <waiting for device> while phone actually boots normaly?
I found that bootloader booting is accesible through fastboot independently from USB debugging option...
I'm considering buying official usb cable but store guy confirmed it works for data/power uses...
Click to expand...
Click to collapse
Are you on Samsung? If so, they don't have fastboot. Nor can you boot to bootloader. Do
Do you have the drivers installed? I have yet to see an unofficial cable not work for data transfer. Excepting damaged ones.
Light at the end of the tunnel!!!
PMFRTT said:
There definitely is a way to flash stock via TWRP, i once did that myself. However you need a dedicated tool on the PC to create a flashable zip, because the firmware can't be flashed by itself
Edit: i saw that you have FRP-lock enabled. Search for a guide on how to disable it and try again
Click to expand...
Click to collapse
Thanks PMFRTT!! I finally disabled FRP-lock and phone is usable again. I now will try to unlock OEM bootloader and enable USB debugging to see what happens. Thanks
Light at the end of the tunnel!!!
SnowFuhrer said:
Are you on Samsung? If so, they don't have fastboot. Nor can you boot to bootloader. Do
Do you have the drivers installed? I have yet to see an unofficial cable not work for data transfer. Excepting damaged ones.
Click to expand...
Click to collapse
Thanks @SnowFuhrer for your reply.
To answer your question yes its SMSUNG. I didn't know about that Thx.
The cable is brand knew but i noticed now that the phone is usable that is claims its on slow charge...may be my PC is quite old now....
Like i said i will try to unlock bootloader and make it accesible to odin to later see what to do.
verdugon said:
Thanks @SnowFuhrer for your reply.
To answer your question yes its SMSUNG. I didn't know about that Thx.
The cable is brand knew but i noticed now that the phone is usable that is claims its on slow charge...may be my PC is quite old now....
Like i said i will try to unlock bootloader and make it accesible to odin to later see what to do.
Click to expand...
Click to collapse
And to unlock the bootloader, just enable OEM unlock in the dev settings and it's ready to flash twrp. I remember when I got my Samsung and I was trying to fastboot unlock it lol.
Thanks to both of you! I will keep the thread on just in case...anyway may be it helps someone else.
verdugon said:
Thanks PMFRTT!! I finally disabled FRP-lock and phone is usable again. I now will try to unlock OEM bootloader and enable USB debugging to see what happens. Thanks
Click to expand...
Click to collapse
Good luck! Let me know how it went.