Related
Hello
Currently my phone is useless, I am blaming myself but somewhat of the ROM I used before this all happened.
For starters, my bootloader is unlocked and s-on. I successfully installed TWRP and rooted using SuperSU. I wanted to try out the custom ROM ViperOne. It installed perfectly fine without any errors. But when I rebooted the phone I am greeted with the lockscreen with no service (x by the bars) and when I go to unlock the phone it goes to a white screen with the HTC logo in the center. It will continue to stay at this screen till it reboots again and does the same thing.
At this point I am frustrated and followed this guide http://forum.xda-developers.com/showthread.php?t=2503646 to revert back to Stock. I was able to do every step correctly besides the flashing of the radio and pushing the Stock_Rom on the phone.
I was able to install the stock rom by putting it on my internal storage and flashing it that way, but still no luck with the radio. But now the Stock_Rom is doing the exact same thing as the Viper, Whitescreen with HTC. Plus it is constantly saying "Unfortunately Phone has stopped" making it unusable.
If someone could please help me out or direct me to another tut to follow I will appreciate it very much. Because at this point I am to believe that I bricked my device and I am unaware if I am able for an upgrade anytime soon.
Thank you for you time.
A little update.
I am not starting to think this whole problem has to do with my radio, simply I do not have 1. How do I get this working again?
Another update.
I tried to follow this guide http://forum.xda-developers.com/showthread.php?t=2250904 (Very helpful btw :good
But still no luck, it froze me at the black screen with HTC and no loading bar.
I just want to be able to use my phone again :crying:
Everything you need is in the first link you posted.
BD619 said:
Everything you need is in the first link you posted.
Click to expand...
Click to collapse
Thank you for your response.
Like I sad, I tried that link already but with no luck. I could be doing something wrong, but I am following word for word.
kavinsky_ep said:
Thank you for your response.
Like I sad, I tried that link already but with no luck. I could be doing something wrong, but I am following word for word.
Click to expand...
Click to collapse
Latest radio can be found HERE
BD619 said:
Latest radio can be found HERE
Click to expand...
Click to collapse
I've downloaded 1.00.20.1108 and I am trying to flash it using fastboot flash zip radio.zip (I renamed it to type it in easier).
But every time I press enter it does signature checking... then it says FAILD (remote: 12 signature verify fail)
Any ideas?
kavinsky_ep said:
I've downloaded 1.00.20.1108 and I am trying to flash it using fastboot flash zip radio.zip (I renamed it to type it in easier).
But every time I press enter it does signature checking... then it says FAILD (remote: 12 signature verify fail)
Any ideas?
Click to expand...
Click to collapse
Flash in recovery like the instructions say lol
BD619 said:
Flash in recovery like the instructions say lol
Click to expand...
Click to collapse
Ok, thank you again. I will try this. I hope to god it works
Sigh. Another problem
After performing the wipe with TWRP and then i type in the cmd adb push nameofrom.zip /sdcard/ but I get the following error in cmd.
adb server is out of date. killing...
* daemon started successfully *
I am confused by this because my drivers are up to date, unless this is a different problem. Any ideas?
kavinsky_ep said:
Sigh. Another problem
After performing the wipe with TWRP and then i type in the cmd adb push nameofrom.zip /sdcard/ but I get the following error in cmd.
adb server is out of date. killing...
* daemon started successfully *
I am confused by this because my drivers are up to date, unless this is a different problem. Any ideas?
Click to expand...
Click to collapse
It's normal for it to say that.
Do you get your serial number returned when you type
adb devices
BD619 said:
It's normal for it to say that.
Do you get your serial number returned when you type
adb devices
Click to expand...
Click to collapse
Hey! I fixed it, I was able to quickly put the radio.zip into my internal storage before the phone could freak out. Went into TWRP and flashed that *****! IT WORKS!
No more custom ROMS for me, I'll just stick to rooting and keeping stock rom.
I would like to thank you for helping me throughout this, I really appreciate this. :good:
btw, if I were unable to do it the way I did, how would I fix it to work with the adb push command?
kavinsky_ep said:
Hey! I fixed it, I was able to quickly put the radio.zip into my internal storage before the phone could freak out. Went into TWRP and flashed that *****! IT WORKS!
No more custom ROMS for me, I'll just stick to rooting and keeping stock rom.
I would like to thank you for helping me throughout this, I really appreciate this. :good:
btw, if I were unable to do it the way I did, how would I fix it to work with the adb push command?
Click to expand...
Click to collapse
Depends what is causing the adb to be wonky most likely it's a driver issue.
Drivers install while booted to OS,Recovery,and fastboot.
BTW when you were doing the adb push romname.zip /sdcard/ were you in recovery or OS?
You are very welcome btw
BD619 said:
Depends what is causing the adb to be wonky most likely it's a driver issue.
Drivers install while booted to OS,Recovery,and fastboot.
BTW when you were doing the adb push romname.zip /sdcard/ were you in recovery or OS?
You are very welcome btw
Click to expand...
Click to collapse
I was in my recovery, TWRP. and using my computer with the CMD. Or by OS do you mean my phone OS. Because I was unable to use my Phone due to the radio not being there.
kavinsky_ep said:
I was in my recovery, TWRP. and using my computer with the CMD. Or by OS do you mean my phone OS. Because I was unable to use my Phone due to the radio not being there.
Click to expand...
Click to collapse
Most likely the drivers were not installed properly while booted to twrp...there are instructions in my guide that will show you how to install them properly.
I was wondering if the phone was booted to OS.
Get yourself S-OFF, and many flashing woes disappear. I have soft-bricked my phone with a Viper myself. You have to be sure you install the correct carrier version and think twice about installing kernels in ViperHub (or whatever they call it). If you install a GSM anything to your Sprint phone, your radio will go away. An RUU will fix this though. Windows 8 does not play well with ADB on our phones, either.
Sent from my One using Tapatalk
I'm having the SAME exact problems as you. Went to flash Viper rom and just get stuck on the white screen with the HTC logo. Glad I'm not the only one!
Hopefully I'll be able to fix mine as well!
Hey guys,
I just flashed the my Moto X (unlocked) to stock 4.4.4, booted up, wanted to flash twrp but after that the recovery just didn`t appear.
So flashed stock 4.4.4 again but now every time i try to flash system.img it says "download failed". I am using the mfastboot.exe and I follow this tutorial: http://mark.cdmaforums.com/MotoX-ReturnToStock.html (option 5)
Everytime I flash something via mfastboot there is the line "(bootloader) Variable not supported!" written before starting to flash, but it is working anyway, except system.img...
Can somebody give me a hint what I am doing wrong?
I just can enter the bootloader and I´m afraid if it runs out of juice I cannot charge it any more.
Solved, tried it serveral times again and it`s working now!
jay-em-ass said:
Solved, tried it serveral times again and it`s working now!
Click to expand...
Click to collapse
What was the solution? Did you try anything different or did you just repeat steps and got lucky?
Sent from my XT1058 using XDA Free mobile app
cxwong1 said:
What was the solution? Did you try anything different or did you just repeat steps and got lucky?
Click to expand...
Click to collapse
Unistalled Motorola Software, reinstalled stock Google ADB drivers and tried it again.
"bootloader" message was still there, but everything flashed fine. Tbh I don't think it was a driver problem...
Strange, but glad to hear everything worked out via re-installation.
jay-em-ass said:
Unistalled Motorola Software, reinstalled stock Google ADB drivers and tried it again.
"bootloader" message was still there, but everything flashed fine. Tbh I don't think it was a driver problem...
Click to expand...
Click to collapse
I have a rooted sprint moto x that was running cm 12.1 and I used a toolkit to try and restore it to stock and ended up deleting the os and twrp recovery. I managed to flash the recovery back onto the phone using adb commands, however my PC doesn't recognize my moto as a USB storage device so I am unable to move the rom zip file to the phone. I tried flashing in fastboot and also adb push to push the file to the phone however nothing works..... If anyone could help me I'd greatly appreciate it
Shadowblade19 said:
I have a rooted sprint moto x that was running cm 12.1 and I used a toolkit to try and restore it to stock and ended up deleting the os and twrp recovery. I managed to flash the recovery back onto the phone using adb commands, however my PC doesn't recognize my moto as a USB storage device so I am unable to move the rom zip file to the phone. I tried flashing in fastboot and also adb push to push the file to the phone however nothing works..... If anyone could help me I'd greatly appreciate it
Click to expand...
Click to collapse
When you get into bootloader mode, are you using fastboot or mfastboot to flash system? If your system image is a single file instead of sparse chunks, you need to use mfastboot.
JulesJam said:
When you get into bootloader mode, are you using fastboot or mfastboot to flash system? If your system image is a single file instead of sparse chunks, you need to use mfastboot.
Click to expand...
Click to collapse
At first I used fastboot to flash the entire zip but it would say download size too large. Then I tried using mfastboot to flash the boot.img separately but that just gives me an error message.
Shadowblade19 said:
At first I used fastboot to flash the entire zip but it would say download size too large. Then I tried using mfastboot to flash the boot.img separately but that just gives me an error message.
Click to expand...
Click to collapse
what is the error message?
JulesJam said:
what is the error message?
Click to expand...
Click to collapse
I can't really check right now I'm at the beach... I'm using fastboot on a windows 8 tablet not a full fledged PC would that make any difference?
Shadowblade19 said:
I can't really check right now I'm at the beach... I'm using fastboot on a windows 8 tablet not a full fledged PC would that make any difference?
Click to expand...
Click to collapse
It is impossible for anyone to know what is wrong with your device if you can't tell us what the error message is. Post back when you know.
JulesJam said:
It is impossible for anyone to know what is wrong with your device if you can't tell us what the error message is. Post back when you know.
Click to expand...
Click to collapse
okay it keeps saying remote failure on the command prompt and it says "downgraded security version, update gpt_main version failed, preflash validation failed for gpt" on the bootloader
UPDATE": so after some time I was sorta able to get the mfastboot to work my moto x booted up normally and seemed to be running stock 4.2.2 however i get the message "the process com.android.phone has stopped" constantly to the point where the phone is unusable
Shadowblade19 said:
okay it keeps saying remote failure on the command prompt and it says "downgraded security version, update gpt_main version failed, preflash validation failed for gpt" on the bootloader
UPDATE": so after some time I was sorta able to get the mfastboot to work my moto x booted up normally and seemed to be running stock 4.2.2 however i get the message "the process com.android.phone has stopped" constantly to the point where the phone is unusable
Click to expand...
Click to collapse
UPDATE2- so after reflashing the files I stopped receiving the message and I am able to make and receive calls and texts. However, the phone will constantly power off after a minute of use... this seems to be the only problem so far.
Shadowblade19 said:
UPDATE2- so after reflashing the files I stopped receiving the message and I am able to make and receive calls and texts. However, the phone will constantly power off after a minute of use... this seems to be the only problem so far.
Click to expand...
Click to collapse
Aha I think I finally got it ! so i forgot to flash the stock recovery over my twrp so when i went to upgrade to 4.4.4 it would keep powering the phone off to install the update but load up twrp intead. A quick flash of the custom recovery and everything seems to be working fine. Thanks for all your help JulesJam I was seriously worried I bricked my phone beyond repair.
Tried several times to do the update through the settings menu.
Everytime it reboots the screen stays black.
I can turn it on, it vibrates for half a second. I see the Android one screen and the screen turns black. So i tried holding the volume up button and power button but no Dev menu.
So I thought it was bricked but after a few tries it rebooted and says it can't install the update.
I've attached the screenshot of the issue. I've tried it 3 times. It redownloaded the update and failed again.
Any ideas?
FIXED
@RomLover1999: gave the tip to reboot without a sim card, and that seemed to have fixed the problem!
seend said:
Tried several times to do the update through the settings menu.
Everytime it reboots the screen stays black.
I can turn it on, it vibrates for half a second. I see the Android one screen and the screen turns black. So i tried holding the volume up button and power button but no Dev menu.
So I thought it was bricked but after a few tries it rebooted and says it can't install the update.
I've attached the screenshot of the issue. I've tried it 3 times. It redownloaded the update and failed again.
Any ideas?
Click to expand...
Click to collapse
did you tried a factory reset before updating
galardo_2 said:
did you tried a factory reset before updating
Click to expand...
Click to collapse
Nope, but just tried it and it didnt work.
Try booting without sim card
Same and via fastboot method same. Any solution? We need help its a one mi a2 more????
Unfortunately the error is not informative. I had this error when installing November update. The only way I found to see what went wrong is to check logcat during upgrade, but I think it requires root. In the end I flashed the OTA using fastboot. Still didn't get this update. Try opening shell from adb and reading logcat. I don't think anyone can help you unless we know what is 5he reason for failure
RomLover1999 said:
Try booting without sim card
Click to expand...
Click to collapse
Oh my, that worked! :highfive:
Why would something like that even work?
seend said:
Oh my, that worked! :highfive:
Why would something like that even work?
Click to expand...
Click to collapse
The november update has a bug in it that it only boots in english with a simcard inserted , other languages make the screen bug out ( at least that's what I had ) and only boot without a simcard
Worked greatly
Hey folks, just reinforcing the answer: removing the sim card before restart did the trick, the update went smooth.
Thanks @RomLover1999 and @seend
January update failed
Help! My phone is Mi A2 lite. I can't install January update. My phone is rooted and unlocked.
Thank you!
The same problem....
The same problem....anyone help?
nedjog said:
The same problem....anyone help?
Click to expand...
Click to collapse
did you unlock ? ever run TWRP/Magisk or similiar?
luminoso said:
did you unlock ? ever run TWRP/Magisk or similiar?
Click to expand...
Click to collapse
Yes..it is unlock and never use TWRP/Magisk.. any sugestion please?
nedjog said:
Yes..it is unlock and never use TWRP/Magisk.. any sugestion please?
Click to expand...
Click to collapse
I don't know, by I have the exact same issue, I've unlocked to enable camera2api and left it unlocked.
I'll take a look this weekend
luminoso said:
I don't know, by I have the exact same issue, I've unlocked to enable camera2api and left it unlocked.
I'll take a look this weekend
Click to expand...
Click to collapse
Ok, my phone is not rooted.
I was having the same issue. In the past I've unlocked in order to enable camera2api.
December/2018 (V10.0.2.0.PDIMIFJ) to January/2019 (V10.0.3.0) was failing via OTA.
This is how I solved it:
Download V10.0.2.0.PDIMIFJ dump from this thread
Reboot phone to Fastboot mode (vol down+power)
Run flash_all_except_data.sh or if you're in windowsflash_all_except_data.bat
In my case my environment is:
Linux Fedora 29
fastboot version c7815d675 from android-tools package (just make sure you have the latest fastboot)
Using original USB-C cable
After flashing and reboot the OTA update installed normally without any issues
luminoso said:
I was having the same issue. In the past I've unlocked in order to enable camera2api.
December/2018 (V10.0.2.0.PDIMIFJ) to January/2019 (V10.0.3.0) was failing via OTA.
This is how I solved it:
Download V10.0.2.0.PDIMIFJ dump from this thread
Reboot phone to Fastboot mode (vol down+power)
Run flash_all_except_data.sh or if you're in windowsflash_all_except_data.bat
In my case my environment is:
Linux Fedora 29
fastboot version c7815d675 from android-tools package (just make sure you have the latest fastboot)
Using original USB-C cable
After flashing and reboot the OTA update installed normally without any issues
Click to expand...
Click to collapse
When i try this it return me an erro rcho missmatching image and device what does it mean?
Thanks
Mr.Krulez said:
When i try this it return me an erro rcho missmatching image and device what does it mean?
Thanks
Click to expand...
Click to collapse
I´m assuming you have xiaomi a2? it must match codename "jasmine"
luminoso said:
I´m assuming you have xiaomi a2? it must match codename "jasmine"
Click to expand...
Click to collapse
fastboot does say that my product is jasmine
Hello!
I just got this phone today and tried to update (8.0 November security update) and keep getting the same error!
I've tried with and without sim card, tried with and without my google acc, and tried with full battery!
Do not really want to unlock/install rom again... Any ideas?
Hi All,
I'm hoping someone will be able to help as I've spent most of the day chasing my tail it seems.
My 'stock' (non-rooted/non-flashed) Pixel 5 went into a boot loop randomly last night.
I've restarted, I've gone into the recovery mode and have tried to flash an OTA via ADB (which may not sound like much but is an achievement for someone with my limited technical skills), it's getting to 94% and then I'm receiving an error on the cmd prompt saying 'adb: failed to read command: No error' but on the phone itself it says that is was a 'success' status 0.
I've tried the current OTA and the developer version and I'm getting the above issue on both.
I tried copying the 'zip' to a USB stick and have plugged that in using the USB A to USB C dongle that comes with the pixel but I'm receiving an error stating that it cannot be initiated.
Can anyone suggest a possible next step? I have some files that I've realised don't go to my cloud backup and they are important to me so I'd like to if possible not have to wipe the device.
Many thanks.
Are you using the latest ADB from the android SDK?
You can always try the factory image and remove the -w from the flash-all.cmd file.
l7777 said:
Are you using the latest ADB from the android SDK?
You can always try the factory image and remove the -w from the flash-all.cmd file.
Click to expand...
Click to collapse
Hi, thanks for taking the time to respond. Everything was downloaded yesterday so is up to date. I re-downloaded just now and checked again and am still getting the same.
(~94%) adb: failed to read command: No error on cmd
Install from ADB completed with status 0 on the phone.
Is there a simple guide on how to flash-all (for someone as not technical as me) that you can point me towards?
Have you try to flash your new firmware on the web? Go to web https://developers.google.com/android/images. Click on Flash and follow instructions.
did you try a different cable or usb port? borrow your friend's pc perhaps?
l7777 said:
Are you using the latest ADB from the android SDK?
You can always try the factory image and remove the -w from the flash-all.cmd file.
Click to expand...
Click to collapse
Hi, thanks for this, I'll try another sideload with the April update and attempt it from another laptop, if that still doesn't work then I'll try the flash as you suggest.
swangjang said:
did you try a different cable or usb port? borrow your friend's pc perhaps?
Click to expand...
Click to collapse
I tried a different cable and port but not another laptop. I'll try that next after trying the April update.
Thanks.
tinhsoftware said:
Have you try to flash your new firmware on the web? Go to web https://developers.google.com/android/images. Click on Flash and follow instructions.
Click to expand...
Click to collapse
Hi, no not yet. I think this will be the last step before I factory reset. Will try another cable, laptop and the April OTA this evening when I have time.
Thanks.
WFHbot said:
Hi, no not yet. I think this will be the last step before I factory reset. Will try another cable, laptop and the April OTA this evening when I have time.
Thanks.
Click to expand...
Click to collapse
Also a note on trying to use the web flash utility. Make sure to look at the advanced options on the installation page, it gives you an option to flash the latest update without wiping your device at all.
That could help in getting the phone running again so you can recover your important files, before deciding to do a compete wipe, if that's what you have planned.
Just look around the settings carefully before flashing and everything should go well .
The same thing happened to me, it must have been the April update, I updated my phone, everything seemed to work and then all of the sudden I was watching a video last night and the phone rebooted itself and kept being stuck in boot, it won't load the os but it keeps restarting itself.
I tried accesing recovery mode but on the bootloader screen it won't let me use the volume keys to start the phone in recovery mode or to try and hard reset it, while on the bootloader screen it resets itself... :/ I'll give google a call
Chad_Petree said:
The same thing happened to me, it must have been the April update, I updated my phone, everything seemed to work and then all of the sudden I was watching a video last night and the phone rebooted itself and kept being stuck in boot, it won't load the os but it keeps restarting itself.
I tried accesing recovery mode but on the bootloader screen it won't let me use the volume keys to start the phone in recovery mode or to try and hard reset it, while on the bootloader screen it resets itself... :/ I'll give google a call
Click to expand...
Click to collapse
That sucks. Hopefully they'll be able to do something more than just a factory reset.
I've tried sideloading the April update and that also failed at 94%. Will try another laptop in a while and see if that works, then try the flash as suggested above, if not then it's a factory reset for me.
ProjectAlly said:
Also a note on trying to use the web flash utility. Make sure to look at the advanced options on the installation page, it gives you an option to flash the latest update without wiping your device at all.
That could help in getting the phone running again so you can recover your important files, before deciding to do a compete wipe, if that's what you have planned.
Just look around the settings carefully before flashing and everything should go well .
Click to expand...
Click to collapse
Thanks, will have a look around and see what I can work out. It's looking like I'll have to go this route...
DO I need to unlock the bootloader do do this flash?
tinhsoftware said:
Have you try to flash your new firmware on the web? Go to web https://developers.google.com/android/images. Click on Flash and follow instructions.
Click to expand...
Click to collapse
Thanks, will have a look and see if this works.
DO I need to unlock the bootloader do do this flash? If so, would this wipe the device?
WFHbot said:
Thanks, will have a look and see if this works.
DO I need to unlock the bootloader do do this flash? If so, would this wipe the device?
Click to expand...
Click to collapse
You do not need to bootloader unlock to use official firmware. You've been trying to do an OTA update, you can try the factory images above. Use the "link" to get a download, unzip, edit the flash-all.bat file, remove the -w from the fastboot flash update line.
Code:
fastboot -w update image-redfin-rq2a.210405.005.zip
Code:
fastboot update image-redfin-rq2a.210405.005.zip
l7777 said:
You do not need to bootloader unlock to use official firmware. You've been trying to do an OTA update, you can try the factory images above. Use the "link" to get a download, unzip, edit the flash-all.bat file, remove the -w from the fastboot flash update line.
Code:
fastboot -w update image-redfin-rq2a.210405.005.zip
Code:
fastboot update image-redfin-rq2a.210405.005.zip
Click to expand...
Click to collapse
Thanks, I tried that. Edited the file and tried running the flash-all.bat file but it's giving me an error:
Setting current slot to 'b' FAILED (remote: 'Fastboot command (set_active: ) is not allowed when locked')
fastboot: error: Command failed
Not sure what I'm doing wrong. Am I missing a step? Should the phone be on a certain menu when running the bat file?
l7777 said:
You do not need to bootloader unlock to use official firmware. You've been trying to do an OTA update, you can try the factory images above. Use the "link" to get a download, unzip, edit the flash-all.bat file, remove the -w from the fastboot flash update line.
Code:
fastboot -w update image-redfin-rq2a.210405.005.zip
Code:
fastboot update image-redfin-rq2a.210405.005.zip
Click to expand...
Click to collapse
Is that a fact? I haven't had a bl unlock for many years now but I thought I could only do an OTA flash from fastboot with a locked bootloader. I know I can factory reset but other than that .. So if I loaded the beta 12 I could go back and flash a factory image? I would certainly flip the OEM switch first just in case.
bobby janow said:
Is that a fact? I haven't had a bl unlock for many years now but I thought I could only do an OTA flash from fastboot with a locked bootloader. I know I can factory reset but other than that .. So if I loaded the beta 12 I could go back and flash a factory image? I would certainly flip the OEM switch first just in case.
Click to expand...
Click to collapse
That's a good question. I assumed it was possible otherwise why have a factory image available. The consensus seems to be mixed though.
OP: I just did an update from January to April and yes I also got the error at 94% from ADB but the phone reported status 0. Booted up no problem. Have you tried booting into safe mode? Is USB Debugging on? Can you get a logcat of the attempted boot?
l7777 said:
That's a good question. I assumed it was possible otherwise why have a factory image available. The consensus seems to be mixed though.
OP: I just did an update from January to April and yes I also got the error at 94% from ADB but the phone reported status 0. Booted up no problem. Have you tried booting into safe mode? Is USB Debugging on? Can you get a logcat of the attempted boot?
Click to expand...
Click to collapse
Hi,
I've tried booting into safe mode by keeping the volume down button pressed but no luck.
I'm pretty sure that the USB debugging is enabled, but not 100% certain.
How would I go about getting logcat of the attempted boot?
Thanks for all the help thus far.
WFHbot said:
Hi,
I've tried booting into safe mode by keeping the volume down button pressed but no luck.
I'm pretty sure that the USB debugging is enabled, but not 100% certain.
How would I go about getting logcat of the attempted boot?
Thanks for all the help thus far.
Click to expand...
Click to collapse
You'll have to factory reset in recovery. I had something similar happen yesterday morning. The reboot was done by me on the way to work though. A factory reset fixed it. Of course all user data was wiped, but Google backups did a good job of restoring almost everything I wanted restored (except for apps not on the G Play Store of course). You'll need to sign into everything again, but most things won't be lost including root.