Database Develop

[Q] Bricked phone Need Help

I bricked my phone. I think its a softbrick because i can still get into HBoot. I had rooted the phone using htconeroot.com and wanted to go back to stock. and I tried using htc1guru.com to go back to complete stock and It worked but the touch did not work and I was back to 4.1.2. So i did the 4.3 update and now I get hung up on the HTC Logo and have no recovery. All I want to do is go back to stock like it originally was and getting my phone working again. Here is the information I believe will help.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4183mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks. Oh and the bootloader says ***TAMPERED*** ***UNLOCKED***

jsjgamer said:
I bricked my phone. I think its a softbrick because i can still get into HBoot. I had rooted the phone using htconeroot.com and wanted to go back to stock. and I tried using htc1guru.com to go back to complete stock and It worked but the touch did not work and I was back to 4.1.2. So i did the 4.3 update and now I get hung up on the HTC Logo and have no recovery. All I want to do is go back to stock like it originally was and getting my phone working again. Here is the information I believe will help.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4183mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks. Oh and the bootloader says ***TAMPERED*** ***UNLOCKED***
Click to expand...
Click to collapse
Try this thread, should just need to relock bootloader and flash, Browse thread first.
http://forum.xda-developers.com/showthread.php?t=2496074

532499 12027
mb_guy said:
Try this thread, should just need to relock bootloader and flash, Browse thread first.
http://forum.xda-developers.com/showthread.php?t=2496074
Click to expand...
Click to collapse
What about the Stock Recovery?

jsjgamer said:
What about the Stock Recovery?
Click to expand...
Click to collapse
Don't think it matters

mb_guy said:
Don't think it matters
Click to expand...
Click to collapse
So once I got the file downloaded exactly how do I flash the stock ROM on and will I still be able to update to 4.4.2?

jsjgamer said:
So once I got the file downloaded exactly how do I flash the stock ROM on and will I still be able to update to 4.4.2?
Click to expand...
Click to collapse
Using fastboot, Just google for info
Here is one
http://forum.xda-developers.com/showthread.php?t=2497614
Notice you have to run the flash command twice!!!

mb_guy said:
Using fastboot, Just google for info
Here is one
http://forum.xda-developers.com/showthread.php?t=2497614
Notice you have to run the flash command twice!!!
Click to expand...
Click to collapse
So I ran the .exe the first time got an error like the forum said. I am trying to run it a second time and it is stuck on Verifying Information on your android phone. Please wait. Screen I have is a Black and Sliver HTC Logo.

jsjgamer said:
So I ran the .exe the first time got an error like the forum said. I am trying to run it a second time and it is stuck on Verifying Information on your android phone. Please wait. Screen I have is a Black and Sliver HTC Logo.
Click to expand...
Click to collapse
Can you flash recovery via fastboot?

CYNiCAL2KX said:
Can you flash recovery via fastboot?
Click to expand...
Click to collapse
I downloaded the stock recovery But not sure how to flash it to my phone.

jsjgamer said:
I downloaded the stock recovery But not sure how to flash it to my phone.
Click to expand...
Click to collapse
to flash a custom recovery
I'm hoping you have knowledge of adb or slightly at least. If not, do some googling and brush up because it's very handy (and easy)
Boot phone into bootloader
1. connect to PC, your phone should read 'Fastboot USB'
2. Open a cmd window in adb/fastboot folder (Shift and right click, then chose 'Open command window here')
3. drag a recovery.img (TWRP or CWM) into the adb folder too
4. type: fastboot flash recovery recovery.img, it should flash within a couple of seconds
then you can try using the recovery to sideload a rom via adb.
I'm not sure about stock since i've never had any issues with custom roms recoverys etc. but many guides are available if you are trying to revert to stock.
good luck

