Database Develop

[Q] Help unbricking

Hi,
I have a Sprint htc one that I had previously unlocked, rooted and installed twrp and cm10.1 on. I was trying to restore the factory rom and now I can't boot up. seams like i have deleted all OS'. I can open the bootloader and twrp. I can not find any zip in twrp to reinstall cm10 just to get the phone working again. I have tried the adb function in twrp but it keeps failing. i have also tried to install the RUU file but can not get it to work. it states that my device has 1.31.651.2 and the RUU I'm trying to use is 1.29.651.7. Is there somewhere I can download the 1.31.651.2 image version. Or is there another way to unbrick my phone.

help
Now I cannot get into TWRP.

Can you get into bootloader?
wondernad said:
Now I cannot get into TWRP.
Click to expand...
Click to collapse
1) Get into bootloader (Power and volume down)
2) go to fastboot
3) Copy the recovery you want to the directory you use for abd and rename it recovery.zip
4) fastboot flash recovery recovery.zip
5) Run fastboot erase cache
6) Then open recovery
7) Go to sideload and sideload a ROM you want. Make sure that is for SPRINT HTC ONE
8) Reboot and good luck

imurg said:
1) Get into bootloader (Power and volume down)
2) go to fastboot
3) Copy the recovery you want to the directory you use for abd and rename it recovery.zip
4) fastboot flash recovery recovery.zip
5) Run fastboot erase cache
6) Then open recovery
7) Go to sideload and sideload a ROM you want. Make sure that is for SPRINT HTC ONE
8) Reboot and good luck
Click to expand...
Click to collapse
Ok so im in fastboot. Is the recovery the 1.31.651.2ruu? or should it be twrp or the like?

wondernad said:
Ok so im in fastboot. Is the recovery the 1.31.651.2ruu? or should it be twrp or the like?
Click to expand...
Click to collapse
Get your recovery here
http://www.teamw.in/project/twrp2/171
After that you should be able to get to sideload in advanced

sideload
how long should the sideload take?

wondernad said:
how long should the sideload take?
Click to expand...
Click to collapse
It takes a while depending on how big the ROM is. Buy you can see the advance in the % dont worry it'll get there
Patience... is it grasshopper?

imurg said:
It takes a while depending on how big the ROM is. Buy you can see the advance in the % dont worry it'll get there
Patience... is it grasshopper?
Click to expand...
Click to collapse
It doesn't give me a %. I'm wondering if its recognizing my device. I do cmd adb devices and it doesn't show the phone. but the phone says it is waiting for package. I've tried it on my desktop(xp but runs ok) and my laptop(windows 7, but slow).

wondernad said:
It doesn't give me a %. I'm wondering if its recognizing my device. I do cmd adb devices and it doesn't show the phone. but the phone says it is waiting for package. I've tried it on my desktop(xp but runs ok) and my laptop(windows 7, but slow).
Click to expand...
Click to collapse
It doesn't seem to recognize the phone. Do you have the latest HTC SYNC Manager? it has the drivers

imurg said:
It doesn't seem to recognize the phone. Do you have the latest HTC SYNC Manager? it has the drivers
Click to expand...
Click to collapse
Yes I did reinstall the drivers. trying to update my android sdk right now.

wondernad said:
Yes I did reinstall the drivers. trying to update my android sdk right now.
Click to expand...
Click to collapse
Just run "adb version" latest is 1.0.31

imurg said:
Just run "adb version" latest is 1.0.31
Click to expand...
Click to collapse
That seams to open a command window for about a millisecond.

wondernad said:
That seams to open a command window for about a millisecond.
Click to expand...
Click to collapse
You need to open a command window. Double click command prompt (The black icon with the c:\_)

imurg said:
You need to open a command window. Double click command prompt (The black icon with the c:\_)
Click to expand...
Click to collapse
ok it is the latest version

wondernad said:
ok it is the latest version
Click to expand...
Click to collapse
Now do not close the command window and try adb devices
If you see your device then try the sideload again without closing the command window until you are finished.

imurg said:
Now do not close the command window and try adb devices
If you see your device then try the sideload again without closing the command window until you are finished.
Click to expand...
Click to collapse
It still does not see the device. says list of devices attatched and has a blank space. then the command prompt comes back up

