When I plug my phone into my computer and run RSD Lite, no phone appears. The operating system of the phone is completely shot, so I need to flash an image of a fresh operating system. I can't do this without being able to use RSD Lite. Motorola Device Manager doesn't seem to be recognizing any available drivers for the device. I really need this phone unbricked. Any answer would be great.
I guess you should leave your phone in bootloader mode.
In order for RSD lite to work, you have to put your device into bootloader mode by holding vol down while you power on. Also, you need to make sure that you have a version of RSD lite that supports it. I've used 6.2.4 successfully.
TheSt33v said:
In order for RSD lite to work, you have to put your device into bootloader mode by holding vol down while you power on. Also, you need to make sure that you have a version of RSD lite that supports it. I've used 6.2.4 successfully.
Click to expand...
Click to collapse
The phone is in bootloader mode and I'm using version 6.2.4.
roll11tide said:
The phone is in bootloader mode and I'm using version 6.2.4.
Click to expand...
Click to collapse
If that's the case, and your phone is still not recognized, there is either a driver problem or a physical connection problem. Assuming you're on Windows, open the device manager. When you plug in the phone, does a new device appear? If so, your problem is likely driver related. If not, there is a problem with the physical connection, which you can troubleshoot by using a different USB port and/or USB cable.
TheSt33v said:
If that's the case, and your phone is still not recognized, there is either a driver problem or a physical connection problem. Assuming you're on Windows, open the device manager. When you plug in the phone, does a new device appear? If so, your problem is likely driver related. If not, there is a problem with the physical connection, which you can troubleshoot by using a different USB port and/or USB cable.
Click to expand...
Click to collapse
I've ttried using different USB ports and cords. Yes, I tried the cord that came with the phone.
roll11tide said:
I've ttried using different USB ports and cords. Yes, I tried the cord that came with the phone.
Click to expand...
Click to collapse
Okay. So if it's in bootloader mode, and absolutely nothing happens in the windows device manager when you plug in the phone (no connected device sound, no unknown device, no known device, no nothing), and you're positive that that USB cable/ports on your PC are working, then it sounds like the USB port on your phone has stopped working, in which case there isn't much you can do. If there is no obvious physical damage, and the phone was never exposed to water, I would try getting Motorola (not Verizon) to replace it. It's free.
TheSt33v said:
Okay. So if it's in bootloader mode, and absolutely nothing happens in the windows device manager when you plug in the phone (no connected device sound, no unknown device, no known device, no nothing), and you're positive that that USB cable/ports on your PC are working, then it sounds like the USB port on your phone has stopped working, in which case there isn't much you can do. If there is no obvious physical damage, and the phone was never exposed to water, I would try getting Motorola (not Verizon) to replace it. It's free.
Click to expand...
Click to collapse
Something happens, it is just recognized as a Fastboot Quark S.
roll11tide said:
Something happens, it is just recognized as a Fastboot Quark S.
Click to expand...
Click to collapse
Hmm. Well then it is set up correctly. If you can't get RSDlite to work, you could always flash your images manually, since basically all RSDlite does is automate the Fastboot commands that are necessary to do this.
1. Install Minimal ADB and Fastboot (or get Fastboot set up in the way of your choice).
2. Unzip the contents of the firmware that you're trying to flash to the same directory as Fastboot.exe.
3. Look for the .bat file that came in the firmware zip and edit it. You should see all of the fastboot commands necessary to flash the firmware.
4. Start fastboot and perform those commands (in the order that they appear) while the phone is in bootloader mode and plugged into the computer.
TheSt33v said:
Hmm. Well then it is set up correctly. If you can't get RSDlite to work, you could always flash your images manually, since basically all RSDlite does is automate the Fastboot commands that are necessary to do this.
1. Install Minimal ADB and Fastboot (or get Fastboot set up in the way of your choice).
2. Unzip the contents of the firmware that you're trying to flash to the same directory as Fastboot.exe.
3. Look for the .bat file that came in the firmware zip and edit it. You should see all of the fastboot commands necessary to flash the firmware.
4. Start fastboot and perform those commands (in the order that they appear) while the phone is in bootloader mode and plugged into the computer.
Click to expand...
Click to collapse
I have tried flashing multiple images with ADB and fastboot, but neither of them work. Sometimes it will flash and it doesn't work, and sometimes the sparsechunks just don't get accepted into the OS. I do not know why this is happening, but I have gotten fastboot to do something to the phone, it just didn't produce any results.
Well...that's bizarre. The only reasons I can think of for a sparsechunk not successfully flashing is that it's not the right image for your model of phone, you're trying to flash an OTA update zip instead of a full firmware zip or you're trying to flash an image that is a lower version than your bootloader's version. I'm not sure what to make of the fact that it sometimes flashes successfully and sometimes does not. However, if flashing all of the images in the full firmware zip does not help you, using RSDlite won't help you either since it does the exact same thing. If I were you, I'd try to get Motorola to replace it. It's really easy to do. You pretty much just fill out a form and they send you a new one. Sorry I can't be of more help.
TheSt33v said:
Well...that's bizarre. The only reasons I can think of for a sparsechunk not successfully flashing is that it's not the right image for your model of phone, you're trying to flash an OTA update zip instead of a full firmware zip or you're trying to flash an image that is a lower version than your bootloader's version. I'm not sure what to make of the fact that it sometimes flashes successfully and sometimes does not. However, if flashing all of the images in the full firmware zip does not help you, using RSDlite won't help you either since it does the exact same thing. If I were you, I'd try to get Motorola to replace it. It's really easy to do. You pretty much just fill out a form and they send you a new one. Sorry I can't be of more help.
Click to expand...
Click to collapse
Thanks, I am already in the process of having Motorola replace the phone as I figured that would be the most logical option. Thanks for all the help! I will leave this thread open as a mystery to the community that hopefully someone will solve and in the process help someone else.
Related
Hi Guys!
I was just regular using my phone for the last few months and then suddenly yesterday it decided to get crazy. First the green light was blinking and I couldn't acess my cellphone, so I rebooted and then it all started.
It stops at the Motorola logo.
I can acess the fastboo flash mode, tried to factory reset or either recovery, but once again stops at the same motorola screen
If I turn if off, I can see the charging status of the phone.
I know nothing about flashing, I've looked around and my XT890 it's a retail version, but I don't know what to download and such. And the worst case is that I'm traveling around US and I'll be here for anothers 12 days and I really need my cellphone back.
kursku said:
Hi Guys!
I was just regular using my phone for the last few months and then suddenly yesterday it decided to get crazy. First the green light was blinking and I couldn't acess my cellphone, so I rebooted and then it all started.
It stops at the Motorola logo.
I can acess the fastboo flash mode, tried to factory reset or either recovery, but once again stops at the same motorola screen
If I turn if off, I can see the charging status of the phone.
I know nothing about flashing, I've looked around and my XT890 it's a retail version, but I don't know what to download and such. And the worst case is that I'm traveling around US and I'll be here for anothers 12 days and I really need my cellphone back.
Click to expand...
Click to collapse
You can restore it easily with RSD Lite.
Just download it here: http://www.4shared.com/rar/vYYHCwBj/RSDLite57.html
And then download a factory image from here: http://forum.xda-developers.com/showthread.php?t=2239706
(Select the one you find appropiate)
Make sure you have the Moto drivers installed, your bootloader is unlocked and then install RSD Lite and extract the image somewhere.
Connect your phone in fastboot, open RSD Lite, and in filename browse to the folder whre you extracted the image and select the .xml file in it.
Then press start and wait.
tatazeuz said:
You can restore it easily with RSD Lite.
Just download it here: http://www.4shared.com/rar/vYYHCwBj/RSDLite57.html
And then download a factory image from here: http://forum.xda-developers.com/showthread.php?t=2239706
(Select the one you find appropiate)
Make sure you have the Moto drivers installed, your bootloader is unlocked and then install RSD Lite and extract the image somewhere.
Connect your phone in fastboot, open RSD Lite, and in filename browse to the folder whre you extracted the image and select the .xml file in it.
Then press start and wait.
Click to expand...
Click to collapse
And it's the fastest and best way for doing it, and void the warranty, right?
Still I can't connect withing the RSD. My cellphone is connected, I can see it in the fastload screen
"USB connected", but can't get it to be shown in the "Show device" in RSD. What can I do now?
kursku said:
Still I can't connect withing the RSD. My cellphone is connected, I can see it in the fastload screen
"USB connected", but can't get it to be shown in the "Show device" in RSD. What can I do now?
Click to expand...
Click to collapse
Make sure you have this installed
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
tatazeuz said:
Make sure you have this installed
Click to expand...
Click to collapse
I intalled and uninstalled to see if changed anything. It seems that it doesn't work.
I'm using a Windows 8 64x version, does it has anything to do with it?
kursku said:
I intalled and uninstalled to see if changed anything. It seems that it doesn't work.
I'm using a Windows 8 64x version, does it has anything to do with it?
Click to expand...
Click to collapse
I don't think so. My Windows 8.1 x64 works fine.
Have you tried different usb ports? That made a difference for me once.
tatazeuz said:
I don't think so. My Windows 8.1 x64 works fine.
Have you tried different usb ports? That made a difference for me once.
Click to expand...
Click to collapse
Yes I did, when It's charging and not in Fastboot, it shows up in the computer connected to de USB. When I change to the fastboot it doesn't show as connected. Even though I can use the cmd to work things out, but can't use it to flash it.
So, it works in a weird way all of them.
Those are the pictures of the connected cellphone, when it's in fastboot it shows as fastboot. When it's charging shows as XT890.
kursku said:
So, it works in a weird way all of them.
Those are the pictures of the connected cellphone, when it's in fastboot it shows as fastboot. When it's charging shows as XT890.
Click to expand...
Click to collapse
Start the phone i nfastboot then try the command "fastboot devices"
Send me a screen. Your PC doesnt seem to recognize the device very well.
I'll try to get a different computer tro try it, but so far no success
Try to put your ADB and Ri files to C:\"your foldername". It could be that there are problems when the files are in your user-accounts folders.
Did you already tried to connect with USB on the backside of your PC? Frontside are mostly hubs which could cause trouble.
via Razr I & Tapatalk 4
ICuaI said:
Try to put your ADB and Ri files to C:\"your foldername". It could be that there are problems when the files are in your user-accounts folders.
Did you already tried to connect with USB on the backside of your PC? Frontside are mostly hubs which could cause trouble.
via Razr I & Tapatalk 4
Click to expand...
Click to collapse
Can I do it with the CMD without the RSI?
What does RSI mean?
via Xoom 2 & Tapatalk 4
So I got carried away with trying to get rid of that three dot menu button at the bottom of the screen and I've slowly managed to work myself into a really bad problem. I'm not necessarily new to this, I've rooted my Droid 2, Droid 3, and GS3, but this has been more complicated for me.
Anyways, my problem is, I was trying to wipe my phone so that I could flash a ROM. This is because I couldn't access my settings (I overwrote the original in an attempt to get rid of the multitask button). But while I was in CWM I factory reset it but I also accidentally deleted the system. My bootloader is unlocked, but now my phone is on and I can't get into recovery, and I'm assuming it's because the whole system is gone so there's nothing to boot.
Another problem I had (while my phone was able to boot up completely), Android File Transfer wouldn't work, I downloaded a rom for the settings.apk but it wouldn't let me transfer files between my computer and phone. I emailed the .apk to myself but since I couldn't access settings I wasn't able to pick my usual email (although now I'm thinking I should have just used the email I first signed in with). Not as much of a concern but input is still welcome.
I've looked up RUU but it looks like it's not available yet for Verizon. Any possible solutions would be MUCH appreciated.
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Gudio142 said:
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Click to expand...
Click to collapse
I'm stuck on the green HTC logo screen and the red warning about the bootloader. I can't boot into recovery anymore. By the way I'm using a Mac but I do have a PC running Windows 8 if there's solutions I could try
Gudio142 said:
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Click to expand...
Click to collapse
I tried flashing into recovery via fastboot but my computer doesn't recognize my device. And I'm pretty sure I had drivers installed since that's how I unlocked the bootloader in the first place..
xerhoffx said:
I tried flashing into recovery via fastboot but my computer doesn't recognize my device. And I'm pretty sure I had drivers installed since that's how I unlocked the bootloader in the first place..
Click to expand...
Click to collapse
Install the latest drivers and try from a windows 7 pc (or windows 8, win 8.1 doesn't work well)
Reinstall drivers if you haven't already and try the correct file for your 'Modelid' here. It's the only way I got mine to work again after i did the same thing.
Note: The file i used had a different software version but it still flashed ok.
After that, if you can find the right Nandroid you now have the ability to flash that
n1234d said:
Install the latest drivers and try from a windows 7 pc (or windows 8, win 8.1 doesn't work well)
Click to expand...
Click to collapse
I only have Windows 8 I believe...
xerhoffx said:
I only have Windows 8 I believe...
Click to expand...
Click to collapse
Try a different PC, worked for another guy whose pc wouldn't detect his phone. See if a pc with XP works..
ndulian increase
jingles98 said:
Reinstall drivers if you haven't already and try the correct file for your 'Modelid' here. It's the only way I got mine to work again after i did the same thing.
Note: The file i used had a different software version but it still flashed ok.
After that, if you can find the right Nandroid you now have the ability to flash that
Click to expand...
Click to collapse
Where could I find a nandroid for Verizon? I feel like Verizon is the most difficult to find.
FIXED
I was finally able to boot into recovery and thank goodness had a CWM backup. Thanks for your input guys.
Was running stock 5.0.1 with a decrypted boot.img. Rooted, unlocked, modified build.prop, TWRP, Franco kernel. Lost ability to connect to a PC, so I can't update manually (that's for another conversation). So I need the 5.1 OTA. I unrooted through SuperSu, flashed stock recovery and stock kernel. Did a factory reset. For some reason, my build.prop stayed modified.
The OTA will download, but fails to install...simply saying "error." Any advice on what could be preventing the OTA from installing?? I was hoping this update would fix my device-to-PC connection.
Thanks
ryan4a said:
Was running stock 5.0.1 with a decrypted system.img. Rooted, unlocked, modified build.prop, TWRP, Franco kernel. Lost ability to connect to a PC, so I can't update manually (that's for another conversation). So I need the 5.1 OTA. I unrooted through SuperSu, flashed stock recovery and stock kernel. Did a factory reset. For some reason, my build.prop stayed modified.
The OTA will download, but fails to install...simply saying "error." Any advice on what could be preventing the OTA from installing?? I was hoping this update would fix my device-to-PC connection.
Thanks
Click to expand...
Click to collapse
Flash system.img and userdata.img and reboot.
gee2012 said:
Flash system.img and userdata.img and reboot.
Click to expand...
Click to collapse
I'm probably more of a noob than I should be and may be in over my head. But how exactly would I flash those images without a PC or root access? Through stock recovery? Where do I find those files?
ryan4a said:
I'm probably more of a noob than I should be and may be in over my head. But how exactly would I flash those images with a PC or root access? Through stock recovery? Where do I find those files?
Click to expand...
Click to collapse
Extract the Google factory image and flash both img`s in fastboot/bootloader, here is a guide http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
ryan4a said:
I'm probably more of a noob than I should be and may be in over my head. But how exactly would I flash those images with a PC or root access? Through stock recovery? Where do I find those files?
Click to expand...
Click to collapse
You can't. You're pretty screwed to be honest, you'll need to have that other conversation about your USB connection now.
gee2012 said:
Extract the Google factory image and flash both img`s in fastboot/bootloader, here is a guide http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Click to expand...
Click to collapse
Thanks again. But this tutorial says
"Boot it in fastboot(bootloader mode) by pressing and holding Power Button + Volume Down at the same time.
Connect your phone to your PC through your USB cable."
Again, my device is not recognized by any computer, even in fastboot mode. Anyway to do this without a PC?
ryan4a said:
Thanks again. But this tutorial says
"Boot it in fastboot(bootloader mode) by pressing and holding Power Button + Volume Down at the same time.
Connect your phone to your PC through your USB cable."
Again, my device is not recognized by any computer, even in fastboot mode. Anyway to do this without a PC?
Click to expand...
Click to collapse
No, not possible without a pc i`am afraid.
gee2012 said:
No, not possible without a pc i`am afraid.
Click to expand...
Click to collapse
Thanks for your help. So if I have stock rom, stock recovery, and stock kernel, why would the OTA fail? I thought unrooting and factory reset would have and put everything back to original. I’m just trying to get the update. Do I need to clean up any other system files? Without root access, I can’t change my build.prop back to original, but I wouldn’t think that would have any effect.
I'm on a Nexus 6 by the way.
ryan4a said:
Thanks for your help. So if I have stock rom, stock recovery, and stock kernel, why would the OTA fail? I thought unrooting and factory reset would have and put everything back to original. I’m just trying to get the update. Do I need to clean up any other system files? Without root access, I can’t change my build.prop back to original, but I wouldn’t think that would have any effect.
I'm on a Nexus 6 by the way.
Click to expand...
Click to collapse
Does the phone boot-up? If yes enable usb debugging and you should get connected and the phone is recognised.. Test if the device is recognised in adb with cmd terminal: adb devices and in fastboot/bootloader: fastboot devices.
Try downloading the latest fastboot drivers, I had the same issue and until i installed the latest ones, it wasnt being detected.
ryan4a said:
Thanks for your help. So if I have stock rom, stock recovery, and stock kernel, why would the OTA fail? I thought unrooting and factory reset would have and put everything back to original. I’m just trying to get the update. Do I need to clean up any other system files? Without root access, I can’t change my build.prop back to original, but I wouldn’t think that would have any effect.
I'm on a Nexus 6 by the way.
Click to expand...
Click to collapse
Root modified system in a way that only reflashing the system image will fix. This was changed when lollipop launched.
---------- Post added at 04:34 PM ---------- Previous post was at 04:31 PM ----------
Oh and if you decrypted, you'll have to flash boot img too.
gee2012 said:
Does the phone boot-up? If yes enable usb debugging and you should get connected and the phone is recognised.. Test if the device is recognised in adb with cmd terminal: adb devices and in fastboot/bootloader: fastboot devices.
Click to expand...
Click to collapse
Yes, phone boots up and runs fine. USB debugging is enabled, but still not recognized. At best, I'll get an "unknown device" in device manager. I can't get the Nexus Root Toolkit to recognize it either, even after using the USBDeview.
fkofilee said:
Try downloading the latest fastboot drivers, I had the same issue and until i installed the latest ones, it wasnt being detected.
Click to expand...
Click to collapse
Where would I get the latest fastboot drivers?
ryan4a said:
Yes, phone boots up and runs fine. USB debugging is enabled, but still not recognized. At best, I'll get an "unknown device" in device manager. I can't get the Nexus Root Toolkit to recognize it either, even after using the USBDeview.
Where would I get the latest fastboot drivers?
Click to expand...
Click to collapse
I use the Google usb drivers, they are in the /android-sdk/ Extras/Google/usb_drivers/ folder
Or, try this:
http://forum.xda-developers.com/showthread.php?t=2588979
gee2012 said:
I use the Google usb drivers, they are in the /android-sdk/ Extras/Google/usb_drivers/ folder
Click to expand...
Click to collapse
Thanks. That was one of the first things I tried. I downloaded the updated drives, but not sure I "installed" them. Still not recognizing my device on any PC or Mac. I'm hoping it's not hardware, because it charges fine when connected to a PC.
ryan4a said:
Thanks. That was one of the first things I tried. I downloaded the updated drives, but not sure I "installed" them. Still not recognizing my device on any PC or Mac. I'm hoping it's not hardware, because it charges fine when connected to a PC.
Click to expand...
Click to collapse
Try a different USB cable
cam30era said:
Try a different USB cable
Click to expand...
Click to collapse
That was one of the other things I first tried.
ryan4a said:
That was one of the other things I first tried.
Click to expand...
Click to collapse
Connect the device to the pc, if the phone shows up in device manager uninstall the device, disconnect and the reconnect the phone and choose manual usb driver install and choose the Google usb drivers and all should be ok.
ryan4a said:
I'm hoping it's not hardware, because it charges fine when connected to a PC.
Click to expand...
Click to collapse
Doesnt indicate anything. Data connection uses more USB pins than charging.. Double check your USB port to check for obstruction or pin damage.
Thanks everyone. I've tried multiple cables and multiple computers. Still nothing. At best, I can only get my phone to show up as an "unknown device" in device manager. Then when I manually install the Google drivers, it says "drivers already installed." Or it will install the drivers in like 1 second and finish. But still no connection. I'll keep trying. Otherwise, I'm screwed and will need to keep my non-rooted device on 5.0.1.
Alright guys, I'll get right to the point with this one. So I was flashing a stock image to get back to Marshmallow from N preview 3, and for whatever reason, I couldn't get my system partition to flash! It would begin, and then just finish early. When I tried again, it kept telling me that the file was in use in another program. I made a new copy of my platform tools and the stock image I needed, and it did the same thing! My first thought was a corrupted system partition, and I was really hoping it wasn't that. I got it to work using my sister's really really slow Windows Vista laptop (not kidding, took an HOUR to flash) and that worked. Since then I reinstalled windows on my main laptop, but was wondering just what could have caused that? It kept partially flashing the image, and then saying it was in use right after when I tried to do it again. Sorry this isn't too much to go on, I don't have screens or logs or anything to help the case, but suggestions? Thanks all!
H4X0R46 said:
.... I got it to work using my sister's really really slow Windows Vista laptop (not kidding, took an HOUR to flash) and that worked.
Click to expand...
Click to collapse
Hardware issue or wrong drivers. Your PC - USB port - USB cable - drivers or drivers not correct/installed wrong drivers.
Before fastboot check PC in device manager if your phone is recognized.
Download toolkit of wugfresh. After installing there is a sub folder with drivers and also as a sub folder with fastboot and adb.
Install the drivers and use the fastboot/adb and check/try again.
NLBeev said:
Hardware issue or wrong drivers. Your PC - USB port - USB cable - drivers or drivers not correct/installed wrong drivers.
Before fastboot check PC in device manager if your phone is recognized.
Download toolkit of wugfresh. After installing there is a sub folder with drivers and also as a sub folder with fastboot and adb.
Install the drivers and use the fastboot/adb and check/try again.
Click to expand...
Click to collapse
Sure hope it wasn't hardware. That would be bad. My sister's did it without problem despite the amount of time it took lol. I always use my laptop to flash images, it just chose today to do that. It's really weird at that, never seen that happen before. Fastboot devices command showed that it was connect and seen, so that's even more strange.
Also, does anyone know a sure fire way to check if my system partition is actually getting corrupted? Or is that much more extensive?
H4X0R46 said:
Also, does anyone know a sure fire way to check if my system partition is actually getting corrupted? Or is that much more extensive?
Click to expand...
Click to collapse
In case the system partition is corrupted the phone will not boot. And the partition will not mount in TWRP recovery.
NLBeev said:
In case the system partition is corrupted the phone will not boot. And the partition will not mount in TWRP recovery.
Click to expand...
Click to collapse
Well, my device boots and I as able to flash xposed with out and issues so that's not the case. Might have just been my computer acting up. Thanks for your input! It helps a lot!
hello everyone. the guys disconnected the usb cable during the firmware and now the phone doesn’t turn on and nothing happens, even in recovery mode it doesn’t enter what to do. tell me. rp2 device.
Gayrat1999 said:
hello everyone. the guys disconnected the usb cable during the firmware and now the phone doesn’t turn on and nothing happens, even in recovery mode it doesn’t enter what to do. tell me. rp2 device.
Click to expand...
Click to collapse
What do you mean it doesn't turn on? You say you are able to get to recovery mode but if it doesn't turn on you shouldn't be able to do this.
reset the stock via adb cli
ComCurio said:
What do you mean it doesn't turn on? You say you are able to get to recovery mode but if it doesn't turn on you shouldn't be able to do this.
Click to expand...
Click to collapse
did you try to flash stock build via adb cli via flash_all.bat(windows) for ./flash_all.sh(Mac). except this time let it finish. if you can get into recovery this should work. just make sure you have installed your android drivers first. once in recovery try to see if device is connected via fastboot devices command. then try the flash_all command. I usaully dump the firmware in the same directory as the platform-tools and just rename it to something like platform-tools - razor Firmware build and make another for kernel build. since I have multiple andriod devices it helps to keep them separate.
op, can you access bootloader? if so, all you will need to do is find a USB C adapter that wont be picky with flashing and flash the stock firmware. The included USB C to C does not work for this (in my experience.) The USB C to C adapter I found worked for flashing for me is: https://www.amazon.com/Blackweb-3-Foot-Charge-Cable-Connector/dp/B07SG7P3KZ/
we need more details to accurately assist you op!