CYNiCAL2KX said:
to flash a custom recovery
I'm hoping you have knowledge of adb or slightly at least. If not, do some googling and brush up because it's very handy (and easy)
Boot phone into bootloader
1. connect to PC, your phone should read 'Fastboot USB'
2. Open a cmd window in adb/fastboot folder (Shift and right click, then chose 'Open command window here')
3. drag a recovery.img (TWRP or CWM) into the adb folder too
4. type: fastboot flash recovery recovery.img, it should flash within a couple of seconds
then you can try using the recovery to sideload a rom via adb.
I'm not sure about stock since i've never had any issues with custom roms recoverys etc. but many guides are available if you are trying to revert to stock.
good luck
Click to expand...
Click to collapse
Still not working. I tried to put TWRP and i get error: cannot load 'openrecovery-twrp-2.5.0.0-m7.img'

1. Please use TWRP 2.6.3.3
2. That error means that the TWRP files is NOT in the same location where fastboot file is.

SaHiLzZ said:
1. Please use TWRP 2.6.3.3
2. That error means that the TWRP files is NOT in the same location where fastboot file is.
Click to expand...
Click to collapse
Got TWRP 2.7 installed now I cannot get it to mount so i can a zip on it.

jsjgamer said:
Got TWRP 2.7 installed now I cannot get it to mount so i can a zip on it.
Click to expand...
Click to collapse
You can't mount USB via twrp. Sideload or Push is the only 2 options.
drag zip to adb folder
adb sideload rom.zip
then wait until it's done, the script should run automatically on the phone after completion

CYNiCAL2KX said:
You can't mount USB via twrp. Sideload or Push is the only 2 options.
drag zip to adb folder
adb sideload rom.zip
then wait until it's done, the script should run automatically on the phone after completion
Click to expand...
Click to collapse
will I get any indication on the computer when sideload is ready? What is push?

jsjgamer said:
will I get any indication on the computer when sideload is ready? What is push?
Click to expand...
Click to collapse
In your recovery, choose advanced. Then Sideload
then swipe to begin sideload.
Now, enter the command : adb sideload rom.zip
then wait until it's complete, it'll show progress status in adb, your phone will automatically run the script once the file has been recieved by your phone.

CYNiCAL2KX said:
In your recovery, choose advanced. Then Sideload
then swipe to begin sideload.
Now, enter the command : adb sideload rom.zip
then wait until it's complete, it'll show progress status in adb, your phone will automatically run the script once the file has been recieved by your phone.
Click to expand...
Click to collapse
Ok. I will try that and let you know how it goes.

CYNiCAL2KX said:
In your recovery, choose advanced. Then Sideload
then swipe to begin sideload.
Now, enter the command : adb sideload rom.zip
then wait until it's complete, it'll show progress status in adb, your phone will automatically run the script once the file has been recieved by your phone.
Click to expand...
Click to collapse
So I got this ROM http://forum.xda-developers.com/showthread.php?t=2626050 The Odexed version and it said successful. How long should it be before it boots up all the way? I have been on the HTC Logo for about 2 mins now.

jsjgamer said:
So I got this ROM http://forum.xda-developers.com/showthread.php?t=2626050 The Odexed version and it said successful. How long should it be before it boots up all the way? I have been on the HTC Logo for about 2 mins now.
Click to expand...
Click to collapse
What phone do you have? that post is a rom for Droid DNA?

CYNiCAL2KX said:
What phone do you have? that post is a rom for Droid DNA?
Click to expand...
Click to collapse
HTC One on T-Mobile

[Q] Bricked HTC m7, No OS, No restore

I have a big problem!
I do not know what really did! But did something very wrong!
I have access to bottloader, fastboot and TWRP v2.6.3.0.
The TWRP complains that there is no operating system and really no files to recover somewhere!
Could anyone help me?
Fastboot getvar all
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.707.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4301mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-59adc32b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Thank you for attention

First of all, it's not bricked, bricked is when it's nothing more than a paper weight, if you can get into recovery and bootloaader then it's far from a brick.
Do you know how to use adb and fastboot, if so..........
Download a Rom of your choice for your device
Place the Rom in the same folder as adb and fastboot on your computer
Put your phone into recovery, and plug into your computer
Open a command window on your computer in the adb folder and type:
Adb push (Rom name).zip /sdcard/
Wait........
Wait some more.......
Make a cup of tea.......
Take ages, wait until it's finished
Unplug your phone from your computer when it's finished
Now on your phone in recovery select instal, you should see the Rom you just pushed in the list, follow the instructions.
In future don't advanced wipe in twrp