wondernad said:
It still does not see the device. says list of devices attatched and has a blank space. then the command prompt comes back up
Click to expand...
Click to collapse
Still not seeing the device. I've tried switching versions of twrp and twrp sideload keeps saying failure. so I put CWM on it and it is opening sideload but the device is not recognized by the computer.

wondernad said:
It still does not see the device. says list of devices attatched and has a blank space. then the command prompt comes back up
Click to expand...
Click to collapse
I think the safest at this point where FASTBOOT recognizes your devices but ADB doesn't is to go back to stock flashing a RUU this only requires FASTBOOT.
This thread will show you how
http://forum.xda-developers.com/showthread.php?t=2251800
Best of lucks

imurg said:
I think the safest at this point where FASTBOOT recognizes your devices but ADB doesn't is to go back to stock flashing a RUU this only requires FASTBOOT.
This thread will show you how
http://forum.xda-developers.com/showthread.php?t=2251800
Best of lucks
Click to expand...
Click to collapse
That isn't working either. the only RUU file I can find is for 1.29.651.10RUU instead of the 1.31.651.2RUU. I have tried running it anyway hoping to limp it back to life but it won't take it. I really need the 1.31.651.2RUU. but can't find it.

http://forum.xda-developers.com/showthread.php?t=2391161&page=4
chack this

