Related
I have a pretty big problem and need some guided help. My stock samsung usb charger sometimes charges the phone and sometimes does not. Tried multiple different chords and got the same results, sometimes works sometimes does not. So now I am assuming this is an internal hardware problem soo I decided I should flash stock images, unroot and relock the bootloader and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash stock images so I can return it to VZW....
Not sure what to do next.. any suggestions would be great...
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
mwalt2 said:
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
Click to expand...
Click to collapse
I tried that. uninstalled the old ones (that worked for 3 months) reinstalled them again and still no luck..
Do you have any other Android processes running on your cpu? Droid Explorer or alike? Droid Ex **** blocks adb; I had a frustrating few minutes once when adb wouldn't connect to my device until I realized DE was running in the background.
Long shot, but just a thought.
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
chuckdz3 said:
and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash
Click to expand...
Click to collapse
You mean fastboot
Melhouse said:
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
Click to expand...
Click to collapse
Yeah I believe that is what I am going to do, I just have to find the sch-i515 CDMA version because I am finding a lot of GSM versions out there right now.
bk201doesntexist said:
You mean fastboot
Click to expand...
Click to collapse
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
chuckdz3 said:
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
Click to expand...
Click to collapse
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
bk201doesntexist said:
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
Click to expand...
Click to collapse
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
chuckdz3 said:
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
Click to expand...
Click to collapse
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
mwalt2 said:
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
Click to expand...
Click to collapse
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
chuckdz3 said:
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
Click to expand...
Click to collapse
yes, you can download the images for your device from google and flash them to your phone using fastboot if you want. I'm pretty sure that would put you back at stock with an unlocked bootloader.
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
bk201doesntexist said:
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
Click to expand...
Click to collapse
I know how to. It was just your demeanor and wording/phrasing that had me confused.
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
brooklynite said:
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
Click to expand...
Click to collapse
*facepalm*
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
mentose457 said:
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
*facepalm*
Melhouse said:
*facepalm*
Click to expand...
Click to collapse
Did I say something stupid?
mentose457 said:
Did I say something stupid?
Click to expand...
Click to collapse
debugging has nothing to do with it.
Windows XP absolutely HATES the samsung galaxy nexus.
The don't play along and it's almost impossible to get the drivers (especially MTP) installed correct.
Fortunately I have a W7 BEAST rig at home.. But the work XP pc can't handle the Nexus
Hi All,
I was running on AEX 4.6, SuperSU, Open Gapps, I wanted to install Google Tez but it doesn't work with rooted devices so after browsing there are some users who are able to use Tez by hiding root (replacing SuperSU with Magisk). I went ahead to SuperSU, tapped on Unroot Device option, accidentally i click on 'yes', when it was showing a message related to bootloader image (I don't know the message though), and now I'm unable to boot into TWRP.
Whenever I try to boot it into recovery, it shows two frames (given as urls) for as long as 1 sec, and then reboots itself.
Need your help guys!!!
Thanks in advance.
https://ibb.co/jCrOqw [frame1]
https://ibb.co/kxOsiG [frame2]
kunalvirk said:
Hi All,
I was running on AEX 4.6, SuperSU, Open Gapps, I wanted to install Google Tez but it doesn't work with rooted devices so after browsing there are some users who are able to use Tez by hiding root (replacing SuperSU with Magisk). I went ahead to SuperSU, tapped on Unroot Device option, accidentally i click on 'yes', when it was showing a message related to bootloader image (I don't know the message though), and now I'm unable to boot into TWRP.
Whenever I try to boot it into recovery, it shows two frames (given as urls) for as long as 1 sec, and then reboots itself.
Need your help guys!!!
Thanks in advance.
https://ibb.co/jCrOqw [frame1]
https://ibb.co/kxOsiG [frame2]
Click to expand...
Click to collapse
Use magisk and hide root for tez app
visheshjain25 said:
Use magisk and hide root for tez app
Click to expand...
Click to collapse
I will brother, but the scenario is that i'm not able to boot to twrp, however I've tried to look for it in ADB fastboot, it is showing my device but nothing is on screen, and the device is listed as unauthorized....
kunalvirk said:
I will brother, but the scenario is that i'm not able to boot to twrp, however I've tried to look for it in ADB fastboot, it is showing my device but nothing is on screen, and the device is listed as unauthorized....
Click to expand...
Click to collapse
Can you access fastboot
selvarajrajkanna said:
Can you access fastboot
Click to expand...
Click to collapse
Thanks for replying brother, I can access fastboot but the screen goes black but it is recognisable in Android MultiTool and under 'adb devices' command but as unauthorized....was wondering if is there any way i can change 'unauthorized' to 'device' so that i can reflash TWRP and ROM.....
Thanks
kunalvirk said:
Thanks for replying brother, I can access fastboot but the screen goes black but it is recognisable in Android MultiTool and under 'adb devices' command but as unauthorized....was wondering if is there any way i can change 'unauthorized' to 'device' so that i can reflash TWRP and ROM.....
Thanks
Click to expand...
Click to collapse
I don't think you can access adb when the phone is on fastboot
Use minimal adb and fastboot
Use
fastboot devices
Command to see if your device is connected
If it is connected then make sure bootloader is unlocked and flash twrp and ROM
selvarajrajkanna said:
I don't think you can access adb when the phone is on fastboot
Use minimal adb and fastboot
Use
fastboot devices
Command to see if your device is connected
If it is connected then make sure bootloader is unlocked and flash twrp and ROM
Click to expand...
Click to collapse
bootloader is already unlocked, but the problem is that when use adb command 'adb devices' it shows my device as unauthorized.....
kunalvirk said:
bootloader is already unlocked, but the problem is that when use adb command 'adb devices' it shows my device as unauthorized.....
Click to expand...
Click to collapse
You can't access abd until your phone is booted into android
Weird, normal here.
selvarajrajkanna said:
You can't access abd until your phone is booted into android
Click to expand...
Click to collapse
So is there any other solution available that can get my phone to woking state.....:crying:
kunalvirk said:
So is there any other solution available that can get my phone to woking state.....:crying:
Click to expand...
Click to collapse
I already told you
Switch off the phone completely
Press volume up and volume down and plug in the data cable
Your device will boot into fastboot
Then you are recover your phone easily
selvarajrajkanna said:
I already told you
Switch off the phone completely
Press volume up and volume down and plug in the data cable
Your device will boot into fastboot
Then you are recover your phone easily
Click to expand...
Click to collapse
Thanks a lot man...!!!.....:good: It worked....actually before there was some driver issues at the machine i was using......
kunalvirk said:
Thanks a lot man...!!!.....:good: It worked....actually before there was some driver issues at the machine i was using......
Click to expand...
Click to collapse
Happy to help
Stuck on boot logo !!!!! :crying:
Can't :
1. Can't boot to ROM (as doing so just stays on boot logo)
2. Can't boot into recovery (as doing this gets me to either black screen or just boots back to the boot logo)
Can :
1. Can enter bootloader
2. Can able to use fastboot commands
Tried:
1. flashing stock ROM several times,
2. flashing stock recovery
3. flashing twrp recovery
:crying:
Check my guide. It might come handy.
https://forum.xda-developers.com/le...-lenovo-p2-t4006405/post80955105#post80955105
alirazaagha said:
Check my guide. It might come handy.
https://forum.xda-developers.com/le...-lenovo-p2-t4006405/post80955105#post80955105
Click to expand...
Click to collapse
Friend thanks for the reply but your link just says "Duplicate thread. "
hackiee said:
Friend thanks for the reply but your link just says "Duplicate thread. "
Click to expand...
Click to collapse
Yes, it was. Check this one.
https://forum.xda-developers.com/lenovo-p2/how-to/guide-unbrick-unlocked-lenovo-p2-t4006401
alirazaagha said:
Yes, it was. Check this one.
https://forum.xda-developers.com/lenovo-p2/how-to/guide-unbrick-unlocked-lenovo-p2-t4006401
Click to expand...
Click to collapse
Thanks for your post friend, but, your guide doesn't fulfill my situation.
As, I am stuck on bootliader or boot logo.
I have flashed all firmwares s048,s233,s244,s51 through fastboot but none of them able to get me out of it.
Even tried flashing various recoveries both stock and twrp but neither of them helped
If, anyhow I can be able to enter into TWRP. It will solve the problem. But, I don't know nothing seems to work.
Even tried corrupting the bootloader and then flashing blankflash, but that too didn't able to get me out of the bootlogo.
Please help ?
alirazaagha said:
Yes, it was. Check this one.
https://forum.xda-developers.com/lenovo-p2/how-to/guide-unbrick-unlocked-lenovo-p2-t4006401
Click to expand...
Click to collapse
Hey, can you please do 1 thing.
Can you provide an image of the bootloader mode of your lenovo p2, if, there's something to lookup idk
I am attaching image of my bootloader, if you can look into it.
Thanks
hackiee said:
Hey, can you please do 1 thing.
Can you provide an image of the bootloader mode of your lenovo p2, if, there's something to lookup idk
I am attaching image of my bootloader, if you can look into it.
Thanks
Click to expand...
Click to collapse
It's alright.
alirazaagha said:
It's alright.
Click to expand...
Click to collapse
nothing strange ? Ok thanks
hackiee said:
nothing strange ? Ok thanks
Click to expand...
Click to collapse
Yep. Go ahead. You can try S244 firmware to try and boot your phone. If it boots then update accordingly as I mentioned in my guide.
alirazaagha said:
Yep. Go ahead. You can try S244 firmware to try and boot your phone. If it boots then update accordingly as I mentioned in my guide.
Click to expand...
Click to collapse
Still no luck! :crying: flashed S244 several times but nothing.
Can you confirm one more thing.
When I give
"Fastboot format system" I get :
"Formatting is not supported for file system with type 'raw'."
screenshot attached. Please check
hackiee said:
Still no luck! :crying: flashed S244 several times but nothing.
Can you confirm one more thing.
When I give
"Fastboot format system" I get :
"Formatting is not supported for file system with type 'raw'."
screenshot attached. Please check
Click to expand...
Click to collapse
OK so you are not following my guide Check .txt file attached in that guide and if you are still unsure then ask me.
alirazaagha said:
OK so you are not following my guide Check .txt file attached in that guide and if you are still unsure then ask me.
Click to expand...
Click to collapse
I have checked the text file of your guide, and they are the same instructions which I have been following since start. :silly:
The "fastboot format system" is a command which I used to do on my Moto G, and was able to format system successfully.
But, I don't remember if it used to work on P2 or not , that's why I asked you. If, you can use that command to check the output on your device.
Thanks
hackiee said:
I have checked the text file of your guide, and they are the same instructions which I have been following since start. :silly:
The "fastboot format system" is a command which I used to do on my Moto G, and was able to format system successfully.
But, I don't remember if it used to work on P2 or not , that's why I asked you. If, you can use that command to check the output on your device.
Thanks
Click to expand...
Click to collapse
Hmmm so you haven't read .txt file carefully. Command is:
Fastboot ERASE system
See the difference now? :silly:
Please, discuss it on that thread if need so others could also benefit from it.
alirazaagha said:
Hmmm so you haven't read .txt file carefully. Command is:
Fastboot ERASE system.
Click to expand...
Click to collapse
OMG, yes brother, I already know the command, and I have used it several times, the fastboot ERASE command, but, as mentioned several timesin the past, it is not solving my problem.
As, I am still not able to enter into any recovery(neither stock nor twrp), and not able to boot and OS.
That's why, I wanna try "Fastboot format system" command.
If, somehow that solves my problem
hackiee said:
OMG, yes brother, I already know the command, and I have used it several times, the fastboot ERASE command, but, as mentioned several timesin the past, it is not solving my problem.
As, I am still not able to enter into any recovery(neither stock nor twrp), and not able to boot and OS.
That's why, I wanna try "Fastboot format system" command.
If, somehow that solves my problem
Click to expand...
Click to collapse
OK. I though that you only tried Format command not erase. You should skip this command and do the whole process. I have added this command so that previous system files are erased. But, I booted my phone without using this command first time. Second time, I tried to see if I can do it all in a single process then I added this command and it worked without any issues and all the process went smooth and phone booted like a new one.
Try all commands but skip erase system command.
stuck on logo , have access to fastboot only
My phone stuck on logo when i open it or when i insert charger
when i try to open recovery(volume up + down) it turned off and i can't open recovery by any way
i can access fastboot
i tried your instruction and Lenovo+P2+UnBrick+OneTeam-EypCnn and all other fastboot roms
i tried install Twrp and stock recovery
i tried blankflash
that didn't help ,i can only access fastboot
what is your recommendation ? it's a hardware issue ?
DrGhost001 said:
stuck on logo , have access to fastboot only
My phone stuck on logo when i open it or when i insert charger
when i try to open recovery(volume up + down) it turned off and i can't open recovery by any way
i can access fastboot
i tried your instruction and Lenovo+P2+UnBrick+OneTeam-EypCnn and all other fastboot roms
i tried install Twrp and stock recovery
i tried blankflash
that didn't help ,i can only access fastboot
what is your recommendation ? it's a hardware issue ?
Click to expand...
Click to collapse
Did you find any solution?
Same issue here, I guess it's a hardware issue: SSD is damaged ?
fastboot erase system
fastboot format:ext4 system
Maybe related to the file system ?
i have the same probelm, do you guys find any solution ?
Hey! I'm currently trying to flash a custom rom on my 9 pro from 11.2.10.10 and i've unlocked the bootloader. ADB commans are working fine, but as soon as I boot into the bootloader and type "fastboot flash boot "recovery.img"" it just doesn't do anything, no "downloading..." text or anything. I then tried to use any other fastboot commands and nothing works, (to be clear, my device is being recognized, "fastboot devices" does show my device. but no other command works, either doesn't do anything, or gives me an error.
any help would be much appreciated
check if you have the last fastboot version - platform-tools_r33.0.1
bengoodall.raw said:
Hey! I'm currently trying to flash a custom rom on my 9 pro from 11.2.10.10 and i've unlocked the bootloader. ADB commans are working fine, but as soon as I boot into the bootloader and type "fastboot flash boot "recovery.img"" it just doesn't do anything, no "downloading..." text or anything. I then tried to use any other fastboot commands and nothing works, (to be clear, my device is being recognized, "fastboot devices" does show my device. but no other command works, either doesn't do anything, or gives me an error.
any help would be much appreciated
Click to expand...
Click to collapse
Have you checked Device Manager to see if there's any unknown devices?
bengoodall.raw said:
Hey! I'm currently trying to flash a custom rom on my 9 pro from 11.2.10.10 and i've unlocked the bootloader. ADB commans are working fine, but as soon as I boot into the bootloader and type "fastboot flash boot "recovery.img"" it just doesn't do anything, no "downloading..." text or anything. I then tried to use any other fastboot commands and nothing works, (to be clear, my device is being recognized, "fastboot devices" does show my device. but no other command works, either doesn't do anything, or gives me an error.
any help would be much appreciated
Click to expand...
Click to collapse
Assuming you're using the latest adb & fastboot versions, what happens when you type "fastboot devices"? Does it show your device?
CZ Eddie said:
Assuming you're using the latest adb & fastboot versions, what happens when you type "fastboot devices"? Does it show your device?
Click to expand...
Click to collapse
Yep, shows my device
Sometimes it does but when I unplug then replug it shows adb bootloader interface
razercortex said:
Have you checked Device Manager to see if there's any unknown devices?
Click to expand...
Click to collapse
Yep I have the latest version
GabrielSousa said:
check if you have the last fastboot version - platform-tools_r33.0.1
Click to expand...
Click to collapse
bengoodall.raw said:
Yep, shows my device
Click to expand...
Click to collapse
Does it work with ANY fastboot commands at all?
Such as "fastboot reboot"?
bengoodall.raw said:
Yep I have the latest version
Click to expand...
Click to collapse
Try running those commands on another PC and let us know if it works.
CZ Eddie said:
Does it work with ANY fastboot commands at all?
Such as "fastboot reboot"?
Click to expand...
Click to collapse
Nope, that doesn't work either
Didn't work either 🫤
razercortex said:
Try running those commands on another PC and let us know if it works.
Click to expand...
Click to collapse
bengoodall.raw said:
gives me an error.
Click to expand...
Click to collapse
Screenshot of the error?
I had similar issues and found out it was because I was executing the commands in the bootloader instead of fastbootd mode. Try running them in fastbootd mode instead?
GloriamSemper said:
I had similar issues and found out it was because I was executing the commands in the bootloader instead of fastbootd mode. Try running them in fastbootd mode instead?
Click to expand...
Click to collapse
Ermm, you're SUPPOSED to run the commands in "bootloader" mode, not fastbootD mode.
I'm kind of curious how unlocking the bootloader worked but using other commands doesn't.
ekin_strops said:
Ermm, you're SUPPOSED to run the commands in "bootloader" mode, not fastbootD mode.
Click to expand...
Click to collapse
I know wierd, right? None the less, certain fastboot commands were only successful for my 2127 in fastbootd
I got bootloop pixel 6 pro
Pc recognize it
Only adb devices and adb fastboot cmd work
Other cmd not work.
Can anyone help me
And always blackscreen. Nothing show or display
Have you enabled USB debugging?
To enable USB debugging you need to enable Developer Options in your phone first. To do this: Go to Settings > About phone > Software info > and then tap the build number about 7 times.
Edit: I can see you have downloaded the Android SDK Platform-Tools on the desktop. Try to run the command under the correct path ( C:\Users\XXXX\Desktop\platform-tools_r33.0.2-windows\platform-tools>
RhapsodyK said:
Have you enabled USB debugging?
To enable USB debugging you need to enable Developer Options in your phone first. To do this: Go to Settings > About phone > Software info > and then tap the build number about 7 times.
Click to expand...
Click to collapse
How will he do this when he is in a boot loop?
CRXed said:
How will he do this when he is in a boot loop?
Click to expand...
Click to collapse
Indeed. I have definitely lost my mind.
Use android flashtool. You can't downgrade on official a13 and I think you have to flash it to both slots or use flashtool
Android Flash Tool
flash.android.com
CRXed said:
How will he do this when he is in a boot loop?
Click to expand...
Click to collapse
Yes i have bootloader unlock. But totally blackscreen now. Any button do not work.
If ADB and Fastboot still work (and since your bootloader is unlocked), then @fil3s suggestion to use the Android Flash Tool is the best option to try.
fil3s said:
Use android flashtool. You can't downgrade on official a13 and I think you have to flash it to both slots or use flashtool
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
Pc not recognize phone.
Nordnord said:
Pc not recognize phone.
Click to expand...
Click to collapse
Guess I misunderstood. Do ADB and Fastboot still work, or don't they? If they don't, you might want to edit your OP.
Nordnord said:
Only adb devices and adb fastboot cmd work
Click to expand...
Click to collapse
Nordnord said:
Pc not recognize phone.
Click to expand...
Click to collapse
Do you have the latest drivers and Platform Tools installed? Try different cables and/or ports?
Here screenshot
Yes driver and platform toos installed. I tried different cable and port.
Abd/fastboot devices cmd works but next like adb reboot bootloader cmd not works.
Nordnord said:
Yes driver and platform toos installed. I tried different cable and port.
Abd/fastboot devices cmd works but next like adb reboot bootloader cmd not works.
Click to expand...
Click to collapse
Are you using A to C cable?
If fastboot devices works type
Code:
fastboot reboot bootloader
Or use adb sideload
Nordnord said:
I got bootloop pixel 6 pro
Pc recognize it
Only adb devices and adb fastboot cmd work
Other cmd not work.
Can anyone help me
Click to expand...
Click to collapse
What were you trying to do, and at what point did this happen?
Is your phone recognized as a Android device, or is it showing up as something else?
Does holding down the Power button + Volume Down do anything?
Lughnasadh said:
Are you using A to C cable?
Click to expand...
Click to collapse
Yep
V0latyle said:
What were you trying to do, and at what point did this happen?
Is your phone recognized as a Android device, or is it showing up as something else?
Does holding down the Power button + Volume Down do anything?
Click to expand...
Click to collapse
Button combination not work
Not enter fastboot mode or recovery mode
fil3s said:
If fastboot devices works type
Code:
fastboot reboot bootloader
Or use adb sideload
Click to expand...
Click to collapse
Fastboot devices works
Adb reboot bootloader cmd not works
Nordnord said:
Fastboot devices works
Adb reboot bootloader cmd not works
Click to expand...
Click to collapse
Fastboot reboot bootloader cmd not works