Seanie280672 said:
First of all, it's not bricked, bricked is when it's nothing more than a paper weight, if you can get into recovery and bootloaader then it's far from a brick.
Do you know how to use adb and fastboot, if so..........
Download a Rom of your choice for your device
Place the Rom in the same folder as adb and fastboot on your computer
Put your phone into recovery, and plug into your computer
Open a command window on your computer in the adb folder and type:
Adb push (Rom name).zip /sdcard/
Wait........
Wait some more.......
Make a cup of tea.......
Take ages, wait until it's finished
Unplug your phone from your computer when it's finished
Now on your phone in recovery select instal, you should see the Rom you just pushed in the list, follow the instructions.
In future don't advanced wipe in twrp
Click to expand...
Click to collapse
C:\Users\fabre_000\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools
>adb push RUU_M7_U_JB_50_hTC_Asia_WWE_1.29.707.4_R_Radio_4A.14.3250.13_10.33.115
0.01_release_312087_signed_2_4.zip /sdcard/
error: device not found
I tried the instructions you gave me, but it did not work.
I have adb and fastboot in the same folder. Fastboot commands work, but not adb

When your in recovery can you see your phone in device manager on your computer ?
Also make sure to type adb in lower case letters, everything else has to be as it appears, your better off naming your Rom to just Rom.zip for ease.

yea. I see in the device manager when selecting recovery TRWP
ok. I try rename RUU.
I'm waiting, now!

Ok. Not work! =T
Updating partition detalis...
E: Storage partition '//TWRP/BACKUPS/FA35XW91781
E: Unable to open zip file.
Error flashing zip '/sdcard/ruu.zip'

I would try with a custom Rom, something like viper one etc, it's a bit tricky with a stock Rom especially as you are s-on, very hard to get the correct file.
Same again though, once downloaded, rename it to Rom.zip for ease.

Seanie280672 said:
I would try with a custom Rom, something like viper one etc, it's a bit tricky with a stock Rom especially as you are s-on, very hard to get the correct file.
Same again though, once downloaded, rename it to Rom.zip for ease.
Click to expand...
Click to collapse
Ok
I'm dowloading VIPERONE 6.2.0 and I will proceed the same process

Good Rom, I'm using it now.
I checked your output with the Rom your downloaded before, and although the carrier matches, defined by the 707, it a much earlier Rom to what you have on your phone now and an older radio, this maybe why you experienced problems flashing it.

You are God, Seannie! You revived my htc! :good:
Brutal! Thank you!
I'm satisfied! But I would leave it as the factory, with stock rom. You could guide me for this? If yes, I can donate for your work. I would be grateful!

andrekerplunk said:
You are God, Seannie! You revived my htc! :good:
Brutal! Thank you!
I'm satisfied! But I would leave it as the factory, with stock rom. You could guide me for this? If yes, I can donate for your work. I would be grateful!
Click to expand...
Click to collapse
What you need is the guru reset Rom to do that, look for yours 707, in the flashable ruu section, but his site is down at the moment, been down for a few days, www.guru1reset.com
Glad you got it working again though. Loads of themes for that Rom in the theme section.

Htc m7 dual complete bricked
Hi!
Having Htc m7 cdwg
It's completely bricked ,
On oning stuck Htc boot logo,
Can access only Htc fastboot mode, but no debug, no recovery mode
Please help me out how to revive my phone

failed to return to stock from cyanogen

Had cyanogenmod installed but wanted to revert back to stock. I am now unable to install any roms and only have access to bootloader and CWM. I have tried running RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2 from my pc but the program closes after the terms and conditions, and my attempts to flash a rom or sideload from cwm have failed as well.
M7-UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4T.24.3218.09
OpenDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MB
Jan 28 2014. 09:32:41.0
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT39MW903199
(bootloader) imei: 354439057262075
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4320mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