[Q] I made my HTC ONE a brick :(

Hi, i did not find a solution anywhere so i trust on you guys I have HTC ONE, and it is rooted and i also have TWRP v2.6.3.0. Then i was trying to update to Android 4.3 and Sense 5.5...it did not work...so i tried to unroot it...then i messed up the phone no i can only go to recovery mode, or twrp...that´s it...how i can make it functional again ? I just wanted it back to original, no need to root anymore...

sandelin85 said:
Hi, i did not find a solution anywhere so i trust on you guys I have HTC ONE, and it is rooted and i also have TWRP v2.6.3.0. Then i was trying to update to Android 4.3 and Sense 5.5...it did not work...so i tried to unroot it...then i messed up the phone no i can only go to recovery mode, or twrp...that´s it...how i can make it functional again ?
Click to expand...
Click to collapse
Use USB-OTG and flash a ROM using that.

If u can get to the bootloader try flashing a new recovery. fastboot flash recovery recovery.img
Sent from my HTC One using Tapatalk

sandelin85 said:
Hi, i did not find a solution anywhere so i trust on you guys I have HTC ONE, and it is rooted and i also have TWRP v2.6.3.0. Then i was trying to update to Android 4.3 and Sense 5.5...it did not work...so i tried to unroot it...then i messed up the phone no i can only go to recovery mode, or twrp...that´s it...how i can make it functional again ? I just wanted it back to original, no need to root anymore...
Click to expand...
Click to collapse
Or else sideload a rom.zip

Sorry, i am kinf of a newbie with those kind of stuff But when i go to fastboot/bootloader, my computer does not work with it, i have tried many different drivers...so i can´t put any files in it anymore...

So you can get into recovery? Have you tried wiping it yet?
Sent from my HTC One using Tapatalk

sandelin85 said:
Sorry, i am kinf of a newbie with those kind of stuff But when i go to fastboot/bootloader, my computer does not work with it, i have tried many different drivers...so i can´t put any files in it anymore...
Click to expand...
Click to collapse
Use windows 7/8 with the latest HTC drivers, it doesn't work with 8.1.

instigator008 said:
So you can get into recovery? Have you tried wiping it yet?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
yes, i can go to twrp v2.6.3.0...then i try to install: OTA_M7_UL_JB43_SENSE55_MR_HTC_Europe_3.62.401...then it says: no md5 file found, no file_contexts --> failed...so i think that i have delete the whole OS...it says also: No OS installed...ups :/

Have you tried wiping through twrp?
Sent from my HTC One using Tapatalk

sandelin85 said:
yes, i can go to twrp v2.6.3.0...then i try to install: OTA_M7_UL_JB43_SENSE55_MR_HTC_Europe_3.62.401...then it says: no md5 file found, no file_contexts --> failed...so i think that i have delete the whole OS...it says also: No OS installed...ups :/
Click to expand...
Click to collapse
Looks like your system partition is empty, so you'll have to install a whole rom ,an OTA won't help an empty system

n1234d said:
Looks like your system partition is empty, so you'll have to install a whole rom ,an OTA won't help an empty system
Click to expand...
Click to collapse
Okey, could you please tell me (like for a child), how to do that ?

sandelin85 said:
Okey, could you please tell me (like for a child), how to do that ?
Click to expand...
Click to collapse
Okay, do you have any rom(eg. ARHD).zip on your phone? If you do, flash that via twrp, and you're done
If you don't, copy a rom to a USB flash drive and connect it to your phone with an OTG Cable, and flash it via twrp
If you don't have an OTG cable, try this to sideload a rom to your internal sd card http://teamw.in/ADBSideload

n1234d said:
Okay, do you have any rom(eg. ARHD).zip on your phone? If you do, flash that via twrp, and you're done
If you don't, copy a rom to a USB flash drive and connect it to your phone with an OTG Cable, and flash it via twrp
If you don't have an OTG cable, try this to sideload a rom to your internal sd card
No, i don´t have any rom in the phone...i´m now trying the last option...the sideload-thing...my other computer is very slow...so it will take while...but how i can get the phone like it was when i bought it ? So no root access and stock rom and so on ???
Click to expand...
Click to collapse

sandelin85 said:
n1234d said:
Okay, do you have any rom(eg. ARHD).zip on your phone? If you do, flash that via twrp, and you're done
If you don't, copy a rom to a USB flash drive and connect it to your phone with an OTG Cable, and flash it via twrp
If you don't have an OTG cable, try this to sideload a rom to your internal sd card
No, i don´t have any rom in the phone...i´m now trying the last option...the sideload-thing...my other computer is very slow...so it will take while...but how i can get the phone like it was when i bought it ? So no root access and stock rom and so on ???
Click to expand...
Click to collapse
Boot your phone into bootloader-fastboot
Connect it to your pc so it shows fastboot-usb
then open cmd in the folder containing adb.exe (press shift+right click>open command prompt window here) and type fastboot getvar all
Post results after removing IMEI and serial no.
Click to expand...
Click to collapse

n1234d said:
sandelin85 said:
Boot your phone into bootloader-fastboot
Connect it to your pc so it shows fastboot-usb
then open cmd in the folder containing adb.exe (press shift+right click>open command prompt window here) and type fastboot getvar all
Post results after removing IMEI and serial no.
Click to expand...
Click to collapse
Now my computer with newest drivers and windows 7 would not even recognice the phone...damn, i´m stuck...again ! Samsung S4 was much easier...i made it a brick, then i connect to safe mode, and samsung kies rescue everything
Click to expand...
Click to collapse

sandelin85 said:
n1234d said:
Now my computer with newest drivers and windows 7 would not even recognice the phone...damn, i´m stuck...again ! Samsung S4 was much easier...i made it a brick, then i connect to safe mode, and samsung kies rescue everything
Click to expand...
Click to collapse
When your phone is in fastboot, type
fastboot devices
Does it list your phone?
If it doesn't, try changing USB ports/cord, and also try uninstalling and then fresh installing new drivers after restarting your pc, then connecting your phone.
Sent from my iPod touch using Tapatalk
---------- Post added at 12:26 AM ---------- Previous post was at 12:22 AM ----------
And what happened to the sideload? Did the rom zip get copied?
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse

How are you getting on? You most likely haven't bricked your ONE
Sent from my HTC One using XDA Premium 4 mobile app

When your phone is in fastboot, type
fastboot devices
Does it list your phone?
If it doesn't, try changing USB ports/cord, and also try uninstalling and then fresh installing new drivers after restarting your pc, then connecting your phone.
Now it finds it again
nd what happened to the sideload? Did the rom zip get copied?
Sideload would not connect, it fails all the time...
How are you getting on? You most likely haven't bricked your ONE
I have tried all things that you guys have suggested...i can´t get any of them to work, for now...So hard find all the right links and so on...i´m not great with android...is there any video or story, how to do that ? I suck My english also, i´m from Finland

It's definitely NOT bricked. I'll keep an eye on this thread, you're getting great help but if you don't end up getting it fixed send me a PM, I sometimes forget about a thread I need to check back in on. It's for sure fixable and there's great advice in here.
Edit I somehow missed your last post before posting this. Send me a PM, and I'll help you get it fixed up after work.

sandelin85 said:
When your phone is in fastboot, type
fastboot devices
Does it list your phone?
If it doesn't, try changing USB ports/cord, and also try uninstalling and then fresh installing new drivers after restarting your pc, then connecting your phone.
Now it finds it again
nd what happened to the sideload? Did the rom zip get copied?
Sideload would not connect, it fails all the time...
How are you getting on? You most likely haven't bricked your ONE
I have tried all things that you guys have suggested...i can´t get any of them to work, for now...So hard find all the right links and so on...i´m not great with android...is there any video or story, how to do that ? I suck My english also, i´m from Finland
Click to expand...
Click to collapse
ok so fastboot is working, as suggested before post a "fastboot getvar all" (remove IMEI and s/n).
If sideload isn't working you can use "adb push", but first thing is to reflash custom recovery just in case it's corrupted.
so download CWM or TWRP (from the threads in xda), then
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
then
adb push <name of rom>.zip /sdcard/ (this will take anywhere between 5 to 15minutes and not show progress, eventually it should come back with "success")
then
install zip in recovery, and choose the <name of rom>.zip and install it.

So im about to flash stock 5.1 - I need the fastboot victara s driver

Phone connects no problem until its time to boot into fastboot mode. It wont connect. I go back to device manager, Its saying I dont have the driver for fastboot victara s. Hopefully someone knows a thing or two about this.

If you mean Motorola ADB interface, try installing these:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481

Gus.Ottawa said:
If you mean Motorola ADB interface, try installing these:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Click to expand...
Click to collapse
Yeah I have that installed, thanks though.

[HELP]Making ADB work with Moto G 2014

Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?

Tenderenden said:
Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?
Click to expand...
Click to collapse
at first learn what ADB is.
at second - fastboot it the proper place to begin with.

PsyClip-R said:
at first learn what ADB is.
at second - fastboot it the proper place to begin with.
Click to expand...
Click to collapse
Well, fastboot don't want to work neither so that answer didn't help at all

Tenderenden said:
How can I fix this?
Click to expand...
Click to collapse
ADB can only be used from a fully booted device (you have to be past the login screen. It's a security measure so no one can mess with your data without approval). You can use fastboot commands though.
Try this
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
XXXXXXXXXXfastboot
Now do your thing, like flashing stock ROM. Multiple tutorials exist for that.

doppelhelix said:
ADB can only be used from a fully booted device (you have to be past the login screen. It's a security measure so no one can mess with your data without approval). You can use fastboot commands though.
Try this
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
XXXXXXXXXXfastboot
Now do your thing, like flashing stock ROM. Multiple tutorials exist for that.
Click to expand...
Click to collapse
That is the answer that I needed!
Can I somehow pull data from this phone using fastboot? Because I think that flashing stock ROM will erase any personal data, but I really need to get it.

Tenderenden said:
That is the answer that I needed!
Can I somehow pull data from this phone using fastboot?
Click to expand...
Click to collapse
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.

doppelhelix said:
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.
Click to expand...
Click to collapse
Okay, I got it. Now, have you got any suggestions how to get contacts and (hopefully) SMS back?

Tenderenden said:
how to get contacts and (hopefully) SMS back?
Click to expand...
Click to collapse
Contacts are synchronised with your Google account (unless you choosed not to). Can't say the same about SMS.

doppelhelix said:
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.
Click to expand...
Click to collapse
Loading custom recovery via
fastboot boot TWRP.img should do the job.
than one can can make a full backup, which might be extracted on pc as a regular archive.

PsyClip-R said:
Loading custom recovery via
fastboot boot TWRP.img should do the job.
Click to expand...
Click to collapse
Does this work with locked bootloader? That would be really messed up.

Tenderenden said:
Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?
Click to expand...
Click to collapse
Is your bootloader locked?
Can you try fastboot oem partition dump userdata (using mfastboot, not Google's fastboot)?

PsyClip-R said:
Loading custom recovery via
fastboot boot TWRP.img should do the job.
than one can can make a full backup, which might be extracted on pc as a regular archive.
Click to expand...
Click to collapse
I will try that. Firstly my friend want to message the seller to get his phone repaired. So I can not touch anything in software until he is done.
doppelhelix said:
Contacts are synchronised with your Google account (unless you choosed not to). Can't say the same about SMS.
Click to expand...
Click to collapse
Unfortunately in this case contacts weren't synchronised.
LuK1337 said:
Is your bootloader locked?
Can you try fastboot oem partition dump userdata (using mfastboot, not Google's fastboot)?
Click to expand...
Click to collapse
Well, it seems that I have to read something more about what you said here firstly xD
And the bootloader is locked.
But I appreciate any new idea that may lead to solving this problem.

Tenderenden said:
I will try that. Firstly my friend want to message the seller to get his phone repaired. So I can not touch anything in software until he is done.
Unfortunately in this case contacts weren't synchronised.
Well, it seems that I have to read something more about what you said here firstly xD
And the bootloader is locked.
But I appreciate any new idea that may lead to solving this problem.
Click to expand...
Click to collapse
fastboot oem partition dump userdata may work with locked BL and it'd be great to know if it does...

LuK1337 said:
fastboot oem partition dump userdata may work with locked BL and it'd be great to know if it does...
Click to expand...
Click to collapse
I will try it as fast as I can. Thanks

Fastboot error Android Q

Hi guyz i wanted to root my phone for enabling camera2api. İ did it on Android 9 and worked perfectly. But i disabled it for updating to Android 10. Now im trying to boot patched boot for installing magisk. Everything is okay untill i type adb reboot bootloader for entering fastboot mode and boot img file. When it enters to fastboot mode i type fastboot devices for checking phone but nothing happening and when i type fastboot boot patched_boot.img it says waiting for device and nothing happening. Also when it restarts, usb debugging automatically turning off. İm turning it on checking phone with abd everything is okay but when it restarts from fastboot usb debugging turns off. Any help? İdk if its bug or im doing something wrong

Maharram said:
Hi guyz i wanted to root my phone for enabling camera2api. İ did it on Android 9 and worked perfectly. But i disabled it for updating to Android 10. Now im trying to boot patched boot for installing magisk. Everything is okay untill i type adb reboot bootloader for entering fastboot mode and boot img file. When it enters to fastboot mode i type fastboot devices for checking phone but nothing happening and when i type fastboot boot patched_boot.img it says waiting for device and nothing happening. Also when it restarts, usb debugging automatically turning off. İm turning it on checking phone with abd everything is okay but when it restarts from fastboot usb debugging turns off. Any help? İdk if its bug or im doing something wrong
Click to expand...
Click to collapse
AFAIK, your first point of reference is the fastboot issue. As long as device isn't recognized in fastboot mode, you won't be able to proceed. Drivers ? USB debugging on and authorized with the PC ? Command prompt being used with elevated rights ?
Regarding Cam2Api, I used a Magisk Module since I use Magisk.

Tianhe said:
AFAIK, your first point of reference is the fastboot issue. As long as device isn't recognized in fastboot mode, you won't be able to proceed. Drivers ? USB debugging on and authorized with the PC ? Command prompt being used with elevated rights ?
Regarding Cam2Api, I used a Magisk Module since I use Magisk.
Click to expand...
Click to collapse
Yep i used magisk module too. Yeah usb debugging on and authorized with pc but not recognized on fastboot mode ( adb mode works )

Maharram said:
Yep i used magisk module too. Yeah usb debugging on and authorized with pc but not recognized on fastboot mode ( adb mode works )
Click to expand...
Click to collapse
I know this might sound silly but are you using the latest platform tools version ?

Tianhe said:
I know this might sound silly but are you using the latest platform tools version ?
Click to expand...
Click to collapse
Yeah. Everytime i used 1.4.3 but this time specially downloaded latest version of adb and platform tools (from What is Adb post on xda)

Maharram said:
Yeah. Everytime i used 1.4.3 but this time specially downloaded latest version of adb and platform tools (from What is Adb post on xda)
Click to expand...
Click to collapse
The only thing I can think of right now is Windows version. I have faced issues on Windows 10 but not in Windows 7. Also try downloading the Platform Tools from developer.android.com (adb is already available in the folder)

Tianhe said:
The only thing I can think of right now is Windows version. I have faced issues on Windows 10 but not in Windows 7
Click to expand...
Click to collapse
Yeah im using win 10 redstone (latest version)
But also i did it on win 10 with Android 9

Tianhe said:
The only thing I can think of right now is Windows version. I have faced issues on Windows 10 but not in Windows 7. Also try downloading the Platform Tools from developer.android.com (adb is already available in the folder)
Click to expand...
Click to collapse
Going to try this. Thanks a lot <3

Maharram said:
Going to try this. Thanks a lot <3
Click to expand...
Click to collapse
Hope you get the desired result. I am also on Win 10 latest update and I had faced issues initially. I have also added a registry hack so that everytime I open CMD with shift+right click it opens with administrator privileges.