My phone's power button is broken. I accidentally went into recovery mode. My computer does not see my phone. How can I get rid of it? When does it run out of charge?
Samsung j6+
karmastir said:
My phone's power button is broken. I accidentally went into recovery mode. My computer does not see my phone. How can I get rid of it? When does it run out of charge?
Samsung j6+
Click to expand...
Click to collapse
Do you have ADB? is so do
Code:
adb reboot
karmastir said:
My phone's power button is broken. I accidentally went into recovery mode. My computer does not see my phone. How can I get rid of it? When does it run out of charge?
Samsung j6+
Click to expand...
Click to collapse
are you using windows? if so have you installed the usb driver? In device manager when you add a device, it will show as an unknown or fastboot device then you just need to add the driver to be able to send probably a fastboot request.
Code:
fastboot reboot
Spoiler: DRIVER STEPS IF YOU NEED
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All you need is the usb driver, you can get from android studio, your manufacturer, or you can try this one from nvidia for the shield, I use it on my phone and it works fine to be able to send fastboot requests
Shield Drivers.zip
drive.google.com
jenneh said:
are you using windows? if so have you installed the usb driver? In device manager when you add a device, it will show as an unknown or fastboot device then you just need to add the driver to be able to send probably a fastboot request.
Code:
fastboot reboot
Spoiler: DRIVER STEPS IF YOU NEED
View attachment 5756167View attachment 5756169View attachment 5756171View attachment 5756173View attachment 5756175
All you need is the usb driver, you can get from android studio, your manufacturer, or you can try this one from nvidia for the shield, I use it on my phone and it works fine to be able to send fastboot requests
Shield Drivers.zip
drive.google.com
Click to expand...
Click to collapse
Does ADB work too?
Arealhooman said:
Does ADB work too?
Click to expand...
Click to collapse
Not in this case bc the user's phone is stuck in recovery, adb is an option we can access only when the device is posted into the actual system, and we have enabled developer options, then usb or wireless debugging, then lastly adb connect. Fastboot skips everything and lets us run commands when the device is not completely online or loaded into the system
jenneh said:
Not in this case bc the user's phone is stuck in recovery, adb is an option we can access only when the device is posted into the actual system, and we have enabled developer options, then usb or wireless debugging, then lastly adb connect. Fastboot skips everything and lets us run commands when the device is not completely online or loaded into the system
Click to expand...
Click to collapse
Ah, i get it now, but doesnt samsung not have fastboot
Arealhooman said:
Ah, i get it now, but doesnt samsung not have fastboot
Click to expand...
Click to collapse
I honestly don't know, haha. I just saw this post, remembered myself in the same boat last year for a different device, and wanted to share what worked for me.
jenneh said:
I honestly don't know, haha. I just saw this post, remembered myself in the same boat last year for a different device, and wanted to share what worked for me.
Click to expand...
Click to collapse
Well, it was a good idea, but I do not think samsung supports fastboot
Arealhooman said:
Well, it was a good idea, but I do not think samsung supports fastboot
Click to expand...
Click to collapse
That's Super interesting knowledge. Thank you for sharing that with me. All the tricky ways samsung likes to use to keep things "safe". Almost makes me want to get one to play cat and mouse too but I already have an awful phone with it's own dastardly tricks. A "Nokia" mtk device with a Preloader instead of a bootloader. A "1 second handshake process" to be able to access or communicate with the preloader, no recovery, no bootloader menu, no fastboot oem commands. Haha. Terrible!
jenneh said:
That's Super interesting knowledge. Thank you for sharing that with me. All the tricky ways samsung likes to use to keep things "safe". Almost makes me want to get one to play cat and mouse too but I already have an awful phone with it's own dastardly tricks. A "Nokia" mtk device with a Preloader instead of a bootloader. A "1 second handshake process" to be able to access or communicate with the preloader, no recovery, no bootloader menu, no fastboot oem commands. Haha. Terrible!
Click to expand...
Click to collapse
I don’t even know what a preloader is could we continut talking and you can explain in dms? And a ”1 second handshake process”….
Arealhooman said:
I don’t even know what a preloader is could we continut talking and you can explain in dms? And a ”1 second handshake process”….
Click to expand...
Click to collapse
Spoiler: SHOW
Since I haven't messed with a samsung phone in almost a decade, I may be wrong, but if I had to guess, I would think that Samsungs come with a Preloader too, which is why there is a need for an external program like Odin.
But what a preloader is, is a layer below the Bootloader, it is what allows certain MTK or Qualcom devices to even be able to access the Bootloader.
I am a Nooby Cake and don't know much about anything, I just read a lot but if you are interested in what I have already read I started writing down the links for preloader knowledge on the last comment on this page of this thread and it continues into the next with nerdy rambling bs.
https://forum.xda-developers.com/t/mapping-out-the-g20s-internals.4416907/page-2
You can pm any questions just know I don't know much more than what I share on my threads haha. But I try to learn more everyday
karmastir said:
My phone's power button is broken. I accidentally went into recovery mode. My computer does not see my phone. How can I get rid of it? When does it run out of charge?
Samsung j6+
Click to expand...
Click to collapse
Go to a service centre. Repair or replace the power button. That's the best thing you can do.
ADB or FASTBOOT won't work at that situation.
.
Goddamn_srilankan said:
Go to a service centre. Repair or replace the power button. That's the best thing you can do.
ADB or FASTBOOT won't work at that situation.
Click to expand...
Click to collapse
You are telling the truth. Unfortunately, the charge does not end. lol
The first thing that came to my mind was adb, but the computer definitely does not see the device.
If I had a chance to reboot. Maybe it can see it, but it doesn't charge or I can't reboot with any key combination.
I guess the only thing to do is to repair the power button.
thanks everyone <3
karmastir said:
The first thing that came to my mind was adb, but the computer definitely does not see the device.
If I had a chance to reboot. Maybe it can see it, but it doesn't charge or I can't reboot with any key combination.
I guess the only thing to do is to repair the power button.
thanks everyone <3
Click to expand...
Click to collapse
<3
Related
Ive flashed many photon Q's before using RSD lite but for some reason now they wont even show up in AP Fastboot. IM not sure why but im wondering if it has anything to do with installing PDAnet a few weeks ago for htc drivers. RSD does however recognize my photon q booted normally. I can choose the file to flash and hit start, but where RSD used to reboot the phone into fastboot and start flashing, it says "The phone failed to switch to fastboot mode". Any help would be appreciated. I used to use RSD 6.1.4 and now use 6.1.5. This is happening with both versions. ive updated drivers, uninstalled and reinstalled drivers, uninstalled PDAnet.....
Have you tried forcing the device into fastboot mode yourself?
Code:
adb reboot bootloader
arrrghhh said:
Have you tried forcing the device into fastboot mode yourself?
Code:
adb reboot bootloader
Click to expand...
Click to collapse
the phone goes into fastboot mode. I can get it by holding vol up and down and power. The problem is that when in fastboot, it isnt recognized by RSD. where in the past it has been. it just stopped one day. the drivers fail and i go to device manager and cant find a driver that needs updating to get the phone to connect. if you know of a driver i need to install manually please let me know what it is cause nothing is jumping out as needing updating. thank you.
wbbjason said:
the phone goes into fastboot mode. I can get it by holding vol up and down and power. The problem is that when in fastboot, it isnt recognized by RSD. where in the past it has been. it just stopped one day. the drivers fail and i go to device manager and cant find a driver that needs updating to get the phone to connect. if you know of a driver i need to install manually please let me know what it is cause nothing is jumping out as needing updating. thank you.
Click to expand...
Click to collapse
Hm, I think the Motorola Device Manager was all I needed on my Windows machine.
arrrghhh said:
Hm, I think the Motorola Device Manager was all I needed on my Windows machine.
Click to expand...
Click to collapse
already had that. most recent version. uninstalled and reinstalled that as well. i have no idea why none of the photon Qs will connect now.
Try usbdeview uninstall and delete! all moto drivers and reinstall.
Photon Q &/or Note 3 on ting.com
arrrghhh said:
Hm, I think the Motorola Device Manager was all I needed on my Windows machine.
Click to expand...
Click to collapse
rbeavers said:
Try usbdeview uninstall and delete! all moto drivers and reinstall.
Photon Q &/or Note 3 on ting.com
Click to expand...
Click to collapse
Thanks for the help guys. So problem still unsolved but today I went back at it and noticed that the phone was showing up in device manager as "Samsung mobile device". So i uninstalled that driver, put it back into AP fastboot and plugged it in. now under "other devices" i have "Fastboot ASANTI_C S" and it needs to be updated. i want to make sure i update it with the correct file. if anyone knows where i can find this on my computer or the internet please let me know. it would be greatly appreciated.
wbbjason said:
Thanks for the help guys. So problem still unsolved but today I went back at it and noticed that the phone was showing up in device manager as "Samsung mobile device". So i uninstalled that driver, put it back into AP fastboot and plugged it in. now under "other devices" i have "Fastboot ASANTI_C S" and it needs to be updated. i want to make sure i update it with the correct file. if anyone knows where i can find this on my computer or the internet please let me know. it would be greatly appreciated.
Click to expand...
Click to collapse
Did you try the Moto Device Manager? That's all I recall needing for Windows.
wbbjason said:
Thanks for the help guys. So problem still unsolved but today I went back at it and noticed that the phone was showing up in device manager as "Samsung mobile device". So i uninstalled that driver, put it back into AP fastboot and plugged it in. now under "other devices" i have "Fastboot ASANTI_C S" and it needs to be updated. i want to make sure i update it with the correct file. if anyone knows where i can find this on my computer or the internet please let me know. it would be greatly appreciated.
Click to expand...
Click to collapse
If you haven't already, you can try putting the USB cable into a different USB slot. I didn't notice it before, but I had mine plugged in to a USB 3.0 slot. It worked for ADB, FASTBOOT and file transfers, so I thought nothing of it. Still the damn thing wouldn't be recognized in RSD Lite 6.5
I just switched it over to another usb slot(USB 2.0 port) and voila, works like a champ every time. You've probably already done this, but I thought I would just throw it out there.
arrrghhh said:
Did you try the Moto Device Manager? That's all I recall needing for Windows.
Click to expand...
Click to collapse
KoolBurnX8 said:
If you haven't already, you can try putting the USB cable into a different USB slot. I didn't notice it before, but I had mine plugged in to a USB 3.0 slot. It worked for ADB, FASTBOOT and file transfers, so I thought nothing of it. Still the damn thing wouldn't be recognized in RSD Lite 6.5
I just switched it over to another usb slot(USB 2.0 port) and voila, works like a champ every time. You've probably already done this, but I thought I would just throw it out there.
Click to expand...
Click to collapse
yeah i tried the device manager. uninstalled and reinstalled. and changing ports doesnt work. i have motorola drivers. like ADB QC Diag that i can install but im not sure its the right one. does anyone know the name of the driver that shows up in device manager when you plug in a photon q in AP fastboot?
wbbjason said:
yeah i tried the device manager. uninstalled and reinstalled. and changing ports doesnt work. i have motorola drivers. like ADB QC Diag that i can install but im not sure its the right one. does anyone know the name of the driver that shows up in device manager when you plug in a photon q in AP fastboot?
Click to expand...
Click to collapse
Not sure if this will help you, but here's a screenshot of Device Manager when I rebooted to bootloader (fastboot) mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I was having trouble, i've also read that RSDLite can be picky about the USB cable you use sometimes. If you have extras or have the one your phone came with, you might wanna give it a shot.
I will be straightforward:
I bought an used OPO, I booted it up, configured the phone, took a photo and then decided to reboot it (turn off and then turn on), then my device simply hard bricked.
1. I already tried turning it on, the device does nothing (no vibration).
2. I already tried using Power + Vol Up and Power + Vol Down, nothing happens (no vibration).
3. Windows recognizes the device as "QHSUSB_BULK", I already tried installing the drivers and using ColorOS flashing tool from here http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , the device IS RECOGNIZED by the tool, but when I start flashing, it starts a loop when trying to flash the "8974_msimage.mbn" file (the progress bar goes until the end and then the process repeat in the same file).
Yes, the device has the bootloader unlocked, because the previous owner flashed a custom ROM, custom kernel and SuperSU.
No, the device isn't recognized by adb.
No, the device isn't recognized by fastboot.
I already tried searching on Google for this issue, everyone who had this issue never replied saying that they fixed the issue...
I never had any kind of soft/hard brick on my Moto G 2014 (and I flashed custom ROMs constantly on it)... so... can someone help me? Thanks!
I'm also willing to give 5$ on PayPal to someone who can fix this issue.
Also, if I try to use the ColorOS flashing tool, the device disconnects in the middle of the process, causing the infinite flash loop.
First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English
sino1641 said:
First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English
Click to expand...
Click to collapse
Nah, your english is fine, I could understand what you are saying.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After I clicked "Start"
Then the "device plugged in" sound plays and the process repeats...
It keeps doing this:
(If you can't view the images, click here:
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-39-42.png
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-40-18.png
http://lori.mrpowergamerbr.com/sharex/2016-07-22_10-41-05.gif
)
Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.
sino1641 said:
Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.
Click to expand...
Click to collapse
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers
MrPowerGamerBR said:
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers
Click to expand...
Click to collapse
Open Device Manager.
Press Power &Vol Up for about 10 seconds.
See if it will change between 9008 and 9006.
I have same thing did it work
I am just wondering if u managed to fix it.
I had the exact same issue. To stop the device from disconnecting, I needed to remove all existing drivers, let the phone charge, plug it into the PC. Hold volume up + power until the PC recognises it. Then I used the color OS flashing tool.
I had to run it as administrator, and it worked fine on Windows 10, without anything extra. However remember you'll lose all your stuff. Lucky for me I had a backup of my entire phone on my PC when I switched file system to F2FS.
This issue in itself has really baffled me. It happened to me when flashing sultans rom, and the phone completely bricked. However I'm using the rom now after fully recovering the device... I guess it's just down to bad luck?
mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Nope, never fixed it, I don't even have the device anymore (now rocking a Moto G Turbo)
mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Don't use "msm8974-download-manager" use qfil to recover the phone. Worked for me.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/
Download 2012 qhs diagnostic driver and use xp machine.It will work just fine.
install a fresh windows either x32/x64 winxp/win 7 extract color OS and install the correct drivers
I have read numerous threads on how to unlock the bootloader, however after the GTab2 7.0 p3100 is/was updated to JB 4.1.2 (VRBMI1), there is nothing i have found after a few days of looking and reading. Is this bootloader locked and no way to flash a custom ROM to it? Obviously, if this is a ridiculously dumb question, then I apologize in advance and the thread should be deleted. I just really would like to flash something really minimal to the 2 GTab2's that I have laying around to use them as home automation tablets in a couple of infrequently visited areas of my house. The stock ROM is really slow imho.
I do realize this is a very old tablet so it may be just too old to do anything with, regardless thanks very much for any help in this!
If you didn't buy it from a carrier and such, it's unlocked
Its from verizon and to the best of my knowledge, it is locked. Whats the best way to be certain of this?
To check if your bootloader is locked: install adb and fastboot to your computer as well as the proper drivers, boot your tab into download mode (power+volume down) and connect it to the computer with usb cable. Open a command prompt and type "fastboot devices" (without the quotes). If everything is right you will see your tab listed. Now for the check type "fastboot getvar unlocked" (again without the quotes). If the result is yes, your bootloader is unlocked.
Ok, so I already had adb/fastboot and odin 3 v 3.12 installed. Odin3 sees the device in both on and download states. adb doesnt see it at all in either mode. Windows 10 is my OS... Device manager see the tab unplug and plug in each time and I have used multiple USB ports as well. Any ideas? Chuck the tabs in the trash perhaps?
Trash is not a good idea It's probably a driver issue. Check that you have installed the adb/fastboot drivers, maybe there is an update to some driver you haven't done or seen yet. Also, try to install for your tab specifically the adb driver through the device manager (I don't know much about windows 10 so I can't tell you exactly how to do it, perhaps right-click on the tab or from some menu).
EDIT: Since odin works, try to install twrp with it. If it fails it's locked and you need fastboot to unlock it.
Thanks for the reply,
I have reinstalled the latest adb drivers in addition to getting the latest platform-tool download for adb and fastboot - the GTab2 shows up in the device manager when plugged in. When the Tab is on, I can see it (adb devices) return a device ID. When I put the GTab2 into download mode, it does not see the device (fastboot devices). I have read that fastboot may not always return a device ID so I tried to enter the command 'fastboot getvar unlocked' and it just hangs waiting for me to plug in a device. This happens for both of the GTab2 that I have. At least I am consistent in my failure. lol
One interesting thing is that when plugged into USB in the device manager the GTab2 shows up in 2 locations when turned on. Under Modems (SAMSUNG Mobile USB Modem #4 ) and under SAMSUNG Android Phone (SAMSUNG Android ADB interface). In download mode, the device shows up only as a modem? Odd.
On one device, I installed twrp as advised and when I try to boot into recovery it now states "System software not authorized by Verizon Wireless has been found on your phone.
Please turn off your phone and go to the nearest Verizon Wireless store for help." ~meh
In download mode it now shows a custom binary download of 1 count lol - looks like I am really needing fastboot to work for me. Thanks for any help that can be provided.
zulutron said:
Thanks for the reply,
I have reinstalled the latest adb drivers in addition to getting the latest platform-tool download for adb and fastboot - the GTab2 shows up in the device manager when plugged in. When the Tab is on, I can see it (adb devices) return a device ID. When I put the GTab2 into download mode, it does not see the device (fastboot devices). I have read that fastboot may not always return a device ID so I tried to enter the command 'fastboot getvar unlocked' and it just hangs waiting for me to plug in a device. This happens for both of the GTab2 that I have. At least I am consistent in my failure. lol
One interesting thing is that when plugged into USB in the device manager the GTab2 shows up in 2 locations when turned on. Under Modems (SAMSUNG Mobile USB Modem #4 ) and under SAMSUNG Android Phone (SAMSUNG Android ADB interface). In download mode, the device shows up only as a modem? Odd.
On one device, I installed twrp as advised and when I try to boot into recovery it now states "System software not authorized by Verizon Wireless has been found on your phone.
Please turn off your phone and go to the nearest Verizon Wireless store for help." ~meh
In download mode it now shows a custom binary download of 1 count lol - looks like I am really needing fastboot to work for me. Thanks for any help that can be provided.
Click to expand...
Click to collapse
"System software not authorized by Verizon Wireless has been found on your phone.
Please turn off your phone and go to the nearest Verizon Wireless store for help."
are you really sure that you have a p3100?? it seems that you have a verizon varient of the tab 2. in this case dont flash p3100 stuff on your device. it will brick
Well, Its 3G capable and has wifi as well. I dont use it for 3G anymore though. That is P3100 afaik. Is there a more definitive way to know this?
zulutron said:
Well, Its 3G capable and has wifi as well. I dont use it for 3G anymore though. That is P3100 afaik. Is there a more definitive way to know this?
Click to expand...
Click to collapse
go to settings --- about the tablet. make a screenshot of this page and post it here.
Here it is. Thank for the help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://tinypic.com/r/2rzv3f8/9 <-- if the above doesnt work
zulutron said:
Its from verizon and to the best of my knowledge, it is locked. Whats the best way to be certain of this?
Click to expand...
Click to collapse
here you said that the tab is from verizon.
there is no rom available for your device.
i say it again
DONT FLASH P3100 STUFF ON THIS TAB !!
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
zulutron said:
Here it is. Thank for the help.
https://unsee.cc/tumezaso/ <-- if the above doesnt work
Click to expand...
Click to collapse
this is a sch-i705 and not a p3100. thats different devices
This thread calls them all SCH-i705
https://forum.xda-developers.com/showthread.php?t=1942674
zulutron said:
This thread calls them all SCH-i705
https://forum.xda-developers.com/showthread.php?t=1942674
Click to expand...
Click to collapse
look at the last 2 posts of the thread. all download links are dead since 1 year.
the best scenario for you. someone can help you out with the files. then you can install a damn old twrp recovery. with that you can backup your current system. nothing more.
there is no up to date twrp and no available rom for this device.
in this case unlocking the bootloader makes no sense, i think.
I appreciate the help for sure. I wont waste any more time on these tabs.
I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.
Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David
DvdStrbl said:
Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David
Click to expand...
Click to collapse
Well see the issue is I'm trying to get All in One to recognize my phone but it won't seem to boot into EDL mode. I installed the Qualcomm USB drivers but it's still not showing my phone. When I use the key combo suggested to boot into EDL mode my phone does refresh in device manager giving me the qualcomm device so I assume this is download mode just not displaying the text anymore. If i try the key combo with my phone unplugged it takes awhile but eventually goes into fastboot.
In this case I can't help you, i googled EDL, it is what I meant and it was all I got :-/
Wish you good luck
If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Bradl79 said:
If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
When I try flashing anything at fastboot it just hangs waiting
viralhysteria said:
I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.
Click to expand...
Click to collapse
what the problem u are facing while flashing from msm tools?
If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.
whoamanwtf said:
If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.
Click to expand...
Click to collapse
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.
viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
During Installing drivers again choose the option (something of) search from internet. And let the file be downloaded and install. Trust me this method works. I too had same problem
whoamanwtf said:
Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.
Click to expand...
Click to collapse
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?
viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
viralhysteria said:
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good. It's Android 9 but that doesn't matter, you can update from there once your phones working again.
whoamanwtf said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good.
Click to expand...
Click to collapse
It says to wait about 5 minutes after starting but I get stuck at this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work
whoamanwtf said:
Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work
Click to expand...
Click to collapse
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?
viralhysteria said:
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?
Click to expand...
Click to collapse
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.
whoamanwtf said:
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.
Click to expand...
Click to collapse
So it sounds dumb but try rebooting your computer and switching USB ports then trying again.
whoamanwtf said:
So it sounds dumb but try rebooting your computer and switching USB ports then trying again.
Click to expand...
Click to collapse
Same thing it just assigned a new COM port
I know this has probably been posted before, butI couldn't find any answers in the posts I found.
The phone has OEM Unlocking turned on in Dev options.
I tried switching off and restarting and then switching back on.
fastboot devices is recognized but all of the fastboot commands I have tried except "help" return the Error - FAILED (remote: 'unknown command')
Why would this be?
It works with 3 other phones we have here to unlock the bootloader. I don't think Ive encountered this before.
Is it possible it could require some unlock key?
Is is a 2022 no name chinese brand.
Any advice is greatly appreciated!
Thank you!
do you run it in PowerShell or CMD?
PowerShell sometimes needs extra in the sytnax or it gets the "command" confused or calls it incorrect...
defcondoc said:
fastboot devices is recognized but all of the fastboot commands I have tried except "help" return the Error - FAILED (remote: 'unknown command')
Why would this be?
Click to expand...
Click to collapse
Answer is simple: Either device isn't booted into Fastboot ( Bootloader ) mode or Fastboot commands aren't supported at all.
FYI:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
simply checks whether your device has been detected and recognized by your computer or not.
simplepinoi177 said:
do you run it in PowerShell or CMD?
PowerShell sometimes needs extra in the sytnax or it gets the "command" confused or calls it incorrect...
Click to expand...
Click to collapse
CMD
I do know what you mean when using powershell, however I haven't used that in a while.
IMO - I think it has to do with phone. I've done enough of these to know its probably the phone, but apparently not enough to know how to fix this one
Thank you!
xXx yYy said:
Answer is simple: Either device isn't booted into Fastboot ( Bootloader ) mode or Fastboot commands aren't supported at all.
FYI:
simply checks whether your device has been detected and recognized by your computer or not.
Click to expand...
Click to collapse
OK. Its booted into the Bootloader. It reads the device and serial.
Why would fastboot commands not be supported? Could the developer lock those out?
Thank you!
defcondoc said:
OK. Its booted into the Bootloader. It reads the device and serial.
Why would fastboot commands not be supported? Could the developer lock those out?
Thank you!
Click to expand...
Click to collapse
does anything come up if you do fastboot getvar all?
simplepinoi177 said:
does anything come up if you do fastboot getvar all?
Click to expand...
Click to collapse
Yes. all the usual phone info.
We have another phone here that is much older with OEM Unlocking Checked ON and can't unlock the bootloader either. It is a brand new UMX Tracfone with android 8 on it.
I'm my experience, the OEM Unlock feature is either grayed out or not available at all if the phone wasn't meant to have the bootloader unlocked.
So why have the option to unlock it, if fastboot commands won't let you unlock?
I'm wondering if you're platform-tools isn't up to date or your usb (cord or port) is doing something "funky"....
simplepinoi177 said:
I'm wondering if you're platform-tools isn't up to date or your usb (cord or port) is doing something "funky"....
Click to expand...
Click to collapse
I've checked over the most obvious stuff. I've tried two other computers as well. We don't have these problems with other phones.
Also, on the second older Tracfone. The command
Code:
fastboot flashing unlock
is accepted but it just hangs and nothing completes. I have to unplug the device and replug to access the bootloader again from CMD
I think maybe these phones need an unlock key or special file or possibly a different fastboot unlock command? I'm clueless as to why these two phones won't let me unlock the bootloader when the option to unlock is turned on.
Because these are some off brand chinese phones. Do they typically lock these types of phones down more often, disabling fastboot commands? Does anyone have experience with these types of phones that don't have access to fastboot commands? Are we wasting our time with these? Should I be asking in a different thread? Maybe a developer section?
defcondoc said:
Yes. all the usual phone info.
Click to expand...
Click to collapse
I asked because, if fastboot devices was the only thing that worked, then that just states the device is connected; whereas the getvar all proves it can actually at least read the data from the device -- doesn't prove it can write or execute other commands.
defcondoc said:
Because these are some off brand chinese phones. Do they typically lock these types of phones down more often, disabling fastboot commands? Does anyone have experience with these types of phones that don't have access to fastboot commands? Are we wasting our time with these? Should I be asking in a different thread? Maybe a developer section?
Click to expand...
Click to collapse
After a small bit of research, it does look like vendor's/manufacturer's can limit or restrict specific/certain fastboot commands...
simplepinoi177 said:
I asked because, if fastboot devices was the only thing that worked, then that just states the device is connected; whereas the getvar all proves it can actually at least read the data from the device -- doesn't prove it can write or execute other commands.
After a small bit of research, it does look like vendor's/manufacturer's can limit or restrict specific/certain fastboot commands...
Click to expand...
Click to collapse
Thanks. Yes, I seemed to have found the same info. However, it seems some are able to bypass in EDL mode. I'm not sure what that involves. It would nice to be able to delete the current rom and flash something else in EDL mode. Do you know if its possible to delete partitions in EDL mode and flash generic partitions from a another phone that has the same processor?
Or maybe we only need to target the boot.IMG. I can get into EDL mode but the software is requiring a firehose MBN file. I have tried generic and ones with the processor but have had no luck so I cannot get access to the partitions.
defcondoc said:
Thanks. Yes, I seemed to have found the same info. However, it seems some are able to bypass in EDL mode. I'm not sure what that involves. It would nice to be able to delete the current rom and flash something else in EDL mode. Do you know if its possible to delete partitions in EDL mode and flash generic partitions from a another phone that has the same processor?
Or maybe we only need to target the boot.IMG. I can get into EDL mode but the software is requiring a firehose MBN file. I have tried generic and ones with the processor but have had no luck so I cannot get access to the partitions.
Click to expand...
Click to collapse
Unfortunately, I know absolutely minimal concerning EDL mode. And because I am completely unfamiliar with the device make & model that you are attempting this with, even moreso I wouldn't even know where to begin with modifying partitions or the requirements of "firehose MBN file" and the such...
Hopefully you figure something out! Good luck to you!