You must first extract the boot.img for whatever rom you are trying to flash and fastboot flash that first before trying to install the rom.
Cyanogen is a non sense rom and uses a different kind of boot, that's why your experiencing the problem you have.

Seanie280672 said:
You must first extract the boot.img for whatever rom you are trying to flash and fastboot flash that first before trying to install the rom.
Cyanogen is a non sense rom and uses a different kind of boot, that's why your experiencing the problem you have.
Click to expand...
Click to collapse
What the heck are you talking about .?? :silly:
OP.. You need to sideload a custom rom, or restore a nandroid backup from ATT firmware matching the main-version.. 4.18.502.7
There are a few restore threads around detailing this, so please help yourself!

Seanie280672 said:
You must first extract the boot.img for whatever rom you are trying to flash and fastboot flash that first before trying to install the rom.
Click to expand...
Click to collapse
@SaHiLzZ
I remember having to flash the boot.img manually each time you flash a custom rom on the endeavoru (One X) but this is not required for the M7

SaHiLzZ said:
OP.. You need to sideload a custom rom, or restore a nandroid backup from ATT firmware matching the main-version.. 4.18.502.7
Click to expand...
Click to collapse
Ive tried sideloading but it doesnt work, idk if Im just not trying to load the right file or what.

So the error is. ?

SaHiLzZ said:
So the error is. ?
Click to expand...
Click to collapse
* failed to write data 'protocol fault (no status)' * usually gets to about 80-90% then gives me this

nwmn9386 said:
* failed to write data 'protocol fault (no status)' * usually gets to about 80-90% then gives me this
Click to expand...
Click to collapse
HAve you tried adb push instead of side load, I suggest you wipe internal memory first if possible though.
Put the rom in your fastboot / adb folder, open a command windows there, Control + Shift + right mouse click and select open command window here then type
adb push (filename).zip /sdcard/
EDIT: sorry forgot to add you must be in recovery main screen to do this obviously with the phone plugged into the computer too.

Seanie280672 said:
HAve you tried adb push instead of side load, I suggest you wipe internal memory first if possible though.
Put the rom in your fastboot / adb folder, open a command windows there, Control + Shift + right mouse click and select open command window here then type
adb push (filename).zip /sdcard/
EDIT: sorry forgot to add you must be in recovery main screen to do this obviously with the phone plugged into the computer too.
Click to expand...
Click to collapse
Keep getting the error "E:Can't mount/SD card" whenever i try to run it on my phone
fixed this error, just needed to format the /sdcard. the rom that i pushed ran but didnt install correctly so i think i may just be trying to install the wrong file

nwmn9386 said:
Keep getting the error "E:Can't mount/SD card" whenever i try to run it on my phone
fixed this error, just needed to format the /sdcard. the rom that i pushed ran but didnt install correctly so i think i may just be trying to install the wrong file
Click to expand...
Click to collapse
Yes, I said you may have to wipe the internal storage, ie sd card.
Try and push and install a custom Rom, pretty much anyone from the M7 android development thread as you have an M7UL, however I would recommend viper one or ARHD.
However the ruu that you are trying to flash seems to be the right one, just checked the details against your output, same radio and firmware, you could always try and get the guru reset Rom zip for your device, just go to www.htc1guru.com and see if there is one there.

[Q] Htc One M7- deleted operating system. Relocked bootloader

Hi guys,
I have a big problem with my HTC One. I wanted to give it to the service, but it costs a lot of money, maybe I will find some help on XDA hopefully.
My bootloader info looks like this:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.57.0000
RADIO- 4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.11.401.10
eMMC-boot 2048MB
May 5 2014,23:16:29.0
I deleted my system partition in twrp recovery. I can get only to bootloader and recovery. I am S-ON all the time, cannot get S-OFF, I get errors all the time using rum runner or firewater. When I type fastboot oem lock, I am stuck in bootloader, cannot enter recovery. Then the bootloader says ***TAMPERED*** ***RELOCKED*** ***SECURITY WARNING***. I really don't know what to do, I'm stuck. Please help :C !!!
Thanks

My fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4332mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.099s

GalaXxXx said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4332mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.099s
Click to expand...
Click to collapse
You should remove your imei and serialno in your previous post. You can use this stock rom zip to go back to stock. It is the same version that you have. Your bootloader must be LOCKED or RELOCKED. Move the file to your adb/fastboot folder and rename it rom.zip. Open a command window on the same folder then type the following:
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip rom.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip rom.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse

Thanks a lot @majmoz
I'm downloading zip file now (slow internet 2 hours remaining). I will try your method, and let you know how it went.

doesn't work ;/
@majmoz , it doesn't work .
I did everything you said and when flashing it says "FAILED (remote: 12 signature verify fail)". Did this command 2 times as you instructed.
The second thing is that the "adb reboot bootloader" command didn't work, cmd said that device not found.
What should I do ?

GalaXxXx said:
@majmoz , it doesn't work .
I did everything you said and when flashing it says "FAILED (remote: 12 signature verify fail)". Did this command 2 times as you instructed.
The second thing is that the "adb reboot bootloader" command didn't work, cmd said that device not found.
What should I do ?
Click to expand...
Click to collapse
Does you bootloader still say "Relocked"? Let try to run the stock firmware 5.11.401.10 using the same method, just rename the download to firmware.zip change the rom.zip in the procedure to firmware.zip.
For adb not working take a look at FAQ Q#2.

My bootloader says TAMPERED RELOCKED SECURITY WARNING
I don't think adb works in bootloader, right ?
The firmware.zip worked, (there was the green bar etc.), but the phone is still not rebooting into system.
hmm... there is no custom recovery anymore, just a phone with red sign. And in bootloader it says only tampered and relocked. Without security warning. @majmoz

GalaXxXx said:
My bootloader says TAMPERED RELOCKED SECURITY WARNING
I don't think adb works in bootloader, right ?
The firmware.zip worked, (there was the green bar etc.), but the phone is still not rebooting into system.
hmm... there is no custom recovery anymore, just a phone with red sign. And in bootloader it says only tampered and relocked. Without security warning. @majmoz
Click to expand...
Click to collapse
You are correct adb does not work in bootloader. When the firmware completed it installed the stock recovery. Since you erased the system partition there is no OS installed. You can try to run the RUU again and it will probably pass now since you have the correct firmware. If this is successful, you will have stock rom and stock firmware on your phone.
What did you mean by give to service?

majmoz said:
You are correct adb does not work in bootloader. When the firmware completed it installed the stock recovery. Since you erased the system partition there is no OS installed. You can try to run the RUU again and it will probably pass now since you have the correct firmware. If this is successful, you will have stock rom and stock firmware on your phone.
What did you mean by give to service?
Click to expand...
Click to collapse
There is an unbrick service here in the forum
I would imagine that's what he's referring to

You are correct adb does not work in bootloader. When the firmware completed it INSTALLED the stock recovery. Since you erased the system partition there is no OS installed. You can try to run the RUU again and it will probably pass now since you have the correct firmware. If this is successful, you will have stock rom and stock firmware on your phone.
What did you mean by give to service?
Click to expand...
Click to collapse
There is an unbrick service here in the forum
I would imagine that's what he's referring to
Click to expand...
Click to collapse
No no, I have a service nearby here in my town. They said they can restore the phone for $30.
I will try the RUU file now, hope it works. I'll be informing what is the status of my "operation" @majmoz @ajbiz11
P.S. How to quote ? You know (Originally Posted by etc.)

GalaXxXx said:
I did everything you said and when flashing it says "FAILED (remote: 12 signature verify fail)".
Click to expand...
Click to collapse
@majmoz I don't think this zip can be flashed using "fastboot flash zip rom.zip", with s-on he can only flash signed ruu from HTC and afaik, htc never released any 5.11.401.10 signed ruu
There is a flashable aroma zip (guru reset) for his version here: https://www.androidfilehost.com/?fid=23501681358543706
to be flashed with a custom recovery (require to unlock the bootloader again)

