On stock 5.0.2 I have tried everything i can think of: tried rooting using a oneclickroot made for the model,kingroot wont install,cant boot to download or fastboot but recovery is working, tried booting to download and fastboot using adb phone just restarts to system also tried installing apks using adb, tried using linux as root(virtual machine) and adb to flash laf.img just get errors and no permission. I likely missed something with linux? opened the phone up shorted to qhs usb dloader 9008 mode to try and use boarddiag(I did this a few years ago to fix my LS980 and boarddiag worked the first time no problem) but the D415 i just get the 2 common errors everyone gets something like no response from phone, and not found in the flash mode selecting correct com port etc. The only thing i can think of is to buy a board. If only i could just manage to flash the download mode (laf.img)
Related
My Oneplus One - 64GB was running LiquidSmooth's Alpha ROM.
I hadn't used the phone in like a month. A couple of days ago i thought there'd be an updated version so i just downloaded a later version. I think I flashed the 01-22 Build.
I did not do a full wipe however. (I realize now that It would have been a good idea to do a full wipe before the flash. :s )
I assumed that since the base of the ROM was the same lollipop, all I had to do was wipe cache/dalvik and flash the update.
Installation proceeded as usual and I wiped cache/dalvik(I'm never sure when to do this so i do it before and after install) once more and then Reboot System.
But the phone went on a bootloop for like 10minutes or so.
I tried to get into Recovery but it just wouldn't. It would just show the 1+ Logo and Powered by android screen and then turn off..
I did however manage to get into the fastboot mode by pressing power +vol up.
Now the problem is, the device doesn't show up in the command prompt when i type
Code:
fastboot devices
I uninstalled all the usb drivers from my pc.
Installed the Universal ADB drivers from kouch's site but still no progress..
Device manager still shows the phone as an unknown device.
What am I doing wrong? What can i do to get the phone to be recognized so I can flash the recovery and flash a new ROM?
It's related of firmware change. After 01.17.2015 you must flash the latest CM12 rom and then flash the rom you want.
That's a known "issue". Hope it helps.
Problem is:
1. I no longer have a working recovery(can't boot into recovery).
2. Rom doesn't boot, stuck in a bootloop.
3. Can get into fastboot mode, but pc doesn't recognize device and it doesn't show up when i type "fastboot devices".
I've already installed "Universal ADB Drivers from here -> http://www.koushikdutta.com/post/universal-adb-driver
What can i do to be able to access phone via fastboot?
Should i remove these drivers and try another driver? If so, which other driver should i install and test with?
I don't have any critical data on the phone, I just want to get it working again so my family members can decide who wants the phone.
thetearer said:
Problem is:
1. I no longer have a working recovery(can't boot into recovery).
2. Rom doesn't boot, stuck in a bootloop.
3. Can get into fastboot mode, but pc doesn't recognize device and it doesn't show up when i type "fastboot devices".
I've already installed "Universal ADB Drivers from here -> http://www.koushikdutta.com/post/universal-adb-driver
What can i do to be able to access phone via fastboot?
Should i remove these drivers and try another driver? If so, which other driver should i install and test with?
I don't have any critical data on the phone, I just want to get it working again so my family members can decide who wants the phone.
Click to expand...
Click to collapse
Uninstall all drivers, reboot PC, install those universal drivers again, reboot PC, connect phone in fastboot mode, try fastboot again.
timmaaa said:
Uninstall all drivers, reboot PC, install those universal drivers again, reboot PC, connect phone in fastboot mode, try fastboot again.
Click to expand...
Click to collapse
That's the order I did stuff in last time I believe. I'll try it again and report back
basically this is my first time trying to flash a custom recovery and after a while of trying multiple methods, none worked
i have firstly install adb,unlocked the bootloader and enabled usb debbuging
the first approach was from xda site following the tutorial, the adb reboot bootloader command just normally restarted the phone and wouldnt put me into bootloader mode, then after manually going to bootloader mode i tried to flash the img with no luck at all and the phone wasnt showing up on adb devices aswell on bootloader mode
then i tried using odin and gave it the tar file but never completed the flashing so im kind of stuck not being able to flash twrp and root the phone aswell so id appreciate your help
thanks for your time
edit: after trying again today and looking at the log, whenever i use odin it will either stop at setupConnection or recovery.img, the phone is also a galaxy j3 SM320FN
check the drivers while in download mode. fastboot devices shows you the phone while in download mode, adb devices shows you the phone while in system mode. these are different drivers. from fastboot you can boot the recovery.img without flashing for testing purposes
I just tried rooting my phone. The phone is cycling back and forth between the bootloader is unlocked screen and the Motorola splash screen.
To repeat some steps from a prior post.
My phone had QPR30.80-58-3 .
I downloaded that ROM and extracted the boot.img file.
I downloaded the latest Magisk Manager and installed it on my phone.
I ran through the patching process for boot.img.
I requested an unlock code from Motorola and unlocked the bootloader.
I flashed the patched boot image which patched partition b.
I flashed the patched boot image to partition a.
I rebooted which began the cycle.
I tried holding down the power button but it returns to the cycle.
I can get back to the bootloader with the Volume Down and Power buttons.
Any suggestions on what could get me back to a functioning phone, rooted or not rooted?
I would confirm the version of the boot image you flashed matches the version of the installed rom. You could also try to flash the unpatched / original boot.img to see if that gets you booting again.
dafunk60 said:
I would confirm the version of the boot image you flashed matches the version of the installed rom. You could also try to flash the unpatched / original boot.img to see if that gets you booting again.
Click to expand...
Click to collapse
I checked that the image I patched was from the QPR30.80-58-3 ROM which matched the level after the phone was updated.
I flashed that original boot image which flashed partition a and then rebooted. I did not flash partition b.
It first came up with the unlock warning screen. It sat on the Motorola splash screen for a noticeable amount of time followed by a yellow screen with a circle around the Motorola symbol. Finally it ended up on a blue Hello there screen with a yellow start button.
This screen was unresponsive. Eventually through various cyclings through all this I ended up on a screen that said Android could not boot and gave me an option of a factory reset. I did that but it did not help getting past the Hi there screen.
I went back and flashed the QPR30.80_58 image on both partitions a and b. This got me back to setting up the phone again. The phone is at QPR30.80_58. I am considering just rooting at this level.
So I tried patching the original QPR30.80_58 boot image. I did notice that it appeared the phone had automatically staged the QPRS30.80_58_3 update. I proceeded in (false) hopes that I could stop that.
It flashed the b partition. Ended up stuck in the bootloader unlock loop. I flashed the a partition but no change.
Previously I had ended up on a recovery screen automatically after some time. I could not force this to happen.
I tried flashing the original unpatched boot image but would end up on a non-functioning Hello there screen.
I tried adb recovery and adb shell but came back with device unauthorized.
I tried following some instructions on using fastboot erase userdata and fastboot erase cache. No change.
I finally found out that the Recovery menu was option off the bootloader screen. However, that came up with No command.
Lenovo Rescue did not want to recognize my XT2043-4 device.
I flashed the unpatched retail QPRS30.80_58_3 boot image to both a and b partitions. That got me back to a functioning phone. After getting through the login and setup steps I did find that it was at QPRS30.80_58_3.
Out of curiosity, I tried Lenovo Rescue again. I received a "Failed to match connected device. Reconnect device, then try again." which did not work.
Now I am at a loss.
DougPeterson said:
So I tried patching the original QPR30.80_58 boot image. I did notice that it appeared the phone had automatically staged the QPRS30.80_58_3 update. I proceeded in (false) hopes that I could stop that.
It flashed the b partition. Ended up stuck in the bootloader unlock loop. I flashed the a partition but no change.
Previously I had ended up on a recovery screen automatically after some time. I could not force this to happen.
I tried flashing the original unpatched boot image but would end up on a non-functioning Hello there screen.
I tried adb recovery and adb shell but came back with device unauthorized.
I tried following some instructions on using fastboot erase userdata and fastboot erase cache. No change.
I finally found out that the Recovery menu was option off the bootloader screen. However, that came up with No command.
Lenovo Rescue did not want to recognize my XT2043-4 device.
I flashed the unpatched retail QPRS30.80_58_3 boot image to both a and b partitions. That got me back to a functioning phone. After getting through the login and setup steps I did find that it was at QPRS30.80_58_3.
Out of curiosity, I tried Lenovo Rescue again. I received a "Failed to match connected device. Reconnect device, then try again." which did not work.
Now I am at a loss.
Click to expand...
Click to collapse
Happy to hear you have a working phone again! The lack of touchscreen response & the stuck at the hello screen issues are what others have reported when they used a boot image from a different version than on the phone. I suspect that something got confused between the version & slot somewhere along the way. As far as the Lenovo Rescue software not seeing the phone, it's communicating via ADB. If I recall correctly I needed to reauthorize the PC to connect via ADB after updating from 30.80-58 to 30.80-58-3. When I connect the phone via USB there's a popup on the phone asking to authorize the PC. Can you connect via ADB in the command line? If yes, you may want to reinstall the Lenovo software. If no, I would troubleshoot the ADB connection.
I originally rooted the 30.80-58 version. When 30.80-58-3 was released all I did was flash the unpatched boot.img, took the update OTA, let it reboot, then flash a patched boot.img from 30.80-58-3. All worked as expected, user data was intact.
dafunk60 said:
Happy to hear you have a working phone again! The lack of touchscreen response & the stuck at the hello screen issues are what others have reported when they used a boot image from a different version than on the phone. I suspect that something got confused between the version & slot somewhere along the way. As far as the Lenovo Rescue software not seeing the phone, it's communicating via ADB. If I recall correctly I needed to reauthorize the PC to connect via ADB after updating from 30.80-58 to 30.80-58-3. When I connect the phone via USB there's a popup on the phone asking to authorize the PC. Can you connect via ADB in the command line? If yes, you may want to reinstall the Lenovo software. If no, I would troubleshoot the ADB connection.
I originally rooted the 30.80-58 version. When 30.80-58-3 was released all I did was flash the unpatched boot.img, took the update OTA, let it reboot, then flash a patched boot.img from 30.80-58-3. All worked as expected, user data was intact.
Click to expand...
Click to collapse
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
DougPeterson said:
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
Click to expand...
Click to collapse
If you want to get into recovery, boot into the bootloader than do
Code:
fastboot reboot fastboot
That'll boot you into fastbootd which has an option to go to the real recovery
DougPeterson said:
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
Click to expand...
Click to collapse
If adb isn't showing any devices connected that would explain why the rescue software cannot find your phone. Perhaps you don't have the correct driver installed. Windows Device Manager shows the phone as a Motorola ADB Device on my PC.
View attachment 5061327
Another possibility is that you have multiple versions of adb on your PC. Older versions won't work but the adb.exe in "C:\Program Files (x86)\Rescue and Smart Assistant" works for sure. With your phone booted into android & unlocked, plug it into your PC. Do you see the "USB debugging connected" on the phone? If you don't I would re-check that USB debugging is enabled. If you do see the debugging notification, on your PC, open a command prompt and navigate to "C:\Program Files (x86)\Rescue and Smart Assistant". Run
Code:
adb devices
Does adb find your phone?
I tried installing the pixel experience rom and after I flashed the aex recovery before side loading the ROM, it went into bootloop and ended up with the stock recovery and ROM. I tried to flash TWRP recovery and go a message that the the boot/recovery image is destroyed so I tried to flash the stock boot image back and since then I am not able to get it out of fastboot mode.
I tried everything, flashing the recovery again, both stock and TWRP and also tried using the flash-all to flash the stock ROM back but nothing seems to be working.
When using the flash-all, I get 'partitions not found' and 'flashing is not allowed in critical partitions' error.
I even tried msmtool but I am not able to get my phone into edl mode for the tool to detect it.
Tried holding the vol+/vol- and connecting the usb cable but to no vain, the tool does not seem to detect it.
I even tried using the all-in-one tool but my phone is not getting detected when it is turned off but it gets detected when it's in flashboot mode from where I cannot enter edl.
Let me know if there is anything I can do to fix it? Or if taking the phone to the official service center help?
Can you reboot from fastboot to edl by entering fastboot reboot-edl? Or similar, don't know exactly anymore
Alternatively see if this can help you getting into edl: https://forum.xda-developers.com/t/guide-how-to-reboot-to-edl-from-fastboot.3394292/
Hi guys, I Have Pixel 3 with Custom twrp recovery one day I accidentally wiped my internal storage and data everything After I cannot get into boot my phone , then I tried with USB it shows 0 mb ,And I mess up with twrp settings everywhere after I changed boot slot b to a and reboot BOOM everything stuck a slot have nothing after I noticed I cannot get into recovery now, its stuck in to fast boot mode but my PC cannot detect my device even though driver installed now what I do please .
Musthafa_3679 said:
Hi guys, I Have Pixel 3 with Custom twrp recovery one day I accidentally wiped my internal storage and data everything After I cannot get into boot my phone , then I tried with USB it shows 0 mb ,And I mess up with twrp settings everywhere after I changed boot slot b to a and reboot BOOM everything stuck a slot have nothing after I noticed I cannot get into recovery now, its stuck in to fast boot mode but my PC cannot detect my device even though driver installed now what I do please .
Click to expand...
Click to collapse
can you get into fastboot? if so, you will probably have to start over. choose the right carrier. if you don't know it or aren't 100% sure, select other. You could also try this one.
DragonFire1024 said:
can you get into fastboot? if so, you will probably have to start over. choose the right carrier. if you don't know it or aren't 100% sure, select other. You could also try this one.
Click to expand...
Click to collapse
I tried google flash tool but my device not detected ,adb not response and fastboot . but it always boot in fastboot but why my PC isn't get device and I tried to go edl but I can't find the way to boot edl please help
Musthafa_3679 said:
I tried google flash tool but my device not detected ,adb not response and fastboot . but it always boot in fastboot but why my PC isn't get device and I tried to go edl but I can't find the way to boot edl please help
Click to expand...
Click to collapse
The standard things to try when the device is not recognized are:
1. Update drivers
2. Make sure you are using the latest version of platform tools from https://developer.android.com/studio/releases/platform-tools
3. Try different USB ports and cables, preferably USB 2.0. USB 3.0 may not work.
4. Try a different PC.
Are you using "fastboot devices" to detect the device? "adb devices" does not work in fastboot mode.
dcarvil said:
The standard things to try when the device is not recognized are:
1. Update drivers
2. Make sure you are using the latest version of platform tools from https://developer.android.com/studio/releases/platform-tools
3. Try different USB ports and cables, preferably USB 2.0. USB 3.0 may not work.
4. Try a different PC.
Are you using "fastboot devices" to detect the device? "adb devices" does not work in fastboot mode.
Click to expand...
Click to collapse
Yes I tried fastboot mode , I installed latest platform tools my mobile don't have any os inside I wiped everything how it will find through platform tools?
And its always fast boot mode whenever I try to boot recovery or normal boot it says error to preloade images , some times no valid slot to boot if I can detect by PC I may be I can change boot slot