Database Develop

[Q] Help getting HTC One Stock

Hello xda community, I'd like to start with saying all the work done on this forum for open-source, freeware, and general android tweaks is awesome! Thank you.
So awesome in fact that I got a little bit ahead of myself with my new "Sprint HTC One". I followed this guide http://forum.xda-developers.com/showthread.php?t=2244060 to Unlock the bootloader, and root my phone. I then went a step further and wanted to flash a custom Rom. I followed this video, but strayed a little bit (whoops!). I went into twrp recovery, and flashed the "Beanstalk" super custom 4.3 (9/24/2013), along with smw6180_superwipe, and 4.3 gapps.
This actually was working for about 4 days, but now it won't connect to the mobile network even when toggling on and off airplane mode (A temp fix for the ROM). I went ahead and looked for solutions, namely to just get back to stock to see if the problem is bigger than just custom ROM. I relocked my bootloader, following http://www.youtube.com/watch?v=0WWNZpaQBh8&list=PLE395F615E026133D&index=11 Thus running into my current issue of Error 140 when trying to flash the RUU.
I'm asking anyone that could help, to offer suggestions on getting my phone back to stock. I would also like a couple suggestions for more stable ROM's (again, i knew what i getting into; ie disclaimers) that offer cool customization!

did you put the stock recovery back on before you locked the bootloader? Also are you super cid?

olorolo said:
did you put the stock recovery back on before you locked the bootloader? Also are you super cid?
Click to expand...
Click to collapse
No i don't believe so, Well now its not even going into twrp recovery. It displays tampered relocked security warning, s-on, hboot 1.44.0000 and This is the only screen i have for fastboot and the bootloader

I've seen this issue before let me take a quick look I think your ok
Sent from my HTCONE using Tapatalk 4
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
You caught me in the middle of flashing the s-off firmware myself
Sent from my HTCONE using Tapatalk 4

Good to hear! Thank you for your time sir

get the newest twrp and rename it to recovery.zip put it in your cmd folder in bootloader type reboot bootloader fastboot flash flash recovery fastboot reboot
---------- Post added at 07:28 PM ---------- Previous post was at 07:18 PM ----------
once you have twrp back flash the s-off firmware http://forum.xda-developers.com/showthread.php?t=2467607 then the 4.3 rom of your choice

olorolo said:
get the newest twrp and rename it to recovery.zip put it in your cmd folder in bootloader type reboot bootloader fastboot flash flash recovery fastboot reboot
Click to expand...
Click to collapse
Either i don't understand fully or its failing. I have fastboot usb selected on my phone connected to usb on pc. I open my folder with cmd in it, and i typed what you said but error is "reboot" is not recognizable.
edit: I also have the trwp 2.6.3 image in the folder along with cmd.

Pug4567 said:
Either i don't understand fully or its failing. I have fastboot usb selected on my phone connected to usb on pc. I open my folder with cmd in it, and i typed what you said but error is "reboot" is not recognizable.
edit: I also have the trwp 2.6.3 image in the folder along with cmd.
Click to expand...
Click to collapse
twrp has to be renamed to recovery.zip try fastboot flash then type flash recovery then the name of the zip which is recovery.zip then fastboot reboot