Yeah @alray , I need to have a 5.11.401.10 signed RUU, but there is no such file avaible to download.
Now, I will unlock my bootloader again, flash custom recovery (TWRP) , and try flash guru reset in this recovery.
Well, I don't really remember, but I think I tried this (maybe with not the same version of guru reset), but I was stuck on "Installation procces" It was 0 % all the time. Let's see how it works out this time with this version of guru.

@alray
I unlocked my bootloader, flashed TWRP, I used adb to push the .zip to sdcard, but the problem now is that the phone says that unable to mount '/data' and unable to mount internal storage. When I click mount in recovery the "data" box doesn't wanna tick .
What should I do ? I'm tired of this ...

Ok, what happened next... I finally did what @alray told me to do. I managed to fix the corrupted data partition, but as I said earlier, when I flash the guru reset in recovery, and start the installation process, it is stuck on 0.00%.
I unlocked the bootloader in order to do this.
No more ideas ? @majmoz ?

GalaXxXx said:
Ok, what happened next... I finally did what @alray told me to do. I managed to fix the corrupted data partition, but as I said earlier, when I flash the guru reset in recovery, and start the installation process, it is stuck on 0.00%.
I unlocked the bootloader in order to do this.
No more ideas ? @majmoz ?
Click to expand...
Click to collapse
What version of TWRP are you using? 2.6.3.3 or 2.8.0.1? I'm pretty sure you checked the MD5 of the files you downloaded.

I'm using TWRP v2.8.0.2. What do you mean by saying you're pretty sure I checked the MD5? I didn't .. @majmoz

GalaXxXx said:
I'm using TWRP v2.8.0.2. What do you mean by saying you're pretty sure I checked the MD5? I didn't .. @majmoz
Click to expand...
Click to collapse
You should always check the MD5 of downloaded files to ensure they did not get corrupted during the downloading process. The MD5 is generally noted on the download site. Here is a how to check the MD5.

I also recommend to use 2.6.3.3 instead of 2.8+

Ohh my god, finally did it !!! Thank you a lot guys !!! I was trying guru reset earlier with unlocked bootloader too, but the twrp version was wrong... ohh, everything because of this new version of twrp.... But thanks, I have my system back . I will be able to do OTA updates now ?
 @majmoz @alray

GalaXxXx said:
Ohh my god, finally did it !!! Thank you a lot guys !!! I was trying guru reset earlier with unlocked bootloader too, but the twrp version was wrong... ohh, everything because of this new version of twrp.... But thanks, I have my system back . I will be able to do OTA updates now ?
@majmoz @alray
Click to expand...
Click to collapse
you should be able to do ota if you have selected to install stock recovery in the aroma installer.

[solved]How to go back to stock (telekom branded )?

Hey,
can someone point me to the right way to reset my HTC One mini 2 Telekom branding back to stock? I want it in the way it was when i first bought it.
thanks

Hi,
Could you post your getvar all info from ADB WITHOUT IMEI and SERIAL NUMBER.
Thanks..

hey, yeah i really would, but my fastboot does not work. I use the minimal adb fastboot and adb works just fine (adb reboot bootloader) but now fastboot doesn't find the device.
Windows devicemanager shows an Android 1.0 device.

HandyBesitzer said:
hey, yeah i really would, but my fastboot does not work. I use the minimal adb fastboot and adb works just fine (adb reboot bootloader) but now fastboot doesn't find the device.
Windows devicemanager shows an Android 1.0 device.
Click to expand...
Click to collapse
Is the device working ?, have you authorized the device in Developer Options as this impacts the device connection in ADB..
As for ROMs you might find it here, if the device is S-Off any version will do, otherwise the version should be same or higher than the version installed, as for steps and everything else, you can visit here
The basic idea is to have a stock Recovery and stock ROM, to get back to full stock, 1st flash stock Recovery via ADB, then flash stock RUU, NEEDLESS TO MENTION ALL DATA WILL BE WIPED.
The other way is for someone to provide a Nandroid image which you can use TWRP to restore, I doubt this is available anywhere, searched everywhere, this is partial stock.

