Im making this post because all of the posts ive searched for EVO3d stock radio have urls that are invalid, below are two examples.
Can someone please post the stock sprint evo3d raido link so i can flash my phone (and so others can have the link)
If someone sends me the file i can host it on my servers and post a link, i just need the file. This should be a 8 or so MB file correct?
http://forum.xda-developers.com/showthread.php?t=1193540
or
http://forum.xda-developers.com/showthread.php?t=1194053
4g:
http://forum.xda-developers.com/showthread.php?t=699032
You missed a thread. That has valid links.
http://forum.xda-developers.com/showthread.php?t=1193101
P.S. wrong section.
nice, thanks very much. i have flashed my radio to stock, however im still having an issue with this one step:
7. Once the phone has been flashed you will need to set the secure flag on the radio for S-ON to do this use "fastboot oem writesecureflag 3" Make sure you are in fastboot menu. To do this power down and hold power down while powering up and select fastboot. I have attached the fast boot and adb files to the post.
Im in the fastboot menu and i have 4 options: Bootloader, Reboot, Reboot Bootloader and Power Down.
Do just stay at this screen, hook up the USB to my computer (same one i used to root the phone so all the HTC drivers and adb ect are installed).
and then run from CMD, adb.exe fastboot oem writesecureflag 3
?
im not clear on how i use ADB to input that command so i can bring the phone to the sprint store to be activated.
tks alot
EDIT: im appologize for the wrong section, i thought it would be in this section so others could see how to return to stock with a good download link. I will be more careful in the future.
I have no reason to turn S-ON but I would guess you would be issuing the fastboot command from the command line on your PC, not the phone (obviously).
You won't need S-ON to have your phone activated. You should be able to do that online or over the phone and not have to go to the store.
Tks, very long story, but i have to bring it in to the sprint store to get activated, so i have to have it back to S-on so they dont see i rooted it.
what mode do i have the phone on/at to then issue the command from CMD on windows?
should it be booted with just usb debugging turned on? or should i have it at the fast boot menu (start up phone with Power and Volume down then choose fast boot).
thanks again.
ok i think i bricked my phone..
i did this: and now the phone will not power on or anything:
C:\adb>fastboot oem writesecureflag 3
...
OKAY [ 0.045s]
finished. total time: 0.048s
C:\adb>
jo2jo said:
ok i think i bricked my phone..
i did this: and now the phone will not power on or anything:
C:\adb>fastboot oem writesecureflag 3
...
OKAY [ 0.045s]
finished. total time: 0.048s
C:\adb>
Click to expand...
Click to collapse
There are a couple "Return to Stock" threads in this section.
Sounds like you set that secure flag without being on an official bootloader?
I was wondering what you meant by "stock radio" as all the radios are from official releases.
You should have been looking for the stock RUU, not radio.
With your phone connected:
Code:
adb devices
or
fastboot devices
and see if you devices number pops up.
Download this, connect your phone, and see if you can run it:
http://www.multiupload.com/WQ82JTN7JL
If you can boot into the bootloader at all, follow this:http://forum.xda-developers.com/showthread.php?t=1194053
***If you can't get either to work, tell the Sprint reps that you got an OTA notification on your phone, you agreed to the install, and that's how your phone ended up in its current state. Take the SDcard out so they don't see any Roms/kernels/rooted app folders, etc.
See if i can run it? it being the link you provided:
http://www.multiupload.com/WQ82JTN7JL
that is a link to a 300mb ROM file? how do i run that? (maybe you gave wrong link)
I cant turn on the phone or do anything, its black screen.
i just dont see how i bricked this, i tried everything, had 2 threads going, ppl walkingi me through it and it still gets bricked.
Can someone please show me a thread where it shows how to return to stock and unroot so you can simply return your phone to sprint? I used the two main ones (which neither is very clear or gives good steps) and i ended up having to ask questions and open threads and with a bricked evo3d.
I ask this bc i know if i would have posted a thread, How do i unroot and return my phone to stock, ppl would have been bashing and saying use search and so forth. maybe im missing a link?
thanks
Related
So I am no noob and have unlocked and rooted 50+ androids in my day. I have personally done 12 Atrixs in the last 12 months. Today I got my hands on a free Atrix and decided I'd go ahead and do the norm.
I used the http://forum.xda-developers.com/showthread.php?t=1182871 method which I always do and proceeded as normal.
I ran the script like always and got the failed to boot 0x1000 error like always. Got the phone to run fastboot and ran the fix but on cmd for the first time ever I got the <waiting for device> message that never seemed to stop "waiting." I have never ran into this before and did everything as I normally do... I'm guessing I hard bricked it but have no idea how that could be.
Since I can get the phone into fastboot is there a way to recover the device and retry the method? If not no biggie as it was free and I could really care less as I have my Atrix, a S II and a Skyrocket lying around that I use regularly but would love to get this bad boy up and running. Please let me know ASAP if there is a fix...
Soo when you type cmd and choose your option
if it says "waiting for device " reboot it into "Fastboot mode
make sure u press volume Up
so then phone should read" Starting fastboot protocal" and type Fastboot devices your output should read
List of devices connected
then your device id like TA084327
something like that then type
fastboot oem unlock
ltdanno360 said:
Soo when you type cmd into pc go to your fastboot folder then type fastboot oem unlock
if it says "waiting for device " unplug phone reboot it into "Fastboot mode
make sure u press volume Up
so the phone will read Starting fastboot protocal Then plug into Pc
Click to expand...
Click to collapse
No no no... I run the script from http://forum.xda-developers.com/showthread.php?t=1182871 and I get to the point where it says "Starting fastboot protocal" and then the script tells me to plug in phone. I do and then I hit enter on script and it then says <waiting for device> ...... therein lies the problem.
*Solved
So I was on my way to unlocking my boot loader and rooting the phone when i ran into this issue. (i am on AT&T)
The phone is stuck on a Red Exclamation Point and then it reboots to a white HTC screen every minute or two.
Where I was at in the process my bootloader was "unlocked", "tampered" displayed. I had even backed up with TWRP. The thing was I couldnt get the USB Debugging turned on. I turned it on before I started the process and was having trouble finishing with superuser and rooting the device. I had been trying forever to setup the S-OFF Feature to NO AVAIL.
Once I unlocked on HTCdev and then setup TWRP I just could never get the phone back to normal.
Once again this is the INT'L Version of the HTC ONE MAX and I just don't know where to turn next.
Please help. I am without phone and just purchased yesterday.
TIA - Mark
Well what you need is an ruu (rom utility updater) which is an updater program officially from htc. but I can't seem to find it for you, perhaps because it's not even made yet..
I'm affraid it's gonna have to go back to the store, are you able to acces to bootloader? if not, then don't worry about it being unlocked, they'll never notice. They're going to reset it for you or give you a replacement.
shaggydiamond said:
Well what you need is an ruu (rom utility updater) which is an updater program officially from htc. but I can't seem to find it for you, perhaps because it's not even made yet..
I'm affraid it's gonna have to go back to the store, are you able to acces to bootloader? if not, then don't worry about it being unlocked, they'll never notice. They're going to reset it for you or give you a replacement.
Click to expand...
Click to collapse
heres my question how do i know what RUU to search for? how do i figure out which version i need based on my phone?
Thanks in advance.
Mark
Well you say you have the international version? but you got it from at&t so it's carrier branded right?
but first things first, you have to be able to access the bootloader to start the ruu. So can you access it?
when in fastboot: find out the CID by this command: fastboot getvar cid
If it answers with : None. Don't worry, try this command: fastboot oem readcid
Then it will tell you the CID. this code is needed when receiving updates from your carrier.
You will need to find the ruu for your CID, any other ruu won't work.
If you find an international ruu for your phone, you can use that one, but you have to have SuperCID.
You can get superCID after you s-off..
If you have SuperCID you can flash any ruu for your device, be careful though, I bricked my htc one s with a wrong ruu.
Goodluck!
the phone is not sold by ATT but is GSM
i cannot access boot loader.
I cant get past the RED EXCLAMATION (so am I bricked?)
this is the phone...
http://www.amazon.com/HTC-One-Max-F...92559809&sr=8-3&keywords=htc+one+max+unlocked
when in fastboot: find out the CID by this command: fastboot getvar cid
If it answers with : None. Don't worry, try this command: fastboot oem readcid
also i did find the TRWP backup if that matters or helps....
i tried both commands and it says fastboot is notrecognized as an internal or external command
operable program or batch file.
Well if you cannot access the bootloader, then you can't use fastboot commands..
Can you tell me what button pressing combinations you have used to enter bootloader?
Can you try to power the phone off completely and then just hold volume down?
The twrp backup can come in handy when your phone gets a working recovery, don't delete that
when i hold down the vol down...it just stays on RED EXCLAMATION....and when I try and enter bootloader mode with vol it just gives me the reset to the White HTC screen and back to the RED EXCL
i have not been able to power down completely
dankduke said:
when i hold down the vol down...it just stays on RED EXCLAMATION....and when I try and enter bootloader mode with vol it just gives me the reset to the White HTC screen and back to the RED EXCL
Click to expand...
Click to collapse
I'm pretty clueless here, If i were you i would keep trying to get in the bootloader. I have had a similar soft brick on my htc one and after half an hour of pressing every key combination it ended up in the bootloader. If that doesn't work I would let it get replaced on warranty
Okay so now I need some HELP.
I took out the SD Card and the SIM Card and the Bootloader screen comes up.
My choices are FASTBOOT, RECOVERY FACTORY RESET, SIM LOCK etc.
What do I do. I feel like I got one chance at this!
And here is my boot loader
my last question....how do i enable the USB Debugging. It shows as being OFF.
Can i do through boot loader or through the CMD Prompt..?
dankduke said:
my last question....how do i enable the USB Debugging. It shows as being OFF.
Can i do through boot loader or through the CMD Prompt..?
Click to expand...
Click to collapse
okey here's what you do, you don't have to have usb debugging enabled. that's only for adb purposes. You need to try and access the twrp recovery from the bootloader. If it doesn't work. try and look for the boot.img file of a twrp recovery for your device and flash that through fastboot
I ported TWRP using Android kitchen to flash to my device (Coolpad 801es) since there isn't an official version. For some reason, I can't seem to get fastboot to play nice with my phone (see my earlier post) so I used flashify. On reboot i'm stuck in a bootloop. I did have the foresight to back up my stock recovery with flashify and transfer it to my PC first, in case something went wrong. Now, I can't boot into recovery at all and ADB isn't working since the phone isn't being recognized by my PC when I plug it in. I just want to flash the stock recovery back and fix this. I can get into fastboot, and the PC does recognize the phone in fastboot, but when I try any commands it just hangs at waiting for device. I've googled but every solution i've seen for fixing a bootloop tells you to boot into recovery to do so.
Can someone please help me out?
UPDATE:
Upon further research, I discovered the reason fastboot commands weren't working is because my phone apparently isn't whitelisted in the fastboot exe. However, if I type Fastboot followed by -i 0x1ebf the commands seem to work. Using this method, fastboot devices lists my phone and fastboot reboot reboots the phone.
I think i'm on the right track, but when I try "Fastboot -i 0x1ebf flash recovery (path to recovery.img)" the terminal shows "sending 'recovery' (10240kb)..." and nothing else. No progress indicator, and i've waited 10 minutes for it to complete which should be more than enough time to flash a 10 meg file, but there's no change it just sits there. Like I said, I think i'm on the right track but I could REALLY use some help. I can't be the first person on here with this problem. Can someone, anyone, PLEASE help me.
So, more Googling would indicate that either i'm not using the correct USB port, or that my bootloader is locked. I have tried all the USB ports on my PC (front and back) as well as two different cables, no joy. As far as the bootloader being locked, the phone is rooted which I thought meant that the bootloader is unlocked as that is part of the rooting process. I try "Fastboot oem unlock" to check but I just get "failed remote no such command unlock" and there is no OEM option under developer options on this phone. I'm trying to piece this together but I could really use some help.
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead.
I can get a black screen with the blue led by running adb reboot bootloader and the phone is recognised from fastboot devices but when I try to unlock the bootloader I get an error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed)
finished. total time: 0.042s
Any help appreciated.
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead or by running adb reboot fastboot
If feels like I haven't go the fastboot USB drivers but I can't see how or where I can add them.
Any help appreciated.
Click to expand...
Click to collapse
Disable driver signature enforcement then reinstall sony drivers
tapiwasam said:
Disable driver signature enforcement then reinstall sony drivers
Click to expand...
Click to collapse
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
adb reboot bootloader just goes into bootloader mode and not fastboot mode which is needed to unlock it. Go directly into fastboot by typing adb reboot fastboot
Then when your phone led is flashing blue, run your fastboot "oem unlock" command.
Saw now that you already tried that sorry about that.
Tried running cmd with admin privileges to see if that shows any difference?
Also from sony:
Please note! It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
.... snip....
Click to expand...
Click to collapse
You don't need to unlock your bootloader to simply downgrade to official MM! Just use flashtool to flash the appropriate MM ftf. There are plenty guides available on XDA and elsewhere.
I'm lost in your explanation.
You wanted to unlock your bootloader to be able to downgrade your phone? That's right? And it's fine to me, but you don't need to do that if you don't feel like. Unlocking your bootloader is nog necessary to downgrade to MM via flashtool.
So you tried to unlock your bootloader. But what you write what happened afterwards is completely unclear to me, because it contradicts itself.
-->> "Also I can see the phone with both adb devices and fastboot devices"
Fine. This means your connected with your phone and fastbook recognizes your phone. So bootloader is unlocked and software to control that works fine.
-->> "However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led."
Fine, so you unlocked your bootloader, and rebooted in fastboot.
-->> Obviously. It's an unlocked bootloader, you can double unlock it or something like that. You can relock it if you want (which doesn't make any difference for what you want to do) but that's a different method.
Is there any reason that you absolutely need to a second method to enter fastboot mode? Or any fastboot mode? It could be possible with another kernel, but I don't see the point to flash another kernel. I would just leave it like it is.
PhilG57 said:
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
Click to expand...
Click to collapse
that is notmal behaviour, that is fastboot mode, indicated by that blue LED
Thanks for the clarification that I don't need to unlock the bootloader to downgrade using flashtool. What I didn't say was that I couldn't reinstall Nougat using the Sony tool software restore option or get anywhere with flashtool because the phone won't go into the blue led mode by inserting the USB and holding the up vol button. I did try running flashtool in one window and the command line tools in another with the idea of running flashtool first and then unplugging the phone and replugging it to use command line to get the blue LED state, but that doesn't work because the command line tools can't see the phone once flashtool is running and has addressed the phone.
From what i read, i assume you are on nougat and want to go back to MM, right?
So you would need flashmode instead of fastboot mode.
You get there with holding Vol down button and plugging in USB cable on turned off phone.
Flashmode also shows a green notification light instead of the blue one.
If you having Problems to get there, please check following:
make sure to have latest version of flashtool installed http://www.flashtool.net/downloads.php
install drivers from your flashtool\drivers folder
don't use an USB 3.0 port or cable(have heard of some people having trouble with)
PhilG57 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed) <- this
finished. total time: 0.042s
Any help appreciated.
Click to expand...
Click to collapse
OP, I had the exact same problem as you. At the time I tried absolutely everything but never found the culprit. So after several months I actually succeeded today
This is the guide I followed - https://forum.xda-developers.com/z5-compact/general/guide-how-to-root-z5c-painful-using-t3549388 and it worked perfectly.
A few pointers:
- Go to the service menu (*#*#SERVICE#*#*) before you begin, before you turn OEM Unlocking ON from Dev Options .
- Take note of what it says in Configuration and Firmware.
- Now enable OEM Unlocking and take note again, it should say stuff like Model Number: Unknown and other unknown stuff.
- Reboot - IMPORTANT.
- Use the guide I gave you and you will be fine, it took me ages to find a solution but now I'm on MM and rooted
Hope I helped :fingers-crossed::fingers-crossed::fingers-crossed:
I have a Moto G Play 2021 (XT2093-4) (another one), that I made a mistake to relock the bootloader after I had it unlocked. I don't have access to the OS on the phone anymore. Previously I had the treble floss installed on it. I don't have TWRP installed. The only thing I have access to is fastboot. I realise I might have completely bricked this phone but I thought I ask here to see if there is any way to unlock the OEM again just using the fastboot.
the fastboot screen on the phone has a menu option to go into recovery mode. stock recovery might be able to restore your phone to working condition.
volume-down + power buttons > fastboot mode > volume button to 'recovery' option > power button to execute. if your recovery screen is broken with the 'no command' message, hold down the power button and quickly press and release the volume-up button. that should get you to the working recovery screen where you can try to factory reset your phone.
strumcat said:
the fastboot screen on the phone has a menu option to go into recovery mode. stock recovery might be able to restore your phone to working condition.
volume-down + power buttons > fastboot mode > volume button to 'recovery' option > power button to execute. if your recovery screen is broken with the 'no command' message, hold down the power button and quickly press and release the volume-up button. that should get you to the working recovery screen where you can try to factory reset your phone.
Click to expand...
Click to collapse
Thanks, but I think my phone is completely messed up now. If you can believe it, I can't even get to recovery mode. I can get to fastboot and then find the recovery mode and click to go to it but then it just starts the fastboot again. I'm basically stuck in fastboot forever. It's just weird cause there's nothing wrong with the hardware. Thanks again.
if you have nothing working on your phone but fastboot mode, that might still be enough to rescue your phone. boot it to the fastboot screen, connect it to a pc that has the fastboot program installed, open a terminal window on the pc wherever fastboot is, and type 'fastboot devices'. if your phone answers with its serial number, you'rr probably able to flash a whole stock rom to it piece by piece. get a stock rom from somewhere like lenovo, using their lmsa program, or just download the right one from lolinet or somewhere. unzip it. then, for instance, to flash the boot.img to your phone you would type 'fastboot flash boot boot.img'. that would replace your possibly broken boot partition with a known good one. then 'fastboot reboot' to see if that helped. there are tutorials on the net for flashing the rest of the rom. be sure to read one, because all of the flash commands aren't that straightforward.
strumcat said:
if you have nothing working on your phone but fastboot mode, that might still be enough to rescue your phone. boot it to the fastboot screen, connect it to a pc that has the fastboot program installed, open a terminal window on the pc wherever fastboot is, and type 'fastboot devices'. if your phone answers with its serial number, you'rr probably able to flash a whole stock rom to it piece by piece. get a stock rom from somewhere like lenovo, using their lmsa program, or just download the right one from lolinet or somewhere. unzip it. then, for instance, to flash the boot.img to your phone you would type 'fastboot flash boot boot.img'. that would replace your possibly broken boot partition with a known good one. then 'fastboot reboot' to see if that helped. there are tutorials on the net for flashing the rest of the rom. be sure to read one, because all of the flash commands aren't that straightforward.
Click to expand...
Click to collapse
Sorry for the really late reply. I tried what you said, but it fails right at the (fastboot flash partition gpt.bin) command and the output I get is:
Sending 'partition' (37 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) flash permission denied
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
It keeps saying flash permission denied. I have another exact same phone with an unlocked bootloader and I did the same on that one and I was able to flash a stock ROM to it. I've tried every RETCA and RETUS on this site: https://mirrors.lolinet.com/firmware/motorola/guamna/official/ but it fails with the same error. I'm going to try all the rest later but it's a lot to download for now.
Thanks again for the help!