I did that am getting error:cannot load recovery.
Also tried fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
that resulted in this
sending 'recovery' (8608 KB)...
OKAY [ 1.120s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.880s
Or should i try http://forum.xda-developers.com/showthread.php?t=2314582

Pug4567 said:
I did that am getting error:cannot load recovery.
Also tried fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
that resulted in this
sending 'recovery' (8608 KB)...
OKAY [ 1.120s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.880s
Or should i try http://forum.xda-developers.com/showthread.php?t=2314582
Click to expand...
Click to collapse
try hassoons all in one toolbox

I got twrp back by unlocking my phone again. Should i proceed with the 3.04.651.2 firmwre? beanstalk is now hanging on splash screen.

The phone isn't being recognized on my computer it seems, it shows as m7wls under device manager, when in twrp 2.6.3. When in bootloader it shows as One device, but neither is accessible.

Also tried flashing the s-off firmware, but got 'error cannot load firmware.zip'
Any more help would be appreciated, almost thinking of taking it back to sprint, i have a protection plan. But i would like to avoid that, im currently going to buy an otg-usb cable as well.

Locked bootloader while trying to unbrick failed rom flash

I'm having a really hard time getting this OP3t to do what I want.
Didn't flash su after trying to manually update to 4.0.2
Constantly tried to flash a new rom, would get stuck at patching system
Tried to use unbrick solution, flashed stock recovery
Upon completion of unbrick solution my bootloader is locked and i cannot get into recovery because md5 checksum fail when booting.
I've tried using the unbricking solution probably 10 times with no change.
I have searched among the threads which have not be helpful enough to solve my solution.
right now it says modem, boot and system failed md5 checksum and just constantly reboots.
Also, phone is not being recognized now in fastboot mode
What do I do???

First of all try to open phone in fastboot mode then connect your cable to pc.
1. Download full stock rom of oos try 4.0.1.
2. use command to lock the bootloader
fastboot oem lock;
3. then flash stock recovery of nouguat 7.0 through fastbootmode .
fastboot flash recovery image.filename.
4. then go to stock recovery and flash full rom zip using adb sideload.
All done and best of luck......
If facing any problem then ask

shubham8166410 said:
First of all try to open phone in fastboot mode then connect your cable to pc.
1. Download full stock rom of oos try 4.0.1.
2. use command to lock the bootloader
fastboot oem lock;
3. then flash stock recovery of nouguat 7.0 through fastbootmode .
fastboot flash recovery image.filename.
4. then go to stock recovery and flash full rom zip using adb sideload.
All done and best of luck......
If facing any problem then ask
Click to expand...
Click to collapse
I'm getting the wont load problem when trying to flash, advice?

Place all the zip file in same folder of adb driver than try to flash it
---------- Post added at 05:58 PM ---------- Previous post was at 05:58 PM ----------
Is your phone booting in fast mode or nkt

shubham8166410 said:
Place all the zip file in same folder of adb driver than try to flash it
---------- Post added at 05:58 PM ---------- Previous post was at 05:58 PM ----------
Is your phone booting in fast mode or nkt
Click to expand...
Click to collapse
NKT? Not sure what that means.
It is going to fastboot however if i list adb devices nothing shows up.
It does respond with bootloader already locked when i try to send that command

Type command fastboot devices
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
Then it will show device then only u can procceed further

shubham8166410 said:
Type command fastboot devices
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
Then it will show device then only u can procceed further
Click to expand...
Click to collapse
Nothing is coming up when I do that, it just returns to the original command prompt line

Can u able to flash phone in fastboot mode or not

shubham8166410 said:
Can u able to flash phone in fastboot mode or not
Click to expand...
Click to collapse
I was able to use the unbrick method from another computer. Thank you for your assitance

[X527] No wifi, no sim detection / Can't complete setup assistant [SOLVED]

Hello friends!
After i tried to find a way to bypass LeEco login on the install of stock based ROM , i have bricked my phone (not really bricked, but i will tell you). On the first boot i cant complete the setup, because X527 dont detect my sim cards and shows no wifi networks (So i cant go to developer options and can not use a dial code).
After i have read a lot, im sure it was a problem with the efs or nvram (The last working boot shows no serial and no bootloader). But now im on Stock ROM and Stock Recovery and need an option to repair efs/nvram over fastboot or stock recovery, without changing anything in the phone itself.
Hope you guys can help me...

i recommend you to install twrp and flash official stock rom it has stock recovery too so it will came back to original state. we have the original stock rom here so dont afraid to install twrp.

anjel05 said:
i recommend you to install twrp and flash official stock rom it has stock recovery too so it will came back to original state. we have the original stock rom here so dont afraid to install twrp.
Click to expand...
Click to collapse
I can't install TWRP because i have to go to the developer options, but my phone can not start....

quasimodo88 said:
I can't install TWRP because i have to go to the developer options, but my phone can not start....
Click to expand...
Click to collapse
What you need in developers option? Oem unlocking and usb debugging? I thnk in our device theyre already on default

anjel05 said:
What you need in developers option? Oem unlocking and usb debugging? I thnk in our device theyre already on default
Click to expand...
Click to collapse
Yes. If i want to install twrp in fastboot mode i get this error:
PS C:\adb> fastboot flash recovery twrp-3.1.1-1-s2.img
target reported max download size of 536870912 bytes
sending 'recovery' (17244 KB)...
OKAY [ 0.562s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.578s

quasimodo88 said:
Yes. If i want to install twrp in fastboot mode i get this error:
PS C:\adb> fastboot flash recovery twrp-3.1.1-1-s2.img
target reported max download size of 536870912 bytes
sending 'recovery' (17244 KB)...
OKAY [ 0.562s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.578s
Click to expand...
Click to collapse
You have to do
U need to unlock first dude

DarknessKiller said:
You have to do
U need to unlock first dude
Click to expand...
Click to collapse
Yes i know bro. But if i try to unlock i get this message:
PS C:\adb> fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s

quasimodo88 said:
Yes i know bro. But if i try to unlock i get this message:
PS C:\adb> fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
Did you install the drivers you need?

anjel05 said:
Did you install the drivers you need?
Click to expand...
Click to collapse
Yes i did. My phone is shown under fastboot devices.

quasimodo88 said:
Yes i know bro. But if i try to unlock i get this message:
PS C:\adb> fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
I think you are ****ed. Why oh why didn't you enable oem unlocking b4 flashing roms?
You can try
Fastboot erase modemst1
Fastboot erase modemst2
But it probably won't work cus your bootloader is locked
You can also try
Fastboot boot <insert name of your twrp img here>
But again doubt it'll work
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
Try googling for an alternative way to unlock your bootloader
---------- Post added at 08:40 PM ---------- Previous post was at 08:31 PM ----------
Also if you can find a way to transfer files to your phone, try downloading eui 19s rom, edit the update script as needed(especially if you are downgrading), then send it to your phone /sdcard as update.zip and try to flash it through stock recovery.

Dudeonyx said:
I think you are ****ed. Why oh why didn't you enable oem unlocking b4 flashing roms?
You can try
Fastboot erase modemst1
Fastboot erase modemst2
But it probably won't work cus your bootloader is locked
You can also try
Fastboot boot <insert name of your twrp img here>
But again doubt it'll work
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
Try googling for an alternative way to unlock your bootloader
---------- Post added at 08:40 PM ---------- Previous post was at 08:31 PM ----------
Also if you can find a way to transfer files to your phone, try downloading eui 19s rom, edit the update script as needed(especially if you are downgrading), then send it to your phone /sdcard as update.zip and try to flash it through stock recovery.
Click to expand...
Click to collapse
Fastboot erase... and fastboot boot... i have already tried.
Fastboot sideload... i have tried too, but im not sure if i do it right. I think my last chance is to try it over an otg cable, right?

quasimodo88 said:
Fastboot erase... and fastboot boot... i have already tried.
Fastboot sideload... i have tried too, but im not sure if i do it right. I think my last chance is to try it over an otg cable, right?
Click to expand...
Click to collapse
Any luck on googling a way to enable oem unlocking without access to developer options?
Or you can treat your phone as if it was bricked. Try downloading the sparse or Qfil file (not sure which is used for unbricking) for your model. And flashing through flashone or Qfil. Google or search xda for steps on how to unbrick this particular phone or Qualcomm phones in general. I believe it involves a step where you hold vol+, vol- & power key.
Anyway goodluck.

Dudeonyx said:
Any luck on googling a way to enable oem unlocking without access to developer options?
Or you can treat your phone as if it was bricked. Try downloading the sparse or Qfil file (not sure which is used for unbricking) for your model. And flashing through flashone or Qfil. Google or search xda for steps on how to unbrick this particular phone or Qualcomm phones in general. I believe it involves a step where you hold vol+, vol- & power key.
Anyway goodluck.
Click to expand...
Click to collapse
I dont find a way to unlock the bootloader. Flashing the qfil i have already tried, but it doesnt repair the issue. I think efs or nvram is broken.

quasimodo88 said:
I dont find a way to unlock the bootloader. Flashing the qfil i have already tried, but it doesnt repair the issue. I think efs or nvram is broken.
Click to expand...
Click to collapse
What version did you flash with Qfil? 19s usually doesn't ask for leeco login so try that. If you can bypass the leeco login I can walk you through the steps to repair your efs, I even have qcn files for x526 and x522 you can edit to fix it.
Don't know if these three options are possible, because I'm not sure what the qfil files contain but
1. with your current qfil if you can find a way to delete the letvaccount apk from the system image and reflash, that should bypass the login issues. Though dm verify might prevent the phone from booting past the splash screen, so you'll need to replace the kernel(boot) img with any custom one like illusion or overload
2. replace the system, data and kernel(boot) image with ones from miui 9 rom. This will flash miui instead and voila, no login issue
3. Replace Qfil recovery image with renamed twrp

Dudeonyx said:
What version did you flash with Qfil? 19s usually doesn't ask for leeco login so try that. If you can bypass the leeco login I can walk you through the steps to repair your efs, I even have qcn files for x526 and x522 you can edit to fix it.
Don't know if these three options are possible, because I'm not sure what the qfil files contain but
1. with your current qfil if you can find a way to delete the letvaccount apk from the system image and reflash, that should bypass the login issues. Though dm verify might prevent the phone from booting past the splash screen, so you'll need to replace the kernel(boot) img with any custom one like illusion or overload
2. replace the system, data and kernel(boot) image with ones from miui 9 rom. This will flash miui instead and voila, no login issue
3. Replace Qfil recovery image with renamed twrp
Click to expand...
Click to collapse
Thank's dude, that sounds good! I have to bypass the leeco setup, what i have to do? Can you give me an instruction, please? You can find the file on this site:
http://www.gsmhelpful.com/2017/08/how-to-flash-letv-le-2-x526-with-qfil-flash-tool.html

quasimodo88 said:
Thank's dude, that sounds good! I have to bypass the leeco setup, what i have to do? Can you give me an instruction, please? You can find the file on this site:
http://www.gsmhelpful.com/2017/08/how-to-flash-letv-le-2-x526-with-qfil-flash-tool.html
Click to expand...
Click to collapse
Have you flashed this? If so did it remove the leeco login or at least make it skipable?
Send a pic of the login screen
---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------
Also unzip the sparse file and send me pics of its contents. Because I can't download the file right now

Dudeonyx said:
Have you flashed this? If so did it remove the leeco login or at least make it skipable?
Send a pic of the login screen
---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------
Also unzip the sparse file and send me pics of its contents. Because I can't download the file right now
Click to expand...
Click to collapse
Yes, i have install it 2 times, but same issue. Can you give me an email address for the pictures, please?

quasimodo88 said:
Yes, i have install it 2 times, but same issue. Can you give me an email address for the pictures, please?
Click to expand...
Click to collapse
I've seen the pics, the system file is in parts so replacing it is very very difficult as I cant be sure how it was split.
But good news, I noticed a file named recovery
So move that file somewhere else.
Then rename your twrp file to recovery and copy it to that folder.
Then try flashing it, if successful this should give you custom recovery and I can work with that

Dudeonyx said:
I've seen the pics, the system file is in parts so replacing it is very very difficult as I cant be sure how it was split.
But good news, I noticed a file named recovery
So move that file somewhere else.
Then rename your twrp file to recovery and copy it to that folder.
Then try flashing it, if successful this should give you custom recovery and I can work with that
Click to expand...
Click to collapse
Ok, i will try it now. Don't run away :fingers-crossed:

quasimodo88 said:
Ok, i will try it now. Don't run away :fingers-crossed:
Click to expand...
Click to collapse
Good luck, also I noticed that your issue isn't leeco account login but rather Google's factory reset protection. So if this fails you can search for ways to bypass google factory reset protection.

I cant flash the recovery in my honor 4x

hello to all, accidentally delete the recovery of my smartphone and I have not been able to flash it using adb commands in Windows 10 therefore I can not restore the smartphone to the factory mode. please help

What error it gives when you type command 'fastboot flash recovery <recovery_file>'?
How did you deleted the recovery?
Also the end ("I can not restore the computer from the factory") doesn't make any sense.

keikari said:
What error it gives when you type command 'fastboot flash recovery <recovery_file>'?
How did you deleted the recovery?
Also the end ("I can not restore the computer from the factory") doesn't make any sense.
Click to expand...
Click to collapse
1. I think I deleted the recovery when I rooted the smartphone with kingroot.
2. the error that gives me is the following:
" S C:\adb> fastboot flash recovery recovery.img
target reported max download size of 524288000 bytes
sending 'recovery' (9304 KB)...
OKAY [ 0.222s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.234s ".

crhistiandavidbonilla47 said:
1. I think I deleted the recovery when I rooted the smartphone with kingroot.
2. the error that gives me is the following:
" S C:\adb> fastboot flash recovery recovery.img
target reported max download size of 524288000 bytes
sending 'recovery' (9304 KB)...
OKAY [ 0.222s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.234s ".
Click to expand...
Click to collapse
Can you still boot normally and do you have root access?
---------- Post added at 08:33 PM ---------- Previous post was at 08:29 PM ----------
Also try to re-unlock bootloader and if it doesn't work, re-lock and then unlock again. So we can be sure you don't have problems with that, because possible fix would otherwise make your phone worse.

keikari said:
Can you still boot normally and do you have root access?
---------- Post added at 08:33 PM ---------- Previous post was at 08:29 PM ----------
Also try to re-unlock bootloader and if it doesn't work, re-lock and then unlock again. So we can be sure you don't have problems with that, because possible fix would otherwise make your phone worse.
Click to expand...
Click to collapse
yes i can still boot normally, i erase kingroot so i think that i dont have root access

crhistiandavidbonilla47 said:
yes i can still boot normally, i erase kingroot so i think that i dont have root access
Click to expand...
Click to collapse
Well then your best choice is probably to try to re-install firmware and hope this does something. Do it with dload and force update method, because it doesn't use default recovery.
Or if you happen to have root access you can try this https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en or similiar app to flash recovery while device running. (Or 'dd' command)

keikari said:
Well then your best choice is probably to try to re-install firmware and hope this does something. Do it with dload and force update method, because it doesn't use default recovery.
Or if you happen to have root access you can try this https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en or similiar app to flash recovery while device running. (Or 'dd' command)
Click to expand...
Click to collapse
Nothing works

I had a similar problem: in fastboot I can install twrp successfully, but when I reboot, boot always to the stock emui recovery...
I don't know why.
I thought it was already installed twrp, I don't know why now boots to the stock one...
Does anyone can help me? Thanks.

Re-lock bootloader

Hi guys!
I try to relock my xt1925-1 but cmd says "(bootloader) Still require signed boot.img" and when i try to flash boot,img I get an error that say :
fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 0.712s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.977s
i dont know how proceed :c
please help me, my phone has pie update but I flash revenge OS but i prefer the stock system

Dagx19 said:
Hi guys!
I try to relock my xt1925-1 but cmd says "(bootloader) Still require signed boot.img" and when i try to flash boot,img I get an error that say :
fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 0.712s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.977s
i dont know how proceed :c
please help me, my phone has pie update but I flash revenge OS but i prefer the stock system
Click to expand...
Click to collapse
Boot phone in fastboot mode, type fastboot flashing lock or fastboot oem lock. Make sure in developer options you have switched the OEM unlock back to lock.

Baronstragen said:
Boot phone in fastboot mode, type fastboot flashing lock or fastboot oem lock. Make sure in developer options you have switched the OEM unlock back to lock.
Click to expand...
Click to collapse
I can't switch the option because it's say "bootloader is already unlocked" and I can't change this

Dagx19 said:
I can't switch the option because it's say "bootloader is already unlocked" and I can't change this
Click to expand...
Click to collapse
You don't need to deactivate the OEM unlocking option. There is no reason to do it.
---------- Post added at 09:19 PM ---------- Previous post was at 08:55 PM ----------
Lock bootloader
You can't relock the bootloader without the stock firmware!!
1.) Download and flash the latest version of your stock rom:
https://mirrors.lolinet.com/firmware/moto/ali/official/
2.) Let your phone boot until the "Welcome" screen appears and boot into fastboot mode.
3.) Run "fastboot oem lock"
=> re-run the command to continue
4.) "Flash valid Android images now. Then re-run this command to lock" => run "fastboot oem lock"
You already flashed the images in step 1.)
5.) Now the bootloader asks for a signed boot.img. Flash the boot.img again and run "fastboot oem lock"
6.) Now the bootloader asks for a signed system.img and/or oem.img
Flash again system, oem and vendor.img (At this step I flashed also the vendor.img when I relocked my phone)
7.) Run a last time "fastboot oem lock" and your bootloader is relocked with status "oem locked".

WoKoschekk said:
You don't need to deactivate the OEM unlocking option. There is no reason to do it.
---------- Post added at 09:19 PM ---------- Previous post was at 08:55 PM ----------
Lock bootloader
You can't relock the bootloader without the stock firmware!!
1.) Download and flash the latest version of your stock rom:
https://mirrors.lolinet.com/firmware/moto/ali/official/
2.) Let your phone boot until the "Welcome" screen appears and boot into fastboot mode.
3.) Run "fastboot oem lock"
=> re-run the command to continue
4.) "Flash valid Android images now. Then re-run this command to lock" => run "fastboot oem lock"
You already flashed the images in step 1.)
5.) Now the bootloader asks for a signed boot.img. Flash the boot.img again and run "fastboot oem lock"
6.) Now the bootloader asks for a signed system.img and/or oem.img
Flash again system, oem and vendor.img (At this step I flashed also the vendor.img when I relocked my phone)
7.) Run a last time "fastboot oem lock" and your bootloader is relocked with status "oem locked".
Click to expand...
Click to collapse
Thank you! In my case i just needed to flash boot.img once and it rebooted without a warning! Again, THANK YOU