Hey, the device is working fine and is s-off.
Adb is working, too. Only the fastboot does not Work. So i start with back to stock rom and then i go back to stock Recovery? But how can i flash the stock Recovery without fastboot?

HandyBesitzer said:
Hey, the device is working fine and is s-off.
Adb is working, too. Only the fastboot does not Work. So i start with back to stock rom and then i go back to stock Recovery? But how can i flash the stock Recovery without fastboot?
Click to expand...
Click to collapse
When you say fastboot does not work, could you elaborate a bit more ? Can you enter fastboot but the device does not show ? Do you have the USB drivers installed for your device ? uninstall the software that came with device, just install the USB drivers, fastboot requires authorization from device, does your device receive authorization, if not then you can Revoke USB Debugging Authorization from developers option, restart device AND you need to remove all traces of USB drivers from PC from device manager (if you are on Windows), restart PC, reinstall drivers, reconnect device, and try to receive authorization to get fastboot to work.
What ROM are you on currently ?
1st you flash Recovery, then you flash ROM.
If fastboot does not work then you will have to flash the RUU via ADB, but again first you have to flash Recovery first via ADB.

tryllz said:
When you say fastboot does not work, could you elaborate a bit more ? Can you enter fastboot but the device does not show ? Do you have the USB drivers installed for your device ? uninstall the software that came with device, just install the USB drivers, fastboot requires authorization from device, does your device receive authorization, if not then you can Revoke USB Debugging Authorization from developers option, restart device AND you need to remove all traces of USB drivers from PC from device manager (if you are on Windows), restart PC, reinstall drivers, reconnect device, and try to receive authorization to get fastboot to work.
What ROM are you on currently ?
1st you flash Recovery, then you flash ROM.
If fastboot does not work then you will have to flash the RUU via ADB, but again first you have to flash Recovery first via ADB.
Click to expand...
Click to collapse
Yeah that's right, i can enter Fastboot but the device does not show up. I think so that i've installed the drivers, since adb works fine. HTC software is and was never installed. USB Debugging is active in the dev settings.
I've lineage OS installed: https://forum.xda-developers.com/one-mini-2/orig-development/rom-lineageos-14-1-one-mini-2-t3602411
But if adb will do, too i'd choose this option. I start with the recovery from here (https://forum.xda-developers.com/one-mini-2/general/htc-one-mini-2-official-ruu-t3425930) but where can i get the Telecom branded ruu?
==EDIT==
i uninstalled and reinstalled the driver and now fastboot is working
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.111011.20.0123
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.19.111.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f807bb3f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
==EDIT2==
I found this collection: http://www.handy-faq.de/forum/htc-one-mini-2-firmwaresammlung-ruus-otas-backups-t309020
I just noticed that i'm still s-on and not s-off. So I'll first flash the recovery 2.19.111.5:
fastboot flash recovery 'filename'
http://www.handy-faq.de/forum/htc-o...ng-ruus-otas-backups-t309020/#comment-2817813
and after that the firmware:
fastboot flashall 'filename'
http://www.handy-faq.de/forum/htc-o...ng-ruus-otas-backups-t309020/#comment-2817816
Or did i forgot something?
==EDIT==
i still had an backup of my own stock rom, so i'm back on HTC Android 4.4.2 with Sense 6.0 and Telekom branding. Only steps i need to do next:
unroot,
remove twrp,
relook bootloader.
will this be done after i flashed the recovery as shown in my edit 2?

HandyBesitzer said:
Yeah that's right, i can enter Fastboot but the device does not show up. I think so that i've installed the drivers, since adb works fine. HTC software is and was never installed. USB Debugging is active in the dev settings.
I've lineage OS installed: https://forum.xda-developers.com/one-mini-2/orig-development/rom-lineageos-14-1-one-mini-2-t3602411
But if adb will do, too i'd choose this option. I start with the recovery from here (https://forum.xda-developers.com/one-mini-2/general/htc-one-mini-2-official-ruu-t3425930) but where can i get the Telecom branded ruu?
==EDIT==
i uninstalled and reinstalled the driver and now fastboot is working
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.111011.20.0123
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.19.111.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f807bb3f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
==EDIT2==
I found this collection: http://www.handy-faq.de/forum/htc-one-mini-2-firmwaresammlung-ruus-otas-backups-t309020
I just noticed that i'm still s-on and not s-off. So I'll first flash the recovery 2.19.111.5:
fastboot flash recovery 'filename'
http://www.handy-faq.de/forum/htc-o...ng-ruus-otas-backups-t309020/#comment-2817813
and after that the firmware:
fastboot flashall 'filename'
http://www.handy-faq.de/forum/htc-o...ng-ruus-otas-backups-t309020/#comment-2817816
Or did i forgot something?
==EDIT==
i still had an backup of my own stock rom, so i'm back on HTC Android 4.4.2 with Sense 6.0 and Telekom branding. Only steps i need to do next:
unroot,
remove twrp,
relook bootloader.
will this be done after i flashed the recovery as shown in my edit 2?
Click to expand...
Click to collapse
Recovery to use for your device : https://androidfilehost.com/?fid=24052804347828369 / The recovery you are point to is for International/European unbranded devices as is my device..
There is going to be a problem seemingly, since you are S-On, you will not be able to flash this RUU for your device since you are already have a higher version and for this RUU an updated version is posted here separately, in this case flashing will fail both via ADB and Fastboot.
Since you have mentioned you have a backup of your own stock ROM, I'm assuming you are talking about Nandroid backup which you have restored, frankly I cannot recall flashing stock recovery after Nandroid restore, you will have to test it out.
HandyBesitzer said:
I just noticed that i'm still s-on and not s-off. So I'll first flash the recovery 2.19.111.5:
fastboot flash recovery 'filename'
http://www.handy-faq.de/forum/htc-o...ng-ruus-otas-backups-t309020/#comment-2817813
Click to expand...
Click to collapse
: CORRECT..
Let me know how it goes..

tryllz said:
Recovery to use for your device : https://androidfilehost.com/?fid=24052804347828369 / The recovery you are point to is for International/European unbranded devices as is my device..
There is going to be a problem seemingly, since you are S-On, you will not be able to flash this RUU for your device since you are already have a higher version and for this RUU an updated version is posted here separately, in this case flashing will fail both via ADB and Fastboot.
Since you have mentioned you have a backup of your own stock ROM, I'm assuming you are talking about Nandroid backup which you have restored, frankly I cannot recall flashing stock recovery after Nandroid restore, you will have to test it out.
Let me know how it goes..
Click to expand...
Click to collapse
yeah it was a nandroid. Next step i flashed the recovery (branded version found here: http://www.handy-faq.de/forum/htc-o...ng-ruus-otas-backups-t309020/#comment-2817813
and now when i select recovery from hboot i get a black screen showing a smartphone with an red ! on it. I guess that's what the stock recovery does, correct?
so last step, how can i relock the bootloader?

Given your response, could you confirm your device can boot OS, as the red ! mark appears when there is no OS ?!
If no OS then I need some time to find the updated version RUU, else the only option remaining is to keep it Nandroid with TWRP for partial stock..
If OS boots then you can use command
Code:
fastboot oem lock
to relock bootloader..

tryllz said:
Given your response, could you confirm your device can boot OS, as the red ! mark appears when there is no OS ?!
If no OS then I need some time to find the updated version RUU, else the only option remaining is to keep it Nandroid with TWRP for partial stock..
If OS boots then you can use command
Code:
fastboot oem lock
to relock bootloader..
Click to expand...
Click to collapse
red ! is only when i boot into bootloader and select recovery. Otherwise stock T-branded Android 4.4.2 boot perfectly. locking worked fine as well.
Thank you for your help, everything is stock again :good:

HandyBesitzer said:
red ! is only when i boot into bootloader and select recovery. Otherwise stock T-branded Android 4.4.2 boot perfectly. locking worked fine as well.
Thank you for your help, everything is stock again :good:
Click to expand...
Click to collapse
Appreciate the update..